
From nobody Sat Apr  1 11:16:38 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A96B12964B for <ietf@ietfa.amsl.com>; Sat,  1 Apr 2017 11:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.275
X-Spam-Level: 
X-Spam-Status: No, score=-2.275 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_GREY=0.424] 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 IXeB2Dm-EFPT for <ietf@ietfa.amsl.com>; Sat,  1 Apr 2017 11:16:35 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 6CB6A129512 for <ietf@ietf.org>; Sat,  1 Apr 2017 11:16:35 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id i203so50121655ywc.3 for <ietf@ietf.org>; Sat, 01 Apr 2017 11:16:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=sVXpAcM6AFtcchlk59pRAW+0TiI66xkdnanzgPT6exk=; b=Bz2iIeqAItZK1mndW1YUI07xV3GxpR4POeO+36tr6RBInCCMFhqTrK0QJB0KC9zvFd 59wuLd730YNycdPzX7GpOmgdAfMzi2zv6WYMYhWJnjtaNbxdgHNgA1Nzk/e/CxWoQBl6 IE4G/wxsj7oxVfm1u2x2Ti54IXYlZeXDzmCtIb2rehkI6uNzLZfoVD87QulGrfnuKE93 eQUC8MiYqiK2g2AIMvoztLnYM67QH8X+lY5fm+Cx0VIdQXnvjiEysbuzkrqS2vqcRu2D sp66aL3gJ1/rTupD4EK45hloDhvEBvI/kfJ77IdtRVSe65ON3pzvEC9xn8WCK3HfYhJh gzOA==
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; bh=sVXpAcM6AFtcchlk59pRAW+0TiI66xkdnanzgPT6exk=; b=UxnAmC6gAdrr+QOAVnfxBIQBAXdIAN2OQ7iGJwasP1W2shOfzYY8H0V9iPcVeA+bk0 oGK6Cze6P+zrD/02iU0Ic5h3OGxF09bjcdRroEofrstg1mTRMAVufF+WQ8RgrML83YNN B1SHlrsQ9m5LcFvm0h+gQYISnwSbbxyXzynHYezfvBkHMq3C0DGubZj+csu7jMgQkWh0 c8ByaIkj6LgfH/KTlAIgwkK5tkXNC286iPG6idxVmFtR9rrS+Hl3BXNKbl+orbN+89RL oFlHvJS9i9Y2BrDahX6hfwRvX9dYrf7ymoFSVmmFDxcObtP5gLXKSxjKW5w6OYUwbN2P 2CWw==
X-Gm-Message-State: AFeK/H1Rz/CoH6LVzgXfHVCwrLp1Bkf3PsW2XsYNdpJLCyz9S+hAkOz8ti63yKv8IALt42gAap8hv7n3jS0MCA==
X-Received: by 10.129.196.67 with SMTP id s3mr6668503ywj.248.1491070594437; Sat, 01 Apr 2017 11:16:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.73.129 with HTTP; Sat, 1 Apr 2017 11:16:33 -0700 (PDT)
Received: by 10.37.73.129 with HTTP; Sat, 1 Apr 2017 11:16:33 -0700 (PDT)
In-Reply-To: <eb1bb52f-490f-a04d-64cc-a7522cd4835c@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <eb1bb52f-490f-a04d-64cc-a7522cd4835c@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 1 Apr 2017 13:16:33 -0500
Message-ID: <CAKKJt-ef3bHKTM4GvvWk5bo972Es+Y4vRyvwoPdpZtmKTgoshw@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c1a85f61dd898054c1eedbf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h4kYeB8agkXoovJPKtVCg44ab8E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Apr 2017 18:16:37 -0000

--94eb2c1a85f61dd898054c1eedbf
Content-Type: text/plain; charset=UTF-8

If you haven't seen it, there's also a surveymonkey link about border
crossing experiences at IETF 98 that is also appropriate for people who
stayed home because of concerns and for US attendees who didn't cross
borders, and the last question on the questionnaire is roughly "do you have
concerns about future US meetings".

I sent my comments there.

https://www.surveymonkey.com/r/WMNH9PS

I assume the survey entries will become publicly available at some point -
attendee surveys usually do.

Thanks,

Spencer

On Mar 31, 2017 18:58, "Stewart Bryant" <stewart.bryant@gmail.com> wrote:

>
>
> On 31/03/2017 15:42, Eliot Lear wrote:
>
>> Hi,
>>
>>
>> On 3/31/17 9:18 AM, IAOC Chair wrote:
>>
>>> The IAOC remains committed to soliciting input on future IETF meeting
>>> locations. With this mail, we are soliciting input on some potential IETF
>>> locations, including one where we have met before, but for which conditions
>>> may have changed.
>>>
>>> Specifically, we seek community input on reasons we could not have a
>>> successful meeting in any of the following cities, or of any limits to
>>> attendee accessibility or inclusiveness that should be considered:
>>>
>>> Ottawa
>>> San Francisco
>>> Austin, TX
>>> Barcelona
>>> Boston
>>> Busan - looks expensive to get to
>>> Calgary - also looks expensive to get to
>>> Denver
>>> Helsinki
>>> Houston
>>> New Orleans
>>> Osaka
>>> Philadelphia
>>> Washington DC
>>>
>>
>> To save everyone doing it, it would be good to show representative
> airfares and times from a major hub in Europe, East and West Coast, and Asia
>
> I am sure cost and travel time will impact acceptability.
>
> - Stewart
>
>

--94eb2c1a85f61dd898054c1eedbf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">If you haven&#39;t seen it, there&#39;s also a surveymonk=
ey link about border crossing experiences at IETF 98 that is also appropria=
te for people who stayed home because of concerns and for US attendees who =
didn&#39;t cross borders, and the last question on the questionnaire is rou=
ghly &quot;do you have concerns about future US meetings&quot;.<div dir=3D"=
auto"><br></div><div dir=3D"auto">I sent my comments there.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://www.surveymonkey.c=
om/r/WMNH9PS">https://www.surveymonkey.com/r/WMNH9PS</a><br></div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I assume the survey entries will beco=
me publicly available at some point - attendee surveys usually do.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Spencer</div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Mar 31, 2017 18:58, &quot;Stewart Bryant&qu=
ot; &lt;<a href=3D"mailto:stewart.bryant@gmail.com">stewart.bryant@gmail.co=
m</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br=
>
<br>
On 31/03/2017 15:42, Eliot Lear wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
<br>
On 3/31/17 9:18 AM, IAOC Chair wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IAOC remains committed to soliciting input on future IETF meeting locat=
ions. With this mail, we are soliciting input on some potential IETF locati=
ons, including one where we have met before, but for which conditions may h=
ave changed.<br>
<br>
Specifically, we seek community input on reasons we could not have a succes=
sful meeting in any of the following cities, or of any limits to attendee a=
ccessibility or inclusiveness that should be considered:<br>
<br>
Ottawa<br>
San Francisco<br>
Austin, TX<br>
Barcelona<br>
Boston<br>
Busan - looks expensive to get to<br>
Calgary - also looks expensive to get to<br>
Denver<br>
Helsinki<br>
Houston<br>
New Orleans<br>
Osaka<br>
Philadelphia<br>
Washington DC<br>
</blockquote>
<br>
</blockquote>
To save everyone doing it, it would be good to show representative airfares=
 and times from a major hub in Europe, East and West Coast, and Asia<br>
<br>
I am sure cost and travel time will impact acceptability.<br>
<br>
- Stewart<br>
<br>
</blockquote></div></div>

--94eb2c1a85f61dd898054c1eedbf--


From nobody Sat Apr  1 15:51:36 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D27B127337 for <ietf@ietfa.amsl.com>; Sat,  1 Apr 2017 15:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 c2AmvhwsFfUF for <ietf@ietfa.amsl.com>; Sat,  1 Apr 2017 15:51:34 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::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 4F4F5127BA3 for <ietf@ietf.org>; Sat,  1 Apr 2017 15:51:34 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id w11so5202211itb.0 for <ietf@ietf.org>; Sat, 01 Apr 2017 15:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:organization:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=RW5Fc5RnDWQfwRlOe1E3yFbWZEKllg3iED4puXCofBg=; b=rtc49o7NktVMk7hPHkUx7sVgUpW/mCie7j5Tl0m0wBQIY8nDW8OMTf8XWVj0CAStii 32FtUPsfy+LIN/UjUPinzPrIbwjp+W9JrL4gqnFQcwbQdO99Soz+qsN03pX7Y6MHC+gW JJctdTsh54BZTCCVbhuK8v6iPdYgWjhryLLIyUdFxwdKTxHKqRNOI9RIdxQ1mHL9sVAH n9NkG0Vvi+WkBFU4z8xqACOp72eFoQhZbpkOpAEFKcgFXdcLlmZqOUgmt2WFQRSzTkIr 3qmCVviuwHU+6KIATXybKJhwdMa7xDwMO448LI3pTgKXxrsQvStA7lDbHz7gQqNI7Uuj edkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:organization:to:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=RW5Fc5RnDWQfwRlOe1E3yFbWZEKllg3iED4puXCofBg=; b=BnK1hWIcFfoWyOtS//IF8XsDAQCtUFYko5lAj7PAyr1YUqIbHqrHhzbd0/Hmi0E9aO 7MalXe1YhTAB6VYO3NdLS+ttPwFIg2DmPC7/+ZQUGFwmD8sHrKVPF4B54ytbllL24WW+ znWI3qPY7pgrApFfWabh6dzZwG8HKulJLaQkA6xcw0iYmFTkHpmD+rMJh5Rhe1R71IE2 Xl4omeFFtQuvSkBmmOFSQq/nhBbkUADyvYpfx7wGKHNPKopfNjZJm/3uruc+qCov1/n+ gu22H6cRDqrh38QDDXE1FA2wVZPdpcH4KeCGD/PX3yeeudEgE2vgk/YQaNJqxAE4i9Bh eoxg==
X-Gm-Message-State: AFeK/H2AXiCU7HAQ34fJ2sB3qN7hHFS7Pt9R5zvNiIoFpd8xjDUe63bw 190hJLFhqHwyAkwq
X-Received: by 10.36.160.195 with SMTP id o186mr4217102ite.102.1491087093592;  Sat, 01 Apr 2017 15:51:33 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id p140sm3517440itc.27.2017.04.01.15.51.32 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Apr 2017 15:51:32 -0700 (PDT)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Compatibility issue
Organization: University of Auckland
To: IETF discussion list <ietf@ietf.org>
Message-ID: <79a279e1-85a5-865d-e427-1aa61427e100@gmail.com>
Date: Sun, 2 Apr 2017 10:51:32 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K_gzBA2F5mBdlpScpez9H_270v0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Apr 2017 22:51:35 -0000

Many people have been asking whether RFC8136 is compatible with the earlier RFC8135. As far as we can tell, there is indeed no incompatibility; they are complementary mechanisms. We will produce a more detailed analysis soon (see section 7.1 of [I-D.farrel-soon]).

Regards
   Brian


From nobody Mon Apr  3 05:16:21 2017
Return-Path: <acmorton@att.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08E3C12426E; Mon,  3 Apr 2017 05:16:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton <acmorton@att.com>
To: <ops-dir@ietf.org>
Cc: isis-wg@ietf.org, ietf@ietf.org, draft-ietf-isis-mi-bis.all@ietf.org
Subject: Opsdir last call review of draft-ietf-isis-mi-bis-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149122177890.24569.17994646583579565022@ietfa.amsl.com>
Date: Mon, 03 Apr 2017 05:16:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H45IaYEC87MNf7Hyg1Xgr0u8ziQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 12:16:19 -0000

Reviewer: Al Morton
Review result: Ready

This draft is a revision of RFC 6822, to add
the option to use multi-topology support:
"An MI-RTR MAY support [RFC5120] multi-topology within a non-zero
 instance when ITID #0 is supported."
This was previously forbidden in RFC 6822,
but deployment experience revealed a desire
for this ability.

Otherwise, the draft makes one clarification 
(placement of the IID-TLV as the first TLV in
 a PDU to speed recognition) and
deals with Errata of 6822.


From nobody Mon Apr  3 08:26:30 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4383B1200C1 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 08:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Alr38UdD70P5 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 08:26:27 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 76BC11287A7 for <ietf@ietf.org>; Mon,  3 Apr 2017 08:26:27 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v33FQOxk009674 for <ietf@ietf.org>; Mon, 3 Apr 2017 11:26:25 -0400 (EDT)
Date: Mon, 3 Apr 2017 11:26:24 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170403152624.GA11714@gsp.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CBE43UWfNN25iEs60brVHcB3dhU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 15:26:29 -0000

On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
> I don't know when I will be refused entry for not handing out
> passwords or pins.

This is worth noting on an equal basis with the question of
whether travelers will be refused entry or only permitted entry
after considerable delays, interrogation, and abuse.  There is
at this moment no articulated, consistent, and uniform policy
in place specifying:

	- who will be asked for passwords
	- why they'll be asked
	- who will do the asking
	- under what circumstances they'll be asked
	- what the ramifications of refusal are
	- what the ramifications of not remembering them are
	- what the ramifications of agreement are
	- what use will be made of them
	- what use will be made of any data they provide access to
	- if they'll be retained
	- if the data they provide access to will be retained
	- if they'll be shared with other US agencies
	- if they'll be shared with other non-US agencies
	- if computing devices will be confiscated
	- if computing devices will be searched
	- if computing devices will be returned
	- if the contents of computing devices will be copied
	- who will have access to that data
	- what use will be made of that data
	- if that data will be retained
	- if that data will be shared with US agencies
	- if that data will be shared with non-US agencies
	- what auditing controls (if any) exist to prevent mis-use
	- when any retained passwords/data will be destroyed (if ever)
	- etc.

Moreover, the ad hoc policies that are in place are used very
inconsistently -- at the personal whims of those enforcing them --
and are subject to change not only without advance notice,
but without any notice of any kind.

Because of this, asking anyone to come to the US at this time is
equivalent to asking them to incur unknown but possibly very large
privacy and security risks, as well the financial risk of losing
any/all computing devices they bring with them.

---rsk


From nobody Mon Apr  3 08:56:59 2017
Return-Path: <acmorton@att.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C12D12943A; Mon,  3 Apr 2017 08:56:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton <acmorton@att.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-httpbis-encryption-encoding.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Subject: Opsdir last call review of draft-ietf-httpbis-encryption-encoding-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149123501161.30894.11402926232358955663@ietfa.amsl.com>
Date: Mon, 03 Apr 2017 08:56:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4QCjwuuOemz7vB6I2rgKmQgqaYs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 15:56:52 -0000

Reviewer: Al Morton
Review result: Ready

Review of HTTP content encryption encoding:

This draft describes a method to encrypt content which will be stored
on hosts at either end of the transport connection, as opposed to
encryption of the connection itself. Since network operations rarely
involve the content of transactions, the issues introduced by this new
capability appear to be limited to the content provider and user. 



From nobody Mon Apr  3 09:23:22 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4B91129407 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 09:23: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, 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 XcCeLIZM81gp for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 09:23:19 -0700 (PDT)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::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 3253F127A97 for <ietf@ietf.org>; Mon,  3 Apr 2017 09:23:19 -0700 (PDT)
Received: by mail-it0-x242.google.com with SMTP id e75so8668100itd.1 for <ietf@ietf.org>; Mon, 03 Apr 2017 09:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=9HZrJz05NRAh9KAzT//KSY4O1cQWPVPp4rztsW5lLmY=; b=S6o6/GHv3mCcY9pNbD4No7Q4sqioF7ai8jk/l3SICdRIn868324S2OHpwR+rqkvyUY iA4W53V8c1363TURlXm8b5Zw9vGIOGKxBEsu/skFIIA0pkxBxlMDWG+7Un35Zszs1fkv 7TvbqhiCG/nRX3COrl4wVkWGkO5B3Lbxf+CH/8rRjFxhiyIX+iaedX63c7AzMsat5A7T uky2cGCGmOBOj4v0P7Lz5HMQttzU/TAgkWZg9+632pBhth/9wJe5yEVnsAlSCmVGsfHg Kn0uQQzdbCNj15eAqw+0wLTGoQw+ZhBqXB9rm485SPPOEXmTxlMl6rUP2aX8NZLYYbjf o7pw==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=9HZrJz05NRAh9KAzT//KSY4O1cQWPVPp4rztsW5lLmY=; b=BRb+WYSm47Uxg9CKYIQGnCw6VgXBhIZFf6oh8xDtgwmp96yN2PspxizuFMvWK6pj3F Ne35cBEZNnjg/8xTPoqiWx/0nPf50FWMXBKZZh2HYPUEnvZS1VL06f8FDe6ANINMCJn5 fhJflkFQPuY+NJVVQixdPMW99XzwkPdzJJn1yCRMpsF8DFebnehhbn6qFS4ZR3cmFc2l LyL4QmDukD7cczawX3wTWDHQdV6rpzYaRpLa7p/POBYtvzGQKUzH0Km/e0h5gfHp3nzK 7X6FnWxIVQKBCTbY/Ir/GOzcODohElfnl3lQn+YsxtdzHKKXBZEQAkb2XbN0ZKc+GsjR SlZg==
X-Gm-Message-State: AFeK/H3uP1AAemR08ka43sElOMFnMTfcfr8WgXxhQ8R+mUPZrAvBTCzw RtEG13OVYMfyNTek
X-Received: by 10.36.144.132 with SMTP id x126mr10351851itd.35.1491236598442;  Mon, 03 Apr 2017 09:23:18 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id w73sm7845782ioi.16.2017.04.03.09.23.17 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Apr 2017 09:23:17 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
Date: Tue, 4 Apr 2017 04:23:21 +1200
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: <20170403152624.GA11714@gsp.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ztd5cFHpaWHqxjkFbIneT3CaBFM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 16:23:21 -0000

On 04/04/2017 03:26, Rich Kulawiec wrote:
> On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
>> I don't know when I will be refused entry for not handing out
>> passwords or pins.
...
> Moreover, the ad hoc policies that are in place are used very
> inconsistently -- at the personal whims of those enforcing them --
> and are subject to change not only without advance notice,
> but without any notice of any kind.
> 
> Because of this, asking anyone to come to the US at this time is
> equivalent to asking them to incur unknown but possibly very large
> privacy and security risks, as well the financial risk of losing
> any/all computing devices they bring with them.

What is specific to the US in all that? Afaik, customs or immigration
officers have similar rights in many, if not most, countries. And they
use them from time to time, at random or as a result of profiling.

Before you formally enter the country, your rights are limited
in most cases, not only in the US.

    Brian


From nobody Mon Apr  3 09:39:41 2017
Return-Path: <prvs=1266000cac=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338FD129476 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 09:39: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVSqEODoxZ2w for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 09:39:38 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3762129446 for <ietf@ietf.org>; Mon,  3 Apr 2017 09:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491237575; x=1491842375; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=vxEM7qyFW0M9e6spgDhKq5u7K 5FJR19NEkuYSrjFxXw=; b=aV4o7wQC3wQQDzLl0YhUpvLsAK3eYmg6B+OXhUE/R Fd5vSN6/F5n4YUX4nc3bAIm+Uay8HLQilduj2eBqh6ahRE1uhHkNQLVcGoZdY224 V6rSFJzf+5voXrskyGHB+XNio/OsQpNdslpMCakoGlvzIVNDhe2pFrf/BhIyLqJy vw=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=AdZYJ/dVKoqcw0sD2vZfFFKtsqJ9ZQMWmHR0uy3X8tFuuwmYr07tJWrjg+fU RwEz8qivPcFn9SzqYrLLMmAiA9ziz3qPA6E3MsMBvwThfy3ByBykQr4TW Y6aBEDucBBRBuy3oMRamKUug/gQkxRMbWh34ikm6DbZMcFu0R+Ps8o=;
X-MDAV-Processed: mail.consulintel.es, Mon, 03 Apr 2017 18:39:35 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 03 Apr 2017 18:39:35 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005401508.msg for <ietf@ietf.org>; Mon, 03 Apr 2017 18:39:35 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170403:md50005401508::Yg32DqcfdzN0ypXs:0000EWfP
X-Return-Path: prvs=1266000cac=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Mon, 03 Apr 2017 18:39:32 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
In-Reply-To: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jATlqg7PdWRxqpl3TFP3gbHE76c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 16:39:40 -0000

I=E2=80=99m not convinced (despite laws may say it), if computer inspection=
, even =E2=80=9Ctemporal=E2=80=9D confiscation, is being used in EU. At lea=
st I never heard about that, and even less in my own country, though I may =
be missing cases in other EU countries.

Definitively if that happens to me in EU, I will not provide passwords even=
 if I don=E2=80=99t have anything to hide, but just because customer=E2=80=
=99s info confidentiality, signed NDAs, etc. I don=E2=80=99t think that wil=
l bring me to the jail. However, in US, detention is a fact, right?

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Brian E Carpenter <brian.e.ca=
rpenter@gmail.com>
Organizaci=C3=B3n: University of Auckland
Responder a: <brian.e.carpenter@gmail.com>
Fecha: lunes, 3 de abril de 2017, 18:23
Para: <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    On 04/04/2017 03:26, Rich Kulawiec wrote:
    > On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
    >> I don't know when I will be refused entry for not handing out
    >> passwords or pins.
    ...
    > Moreover, the ad hoc policies that are in place are used very
    > inconsistently -- at the personal whims of those enforcing them --
    > and are subject to change not only without advance notice,
    > but without any notice of any kind.
    >=20
    > Because of this, asking anyone to come to the US at this time is
    > equivalent to asking them to incur unknown but possibly very large
    > privacy and security risks, as well the financial risk of losing
    > any/all computing devices they bring with them.
   =20
    What is specific to the US in all that? Afaik, customs or immigration
    officers have similar rights in many, if not most, countries. And they
    use them from time to time, at random or as a result of profiling.
   =20
    Before you formally enter the country, your rights are limited
    in most cases, not only in the US.
   =20
        Brian
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Apr  3 10:30:34 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF331294A2 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 e_1DymGBJ2tc for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:30:30 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F20129469 for <ietf@ietf.org>; Mon,  3 Apr 2017 10:30:29 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v33HUPRu012109; Mon, 3 Apr 2017 18:30:25 +0100
Received: from 950129200 ([176.241.251.3]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v33HUMPJ012064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2017 18:30:24 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <jordi.palet@consulintel.es>, <ietf@ietf.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
In-Reply-To: <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
Subject: RE: IAOC requesting input on (potential) meeting cities
Date: Mon, 3 Apr 2017 18:30:23 +0100
Message-ID: <036e01d2ac9f$fb507fa0$f1f17ee0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFb7UdzNBI3kdRkrGhvD6cdDyzLXQFYwAu9ATYZwfACCIxZsQML5EJ5Ac0VpS2iVeGgoA==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22984.001
X-TM-AS-Result: No--0.258-10.0-31-10
X-imss-scan-details: No--0.258-10.0-31-10
X-TMASE-MatchedRID: cgbqQT5W8hfp3af8JUgdfZWOaq+3+nxyQZXZg2I8JaYfLKImj9wbKcLm p4jPUF8tGxvblWcpseoXIJWO/t2Wjkgvx3HLJkt/hrs6JAEL1u5DGFvBeB2nXKcGzwaLMMjHkhD 59e4L9IBEL14+z1q2lm4zw1WaxVryLCZbmZch5WNm85QoNuKKviPpi9fgNRZlmyiLZetSf8kir3 kOMJmHTBQabjOuIvShC24oEZ6SpSmb4wHqRpnaDmq8Lkk5aVYG4Ix54b1sbVS3dhW6+e5ZEjRyg 7jurDbupk/YYdZOTbbQ93UkZEt7j6qSD1cQCf4fMxPUuKay130eHRwzi++twPR5gLDNdb9LuOZo yiCGGN8YgmnfWgSln5vaf0QvfUyeC8XKjsVbJjU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hQzfp7o8u3jjhd_dPYJ2aejVWp8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 17:30:32 -0000

Sadly it has happened in the UK.

http://www.msnbc.com/all/uk-unlawfully-detained-partner-snowden

Adrian

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of JORDI PALET =
MARTINEZ
> Sent: 03 April 2017 17:40
> To: ietf@ietf.org
> Subject: Re: IAOC requesting input on (potential) meeting cities
>=20
> I=E2=80=99m not convinced (despite laws may say it), if computer =
inspection, even
> =E2=80=9Ctemporal=E2=80=9D confiscation, is being used in EU. At least =
I never heard about that,
> and even less in my own country, though I may be missing cases in =
other EU
> countries.
>=20
> Definitively if that happens to me in EU, I will not provide passwords =
even if I
> don=E2=80=99t have anything to hide, but just because =
customer=E2=80=99s info confidentiality,
> signed NDAs, etc. I don=E2=80=99t think that will bring me to the =
jail. However, in US,
> detention is a fact, right?


From nobody Mon Apr  3 10:32:32 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F33129469 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.397
X-Spam-Level: 
X-Spam-Status: No, score=-5.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, 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 JGf60ih-AoVo for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:32:29 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 8D9081294A2 for <ietf@ietf.org>; Mon,  3 Apr 2017 10:32:28 -0700 (PDT)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx43.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1cv5q1-0004od-9Z for ietf@ietf.org; Mon, 03 Apr 2017 19:32:26 +0200
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1cv5pp-0000Av-00 for ietf@ietf.org; Mon, 03 Apr 2017 13:32:18 -0400
Received: (qmail 22531 invoked from network); 3 Apr 2017 17:32:07 -0000
Received: from unknown (HELO [192.168.1.100]) (Authenticated-user:_huitema@huitema.net@[172.56.42.160]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 3 Apr 2017 17:32:07 -0000
To: ietf@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <ac736542-2394-feb0-3aaa-c75f15162f5f@huitema.net>
Date: Mon, 3 Apr 2017 10:32:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: IAOC requesting input on (potential) meeting cities
X-Originating-IP: 168.144.250.245
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.36)
X-Recommended-Action: accept
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49EdlGitVsfXsrKty9N3esIJTugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXpv7AxO+5FNucWAwhBFOJK/RcOb18WfxGyg6Om6u4YYm9W+X6dknWcMJVco zZrQYuI5hjoyEb9Oq0NWpyO3vrfYy2h1mQR50Wwo5hSyeApVLD3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSB0ktSrwQbrgk6jfwMHIN4qnTFgIfDMShmlQFqCr5hA8xAXSGwpLGc/Znuh3MoIpK0d13OC0Fp +u8Ltg3XM4AI47bRF0J+AL6gRRwFcty0/RGJ+cv73CChOPjKA0/DVd83mzKXD5o/Ia+BqyQ7Q0nt IZ2PVtMHd8bHCmdzlxzVIEgwyGTHIAoNFX+jcW7DGmdE6eBVl9/A6GtGi+mfMSANmgQ9/T0zHbtC pLbhgZ6Z/Qhqxiuap5uKiBpffUsHYsfmrbtbs8GJuRKR6hnrta1usy6F/SOWlhnS7qkS/mOkSgD5 8bDUIriOSOQTK7vaz2jBsjp0rjSY76LAIHA6cW4Oa0X1c90QyXfvSiR99EaOACq0wyQPgYbWCRpe waGWkMJTxdwDV/LdQk4Dnvnv/o4ZpIN8Tfe43vaXKX/yihCEqxIlRZaHuAWSnHeK3PdSA6Q+2n/k rhIYlNMbfS0wdTtG+6KM/oHosNdKX7z8UU/FfpPcu6wTHpnlfUs9BUPj1rZ3
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kf2ToQtJwmOy9CLLDHBuzJl3RFs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 17:32:31 -0000

On 4/3/2017 9:39 AM, JORDI PALET MARTINEZ wrote:
> I=E2=80=99m not convinced (despite laws may say it), if computer inspec=
tion, even =E2=80=9Ctemporal=E2=80=9D confiscation, is being used in EU. =
At least I never heard about that, and even less in my own country, thoug=
h I may be missing cases in other EU countries.
You are indeed missing something.

Here is one pretty famous case, happened in Heathrow: Greenwald's
partner detained, thumb drives confiscated.
http://www.thedrum.com/news/2013/08/19/snowden-documents-seized-heathrow-=
intimidation-says-greenwald-his-partner-detained

Here is a clip about Canada's refusal to disclose laptop search policy:
http://boingboing.net/2010/02/09/canadian-customs-ref.html

Article 60 of French custom code authorizes inspection of anything you
carry, can be interpreted as authorizing search of laptops or cell phones=
:
https://www.legifrance.gouv.fr/affichCode.do;jsessionid=3DAA678D3E2AC8734=
93D4025F33776856A.tpdila20v_2?idSectionTA=3DLEGISCTA000006138841&cidTexte=
=3DLEGITEXT000006071570&dateTexte=3D20130315

Various European countries, including the UK and France, have passed
inquisitive snooping laws. Maybe they are less visible than what happens
in the US, but I would not hold my breath...

-- Christian Huitema







>
> Definitively if that happens to me in EU, I will not provide passwords =
even if I don=E2=80=99t have anything to hide, but just because customer=E2=
=80=99s info confidentiality, signed NDAs, etc. I don=E2=80=99t think tha=
t will bring me to the jail. However, in US, detention is a fact, right?
>
> Regards,
> Jordi
> =20
>



From nobody Mon Apr  3 10:51:14 2017
Return-Path: <prvs=1266000cac=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 385561294B4 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4AuEc8SzNsV for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 10:51:11 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC9B01294E7 for <ietf@ietf.org>; Mon,  3 Apr 2017 10:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491241863; x=1491846663; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=b0JIUH5yAJUElU1CVgtOm3Hoy gAAHdIT1Cwsk08ntVE=; b=qkT8H+SLpIf32HdpXKvKtJtjfc/naj97OstmugvWl rhYipyVbDRgYZ3NAS2+WhjJM6+N0KXgBAfl99YxkoRe/LCyNmLiRlosBIIt92Slg WUk7S3ARr8mFLWCwoA6ShSGw6VfifvMKCeXNuFJ75tjL0gevCqVjYZydr05sVSC3 cg=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=YkmoJ7dtippy6ClqJqQgXXTl6zQxPY2usl02w8t4a3IoHk3IjyGQ8JVO7tJ9 /WvndLAqAXgQhysTGNdciaOl+zLRQb49OBkIOMlcRGoBKFdXln/WkhPf2 B9vU1yvk9QYB3tYMhpgGdOuPIA0oVwJDrkQtC6kRxM549kbpRDfndE=;
X-MDAV-Processed: mail.consulintel.es, Mon, 03 Apr 2017 19:51:03 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 03 Apr 2017 19:51:03 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005401564.msg for <ietf@ietf.org>; Mon, 03 Apr 2017 19:51:02 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170403:md50005401564::RUOpJqSAbzn5iUtS:00004jkC
X-Return-Path: prvs=1266000cac=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Mon, 03 Apr 2017 19:50:58 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <B223FC55-A82E-4F3E-A02E-92061A04FD66@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <ac736542-2394-feb0-3aaa-c75f15162f5f@huitema.net>
In-Reply-To: <ac736542-2394-feb0-3aaa-c75f15162f5f@huitema.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nNO894hJRsAeaidYrHsfDwNvFk0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 17:51:13 -0000

I think the =E2=80=9Cborder=E2=80=9D line between what is being done in EU =
and US is that in EU this is only done under a terrorism classification ?

I can ask about this to a Spanish State Lawyer that I will be able to talk =
at the end of the week =E2=80=A6

I knew about the UK case, but I no longer consider UK part of the EU, never=
 has been =E2=80=9Ctotally=E2=80=9D, and clearly it should be considered al=
so when we plan new meetings.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Christian Huitema <huitema@hu=
itema.net>
Responder a: <huitema@huitema.net>
Fecha: lunes, 3 de abril de 2017, 19:32
Para: <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

   =20
   =20
    On 4/3/2017 9:39 AM, JORDI PALET MARTINEZ wrote:
    > I=E2=80=99m not convinced (despite laws may say it), if computer insp=
ection, even =E2=80=9Ctemporal=E2=80=9D confiscation, is being used in EU. =
At least I never heard about that, and even less in my own country, though =
I may be missing cases in other EU countries.
    You are indeed missing something.
   =20
    Here is one pretty famous case, happened in Heathrow: Greenwald's
    partner detained, thumb drives confiscated.
    http://www.thedrum.com/news/2013/08/19/snowden-documents-seized-heathro=
w-intimidation-says-greenwald-his-partner-detained
   =20
    Here is a clip about Canada's refusal to disclose laptop search policy:
    http://boingboing.net/2010/02/09/canadian-customs-ref.html
   =20
    Article 60 of French custom code authorizes inspection of anything you
    carry, can be interpreted as authorizing search of laptops or cell phon=
es:
    https://www.legifrance.gouv.fr/affichCode.do;jsessionid=3DAA678D3E2AC87=
3493D4025F33776856A.tpdila20v_2?idSectionTA=3DLEGISCTA000006138841&cidTexte=
=3DLEGITEXT000006071570&dateTexte=3D20130315
   =20
    Various European countries, including the UK and France, have passed
    inquisitive snooping laws. Maybe they are less visible than what happen=
s
    in the US, but I would not hold my breath...
   =20
    -- Christian Huitema
   =20
   =20
   =20
   =20
   =20
   =20
   =20
    >
    > Definitively if that happens to me in EU, I will not provide password=
s even if I don=E2=80=99t have anything to hide, but just because customer=
=E2=80=99s info confidentiality, signed NDAs, etc. I don=E2=80=99t think th=
at will bring me to the jail. However, in US, detention is a fact, right?
    >
    > Regards,
    > Jordi
    > =20
    >
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Apr  3 11:39:12 2017
Return-Path: <sbanks@encrypted.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77E5112962A for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 11:39:07 -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 iCqvOW4kWIMm for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 11:39:03 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17894129622 for <ietf@ietf.org>; Mon,  3 Apr 2017 11:39:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 406AB80385; Mon,  3 Apr 2017 14:39:02 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2-6bJvOJ1Qsx; Mon,  3 Apr 2017 14:39:02 -0400 (EDT)
Received: from divinaair.netscout.com (50-195-106-33-static.hfc.comcastbusiness.net [50.195.106.33]) by aws.hosed.org (Postfix) with ESMTPSA id 00ABD80384; Mon,  3 Apr 2017 14:39:01 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Sarah B <sbanks@encrypted.net>
In-Reply-To: <20170403152624.GA11714@gsp.org>
Date: Mon, 3 Apr 2017 11:39:01 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <16F26591-DB89-4AE8-96C5-4944301C0C6D@encrypted.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1WIK0tgJ76NvbEcThXGbxA_UUsQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 18:39:07 -0000

FWIW, i think all of this has been true, well before Trump took office, =
and made these changes to the current travel policies...=20

/S

> On Apr 3, 2017, at 8:26 AM, Rich Kulawiec <rsk@gsp.org> wrote:
>=20
> On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
>> I don't know when I will be refused entry for not handing out
>> passwords or pins.
>=20
> This is worth noting on an equal basis with the question of
> whether travelers will be refused entry or only permitted entry
> after considerable delays, interrogation, and abuse.  There is
> at this moment no articulated, consistent, and uniform policy
> in place specifying:
>=20
> 	- who will be asked for passwords
> 	- why they'll be asked
> 	- who will do the asking
> 	- under what circumstances they'll be asked
> 	- what the ramifications of refusal are
> 	- what the ramifications of not remembering them are
> 	- what the ramifications of agreement are
> 	- what use will be made of them
> 	- what use will be made of any data they provide access to
> 	- if they'll be retained
> 	- if the data they provide access to will be retained
> 	- if they'll be shared with other US agencies
> 	- if they'll be shared with other non-US agencies
> 	- if computing devices will be confiscated
> 	- if computing devices will be searched
> 	- if computing devices will be returned
> 	- if the contents of computing devices will be copied
> 	- who will have access to that data
> 	- what use will be made of that data
> 	- if that data will be retained
> 	- if that data will be shared with US agencies
> 	- if that data will be shared with non-US agencies
> 	- what auditing controls (if any) exist to prevent mis-use
> 	- when any retained passwords/data will be destroyed (if ever)
> 	- etc.
>=20
> Moreover, the ad hoc policies that are in place are used very
> inconsistently -- at the personal whims of those enforcing them --
> and are subject to change not only without advance notice,
> but without any notice of any kind.
>=20
> Because of this, asking anyone to come to the US at this time is
> equivalent to asking them to incur unknown but possibly very large
> privacy and security risks, as well the financial risk of losing
> any/all computing devices they bring with them.
>=20
> ---rsk


From nobody Mon Apr  3 11:44:30 2017
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EECC1294E6 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 11:44:28 -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 Gb2kib3l02Vn for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 11:44:27 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::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 06E431294D4 for <ietf@ietf.org>; Mon,  3 Apr 2017 11:44:27 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id w11so180749471wrc.3 for <ietf@ietf.org>; Mon, 03 Apr 2017 11:44:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=izOrvwIx3eXwRl32KkGj9OH3Ah51GPGHUCW2npfQGKg=; b=iYa6aiLzAlQIlQfBs6OLxpvA6fTWTn73G1UBxdfxgazPH2SP1IEuaqpSO3tT0p9NGI gDCULRkVGfvY+1+bYv0nV0Inh3iV75zuzKim1EvOkroUSBFydpQU+o1bLINI6qr/JEzG T/6t9MFEp7bue+1VU1MQZ1s9nFKJ/BDpLjhiaDG89wvYViXQellFCDlqtqDlaJPHW859 V4d04TUc9r45ay1UF/TeeqJAM3HcAuCCvBtOOzFuPe9+RFyE/R6T41XtDx6FqmwQC7VQ jMCnM96lZ1RaaIh5ykRWrpx0/q00iBk92+lwlMN7KDhDu5MihNtEKVn+V92Sa6qTcD9j h2DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=izOrvwIx3eXwRl32KkGj9OH3Ah51GPGHUCW2npfQGKg=; b=eCIpVNXr7OqVZZVYMwCs4CYpvHCV/dIPICfnex5eOnk3XM6/XxmWSusYgxYS9R7X3Z s33CCLGy/FF5wuNkz0bJoYmPM8nkW/WHkK19B2xfWe665mqQMgv73yem1+g66DLkOiIb cKMvT6tlA396qp19BSNt2MJFZFLhugNGvJJBIqF/YfozdyVP4lHLondg78V6v9hE0SCC Ot+V6dbDv7+IzfFAsrZd2z7dBKeUyqqjwMqNQodC2kWD8vZEz8Zwkpei5to+JR222258 DYjWzdlsLofcaafom0LzUmDPJwhuRJ3fTj6kEMkljv+4LxzJ+dXpInkr//EuUfcoEL8D 7rLg==
X-Gm-Message-State: AFeK/H2oLP+uGoEtkVFh1XzbmVu5jPoOsKzZQf/cfw39jHoS3jp6X5TSb+3Z1yQr3X5K9OqzLa6vQf28y7MHOQ==
X-Received: by 10.223.162.198 with SMTP id t6mr17689706wra.155.1491245065540;  Mon, 03 Apr 2017 11:44:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.169.228 with HTTP; Mon, 3 Apr 2017 11:44:24 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 3 Apr 2017 13:44:24 -0500
Message-ID: <CAC8QAccNXCQivK7J7r8k0ZAOCmFPoi42orEDTrFpo1vbjTvmPQ@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f403045e9cf6679b0a054c478c03
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZFTgyE8y-j24fou-V5dTyeHo8XM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 18:44:29 -0000

--f403045e9cf6679b0a054c478c03
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 3, 2017 at 11:23 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 04/04/2017 03:26, Rich Kulawiec wrote:
> > On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
> >> I don't know when I will be refused entry for not handing out
> >> passwords or pins.
> ...
> > Moreover, the ad hoc policies that are in place are used very
> > inconsistently -- at the personal whims of those enforcing them --
> > and are subject to change not only without advance notice,
> > but without any notice of any kind.
> >
> > Because of this, asking anyone to come to the US at this time is
> > equivalent to asking them to incur unknown but possibly very large
> > privacy and security risks, as well the financial risk of losing
> > any/all computing devices they bring with them.
>
> What is specific to the US in all that? Afaik, customs or immigration
> officers have similar rights in many, if not most, countries. And they
> use them from time to time, at random or as a result of profiling.
>
> Before you formally enter the country, your rights are limited
> in most cases, not only in the US.
>

+1

Behcet

>
>     Brian
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Apr 3, 2017 at 11:23 AM, Brian E Carpenter <span dir=3D"ltr">&l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.=
carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rg=
b(204,204,204);border-left-width:1px;border-left-style:solid"><span>On 04/0=
4/2017 03:26, Rich Kulawiec wrote:<br>
&gt; On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:<br>
&gt;&gt; I don&#39;t know when I will be refused entry for not handing out<=
br>
&gt;&gt; passwords or pins.<br>
</span>...<br>
<span>&gt; Moreover, the ad hoc policies that are in place are used very<br=
>
&gt; inconsistently -- at the personal whims of those enforcing them --<br>
&gt; and are subject to change not only without advance notice,<br>
&gt; but without any notice of any kind.<br>
&gt;<br>
&gt; Because of this, asking anyone to come to the US at this time is<br>
&gt; equivalent to asking them to incur unknown but possibly very large<br>
&gt; privacy and security risks, as well the financial risk of losing<br>
&gt; any/all computing devices they bring with them.<br>
<br>
</span>What is specific to the US in all that? Afaik, customs or immigratio=
n<br>
officers have similar rights in many, if not most, countries. And they<br>
use them from time to time, at random or as a result of profiling.<br>
<br>
Before you formally enter the country, your rights are limited<br>
in most cases, not only in the US.<br></blockquote><div><br></div><div>+1</=
div><div><br></div><div>Behcet=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(2=
04,204,204);border-left-width:1px;border-left-style:solid">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
<br>
</font></span></blockquote></div><br></div></div>

--f403045e9cf6679b0a054c478c03--


From nobody Mon Apr  3 12:13:53 2017
Return-Path: <ldaigle@thinkingcat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F184C127449 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 12:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Level: 
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, T_DKIM_INVALID=0.01, URIBL_GREY=0.424] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=thinkingcat.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 BjlAzLAe5rZz for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 12:13:49 -0700 (PDT)
Received: from homiemail-a113.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BB54129503 for <ietf@ietf.org>; Mon,  3 Apr 2017 12:13:49 -0700 (PDT)
Received: from homiemail-a113.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTP id 0D7D63000272A; Mon,  3 Apr 2017 12:13:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=V7rA/mi6tUv+hm ca9KXDXYtzXhY=; b=XGOuzdbHpyBjDU6N9kx0CevXgKP3jD7RYg09IGasCvanF8 MQMOD65xMSmdE6khbLnbtaNMdxkVLlOY/kBOY3Pu6/AdRDK+pCiHvPxXFsjARj8w mlmqN+FNH5FRiFsC5l/GoBLwfd92WKqbJVvGqQ/T0+XMoRaND4sC/jmZLQIrY=
Received: from [192.168.1.5] (pool-173-72-147-193.clppva.fios.verizon.net [173.72.147.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTPSA id 79FC930002727; Mon,  3 Apr 2017 12:13:48 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Ross Finlayson" <finlayson@live555.com>
Cc: "Randy Bush" <randy@psg.com>, IETF <ietf@ietf.org>
Subject: And, request for feedback on US-based meetings Re: IAOC requesting input on (potential) meeting cities
Date: Mon, 03 Apr 2017 15:13:47 -0400
Message-ID: <C0AA0789-C7DF-4F15-B600-9A8B97A8AED9@thinkingcat.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0691EE12-D07D-4907-ADE3-2D909FE46727_="
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IuRXv8oX7POpYnu2Y0FJye0UcHw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 19:13:52 -0000

--=_MailMate_0691EE12-D07D-4907-ADE3-2D909FE46727_=
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable


Yes, the OP (that would be me) realized 48h too late that it would have=20
been awesome to have set the reply-to to the venue-selection address. =20
Sigh.

I also should have noted in the message that venue-selection is for=20
dropping off input for review by meeting planners (though the archive is=20
publicly visible).  The list settings are selected to discourage=20
discussion threads.  To the extent people need to debate the challenges=20
and realities of crossing borders (e.g., the UK-has-required-decryption=20
thread), the IETF discuss list is the better place for it.

And, as Spencer noted, the IAOC has asked for more structured input on=20
the specific questions related to IETF 102 =E2=80=94 in a structured form=
 to=20
1/ give people the option of reasonable anonymity and 2/ give the IAOC=20
some possibility of being able to digest the input from a lot of=20
responses (over 150 so far).

See original message, below.

Forwarded message:

> From: IAOC Chair <iaoc-chair@ietf.org>
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: iaoc@ietf.org
> Subject: Request for feedback on US-based meetings
> Date: Fri, 31 Mar 2017 08:25:27 -0700
>
> As the realities of global travel continue to change, the IAOC is=20
> endeavouring to monitor the situations that will impact all of our=20
> participants. We met this week in the United States, a country that=20
> has made moves to change its visa and visitor requirements abruptly=20
> and significantly in recent weeks. Prior to the meeting, we received=20
> input from people who would be unable to attend the meeting in=20
> Chicago. We are interested in hearing whether or what unusual or=20
> additional challenges people faced as they prepared their travel=20
> and/or crossed the border to come to the Chicago meeting.
>
> To that end, we have created a form for providing input. Please share=20
> your thoughts here:
>
> https://www.surveymonkey.com/r/WMNH9PS
>
> Your contribution will be kept confidential within the IAOC and its=20
> Meetings Committee. We are only asking you to identify yourself if you=20
> are willing to be contacted for follow up.
>
> Context:
>
> We have more meetings booked in the US in the upcoming years, and are=20
> reassessing these. We continue to monitor the situation for people=20
> traveling to this country (as we do for travel to other IETF meeting=20
> host countries), and will make updates as and when necessary. We are=20
> also conscious, however, that travel requirements may make it=20
> difficult for US residents to travel to a non-US IETF meeting with a=20
> reasonable expectation of a smooth return home. They may be only able=20
> to attend US meetings.
>
> In all cases, our aim is to provide a meeting venue that will support=20
> the work of the IETF =E2=80=94 including accessibility for participatio=
n.=20
> With the unpredictability of US immigration laws, it is difficult to=20
> assess whether holding IETF 102 in San Francisco (as currently=20
> scheduled) will yield the level of accessibility the IETF expects and=20
> plans for its meetings. However, if we are to secure a suitable=20
> alternative location, we need to decide to do so in the very near=20
> term.
>
> Your input in the form would be most helpful.


Leslie.

--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------

On 31 Mar 2017, at 16:32, Ross Finlayson wrote:

>> On Mar 31, 2017, at 8:55 AM, Randy Bush <randy@psg.com> wrote:
>>
>>>> Please send input to venue-selection@ietf.org.
>>
>> so, i am curious.  do people
>>  o think their imput is more important than that of we small people,
>>  o can't read or follow instructions,
>>  o or some other thing i do not understand?
>
> Probably a combination of (1) and (2) - but it=E2=80=99s a pity that th=
e OP=20
> (original poster) didn=E2=80=99t set the =E2=80=9CReply-To:=E2=80=9D he=
ader in their=20
> email.  That would have been a perfect use for it.
>
> 	Ross.

--=_MailMate_0691EE12-D07D-4907-ADE3-2D909FE46727_=
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 http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Yes, the OP (that would be me) realized 48h too late that=
 it would have been awesome to have set the reply-to to the venue-selecti=
on address.  Sigh.</p>

<p dir=3D"auto">I also should have noted in the message that venue-select=
ion is for dropping off input for review by meeting planners (though the =
archive is publicly visible).  The list settings are selected to discoura=
ge discussion threads.  To the extent people need to debate the challenge=
s and realities of crossing borders (e.g., the UK-has-required-decryption=
 thread), the IETF discuss list is the better place for it.</p>

<p dir=3D"auto">And, as Spencer noted, the IAOC has asked for more struct=
ured input on the specific questions related to IETF 102 =E2=80=94 in a s=
tructured form to 1/ give people the option of reasonable anonymity and 2=
/ give the IAOC some possibility of being able to digest the input from a=
 lot of responses (over 150 so far).   </p>

<p dir=3D"auto">See original message, below.</p>

<p dir=3D"auto">Forwarded message:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">F=
rom: IAOC Chair &lt;iaoc-chair@ietf.org&gt;<br>
To: IETF Announcement List &lt;ietf-announce@ietf.org&gt;<br>
Cc: iaoc@ietf.org<br>
Subject: Request for feedback on US-based meetings<br>
Date: Fri, 31 Mar 2017 08:25:27 -0700<br>
<br>
As the realities of global travel continue to change, the IAOC is endeavo=
uring to monitor the situations that will impact all of our participants.=
 We met this week in the United States, a country that has made moves to =
change its visa and visitor requirements abruptly and significantly in re=
cent weeks. Prior to the meeting, we received input from people who would=
 be unable to attend the meeting in Chicago. We are interested in hearing=
 whether or what unusual or additional challenges people faced as they pr=
epared their travel and/or crossed the border to come to the Chicago meet=
ing.<br>
<br>
To that end, we have created a form for providing input. Please share you=
r thoughts here:<br>
<br>
<a href=3D"https://www.surveymonkey.com/r/WMNH9PS" style=3D"color:#777">h=
ttps://www.surveymonkey.com/r/WMNH9PS</a><br>
<br>
Your contribution will be kept confidential within the IAOC and its Meeti=
ngs Committee. We are only asking you to identify yourself if you are wil=
ling to be contacted for follow up.<br>
<br>
Context:<br>
<br>
We have more meetings booked in the US in the upcoming years, and are rea=
ssessing these. We continue to monitor the situation for people traveling=
 to this country (as we do for travel to other IETF meeting host countrie=
s), and will make updates as and when necessary. We are also conscious, h=
owever, that travel requirements may make it difficult for US residents t=
o travel to a non-US IETF meeting with a reasonable expectation of a smoo=
th return home. They may be only able to attend US meetings.<br>
<br>
In all cases, our aim is to provide a meeting venue that will support the=
 work of the IETF =E2=80=94 including accessibility for participation. Wi=
th the unpredictability of US immigration laws, it is difficult to assess=
 whether holding IETF 102 in San Francisco (as currently scheduled) will =
yield the level of accessibility the IETF expects and plans for its meeti=
ngs. However, if we are to secure a suitable alternative location, we nee=
d to decide to do so in the very near term.<br>
<br>
Your input in the form would be most helpful.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Leslie.</p>

<p dir=3D"auto">-- </p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">Leslie Daigle<br>
Principal, ThinkingCat Enterprises LLC</p>

<h2 style=3D"font-size:1.2em"><a href=3D"mailto:ldaigle@thinkingcat.com" =
style=3D"color:#3983C4">ldaigle@thinkingcat.com</a></h2>

<p dir=3D"auto">On 31 Mar 2017, at 16:32, Ross Finlayson wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">On Mar 31, 2017, at 8:55 AM,=
 Randy Bush &lt;randy@psg.com&gt; wrote:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><blockquote style=3D"border=
-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; borde=
r-left-color:#BBB"><p dir=3D"auto">Please send input to venue-selection@i=
etf.org.</p>
</blockquote></blockquote><p dir=3D"auto">so, i am curious.  do people<br=
>
 o think their imput is more important than that of we small people,<br>
 o can't read or follow instructions,<br>
 o or some other thing i do not understand?</p>
</blockquote><p dir=3D"auto">Probably a combination of (1) and (2) - but =
it=E2=80=99s a pity that the OP (original poster) didn=E2=80=99t set the =
=E2=80=9CReply-To:=E2=80=9D header in their email.  That would have been =
a perfect use for it.<br>
<br>
	Ross.</p>
</blockquote></div>
<div style=3D"white-space:normal">
</div>
</div>
</body>
</html>

--=_MailMate_0691EE12-D07D-4907-ADE3-2D909FE46727_=--


From nobody Mon Apr  3 14:51:39 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31523129329 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 14:51:38 -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 J-TwCYHPYWvI for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 14:51:35 -0700 (PDT)
Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (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 AB97F128CD5 for <ietf@ietf.org>; Mon,  3 Apr 2017 14:51:35 -0700 (PDT)
Received: by mail-it0-x243.google.com with SMTP id w11so9537390itb.0 for <ietf@ietf.org>; Mon, 03 Apr 2017 14:51:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Zz/WOdBA7DgVkukamAtO+kvT5w3g7AvCjzxoUAlQgZE=; b=JICd3mPwY31mD+0jPzN+Oz890fYusmNkLr4BrW4jNykxIz2pxyoNXfl2E+FPPT8I5i 8ZnK4yAkM90ZgddXHWDOxDMyGK47b++XweVXzHmoq/m5/ujnya0HpHPPX3o11B0v6xVM ZhJfVHm0ynnZ94ReDqRZH2PdgnyMHNQaK7h7YpuKEbqxF40J5maUmpcD7DAp6uep9LEV EjgD+rwNQXklWz6YFQ+YGyZGuTALmzsh86rdiZRE+eum/SGkE+qI5lVMSdJjCzT4TELD WNI6z8eIZgIddF2dLXafp/PMtR0vAgKEPJl9jRWo8cecJwOMGZdciRt2mxlPwxppR62N xFMw==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Zz/WOdBA7DgVkukamAtO+kvT5w3g7AvCjzxoUAlQgZE=; b=Djv41xtpE8+AVn4SuFRWhaMnX7HnGAf51/NVZyUi8dzVlwAN7yBjHlL00wrRRJGmv6 EbpmOQ3WBP5wMLEAEsvGRizszvcdEdIkNTvLtowStcY1JYkb9EKyUVH0u3GRn/7mF/NT M2/C4QAWu0dxwWPDTdRDKmKFcwiwUzTzZK/5XB9CJUMfa/O6G5yxGw5viz13NI/v1RAr X4ECNY2iCq1X4D2/UOSiy22HE+kqetIhkxH3kVw7dB3w+5EgrQiMtJaxPQuIuoZ7OclG EGUwR5J4cksh4bp20E3WOFI/TODqriQbdde9LZivKDinDCZ4JYlF8fpdWYz5q6T3Js6l 2A3g==
X-Gm-Message-State: AFeK/H23mN2BXZLSe0AXF/80lm9bxP5OnPbgVv63xJYUz4lAXZ4Tlo6H GU8RXn3/o3lMyCAT
X-Received: by 10.36.237.7 with SMTP id r7mr12957781ith.0.1491256294911; Mon, 03 Apr 2017 14:51:34 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id h11sm8189334ioa.43.2017.04.03.14.51.34 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Apr 2017 14:51:34 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <ac736542-2394-feb0-3aaa-c75f15162f5f@huitema.net> <B223FC55-A82E-4F3E-A02E-92061A04FD66@consulintel.es>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8db4104e-6ce4-9748-a040-7b52dae7196f@gmail.com>
Date: Tue, 4 Apr 2017 09:51:32 +1200
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: <B223FC55-A82E-4F3E-A02E-92061A04FD66@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZNL65XSh8C5cEQv1Y3d9eHu8NN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 21:51:38 -0000

Jordi,

It won't happen when travelling between two "Schengen" countries, I suppo=
se.
But when you enter or leave the Schengen zone, you go through an immigrat=
ion
checkpoint.

That's a more important distinction than EU/non-EU in this particular cas=
e.

    Brian
On 04/04/2017 05:50, JORDI PALET MARTINEZ wrote:
> I think the =E2=80=9Cborder=E2=80=9D line between what is being done in=
 EU and US is that in EU this is only done under a terrorism classificati=
on ?
>=20
> I can ask about this to a Spanish State Lawyer that I will be able to t=
alk at the end of the week =E2=80=A6
>=20
> I knew about the UK case, but I no longer consider UK part of the EU, n=
ever has been =E2=80=9Ctotally=E2=80=9D, and clearly it should be conside=
red also when we plan new meetings.
>=20
> Regards,
> Jordi
> =20
>=20
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Christian Huitema <huitem=
a@huitema.net>
> Responder a: <huitema@huitema.net>
> Fecha: lunes, 3 de abril de 2017, 19:32
> Para: <ietf@ietf.org>
> Asunto: Re: IAOC requesting input on (potential) meeting cities
>=20
>    =20
>    =20
>     On 4/3/2017 9:39 AM, JORDI PALET MARTINEZ wrote:
>     > I=E2=80=99m not convinced (despite laws may say it), if computer =
inspection, even =E2=80=9Ctemporal=E2=80=9D confiscation, is being used i=
n EU. At least I never heard about that, and even less in my own country,=
 though I may be missing cases in other EU countries.
>     You are indeed missing something.
>    =20
>     Here is one pretty famous case, happened in Heathrow: Greenwald's
>     partner detained, thumb drives confiscated.
>     http://www.thedrum.com/news/2013/08/19/snowden-documents-seized-hea=
throw-intimidation-says-greenwald-his-partner-detained
>    =20
>     Here is a clip about Canada's refusal to disclose laptop search pol=
icy:
>     http://boingboing.net/2010/02/09/canadian-customs-ref.html
>    =20
>     Article 60 of French custom code authorizes inspection of anything =
you
>     carry, can be interpreted as authorizing search of laptops or cell =
phones:
>     https://www.legifrance.gouv.fr/affichCode.do;jsessionid=3DAA678D3E2=
AC873493D4025F33776856A.tpdila20v_2?idSectionTA=3DLEGISCTA000006138841&ci=
dTexte=3DLEGITEXT000006071570&dateTexte=3D20130315
>    =20
>     Various European countries, including the UK and France, have passe=
d
>     inquisitive snooping laws. Maybe they are less visible than what ha=
ppens
>     in the US, but I would not hold my breath...
>    =20
>     -- Christian Huitema
>    =20
>    =20
>    =20
>    =20
>    =20
>    =20
>    =20
>     >
>     > Definitively if that happens to me in EU, I will not provide pass=
words even if I don=E2=80=99t have anything to hide, but just because cus=
tomer=E2=80=99s info confidentiality, signed NDAs, etc. I don=E2=80=99t t=
hink that will bring me to the jail. However, in US, detention is a fact,=
 right?
>     >
>     > Regards,
>     > Jordi
>     > =20
>     >
>    =20
>    =20
>    =20
>    =20
>=20
>=20
>=20
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>=20
> This electronic message contains information which may be privileged or=
 confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that=
 any disclosure, copying, distribution or use of the contents of this inf=
ormation, including attached files, is prohibited.
>=20
>=20
>=20
>=20


From nobody Mon Apr  3 15:11:26 2017
Return-Path: <prvs=1266000cac=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4EA7129461 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 15:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIVtFu2C89p4 for <ietf@ietfa.amsl.com>; Mon,  3 Apr 2017 15:11:21 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE1B11289B0 for <ietf@ietf.org>; Mon,  3 Apr 2017 15:11:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491257478; x=1491862278; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=arHekjWlxu3SQgPoYUhwLQL6B 6VVf0kyVGKKi8sCTNA=; b=IVV8Tsvtuq/EaX1cDfeInQoc87BzSDIEvpY259CQs FJ/ENkM7+IFzQf1RAsw0lPJkabwdFW86Rp12yGl/uG3QltanaE7b/5EVJdCxD5bF o8rILh/QZjnPIQyETMRuF6LP3pRLJsRNtUlbmaILz4dnrgMcIX9tRDC0v/p55CSg vg=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=be5fURSpqibtf9WCgCouq7lQrM7R95ftGg543E7TU8shp4yIG7SeGyf8Z6ok FT6MqjhXw2lCUh1iShFNkIHJWHCWVcxiGi/1UqKPDSU4P7iid1zdC9dsC K9vMol2uiV4jGPUdTiTkJY0E+/hzGMUu5oXMwCl7N+b7Do9R+wG3/U=;
X-MDAV-Processed: mail.consulintel.es, Tue, 04 Apr 2017 00:11:18 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 04 Apr 2017 00:11:17 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005401731.msg for <ietf@ietf.org>; Tue, 04 Apr 2017 00:11:16 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170403:md50005401731::I+2MdLkCgJGaoWNP:00002s9c
X-Return-Path: prvs=1266000cac=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Tue, 04 Apr 2017 00:11:15 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <A9B4DE68-C098-42A3-B135-AE93BDF12087@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <ac736542-2394-feb0-3aaa-c75f15162f5f@huitema.net> <B223FC55-A82E-4F3E-A02E-92061A04FD66@consulintel.es> <8db4104e-6ce4-9748-a040-7b52dae7196f@gmail.com>
In-Reply-To: <8db4104e-6ce4-9748-a040-7b52dae7196f@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kk5qVHgJaKHhXLmBgPenTDSVo6Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 22:11:24 -0000

Hi Brian,

I was considering the EU =E2=80=9Cborders=E2=80=9D to outside-EU, not inter=
nal among EU countries.

When I come back from US, Latin America, Africa, AP, to the EU, I feel much=
 safer than when I go to US.

When I travel to *ANY* region or country in the world, except US, I feel ve=
ry safe.

And is not just how I feel, but how I see people coming to EU feels relativ=
ely safe (of course unless they aren=E2=80=99t trying to bypass immigration=
 laws).

I feel each time less and less safe going to US and I see people from other=
 regions outside EU, even people from Canada, feeling unsafe as well.

It is a matter of facts and stats, despite whatever laws say, despite what =
are the human rights, privacy rights, etc., definitively, US reputation for=
 any non-US citizen is going darker and darker.

I need to see if I still feel safe when traveling to UK next time =E2=80=A6=
 after Brexit gets completed.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Brian E Carpenter <brian.e.ca=
rpenter@gmail.com>
Organizaci=C3=B3n: University of Auckland
Responder a: <brian.e.carpenter@gmail.com>
Fecha: lunes, 3 de abril de 2017, 23:51
Para: <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    Jordi,
   =20
    It won't happen when travelling between two "Schengen" countries, I sup=
pose.
    But when you enter or leave the Schengen zone, you go through an immigr=
ation
    checkpoint.
   =20
    That's a more important distinction than EU/non-EU in this particular c=
ase.
   =20
        Brian
    On 04/04/2017 05:50, JORDI PALET MARTINEZ wrote:
    > I think the =E2=80=9Cborder=E2=80=9D line between what is being done =
in EU and US is that in EU this is only done under a terrorism classificati=
on ?
    >=20
    > I can ask about this to a Spanish State Lawyer that I will be able to=
 talk at the end of the week =E2=80=A6
    >=20
    > I knew about the UK case, but I no longer consider UK part of the EU,=
 never has been =E2=80=9Ctotally=E2=80=9D, and clearly it should be conside=
red also when we plan new meetings.
    >=20
    > Regards,
    > Jordi
    > =20
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Christian Huitema <huit=
ema@huitema.net>
    > Responder a: <huitema@huitema.net>
    > Fecha: lunes, 3 de abril de 2017, 19:32
    > Para: <ietf@ietf.org>
    > Asunto: Re: IAOC requesting input on (potential) meeting cities
    >=20
    >    =20
    >    =20
    >     On 4/3/2017 9:39 AM, JORDI PALET MARTINEZ wrote:
    >     > I=E2=80=99m not convinced (despite laws may say it), if compute=
r inspection, even =E2=80=9Ctemporal=E2=80=9D confiscation, is being used i=
n EU. At least I never heard about that, and even less in my own country, t=
hough I may be missing cases in other EU countries.
    >     You are indeed missing something.
    >    =20
    >     Here is one pretty famous case, happened in Heathrow: Greenwald's
    >     partner detained, thumb drives confiscated.
    >     http://www.thedrum.com/news/2013/08/19/snowden-documents-seized-h=
eathrow-intimidation-says-greenwald-his-partner-detained
    >    =20
    >     Here is a clip about Canada's refusal to disclose laptop search p=
olicy:
    >     http://boingboing.net/2010/02/09/canadian-customs-ref.html
    >    =20
    >     Article 60 of French custom code authorizes inspection of anythin=
g you
    >     carry, can be interpreted as authorizing search of laptops or cel=
l phones:
    >     https://www.legifrance.gouv.fr/affichCode.do;jsessionid=3DAA678D3=
E2AC873493D4025F33776856A.tpdila20v_2?idSectionTA=3DLEGISCTA000006138841&ci=
dTexte=3DLEGITEXT000006071570&dateTexte=3D20130315
    >    =20
    >     Various European countries, including the UK and France, have pas=
sed
    >     inquisitive snooping laws. Maybe they are less visible than what =
happens
    >     in the US, but I would not hold my breath...
    >    =20
    >     -- Christian Huitema
    >    =20
    >    =20
    >    =20
    >    =20
    >    =20
    >    =20
    >    =20
    >     >
    >     > Definitively if that happens to me in EU, I will not provide pa=
sswords even if I don=E2=80=99t have anything to hide, but just because cus=
tomer=E2=80=99s info confidentiality, signed NDAs, etc. I don=E2=80=99t thi=
nk that will bring me to the jail. However, in US, detention is a fact, rig=
ht?
    >     >
    >     > Regards,
    >     > Jordi
    >     > =20
    >     >
    >    =20
    >    =20
    >    =20
    >    =20
    >=20
    >=20
    >=20
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >=20
    > This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that a=
ny disclosure, copying, distribution or use of the contents of this informa=
tion, including attached files, is prohibited.
    >=20
    >=20
    >=20
    >=20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Apr  3 19:01:56 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69DE512953B; Mon,  3 Apr 2017 19:01: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, 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 jMLhRh2XBAzp; Mon,  3 Apr 2017 19:01:46 -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 CEF4D129536; Mon,  3 Apr 2017 19:01:45 -0700 (PDT)
Received: from [10.0.0.194] (unknown [80.12.33.88]) (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 ECEE180ACC; Tue,  4 Apr 2017 03:53:40 +0200 (CEST)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com>
Date: Tue, 4 Apr 2017 01:15:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WHMkNI_SIf2AhfUDP6RMJmyAOoY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 02:01:47 -0000

On 03/31/2017 04:11 PM, Robert Raszuk wrote:
> I do not understand how 2460bis makes it "easier" if proposed change to
> the text directly tries to prohibit what is described in a document
> already long time back accepted as a 6man working group draft.

This is incorrect. For instance, the condition to accepting such I-D as
a wg items was indeed that EH insertion was removed, and that
encapsulation be used instead.

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 Apr  3 23:12:15 2017
Return-Path: <rraszuk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 723F9129522; Mon,  3 Apr 2017 23:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBWRWAHKTm5y; Mon,  3 Apr 2017 23:12:05 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAC4D1274D2; Mon,  3 Apr 2017 23:12:03 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id a140so23150995ita.0; Mon, 03 Apr 2017 23:12:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=A04AZGXnc0nwdH7Q/VkrNepyLWytWL9haOmEDxsjpN4=; b=DZEmx8DoGINV3IYZaGhVsB0UFw6L0cgjiQXanqx9paUbxoV41V5AigYSVPrgvt4HYI 8WyWSAxLsQ541uiHYgQd7eyrKFmFHAOfypBwXyCo6XHsI4IMOYYb20snoJEb/DWcRAig HTsDv4qfwahvM0fOslnT7owxklxItifqEIgPTcCm8TyAKir5yLAmcNPB+LSAp1QZj43O S3hN5hY/oUO69HxvOztHraRj8dIxJnAUqGmGVUWEitvECMU3fyoEeYHiP86JbA0ivM5U 7NjJpEdeSwYMXGclSQzup+ITS4iM21xjSvJOYGiS86luqe9zMK02gRRn4/BNU5sDy69s oIUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=A04AZGXnc0nwdH7Q/VkrNepyLWytWL9haOmEDxsjpN4=; b=f+KRRkvmZSUhePihZTfkl022iWABdQ1rtGKzw6gWH/MRqI4X/iNKG0VqNTWko0E/j+ 1ChtwPGnocz5lHRUbq1riCko97QEzp0SFWqp54yoRpAIEiyN3cqndMM0p3Vdm/Fet90X eAQn799d/E20plZuURbDObyBGWEAmpoBlyCx12tjLPs8tyyNH+n3mLsrhHVPkO8gtDzB 7cDjqD7YxKr8+bjz0cnxdoS2VlvftH/tMdvXPHGck67GYESuMWm6U70llUhJFUbyHXlF rwyWG1a3Ov1HvxZ7Un89DEiHuq4+OjFf4uR7UKxp6yNkKlZ1OXBbxwTNAV7aN7BkCISW jtIA==
X-Gm-Message-State: AFeK/H0wX0bgPx/kQQ9iJ2s/perF8tVFYS0vN3U9pmK3ixvRmLss7aH/o6N22teCQxn/5/SS1WEUP97ChkCgJw==
X-Received: by 10.36.115.12 with SMTP id y12mr8041129itb.24.1491286323043; Mon, 03 Apr 2017 23:12:03 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Mon, 3 Apr 2017 23:12:02 -0700 (PDT)
In-Reply-To: <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 4 Apr 2017 08:12:02 +0200
X-Google-Sender-Auth: C20EmhPWFEbnqTVcvAnYj28zJK4
Message-ID: <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Fernando Gont <fgont@si6networks.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Leddy, John" <John_Leddy@comcast.com>,  6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a11444dca8b2c72054c512764
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pLPHimOi4mNyWub2YNSlJj9tdHA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 06:12:07 -0000

--001a11444dca8b2c72054c512764
Content-Type: text/plain; charset=UTF-8

Hi Fernando,

The WG document talks about two cases ...

* EH insertion at the host (src of packet)

* IPv6 new encapsulation + EH insertion on the ingress to SR domain
followed by decapsulation at the egress of SR domain.

I hope we can agree on that.

However is it wise to expect any time within SR domain for a packet (v6
encapsulated on ingress) to get steered differently (say coming out of
service chain) to decapsulate and encapsulate again ? Seems to me like
quite local box decision anyway.

Hence my comment about implicit insertion.

In any case if we see this entire thread the only technical concern with EH
insertion was MTU. And how that issue is solved when you do additional IPv6
header encap ?

Or maybe encap is allowed simply as it can not be forbidden :))

Cheers,
Robert.


On Tue, Apr 4, 2017 at 1:15 AM, Fernando Gont <fgont@si6networks.com> wrote:

> On 03/31/2017 04:11 PM, Robert Raszuk wrote:
> > I do not understand how 2460bis makes it "easier" if proposed change to
> > the text directly tries to prohibit what is described in a document
> > already long time back accepted as a 6man working group draft.
>
> This is incorrect. For instance, the condition to accepting such I-D as
> a wg items was indeed that EH insertion was removed, and that
> encapsulation be used instead.
>
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>

--001a11444dca8b2c72054c512764
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Fernando,</div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small">The WG document talks about two cases ...=C2=A0<=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small">* EH insertion at the =
host (src of packet)=C2=A0</div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all">* IPv6 new encapsulation + EH insertion on the ingress to SR domain fo=
llowed by decapsulation at the egress of SR domain.</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"=
><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetic=
a,sans-serif;font-size:small">I hope we can agree on that.=C2=A0</div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small">However is it wise to expect any=
 time within SR domain for a packet (v6 encapsulated on ingress) to get ste=
ered differently (say coming out of service chain) to decapsulate and encap=
sulate again ? Seems to me like quite local box decision anyway.=C2=A0</div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-fa=
mily:arial,helvetica,sans-serif;font-size:small">Hence my comment about imp=
licit insertion.</div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">In an=
y case if we see this entire thread the only technical concern with EH inse=
rtion was MTU. And how that issue is solved when you do additional IPv6 hea=
der encap ?=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:ar=
ial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Or m=
aybe encap is allowed simply as it can not be forbidden :))</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small">Cheers,<br>Robert.</div><div class=3D=
"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:s=
mall"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Tue, Apr 4, 2017 at 1:15 AM, Fernando Gont <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">On 03/31/2017 04:11 PM, Robert Raszuk wrote:<br>
&gt; I do not understand how 2460bis makes it &quot;easier&quot; if propose=
d change to<br>
&gt; the text directly tries to prohibit what is described in a document<br=
>
&gt; already long time back accepted as a 6man working group draft.<br>
<br>
</span>This is incorrect. For instance, the condition to accepting such I-D=
 as<br>
a wg items was indeed that EH insertion was removed, and that<br>
encapsulation be used instead.<br>
<br>
Thanks,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a><=
br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a11444dca8b2c72054c512764--


From nobody Tue Apr  4 04:51:38 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA75129622 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 04:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.697
X-Spam-Level: 
X-Spam-Status: No, score=-4.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_HELO_PASS=-0.001, 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=btconnect.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 99UbY_rikY74 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 04:51:36 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10114.outbound.protection.outlook.com [40.107.1.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8995D12947F for <ietf@ietf.org>; Tue,  4 Apr 2017 04:51:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LJzIMWgMI8uRqefpu/ZQppqIQD0Ro/cwfhhUk5ldXKc=; b=BfVRncuLllwQUL+DZnBZVATdGRKzeLDxu94D7J8Kc2u0q4IyHEKV6Iyu/ZOxSnP5eDcDDEhxJ7hWoONe+P8eniBBDzZhR93/UQepLtPdYAz2iza7hhTuVKn4yojxC83aqDLw/KstXZfU7FnnKz+rPx+2vPtnYF38KIywcnmIPgg=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.169.157.161) by HE1PR07MB1561.eurprd07.prod.outlook.com (10.169.123.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.8; Tue, 4 Apr 2017 11:51:30 +0000
Message-ID: <0da801d2ad39$891d36e0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Tue, 4 Apr 2017 11:20:33 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.169.157.161]
X-ClientProxiedBy: VI1PR0801CA0084.eurprd08.prod.outlook.com (10.173.67.156) To HE1PR07MB1561.eurprd07.prod.outlook.com (10.169.123.11)
X-MS-Office365-Filtering-Correlation-Id: 718325d2-fd74-419c-73c1-08d47b50ef4f
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:HE1PR07MB1561; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 3:MmNOKTcUK2hbG3tB8EYK8Me0qrHK+25/zP28R3UO6V+ekFjmOiSWjOnDYXeCofutaeG/2ZXBDTin3YNStZj5mLY4nGF4/Gk/iPnZ2sbvfN+xnoA6hKT868T42styRr4LGK3QDYs3ufGwF/4SwF1KPe4twV1enF2F23iSW//91Q3YKL7eH5vKFDHrsEkWlCA9ShaaQZvcW3I/ugUR2l8Y5PxFaYiozZ1blRJBzGm1AhageidSJnQmqZLz0bGkbE1JivpZEDFML6pyGXtTeROhPHzhUKux+vE85zdN8WR5n2ZD5T3qee1DCk6uKR0yX5BbuwNw+NwmnzpMRgQp/sWldg==; 25:1xi/Zd+NsPQkfPAZWFPVrO/BzAWTl8NIm6kkHT1DFdCUrwJ+OSERkSYadYjPXuuToQsC8WxRwL38akVFPCTEWLTvMz3pH+TzYXV2TSyUNq7fIBHZ5O8dImLhnvdjbocoFNFehySYixCGrw+bixcLQzuN2QKAu8GV3StrpagXP5e4bQ1JWkllx92sI9uX8sOqbGplNzXPs+2p8pvSHiGr+KvrkqUPL2vsjT8lkEt7awIbVXGRfS4vM+IzzH7PxJlgdDtqPQYbJZRK0UHnhFMLB6+vuoGql+A6K2eJ0E5w96U7d0vhUdcAN17vqypRon4g4XRBsIOyHyephvxRUcF0AkWfjziMsjh085hjCfwrGnfPO3jtBmN9rIyIHUSQZncFnri6xaGU6Sf09VlqrkJC/Dp+kaKSoaim3BFRLGsRxuMgNTsPW8hlIQcvk39UU6WHfUzn74TRB0RA94T0D0mLIg==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 31:Cl2T3E5DpoC/I88nrAHyVFXu+ILHPJvBX1j9wFzPwHjnzPJnaFwyYZYKN4R8OES+HK47gg2srXRFZ/4xzFZMHeHjTGu9C0KtMXO1S16ohAVESGez0xMQmNvFLfSjGPpAXtqcpi3L4j6nqzNDftQTyYqStioJbGWIPB1hAFA1WIHGIdikeHT0r7GW7iQewFttQn0Z5h0TZbZOLnRCqw/qM1Mi9u1x5DOa4fni+nTTzUR8T3ZZBuqam+hUFoWX+mERc2A+Cfh0vUqm9NFVGN8JbmY6daME/6Xz/WXRS7QZXN0=
X-Microsoft-Antispam-PRVS: <HE1PR07MB1561C1E6FF92FCB3C9C7DA24C60B0@HE1PR07MB1561.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(20558992708506)(192374486261705);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6041248)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(20161123564025)(20161123562025)(6072148); SRVR:HE1PR07MB1561; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1561; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 4:n74VJpJB1x6RHG/upF/0tC+UC4aIy/Sq1ewmWBf11WZL4P39K88kkgU0fgAvCmfA11P/ssDe9o0x0Xoo+7B7z4MxvfExPyMaeUG1w26BOzCwAC/kjHNZUbO78WBy5gr7IeCcXTBzYx3aoWTI/9fpTWwQscgUoRjj1r0GFw5jQrGG3SX6Il2k1mg11lx4dhTvwC+JR6n9sxiIeUu+OyIyfRZ5dNyMQh4y2yU78ENT4hf9kZbNvg7ZLvPnEQAe2syugfUhasONG2C3CgZ0a98YR1DJYb7tpZwjUt/YjoEgbO4jZM4CaLZpdlXE3LdMoS7u0BEIZT1iFX+K5a7dCZsd+zDQ11JdAqImETNPX0kZPbtIu3bONHZIkdtmR/NLN0H6PK9zpLNTzgLg1kvExcxbelbrWFJmT8Wf96NKwslqIVb5WYW4qC20TYMlfIrve1vB7AdHvohO53z5VIM7cZD4ra/yMcap40fpq1SeDwTCdIr3axD5cKHYTVlLH/goX/eki28Kqz4zlE2crRtXNXKuDUFto1hqG8tERt+FufxbtvJZ/VBla7Vzc9lIgxMeg7uKkDPcFuSMBeQY/eGU9+5jgmu1JurtD09+4npEfGnKsrV+6cMAjqzV3eLVEuHMzAESr/ru3otoBXbLzHCDNRmgTyi0RF7aHamo9NUk4UYSnt2rYWVvDJAuIt83iajAyMSwfGJl5lzDCgnliyUKnlji0Pts7d1aXmXffcfcNMx3vOfLPaqVpHBWzvcx4S27Jm6PlbGomluDhbt80mfizrf1UphZJu5AlmdWwCXwfq9PGXQ=
X-Forefront-PRVS: 0267E514F9
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39840400002)(39860400002)(39850400002)(39400400002)(39410400002)(39450400003)(377454003)(13464003)(24454002)(25786009)(44716002)(62236002)(93886004)(4720700003)(3846002)(53546009)(50466002)(38730400002)(1556002)(47776003)(66066001)(229853002)(5820100001)(61296003)(230700001)(189998001)(23676002)(6116002)(42186005)(8676002)(50226002)(7736002)(84392002)(81816999)(81166006)(305945005)(50986999)(14496001)(81686999)(6486002)(86362001)(6496005)(33646002)(44736005)(6246003)(9686003)(53936002)(5660300001)(2906002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1561; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYxOzIzOlJEQmVjWWZoK08zdlU0V3l0UFNnSkNzUEVK?= =?utf-8?B?VDdBZmVzVVh3eGhrWlFDR0Q2Wk53eFVDeVdUdm9jWXZibjlYaUZSUlZpOHln?= =?utf-8?B?N2ZTbnlvRXJDcDFKbEZiNzBCWTloTlhCS2U2UjFBbTF2RlVFVi9YNERDM2pG?= =?utf-8?B?RzkzYVJCZDh2ME9JZCtvRVZvRWFySlJPbXMzTUNrT09sRjZma0NReWk5bWln?= =?utf-8?B?Y090aCtkSVVqRWx5S1NnQ05BL2JLbTVqakk2WlRES3NWby9mN1d2dEttYVZv?= =?utf-8?B?V3IwRllKb1FqN1pLOUY3YktpaXAvanN0MDF4ZjVqT1FXMXNKdjhVbWhoVVBG?= =?utf-8?B?Zk9wUWRucU1rQUkydGtIaXcwMkkvN1Z6SHpWdGJSazVqb3ZwNzVnSnRlUkRK?= =?utf-8?B?UHF3d2xqU1RwSTNTZmV0SU84WC9DRkVxSjZOY3J4Z0NiWjhLbmo1bUhqSlZM?= =?utf-8?B?VW54dDFLR2cwOUNJVUZleUNFN085b1BvejVXelNFZVIvQ01pUzFxSkdSSVpw?= =?utf-8?B?KzZhTTBHTWR2aERwUHlRbVY2cWYwVFJZWVBBeVlQaUY0aXdZSldvRVdLalVU?= =?utf-8?B?OENpMVdlTXptcTdXb1Rtd3VvWHhSWmlzL241OG9SSS8ya29LVFE1UldSZnN1?= =?utf-8?B?ckpUN0J0WGlrNnBGWm1xaTVwVm1SOC9qb0hLcC9kZWlLOVNhaEdRVWlJbmdL?= =?utf-8?B?QythN0xreHc0MGQyOHRpbmw2MWFvUG1FY1IyTjR4N1NZdWJ6S2FZQzNZNWln?= =?utf-8?B?MUdZUWJQZnlSWEg3T3ducGJxSytjV1A5Uk9nQitXYUpSTHR2dE1JSHc1azRS?= =?utf-8?B?OGVrcHl5UklLV1pqN1RSWVd0c05VbEpIcm5aUms2enNiODJQdlhzSE0ybjln?= =?utf-8?B?U2V6c01tWTlMWHY2amhTWUhRbERGS2JCY3lyMGZpbE0wRWpITGVLSVJHSDls?= =?utf-8?B?Rkg0OEV2VTFpZGpibWRNSU81T2RVZ2VSQmlHcGZjazJrWEZxeEJHdFU5U1RT?= =?utf-8?B?Uy9nMDI1bFd3Y1V4WVpkZU9hNFBac1k1YUplS0VkbjRoSm5OeUF6ZVl2c2NT?= =?utf-8?B?WmRUNjFjc2Y0VWdHVjdMclk3R2R6TDdZdDhUdW8rcUE2T0hwYVRKUHh6Yzlj?= =?utf-8?B?N2pyMFZJRS92RUZQeGlyUE1PeEp4bnc0cVcyUGN6bFZvUmI0QzAwcG1DWWJa?= =?utf-8?B?cUdMSUVMNjZsMU1kZXhqeXFseFg4YldmcDE4TnduYnljNStPbkd1VjkwdHFR?= =?utf-8?B?bVZMS2E5TmpHZ1A0WElJam1qaXBxZXplc0taUGxXc2YraFI3OUc0ZEFjdG1O?= =?utf-8?B?cUZHWU43SDNDdWdhSDNVQmxWaGh1dXVoTHU0akQyRzl1aitFNjFCWXdVL0N5?= =?utf-8?B?eXN5bzR1TVVGWk12NGl0czEwQWV6Ylloc0VjOHovOG0rMUVxeE94QzczUlZm?= =?utf-8?B?TW9JZ2tyeXJ3TEZIdDlKMi9uQ2ZzTmlxeHRNaDdjdi9HYVZ6YzkrQU1RYStu?= =?utf-8?B?NnJHTnVvbXFYcS9ubmRCVXdXN25ScGVYd3Z0RVpMYWg5SHE4d1dkZUYra2dR?= =?utf-8?B?S0JTS0VROTJjUjNxVWV4N3QrUTlIYzROWGpvWnJ2anczVnVINENqK0RpV3pj?= =?utf-8?B?dEt5STZQaTA5NzZTSldJaFFXeXBERWE5YmtSSk8zaysyRm9MS0JMRmJLWm5E?= =?utf-8?B?ZHBuVngrY1U0cjRGS2liWnFHYjV4RTFCZFZMaklaUlBFeU5aVjNBcXBlaXRr?= =?utf-8?Q?EwIXARBZj7xROysWedaxYxXubLrBiMHkvEuQo=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 6:7xTvTUxjRIqKTHR8SY0r1mcOoh6ir1zKrsXaq3oPWX/wnbePa9y5f0G24iaUwwNmwCfRunM/J3nm3z2+j4xoEptWicY2XX4ymbWL9dEYYoA78vG72vxj+zqel/UtIKJ0zuhMz8lRLy7Y7KBRjKYEPjxRlaqg8IZ7tOJX4c+sgKW6LWuyJL+F+P9nuInyOLWgeYCM/QJrevggl6DlGi4Oq0bcUoYKP4+NgudmOkj9i90FpIY4vOOx+g/lrrxRZ1+SGkT53zLN0q+SzzfraOvqUM67wwr/hml/hMcIo6RiRqmTqfLQ99BGFTikoOvXJ/C66Lpfqc/dtv+PtbyI8s6HfmKFxWTuTuhuwCxPxFkk1W0hHHwAs5PP20hn4f/zNGfvigrCMENAKPkgjuaw0RlP9A==; 5:4a8CzPFgxzaUMXxncsP33DfVESHBvrfPaG56USzBZVSekL9AvRxlWZUBY5HMOXz9Cc4O9+JaI5lSNvwoDKdPj7joRhWRCmR4A0GTwGdEo5LzIhIsPbyTl9vXHr4MpQFKzlzv0Sr9m1MNuBqGQ8S8YQ==; 24:E+sVvB8kaFcI6PoMzabwgcFlY7TpHGbaggdavpdx1SiR1XplU4HgUC12P5wnF0SdHGxu0YA/mxKgc2HJGEb05XwH0t3/pDDebjuGVgjP3ao=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 7:Ey/QrHG7JdLklK0RtgpkcYStr1F1qsLLGwxLuIJh0gBw98wUhSQzIVTfUh8fvbSrySRj8C9qaKRcoL4rSxW9BzUmp4ZKNjas5qkLLKnpPCODILY0mfojviBwK7iGFH35uoeYGgwP4IKh1nEo+3Mnvo3AOhU8revhSwhxdvksPAGUHvyPf45R1ln6tGNrJxdZ8Ur3+qnpvEEgXY8aGYFyYGKziX4wNK8jMqAqeBj0EKqEO9PZXDqr4ZANbLGym+h+PRJEhb1UsWXglP+tBfVqPqE0/KfYSdh2sjrn/YyT7H4WWmKm0/X1JTmRzKLujaKMvDMttztnh+6tz9YpHFAvng==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Apr 2017 11:51:30.4430 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1561
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gjiq9-FH3hp-PFd9wypwDm0vCb4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 11:51:38 -0000

---- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: <ietf@ietf.org>
Sent: Monday, April 03, 2017 5:23 PM

> On 04/04/2017 03:26, Rich Kulawiec wrote:
> > On Fri, Mar 31, 2017 at 11:59:49AM -0500, Paul Wouters wrote:
> >> I don't know when I will be refused entry for not handing out
> >> passwords or pins.
> ...
> > Moreover, the ad hoc policies that are in place are used very
> > inconsistently -- at the personal whims of those enforcing them --
> > and are subject to change not only without advance notice,
> > but without any notice of any kind.
> >
> > Because of this, asking anyone to come to the US at this time is
> > equivalent to asking them to incur unknown but possibly very large
> > privacy and security risks, as well the financial risk of losing
> > any/all computing devices they bring with them.
>
> What is specific to the US in all that? Afaik, customs or immigration
> officers have similar rights in many, if not most, countries. And they
> use them from time to time, at random or as a result of profiling.

Fly into the UK from Middle Eastern countries and you are now required
to place any electronic device larger than an iPad into the hold, where
it will not be covered by most insurance policies.  This was introduced
at short notice.

The press reports say that other European countries and Canada are
considering similar restrictions.

I am reminded of the inkjet cartridge bombs of a few years ago.

Tom Petch

> Before you formally enter the country, your rights are limited
> in most cases, not only in the US.
>
>     Brian
>


From nobody Tue Apr  4 05:57:34 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D795126BF7; Tue,  4 Apr 2017 05:57: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, 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 7HSAmAxS_ZtP; Tue,  4 Apr 2017 05:57:24 -0700 (PDT)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 B8C6F1272E1; Tue,  4 Apr 2017 05:57:24 -0700 (PDT)
Received: by mail-io0-x243.google.com with SMTP id f84so14941858ioj.0; Tue, 04 Apr 2017 05:57:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=WWQfwUJPwpAcRz1apkb40APl7+n7NxiBjuS1xaIv7Zk=; b=Ko4fK2GIT8ecN+8U73CW71DXbd6jp4zQ0iPbmNwWzBlhxEEPksAGdazIc+Myjyn6D4 NSyYGYxj3Y6H/De2+AboUWGhdapulwOrbYZPWxiIEKsMOl1Zc2R2a9OXiocsBwHXosaf te2lpEda+qV3X352bfWlCQqjrO41Qd4HFEkUS0T+dHlA8SN95zsGWgCa0EzcVXD1xs7r 38Mltg2Pof7VDfH/1lNugA9ZNs2eOK/Qd6QDji3YAMa89itgctvwxn4lwLj5chQwNNxF TysBQUcNShltS43AAWLqSkgh0c8Xrn9IynAqTljAMn1jdFDpWCVCTS9XYeqJONympDPk 0ofA==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=WWQfwUJPwpAcRz1apkb40APl7+n7NxiBjuS1xaIv7Zk=; b=TD4S/igOZ1kp2UYCbtpDvc/aLIRzhbgHQOZtpTnTW1OIQJYIqV4FecHjuSiH5MmAnM 79Av2FsmRAL0IwB/K5fTTdzwwS69u1ND3XdcGX7zfCqXjobv3Tj0tf63+4ULaRlToKkU TkOYUS2/wuwaIVVriG56oTSmFaiZINM2900/LePvvn63irLg46MgswbX2mnjUlsP6Pze S3dDIOz/EDYNOrr8a7uimqi8Qce3T7++yCAUNUd9FcHrCEttsSjhNZ+C4C1Dxaz9+jHV pmo+1nqcQsdDJ1nh2+TSA5ZFQj0ezgLCn0kxBgNgdZ3Z2yxizxEvsydmq/U5IynSfhLC kpOg==
X-Gm-Message-State: AFeK/H21SP4Z2kdP45Pl8McmYHbbTWJNBCa0xY6BGgAA/jy6GOaJJLkK67bXncgHo0yieg==
X-Received: by 10.107.174.27 with SMTP id x27mr21260900ioe.35.1491310643940; Tue, 04 Apr 2017 05:57:23 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id v187sm8627663ith.18.2017.04.04.05.57.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 05:57:23 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>, Fernando Gont <fgont@si6networks.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com> <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ec10ed2a-a187-4539-d62e-67d331881887@gmail.com>
Date: Wed, 5 Apr 2017 00:57:19 +1200
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: <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NEdc_U1Psx7O5BU5Q3ArG6x8FzA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 12:57:26 -0000

On 04/04/2017 18:12, Robert Raszuk wrote:
> Hi Fernando,
> 
> The WG document talks about two cases ...
> 
> * EH insertion at the host (src of packet)
> 
> * IPv6 new encapsulation + EH insertion on the ingress to SR domain
> followed by decapsulation at the egress of SR domain.
> 
> I hope we can agree on that.

We can't, because neither of them is "insertion". They are simply packets
created at their source (the encapsulator) that happen to contain SR headers,
or any other kind of IPv6 extension header for that matter.

> However is it wise to expect any time within SR domain for a packet (v6
> encapsulated on ingress) to get steered differently (say coming out of
> service chain) to decapsulate and encapsulate again ? Seems to me like
> quite local box decision anyway.

Yes, they can decapsulate and re-encapsulate as often as they like and 
remain consistent with 2460bis.

> Hence my comment about implicit insertion.
> 
> In any case if we see this entire thread the only technical concern with EH
> insertion was MTU. And how that issue is solved when you do additional IPv6
> header encap ?

PMTUD applies to the path between source A (encapsulator) and destination B
(decapsulator). If you decapsulate at B and the encapsulate again, PMTUD
applies to the path between B (encapsulator) and C (decapsulator). They are
completely independent; it's a new packet. PMTUD doesn't occur between A 
and C at all.

    Brian

> 
> Or maybe encap is allowed simply as it can not be forbidden :))
> 
> Cheers,
> Robert.
> 
> 
> On Tue, Apr 4, 2017 at 1:15 AM, Fernando Gont <fgont@si6networks.com> wrote:
> 
>> On 03/31/2017 04:11 PM, Robert Raszuk wrote:
>>> I do not understand how 2460bis makes it "easier" if proposed change to
>>> the text directly tries to prohibit what is described in a document
>>> already long time back accepted as a 6man working group draft.
>>
>> This is incorrect. For instance, the condition to accepting such I-D as
>> a wg items was indeed that EH insertion was removed, and that
>> encapsulation be used instead.
>>
>> Thanks,
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>>
>>
> 


From nobody Tue Apr  4 06:22:38 2017
Return-Path: <rraszuk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0155129574; Tue,  4 Apr 2017 06:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SsRXSgF1wxDH; Tue,  4 Apr 2017 06:22:34 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 74E28127BA3; Tue,  4 Apr 2017 06:22:34 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id b140so95204517iof.1; Tue, 04 Apr 2017 06:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Qw4cyhUsyuBzjahzoNrzCFKLxnM9UwLM4k4KhcpIWl0=; b=OPE64tGqzV8S70Hi92AS3AHS2OLT5l0dj2k5YTIffK/oZ0qyeI+c2BfeIL0nK//qma QnOR4jik95172jBG6g9Uk+djP1kJxyNsFmlAoZsVbSvD/FaNQbFx9QdPWXF0KAwqCdAu 9FQ1rB+nKOI3/6UXAsbZin6GalA5rBzSm35UlDcMAGUmYYdYJsc2+PZWdWfMsK4UZf1K d30ezUbIWziPB+Y3JX/axcChDjnkF5QD8Th8aqYOvq7NHKwN1j+UW7xOVEVZnSqmFnfH Y24RrG9H8nNQbHZgvm2M6A682ThitsJOGaGfzOumW2j6gZUg6PUHGStvw6eMB6pbgmvV xqMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Qw4cyhUsyuBzjahzoNrzCFKLxnM9UwLM4k4KhcpIWl0=; b=mK7gSt9mYGEeHpae7Z9va+WLbQM1od77mcDIRyfgkxHyqfBPr9mrz1bIj0d2A90d+/ 76jQqZd+V32zxrj38TkzTSaB6m6rBj8BCcOJk3Emzapkwejm/caUvOVAN47UMTiqyWWy XNFWUn0NmwCttgr1j8oacF0sI0rFXTZdZRC/wXapAab8OgPfx2pM37BTjPs2jL1W7F8x mZYNAyIoYASTlbJy2wtKxqirPRwQ2AmG8chvKu6d4x+zII4v3rOrYikkmSm0SffsYeGP 1d9hv1Otwa2dqSJZLTr+t9KdRJPhIrlx37uUOCYzwRoC7nC/jxlZHH/NmGm74CU8xwVO DJMA==
X-Gm-Message-State: AFeK/H2cmtDLaUXzD6q5dvFVdqibpvzRn0h4QHKH+qiGvdLRxfFNNENNO2ycSQQSdJRR9tx3av8X2+oxblbZIA==
X-Received: by 10.107.16.217 with SMTP id 86mr22120729ioq.228.1491312153820; Tue, 04 Apr 2017 06:22:33 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.90.71 with HTTP; Tue, 4 Apr 2017 06:22:32 -0700 (PDT)
In-Reply-To: <ec10ed2a-a187-4539-d62e-67d331881887@gmail.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com> <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com> <ec10ed2a-a187-4539-d62e-67d331881887@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 4 Apr 2017 15:22:32 +0200
X-Google-Sender-Auth: 0rzdkcIfF7pHL8czRE0jvWMHiO0
Message-ID: <CA+b+ERnowxo2ynO9QomXMOEwnQjVJB703NsNUzW9qACOco8CVg@mail.gmail.com>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, "Leddy, John" <John_Leddy@comcast.com>,  6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>,  "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ecee82da7fc054c572bef
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wMxS3E2gzry85fReMeA1SZSFHoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 13:22:37 -0000

--001a113ecee82da7fc054c572bef
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Brian,

> In any case if we see this entire thread the only technical concern with
> EH
> > insertion was MTU. And how that issue is solved when you do additional
> IPv6
> > header encap ?
>
> PMTUD applies to the path between source A (encapsulator) and destination=
 B
> (decapsulator). If you decapsulate at B and the encapsulate again, PMTUD
> applies to the path between B (encapsulator) and C (decapsulator). They a=
re
> completely independent; it's a new packet. PMTUD doesn't occur between A
> and C at all.
>


=E2=80=8BAre you saying that it is "legal" to fragment IPv6 packet by a rou=
ter at
the encapsulation point in the network ?

That would be news to me.

Many thx,
Robert.

--001a113ecee82da7fc054c572bef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Brian,</div><div class=3D"gmail_defa=
ult" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br><=
/div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><span class=3D"">&gt; In any case if we see this entire thre=
ad the only technical concern with EH<br>
&gt; insertion was MTU. And how that issue is solved when you do additional=
 IPv6<br>
&gt; header encap ?<br>
<br>
</span>PMTUD applies to the path between source A (encapsulator) and destin=
ation B<br>
(decapsulator). If you decapsulate at B and the encapsulate again, PMTUD<br=
>
applies to the path between B (encapsulator) and C (decapsulator). They are=
<br>
completely independent; it&#39;s a new packet. PMTUD doesn&#39;t occur betw=
een A<br>
and C at all.<br></blockquote><div><br></div><div><br></div><div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small">=E2=80=8BAre you saying that it is &quot;legal&quot; to fragment I=
Pv6 packet by a router at the encapsulation point in the network ?=C2=A0</d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small">That would be news to me=
.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-family:arial,helvetica,sans-serif;font-size:small">Many thx,</div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small">Robert.</div><br></div></div></div></div>

--001a113ecee82da7fc054c572bef--


From nobody Tue Apr  4 06:37:06 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5FC127599; Tue,  4 Apr 2017 06:36:58 -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 aNKDZwr5qnz5; Tue,  4 Apr 2017 06:36:57 -0700 (PDT)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::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 C7A1E127342; Tue,  4 Apr 2017 06:36:55 -0700 (PDT)
Received: by mail-io0-x242.google.com with SMTP id n76so15034793ioe.1; Tue, 04 Apr 2017 06:36:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=bUPVykfyFdCqBRXvqE4Nuor2LA7ZNf9hFPB9foDs0GY=; b=SC0R6/eT5Q7TddBgVKW3IlbU656R2831Cc0QLiWli9NZqt9M+AxkdtSDqyYFLDDiiU VNczL1O50erfYq1jqylUwVDYprmzFmdLlMj7FlFElUV4A0prgDagXc/jUDP4rsRC5xIU NTrLd3LlCLQ86HlO4W8twZEYgNTwh0Haj+YvNHbLBJEblTP5UDJcchhUco/MYNEs5Qea s5X/7jBziSpzhTqXFyg4aV14mydk4y1nabd1Dhc8tdr9xCrZHSVQZ0xUqsj7KIOc4LEL x4HpCzU7l8Njwqgx7aejrHakJA67yjUSwBy3ZpSsejp2jSsrOQdsiZDKp3PQM88nDDAE uE3Q==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=bUPVykfyFdCqBRXvqE4Nuor2LA7ZNf9hFPB9foDs0GY=; b=hQneZ8ZZ8pPlJQdQA9xE5tRADDY7x/eN0eXlQsGl9oouy1V8w242VPO4As8hdgyCBy /28ShvxE6DK9thuuSa/5xvak0KnYoKmgfxpsfwZK9zWt3FpTieuAFIscHBqg8dFQYBBi 1M8aBrJuRCosgweRY5IudP5JvDImZpb5fszpszhpjEdgWMKMm7ZYJ1cxXs1mC+yypAmT 0VMCtaWwUKk9FlH10M3Y+9BCulNL8JE/pkfveBhdxXh69a4SFfnzuH+tA2p9qGtPcjZI 5qbOKgkSAR4uyTGD1mHEULwPSIq3+vjDbFyQCek8+qqTBB3BYiDMUF6vXzoJHJhRCETM hgEg==
X-Gm-Message-State: AFeK/H3/X4YiSuUBRXVrVHA79m8jG672T9nU5tc66aCMOJ4y255W9i6zomhy+REt95QgcA==
X-Received: by 10.107.62.68 with SMTP id l65mr24996480ioa.213.1491313014869; Tue, 04 Apr 2017 06:36:54 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id m77sm7240562ita.16.2017.04.04.06.36.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 06:36:54 -0700 (PDT)
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
To: Robert Raszuk <robert@raszuk.net>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com> <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com> <ec10ed2a-a187-4539-d62e-67d331881887@gmail.com> <CA+b+ERnowxo2ynO9QomXMOEwnQjVJB703NsNUzW9qACOco8CVg@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0a74d9a6-24d3-ea00-07f2-61144f7725a4@gmail.com>
Date: Wed, 5 Apr 2017 01:36:54 +1200
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: <CA+b+ERnowxo2ynO9QomXMOEwnQjVJB703NsNUzW9qACOco8CVg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/57UAAeaf2uSM3VsrpPnDIYVRdnQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 13:36:59 -0000

On 05/04/2017 01:22, Robert Raszuk wrote:
> Hi Brian,
>=20
>> In any case if we see this entire thread the only technical concern wi=
th
>> EH
>>> insertion was MTU. And how that issue is solved when you do additiona=
l
>> IPv6
>>> header encap ?
>>
>> PMTUD applies to the path between source A (encapsulator) and destinat=
ion B
>> (decapsulator). If you decapsulate at B and the encapsulate again, PMT=
UD
>> applies to the path between B (encapsulator) and C (decapsulator). The=
y are
>> completely independent; it's a new packet. PMTUD doesn't occur between=
 A
>> and C at all.
>>
>=20
>=20
> =E2=80=8BAre you saying that it is "legal" to fragment IPv6 packet by a=
 router at
> the encapsulation point in the network ?

I can't see any reason why the encapsulating packet couldn't be fragmente=
d;
it's just a packet (whose payload happens to be another packet). But I wo=
uld
hope that jumbo frames would make this unnecessary in the scenarios where=

SR will be used.

Also, assuming 2460bis is on its way through the IESG and RFC Editor soon=
,
I can't see any reason why draft-ietf-6man-segment-routing-header-06
couldn't proceed to WG Last Call. I'm not quite sure why we're having thi=
s
conversation.

   Brian


From nobody Tue Apr  4 06:56:50 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92366126DEE; Tue,  4 Apr 2017 06:56:42 -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 3yCaJ_VXcXaq; Tue,  4 Apr 2017 06:56:40 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 854E212869B; Tue,  4 Apr 2017 06:56:40 -0700 (PDT)
X-AuditID: c6180641-417ff700000058cf-45-58e35fbd5744
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by  (Symantec Mail Security) with SMTP id 8B.9C.22735.DBF53E85; Tue,  4 Apr 2017 10:56:31 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0339.000; Tue, 4 Apr 2017 09:56:37 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Raszuk <robert@raszuk.net>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fernando Gont <fgont@si6networks.com>, "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis.all@ietf.org" <draft-ietf-6man-rfc2460bis.all@ietf.org>
Subject: Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Topic: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08
Thread-Index: AQHSnTZv86cghjjmGk6P6rsvHH5Q4qGssVmAgAD+BwCAAAesgIAAIVmAgAAFgwCAAASPgIAAEkGAgABB5oCAAAHpgIAAAteAgAACGICAAAp2gIABEiqAgAVOxgCAAHSFAIAAcTyAgAAHDACAAAmFgA==
Date: Tue, 4 Apr 2017 13:56:37 +0000
Message-ID: <49627D61-E761-4739-A349-C9639F0D6350@ericsson.com>
References: <599257D7-532D-4512-929B-D124623EAF35@ericsson.com> <6B662F87-B0E6-4613-B406-8A22CA95DFA5@cisco.com> <4917F161-2EC8-43E0-AF4C-BFAEE44A492C@cable.comcast.com> <198e3116-5448-2fdf-4da7-4811a0133f05@gmail.com> <50E4A84C-F0ED-45ED-AA89-5713CBD8F9E0@gmail.com> <5aebc8ed-f873-94e9-1ae4-dab7b3a8ebef@gmail.com> <CA+b+ERk8kHWyBY3GPp21-pgrL_SsShaLkrn4UdecFeQPYamSEg@mail.gmail.com> <A0F19A98-7DBE-4616-B949-529ED2A81D62@ericsson.com> <CA+b+ERk_cKGB6a0SQd560cMiOzT4KbSic6fCCwQWrhNkNEcO3Q@mail.gmail.com> <76ABEAE0-6A89-4C69-82ED-968F949A3B19@employees.org> <CA+b+ERmqpRuw0z4ZQkhNYfEqGvqEJKYwM0hkuWg8dZrYXT4DdQ@mail.gmail.com> <FCFFDDCF-7A53-41E2-B414-53E568C92B35@employees.org> <CA+b+ERmELF1p_5vX_nqhB58Bm8c34N6=kkijuCRYkfkQcfKneQ@mail.gmail.com> <0ae6ba21-0529-e9ca-ab74-b18a85acad4a@gmail.com> <CA+b+ERm7vO-ZpSHKLvY+BfgWpMa7+abKR6BFnXkgUuUPEXYVEg@mail.gmail.com> <931f29e0-a029-2098-38c9-bc65e43ca0ab@si6networks.com> <CA+b+ERk2E43abOjYQSLQNpYu7OUunZhMzrHdaNxndWEujPa9Qw@mail.gmail.com> <ec10ed2a-a187-4539-d62e-67d331881887@gmail.com> <CA+b+ERnowxo2ynO9QomXMOEwnQjVJB703NsNUzW9qACOco8CVg@mail.gmail.com>
In-Reply-To: <CA+b+ERnowxo2ynO9QomXMOEwnQjVJB703NsNUzW9qACOco8CVg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_63BBCF24-C889-42DE-ABE0-68654718A7D1"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUyuXRPlO7++McRBp8vslu0XdzHZPHq7TU2 iyer3rBZPNs4n8Xi5dn3TBZLFyxnsmha2MTswO5xvbOF2WPnrLvsHkuW/GTy2L1xAZPHh0M9 7AGsUVw2Kak5mWWpRfp2CVwZa1/1MBVs8a3Y1/2HrYHxk3sXIyeHhICJRFtrH2MXIxeHkMAG RomdS6+zQTjLGCX2zTjECFLFBlS1YednJhBbREBVovPEI2aQImaBmUwSj24fYAZJCAt4SEza dI0FoshTYt3GwywgRSIgky7f+g/UzcHBIqAi8fBGFojJK2AvsfSID8SyXxwSC3uugM3hFAiU +Hh9P9gcRgExie+n1oAtZhYQl7j1ZD4TxNkiEg8vnmaDsEUlXj7+xwphK0l8/D2fHeK4KYwS pxesByviFRCUODnzCcsERpFZSGbNQlY3C0kdRFGSxKkN/6FsbYllC18zQ9iaEvu7l2MR15Do /DaRFcI2lXh99CMjhG0tMePXQTYIW1FiSvdD9gWM3KsYOUqLC3Jy040MNzECo/6YBJvjDsa9 vZ6HGAU4GJV4eBVkH0UIsSaWFVfmHmJUAWp9tGH1BUYplrz8vFQlEd6YRY8jhHhTEiurUovy 44tKc1KLDzFKc7AoifO+K78QISSQnliSmp2aWpBaBJNl4uCUamAUWXi1eeu/5KmhzAe10xn8 D0xIcX60bg139MKcXQfqOfpVAl3tdq24pVTNXPj7K2OhAMvHtDyFivkh0W4frX9y2L+bxCJ1 /Nua5z8/Z68uCHG+YSGyY4aENtcel861j6wOzr1mlCJ2OdpfI6R86rdEmZVrF3aYl37gCpmQ MuPwu80OvsE37l5QYinOSDTUYi4qTgQAvaEWOgIDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2epRHT8qmvo_eRDra0GpsyG3f8E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 13:56:43 -0000

--Apple-Mail=_63BBCF24-C889-42DE-ABE0-68654718A7D1
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_CE5659DB-942D-49A9-A5F6-930E93C08D52"


--Apple-Mail=_CE5659DB-942D-49A9-A5F6-930E93C08D52
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Robert,

> On Apr 4, 2017, at 9:22 AM, Robert Raszuk <robert@raszuk.net> wrote:
>=20
> Hi Brian,
>=20
> > In any case if we see this entire thread the only technical concern =
with EH
> > insertion was MTU. And how that issue is solved when you do =
additional IPv6
> > header encap ?
>=20
> PMTUD applies to the path between source A (encapsulator) and =
destination B
> (decapsulator). If you decapsulate at B and the encapsulate again, =
PMTUD
> applies to the path between B (encapsulator) and C (decapsulator). =
They are
> completely independent; it's a new packet. PMTUD doesn't occur between =
A
> and C at all.
>=20
>=20
> =E2=80=8BAre you saying that it is "legal" to fragment IPv6 packet by =
a router at the encapsulation point in the network ?=20

>=20
> That would be news to me.=20

Yes. It is legal. Please take a look at section 7 of RFC2473.

Regards
Suresh=

--Apple-Mail=_CE5659DB-942D-49A9-A5F6-930E93C08D52
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; -webkit-line-break: after-white-space;" =
class=3D"">Hi Robert,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Apr 4, 2017, at 9:22 AM, =
Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net" =
class=3D"">robert@raszuk.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Hi =
Brian,</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br =
class=3D""></div><div class=3D"gmail_extra"><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"><span =
class=3D"">&gt; In any case if we see this entire thread the only =
technical concern with EH<br class=3D"">
&gt; insertion was MTU. And how that issue is solved when you do =
additional IPv6<br class=3D"">
&gt; header encap ?<br class=3D"">
<br class=3D"">
</span>PMTUD applies to the path between source A (encapsulator) and =
destination B<br class=3D"">
(decapsulator). If you decapsulate at B and the encapsulate again, =
PMTUD<br class=3D"">
applies to the path between B (encapsulator) and C (decapsulator). They =
are<br class=3D"">
completely independent; it's a new packet. PMTUD doesn't occur between =
A<br class=3D"">
and C at all.<br class=3D""></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D""><div=
 class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small">=E2=80=8B=
Are you saying that it is "legal" to fragment IPv6 packet by a router at =
the encapsulation point in the network =
?&nbsp;</div></div></div></div></div></div></blockquote></div><div><blockq=
uote type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div =
class=3D""><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br =
class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small">That =
would be news to =
me.&nbsp;</div></div></div></div></div></div></blockquote><div><br =
class=3D""></div>Yes. It is legal. Please take a look at section 7 of =
RFC2473.</div><div><br class=3D""></div></div><div =
class=3D"">Regards</div><div class=3D"">Suresh</div></body></html>=

--Apple-Mail=_CE5659DB-942D-49A9-A5F6-930E93C08D52--

--Apple-Mail=_63BBCF24-C889-42DE-ABE0-68654718A7D1
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwNDA0MTM1NjM4WjAjBgkqhkiG9w0B
CQQxFgQU2xsx4q0G1UkuF1+RzAWPYYxQHqgwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQCcS1rRq1tV+pO8gxJGwlDG1GdoHR0nGMvyG9n6vudIM50Gm+hamhdj+3tNJlYY
FiBBSmFndT4cTgAbKUVZCrjLUpVgThlGA8TFn3ql2W9Ey1fWpJnf3WDHTEgMw2ymZexldgq5bTHS
b6bIAC4fJh8eAJIX6AcKjTrVdoK0qiHIFoHsTpNpVed4GJ/dcxKzfj4csNPk280Eyjtm7k8y81LM
lTpP7TbugVtrrMMmiF97Ft8Fad2NaCXpPU1pCesijcBkrAb+ydv7ooqcAtORJZBkoiJUL9/DOpBG
8iTMmVRujPNVTjayPgckp3bCSH/bjNFsic47Khf917XtA707NA/JAAAAAAAA

--Apple-Mail=_63BBCF24-C889-42DE-ABE0-68654718A7D1--


From nobody Tue Apr  4 11:15:12 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39724124281 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 11:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level: 
X-Spam-Status: No, score=-4.296 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, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 twcjEVFA9QiE for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 11:15:10 -0700 (PDT)
Received: from homiemail-a106.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2E27120046 for <ietf@ietf.org>; Tue,  4 Apr 2017 11:15:09 -0700 (PDT)
Received: from homiemail-a106.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a106.g.dreamhost.com (Postfix) with ESMTP id 724663000291E; Tue,  4 Apr 2017 11:15:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=u/sE9oPvVx02YUAgQmxVC4hQIlw=; b=dGVPnH+U8Ic u1vIhWpvrQthi0kEc/YLBFFf9c4FKc4HcYFKXWZ7ArruGJ7LswAH4q+rMvQUYdsy 5gyswJQV2BUHDUdgYLUk2V9oYG4iqdLRKESKj+oWHTiTqEs0OigrZIeBVrpAXIhT 5Wg6d/7y0PZPaqdh/l19nEHm49coh/ZI=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a106.g.dreamhost.com (Postfix) with ESMTPSA id 04E5530002902; Tue,  4 Apr 2017 11:15:08 -0700 (PDT)
Date: Tue, 4 Apr 2017 13:15:07 -0500
From: Nico Williams <nico@cryptonector.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404181505.GA4004@localhost>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5G5TiTHliBdhmaayEfjzDuk3BuE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 18:15:11 -0000

On Mon, Apr 03, 2017 at 06:39:32PM +0200, JORDI PALET MARTINEZ wrote:
> Definitively if that happens to me in EU, I will not provide passwords
> even if I don=E2=80=99t have anything to hide, but just because custome=
r=E2=80=99s
> info confidentiality, signed NDAs, etc. I don=E2=80=99t think that will=
 bring
> me to the jail. However, in US, detention is a fact, right?

It's not.  If you're a U.S. person (citizen, national, or permanent
resident) you cannot be refused entry on account of refusal to provide
passwords to your devices (though, if Customs believes you're carrying
contraband and has sufficient probable cause you might be charged and
arrested, but failure to provide passwords alone is insufficient).  If
you're NOT a U.S. person you may be refused entry, but cannot be
detained indefinitely, and you cannot be refused the right to go home.

The reports of harassment are worrisome, and even more so reports that
lack of devices, or having clean devices, is taken as suspicious.

Employees of many companies simply can't carry non-clean devices if
*credentials* compromise at borders would have negative consequences for
them.  But if carrying clean devices (or no devices) can lead to denial
of entry, then why bother going at all?

All that said, I've been harassed by Customs in Japan and Canada, and I
have heard harassment stories in Argentina (where I hail from) and
elsewhere.  My impression and experience is that Europeans customs are
the least likely to harass visitors.

Nico
--=20


From nobody Tue Apr  4 11:43:17 2017
Return-Path: <andy@hxr.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23FC129498 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 11:43:15 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.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 7G5RM-lkvIOU for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 11:43:14 -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 3694412426E for <ietf@ietf.org>; Tue,  4 Apr 2017 11:43:14 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id d2so40865318oig.1 for <ietf@ietf.org>; Tue, 04 Apr 2017 11:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N4sV0DASMeHwn88DUc+36lCOUM9XEbFK71Bk9tRmAcs=; b=1zgkVGtcUX5JSuKIxvbCTicz8HT/isMOVQuhOehIgnGilYb7S5z+pFNA8PMwH1aBYF fQn0oMI/bCbHU7p4kdB7gRwdmjG57bGAeMRrpS/JTm/bFGXWudEibXUrVrH7YdnAzeNU qEJr7zu7gnb46ExjZn63XmOJCKs4juYHfrMW5lwJ7EV2xlZmF00FlY0RSsCTPYk12vRx XgdkPwICpmfOxTUbamur5zjyhTtXRgJeHDz2wQIiEuEHAg6VW/OX52SzDYV+mLe1uwzx bn+V2RRwhLfyWebTeFsCAb65MLpIEBCSb8p3SrE6yFWRl8C/u10LYl/3xTlygVbMNKkW 7qtA==
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=N4sV0DASMeHwn88DUc+36lCOUM9XEbFK71Bk9tRmAcs=; b=Ol7quAy/uuIp0tqIvZNqSRvDEE083EV8WbjBzw46EedXYvDpfQZ9NwAm35rZD8Cet5 RabfAmqGp8HfyYMbgTe96ib6KwBnWnMZx21vDnRiv5MSavXBixl9E4KQbxIgJhaxVUhf Yi8VV0QKYJbAaWvIN2CjngCnG5vaLUKZJNZCFXyCZq8gfupeQ0P2Bspg1pEQs6A+k66F 1Q1xt6yxGsDPcbG8QaAh6u8LkI+dvNoJFioiHgU6uXXQN2Nngie+U4RN1HEIol2DjFo7 feTaa0ZbYC0lizwLK8IXCLGLTIdmEtvthQZR6DJqCPbWKAnUwLSlMyMmlLAlCeRvCqTe 2GaA==
X-Gm-Message-State: AN3rC/4bI9i9fWVTFnw22TwdshYZVI4dxLy1ocEsWy9/k7aTCwdu7iEZdwrmt1gEeTBVqJncWoUCF6n7KxE4OA==
X-Received: by 10.157.60.231 with SMTP id t36mr141901otf.193.1491331393457; Tue, 04 Apr 2017 11:43:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.30.132 with HTTP; Tue, 4 Apr 2017 11:43:12 -0700 (PDT)
X-Originating-IP: [192.252.241.5]
In-Reply-To: <20170404181505.GA4004@localhost>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost>
From: Andrew Newton <andy@hxr.us>
Date: Tue, 4 Apr 2017 13:43:12 -0500
Message-ID: <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Nico Williams <nico@cryptonector.com>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GUHlXqPZqGfpajSdOSxBqkb8LzA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 18:43:16 -0000

On Tue, Apr 4, 2017 at 1:15 PM, Nico Williams <nico@cryptonector.com> wrote:
> All that said, I've been harassed by Customs in Japan and Canada, and I
> have heard harassment stories in Argentina (where I hail from) and
> elsewhere.  My impression and experience is that Europeans customs are
> the least likely to harass visitors.

If we are going to base our decision on anecdotal experiences, my
worst encounters have all been in Europe. I don't think that means
anything other than my worst encounters have an an odd pattern. I also
know people who have been detained and denied entry into Canada
because the Canadians believed them to be violent criminals. They
weren't, but because the Canadians have arrest records but not
conviction/acquittal records from other countries there tend to be
misunderstandings (btw, the US does this as well, not picking on
Canada).

In my opinion, statistics will better inform this discussion.

-andy


From nobody Tue Apr  4 13:29:28 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61D91294F7 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.295
X-Spam-Level: 
X-Spam-Status: No, score=-4.295 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, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 dLczUFZ-5iUo for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:29:25 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DF32127419 for <ietf@ietf.org>; Tue,  4 Apr 2017 13:29:25 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTP id AD0A4A00400B; Tue,  4 Apr 2017 13:29:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=7Lo4/ZHAuOJqVi KkwBY1L9hlkYo=; b=EcnPZtyIWrlI58L7iGJlV2Eg987DLP+InJfn2R6H/0CZTl mm020eVpjM2vXCmGjZn4Bh+tOx4tXiv6NZqYnMaBy9xUe6XK+mwws4MHciX09yqb +pnlF/02X2M6nxpHCZXGnWASAeYIYWOU6aZv4iBt7ouHaAzb+LPV2ow1005Ow=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTPSA id 2B0D9A00012B; Tue,  4 Apr 2017 13:29:24 -0700 (PDT)
Date: Tue, 4 Apr 2017 15:24:47 -0500
From: Nico Williams <nico@cryptonector.com>
To: Andrew Newton <andy@hxr.us>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404202446.GB4004@localhost>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oup6vWulqCAJAkP28etto6S7ajU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 20:29:27 -0000

On Tue, Apr 04, 2017 at 01:43:12PM -0500, Andrew Newton wrote:
> On Tue, Apr 4, 2017 at 1:15 PM, Nico Williams <nico@cryptonector.com> wrote:
> > All that said, I've been harassed by Customs in Japan and Canada, and I
> > have heard harassment stories in Argentina (where I hail from) and
> > elsewhere.  My impression and experience is that Europeans customs are
> > the least likely to harass visitors.
> 
> If we are going to base our decision on anecdotal experiences, my
> worst encounters have all been in Europe. I don't think that means
> anything other than my worst encounters have an an odd pattern. I also
> know people who have been detained and denied entry into Canada
> because the Canadians believed them to be violent criminals. They
> weren't, but because the Canadians have arrest records but not
> conviction/acquittal records from other countries there tend to be
> misunderstandings (btw, the US does this as well, not picking on
> Canada).
> 
> In my opinion, statistics will better inform this discussion.

My unstated point was that the US border situation is not really
different from anywhere else.  YMMV.  Stats would be nice, but I suspect
there are no reliable stats available, though individual organizations
like the IETF can probably track how many of *its* participants are
harassed at the various countries where it has held conferences.

Perhaps the IETF could gather and publish such statistics going forward.
Though given the relatively fickle nature of border enforcement (I
imagine it tends to be reactive as well as proactive, so recent events
probably tend to affect policy), stats may not be terribly predictive.

Nico
-- 


From nobody Tue Apr  4 13:43:06 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068D9126E3A for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 tuuMkospXO0e for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:43:02 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F3A12441E for <ietf@ietf.org>; Tue,  4 Apr 2017 13:43:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A0C3CBE55; Tue,  4 Apr 2017 21:42:59 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8-S8pxximiI; Tue,  4 Apr 2017 21:42:58 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 237A1BE38; Tue,  4 Apr 2017 21:42:58 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491338578; bh=/zMykysDA2LJ4izeY8Pq9MQUJcs+GK9SRcvBooZSvO0=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=gDByk6hSrTsAegbifevdmxW6IeL2nGiEaeG+TgfhJOSG8NfEZxzPlSNVgoCZnW1M2 zHFRZWC4WLNkPhvXZN1XaDjT82Ti7ZODFAAJ7cHAWqIE4D6/1VWR+ZGP1Mv80gMyKe ivzoiiQm62USVQjNJ+6ihKl6uHJ5UMFAJTVZ/y0c=
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Nico Williams <nico@cryptonector.com>, Andrew Newton <andy@hxr.us>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
Date: Tue, 4 Apr 2017 21:42:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170404202446.GB4004@localhost>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w6EO9HOl9Pp3N57859VlbxbDesN9Jtnqx"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jW4hZNAdXsGXOVDGQLOw_tIPW-Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 20:43:05 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--w6EO9HOl9Pp3N57859VlbxbDesN9Jtnqx
Content-Type: multipart/mixed; boundary="RbfS41p6AAdUMIdGmBvWn4Rgo7ddIf35s";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Nico Williams <nico@cryptonector.com>, Andrew Newton <andy@hxr.us>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
 <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
 <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
In-Reply-To: <20170404202446.GB4004@localhost>

--RbfS41p6AAdUMIdGmBvWn4Rgo7ddIf35s
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Nico,

On 04/04/17 21:24, Nico Williams wrote:
> My unstated point was that the US border situation is not really
> different from anywhere else.

I disagree. I think that as of now, of the places in which
we're likely to have face-to-face meetings, the uncertainty
with respect to rule-changes involved in future US meetings
is much higher than other places. Again, that's only in terms
of places in which we're likely to meet in the next N years.
That's a mega-negative for US-based meetings IMO.

S.


--RbfS41p6AAdUMIdGmBvWn4Rgo7ddIf35s--

--w6EO9HOl9Pp3N57859VlbxbDesN9Jtnqx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY5AVRAAoJEC88hzaAX42iyBsH/RWCk3CupcXKd5L+sVj9zs0y
93N+16VlI3QY0dbXdNBKM4fvJKrbWxx1C9k4wbgsGOKMAJC5e5grGXKql++BC94j
k7w/QSfvUfoKDI5zku7YAQSKtGjqGene/10kd0cdY5qgSPQQgLl7Iwf3izsUf4e5
+oPyRDb/aIaZHbNccl+zaPBztEaJAmJxkhT5KQ9m07IxVuUPZoHVevkHJjO1J8ID
IZm1eLyhWdYvAGHlY7mKrU2zL0HShWBIvt7406RKxASIEv2agdB3nqCNd00Gw6RQ
Bl2ffOCLiFhimGHu7da5mP4OjC5WJl2bOXiOkHwrTE1z0iItLfvG8kBUytWkiYk=
=n9Ka
-----END PGP SIGNATURE-----

--w6EO9HOl9Pp3N57859VlbxbDesN9Jtnqx--


From nobody Tue Apr  4 13:46:19 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBFC9129434 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 S2xRvNl7-wOM for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 13:46:17 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 720C6126E3A for <ietf@ietf.org>; Tue,  4 Apr 2017 13:46:17 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id 3487F540B31; Tue,  4 Apr 2017 16:46:17 -0400 (EDT)
Date: Tue, 4 Apr 2017 16:46:17 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Nico Williams <nico@cryptonector.com>, Andrew Newton <andy@hxr.us>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404204617.GC16732@puck.nether.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RF6kHWtkIfq6VsRylC5n5X_LFLU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 20:46:19 -0000

On Tue, Apr 04, 2017 at 09:42:57PM +0100, Stephen Farrell wrote:
> 
> Hi Nico,
> 
> On 04/04/17 21:24, Nico Williams wrote:
> > My unstated point was that the US border situation is not really
> > different from anywhere else.
> 
> I disagree. I think that as of now, of the places in which
> we're likely to have face-to-face meetings, the uncertainty
> with respect to rule-changes involved in future US meetings
> is much higher than other places. Again, that's only in terms
> of places in which we're likely to meet in the next N years.
> That's a mega-negative for US-based meetings IMO.

	I welcome the data that is being collected vs all the
armchair responses.

	This reminds me of the IPv6-only question, there's the
zero users that were on the IPv6-only ssid in chicago.  This may
be a real issue, or not.

	I think the thread can end until the data is reported
and we can then provide our commentary on that.

	- Jared

-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.


From nobody Tue Apr  4 14:03:15 2017
Return-Path: <andy@hxr.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEE21126557 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:03:13 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.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 9frQ6qYapA_X for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:03:12 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 BA6411294F5 for <ietf@ietf.org>; Tue,  4 Apr 2017 14:03:11 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id f193so178263352oib.2 for <ietf@ietf.org>; Tue, 04 Apr 2017 14:03:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gAXOoxLzVhG7QeHJmeBEPMKXYlpYbTpkd85p1x1WgM8=; b=MYSpW04V0Sn/uvidy5reSERbaz63sg9je+9nRrxGs2yTkCjKCzBSW63zxtMefUrsRM 9dbScwradOeg84gENo86YQkl1nOx3HydPhy9uri0dmoOKWliob1SnojerRTVusfVp4y3 5zzF5r9mQfqPDzWqq9LkUOgbN+Ps8UFLKBpVpKt2W+iw8s/E0JVAAuAdIupfOnbaJfhS +OgSuyswdPtzuUbjwdkWpYhIVzRr0MXvxc05N4q8v3JmBF+Ut/SVXdQ3BI+/VPyPBRzT ksUg+OgemeROQsJLwMztC3nFbCN73iSNIoKZR2mfyE7DstRCsjgVwTleE/21o/7God/A 8CWw==
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=gAXOoxLzVhG7QeHJmeBEPMKXYlpYbTpkd85p1x1WgM8=; b=lEax7nqdJLHCG9O6dZ0DaUt/nQbzsI7RbljDyBj4+xjaryM5yECsjfwBqJBToW3d24 R/I9NYwRtgog1tY1nmtWDUGOn/lcks9Hv5R8SVPnQmaHoCeQwFlwM31PGiUzM0udIvgT V2Ww0OwHt+C3sssYehDCjhfmGRbADgOHywVW1N4nJ3A2i5xCLNw85hwMY1wMjquz8z5U uevjUBeEKQJAIwSDDMSoO0e3Wn3dSS4RTulimdFrNP3D9eNO3bpft6o1+KzG/5AmQHLh d22GCwjkScwxVFuDYu9vKnVO0bxXsyaOXDcbNr4hjKsUCh9bA3Xmt30z1H115qawHTBc yxtQ==
X-Gm-Message-State: AFeK/H1TH8M+Mwy/bd3h0fACJyGP4yjmuJB8sZq+acDsAQuI/oWgC14HsjM3TvjkeZvbXkIQs9JJyPIljTfiCw==
X-Received: by 10.202.52.70 with SMTP id b67mr6362908oia.82.1491339790987; Tue, 04 Apr 2017 14:03:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.13.45 with HTTP; Tue, 4 Apr 2017 14:03:10 -0700 (PDT)
X-Originating-IP: [192.252.241.5]
In-Reply-To: <20170404204617.GC16732@puck.nether.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net>
From: Andrew Newton <andy@hxr.us>
Date: Tue, 4 Apr 2017 16:03:10 -0500
Message-ID: <CAAQiQRdL+QUNzKG_rLMiv+7_ZiUNCMKix=DpKMN=QQPrHi+E_w@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Jared Mauch <jared@puck.nether.net>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Nico Williams <nico@cryptonector.com>,  IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2XzflXnZAOFsRFDggwN5gEmH97g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 21:03:14 -0000

On Tue, Apr 4, 2017 at 3:46 PM, Jared Mauch <jared@puck.nether.net> wrote:
>         I welcome the data that is being collected vs all the
> armchair responses.
>
>         This reminds me of the IPv6-only question, there's the
> zero users that were on the IPv6-only ssid in chicago.  This may
> be a real issue, or not.
>
>         I think the thread can end until the data is reported
> and we can then provide our commentary on that.

I agree with Nico and Jared on this point.
-andy


From nobody Tue Apr  4 14:11:58 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACAD5129564 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:11:56 -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 mLSvhsWk6tjl for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:11:55 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::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 CD1C212778E for <ietf@ietf.org>; Tue,  4 Apr 2017 14:11:54 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id w43so43755436wrb.1 for <ietf@ietf.org>; Tue, 04 Apr 2017 14:11: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=C+U4MKhwEW5DJWOmdAa4nDi0UM2IDf+TDMFZjg1Glgc=; b=boMXnOpHqtX68At1OAOLIt8VmGMPThI4p9C8L7Tee2HrYIJgt6Kjqg7BljOJ0TgQ+8 zxK4bYJgvohEsA/BFBIHsrt03PXJXLPS4pLyFYUcMR0N/DwJ57ZDaAIeb1tZS0U7c61C bv2vvyEHUOQDX3Uao7fOWaGr8ov5QIB9GM7zdOEtmrUe463E2oYdl5iz0vqnepXgIOXz fiJX0G7aLwT2eX4j4N6QyXGfNu73EUd5aoP5PvjAHBgCr/r4wYZTheOuYioRWjEQX4XA 9DZ/W2EgMcqPRCfW5Vc73ySfMEYNNk0+KUE7cxuaomWZK3/Fx3SdiY1rnTlDXMZZLsZr 3neA==
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=C+U4MKhwEW5DJWOmdAa4nDi0UM2IDf+TDMFZjg1Glgc=; b=odEOPt8Cr3Hf+tJK8BP/MvyIEHuUWtaHG9wxjabqcnovtC4iTYakVNEheqh/BUnWyP ka9a23xvte5EzQTC/OuRevN63ryB7tpZnNQBeRx/rq1YjuNbCZ0NEQbcdv4L/81cty2C 9eoX3GijZZJgmND/BBYa1xmHMfve1noSiyIQAU8d3p0Cyes3PSAsTLKKoFHGppwSb2Tn AI+6I9W6jx/t/nrMNh1tZiXzV3qh3DbPukc+tWCPFJpCsDxPMWMowZnaQKZnwtsbqHjI PRdCyaakvQAESEup8CzDr+pCl8LX7wL1hXZntPXLWKzThd1lxCDBg45pZWCUwpefGkci 48fw==
X-Gm-Message-State: AFeK/H1PZomW3dw2VZQLx7IQe2EvV37Hr6cG2Xq9XrwYSIbsMo7nRavO3sRwDSZXa32tag==
X-Received: by 10.223.166.170 with SMTP id t39mr18402611wrc.44.1491340313397;  Tue, 04 Apr 2017 14:11:53 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id v186sm19776464wmv.2.2017.04.04.14.11.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 14:11:52 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_09B2C8BF-DCE5-4A7A-AC19-19012488DF0B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Wed, 5 Apr 2017 00:11:49 +0300
In-Reply-To: <20170404204617.GC16732@puck.nether.net>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Jared Mauch <jared@puck.nether.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9xcAAeUR5Lm2zFKeyDmdB0xcUrs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 21:11:57 -0000

--Apple-Mail=_09B2C8BF-DCE5-4A7A-AC19-19012488DF0B
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F32F1931-8526-41EC-B37B-16BF61ADF738"


--Apple-Mail=_F32F1931-8526-41EC-B37B-16BF61ADF738
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 4 Apr 2017, at 23:46, Jared Mauch <jared@puck.nether.net> wrote:
>=20
> 	I think the thread can end until the data is reported
> and we can then provide our commentary on that.

There is not going to be data. There are going to be the results of a =
web questionnaire filled out by a self-selected sample.

Heavily biased data is not necessarily better than anecdote and =
conjecture.

Yoav


--Apple-Mail=_F32F1931-8526-41EC-B37B-16BF61ADF738
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<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; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 4 Apr 2017, at 23:46, Jared Mauch &lt;<a =
href=3D"mailto:jared@puck.nether.net" =
class=3D"">jared@puck.nether.net</a>&gt; wrote:</div><div class=3D""><br =
style=3D"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;" =
class=3D""><span class=3D"Apple-tab-span" style=3D"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: pre; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">	</span><span style=3D"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; float: none; display: =
inline !important;" class=3D"">I think the thread can end until the data =
is reported</span><br style=3D"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;" class=3D""><span style=3D"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; float: none; display: =
inline !important;" class=3D"">and we can then provide our commentary on =
that.</span><br style=3D"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;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">There is not going to be data. There are =
going to be the results of a web questionnaire filled out by a =
self-selected sample.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Heavily biased data is not necessarily better than anecdote =
and conjecture.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Yoav</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_F32F1931-8526-41EC-B37B-16BF61ADF738--

--Apple-Mail=_09B2C8BF-DCE5-4A7A-AC19-19012488DF0B
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-----

iQEcBAEBCgAGBQJY5AwWAAoJELhJCxUKWMyZaDkH/iMH4FCVHAiSRjZlPGzL9PCn
i8QrOoRz6bPS0CpcHyioeA+Pxc5CjZBvzD8Z1T+I0+pFSa564H+Fm1Qlm1n7yJIE
n2UBsOx6lGJ/w7ZBQEmat1I51kfw9UnCChTl0CJP8hEm0EWI00i86fkuIVTmu9CO
Rsp9LboZR32LO0hHGnU7qz1ajdpkFnT5u22y960OWM5Yg3kQTbonxftiXXoW5m2U
1Qm5mQbVboYWwQY+FsEmIwdbm7I2wxbJB8nCQFzU7W/J158ERddxNywMHyLvjdji
OVfgTOJmDeUCaI/XNP3BsMU/NkvOuUxQPsbQ42ASkzDXtHks+8rbUccIWgrT5VQ=
=A7+8
-----END PGP SIGNATURE-----

--Apple-Mail=_09B2C8BF-DCE5-4A7A-AC19-19012488DF0B--


From nobody Tue Apr  4 14:13:17 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78CB01296C4 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:13:15 -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, RCVD_IN_DNSWL_MED=-2.3, 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 4pnDodCSHez0 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:13:13 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 05DDE126DFB for <ietf@ietf.org>; Tue,  4 Apr 2017 14:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v34LCpwf020191; Tue, 4 Apr 2017 23:12:51 +0200 (CEST)
Received: from client-0157.vpn.uni-bremen.de (client-0157.vpn.uni-bremen.de [134.102.107.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vyMBV63HkzDHMn; Tue,  4 Apr 2017 23:12:50 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
Date: Tue, 4 Apr 2017 23:12:48 +0200
Cc: Nico Williams <nico@cryptonector.com>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
X-Mao-Original-Outgoing-Id: 513033168.039044-128005f8269c85a6276f4a87de6cb870
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
To: Andrew Newton <andy@hxr.us>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yjxcB-sXONTbe07YK8D-ZXHDye8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 21:13:15 -0000

On Apr 4, 2017, at 20:43, Andrew Newton <andy@hxr.us> wrote:
>=20
> In my opinion, statistics will better inform this discussion.

Statistics is useful for reasoning about stable countries.

(It may also be useful to remember that the US is unsafe beyond its =
borders.
Chicago has the murder rate Colombia had in 2013, before the peace =
process fully set in.
Statistically, the chance of any IETFer being killed last week was about =
1.5 %.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr  4 14:15:31 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D0C129510 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:15:30 -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, 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 Ci4w3FlnpRZt for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:15:28 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 5299A1294F5 for <ietf@ietf.org>; Tue,  4 Apr 2017 14:15:28 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v34LFQKA012906 for <ietf@ietf.org>; Tue, 4 Apr 2017 17:15:27 -0400 (EDT)
Date: Tue, 4 Apr 2017 17:15:26 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404211526.GA25253@gsp.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170404202446.GB4004@localhost>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TqQlt4S64gqXhCK3HIVYSaVTLNg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 21:15:30 -0000

On Tue, Apr 04, 2017 at 03:24:47PM -0500, Nico Williams wrote:
> Stats would be nice, but I suspect there are no reliable
> stats available [...]

There aren't, because FOIA requests attempting to learn them have not
been answered.  And that's why there's now a lawsuit filed by the
Knight First Amendment Institute at Columbia University against the
US DHS and ICE:

	https://www.documentcloud.org/documents/3525562-Complaint-03-27-2017.html

However, any number of organizations, e.g., the EFF, the ACLU, etc.,
have independently noted the recent sharp uptick.  In addition, the Wall
Street Journal is reporting today that a new set of procedures under
consideration will include demanding the phone passwords from *all*
foreigners entering the US.

---rsk


From nobody Tue Apr  4 14:56:56 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF49129771 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 Ze6nckFVEIzd for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 14:56:45 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9635129721 for <ietf@ietf.org>; Tue,  4 Apr 2017 14:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3439; q=dns/txt; s=iport; t=1491343005; x=1492552605; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=qedPnj5rRvyTsDbpKI9oMnFl8KnwfKPegOjLCv3mirw=; b=l/LCH6ybVR4RPm8C7peGptdoGZgde0shD7u7BZ7JMQq0su5Qfm3kGZRH uCs/i8eBMII5ExNhSwk1LY3AJ6iA+FyYVdDxmNVc9Itk612dvaDkYxdhh MtvXntj+pnGLTP4wYdxY3oRsJdf+YUBs9eJbn5o0xai0s/gEGEjbEBqBs 8=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DFAQBVFeRY/5JdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1RhhG6KEpFblVOCDi6FdAKDQz8YAQIBAQEBAQEBayiFFgEFI1Y?= =?us-ascii?q?QCxgqAgJXBgEMCAEBFol0Dq0mgiaKaQEBAQEBAQEBAQEBAQEBAQEBAQEQCgWIU?= =?us-ascii?q?4Jqh1qCXwWcbYN8ggyMSIF9iGQjhjiTdR84gQUlFggYFYUaHYFlPolQAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,276,1486425600";  d="asc'?scan'208";a="218466540"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2017 21:56:44 +0000
Received: from [10.86.249.69] (bxb-vpn3-325.cisco.com [10.86.249.69]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v34LuguD025187; Tue, 4 Apr 2017 21:56:43 GMT
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Jared Mauch <jared@puck.Nether.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
From: Eliot Lear <lear@cisco.com>
Message-ID: <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
Date: Tue, 4 Apr 2017 23:56:42 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170404204617.GC16732@puck.nether.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xLI0CHWIFkqkrW9crpB2xbtGdMrIKVGcL"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GNkAxXeaw2iR62crx00SBw0hNfU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 21:56:48 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xLI0CHWIFkqkrW9crpB2xbtGdMrIKVGcL
Content-Type: multipart/mixed; boundary="oAx2N7koUX9MtIAPlCKLJRKnkp427ODsd";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Jared Mauch <jared@puck.Nether.net>,
 Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
 <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
 <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
 <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
 <20170404204617.GC16732@puck.nether.net>
In-Reply-To: <20170404204617.GC16732@puck.nether.net>

--oAx2N7koUX9MtIAPlCKLJRKnkp427ODsd
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Jared, man, read the newspapers.


On 4/4/17 10:46 PM, Jared Mauch wrote:
> On Tue, Apr 04, 2017 at 09:42:57PM +0100, Stephen Farrell wrote:
>> Hi Nico,
>>
>> On 04/04/17 21:24, Nico Williams wrote:
>>> My unstated point was that the US border situation is not really
>>> different from anywhere else.
>> I disagree. I think that as of now, of the places in which
>> we're likely to have face-to-face meetings, the uncertainty
>> with respect to rule-changes involved in future US meetings
>> is much higher than other places. Again, that's only in terms
>> of places in which we're likely to meet in the next N years.
>> That's a mega-negative for US-based meetings IMO.
> 	I welcome the data that is being collected vs all the
> armchair responses.
>
> 	This reminds me of the IPv6-only question, there's the
> zero users that were on the IPv6-only ssid in chicago.  This may
> be a real issue, or not.
>
> 	I think the thread can end until the data is reported
> and we can then provide our commentary on that.

How do you gather data when the circumstances are changing day in and
day out?  Here's the latest fun.

https://www.theguardian.com/us-news/2017/apr/04/trump-extreme-vetting-vis=
itors-to-us-share-contacts-passwords

The implication being that someone could be turned away at the border
based on private political views.

Eliot




--oAx2N7koUX9MtIAPlCKLJRKnkp427ODsd--

--xLI0CHWIFkqkrW9crpB2xbtGdMrIKVGcL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY5BaaAAoJEIe2a0bZ0nozzWEIAIzOrniEfluga0pZuk7Ke1Wv
vPKCr5kcG0YRsGnq2JBhwEUHuj+CTZ37sxn3Au9nIlA5qzfMtFeJ/exjVpdv7gWn
575iOzAdDk0Yd9dEBZAh/AMHIVqo2lj5/w3PIYUlhI17tWFi8uu16a9ygM6FbznR
5LMT+/8iNfza1OlzLgZD6ykH7umRWSaL2kcE5x7tHT50EBIJMSIKxZb4Et/GGdLK
V2K9KScs4v+Wja7RR4DGHvxoqofzQ7Il/OqASXP8gEJoV56DiGdb8cE6CSmBTWvc
4eZdhYDV/R/d6sXHdD66dp2yMIjEiYMuyZzfd0VH+HXjlouZ/N45xNt0hY4umDQ=
=jEDH
-----END PGP SIGNATURE-----

--xLI0CHWIFkqkrW9crpB2xbtGdMrIKVGcL--


From nobody Tue Apr  4 15:15:20 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F9C1293E0 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level: 
X-Spam-Status: No, score=-4.296 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, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 zomS6TO1aiHJ for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:15:17 -0700 (PDT)
Received: from homiemail-a34.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B856A1270AC for <ietf@ietf.org>; Tue,  4 Apr 2017 15:15:17 -0700 (PDT)
Received: from homiemail-a34.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTP id 24779A004F17; Tue,  4 Apr 2017 15:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=TiXTXhvLLv2NXl F2bSowBIaiV0s=; b=dNQxh0Uotp7f0WeF3cdWgTrJF1bCI7tV3Lh+Yj1usKaBhi qL51LFJmig7di66ZSXNJqXGskiwpow7NvjBLVbidBIK6Cl7GLYjVDLdXTd3EnSpv rvCx6n7yGxqMgLVK81Nse2liGL5TGw7gHxrTT/JphOMKIdjEQgs/0biteIuKY=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTPSA id 8C1A9A004F15; Tue,  4 Apr 2017 15:15:16 -0700 (PDT)
Date: Tue, 4 Apr 2017 17:10:42 -0500
From: Nico Williams <nico@cryptonector.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: Jared Mauch <jared@puck.nether.net>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404221042.GC4004@localhost>
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yP1vZaVY4dSLT_ckZFvpOsN2JNM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 22:15:19 -0000

On Wed, Apr 05, 2017 at 12:11:49AM +0300, Yoav Nir wrote:
> There is not going to be data. There are going to be the results of a
> web questionnaire filled out by a self-selected sample.

When an IETF participant is turned away at some border, or has their
devices inspected, or is presented with demands for their passwords,
they should inform the IETF so that the IETF can count such incidents.

I suppose a participant could be told not to tell, but it's very
difficult to ignore absence.  At the very least it should be possible to
count entry denial events.

I do suspect that the U.S. will be a more difficult location for more
attendees than other locations.  Certainly the news we all see is not
encouraging as to hosting IETF meetings in the U.S.  This I don't deny.
Though it's also possible that this is becoming a self-reinforcing meme
and that we're just not seeing incidents in other countries in the news.
In any case, the U.S. certainly does not have a monopoly on the border
harasment business.

Some people may wish to boycott the U.S. by refusing to host events
there.  There is some precedent for such a boycott.  For example, some
time back an obscure agency of the Texas state government decided to
guard its surplus budget by policing public drunkenness at hotel bars,
which led to a number of conferences pulling out of Texas, and the
ensuing bad PR led the legislature to rein in said agency.

However, at the scale of a state/province the politics of boycotts is
generally not partisan, but at a national/global scale it tends to be
rankly partisan, and boycotts may not be productive and may be divisive,
and should be approached with care.  Here "care" means: get some
evidence of negative impact on participation.  Reducing frequency of
U.S. meetings is not a boycott, and is something the IETF has been doing
for a long time anyways.  Further reducing that frequency in the short
term would be perfectly fine, though it would also reduce opportunities
for gather the stats we really need to make a sound, non-partisan
decision to boycott if the stats warrant it.

Nico
-- 


From nobody Tue Apr  4 15:23:58 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1B5126E01 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level: 
X-Spam-Status: No, score=-4.296 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, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 nsI0XT-dTKzV for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:23:55 -0700 (PDT)
Received: from homiemail-a34.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA3F5129693 for <ietf@ietf.org>; Tue,  4 Apr 2017 15:23:47 -0700 (PDT)
Received: from homiemail-a34.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTP id 67BFBA004F20; Tue,  4 Apr 2017 15:23:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=zPOqmOZiAK4tux nYeUtXyyKWwR0=; b=nT7iAb1Al91Rfb1SpXUlSnp9/HrDiKWqehytGMw7BGbU81 99DJqT6lU7TVhhP0kIClhpQ8Dpsxd5y30vnMbl6xTTxwfXj/aR2E6U9US5wleSce YDG5U3GfxECOZA4pcHP6fh2lzaRTJ93DPCgWr9A8tVIWi9ZWIjXl7Rz4+C/OM=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTPSA id ECBC6A004F1B; Tue,  4 Apr 2017 15:23:46 -0700 (PDT)
Date: Tue, 4 Apr 2017 17:19:13 -0500
From: Nico Williams <nico@cryptonector.com>
To: Rich Kulawiec <rsk@gsp.org>
Cc: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170404221912.GD4004@localhost>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170404211526.GA25253@gsp.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MP0okyOmZ9kLhhzZfp3YaNi6UiY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 22:23:57 -0000

On Tue, Apr 04, 2017 at 05:15:26PM -0400, Rich Kulawiec wrote:
> However, any number of organizations, e.g., the EFF, the ACLU, etc.,
> have independently noted the recent sharp uptick.  In addition, the Wall
> Street Journal is reporting today that a new set of procedures under
> consideration will include demanding the phone passwords from *all*
> foreigners entering the US.

*That* would be a huge deal.  I don't quite believe it likely to happen
though: it would require lots of new hardware and staffing to do
anything useful with every visitor's devices and password _and_ keep
entry bandwidth as high as today (_and_ keep tourism and business travel
to the U.S. from collapsing).

(I wouldn't necessarily mind traveling with a clean phone everywhere,
but the problem with that is that there have been reports where having a
clean phone has been used as rationale for sending the visitor back.)

If a country starts demanding access to and passwords for every
visitor's every device (and then making use of said access and
credentials) then certainly the IETF must avoid holding meetings in that
country -- not so much (or only) as a political statement, but (also) to
protect its participants.  Especially so if having a clean phone is then
considered suspicious enough to send participants back.

Nico
-- 


From nobody Tue Apr  4 15:34:04 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBBE126C7B for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 La4t6-UXrjYW for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:34:01 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id F1B2912878D for <ietf@ietf.org>; Tue,  4 Apr 2017 15:33:55 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:703e:63f5:b926:de50] (unknown [IPv6:2603:3015:3603:8e00:703e:63f5:b926:de50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 5780A540AD6; Tue,  4 Apr 2017 18:33:54 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
Date: Tue, 4 Apr 2017 18:33:53 -0400
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCD9A815-2A2D-4BDF-8BA6-E1420C436058@puck.nether.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
To: Eliot Lear <lear@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_qGdWTJ2iaqoAgmMMYmqtRQ5i1s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 22:34:02 -0000

Thanks. I do.=20

I wait to see what set of the IETF population actually reported an issue vs w=
hat you think the IETF population faces.=20

I happen to have been least inconvenienced by this meeting as it was within t=
he fly:drive decision radius.=20

Singapore (for me) will have the highest RTT as its 24h or so one way.=20

I'm aware of the overall trends and detailed issues that have transpired and=
 have family members who work for US CBP and am having regular contact with t=
hem.=20

Jared Mauch

> On Apr 4, 2017, at 5:56 PM, Eliot Lear <lear@cisco.com> wrote:
>=20
> Jared, man, read the newspapers.


From nobody Tue Apr  4 15:56:12 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B2F1271DF for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:56: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, 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 NgNcy_MupCax for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 15:56:08 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::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 AA031128CD5 for <ietf@ietf.org>; Tue,  4 Apr 2017 15:56:08 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id 81so164981773pgh.2 for <ietf@ietf.org>; Tue, 04 Apr 2017 15:56:08 -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; bh=edZSp0hLxqnsC+2MXM9IVu91VMGgx6SGZ4ANsAfSFNs=; b=dospXPuvtPsPXdd4BOAlkepvnpYScK4wVipfoSDIAuUuyy9aFfk207DDSs7YMs8n6N otVT/0cXbpEIaozcXvQliqkI4eDR+WbK/sLEEKJKOUSV9kHrHpGZ/D9qRHFt7ERTgEgF fP2uvhYyVhpVVjMeTq12pySUag0ZXzG0eS6XLh5oMPCbAa4LM9ijTWD3L9Fl6cEQe7jW EZvvOj8syTf2bgrQdogKjDgHsP0FiqQuIzNqIw57pKyWUWAjOGSIT5LRUaMA+4iUYAhH Nkg7xUdrS3M7Iut/Q2erMqh+P5kAs+Q16Vlir4d/D3F1qjkY2FRNnmf+HwEW3xOedZCi aZvQ==
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; bh=edZSp0hLxqnsC+2MXM9IVu91VMGgx6SGZ4ANsAfSFNs=; b=khj4oZjYPbY/rA/J5eZ8GiuYriJ/OPurYtTR7REgjLmEg1G64Gi/4/PfOutIq73oxk ouc33ham/V4MWUM6bAzK7bIhg2d27LcOP2lH1rTGH7iESQF9VD23vafVrCB8US9W0Ygb fcFj5J78QlcP52THWMpaY+WnhaXyysUbsMmzspxLhrEc/miKFyu55EvR5zJkK/4160B8 4uGQ3ls3RVTpcq1KlWpNKP+ZEdcNf4gVcbdgyXkJDZ+t3/rStAnqKl5hN0npg6iONgRx YbV4ToINSKwTSZlhY1mAQmGFIXN5Gw0ohc6hc8DbA3cNzW98b8dM/c8T2klbdXSuscYl iM5g==
X-Gm-Message-State: AFeK/H2G5HT0pejxJWt6UGSiDnKmNGxApw8Q0dLIL0dr73+2UKCORXvnuHqqLnkFY28D7w==
X-Received: by 10.98.201.77 with SMTP id k74mr25238977pfg.74.1491346567413; Tue, 04 Apr 2017 15:56:07 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-78-125-radius.dynamic.acsalaska.net. [63.140.78.125]) by smtp.gmail.com with ESMTPSA id y6sm22239870pgc.40.2017.04.04.15.56.06 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 15:56:06 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com>
Date: Tue, 4 Apr 2017 14:56:04 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MA8tXGw9cGpiwGo0Gd5sbLfJxjq1U62jh"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sn3kNGkFxlIxUTwM_DNN6UJgqPs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 22:56:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MA8tXGw9cGpiwGo0Gd5sbLfJxjq1U62jh
Content-Type: multipart/mixed; boundary="1WIJhuePiFjFovEmjrqw1m0K8f0wBgXFq";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: ietf@ietf.org
Message-ID: <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
 <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
 <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
 <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
 <20170404204617.GC16732@puck.nether.net>
 <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
In-Reply-To: <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>

--1WIJhuePiFjFovEmjrqw1m0K8f0wBgXFq
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/4/17 1:56 PM, Eliot Lear wrote:
> Jared, man, read the newspapers.

Well, there's certainly that (the Canadian paper, the Globe and
Mail, has done a lot of excellent work on tracking down incidents
where Canadians have had problems entering the US, as one example).

I think the broader problem is that there's just a lot of uncertainty
and inconsistency, and even if it were possible to collect an
authoritative list of incidents it wouldn't capture the problem that
many people crossing the border in and out of the US these days don't
really know what to expect.  It's one thing when you're not sure
whether or not your bag of dog food will be permitted in and an
entirely different one when you're not sure whether or not you'll
be turned back.

I don't know how to capture that uncertainty in a way that will
satisfy the skeptics but it does seem to me to be a very serious
problem with respect to planning.

Melinda



--1WIJhuePiFjFovEmjrqw1m0K8f0wBgXFq--

--MA8tXGw9cGpiwGo0Gd5sbLfJxjq1U62jh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQIcBAEBCgAGBQJY5CSFAAoJELiGRpM6HoEuuI8P/3T5Bzmc0DZn38y+1wfdVU9t
P8Gp3HRYRrUvW7bn3zA8cTt+bQr2DSeramY74AV9vfNN06lk5G1YWARYNh4llgG4
XHrW6HzXYIWlCKuccX4icoLCEIEgzpdKFojadEOdic61YrY1Lrfr5pUvJ3qUpvLN
GmTJgXWLjQ7vmUxgoFbUSSv67WI/qovPLUZFNNOTUCJU+F+XvQESmt5bn2m71qmV
8Ow03n7hXR9Z0DhZwWlLLqHPPzxOkszTQEDl8IZZ9L8fL5Wr3FubUNqcbvFd2FSH
mvvzg1xs14H3mmFoNWRgY1jcw9O3hOH1ACuMSJKteqpXRtfcUro+HACbgy4HxWSQ
PCMTXp3t758j6msYAyucqkpKmfW8OzrSfvJ2oGdnKOqetuFyiwVVsO/UE9fiu89E
3KMnAsTpyoWHkWf+vCL70cnKFBcb47p8JB+hnJOICFCwS1OKQeD4lIQvpYh1X5Ck
gmwvAfPrSMZzcGFg9bpwEqRjeCP7FHyeWrKpZap2+2S/wWnSQ/2bmuEyAB7uCaO3
Q4Ga03jyppfYuhc3DLctbeSDEeF11ftzbRPA3yN/G2I5zIw9y41lBqJ2ounYqlb0
Nwvdexd3rJ/so8kOzGFDH5XEvI9dht81nczZR2jfa/6hPrn4GJYVxd50WmToJdPn
nF943o969BtgFNA0jTXp
=ZfCZ
-----END PGP SIGNATURE-----

--MA8tXGw9cGpiwGo0Gd5sbLfJxjq1U62jh--


From nobody Tue Apr  4 16:06:46 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 361DA1270A3 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 6f-xjxw14ghl for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:06:44 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207: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 C74DE1292FD for <ietf@ietf.org>; Tue,  4 Apr 2017 16:06:43 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-11v.sys.comcast.net with SMTP id vXX2cLJbNT4XXvXX9cHSt2; Tue, 04 Apr 2017 23:06:43 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1491347203; bh=PtgaQe/pp4ruobmZfZdKc5OAypjAREjKwPdr/zdKsw8=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=FvO2dEBD5SH/EBuwx2B13LWO8KrLPT113wMZvtwv3mJQiDvxA6y7IF7dXgEaEqxTs f4mFy6QJCEjFOPImFs0AXht07bONZB7u98untCf2l9dTYbK+BzUVc++GOXUGm5d03b Q71rU49W8+ZBkmBQcUhBWjmAFCMqDuIEJcTVzyKcJF5eJ+5rFy3J2Aiqyji7F/usmm xS5XEwF5tu5c8mNF/Gq6SeyaDExeuF9tRPK9UAuls3hNcso3L4E6GMR4spyhkz6QP0 xoZUW8S6BS5klSrLO/xATBWRBTfzHFDS2Beyy+Vy5se/BhjVXlXJR9LLPIemVcV1J1 ruaboZmy+6tpw==
Received: from [IPv6:2607:fb90:136d:20e3:9973:b2f8:4249:5520] ([IPv6:2607:fb90:136d:20e3:9973:b2f8:4249:5520]) by resomta-ch2-08v.sys.comcast.net with SMTP id vXWnceO1ftZO6vXWscyzhT; Tue, 04 Apr 2017 23:06:39 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: IAOC requesting input on (potential) meeting cities
From: mike stJohns <mstjohns@comcast.net>
X-Mailer: iPad Mail (14D27)
In-Reply-To: <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org>
Date: Tue, 4 Apr 2017 19:06:20 -0400
Cc: Andrew Newton <andy@hxr.us>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-CMAE-Envelope: MS4wfPXH2dD+puAaiyduhqjcavA20Kdwjt+HXViPvAxCOYcEbUPP/ESVh8NfMdPQxWdUSSXRnK9/Lb4BG1dHNpqaV8DoawDQgIcHafemPMcvKDeJfI31VBP0 AOlpQ8EOQFO957oNz2jhSQSckkXAZxm8zWBRQokB5yutWLILTmQhRCjygsfMec1qkOoIObOcy8CqvgwqvLR4o5jRJQ6SsknAfeUzfMAt4/3ChF185o22ezYH Z4M6TRoxVDnJl73I4sO+T4QwE9LZEAidAOtxrtUltrY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p57nHl0Ucyj7xtKRGNs3iw1bl5A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 23:06:45 -0000

Carsten, you're off by very large factor.   The Chicago murder rate reported=
 last year was 27 deaths per 100000 for the entire year.   That works out to=
 be about .5 deaths per week per 100000 or .005 deaths per week per 1000( th=
e number of people attending the IETF) Or .0005% of the IETF population for t=
he week we were there. =20

I'm doing this math in my head while having a glass of wine so it's possible=
 I've dropped or added a zero or two but it is definitely not 1.5%.   It's w=
orse than it should be, but it's irresponsible to suggest that the level of r=
isk was that high. =20

Mike

Sent from my iPad

> On Apr 4, 2017, at 17:12, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>> On Apr 4, 2017, at 20:43, Andrew Newton <andy@hxr.us> wrote:
>>=20
>> In my opinion, statistics will better inform this discussion.
>=20
> Statistics is useful for reasoning about stable countries.
>=20
> (It may also be useful to remember that the US is unsafe beyond its border=
s.
> Chicago has the murder rate Colombia had in 2013, before the peace process=
 fully set in.
> Statistically, the chance of any IETFer being killed last week was about 1=
.5 %.)
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20


From nobody Tue Apr  4 16:35:13 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6DF128B44 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 N2V5nKoLWG98 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:35:10 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::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 50350127097 for <ietf@ietf.org>; Tue,  4 Apr 2017 16:35:09 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id r203so181719444oib.3 for <ietf@ietf.org>; Tue, 04 Apr 2017 16:35:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3p+d/exkH4mlpgc1V2jzBWduOXufW7Gz8eNnAlze/QU=; b=W3cUmxatmhqVId+Y22l1BiHeKSsnQgng17foiIy9SFvtEodjzXNfa+ywPday8qfGQJ kBz9vJLWN9gUzllK3734dJGqjAsnNKYU4NBMTwbHfPDRE386G+89A3JQ2hrtBf0lagTV 8M3+CDMv82suw4qoPFANWKfafV7VH4Jg3g0rA2/hJiiX7lO9RzjPgzNpCrIUsBz8jnXo fggkQs71CksPwTh2HSkyxs76xsX1Lm9UVbrKrBk57kAJOAGMZEKZi5jGK4eYUnDdcN4O hZsounBDlpVkfrx7hkZUTa6bxqdyCI1aNSJKMQ9zljaEbPSHYKE6ut8dZ5sJmhXN/iCt uqrg==
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=3p+d/exkH4mlpgc1V2jzBWduOXufW7Gz8eNnAlze/QU=; b=pyYnZzIJXhSZrCHdoK1VSXEEt+zhwwWzO1Lfem6niBYGaE2EtxZ8FQQpprT64SDmKY 5pq/3lcDDE5eFtV+rwginbmgMAykDLRIYEnBOILY6iQ4d2TrFBzJ1lIN9Wns8EvNaxag 9LAitutq+nNAAhluKU/CBAUJNPCU0uXzSOeRCw4hnE+8lNr+6bP/hysyI1cb2ziuaEnx /+DkS+rXyTsFE23Qxmy7iOUSj/+XnP8T4l/erFvhQcj+NhdoRSQd06QtDgUMiGe5EJ35 RiBjRmFifq6vYaFywQDwDBhiKy78AG6huEEcB9E7ndIEhAoW1EmcCL19i+mL4vZe5R++ qtIg==
X-Gm-Message-State: AFeK/H0qQAdPg5ENAP2o4mjc6yaQvr0sYIcwyJ8atouihcmq2jFfh6JZ7moqn58eyRd4wotb6euPvjV7+7Vy7Q==
X-Received: by 10.157.53.10 with SMTP id o10mr12682896otc.50.1491348908606; Tue, 04 Apr 2017 16:35:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.231.201 with HTTP; Tue, 4 Apr 2017 16:34:47 -0700 (PDT)
In-Reply-To: <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com> <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 4 Apr 2017 16:34:47 -0700
Message-ID: <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Melinda Shore <melinda.shore@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113e0e26ef1f08054c5fb91d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KtBFlo6X6EGHmEqvGNd57OeVidk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 23:35:12 -0000

--001a113e0e26ef1f08054c5fb91d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

At least once, I was questioned extensively when going from the US to a
meeting in Canada. I had to show evidence of the meeting and my itinerary
and convince them that I wasn=E2=80=99t entering Canada to take work away f=
rom a
Canadian. That said, I still support holding meetings in Canada.

Cheers,
Andy

On Tue, Apr 4, 2017 at 3:56 PM, Melinda Shore <melinda.shore@gmail.com>
wrote:

> On 4/4/17 1:56 PM, Eliot Lear wrote:
> > Jared, man, read the newspapers.
>
> Well, there's certainly that (the Canadian paper, the Globe and
> Mail, has done a lot of excellent work on tracking down incidents
> where Canadians have had problems entering the US, as one example).
>
> I think the broader problem is that there's just a lot of uncertainty
> and inconsistency, and even if it were possible to collect an
> authoritative list of incidents it wouldn't capture the problem that
> many people crossing the border in and out of the US these days don't
> really know what to expect.  It's one thing when you're not sure
> whether or not your bag of dog food will be permitted in and an
> entirely different one when you're not sure whether or not you'll
> be turned back.
>
> I don't know how to capture that uncertainty in a way that will
> satisfy the skeptics but it does seem to me to be a very serious
> problem with respect to planning.
>
> Melinda
>
>
>

--001a113e0e26ef1f08054c5fb91d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">At least once, I was questioned extensively when going fro=
m the US to a meeting in Canada. I had to show evidence of the meeting and =
my itinerary and convince them that I wasn=E2=80=99t entering Canada to tak=
e work away from a Canadian. That said, I still support holding meetings in=
 Canada.<div><br></div><div>Cheers,</div><div>Andy</div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Tue, Apr 4, 2017 at 3:56 PM, Meli=
nda Shore <span dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" =
target=3D"_blank">melinda.shore@gmail.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><span class=3D"">On 4/4/17 1:56 PM, Eliot Lear wrote=
:<br>
&gt; Jared, man, read the newspapers.<br>
<br>
</span>Well, there&#39;s certainly that (the Canadian paper, the Globe and<=
br>
Mail, has done a lot of excellent work on tracking down incidents<br>
where Canadians have had problems entering the US, as one example).<br>
<br>
I think the broader problem is that there&#39;s just a lot of uncertainty<b=
r>
and inconsistency, and even if it were possible to collect an<br>
authoritative list of incidents it wouldn&#39;t capture the problem that<br=
>
many people crossing the border in and out of the US these days don&#39;t<b=
r>
really know what to expect.=C2=A0 It&#39;s one thing when you&#39;re not su=
re<br>
whether or not your bag of dog food will be permitted in and an<br>
entirely different one when you&#39;re not sure whether or not you&#39;ll<b=
r>
be turned back.<br>
<br>
I don&#39;t know how to capture that uncertainty in a way that will<br>
satisfy the skeptics but it does seem to me to be a very serious<br>
problem with respect to planning.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a113e0e26ef1f08054c5fb91d--


From nobody Tue Apr  4 16:50:59 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10291129459 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:50: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 q6K5mgMG1lEt for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 16:50:55 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA477129453 for <ietf@ietf.org>; Tue,  4 Apr 2017 16:50:54 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id g2so163250132pge.3 for <ietf@ietf.org>; Tue, 04 Apr 2017 16:50:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=IxJksATFi9UKpEJ0zclyGJWsjktGmUuOdhTyCIIChVk=; b=X+F6oFr++7D+Pkl3ZRmFaFUjZSuy0HysVNkRFhcKBsbUwZ3UsqdvNir04DmV4Jy8pg 8nzE7lHmDAfzI7dnQY8jLYnqnU9MhnHSSosIQKaYRbhsVshV5swmM3zqVi7ip8HyX2II 9e974OU3kSrVz5s5n6k9azNieGLjU/P6bxtCX6uTegFHQGLtz2Oh47sefL8KU4u94eW0 1XRJGkQO6T6QWZHQ3oOCKazdSv0ItD0DWKLrPjzEKxktx0fcckEinMI3w8Mbnk/CYKQF LnGR+gaDzveVGyZhLaA5leFS+WA2Vp5F6YD86MsQyC59gfhQVrTsWrW4rgtWfyBdTuOF w5sQ==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=IxJksATFi9UKpEJ0zclyGJWsjktGmUuOdhTyCIIChVk=; b=HKSM46dyJEVRnc/YgBcH+Zk288dFi8PMSj9ilUtaFxUkMWff8mioic7kxWXLypv70A oKEQo2Tourt4o87ZCc+XhBBa91q9yqmfbvLF3xAHmgN46Pv1LK6lhpf7ZaqHBUxOqC+Z JNWSCSGNHZdtxlNw0uaW2EJjjUQ9GUNht4HR42b4/LucpgXbubUWLwh4tDiKDiQdxLO2 Ar2u+qVo1Xw2Sr8kFZig5eBjKNE0f7WpdFGg2speOWkM8Ob/lsnFTNhkZHdKAwKBxotj wGGigGKibGE940k8iXvlZDyn4z9vi22CDVhuIJgL/ufqoU70K5WettkFh/Etg+FEq+Nq tVGg==
X-Gm-Message-State: AFeK/H2Sda/qZtrBjfuYVT/hpowjlibjHgNMi6vL/5/xO1hvwW6hL33B0rwwVOFcrZhUyA==
X-Received: by 10.99.152.65 with SMTP id l1mr26559436pgo.59.1491349854217; Tue, 04 Apr 2017 16:50:54 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (209-112-132-193-radius.dynamic.acsalaska.net. [209.112.132.193]) by smtp.gmail.com with ESMTPSA id m4sm33629786pfi.74.2017.04.04.16.50.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 16:50:53 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: "Andrew G. Malis" <agmalis@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com> <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com> <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com>
Date: Tue, 4 Apr 2017 15:50:50 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Bq7WX57qPOGgf4jg9foR6iHRB4uqViIjL"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mh7G_6wNOY4gwCznyrtf9_KWw1o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 23:50:57 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Bq7WX57qPOGgf4jg9foR6iHRB4uqViIjL
Content-Type: multipart/mixed; boundary="1wNUmi6PSsi2jOUE4Ik4j5tUDNpivfMMo";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Message-ID: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com>
 <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com>
 <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
 <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
 <20170404204617.GC16732@puck.nether.net>
 <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com>
 <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com>
 <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
In-Reply-To: <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>

--1wNUmi6PSsi2jOUE4Ik4j5tUDNpivfMMo
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/4/17 3:34 PM, Andrew G. Malis wrote:
> At least once, I was questioned extensively when going from the US to a=

> meeting in Canada. I had to show evidence of the meeting and my
> itinerary and convince them that I wasn=E2=80=99t entering Canada to ta=
ke work
> away from a Canadian. That said, I still support holding meetings in Ca=
nada.

That's not comparable.  We know what the policy is concerning
Americans working in Canada, and that how you describe "meeting"
can affect whether or not it's considered to be work.  People
without the appropriate papers (whether it's citizenship, residence,
or a visa) are not permitted to work in Canada, period.  You should
know that before entering Canada.  (That said, I'm truly sorry you were
asked for evidence supporting the reason you gave for entering the
country).

Here, we're talking about uncertainty about whether or not Canadian
citizens (for example) will be permitted to enter the US based on
religious beliefs or (in the case of naturalized citizens) country of
birth.  Sometimes they are, sometimes they're not, and it appears to be
independent of any publicly-announced policy.  Similarly, US citizens
do not have the right to enter the US (that's not that widely-known,
unfortunately) and some citizens and green card holders have been
turned away or detained when trying to re-enter the US because of
their religion or country of birth.  This is not comparable to a
situation in which someone trying to enter a country is asked to
provide evidence supporting their assertions about why they're entering.

Melinda



--1wNUmi6PSsi2jOUE4Ik4j5tUDNpivfMMo--

--Bq7WX57qPOGgf4jg9foR6iHRB4uqViIjL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQIcBAEBCgAGBQJY5DFbAAoJELiGRpM6HoEuwukP/1Y06J59JLtZFff9BY4sQ4dI
z40/mlKXJxQQm1296CO9aU0GmIizmzgc78qxKpLmpea+s5VXzb7V7uQ1ir7PhU+H
QNcn1FP1bOcrNAGxkQut5cB5qjP/Y13h3P0dPpJ5g6m72LHORqyxNnVbRG3OEHa+
5lLjDpRmt4wsfoIlNtlH3r9TbysfitrsBlrvXWo00X+A0q5gl0A0HdzZGW0ZnTM4
6qquf7N9o94EqY1Z5HoM5kFr2Xz+rBSPojjGKlPoiv1iact7/S1Jrz4DX7zyweVQ
9xXdr1e0uEblIBizX1kGLdqUOrTW+AGF7PhL0bot+4n/HsSAevjjBAIKt+g293yi
myqTt/TmdtxT4zZYD54Kswg50iKnu5e+2Li2uHU29O2EclL34eVfKLegFYoYT5wK
WpDg6jqOMlhnQq6AZmFh75ZuoSpsl18daYunfdvTvQptQmESCLDV8v6rbX96LkiH
AywAUSo+o7iTjcFxiaMprYrHjRZPZOJFVcCXW/RliXw7EWNe/D9ytHaqZrccS0CS
w4Lswq3drLo6p1/D+Z4Dds204IHLbgSzqycNm4NA4Gpv4tE6IWzkD8XEDvyZ+ups
q0O+Oy5Pfo0O5To4fb4Y54KhvVExmohI5gr3FiczqXkdCzIPnGu7vt2yZYyS1Opp
K09qKFzZ29AjUEXbvcAh
=yVMl
-----END PGP SIGNATURE-----

--Bq7WX57qPOGgf4jg9foR6iHRB4uqViIjL--


From nobody Tue Apr  4 17:41:01 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6991294BD for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 17:40:59 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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=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 DVSr3PPfI9Re for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 17:40:57 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::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 8B4E312951E for <ietf@ietf.org>; Tue,  4 Apr 2017 17:40:57 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id o126so25822854pfb.3 for <ietf@ietf.org>; Tue, 04 Apr 2017 17:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=joSRX4U3Qdg6P9SLjSwC0M9zkJW1CUYFqWk3Z1UErOM=; b=VkI1LAZCtGs7sHnO2Ii2YC7N9WEiUM2Ae5QZdbUl4VWJ5mqOpEHEqPzrFsFa5Z4TwS gM293uBsMCxhdk9GMpalgRBb87OVvDsmlghI92DlSa681EAodrwXdy60epKmOIZFUIM0 zRhg2waY6/JixpINtlC/hl6S+QMXR2KiL6vTJSsi3HH8CJlvj8G0AqyuIyF5S412oe41 NbFr/3E2N61ub2Y2OdT2OziF9P4DSI0nGFHGKx9ES1gzF1AVPEv4UpYTC3ugdcDv+my2 M7FpHXkOTHFbZ1cX/2llKTbxpuUf1pvZ53EVQKCx3KRT+m4qF+02BCVeDczXdzEXe46p bp8w==
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=joSRX4U3Qdg6P9SLjSwC0M9zkJW1CUYFqWk3Z1UErOM=; b=Q86mnGmvx7IDBEntgJWbcPUfvsEGmofPHS+8eu+RvVK8JtRdVEktEhyLchrHYr46Ax MkSp8bINdRt06lla+dpuOSHSiyTSUBPh1Q/9UVFv37vU1rI1JDFdGW1iJzAnMf9tQsy3 OPJ6oojngoRGOvGTAPWBHRrCikcRenfGQiZoDqCg+wdLos0+/Q5PF4xBgNn2wIylQ99O g0OyGlBgpU1PQ5lFVQVc7dPhpz55kr39WJqytgQlR6ep7ivAfbK0OBVNng3lbQ7XlIcI cQlNlGW9D6cExu3oijBoTl2NCg+nfIPh62vvIOzOL4EoJQzFe/HD4BsZ1l78UU70sUaL 8t9g==
X-Gm-Message-State: AFeK/H1LzEMUNxtKXuUTrOwMKBbkDfmD1XqNI3S4rbxFcgchHGLs0ZTVjbRcrfslsCSjskYa
X-Received: by 10.84.143.195 with SMTP id 61mr33093970plz.46.1491352856855; Tue, 04 Apr 2017 17:40:56 -0700 (PDT)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id a5sm33741512pfh.124.2017.04.04.17.40.55 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 17:40:55 -0700 (PDT)
From: james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_83DD442A-FDA9-426D-B009-5CDD8CD23EDD"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Tue, 4 Apr 2017 17:40:54 -0700
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <20170403152624.GA11714@gsp.org>
Message-Id: <FAF82FC8-58AB-43AA-A094-280EA248E319@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-QxF8qtkycatoR4KLsan10irYeA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 00:40:59 -0000

--Apple-Mail=_83DD442A-FDA9-426D-B009-5CDD8CD23EDD
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Apr 3, 2017, at 08:26, Rich Kulawiec <rsk@gsp.org> wrote:
> 
> 	- if the data they provide access to will be retained


		- if the data protected by the password will be modified or deleted
		- if the software on the protected device will be modified or deleted


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_83DD442A-FDA9-426D-B009-5CDD8CD23EDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<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; -webkit-line-break: after-white-space;" =
class=3D"">On Apr 3, 2017, at 08:26, Rich Kulawiec &lt;<a =
href=3D"mailto:rsk@gsp.org" class=3D"">rsk@gsp.org</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"font-family: Menlo-Regular; font-size: =
11px; 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: pre; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;">	</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">- if the data they provide access to will be =
retained</span><br style=3D"font-family: Menlo-Regular; font-size: 11px; =
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-stroke-width: 0px;" =
class=3D""></div></blockquote></div><div class=3D""><br =
class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>- if the data protected =
by the password will be modified or deleted</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		</span>- =
if the software on the protected device will be modified or =
deleted</div><div class=3D""><br class=3D""></div><br class=3D""><div =
class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_83DD442A-FDA9-426D-B009-5CDD8CD23EDD--


From nobody Tue Apr  4 17:54:20 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 009591204DA for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 17:54:19 -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 DMMcIf99iRmN for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 17:54:10 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 120C412947B for <ietf@ietf.org>; Tue,  4 Apr 2017 17:54:09 -0700 (PDT)
Received: (qmail 33132 invoked from network); 5 Apr 2017 00:54:09 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 Apr 2017 00:54:09 -0000
Date: 5 Apr 2017 00:53:47 -0000
Message-ID: <20170405005347.39142.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BDOysfgREAS2MERjhfo4TbklHTs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 00:54:19 -0000

>That's not comparable.  We know what the policy is concerning
>Americans working in Canada, and that how you describe "meeting"
>can affect whether or not it's considered to be work. ...

But it's not consistent.  In nearly every case when I show up at the
Canadian border, show my NEXUS card and tell them I'm going to a
meeting, they wave me through.  One time when I got bored of the usual
route, I entered Canada via ferry on a rural island in the St
Lawrence, and it rapidly became obvious that I was the high point of
their week, as they wasted the better part of an hour searching my
car, getting all suspicious about the papers I had for a presentation
at the meeting, and even calling headquarters to see if I needed a
visa.

I agree that Canada is a fairly easy country to get in and out of
(unless you have a DUI arrest) but it varies a lot so anecdotes about
entering Canada or any other country don't tell you much.

R's,
John


From nobody Tue Apr  4 19:13:37 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE93120727 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 19:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 lI6O2dOHTvH0 for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 19:13:34 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 5D6CA1241FC for <ietf@ietf.org>; Tue,  4 Apr 2017 19:13:34 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id 725BA540BB8; Tue,  4 Apr 2017 22:13:31 -0400 (EDT)
Date: Tue, 4 Apr 2017 22:13:31 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170405021330.GD16732@puck.nether.net>
References: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com> <20170405005347.39142.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170405005347.39142.qmail@ary.lan>
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qPvbpMIbOiDDcfjc4dfVtkSQv2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 02:13:36 -0000

On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wrote:
> I agree that Canada is a fairly easy country to get in and out of
> (unless you have a DUI arrest) but it varies a lot so anecdotes about
> entering Canada or any other country don't tell you much.

	Agreed.  When I received my NEXUS card they explicity told me
if I was traveling to a conference and was presenting that I would
require additional paperwork, possibly including a letter of invitation,
and/or a visa.  I presume if I were presenting at an IETF WG I would
check the appropriate box when registering as well and I would get
the paperwork.

	I've also been detained upon re-entering the US for more than 
an hour with my entire family recently crossing the land border.  This
was not a fun experience.

	Either way, I'm waiting to hear the report from Leslie et al
from people based on the survey questions asked.  They seemed quite
comprehensive.

	- Jared

-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.


From nobody Tue Apr  4 21:39:32 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC9A126C0F for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 21:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.023
X-Spam-Level: 
X-Spam-Status: No, score=-14.023 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 q3Y6hMeI2EIb for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 21:39:29 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006FC1243F6 for <ietf@ietf.org>; Tue,  4 Apr 2017 21:39:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5176; q=dns/txt; s=iport; t=1491367169; x=1492576769; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=AEWDvfrz72+czP6R7gEFzbe/sym8PEHmOSSAymN+hEs=; b=CiMB6+cJfdPyyaCo79AoAlk4F6gy1RWPpXE+L/uEEqij+2LUPTCJ2B9c astJJoDHuOCrjyQAZHwkIankREvoWwxTYb4vubQwCsqb/zhSIMj9b5wpN /B77iocbMQTiqaqiJi4Frtez2UiXzAPoIoQ7u97OopyzgSOPY9hCHLZMd I=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B+BAAwdORY/40NJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1SFT5ttlVWCDoYiAoNDQRYBAgEBAQEBAQFrKIUVAQEBAQIBI0M?= =?us-ascii?q?CDAUFCwsYKgICVwYBDAgBARaJbAirNYImimoBAQEBAQEBAQEBAQEBAQEBAQERD?= =?us-ascii?q?4hTgmqEJhEBgyKCXwWccIN8gg2EH4gqimGGW5N2JgEwfQglFggYFUGEWR2BZT6?= =?us-ascii?q?HUIIuAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,277,1486425600";  d="asc'?scan'208";a="406657537"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Apr 2017 04:39:28 +0000
Received: from [10.86.249.69] (bxb-vpn3-325.cisco.com [10.86.249.69]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v354dPt7011526; Wed, 5 Apr 2017 04:39:25 GMT
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Nico Williams <nico@cryptonector.com>, Yoav Nir <ynir.ietf@gmail.com>
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Jared Mauch <jared@puck.nether.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com>
Date: Wed, 5 Apr 2017 06:39:24 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170404221042.GC4004@localhost>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bhs2NHmI97DftfptLhncUXE8Lkp4CxBTC"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/swxKiDaVTJSpMdHksy-cSuk2o3M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 04:39:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bhs2NHmI97DftfptLhncUXE8Lkp4CxBTC
Content-Type: multipart/mixed; boundary="89ct29xUJXkKtTCgLWFHafVrqw5HVe2RW";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Nico Williams <nico@cryptonector.com>, Yoav Nir <ynir.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>,
 Jared Mauch <jared@puck.nether.net>
Message-ID: <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
 <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
 <20170404204617.GC16732@puck.nether.net>
 <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com>
 <20170404221042.GC4004@localhost>
In-Reply-To: <20170404221042.GC4004@localhost>

--89ct29xUJXkKtTCgLWFHafVrqw5HVe2RW
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Nico,

On 4/5/17 12:10 AM, Nico Williams wrote:
> I do suspect that the U.S. will be a more difficult location for more
> attendees than other locations.  Certainly the news we all see is not
> encouraging as to hosting IETF meetings in the U.S.  This I don't deny.=

> Though it's also possible that this is becoming a self-reinforcing meme=

> and that we're just not seeing incidents in other countries in the news=
=2E
> In any case, the U.S. certainly does not have a monopoly on the border
> harasment business.

Certainly people have had trouble getting into other countries, most
notably Canada where an IAB member was refused entry.  But this isn't
just news.  It is a series of declarations by the U.S. government of
their intentions, and the IAOC has to plan ahead.  That's why Jared's
request for data is simply not tenable *at this stage*.  If it turns out
that things aren't so bad, the IAOC can react accordingly.  However, as
I wrote in my original email, there is now good reason to believe that
things will get worse, due to the European Parliament=E2=80=99s decision =
to
require visas from U.S. citizens.

> Some people may wish to boycott the U.S. by refusing to host events
> there.  There is some precedent for such a boycott.  For example, some
> time back an obscure agency of the Texas state government decided to
> guard its surplus budget by policing public drunkenness at hotel bars,
> which led to a number of conferences pulling out of Texas, and the
> ensuing bad PR led the legislature to rein in said agency.
>
> However, at the scale of a state/province the politics of boycotts is
> generally not partisan, but at a national/global scale it tends to be
> rankly partisan, and boycotts may not be productive and may be divisive=
,
> and should be approached with care.  Here "care" means: get some
> evidence of negative impact on participation. =20

We ALREADY have evidence, as some people couldn't make Chicago, and said
so on this very list (and, by the way, were shamefully attacked and
dismissed (no, it certainly wasn't you)).  What we don't have is an
understanding of the order of magnitude of the impact, and that is going
to be very hard to gather in so  fluid a situation with so long a
lookahead.  The point, by the way, as I see it, is not to punish the
U.S. but to hold a successful meeting (that is what the mtgvenue draft
states as well).

> Reducing frequency of
> U.S. meetings is not a boycott, and is something the IETF has been doin=
g
> for a long time anyways.  Further reducing that frequency in the short
> term would be perfectly fine, though it would also reduce opportunities=

> for gather the stats we really need to make a sound, non-partisan
> decision to boycott if the stats warrant it.
>

Turn this around: suppose we do keep the meeting in San Francisco, for
instance, and some number of people cannot get there for whatever
reason, or cannot otherwise function on an equal footing.  Would the
IAOC then be attacked for having ignored the vast number of warnings
that have been signaled?

Eliot


--89ct29xUJXkKtTCgLWFHafVrqw5HVe2RW--

--bhs2NHmI97DftfptLhncUXE8Lkp4CxBTC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY5HT8AAoJEIe2a0bZ0nozMIsH/0cRY3+HSk3Yyj9IepNKqXK5
/S+c1JgDQW5JCfs7v5VOlpHTmojikO7nOMStXja1VqE99GsIffDEOLijq3UNhLK4
18rcCqN/q2hUT+sd0WPCGW8YWn9uqRjG/49oEP9I0JLE0G6yGMk+FaCRGvDIm365
HEcuUQ4QEXUmVfNpnfXyI4hscRDryBYRgMmZ8QUMY3V61YvoBMNWaATA5eW1XvRR
O0uMjvQMrVf7iTlv2eCx/IXUFNTOvCmsHvpdGLhqDZjlUltKF4IAtnr7HyJHwvSv
tmDRrgURkjxhVKEGtNN1yARUhCiS0NAUVav7q+KBeObkf10oVIXir5Ro3w6Pacc=
=E6it
-----END PGP SIGNATURE-----

--bhs2NHmI97DftfptLhncUXE8Lkp4CxBTC--


From nobody Tue Apr  4 22:56:35 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C826112940F for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 22:56:33 -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 1WtwR3m0eVFm for <ietf@ietfa.amsl.com>; Tue,  4 Apr 2017 22:56:31 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 E5EC512940B for <ietf@ietf.org>; Tue,  4 Apr 2017 22:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v355uMOW012730; Wed, 5 Apr 2017 07:56:23 +0200 (CEST)
Received: from client-0226.vpn.uni-bremen.de (client-0226.vpn.uni-bremen.de [134.102.107.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vyZpZ68dPzDHSB; Wed,  5 Apr 2017 07:56:22 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net>
Date: Wed, 5 Apr 2017 07:56:21 +0200
Cc: IETF <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 513064581.695428-e4f2d61af1d0a386a4969298f5833a15
Content-Transfer-Encoding: quoted-printable
Message-Id: <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net>
To: mike stJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0jewU2f9PWZHqwUuMoeE3HTJqGg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 05:56:34 -0000

On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
>=20
> .005 deaths per week per 1000

Right, the 270 micromorts per year (~ 5 micromorts per week) you cited =
would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting =
killed =E2=80=94 a factor three less than the 1.5 % that my numbers =
result in, but not off by a large factor.
(Still, I wonder where that factor three comes from.)

Luckily, we hit the other 98.5 % this week.

(I=E2=80=99m not that worried by the ~ 15 micromorts of risk I =
personally was subjected to, given that I spent on the order of 250 =
microlives for the time that went into this meeting.
But my wife, who had been planning our wonderful vacation in Colombia =
earlier this year, definitely was.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr  5 01:11:20 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2611243F6 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 01:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 6mU75MfmJN9j for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 01:11:17 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.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 770ED1241FC for <ietf@ietf.org>; Wed,  5 Apr 2017 01:11:17 -0700 (PDT)
X-AuditID: c1b4fb30-ea83298000006667-02-58e4a6a3cb86
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by  (Symantec Mail Security) with SMTP id 91.CB.26215.3A6A4E85; Wed,  5 Apr 2017 10:11:15 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.158]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0339.000; Wed, 5 Apr 2017 10:11:07 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>, mike stJohns <mstjohns@comcast.net>
CC: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Thread-Topic: IAOC requesting input on (potential) meeting cities
Thread-Index: AQHSrW9jSzJb0/d0MEKmqC/w6m/JqaG1ajkAgAApzQCAAB+4AIAAco+AgABY/gA=
Date: Wed, 5 Apr 2017 08:11:06 +0000
Message-ID: <D50A7FA0.1A840%christer.holmberg@ericsson.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org>
In-Reply-To: <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.2.170228
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F8FBB6565160F842B8F9BA48EF0D3EF5@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBIsWRmVeSWpSXmKPExsUyM2K7iu7iZU8iDI5cN7c4MuUuq8WzjfNZ LKasy3Jg9pj8eA6jx5IlP5k8pi3KDGCO4rJJSc3JLEst0rdL4MpYfyK/YCpXxdTJD9kbGLs5 uhg5OSQETCQOfOhk7mLk4hASWM8ocerHPlYIZzGjxIXpOxi7GDk42AQsJLr/aYM0iAi4Syw/ fYMFxGYWkJC4PuEdE4gtLOAg0fHpEQtEjaPEsi29ULafRM/lu2A1LAIqEj3/5oDZvALWEqf/ r4NafIhF4sy8V2AJTqDEyT3dbCA2o4CYxPdTa5gglolL3HoynwniagGJJXvOM0PYohIvH/9j BbFFBfQk9v37ygYRV5Rof9rACNFrIPH+3HxmCNtaYuu+FjYIW1ti2cLXzBAHCUqcnPmEZQKj +Cwk62YhaZ+FpH0WkvZZSNoXMLKuYhQtTi1Oyk03MtJLLcpMLi7Oz9PLSy3ZxAiMv4Nbfhvs YHz53PEQowAHoxIP74NljyOEWBPLiitzDzFKcDArifAWLXkSIcSbklhZlVqUH19UmpNafIhR moNFSZzXcd+FCCGB9MSS1OzU1ILUIpgsEwenVAPjsv3fZyv1uS+dNiNcWv/ig+gvV4v/HPlS K7dhWW/S4v5SP1cXoU+q7w+HeDiucFnHYHHPnG31zNliP22bnBKvrW/745xgoHAitvrphAy7 eaf9o56U/ZiiuHN2maWl+7ct1xNPBRy4a89W9VEz4SFT0r4/PH88rWef3r38ZZjqpxUiujK5 6+UPKrEUZyQaajEXFScCAMQ6tym7AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8oLHChLt-eVHWitHkCv5zlfoG0A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 08:11:19 -0000

Chicago is a big city, and the murder rate varies widely between different
areas. So, if you do your maths based on the numbers in the areas where
IETFers are likely to move around, and the kind of activities IETFers are
likely to participate in (much of the violence is related to
gang/drug-related activities), I=B9m sure the result is going to be even
smaller=8A=20





On 05/04/17 08:56, "ietf on behalf of Carsten Bormann"
<ietf-bounces@ietf.org on behalf of cabo@tzi.org> wrote:

>On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
>>=20
>> .005 deaths per week per 1000
>
>Right, the 270 micromorts per year (~ 5 micromorts per week) you cited
>would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting
>killed =8B a factor three less than the 1.5 % that my numbers result in,
>but not off by a large factor.
>(Still, I wonder where that factor three comes from.)
>
>Luckily, we hit the other 98.5 % this week.
>
>(I=B9m not that worried by the ~ 15 micromorts of risk I personally was
>subjected to, given that I spent on the order of 250 microlives for the
>time that went into this meeting.
>But my wife, who had been planning our wonderful vacation in Colombia
>earlier this year, definitely was.)
>
>Gr=FC=DFe, Carsten
>


From nobody Wed Apr  5 01:26:07 2017
Return-Path: <prvs=1268eec01c=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 740D71241FC for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 01:26: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4c3kHG0eBmH5 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 01:26:03 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4696129412 for <ietf@ietf.org>; Wed,  5 Apr 2017 01:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491380760; x=1491985560; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=gySLDdQkgXaY0dn+jAUKlBNR/ RCiDXJf9a1uYClixGI=; b=AZn1u071U1HcG3SHh7G5JICb+haFi1EdDc4Qmi9hw NFR4te/ZYHScd4mw+k9Zi8ENwnRByCcnMaZADj9Ga/LMCdPtmRWiAdfLQDMq30Pa xNZkpN906x6byO5wUSygSbeNM80CM/M6aNKIbP20zJsqg2MxjjqPR/EgAJRTQ48p NQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=XAM3eh2KYDejYYehGKc5W8MBX/FwqgBNkrHTvQQP5wqZVDWvvWjQBqQWQSB/ IsPPwZi/PYRC4SjpK5VKs9xRnkSnzjcBQYqgPYhCWxb9CXMFNlx6YBVpz u4HDGWg/9oKBbKtjJ/tRbrA+mfTU5wTwvVf7lrfQDr9E0HYwBbeRfo=;
X-MDAV-Processed: mail.consulintel.es, Wed, 05 Apr 2017 10:26:00 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 05 Apr 2017 10:25:59 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005402809.msg for <ietf@ietf.org>; Wed, 05 Apr 2017 10:25:59 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170405:md50005402809::qNop2TZFR+IA3GLZ:00001o7X
X-Return-Path: prvs=1268eec01c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Wed, 05 Apr 2017 10:25:54 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>, <ioac@ietf.org>
Message-ID: <FBC8267C-32A8-4358-A0A5-C2A0A236318A@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com>
In-Reply-To: <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6KZi_iO9u2Bw3pWGyNLdHPCmiHg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 08:26:06 -0000

One important question here, same as we had in the case of Singapore.

If we cancel San Francisco, how much that is going to cost to the IETF for =
each of two planned meetings?

Furthermore, can the IAOC respond to this:

Can we cancel the actual hotel contract considering the new US situation? I=
f not, has this been considered for new contracts to avoid this problem?

I think the relevant information in the contract need to be disclosed and h=
ave it now on the table, otherwise we will be wasting the time discussing p=
ossibilities that are actually impossible to assume for the IETF =E2=80=A6

My general position is:
1) I will prefer not cancelling already planned meetings.
2) I will prefer not =E2=80=9Cblocking=E2=80=9D any regions or countries fr=
om future meetings, including US.
3) However, for already contracted meetings, if this is going to cost IETF =
thousands of dollars, we can=E2=80=99t afford that.
4) We must work with authorities to avoid people being banned for attending=
 the meetings.

Maybe I=E2=80=99ve missed responses to some of my answers already, in any c=
ase, can the IAOC provide urgently those with a complete summary of the sit=
uation?

Regards,
Jordi
=20

-----Mensaje original-----
De: Eliot Lear <lear@cisco.com>
Responder a: <lear@cisco.com>
Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 6:39
Para: Nico Williams <nico@cryptonector.com>, Yoav Nir <ynir.ietf@gmail.com>
CC: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>=
, Jared Mauch <jared@puck.nether.net>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    Nico,
   =20
    On 4/5/17 12:10 AM, Nico Williams wrote:
    > I do suspect that the U.S. will be a more difficult location for more
    > attendees than other locations.  Certainly the news we all see is not
    > encouraging as to hosting IETF meetings in the U.S.  This I don't den=
y.
    > Though it's also possible that this is becoming a self-reinforcing me=
me
    > and that we're just not seeing incidents in other countries in the ne=
ws.
    > In any case, the U.S. certainly does not have a monopoly on the borde=
r
    > harasment business.
   =20
    Certainly people have had trouble getting into other countries, most
    notably Canada where an IAB member was refused entry.  But this isn't
    just news.  It is a series of declarations by the U.S. government of
    their intentions, and the IAOC has to plan ahead.  That's why Jared's
    request for data is simply not tenable *at this stage*.  If it turns ou=
t
    that things aren't so bad, the IAOC can react accordingly.  However, as
    I wrote in my original email, there is now good reason to believe that
    things will get worse, due to the European Parliament=E2=80=99s decisio=
n to
    require visas from U.S. citizens.
   =20
    > Some people may wish to boycott the U.S. by refusing to host events
    > there.  There is some precedent for such a boycott.  For example, som=
e
    > time back an obscure agency of the Texas state government decided to
    > guard its surplus budget by policing public drunkenness at hotel bars=
,
    > which led to a number of conferences pulling out of Texas, and the
    > ensuing bad PR led the legislature to rein in said agency.
    >
    > However, at the scale of a state/province the politics of boycotts is
    > generally not partisan, but at a national/global scale it tends to be
    > rankly partisan, and boycotts may not be productive and may be divisi=
ve,
    > and should be approached with care.  Here "care" means: get some
    > evidence of negative impact on participation. =20
   =20
    We ALREADY have evidence, as some people couldn't make Chicago, and sai=
d
    so on this very list (and, by the way, were shamefully attacked and
    dismissed (no, it certainly wasn't you)).  What we don't have is an
    understanding of the order of magnitude of the impact, and that is goin=
g
    to be very hard to gather in so  fluid a situation with so long a
    lookahead.  The point, by the way, as I see it, is not to punish the
    U.S. but to hold a successful meeting (that is what the mtgvenue draft
    states as well).
   =20
    > Reducing frequency of
    > U.S. meetings is not a boycott, and is something the IETF has been do=
ing
    > for a long time anyways.  Further reducing that frequency in the shor=
t
    > term would be perfectly fine, though it would also reduce opportuniti=
es
    > for gather the stats we really need to make a sound, non-partisan
    > decision to boycott if the stats warrant it.
    >
   =20
    Turn this around: suppose we do keep the meeting in San Francisco, for
    instance, and some number of people cannot get there for whatever
    reason, or cannot otherwise function on an equal footing.  Would the
    IAOC then be attacked for having ignored the vast number of warnings
    that have been signaled?
   =20
    Eliot
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr  5 02:47:14 2017
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C0512944C for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 02:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 GAjZ3Yp_AhUG for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 02:47:11 -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 692B51201F8 for <ietf@ietf.org>; Wed,  5 Apr 2017 02:47:11 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id r203so8842061oib.3 for <ietf@ietf.org>; Wed, 05 Apr 2017 02:47:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=GsAHh0ZQrwsPEZ78aiCoOByqty5wdErNM0b0ltFd8eE=; b=gDDMHvTUCWTQVve9gAfZ8r9MCkaNGT9fvJWfR0dbHPwqsVeHPvBT2CtrR52keUjDZk jlImslqoAL2qRhOj8LyPrpAZeMlXTVOjS3vAVhfy7iVB8yYfDtuBmAS/IGh22Gv+g000 Zj+9gYtJhgz1R3SDEqitaaiz8tBs1zwCKrprbQ91PEVLwr0SJFlFVJaq6sLz2FP3nVkD 01RKjeSIzQUSlAWKfwJ1bxRt5gLMHKDc+5O5dmkYUi2aNso5ER2qr4dXL8rYpgassFpQ q8e98J5Ej1ejwiZ8nSOw6KK76SPXH3o0VJTqMc7B2WNOf3q9ioHRuGzGcLod99HUIAFx +WNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=GsAHh0ZQrwsPEZ78aiCoOByqty5wdErNM0b0ltFd8eE=; b=Qap9ssGEGuCfw8pXf+0Wc0T4n9sycEmSNK6zSg5e8MHLNTXU+Pk7eLZ0HGYuimvi6p wnsR81U9pRU3gWuaJvlryt1fhnEdWbV8eKtAb0ef/dBCXYY2fIRyQTBwEM5ULCUqIZ9j OGQDIQjCyyENh+lfOjVgFnUVwOAQGtl9fz22Yn520m7QpcIYFJl6NT2uVXKMQkkl+Gpj 4NmiTA8k1+ebk010XpiCposBqJRQD+eYbHVcc8rAU4jsy7VfDEMJJlZWFUcLwttt2Bdi ll0WYxuZzi1ub+0xWaevyHFuNLasx3kmwDMoVCKOqJ5QAuG/VOhocTO3FbG7syS3wRWt WGKg==
X-Gm-Message-State: AFeK/H1r7Gfs5D5lLrrE8/d1uwOqVFgdhT8/xIB6RoWruJn5CQ4hCbV0MYBXp6IX1kCeb3VI6cxK1juQANVlRQ==
X-Received: by 10.157.19.114 with SMTP id q47mr16432237otq.77.1491385630036; Wed, 05 Apr 2017 02:47:10 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.182.42.106 with HTTP; Wed, 5 Apr 2017 02:46:29 -0700 (PDT)
In-Reply-To: <FBC8267C-32A8-4358-A0A5-C2A0A236318A@consulintel.es>
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com> <FBC8267C-32A8-4358-A0A5-C2A0A236318A@consulintel.es>
From: Dick Franks <rwfranks@acm.org>
Date: Wed, 5 Apr 2017 10:46:29 +0100
X-Google-Sender-Auth: Ay1sH6bNY6h4UICSezIscwOGQ3w
Message-ID: <CAKW6Ri59h1vC6pO=3UXa1kF4fwh=4LeJ+nU-zzT10RBXRNnicw@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Jordi Palet Martinez <jordi.palet@consulintel.es>
Cc: IETF <ietf@ietf.org>, ioac@ietf.org
Content-Type: multipart/alternative; boundary=001a1134fcc0b398b7054c6846f2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NDaAnDRHnUttb-Pu2pm2M0bBZDk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 09:47:13 -0000

--001a1134fcc0b398b7054c6846f2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5 April 2017 at 09:25, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
wrote:

> One important question here, same as we had in the case of Singapore.
>
> If we cancel San Francisco, how much that is going to cost to the IETF fo=
r
> each of two planned meetings?
>

>8


> 3) However, for already contracted meetings, if this is going to cost IET=
F
> thousands of dollars, we can=E2=80=99t afford that.
>

If the entire foreign contingent votes with its feet and stays home,
strikes me that IETF can't afford that either.


And further to your earlier remark:

The UK is, and will remain, a part of the EU until March 2019 in accordance
with Lisbon Treaty, Article 50.

PS  The Treaty of Utrecht has no equivalent of Article 50.

--001a1134fcc0b398b7054c6846f2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 5 April 2017 at 09:25, JORDI PALET MARTINEZ <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:jordi.palet@consulintel.es" target=3D"_blank">jordi.palet@c=
onsulintel.es</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One i=
mportant question here, same as we had in the case of Singapore.<br>
<br>
If we cancel San Francisco, how much that is going to cost to the IETF for =
each of two planned meetings?<br></blockquote><div><br>&gt;8 <br></div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
3) However, for already contracted meetings, if this is going to cost IETF =
thousands of dollars, we can=E2=80=99t afford that.<br></blockquote><br></d=
iv><div class=3D"gmail_quote">If the entire foreign contingent votes with i=
ts feet and stays home, strikes me that IETF can&#39;t afford that either.<=
br><br><br></div><div class=3D"gmail_quote">And further to your earlier rem=
ark:<br><br>The UK is, and will remain, a part of the EU until March 2019 i=
n accordance with Lisbon Treaty, Article 50.<br><br></div><div class=3D"gma=
il_quote">PS=C2=A0 The Treaty of Utrecht has no equivalent of Article 50.<b=
r><br></div></div></div>

--001a1134fcc0b398b7054c6846f2--


From nobody Wed Apr  5 02:55:29 2017
Return-Path: <prvs=1268eec01c=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 084E2129432 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 02:55:28 -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, LOTS_OF_MONEY=0.001, T_MONEY_PERCENT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Js_CohZbKdrU for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 02:55:26 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB3F1201F8 for <ietf@ietf.org>; Wed,  5 Apr 2017 02:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491386124; x=1491990924; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=sqrAk9FDJpgDXDBEFtmIpgmW+ LDXIA2FAZHzyQ3Ztcw=; b=HfJYrgmdfPVV9sInN9VUS75STMEBfIacF9oyBZfjL ttV0fEmLxygJJNhRrnYpAZaTjQsqT6bZ204r/obU5x+O6wr5xYVwRmwpWp1u+ahv /1iU8bHhlwd0CB59dRPwxUU8fMFCZNmDvzHssbObvlnaHBFWW8hukDWF1A5/G0j0 bg=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=fANRv2eXxUKQoIsAICprHfL5sfr2Td5qOMI4DBHed4K3Mpj2xV8Rfoq0+an8 /mr1Zs8rA5LW6PUSdSL9deCOFReDAQNH/PuyhOG2ZCbZYPfl5w9EUdP56 tDqSjxhvwLwFZEqp2FqQmldQNNXG+AX0gEKPkgadKQnP6a6fZQlC38=;
X-MDAV-Processed: mail.consulintel.es, Wed, 05 Apr 2017 11:55:24 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 05 Apr 2017 11:55:23 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005402865.msg for <ietf@ietf.org>; Wed, 05 Apr 2017 11:55:22 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170405:md50005402865::KudKBjjCkqJxrVKQ:00001UCj
X-Return-Path: prvs=1268eec01c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Wed, 05 Apr 2017 11:55:21 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>
CC: <iaoc@ietf.org>
Message-ID: <125229D3-4DCF-484D-A836-2AD43EE28DE9@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <5d6085d5-c8d1-22f3-d9e7-a1a9294e655c@cisco.com> <FBC8267C-32A8-4358-A0A5-C2A0A236318A@consulintel.es> <CAKW6Ri59h1vC6pO=3UXa1kF4fwh=4LeJ+nU-zzT10RBXRNnicw@mail.gmail.com>
In-Reply-To: <CAKW6Ri59h1vC6pO=3UXa1kF4fwh=4LeJ+nU-zzT10RBXRNnicw@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M0If2ByWTqoC6_k2obm14eqo5UY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 09:55:28 -0000

Agree, but we should have the figures to make a right and balanced decision=
, right?

Is not the same if it cost 100.000 USD than 10.000 or 200.000 for each of t=
hose meetings =E2=80=A6, despite the risk of having 50% of the participants=
 not attending, which in terms of just =E2=80=9Cmoney=E2=80=9D (not saying =
is the only thing that matters), 550 participants (half of regular attendan=
ce) means 440.000 USD at 800 USD registration fee.

Regarding UK, yeah, I should have said Schengen, I think somebody else alre=
ady mention that point before.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Dick Franks <rwfranks@acm.org=
>
Responder a: <rwfranks@acm.org>
Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 11:46
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: IETF <ietf@ietf.org>, <ioac@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

   =20
   =20
    On 5 April 2017 at 09:25, JORDI PALET MARTINEZ <jordi.palet@consulintel=
.es> wrote:
   =20
    One important question here, same as we had in the case of Singapore.
   =20
    If we cancel San Francisco, how much that is going to cost to the IETF =
for each of two planned meetings?
   =20
   =20
   =20
    >8=20
   =20
    =20
   =20
    3) However, for already contracted meetings, if this is going to cost I=
ETF thousands of dollars, we can=E2=80=99t afford that.
   =20
   =20
   =20
   =20
    If the entire foreign contingent votes with its feet and stays home, st=
rikes me that IETF can't afford that either.
   =20
   =20
   =20
    And further to your earlier remark:
   =20
    The UK is, and will remain, a part of the EU until March 2019 in accord=
ance with Lisbon Treaty, Article 50.
   =20
   =20
    PS  The Treaty of Utrecht has no equivalent of Article 50.
   =20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr  5 03:33:53 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A76531293D6 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 03:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 4YzcBmwRehMu for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 03:33:51 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 DC8611201F8 for <ietf@ietf.org>; Wed,  5 Apr 2017 03:33:50 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v35AXnYf027081 for <ietf@ietf.org>; Wed, 5 Apr 2017 06:33:49 -0400 (EDT)
Date: Wed, 5 Apr 2017 06:33:49 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170405103349.GA3151@gsp.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <20170404221912.GD4004@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170404221912.GD4004@localhost>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FmqPFujKE2bNTDBEnWlSb9Fp8z0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 10:33:53 -0000

On Tue, Apr 04, 2017 at 05:19:13PM -0500, Nico Williams wrote:
> *That* would be a huge deal.  I don't quite believe it likely to happen
> though: it would require lots of new hardware and staffing to do
> anything useful with every visitor's devices and password [...]

It would.  But it would require neither new hardware nor staffing to
do something useful with *some* visitors' devices and passwords and to
merely engage in security theater with the rest.  It appears that
this policy is intended to be comprehensive in order to avoid subsequent
court challenges based on the selection of certain groups of people.

> [...] _and_ keep entry bandwidth as high as today (_and_ keep tourism
> and business travel to the U.S. from collapsing).

It's not at all clear that either of these are policy objectives.

---rsk


From nobody Wed Apr  5 03:37:56 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58664127201 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 03:37:54 -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 Ldg1xoF_fpZY for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 03:37:52 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 AC4261201F8 for <ietf@ietf.org>; Wed,  5 Apr 2017 03:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v35AbYcp014624; Wed, 5 Apr 2017 12:37:34 +0200 (CEST)
Received: from client-0172.vpn.uni-bremen.de (client-0172.vpn.uni-bremen.de [134.102.107.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vyj3266SvzDHfV; Wed,  5 Apr 2017 12:37:34 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20170404211526.GA25253@gsp.org>
Date: Wed, 5 Apr 2017 12:37:34 +0200
Cc: IETF <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 513081453.952522-823acf4a412ee8c17acebee12aa021fd
Content-Transfer-Encoding: quoted-printable
Message-Id: <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8yWtc3QDrnfsXOvHVj7HxHIZVW0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 10:37:54 -0000

On Apr 4, 2017, at 23:15, Rich Kulawiec <rsk@gsp.org> wrote:
>=20
> the Wall
> Street Journal is reporting today that a new set of procedures under
> consideration will include demanding the phone passwords from *all*
> foreigners entering the US.

=
https://www.wsj.com/articles/trump-administration-considers-far-reaching-s=
teps-for-extreme-vetting-1491303602?mod=3De2tw

Whoa.  *Not stable*.

San Francisco/West Coast (including Hawaii) used to be a better =
destination than the rest of the USA, as it is governed by the Ninth =
Circuit, which seemed to keep a remnant of rule of law alive.  Not sure =
that privileged status will remain.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr  5 04:24:02 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D9A2129452 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 04:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.979
X-Spam-Level: 
X-Spam-Status: No, score=-0.979 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, MISSING_HEADERS=1.021, 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 OkCgqvs5JfJq for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 04:24:00 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::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 4C5B61201F8 for <ietf@ietf.org>; Wed,  5 Apr 2017 04:24:00 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id w43so9375040wrb.0 for <ietf@ietf.org>; Wed, 05 Apr 2017 04:24:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:cc:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=CGrpxd5BVtV7DzXZuOmXrPQssQsAvWSKDMwbw8pHfio=; b=Q/ZeW/7tMk91dmQlIPbpZPcl7/pAhWuEL8AJy53G+VMGZdZfZxbwSiIO7/QOlBlWT5 VRqYYmzOgr3ZrX8SRma42kxd5FjOJPI4ZNnEZZ2U6+GgYxqTmLfcx5cowoueSFBG/iCB bdPLxQHOz+MPUUiUVOopsaCG7yudmbeV33QVV+MfLDyg1I2/Odj7hD+6VsK+GkoNDw5T bsjoyBJjPKe7HhN5wr3WlCJI+ne72SRONqVOpQoq6pVxEgyPeDhUXO7gVDw8je9Y7LCF 9SzewWMY/M7EVeB2KBfw7G9xRp4+p8no1NScpTL1hHDa8CNCFkAGuFo8qUlJ4hCLz7+z ursA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=CGrpxd5BVtV7DzXZuOmXrPQssQsAvWSKDMwbw8pHfio=; b=cIyWaYnI6tzNGdJVA40MqgkRECF0Bl62utjAa8HS2jYLJNySBUtFQElBhCJPBNGbBa oThdFrolnGAw9Erhcj2QQ9895h6APavxWhm8f4qnmpW3zI0yJOECwe5+xARddeWeMtRS YaCm+DGIRPQ3ioFT0tDf93rTvqhihG9zGwLkk7djmxYrTZDB/P7lRrFXuEHF1rcdGFed CAR6aqTIdrt/OlPq50rQekZbcvzaRNiTqemmCGanAG5qjCTgwRDuP2hWgGTXvhLHgKM1 dtDOZrLvFs0mgeGUDQeTeqjSmVUmfd2lpDFPiiRCYZhHV708n5b/0EvqApUPL4VIZtt1 qNHA==
X-Gm-Message-State: AFeK/H3NSKRYOBz+mjXTVInA/tzzxOy39Bt0GlaIfvvydMSdYXtwzZ8z2k51w1cmKdWtjw==
X-Received: by 10.223.168.120 with SMTP id l111mr25623074wrc.173.1491391437638;  Wed, 05 Apr 2017 04:23:57 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id o15sm25801106wra.61.2017.04.05.04.23.56 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Apr 2017 04:23:57 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <20170404221912.GD4004@localhost>
Cc: IETF <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <8b83a115-437f-dd02-4a22-1fc0d45b301d@gmail.com>
Date: Wed, 5 Apr 2017 12:23:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170404221912.GD4004@localhost>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pKoYwryVpG5xNdhVawjmTMfg42Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 11:24:01 -0000

On 04/04/2017 23:19, Nico Williams wrote:
> If a country starts demanding access to and passwords for every
> visitor's every device

.. hopefully they will accept a list of possible passwords plus password 
recovery as an answer, because for anything that I rarely use such as 
facebook, I work my way down a list of possible passwords and more often 
than not end up using password recovery.

Stewart


From nobody Wed Apr  5 04:37:21 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD34129480 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 04:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 O9UzJfmLu7kv for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 04:37:18 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 20769129476 for <ietf@ietf.org>; Wed,  5 Apr 2017 04:37:18 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v35BbGge028423 for <ietf@ietf.org>; Wed, 5 Apr 2017 07:37:17 -0400 (EDT)
Date: Wed, 5 Apr 2017 07:37:16 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170405113716.GA6511@gsp.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <FAF82FC8-58AB-43AA-A094-280EA248E319@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FAF82FC8-58AB-43AA-A094-280EA248E319@google.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uubYdHklmSW8VReZ95PTAnHLDBc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 11:37:19 -0000

On Tue, Apr 04, 2017 at 05:40:54PM -0700, james woodyatt wrote:
> On Apr 3, 2017, at 08:26, Rich Kulawiec <rsk@gsp.org> wrote:
> > 
> > 	- if the data they provide access to will be retained
> 
> 
> 		- if the data protected by the password will be modified or deleted
> 		- if the software on the protected device will be modified or deleted

You're absolutely right, those should be on the list.  Let me also add
two more.  (1) Given the long, steady, depressing history of massive breaches
of various governments' databases, there is no way to know if passwords
acquired and data siphoned off will be adequately protected.  (2) There's
also no way to know what any enterprising person will independently
choose to do with this veritable goldmine of saleable information --
doubly so given the lack of checks and balances, audits, controls, etc.

---rsk


From nobody Wed Apr  5 05:46:46 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA3B1287A0 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 05:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, 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 L594I1Tqapzd for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 05:46:43 -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 20B36127B31 for <ietf@ietf.org>; Wed,  5 Apr 2017 05:46:41 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id b187so13534833oif.0 for <ietf@ietf.org>; Wed, 05 Apr 2017 05:46:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:cc; bh=p2Kau6mJ33qb/0SCX4cLs8jtOvs463lAvSEwFMR8WYE=; b=m8W5IFKUbHkzFDQmzt/6fcM5dIJtNN1IpphBSEjQYZP1WIgGuDeanNdP1pA0DhL4TG f37HcnLEuEkn71m2ho7wijzR9D1b5FJ1lQl5YnnNFiiQJEqGCq7uMNWDGpfNe+uOTRw/ 4GXpR7IwbDq4pr1E2IsZPoeABB3UbQVdD7km9g5gbu9qOd82WT6IEnB6lgt5mVvRzgHa wqAvxQ8R/4lCk2nRYxoZveO57ichKumPPscUctFLiS9ruRGkxD2OV604szAazrqdrKSw lKrbyUS2egBXHzgi5J/tavJyDnE59fWRQteHx7tmDRhKvp/csNZkRR+dTnecOWHPlP+J 8wzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:cc; bh=p2Kau6mJ33qb/0SCX4cLs8jtOvs463lAvSEwFMR8WYE=; b=aM6J6elTp88CrUtF/obaH3QoGnXXlXu9I1x8IbbJ1kOdSm4lSF6zJjKB+p6tNuiDPF RQrlJgFZYKgQBILF1w7pMKjZQwyReBtmwOMDYSbH27B5fwOO5D69YoKF64BWID+OM7IY hveRhHijz8twq+5FIMQwpz6eGHeQ2Gc8FoErIDNnkrmifdFsVVWoTebV9dTynnyaCcjg V0ffFAvz02jbKRHv+eWtyaIoDy/T+ePu54fVkGr4pchOqJ7gS8qun5B7WUd9YcH5Gcrq laZY+hWgs1ZkSDB6Z3SeVXYNtRqDEh/i2c11RwXxwWMF91vmD/jeIQTeSzwEE3ccWYHX KOmQ==
X-Gm-Message-State: AFeK/H1/TvnzjMRjvAXvH8WczPIdGZl9eYZn5zmgjvxLE2GuPjSqXDY26K1xZxQMwACEDPYXYLEK4C4m3DXH1g==
X-Received: by 10.157.80.20 with SMTP id a20mr16278239oth.89.1491396400035; Wed, 05 Apr 2017 05:46:40 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.46.138 with HTTP; Wed, 5 Apr 2017 05:46:39 -0700 (PDT)
In-Reply-To: <20170405113716.GA6511@gsp.org>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <FAF82FC8-58AB-43AA-A094-280EA248E319@google.com> <20170405113716.GA6511@gsp.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 5 Apr 2017 08:46:39 -0400
X-Google-Sender-Auth: XExEjFZxit0PUqbAnLlvdIwGowY
Message-ID: <CAMm+LwhiqeOcOeGJX67J93_pWm1t_9DKwwFsJsQpsQhYSzGabA@mail.gmail.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f403043530a4a4bd36054c6ac8c9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/poC0qDOWJ3kwpvWBx0OUGPr4XTU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 12:46:44 -0000

--f403043530a4a4bd36054c6ac8c9
Content-Type: text/plain; charset=UTF-8

The core problem here is that the Trump administration has followed through
on campaign pledges to implement rules that are irrational and
unpredictable. At this point in time, nobody can know for certain what the
rules will be in six months time, let alone the two year planning horizon
for meetings.

What we face here is a situation of predictable unpredictability. In such a
situation, it is necessary to always plan for the worst case scenario. That
the situation 'might' be OK is irrelevant in the context of a two year
planning window for a meeting costing roughly a million dollars a time.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
 core problem here is that the Trump administration has followed through on=
 campaign pledges to implement rules that are irrational and unpredictable.=
 At this point in time, nobody can know for certain what the rules will be =
in six months time, let alone the two year planning horizon for meetings.</=
div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div c=
lass=3D"gmail_default" style=3D"font-size:small">What we face here is a sit=
uation of predictable unpredictability. In such a situation, it is necessar=
y to always plan for the worst case scenario. That the situation &#39;might=
&#39; be OK is irrelevant in the context of a two year planning window for =
a meeting costing roughly a million dollars a time.</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div></div>

--f403043530a4a4bd36054c6ac8c9--


From nobody Wed Apr  5 06:23:18 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E332C127076 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:23:16 -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, RP_MATCHES_RCVD=-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 sh-T6dFA58JI for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:23:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494771250B8 for <ietf@ietf.org>; Wed,  5 Apr 2017 06:23:15 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D21AE203AF for <ietf@ietf.org>; Wed,  5 Apr 2017 09:47:32 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0FBA2636BB for <ietf@ietf.org>; Wed,  5 Apr 2017 09:23:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com> <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com> <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 05 Apr 2017 09:23:14 -0400
Message-ID: <6955.1491398594@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IMwYa0mElmgW5b3LhJqSBFGlA5Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 13:23:17 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Andrew G. Malis <agmalis@gmail.com> wrote:
    > At least once, I was questioned extensively when going from the US to
    > a meeting in Canada. I had to show evidence of the meeting and my
    > itinerary and convince them that I wasn=E2=80=99t entering Canada to =
take work
    > away from a Canadian. That said, I still support holding meetings in
    > Canada.

IETF98 was among the only times I was *NOT* asked questions like that when
entering the US.   I did enter at Midway.   That none of are asked such
questions when entering europe always surprises me.

I'm not sure what "extensively" means; if that means you were taken aside, =
or
not.  I've been through that at the US border.

"Chair of work group" would always be a bad thing to say, since it has the
word "work" in it.  Never talk about customers.  The IETF is a meeting of
peers.

(Once because it was 5am, and I was just really loud since I was really sti=
ll
asleep).

But, in all cases I felt confident that I would be treated with respect,
(even by the border guard who didn't seem to believe that e-tickets were
real).

I did *not* feel that way while preparing to travel to IETF98.
My fears were not realized; but as Eliot has said, it's *exactly* the
uncertainty that is a problem.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljk78EACgkQgItw+93Q
3WVuTwf/aAS0mkEq5LGJHg63S/r+3P87KEHaZS+mAlO/U397ublGUNRM2maUpJJ5
rqJ3bM2jVzLdMNl75glsBRsDFYCzOgboKre4X7tPzKz8BY5BKWc2B4gFNB8Q7f1Y
y3E0hTxUv2WU6UaIHe1/9F5l/ML2+G3YzDys6EhliUqTP/i8sgIDK8FZSPFIdR6T
mJGmAa0veCdF7E+3m3cya0VxsFrddg5jCMg9PcvoZlGUft9tRYI1tcb/8QuXlOAn
/WbWNJK+/ZX/FxpdzILTWZbe21Vi4nSpcsvwqNGsr4hNE8sjoVHQ28GB2OTnwrrk
iDTg4OYRv/yJNARt0n/wPNBHGBcfZg==
=4yhD
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr  5 06:25:57 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BECA31275AB for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:25:56 -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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 wMr1x5c1qNHI for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:25:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3732A1250B8 for <ietf@ietf.org>; Wed,  5 Apr 2017 06:25:55 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 4C858203AF; Wed,  5 Apr 2017 09:50:13 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7A867636BB; Wed,  5 Apr 2017 09:25:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Jared Mauch <jared@puck.Nether.net>
cc: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <20170405021330.GD16732@puck.nether.net>
References: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com> <20170405005347.39142.qmail@ary.lan> <20170405021330.GD16732@puck.nether.net>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 05 Apr 2017 09:25:54 -0400
Message-ID: <7538.1491398754@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k5GE4c1XA16Jm6wd1HpmbF0ioKw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 13:25:57 -0000

--=-=-=
Content-Type: text/plain


Jared Mauch <jared@puck.Nether.net> wrote:
    > On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wrote:
    >> I agree that Canada is a fairly easy country to get in and out of
    >> (unless you have a DUI arrest) but it varies a lot so anecdotes about
    >> entering Canada or any other country don't tell you much.

    > Agreed.  When I received my NEXUS card they explicity told me
    > if I was traveling to a conference and was presenting that I would
    > require additional paperwork, possibly including a letter of invitation,
    > and/or a visa.  I presume if I were presenting at an IETF WG I would
    > check the appropriate box when registering as well and I would get
    > the paperwork.

No!  Only if you have been paid to present.
     i.e. you are Al Gore coming to talk at the Air Canada center in Toronto.

We don't do presentations like that at the IETF.
The IETF is not like most non-technical "conferences".

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljk8GIACgkQgItw+93Q
3WV6+wgAksmv2Ux3cwTcOOCORzyab/Zwzfc6I3NGfAe+7saO2DssTq0ppbztaRti
KWLevSOV49fyI78MKE7W9gSUjHyBtXo5HtfYeBZ7bJM0+0GW2IOohDJE5tFguST1
3CkuGUfScnBEWmQn1ybSJHUo5oQ9xrbJFJkQKdk4yLaWDqkz2dLzHOV6V1gyMyew
tuX/WXY3wmK+rCt8nenquUAa//nEZ9arn9qdGI1X+wee7awiZLBBhLCaog71jIms
9GQC499mCrj35tDAsX0GFPDbMfKIMETfuAcBgJmqJW9Bb+IAd+V4T+jGCyGXqUbG
ZTP7F5xN0DHuAtc6XZMd1KgyBTtywQ==
=CJmU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr  5 06:50:02 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9414127863 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 JM9FEbSvg0_p for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 06:49:58 -0700 (PDT)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (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 E4B011250B8 for <ietf@ietf.org>; Wed,  5 Apr 2017 06:49:57 -0700 (PDT)
Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-02v.sys.comcast.net with SMTP id vlJsciLSVRJJCvlJscbj36; Wed, 05 Apr 2017 13:49:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1491400196; bh=p/INJqfEtw1dMSxiZkQ6l0y1ZRQR1N2QxJzPSLzP6/U=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=N+WKlR783h6MXKknW204prLwQpRdwyK9yMtjEvodxY3EcmNRY4NnteHZwCylyAC3P lMf4j6x72gkY9Rvu/6URtd8l6vn0ZUf0vI5ewQdfh+dcyyLje/iXIXoOSJMJog2o9z KPsKbB4d2gRK8TPOxn3Kfm1gDqdjX0ZFaZNgp6F+cmvKMPzya2fFxirx9unZTBbl/e CRb1svoSdhUAw7W269k2j/cytrp4Vju3Ztutano4+gcRbhfHE3hxrOES/fbOXqtqm8 Xq0QF/2v9p3/lV/v5QEA9IABD05GwCQk7bBN/dK6YinbwfbqAnG+hMe5JCoIiLS4EM PHQaiV2AAApjg==
Received: from [IPv6:2601:152:4400:a2e0::1599] ([IPv6:2601:152:4400:a2e0::1599]) by resomta-po-12v.sys.comcast.net with SMTP id vlJqclXoldPKDvlJrcvko0; Wed, 05 Apr 2017 13:49:56 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: IAOC requesting input on (potential) meeting cities
From: mike stJohns <mstjohns@comcast.net>
X-Mailer: iPad Mail (14D27)
In-Reply-To: <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org>
Date: Wed, 5 Apr 2017 09:49:54 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-CMAE-Envelope: MS4wfC9xo/RDgZ8oMz/6fyy7IMzOzkDoF1CFszDrSSYuX35m/uVILsaKuJvxJ6aMMRIIvY3crVH4fg3OXwmA19kBgmTf/qV1isK99XnobCDQne9NQlsYCHpS s9Ye9tqLGkoYMU4dTmKG7wYKd8gcVxxx9s50dMteEpM2fkKmN96Zr6JH2rJ/47UtGBe+OY5AgY5DXQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXCFNdTphkW18mIHplJRU8LpDDY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 13:50:00 -0000

Let's try this one more time


27 deaths in 100 would be 27%
27 deaths in 1000 would be 2.7%
27 deaths in 10000 would be .27%
27 deaths in 100000 would be a rate of .027%
The above are all expected deaths per year for the given population - so div=
ide .027% by 52 to get .00051% per week.  That's roughly the chance per indi=
vidual to die during the week from murder.   That's *my* risk for a week of t=
he IETF and that's what should matter to each individual.  =20

If you take that and multiply it by the IETF population you get .005 expecte=
d deaths within the IETF for the entire week.  =20

Now you're using the "at least one" criteria, which works out to be 1-(1-.00=
00051)^1000 =3D .005 or .5% of at least one person dying in the week so your=
 numbers are somewhat reasonable, but don't actually mean anything.  E.g thi=
s is basically the birthday paradox which grows the probability quickly with=
 the size of the set.  =20

 I'll give you an example.  The death rate per 1000 in Germany per year for a=
ll causes is about 11.  That works out to about a 20% chance of at least one=
 person dying in the IETF during the week from all causes including murder i=
f we all lived in Germany.   The equivalent statistic for the US is 8 per 10=
00 which works out to 15% for the IETF for the week.  But we don't seem to b=
e dropping at anywhere close to that rate ( e.g. A death at the meting every=
 5 meetings). =20

Death probabilities are *highly* dependent on the specific populations you'r=
e looking at and actuaries get paid a lot of money to calculate them.  The a=
ctual probabilities for the IETF would benefit from affluence, age, medical c=
are, education, location, etc.=20

Mike



Sent from my iPad

>> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
>>=20
>> .005 deaths per week per 1000
>=20
> Right, the 270 micromorts per year (~ 5 micromorts per week) you cited wou=
ld lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting killed =E2=
=80=94 a factor three less than the 1.5 % that my numbers result in, but not=
 off by a large factor.
> (Still, I wonder where that factor three comes from.)
>=20
> Luckily, we hit the other 98.5 % this week.
>=20
> (I=E2=80=99m not that worried by the ~ 15 micromorts of risk I personally w=
as subjected to, given that I spent on the order of 250 microlives for the t=
ime that went into this meeting.
> But my wife, who had been planning our wonderful vacation in Colombia earl=
ier this year, definitely was.)
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20


From nobody Wed Apr  5 07:26:14 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF89129447 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 07:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 TG9X5riMtDrT for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 07:26:10 -0700 (PDT)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (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 700F0128768 for <ietf@ietf.org>; Wed,  5 Apr 2017 07:26:04 -0700 (PDT)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-07v.sys.comcast.net with SMTP id vlsZc5ednJZefvlspcTR7S; Wed, 05 Apr 2017 14:26:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1491402363; bh=VjfkOFvpS4ZeABlZGEuy18+Agpx6qUNF2tT6/Rs0NKk=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=eotLiP3KAD3MgvIF2b+56ioPsYA6XxaIoWvKBrg/MgaJxFo0HXAwU8/67aKAY41BO PTzb7hffAKij8K4Jq21i2r3L/5HO9+C4HUS03pZ1YIAlXezDfzvpVFW329oxgAuLBK WMcMAgl1kBYvn9cT775yntyTedvX3Uow0lQFflaLTM+by9KHfAD5Xg5vXW0kbyfUKB dfpUT+eTeEf/JqJ4JLwWTw8c022U+bgBGSTiIGL9++J3ak3I5LBSlQKu4b5e1nQuQl OPMWGznDX1xcMlfELtZtUbRi5P9+PB6HkGqyMlUPjl8AtsEATWX1mDal+1M8MnnZmA S9zl4vY6+hRBA==
Received: from [IPv6:2601:152:4400:a2e0::1594] ([IPv6:2601:152:4400:a2e0::1594]) by resomta-po-13v.sys.comcast.net with SMTP id vlsocopsrDIoGvlsocGQOC; Wed, 05 Apr 2017 14:26:03 +0000
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org> <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net>
Date: Wed, 5 Apr 2017 10:26:20 -0400
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: <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfLNPK9l9iB1t5cpGlgIDIwZNNTpIb/xkqWCP0i9KRvk6bEDSwrTcC/GIu+O5B7tRFxruIWNbxCr0SePjxit4XmM89Le2BU/rVdHckLO/8eIkBjmLHYsD sRnynKUPIjNWbBHsRacOAshR9BQFOcVC83YRtu0979Y1s17InKKpv2oV
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9blRL9-XIwITZcvUcGOOxzQeuv0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 14:26:12 -0000

I meant to include (damn iPad):

Carsten's original email was
> Statistically, the chance of any IETFer being killed last week was about 1.5 %.

"Any IETFer being killed" (I read the above as "Any [given] IETFer")  is 
the .00051% chance.  "At least one IETFer" is the .5% chance.  "Anyone 
in the IETF" could mean either - precision is important and I still 
don't actually know which Carsten meant.

Later, Mike

On 4/5/2017 9:49 AM, mike stJohns wrote:
> Let's try this one more time
>
>
> 27 deaths in 100 would be 27%
> 27 deaths in 1000 would be 2.7%
> 27 deaths in 10000 would be .27%
> 27 deaths in 100000 would be a rate of .027%
> The above are all expected deaths per year for the given population - so divide .027% by 52 to get .00051% per week.  That's roughly the chance per individual to die during the week from murder.   That's *my* risk for a week of the IETF and that's what should matter to each individual.
>
> If you take that and multiply it by the IETF population you get .005 expected deaths within the IETF for the entire week.
>
> Now you're using the "at least one" criteria, which works out to be 1-(1-.0000051)^1000 = .005 or .5% of at least one person dying in the week so your numbers are somewhat reasonable, but don't actually mean anything.  E.g this is basically the birthday paradox which grows the probability quickly with the size of the set.
>
>   I'll give you an example.  The death rate per 1000 in Germany per year for all causes is about 11.  That works out to about a 20% chance of at least one person dying in the IETF during the week from all causes including murder if we all lived in Germany.   The equivalent statistic for the US is 8 per 1000 which works out to 15% for the IETF for the week.  But we don't seem to be dropping at anywhere close to that rate ( e.g. A death at the meting every 5 meetings).
>
> Death probabilities are *highly* dependent on the specific populations you're looking at and actuaries get paid a lot of money to calculate them.  The actual probabilities for the IETF would benefit from affluence, age, medical care, education, location, etc.
>
> Mike
>
>
>
> Sent from my iPad
>
>>> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
>>>
>>> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
>>>
>>> .005 deaths per week per 1000
>> Right, the 270 micromorts per year (~ 5 micromorts per week) you cited would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting killed — a factor three less than the 1.5 % that my numbers result in, but not off by a large factor.
>> (Still, I wonder where that factor three comes from.)
>>
>> Luckily, we hit the other 98.5 % this week.
>>
>> (I’m not that worried by the ~ 15 micromorts of risk I personally was subjected to, given that I spent on the order of 250 microlives for the time that went into this meeting.
>> But my wife, who had been planning our wonderful vacation in Colombia earlier this year, definitely was.)
>>
>> Grüße, Carsten
>>


From nobody Wed Apr  5 08:14:02 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09DC512947E for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 08:13:53 -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 ECvP39hJ6nP8 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 08:13:51 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::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 24AE812945C for <ietf@ietf.org>; Wed,  5 Apr 2017 08:13:51 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id x125so9555802pgb.0 for <ietf@ietf.org>; Wed, 05 Apr 2017 08:13:51 -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=AGwO4a0Lirr2M0dSHr/nLH0QOh0yVwcst4WiAwZYjuw=; b=ATIyu7ck6277FdYnB+zK35dvgCue+BRVGcgeY/knh2nqgBg3fCPC+o5ndo84R+Nl14 UzOPA5ZFQZUOEWECp1Y4uaANvIZF82K/x2Ze8FxumBWnsGh/CPdCsoYXV8wh+NoT5d73 IyjIrhQ7ZjqFfaY88Y9ZRSeNoox8/yrHyViFgDJKULbJhPpurCd63TVNBZc1x6GSr8xB qRjJZT06CG0Wdh/iHaEl3z43+IpZ9lCQROOJS/iJlR0MObAlVK9G6HCbcaYccWDMpZhw gl8QgsD5RMxYDsntBszzOY0Dh9Jrxzh61ntd58LIbegnBTx3ge3n4BicDgHu54Vdfef4 sNiA==
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=AGwO4a0Lirr2M0dSHr/nLH0QOh0yVwcst4WiAwZYjuw=; b=fJjzpUP0vHhdeUp/DqZiuFCpCoe4Uz+6Emq3gpLEiGzH8Ycy2uFLzo+6GNpPFmg5t1 e0o3J2+Uaa9HqrYxt9dsKNEKEHPGHeg9kp3al6L9NdCItoN+Op7qwDG8jGee3DrDODgH 6bP5NFOQp/X20yBmlFL+Ke5aRVL5H3AcJB2uncu8959w+G9g8jwkQpHqNHwdBM4CWXQ5 B5+9XRE/k6341wieJpODkN4UR2rmcUnyf4tw5jQzGquY4+Rvk4/L2ZK44QYsQtJUQv8A godB8H5rK3zQpgeP3zAtkQT1kPiK/50kHv9xCgR7+RqqV/8khXcXB20nbMm1j3G+2Rfy 3fPQ==
X-Gm-Message-State: AFeK/H0HsFEAfkev62XsnmAR/CEyAYtT+O2rglUTc2cUIt+0IfFV3q8g8n9OwY5VrXph9g==
X-Received: by 10.98.86.71 with SMTP id k68mr28721317pfb.215.1491405230795; Wed, 05 Apr 2017 08:13:50 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:e4bc:4cc2:2258:7a5? ([2601:647:4d01:db10:e4bc:4cc2:2258:7a5]) by smtp.gmail.com with ESMTPSA id b74sm38233247pfd.90.2017.04.05.08.13.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Apr 2017 08:13:49 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <F51651E3-7668-4D00-8879-979680E19E38@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3467AF1C-5239-46C2-87FF-1533962550C9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Wed, 5 Apr 2017 08:13:47 -0700
In-Reply-To: <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Michael StJohns <mstjohns@comcast.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org> <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net> <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WovgDC5MVSIs2iBbR3YLac2OZOw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 15:13:53 -0000

--Apple-Mail=_3467AF1C-5239-46C2-87FF-1533962550C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Apr 5, 2017, at 7:26 AM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
> I meant to include (damn iPad):
>=20
> Carsten's original email was
>> Statistically, the chance of any IETFer being killed last week was =
about 1.5 %.
>=20
> "Any IETFer being killed" (I read the above as "Any [given] IETFer")  =
is the .00051% chance.  "At least one IETFer" is the .5% chance.  =
"Anyone in the IETF" could mean either - precision is important and I =
still don't actually know which Carsten meant.

I am happy that no IETFer got killed.  We did have some heated debates =
:-)

Bob



--Apple-Mail=_3467AF1C-5239-46C2-87FF-1533962550C9
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-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJY5QmsAAoJEK7rdBF357uoyhYH/1uC/H5fI13axX61rWAAUaKI
eQvzIqBbGq5s0n6LaPgBF3QtMGfupN1Dx/LO50Ggm9u3zgFPyIGDBKu1n18hssuR
N1djOEc0J2dLp2nGcd3iYAB6+RzL+zON6DzT/ud6DVOgb97GIFU7DOpkbZzCugld
bYfMltSwvbs8zLeTGJII4Y05b39SRhg2q3rLlx80cg32d9rzBHIk6WrdlJ501Z0U
wiQlgRNj6EjdiLxjnW+FMSuYtsLJGNm+PJKfrkrKbVvVSEhj07Py4vObYJPpXeRo
bh1LCfKCqobzJyYnesOiRkMuz2ZPJUnoDFRrblGeRPDBxerfgDg20H7mY3SYgUw=
=Z5xW
-----END PGP SIGNATURE-----

--Apple-Mail=_3467AF1C-5239-46C2-87FF-1533962550C9--


From nobody Wed Apr  5 08:17:17 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7017E129447 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 08:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 xAD3V-HiHltS for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 08:17:13 -0700 (PDT)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (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 6854312941C for <ietf@ietf.org>; Wed,  5 Apr 2017 08:17:13 -0700 (PDT)
Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-06v.sys.comcast.net with SMTP id vmfTcYwF8bempvmgKc4roM; Wed, 05 Apr 2017 15:17:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1491405432; bh=3RY1RaIVAawEHznqITkqwNXQFXXG2uAIB0kfO2hcvEM=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Paurdhr3LGVJLSgenMUsgyU7vOkuf2Ou6u4H6kpE1b8+W8EXK3Navc/OA3+ecaXLP bA9xkCVcT181tBQwbOA7jCZDRPY+jcM+VIg1wkHfGYpNb4B6DcNJg/E1yu6yRfmam1 SEHEOHfQWuLinBAMFR5sZCO2yh/0OQRP65Tdu6fy1wCov2B95Nn+EGMzbf0k5ar5lB n50IYqtCEVbl2TnvWk7kj6+ZiClJUQE6UKofeu9rVJjbIMkRCZWFytd2ob0n6DyIcf d8aS/oTR0jYdoURzvl2PEMTogylukqE2dQm/YrdwEyj5v7nsVlkD4mKqAsJQJB9wB/ p01t3VPgHWS2g==
Received: from [IPv6:2601:152:4400:a2e0::1594] ([IPv6:2601:152:4400:a2e0::1594]) by resomta-po-01v.sys.comcast.net with SMTP id vmgJcSa7pPheQvmgJcTsIm; Wed, 05 Apr 2017 15:17:12 +0000
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Bob Hinden <bob.hinden@gmail.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org> <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net> <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net> <F51651E3-7668-4D00-8879-979680E19E38@gmail.com>
Cc: IETF <ietf@ietf.org>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <421b15b4-628c-d790-3c08-ce72cf725ab9@comcast.net>
Date: Wed, 5 Apr 2017 11:17:29 -0400
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: <F51651E3-7668-4D00-8879-979680E19E38@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfKv+F/BpDmLBnBfZa34UIyzLguViYOu4gw+ot6qYHdwj+mgao6WtH0GLgfHJR+ihHK9sMZ6TxBTSdkFgVoi9krJFarI2fS+fzYPxNe+ZoGFZP8WS3TLZ ZF+3zeM/B7UUlu1R74a1rhLzlQ9ykNYQX6kH7E1VWNg517hAF5bm0RDUn/eaqevOSRi9zRHkM+LmiwNaiDNSjPwao15jSqNUsaU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TgfqRVT9SfARXIoMPep52UPxPVY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 15:17:15 -0000

On 4/5/2017 11:13 AM, Bob Hinden wrote:
>
> I am happy that no IETFer got killed.  We did have some heated debates :-)
>
> Bob
>
>
I once saw Dave Clark after a particularly contentious side meeting at 
an early IETF and said that I was glad I didn't see blood. His response 
was classic Dave: "It was the kind of meeting where the only blood came 
from biting your tongue."

Mike

The IETF - 30 years of Standards by Combat!


From nobody Wed Apr  5 10:24:26 2017
Return-Path: <zack@cloudbakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECBD12948F for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:24:11 -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, DKIM_SIGNED=0.1, DKIM_VALID=-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 (2048-bit key) header.d=cloudbakers-net.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 QriihM7jZ4Zd for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:24:05 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 487E21287A7 for <ietf@ietf.org>; Wed,  5 Apr 2017 10:24:04 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id w11so22782306wrc.3 for <ietf@ietf.org>; Wed, 05 Apr 2017 10:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudbakers-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UOqakt3IxDrSyOM28iga2mNLwWrW18O08wBhBcRxSBw=; b=VN6pM/TgoJ8javhRJIcN3U0WtcVa8pIylqfmAQIDg9wpv0aqZeRjkWm/sT9Es6VuCY HkPAseUXXuET26B5z5YD798MQ2O87rJOX3YrewVaf37Vvw0JSIuE50+2vg9GPHdkbg+g ZYKbMFRYbFzpJxxt1rV0+m10m6QQo2W3SBKSMRETAbEHwePZVBTm3wC2ag1d2tlGEtf2 iBmOXUYclmZkSRsl8Ez7JQp0nJq03klONdVX4/cNutXejKDhqpMR43G/Gqow1hVLtxnW Rc/uCbzOjJ/PGR86Q04q7veg0I5+3kXxmFLbIYD5cUTQiPEy0AVv3PJ3oRTd4FoIiy1l 5cgA==
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=UOqakt3IxDrSyOM28iga2mNLwWrW18O08wBhBcRxSBw=; b=YiOwD786L9B6Jm1OVHDjBVp8wV0xoCQN5oDxYwGY1Wm5spVUepciqxFNXxnkp0umhO Ff3hNPnU3mUq6FPKQa0ITXYwGRdFKcr9TIEPBe9pwMKrc3vyweF549QDCKssw6/0W0Xr DBfxjCdTuxYeknUjt3AnTPZ9k2ys5dwz+qDz8HuPXmgVpox465l3NXu/GBTBfNxB6OBL C6L30jmyhIVjkFeSKsoPJyWYjG2Tuhti2R/8Qti5D6iycXYTXkivdlbk0BmIEpdSiGup X4v1aa9K5cckO3n6z4wT8fXLRcCPhh0HEr5LnWnPglBpZMTShycI6erF2Sn8NKborlfb D2zA==
X-Gm-Message-State: AFeK/H1E8izsoMsqioJMPMswBxrFt9abGibxrERJ9WdIpOr1IR8KPTo/9lWxDyyI02urYhLVbG9v4jC5WLhDpX9i9GNRet+q/9n5nzZzZj41ygwBX6LzyQbKe1znOyR+l9wizyQpHbfERcqSibny1Z7as48PyNAj67IJMFdHNJuKL03OaMoEzYOCueiJVha9yfNUn4ghJavClCD9ITy0GKLv3dzMcQI/mnL99/6eUbZG3coJGsBwokbw
X-Received: by 10.28.137.211 with SMTP id l202mr20678991wmd.118.1491413042219;  Wed, 05 Apr 2017 10:24:02 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.5562.1491405436.3760.ietf@ietf.org>
In-Reply-To: <mailman.5562.1491405436.3760.ietf@ietf.org>
From: Zack Cylinder <zack@cloudbakers.net>
Date: Wed, 05 Apr 2017 17:23:51 +0000
Message-ID: <CADc3KoKmfZuD03TtsX7iC=6jrvMe3LLJjjPy4eMX=iD-kEJajA@mail.gmail.com>
Subject: Re: ietf Digest, Vol 107, Issue 14
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114444969862d0054c6ea839
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TAdQGThOHePWYfQ4lxGEWhEqQTk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 17:24:12 -0000

--001a114444969862d0054c6ea839
Content-Type: text/plain; charset=UTF-8

Hey everyone,

Please see below and let me know if you have questions


On Wed, Apr 5, 2017 at 10:17 AM <ietf-request@ietf.org> wrote:

> Send ietf mailing list submissions to
>         ietf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
>         ietf-request@ietf.org
>
> You can reach the person managing the list at
>         ietf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ietf digest..."
>
>
> Today's Topics:
>
>    1. Re: IAOC requesting input on (potential) meeting cities
>       (Michael Richardson)
>    2. Re: IAOC requesting input on (potential) meeting cities
>       (Michael Richardson)
>    3. Re: IAOC requesting input on (potential) meeting cities
>       (mike stJohns)
>    4. Re: IAOC requesting input on (potential) meeting cities
>       (Michael StJohns)
>    5. Re: IAOC requesting input on (potential) meeting cities
>       (Bob Hinden)
>    6. Re: IAOC requesting input on (potential) meeting cities
>       (Michael StJohns)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 05 Apr 2017 09:23:14 -0400
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> To: IETF Discussion <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <6955.1491398594@obiwan.sandelman.ca>
> Content-Type: text/plain; charset="utf-8"
>
>
> Andrew G. Malis <agmalis@gmail.com> wrote:
>     > At least once, I was questioned extensively when going from the US to
>     > a meeting in Canada. I had to show evidence of the meeting and my
>     > itinerary and convince them that I wasn?t entering Canada to take
> work
>     > away from a Canadian. That said, I still support holding meetings in
>     > Canada.
>
> IETF98 was among the only times I was *NOT* asked questions like that when
> entering the US.   I did enter at Midway.   That none of are asked such
> questions when entering europe always surprises me.
>
> I'm not sure what "extensively" means; if that means you were taken aside,
> or
> not.  I've been through that at the US border.
>
> "Chair of work group" would always be a bad thing to say, since it has the
> word "work" in it.  Never talk about customers.  The IETF is a meeting of
> peers.
>
> (Once because it was 5am, and I was just really loud since I was really
> still
> asleep).
>
> But, in all cases I felt confident that I would be treated with respect,
> (even by the border guard who didn't seem to believe that e-tickets were
> real).
>
> I did *not* feel that way while preparing to travel to IETF98.
> My fears were not realized; but as Eliot has said, it's *exactly* the
> uncertainty that is a problem.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 487 bytes
> Desc: not available
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/82807627/attachment.asc
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 05 Apr 2017 09:25:54 -0400
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> To: Jared Mauch <jared@puck.Nether.net>
> Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <7538.1491398754@obiwan.sandelman.ca>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Jared Mauch <jared@puck.Nether.net> wrote:
>     > On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wrote:
>     >> I agree that Canada is a fairly easy country to get in and out of
>     >> (unless you have a DUI arrest) but it varies a lot so anecdotes
> about
>     >> entering Canada or any other country don't tell you much.
>
>     > Agreed.  When I received my NEXUS card they explicity told me
>     > if I was traveling to a conference and was presenting that I would
>     > require additional paperwork, possibly including a letter of
> invitation,
>     > and/or a visa.  I presume if I were presenting at an IETF WG I would
>     > check the appropriate box when registering as well and I would get
>     > the paperwork.
>
> No!  Only if you have been paid to present.
>      i.e. you are Al Gore coming to talk at the Air Canada center in
> Toronto.
>
> We don't do presentations like that at the IETF.
> The IETF is not like most non-technical "conferences".
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 487 bytes
> Desc: not available
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/7bafa802/attachment.asc
> >
>
> ------------------------------
>
> Message: 3
> Date: Wed, 5 Apr 2017 09:49:54 -0400
> From: mike stJohns <mstjohns@comcast.net>
> To: Carsten Bormann <cabo@tzi.org>
> Cc: IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net>
> Content-Type: text/plain;       charset=utf-8
>
> Let's try this one more time
>
>
> 27 deaths in 100 would be 27%
> 27 deaths in 1000 would be 2.7%
> 27 deaths in 10000 would be .27%
> 27 deaths in 100000 would be a rate of .027%
> The above are all expected deaths per year for the given population - so
> divide .027% by 52 to get .00051% per week.  That's roughly the chance per
> individual to die during the week from murder.   That's *my* risk for a
> week of the IETF and that's what should matter to each individual.
>
> If you take that and multiply it by the IETF population you get .005
> expected deaths within the IETF for the entire week.
>
> Now you're using the "at least one" criteria, which works out to be
> 1-(1-.0000051)^1000 = .005 or .5% of at least one person dying in the week
> so your numbers are somewhat reasonable, but don't actually mean anything.
> E.g this is basically the birthday paradox which grows the probability
> quickly with the size of the set.
>
>  I'll give you an example.  The death rate per 1000 in Germany per year
> for all causes is about 11.  That works out to about a 20% chance of at
> least one person dying in the IETF during the week from all causes
> including murder if we all lived in Germany.   The equivalent statistic for
> the US is 8 per 1000 which works out to 15% for the IETF for the week.  But
> we don't seem to be dropping at anywhere close to that rate ( e.g. A death
> at the meting every 5 meetings).
>
> Death probabilities are *highly* dependent on the specific populations
> you're looking at and actuaries get paid a lot of money to calculate them.
> The actual probabilities for the IETF would benefit from affluence, age,
> medical care, education, location, etc.
>
> Mike
>
>
>
> Sent from my iPad
>
> >> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
> >>
> >> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
> >>
> >> .005 deaths per week per 1000
> >
> > Right, the 270 micromorts per year (~ 5 micromorts per week) you cited
> would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting
> killed ? a factor three less than the 1.5 % that my numbers result in, but
> not off by a large factor.
> > (Still, I wonder where that factor three comes from.)
> >
> > Luckily, we hit the other 98.5 % this week.
> >
> > (I?m not that worried by the ~ 15 micromorts of risk I personally was
> subjected to, given that I spent on the order of 250 microlives for the
> time that went into this meeting.
> > But my wife, who had been planning our wonderful vacation in Colombia
> earlier this year, definitely was.)
> >
> > Gr??e, Carsten
> >
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 5 Apr 2017 10:26:20 -0400
> From: Michael StJohns <mstjohns@comcast.net>
> To: ietf@ietf.org
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> I meant to include (damn iPad):
>
> Carsten's original email was
> > Statistically, the chance of any IETFer being killed last week was about
> 1.5 %.
>
> "Any IETFer being killed" (I read the above as "Any [given] IETFer")  is
> the .00051% chance.  "At least one IETFer" is the .5% chance.  "Anyone
> in the IETF" could mean either - precision is important and I still
> don't actually know which Carsten meant.
>
> Later, Mike
>
> On 4/5/2017 9:49 AM, mike stJohns wrote:
> > Let's try this one more time
> >
> >
> > 27 deaths in 100 would be 27%
> > 27 deaths in 1000 would be 2.7%
> > 27 deaths in 10000 would be .27%
> > 27 deaths in 100000 would be a rate of .027%
> > The above are all expected deaths per year for the given population - so
> divide .027% by 52 to get .00051% per week.  That's roughly the chance per
> individual to die during the week from murder.   That's *my* risk for a
> week of the IETF and that's what should matter to each individual.
> >
> > If you take that and multiply it by the IETF population you get .005
> expected deaths within the IETF for the entire week.
> >
> > Now you're using the "at least one" criteria, which works out to be
> 1-(1-.0000051)^1000 = .005 or .5% of at least one person dying in the week
> so your numbers are somewhat reasonable, but don't actually mean anything.
> E.g this is basically the birthday paradox which grows the probability
> quickly with the size of the set.
> >
> >   I'll give you an example.  The death rate per 1000 in Germany per year
> for all causes is about 11.  That works out to about a 20% chance of at
> least one person dying in the IETF during the week from all causes
> including murder if we all lived in Germany.   The equivalent statistic for
> the US is 8 per 1000 which works out to 15% for the IETF for the week.  But
> we don't seem to be dropping at anywhere close to that rate ( e.g. A death
> at the meting every 5 meetings).
> >
> > Death probabilities are *highly* dependent on the specific populations
> you're looking at and actuaries get paid a lot of money to calculate them.
> The actual probabilities for the IETF would benefit from affluence, age,
> medical care, education, location, etc.
> >
> > Mike
> >
> >
> >
> > Sent from my iPad
> >
> >>> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
> >>>
> >>> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
> >>>
> >>> .005 deaths per week per 1000
> >> Right, the 270 micromorts per year (~ 5 micromorts per week) you cited
> would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting
> killed ? a factor three less than the 1.5 % that my numbers result in, but
> not off by a large factor.
> >> (Still, I wonder where that factor three comes from.)
> >>
> >> Luckily, we hit the other 98.5 % this week.
> >>
> >> (I?m not that worried by the ~ 15 micromorts of risk I personally was
> subjected to, given that I spent on the order of 250 microlives for the
> time that went into this meeting.
> >> But my wife, who had been planning our wonderful vacation in Colombia
> earlier this year, definitely was.)
> >>
> >> Gr??e, Carsten
> >>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 5 Apr 2017 08:13:47 -0700
> From: Bob Hinden <bob.hinden@gmail.com>
> To: Michael StJohns <mstjohns@comcast.net>
> Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <F51651E3-7668-4D00-8879-979680E19E38@gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
> > On Apr 5, 2017, at 7:26 AM, Michael StJohns <mstjohns@comcast.net>
> wrote:
> >
> > I meant to include (damn iPad):
> >
> > Carsten's original email was
> >> Statistically, the chance of any IETFer being killed last week was
> about 1.5 %.
> >
> > "Any IETFer being killed" (I read the above as "Any [given] IETFer")  is
> the .00051% chance.  "At least one IETFer" is the .5% chance.  "Anyone in
> the IETF" could mean either - precision is important and I still don't
> actually know which Carsten meant.
>
> I am happy that no IETFer got killed.  We did have some heated debates :-)
>
> Bob
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 496 bytes
> Desc: Message signed with OpenPGP
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/f09b94af/attachment.asc
> >
>
> ------------------------------
>
> Message: 6
> Date: Wed, 5 Apr 2017 11:17:29 -0400
> From: Michael StJohns <mstjohns@comcast.net>
> To: Bob Hinden <bob.hinden@gmail.com>
> Cc: IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <421b15b4-628c-d790-3c08-ce72cf725ab9@comcast.net>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 4/5/2017 11:13 AM, Bob Hinden wrote:
> >
> > I am happy that no IETFer got killed.  We did have some heated debates
> :-)
> >
> > Bob
> >
> >
> I once saw Dave Clark after a particularly contentious side meeting at
> an early IETF and said that I was glad I didn't see blood. His response
> was classic Dave: "It was the kind of meeting where the only blood came
> from biting your tongue."
>
> Mike
>
> The IETF - 30 years of Standards by Combat!
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ietf mailing list
> ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> ------------------------------
>
> End of ietf Digest, Vol 107, Issue 14
> *************************************
>
-- 
Zack Cylinder
Cloudbakers
Cloud Training Specialist

--001a114444969862d0054c6ea839
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Hey everyone,=C2=A0</div><div><br></div><div>Please see below and let =
me know if you have questions=C2=A0</div><div><br></div><div><br><div class=
=3D"gmail_quote"><div>On Wed, Apr 5, 2017 at 10:17 AM &lt;<a href=3D"mailto=
:ietf-request@ietf.org">ietf-request@ietf.org</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Send ietf mailing list submissions to<br class=3D=
"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf@ietf.org" class=3D"gmail=
_msg" target=3D"_blank">ietf@ietf.org</a><br class=3D"gmail_msg">
<br class=3D"gmail_msg">
To subscribe or unsubscribe via the World Wide Web, visit<br class=3D"gmail=
_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinf=
o/ietf" rel=3D"noreferrer" class=3D"gmail_msg" target=3D"_blank">https://ww=
w.ietf.org/mailman/listinfo/ietf</a><br class=3D"gmail_msg">
or, via email, send a message with subject or body &#39;help&#39; to<br cla=
ss=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf-request@ietf.org" class=
=3D"gmail_msg" target=3D"_blank">ietf-request@ietf.org</a><br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
You can reach the person managing the list at<br class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf-owner@ietf.org" class=3D=
"gmail_msg" target=3D"_blank">ietf-owner@ietf.org</a><br class=3D"gmail_msg=
">
<br class=3D"gmail_msg">
When replying, please edit your Subject line so it is more specific<br clas=
s=3D"gmail_msg">
than &quot;Re: Contents of ietf digest...&quot;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Today&#39;s Topics:<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0 =C2=A01. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael Richardson)<br class=3D"gmail_msg">
=C2=A0 =C2=A02. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael Richardson)<br class=3D"gmail_msg">
=C2=A0 =C2=A03. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (mike stJohns)<br class=3D"gmail_msg">
=C2=A0 =C2=A04. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael StJohns)<br class=3D"gmail_msg">
=C2=A0 =C2=A05. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Bob Hinden)<br class=3D"gmail_msg">
=C2=A0 =C2=A06. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael StJohns)<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
----------------------------------------------------------------------<br c=
lass=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 1<br class=3D"gmail_msg">
Date: Wed, 05 Apr 2017 09:23:14 -0400<br class=3D"gmail_msg">
From: Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca" cla=
ss=3D"gmail_msg" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;<br class=
=3D"gmail_msg">
To: IETF Discussion &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg=
" target=3D"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:6955.1491398594@obiwan.sandelman.ca" clas=
s=3D"gmail_msg" target=3D"_blank">6955.1491398594@obiwan.sandelman.ca</a>&g=
t;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br class=3D"gmail_msg=
">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Andrew G. Malis &lt;<a href=3D"mailto:agmalis@gmail.com" class=3D"gmail_msg=
" target=3D"_blank">agmalis@gmail.com</a>&gt; wrote:<br class=3D"gmail_msg"=
>
=C2=A0 =C2=A0 &gt; At least once, I was questioned extensively when going f=
rom the US to<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; a meeting in Canada. I had to show evidence of the meeti=
ng and my<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; itinerary and convince them that I wasn?t entering Canad=
a to take work<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; away from a Canadian. That said, I still support holding=
 meetings in<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; Canada.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
IETF98 was among the only times I was *NOT* asked questions like that when<=
br class=3D"gmail_msg">
entering the US.=C2=A0 =C2=A0I did enter at Midway.=C2=A0 =C2=A0That none o=
f are asked such<br class=3D"gmail_msg">
questions when entering europe always surprises me.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I&#39;m not sure what &quot;extensively&quot; means; if that means you were=
 taken aside, or<br class=3D"gmail_msg">
not.=C2=A0 I&#39;ve been through that at the US border.<br class=3D"gmail_m=
sg">
<br class=3D"gmail_msg">
&quot;Chair of work group&quot; would always be a bad thing to say, since i=
t has the<br class=3D"gmail_msg">
word &quot;work&quot; in it.=C2=A0 Never talk about customers.=C2=A0 The IE=
TF is a meeting of<br class=3D"gmail_msg">
peers.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
(Once because it was 5am, and I was just really loud since I was really sti=
ll<br class=3D"gmail_msg">
asleep).<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
But, in all cases I felt confident that I would be treated with respect,<br=
 class=3D"gmail_msg">
(even by the border guard who didn&#39;t seem to believe that e-tickets wer=
e<br class=3D"gmail_msg">
real).<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I did *not* feel that way while preparing to travel to IETF98.<br class=3D"=
gmail_msg">
My fears were not realized; but as Eliot has said, it&#39;s *exactly* the<b=
r class=3D"gmail_msg">
uncertainty that is a problem.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
--<br class=3D"gmail_msg">
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" class=3D"=
gmail_msg" target=3D"_blank">mcr+IETF@sandelman.ca</a>&gt;, Sandelman Softw=
are Works<br class=3D"gmail_msg">
=C2=A0-=3D IPv6 IoT consulting =3D-<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 487 bytes<br class=3D"gmail_msg">
Desc: not available<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/82807627/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/82807627/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 2<br class=3D"gmail_msg">
Date: Wed, 05 Apr 2017 09:25:54 -0400<br class=3D"gmail_msg">
From: Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca" cla=
ss=3D"gmail_msg" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;<br class=
=3D"gmail_msg">
To: Jared Mauch &lt;<a href=3D"mailto:jared@puck.Nether.net" class=3D"gmail=
_msg" target=3D"_blank">jared@puck.Nether.net</a>&gt;<br class=3D"gmail_msg=
">
Cc: John Levine &lt;<a href=3D"mailto:johnl@taugh.com" class=3D"gmail_msg" =
target=3D"_blank">johnl@taugh.com</a>&gt;, <a href=3D"mailto:ietf@ietf.org"=
 class=3D"gmail_msg" target=3D"_blank">ietf@ietf.org</a><br class=3D"gmail_=
msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:7538.1491398754@obiwan.sandelman.ca" clas=
s=3D"gmail_msg" target=3D"_blank">7538.1491398754@obiwan.sandelman.ca</a>&g=
t;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br class=3D"gmail_=
msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Jared Mauch &lt;<a href=3D"mailto:jared@puck.Nether.net" class=3D"gmail_msg=
" target=3D"_blank">jared@puck.Nether.net</a>&gt; wrote:<br class=3D"gmail_=
msg">
=C2=A0 =C2=A0 &gt; On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wr=
ote:<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; I agree that Canada is a fairly easy country to get =
in and out of<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; (unless you have a DUI arrest) but it varies a lot s=
o anecdotes about<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; entering Canada or any other country don&#39;t tell =
you much.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; Agreed.=C2=A0 When I received my NEXUS card they explici=
ty told me<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; if I was traveling to a conference and was presenting th=
at I would<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; require additional paperwork, possibly including a lette=
r of invitation,<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; and/or a visa.=C2=A0 I presume if I were presenting at a=
n IETF WG I would<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; check the appropriate box when registering as well and I=
 would get<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; the paperwork.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
No!=C2=A0 Only if you have been paid to present.<br class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0i.e. you are Al Gore coming to talk at the Air Canada c=
enter in Toronto.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
We don&#39;t do presentations like that at the IETF.<br class=3D"gmail_msg"=
>
The IETF is not like most non-technical &quot;conferences&quot;.<br class=
=3D"gmail_msg">
<br class=3D"gmail_msg">
--<br class=3D"gmail_msg">
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" class=3D"=
gmail_msg" target=3D"_blank">mcr+IETF@sandelman.ca</a>&gt;, Sandelman Softw=
are Works<br class=3D"gmail_msg">
=C2=A0-=3D IPv6 IoT consulting =3D-<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 487 bytes<br class=3D"gmail_msg">
Desc: not available<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/7bafa802/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/7bafa802/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 3<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 09:49:54 -0400<br class=3D"gmail_msg">
From: mike stJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"gma=
il_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail_ms=
g">
To: Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" class=3D"gmail_msg"=
 target=3D"_blank">cabo@tzi.org</a>&gt;<br class=3D"gmail_msg">
Cc: IETF &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D=
"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:620C9C4C-413C-439C-9109-B30BBAB921B1@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">620C9C4C-413C-439C-9109-B30B=
BAB921B1@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain;=C2=A0 =C2=A0 =C2=A0 =C2=A0charset=3Dutf-8<br clas=
s=3D"gmail_msg">
<br class=3D"gmail_msg">
Let&#39;s try this one more time<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
27 deaths in 100 would be 27%<br class=3D"gmail_msg">
27 deaths in 1000 would be 2.7%<br class=3D"gmail_msg">
27 deaths in 10000 would be .27%<br class=3D"gmail_msg">
27 deaths in 100000 would be a rate of .027%<br class=3D"gmail_msg">
The above are all expected deaths per year for the given population - so di=
vide .027% by 52 to get .00051% per week.=C2=A0 That&#39;s roughly the chan=
ce per individual to die during the week from murder.=C2=A0 =C2=A0That&#39;=
s *my* risk for a week of the IETF and that&#39;s what should matter to eac=
h individual.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
If you take that and multiply it by the IETF population you get .005 expect=
ed deaths within the IETF for the entire week.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Now you&#39;re using the &quot;at least one&quot; criteria, which works out=
 to be 1-(1-.0000051)^1000 =3D .005 or .5% of at least one person dying in =
the week so your numbers are somewhat reasonable, but don&#39;t actually me=
an anything.=C2=A0 E.g this is basically the birthday paradox which grows t=
he probability quickly with the size of the set.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0I&#39;ll give you an example.=C2=A0 The death rate per 1000 in German=
y per year for all causes is about 11.=C2=A0 That works out to about a 20% =
chance of at least one person dying in the IETF during the week from all ca=
uses including murder if we all lived in Germany.=C2=A0 =C2=A0The equivalen=
t statistic for the US is 8 per 1000 which works out to 15% for the IETF fo=
r the week.=C2=A0 But we don&#39;t seem to be dropping at anywhere close to=
 that rate ( e.g. A death at the meting every 5 meetings).<br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
Death probabilities are *highly* dependent on the specific populations you&=
#39;re looking at and actuaries get paid a lot of money to calculate them.=
=C2=A0 The actual probabilities for the IETF would benefit from affluence, =
age, medical care, education, location, etc.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Sent from my iPad<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&gt;&gt; On Apr 5, 2017, at 01:56, Carsten Bormann &lt;<a href=3D"mailto:ca=
bo@tzi.org" class=3D"gmail_msg" target=3D"_blank">cabo@tzi.org</a>&gt; wrot=
e:<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; On Apr 5, 2017, at 01:06, mike stJohns &lt;<a href=3D"mailto:mstjo=
hns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast.net=
</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; .005 deaths per week per 1000<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Right, the 270 micromorts per year (~ 5 micromorts per week) you cited=
 would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting kil=
led ? a factor three less than the 1.5 % that my numbers result in, but not=
 off by a large factor.<br class=3D"gmail_msg">
&gt; (Still, I wonder where that factor three comes from.)<br class=3D"gmai=
l_msg">
&gt;<br class=3D"gmail_msg">
&gt; Luckily, we hit the other 98.5 % this week.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; (I?m not that worried by the ~ 15 micromorts of risk I personally was =
subjected to, given that I spent on the order of 250 microlives for the tim=
e that went into this meeting.<br class=3D"gmail_msg">
&gt; But my wife, who had been planning our wonderful vacation in Colombia =
earlier this year, definitely was.)<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Gr??e, Carsten<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 4<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 10:26:20 -0400<br class=3D"gmail_msg">
From: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"=
gmail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail=
_msg">
To: <a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">=
ietf@ietf.org</a><br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">cd5a3b9d-29dd-0d8b-b0a4-2a24=
65ea89b1@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed<br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
I meant to include (damn iPad):<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Carsten&#39;s original email was<br class=3D"gmail_msg">
&gt; Statistically, the chance of any IETFer being killed last week was abo=
ut 1.5 %.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&quot;Any IETFer being killed&quot; (I read the above as &quot;Any [given] =
IETFer&quot;)=C2=A0 is<br class=3D"gmail_msg">
the .00051% chance.=C2=A0 &quot;At least one IETFer&quot; is the .5% chance=
.=C2=A0 &quot;Anyone<br class=3D"gmail_msg">
in the IETF&quot; could mean either - precision is important and I still<br=
 class=3D"gmail_msg">
don&#39;t actually know which Carsten meant.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Later, Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
On 4/5/2017 9:49 AM, mike stJohns wrote:<br class=3D"gmail_msg">
&gt; Let&#39;s try this one more time<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; 27 deaths in 100 would be 27%<br class=3D"gmail_msg">
&gt; 27 deaths in 1000 would be 2.7%<br class=3D"gmail_msg">
&gt; 27 deaths in 10000 would be .27%<br class=3D"gmail_msg">
&gt; 27 deaths in 100000 would be a rate of .027%<br class=3D"gmail_msg">
&gt; The above are all expected deaths per year for the given population - =
so divide .027% by 52 to get .00051% per week.=C2=A0 That&#39;s roughly the=
 chance per individual to die during the week from murder.=C2=A0 =C2=A0That=
&#39;s *my* risk for a week of the IETF and that&#39;s what should matter t=
o each individual.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; If you take that and multiply it by the IETF population you get .005 e=
xpected deaths within the IETF for the entire week.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Now you&#39;re using the &quot;at least one&quot; criteria, which work=
s out to be 1-(1-.0000051)^1000 =3D .005 or .5% of at least one person dyin=
g in the week so your numbers are somewhat reasonable, but don&#39;t actual=
ly mean anything.=C2=A0 E.g this is basically the birthday paradox which gr=
ows the probability quickly with the size of the set.<br class=3D"gmail_msg=
">
&gt;<br class=3D"gmail_msg">
&gt;=C2=A0 =C2=A0I&#39;ll give you an example.=C2=A0 The death rate per 100=
0 in Germany per year for all causes is about 11.=C2=A0 That works out to a=
bout a 20% chance of at least one person dying in the IETF during the week =
from all causes including murder if we all lived in Germany.=C2=A0 =C2=A0Th=
e equivalent statistic for the US is 8 per 1000 which works out to 15% for =
the IETF for the week.=C2=A0 But we don&#39;t seem to be dropping at anywhe=
re close to that rate ( e.g. A death at the meting every 5 meetings).<br cl=
ass=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Death probabilities are *highly* dependent on the specific populations=
 you&#39;re looking at and actuaries get paid a lot of money to calculate t=
hem.=C2=A0 The actual probabilities for the IETF would benefit from affluen=
ce, age, medical care, education, location, etc.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Mike<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Sent from my iPad<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; On Apr 5, 2017, at 01:56, Carsten Bormann &lt;<a href=3D"mailt=
o:cabo@tzi.org" class=3D"gmail_msg" target=3D"_blank">cabo@tzi.org</a>&gt; =
wrote:<br class=3D"gmail_msg">
&gt;&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; On Apr 5, 2017, at 01:06, mike stJohns &lt;<a href=3D"mailto:m=
stjohns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast=
.net</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; .005 deaths per week per 1000<br class=3D"gmail_msg">
&gt;&gt; Right, the 270 micromorts per year (~ 5 micromorts per week) you c=
ited would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting=
 killed ? a factor three less than the 1.5 % that my numbers result in, but=
 not off by a large factor.<br class=3D"gmail_msg">
&gt;&gt; (Still, I wonder where that factor three comes from.)<br class=3D"=
gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; Luckily, we hit the other 98.5 % this week.<br class=3D"gmail_msg"=
>
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; (I?m not that worried by the ~ 15 micromorts of risk I personally =
was subjected to, given that I spent on the order of 250 microlives for the=
 time that went into this meeting.<br class=3D"gmail_msg">
&gt;&gt; But my wife, who had been planning our wonderful vacation in Colom=
bia earlier this year, definitely was.)<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; Gr??e, Carsten<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 5<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 08:13:47 -0700<br class=3D"gmail_msg">
From: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail=
_msg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<br class=3D"gmail_msg"=
>
To: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"gm=
ail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail_m=
sg">
Cc: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail_m=
sg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;, IETF &lt;<a href=3D"mai=
lto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">ietf@ietf.org</a>&=
gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:F51651E3-7668-4D00-8879-979680E19E38@gmai=
l.com" class=3D"gmail_msg" target=3D"_blank">F51651E3-7668-4D00-8879-979680=
E19E38@gmail.com</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br class=3D"gmail_=
msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&gt; On Apr 5, 2017, at 7:26 AM, Michael StJohns &lt;<a href=3D"mailto:mstj=
ohns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast.ne=
t</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I meant to include (damn iPad):<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Carsten&#39;s original email was<br class=3D"gmail_msg">
&gt;&gt; Statistically, the chance of any IETFer being killed last week was=
 about 1.5 %.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; &quot;Any IETFer being killed&quot; (I read the above as &quot;Any [gi=
ven] IETFer&quot;)=C2=A0 is the .00051% chance.=C2=A0 &quot;At least one IE=
TFer&quot; is the .5% chance.=C2=A0 &quot;Anyone in the IETF&quot; could me=
an either - precision is important and I still don&#39;t actually know whic=
h Carsten meant.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I am happy that no IETFer got killed.=C2=A0 We did have some heated debates=
 :-)<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Bob<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 496 bytes<br class=3D"gmail_msg">
Desc: Message signed with OpenPGP<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/f09b94af/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/f09b94af/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 6<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 11:17:29 -0400<br class=3D"gmail_msg">
From: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"=
gmail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail=
_msg">
To: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail_m=
sg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<br class=3D"gmail_msg">
Cc: IETF &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D=
"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:421b15b4-628c-d790-3c08-ce72cf725ab9@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">421b15b4-628c-d790-3c08-ce72=
cf725ab9@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3Dwindows-1252; format=3Dflowed<br class=
=3D"gmail_msg">
<br class=3D"gmail_msg">
On 4/5/2017 11:13 AM, Bob Hinden wrote:<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I am happy that no IETFer got killed.=C2=A0 We did have some heated de=
bates :-)<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Bob<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
I once saw Dave Clark after a particularly contentious side meeting at<br c=
lass=3D"gmail_msg">
an early IETF and said that I was glad I didn&#39;t see blood. His response=
<br class=3D"gmail_msg">
was classic Dave: &quot;It was the kind of meeting where the only blood cam=
e<br class=3D"gmail_msg">
from biting your tongue.&quot;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
The IETF - 30 years of Standards by Combat!<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Subject: Digest Footer<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
_______________________________________________<br class=3D"gmail_msg">
ietf mailing list<br class=3D"gmail_msg">
<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">ietf=
@ietf.org</a><br class=3D"gmail_msg">
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" rel=3D"noreferrer" c=
lass=3D"gmail_msg" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
ietf</a><br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
End of ietf Digest, Vol 107, Issue 14<br class=3D"gmail_msg">
*************************************<br class=3D"gmail_msg">
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-smartmail=
=3D"gmail_signature"><div dir=3D"ltr">Zack Cylinder<br><div>Cloudbakers</di=
v><div>Cloud Training Specialist</div></div></div>

--001a114444969862d0054c6ea839--


From nobody Wed Apr  5 10:24:34 2017
Return-Path: <zack@cloudbakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A481287A7 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:24:11 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=cloudbakers-net.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 zNw7zKSfbrjj for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:24:05 -0700 (PDT)
Received: from mail-wr0-x246.google.com (mail-wr0-x246.google.com [IPv6:2a00:1450:400c:c0c::246]) (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 1C84A129408 for <ietf@ietf.org>; Wed,  5 Apr 2017 10:24:04 -0700 (PDT)
Received: by mail-wr0-x246.google.com with SMTP id f50so2667850wrf.7 for <ietf@ietf.org>; Wed, 05 Apr 2017 10:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudbakers-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UOqakt3IxDrSyOM28iga2mNLwWrW18O08wBhBcRxSBw=; b=yT/zTmI4lcDnkgbnC6RVk0ttPeB3ZZVlm6yhLidH2Gv8jQz54Gln9EQsx/i1WV53lH CplDybG8nK1WQZdoRfyz3O7XyQZsXifUXTuFQM9e3Kw8nDw4ps4YQU2CH903UISYGDOe lqGg/ggeacWuj8ge2RNCluoYtxRgvJ9tKmbLk7rnwd8o0O/hwXYeu2DJNQHAm5r9HOuQ OK4RC4G6nM5Nkovj8MaYSE2qjWAaKDB9eXFa1DkGBzh3UT9YhcFEHF1kUc1pyGTOs2Fw aRQWPUTTAVAAWxad9lnq641XCpz4XFrq5aHkYhJHJLpn2nxMtTfvacki/n/vY2gGnGFm K5tw==
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=UOqakt3IxDrSyOM28iga2mNLwWrW18O08wBhBcRxSBw=; b=B1EYFazIcM9T2Ab/hk7goAU/FP0Ri4qSld7IGnA1qSs8HTza2n/JzJ94yyAXIqXP0q lwMVaR7ZgC/Y6epbhd1zI5NaiXfi5Oza3zf26D/rluhbOKpiC6YAh8vwc0DKGvuY2pNc MJlDzK1ab9strjUlgudScs/0WY70KgBaMDPsb76QIuBdVutbcht0wNIkD5Rt0fYQohL0 1aMlnC1Ug2F0e7TBs9Tv8UghjC6up8qPIoV/VnWf0UDUMHu+oo41eydD9thSifqlK+yO xAssXgT8APLl+2dwusenhFMaqQz8andcfh144iCygnmijhgqKLq7OWV8/xj5vIXGWso7 Lh+Q==
X-Gm-Message-State: AFeK/H0qADgxmLqQpn1WPzr7pwmjaVKtYecIYx4yZgnYQ2F9Wb1zzEB3XvkdEmRiPVrbIwbtqUfawE+jvNgqn4U4vVzTDaMuz14VMrvvJV0cbVuU9xbLyIaf40d7OS36tkUhy160rwdEBRu39ZKsmcedf22xL2KDOz14BGvFnKEJM4ls9JnbRS39kM6PuZPglRbmLQ33uHg8+lH7oJ8tg/OxVmJ51oeDSbpW19AiljYfZoyaxF+FZDTu
X-Received: by 10.28.137.211 with SMTP id l202mr20679019wmd.118.1491413042583;  Wed, 05 Apr 2017 10:24:02 -0700 (PDT)
X-Received: by 10.28.137.211 with SMTP id l202mr20678991wmd.118.1491413042219;  Wed, 05 Apr 2017 10:24:02 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.5562.1491405436.3760.ietf@ietf.org>
In-Reply-To: <mailman.5562.1491405436.3760.ietf@ietf.org>
From: Zack Cylinder <zack@cloudbakers.net>
Date: Wed, 05 Apr 2017 17:23:51 +0000
Message-ID: <CADc3KoKmfZuD03TtsX7iC=6jrvMe3LLJjjPy4eMX=iD-kEJajA@mail.gmail.com>
Subject: [EMAIL FROM ZACK:] Re: ietf Digest, Vol 107, Issue 14
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114444969862d0054c6ea839
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TAdQGThOHePWYfQ4lxGEWhEqQTk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 17:24:12 -0000

--001a114444969862d0054c6ea839
Content-Type: text/plain; charset=UTF-8

Hey everyone,

Please see below and let me know if you have questions


On Wed, Apr 5, 2017 at 10:17 AM <ietf-request@ietf.org> wrote:

> Send ietf mailing list submissions to
>         ietf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
>         ietf-request@ietf.org
>
> You can reach the person managing the list at
>         ietf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ietf digest..."
>
>
> Today's Topics:
>
>    1. Re: IAOC requesting input on (potential) meeting cities
>       (Michael Richardson)
>    2. Re: IAOC requesting input on (potential) meeting cities
>       (Michael Richardson)
>    3. Re: IAOC requesting input on (potential) meeting cities
>       (mike stJohns)
>    4. Re: IAOC requesting input on (potential) meeting cities
>       (Michael StJohns)
>    5. Re: IAOC requesting input on (potential) meeting cities
>       (Bob Hinden)
>    6. Re: IAOC requesting input on (potential) meeting cities
>       (Michael StJohns)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 05 Apr 2017 09:23:14 -0400
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> To: IETF Discussion <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <6955.1491398594@obiwan.sandelman.ca>
> Content-Type: text/plain; charset="utf-8"
>
>
> Andrew G. Malis <agmalis@gmail.com> wrote:
>     > At least once, I was questioned extensively when going from the US to
>     > a meeting in Canada. I had to show evidence of the meeting and my
>     > itinerary and convince them that I wasn?t entering Canada to take
> work
>     > away from a Canadian. That said, I still support holding meetings in
>     > Canada.
>
> IETF98 was among the only times I was *NOT* asked questions like that when
> entering the US.   I did enter at Midway.   That none of are asked such
> questions when entering europe always surprises me.
>
> I'm not sure what "extensively" means; if that means you were taken aside,
> or
> not.  I've been through that at the US border.
>
> "Chair of work group" would always be a bad thing to say, since it has the
> word "work" in it.  Never talk about customers.  The IETF is a meeting of
> peers.
>
> (Once because it was 5am, and I was just really loud since I was really
> still
> asleep).
>
> But, in all cases I felt confident that I would be treated with respect,
> (even by the border guard who didn't seem to believe that e-tickets were
> real).
>
> I did *not* feel that way while preparing to travel to IETF98.
> My fears were not realized; but as Eliot has said, it's *exactly* the
> uncertainty that is a problem.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 487 bytes
> Desc: not available
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/82807627/attachment.asc
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 05 Apr 2017 09:25:54 -0400
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> To: Jared Mauch <jared@puck.Nether.net>
> Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <7538.1491398754@obiwan.sandelman.ca>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Jared Mauch <jared@puck.Nether.net> wrote:
>     > On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wrote:
>     >> I agree that Canada is a fairly easy country to get in and out of
>     >> (unless you have a DUI arrest) but it varies a lot so anecdotes
> about
>     >> entering Canada or any other country don't tell you much.
>
>     > Agreed.  When I received my NEXUS card they explicity told me
>     > if I was traveling to a conference and was presenting that I would
>     > require additional paperwork, possibly including a letter of
> invitation,
>     > and/or a visa.  I presume if I were presenting at an IETF WG I would
>     > check the appropriate box when registering as well and I would get
>     > the paperwork.
>
> No!  Only if you have been paid to present.
>      i.e. you are Al Gore coming to talk at the Air Canada center in
> Toronto.
>
> We don't do presentations like that at the IETF.
> The IETF is not like most non-technical "conferences".
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 487 bytes
> Desc: not available
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/7bafa802/attachment.asc
> >
>
> ------------------------------
>
> Message: 3
> Date: Wed, 5 Apr 2017 09:49:54 -0400
> From: mike stJohns <mstjohns@comcast.net>
> To: Carsten Bormann <cabo@tzi.org>
> Cc: IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <620C9C4C-413C-439C-9109-B30BBAB921B1@comcast.net>
> Content-Type: text/plain;       charset=utf-8
>
> Let's try this one more time
>
>
> 27 deaths in 100 would be 27%
> 27 deaths in 1000 would be 2.7%
> 27 deaths in 10000 would be .27%
> 27 deaths in 100000 would be a rate of .027%
> The above are all expected deaths per year for the given population - so
> divide .027% by 52 to get .00051% per week.  That's roughly the chance per
> individual to die during the week from murder.   That's *my* risk for a
> week of the IETF and that's what should matter to each individual.
>
> If you take that and multiply it by the IETF population you get .005
> expected deaths within the IETF for the entire week.
>
> Now you're using the "at least one" criteria, which works out to be
> 1-(1-.0000051)^1000 = .005 or .5% of at least one person dying in the week
> so your numbers are somewhat reasonable, but don't actually mean anything.
> E.g this is basically the birthday paradox which grows the probability
> quickly with the size of the set.
>
>  I'll give you an example.  The death rate per 1000 in Germany per year
> for all causes is about 11.  That works out to about a 20% chance of at
> least one person dying in the IETF during the week from all causes
> including murder if we all lived in Germany.   The equivalent statistic for
> the US is 8 per 1000 which works out to 15% for the IETF for the week.  But
> we don't seem to be dropping at anywhere close to that rate ( e.g. A death
> at the meting every 5 meetings).
>
> Death probabilities are *highly* dependent on the specific populations
> you're looking at and actuaries get paid a lot of money to calculate them.
> The actual probabilities for the IETF would benefit from affluence, age,
> medical care, education, location, etc.
>
> Mike
>
>
>
> Sent from my iPad
>
> >> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
> >>
> >> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
> >>
> >> .005 deaths per week per 1000
> >
> > Right, the 270 micromorts per year (~ 5 micromorts per week) you cited
> would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting
> killed ? a factor three less than the 1.5 % that my numbers result in, but
> not off by a large factor.
> > (Still, I wonder where that factor three comes from.)
> >
> > Luckily, we hit the other 98.5 % this week.
> >
> > (I?m not that worried by the ~ 15 micromorts of risk I personally was
> subjected to, given that I spent on the order of 250 microlives for the
> time that went into this meeting.
> > But my wife, who had been planning our wonderful vacation in Colombia
> earlier this year, definitely was.)
> >
> > Gr??e, Carsten
> >
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 5 Apr 2017 10:26:20 -0400
> From: Michael StJohns <mstjohns@comcast.net>
> To: ietf@ietf.org
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comcast.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> I meant to include (damn iPad):
>
> Carsten's original email was
> > Statistically, the chance of any IETFer being killed last week was about
> 1.5 %.
>
> "Any IETFer being killed" (I read the above as "Any [given] IETFer")  is
> the .00051% chance.  "At least one IETFer" is the .5% chance.  "Anyone
> in the IETF" could mean either - precision is important and I still
> don't actually know which Carsten meant.
>
> Later, Mike
>
> On 4/5/2017 9:49 AM, mike stJohns wrote:
> > Let's try this one more time
> >
> >
> > 27 deaths in 100 would be 27%
> > 27 deaths in 1000 would be 2.7%
> > 27 deaths in 10000 would be .27%
> > 27 deaths in 100000 would be a rate of .027%
> > The above are all expected deaths per year for the given population - so
> divide .027% by 52 to get .00051% per week.  That's roughly the chance per
> individual to die during the week from murder.   That's *my* risk for a
> week of the IETF and that's what should matter to each individual.
> >
> > If you take that and multiply it by the IETF population you get .005
> expected deaths within the IETF for the entire week.
> >
> > Now you're using the "at least one" criteria, which works out to be
> 1-(1-.0000051)^1000 = .005 or .5% of at least one person dying in the week
> so your numbers are somewhat reasonable, but don't actually mean anything.
> E.g this is basically the birthday paradox which grows the probability
> quickly with the size of the set.
> >
> >   I'll give you an example.  The death rate per 1000 in Germany per year
> for all causes is about 11.  That works out to about a 20% chance of at
> least one person dying in the IETF during the week from all causes
> including murder if we all lived in Germany.   The equivalent statistic for
> the US is 8 per 1000 which works out to 15% for the IETF for the week.  But
> we don't seem to be dropping at anywhere close to that rate ( e.g. A death
> at the meting every 5 meetings).
> >
> > Death probabilities are *highly* dependent on the specific populations
> you're looking at and actuaries get paid a lot of money to calculate them.
> The actual probabilities for the IETF would benefit from affluence, age,
> medical care, education, location, etc.
> >
> > Mike
> >
> >
> >
> > Sent from my iPad
> >
> >>> On Apr 5, 2017, at 01:56, Carsten Bormann <cabo@tzi.org> wrote:
> >>>
> >>> On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
> >>>
> >>> .005 deaths per week per 1000
> >> Right, the 270 micromorts per year (~ 5 micromorts per week) you cited
> would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting
> killed ? a factor three less than the 1.5 % that my numbers result in, but
> not off by a large factor.
> >> (Still, I wonder where that factor three comes from.)
> >>
> >> Luckily, we hit the other 98.5 % this week.
> >>
> >> (I?m not that worried by the ~ 15 micromorts of risk I personally was
> subjected to, given that I spent on the order of 250 microlives for the
> time that went into this meeting.
> >> But my wife, who had been planning our wonderful vacation in Colombia
> earlier this year, definitely was.)
> >>
> >> Gr??e, Carsten
> >>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 5 Apr 2017 08:13:47 -0700
> From: Bob Hinden <bob.hinden@gmail.com>
> To: Michael StJohns <mstjohns@comcast.net>
> Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <F51651E3-7668-4D00-8879-979680E19E38@gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
> > On Apr 5, 2017, at 7:26 AM, Michael StJohns <mstjohns@comcast.net>
> wrote:
> >
> > I meant to include (damn iPad):
> >
> > Carsten's original email was
> >> Statistically, the chance of any IETFer being killed last week was
> about 1.5 %.
> >
> > "Any IETFer being killed" (I read the above as "Any [given] IETFer")  is
> the .00051% chance.  "At least one IETFer" is the .5% chance.  "Anyone in
> the IETF" could mean either - precision is important and I still don't
> actually know which Carsten meant.
>
> I am happy that no IETFer got killed.  We did have some heated debates :-)
>
> Bob
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 496 bytes
> Desc: Message signed with OpenPGP
> URL: <
> https://mailarchive.ietf.org/arch/browse/ietf/attachments/20170405/f09b94af/attachment.asc
> >
>
> ------------------------------
>
> Message: 6
> Date: Wed, 5 Apr 2017 11:17:29 -0400
> From: Michael StJohns <mstjohns@comcast.net>
> To: Bob Hinden <bob.hinden@gmail.com>
> Cc: IETF <ietf@ietf.org>
> Subject: Re: IAOC requesting input on (potential) meeting cities
> Message-ID: <421b15b4-628c-d790-3c08-ce72cf725ab9@comcast.net>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 4/5/2017 11:13 AM, Bob Hinden wrote:
> >
> > I am happy that no IETFer got killed.  We did have some heated debates
> :-)
> >
> > Bob
> >
> >
> I once saw Dave Clark after a particularly contentious side meeting at
> an early IETF and said that I was glad I didn't see blood. His response
> was classic Dave: "It was the kind of meeting where the only blood came
> from biting your tongue."
>
> Mike
>
> The IETF - 30 years of Standards by Combat!
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ietf mailing list
> ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> ------------------------------
>
> End of ietf Digest, Vol 107, Issue 14
> *************************************
>
-- 
Zack Cylinder
Cloudbakers
Cloud Training Specialist

--001a114444969862d0054c6ea839
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Hey everyone,=C2=A0</div><div><br></div><div>Please see below and let =
me know if you have questions=C2=A0</div><div><br></div><div><br><div class=
=3D"gmail_quote"><div>On Wed, Apr 5, 2017 at 10:17 AM &lt;<a href=3D"mailto=
:ietf-request@ietf.org">ietf-request@ietf.org</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Send ietf mailing list submissions to<br class=3D=
"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf@ietf.org" class=3D"gmail=
_msg" target=3D"_blank">ietf@ietf.org</a><br class=3D"gmail_msg">
<br class=3D"gmail_msg">
To subscribe or unsubscribe via the World Wide Web, visit<br class=3D"gmail=
_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinf=
o/ietf" rel=3D"noreferrer" class=3D"gmail_msg" target=3D"_blank">https://ww=
w.ietf.org/mailman/listinfo/ietf</a><br class=3D"gmail_msg">
or, via email, send a message with subject or body &#39;help&#39; to<br cla=
ss=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf-request@ietf.org" class=
=3D"gmail_msg" target=3D"_blank">ietf-request@ietf.org</a><br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
You can reach the person managing the list at<br class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:ietf-owner@ietf.org" class=3D=
"gmail_msg" target=3D"_blank">ietf-owner@ietf.org</a><br class=3D"gmail_msg=
">
<br class=3D"gmail_msg">
When replying, please edit your Subject line so it is more specific<br clas=
s=3D"gmail_msg">
than &quot;Re: Contents of ietf digest...&quot;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Today&#39;s Topics:<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0 =C2=A01. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael Richardson)<br class=3D"gmail_msg">
=C2=A0 =C2=A02. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael Richardson)<br class=3D"gmail_msg">
=C2=A0 =C2=A03. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (mike stJohns)<br class=3D"gmail_msg">
=C2=A0 =C2=A04. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael StJohns)<br class=3D"gmail_msg">
=C2=A0 =C2=A05. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Bob Hinden)<br class=3D"gmail_msg">
=C2=A0 =C2=A06. Re: IAOC requesting input on (potential) meeting cities<br =
class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0 (Michael StJohns)<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
----------------------------------------------------------------------<br c=
lass=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 1<br class=3D"gmail_msg">
Date: Wed, 05 Apr 2017 09:23:14 -0400<br class=3D"gmail_msg">
From: Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca" cla=
ss=3D"gmail_msg" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;<br class=
=3D"gmail_msg">
To: IETF Discussion &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg=
" target=3D"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:6955.1491398594@obiwan.sandelman.ca" clas=
s=3D"gmail_msg" target=3D"_blank">6955.1491398594@obiwan.sandelman.ca</a>&g=
t;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br class=3D"gmail_msg=
">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Andrew G. Malis &lt;<a href=3D"mailto:agmalis@gmail.com" class=3D"gmail_msg=
" target=3D"_blank">agmalis@gmail.com</a>&gt; wrote:<br class=3D"gmail_msg"=
>
=C2=A0 =C2=A0 &gt; At least once, I was questioned extensively when going f=
rom the US to<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; a meeting in Canada. I had to show evidence of the meeti=
ng and my<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; itinerary and convince them that I wasn?t entering Canad=
a to take work<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; away from a Canadian. That said, I still support holding=
 meetings in<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; Canada.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
IETF98 was among the only times I was *NOT* asked questions like that when<=
br class=3D"gmail_msg">
entering the US.=C2=A0 =C2=A0I did enter at Midway.=C2=A0 =C2=A0That none o=
f are asked such<br class=3D"gmail_msg">
questions when entering europe always surprises me.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I&#39;m not sure what &quot;extensively&quot; means; if that means you were=
 taken aside, or<br class=3D"gmail_msg">
not.=C2=A0 I&#39;ve been through that at the US border.<br class=3D"gmail_m=
sg">
<br class=3D"gmail_msg">
&quot;Chair of work group&quot; would always be a bad thing to say, since i=
t has the<br class=3D"gmail_msg">
word &quot;work&quot; in it.=C2=A0 Never talk about customers.=C2=A0 The IE=
TF is a meeting of<br class=3D"gmail_msg">
peers.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
(Once because it was 5am, and I was just really loud since I was really sti=
ll<br class=3D"gmail_msg">
asleep).<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
But, in all cases I felt confident that I would be treated with respect,<br=
 class=3D"gmail_msg">
(even by the border guard who didn&#39;t seem to believe that e-tickets wer=
e<br class=3D"gmail_msg">
real).<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I did *not* feel that way while preparing to travel to IETF98.<br class=3D"=
gmail_msg">
My fears were not realized; but as Eliot has said, it&#39;s *exactly* the<b=
r class=3D"gmail_msg">
uncertainty that is a problem.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
--<br class=3D"gmail_msg">
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" class=3D"=
gmail_msg" target=3D"_blank">mcr+IETF@sandelman.ca</a>&gt;, Sandelman Softw=
are Works<br class=3D"gmail_msg">
=C2=A0-=3D IPv6 IoT consulting =3D-<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 487 bytes<br class=3D"gmail_msg">
Desc: not available<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/82807627/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/82807627/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 2<br class=3D"gmail_msg">
Date: Wed, 05 Apr 2017 09:25:54 -0400<br class=3D"gmail_msg">
From: Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca" cla=
ss=3D"gmail_msg" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;<br class=
=3D"gmail_msg">
To: Jared Mauch &lt;<a href=3D"mailto:jared@puck.Nether.net" class=3D"gmail=
_msg" target=3D"_blank">jared@puck.Nether.net</a>&gt;<br class=3D"gmail_msg=
">
Cc: John Levine &lt;<a href=3D"mailto:johnl@taugh.com" class=3D"gmail_msg" =
target=3D"_blank">johnl@taugh.com</a>&gt;, <a href=3D"mailto:ietf@ietf.org"=
 class=3D"gmail_msg" target=3D"_blank">ietf@ietf.org</a><br class=3D"gmail_=
msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:7538.1491398754@obiwan.sandelman.ca" clas=
s=3D"gmail_msg" target=3D"_blank">7538.1491398754@obiwan.sandelman.ca</a>&g=
t;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br class=3D"gmail_=
msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Jared Mauch &lt;<a href=3D"mailto:jared@puck.Nether.net" class=3D"gmail_msg=
" target=3D"_blank">jared@puck.Nether.net</a>&gt; wrote:<br class=3D"gmail_=
msg">
=C2=A0 =C2=A0 &gt; On Wed, Apr 05, 2017 at 12:53:47AM -0000, John Levine wr=
ote:<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; I agree that Canada is a fairly easy country to get =
in and out of<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; (unless you have a DUI arrest) but it varies a lot s=
o anecdotes about<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt;&gt; entering Canada or any other country don&#39;t tell =
you much.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; Agreed.=C2=A0 When I received my NEXUS card they explici=
ty told me<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; if I was traveling to a conference and was presenting th=
at I would<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; require additional paperwork, possibly including a lette=
r of invitation,<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; and/or a visa.=C2=A0 I presume if I were presenting at a=
n IETF WG I would<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; check the appropriate box when registering as well and I=
 would get<br class=3D"gmail_msg">
=C2=A0 =C2=A0 &gt; the paperwork.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
No!=C2=A0 Only if you have been paid to present.<br class=3D"gmail_msg">
=C2=A0 =C2=A0 =C2=A0i.e. you are Al Gore coming to talk at the Air Canada c=
enter in Toronto.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
We don&#39;t do presentations like that at the IETF.<br class=3D"gmail_msg"=
>
The IETF is not like most non-technical &quot;conferences&quot;.<br class=
=3D"gmail_msg">
<br class=3D"gmail_msg">
--<br class=3D"gmail_msg">
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" class=3D"=
gmail_msg" target=3D"_blank">mcr+IETF@sandelman.ca</a>&gt;, Sandelman Softw=
are Works<br class=3D"gmail_msg">
=C2=A0-=3D IPv6 IoT consulting =3D-<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 487 bytes<br class=3D"gmail_msg">
Desc: not available<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/7bafa802/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/7bafa802/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 3<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 09:49:54 -0400<br class=3D"gmail_msg">
From: mike stJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"gma=
il_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail_ms=
g">
To: Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" class=3D"gmail_msg"=
 target=3D"_blank">cabo@tzi.org</a>&gt;<br class=3D"gmail_msg">
Cc: IETF &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D=
"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:620C9C4C-413C-439C-9109-B30BBAB921B1@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">620C9C4C-413C-439C-9109-B30B=
BAB921B1@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain;=C2=A0 =C2=A0 =C2=A0 =C2=A0charset=3Dutf-8<br clas=
s=3D"gmail_msg">
<br class=3D"gmail_msg">
Let&#39;s try this one more time<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
27 deaths in 100 would be 27%<br class=3D"gmail_msg">
27 deaths in 1000 would be 2.7%<br class=3D"gmail_msg">
27 deaths in 10000 would be .27%<br class=3D"gmail_msg">
27 deaths in 100000 would be a rate of .027%<br class=3D"gmail_msg">
The above are all expected deaths per year for the given population - so di=
vide .027% by 52 to get .00051% per week.=C2=A0 That&#39;s roughly the chan=
ce per individual to die during the week from murder.=C2=A0 =C2=A0That&#39;=
s *my* risk for a week of the IETF and that&#39;s what should matter to eac=
h individual.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
If you take that and multiply it by the IETF population you get .005 expect=
ed deaths within the IETF for the entire week.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Now you&#39;re using the &quot;at least one&quot; criteria, which works out=
 to be 1-(1-.0000051)^1000 =3D .005 or .5% of at least one person dying in =
the week so your numbers are somewhat reasonable, but don&#39;t actually me=
an anything.=C2=A0 E.g this is basically the birthday paradox which grows t=
he probability quickly with the size of the set.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
=C2=A0I&#39;ll give you an example.=C2=A0 The death rate per 1000 in German=
y per year for all causes is about 11.=C2=A0 That works out to about a 20% =
chance of at least one person dying in the IETF during the week from all ca=
uses including murder if we all lived in Germany.=C2=A0 =C2=A0The equivalen=
t statistic for the US is 8 per 1000 which works out to 15% for the IETF fo=
r the week.=C2=A0 But we don&#39;t seem to be dropping at anywhere close to=
 that rate ( e.g. A death at the meting every 5 meetings).<br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
Death probabilities are *highly* dependent on the specific populations you&=
#39;re looking at and actuaries get paid a lot of money to calculate them.=
=C2=A0 The actual probabilities for the IETF would benefit from affluence, =
age, medical care, education, location, etc.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Sent from my iPad<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&gt;&gt; On Apr 5, 2017, at 01:56, Carsten Bormann &lt;<a href=3D"mailto:ca=
bo@tzi.org" class=3D"gmail_msg" target=3D"_blank">cabo@tzi.org</a>&gt; wrot=
e:<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; On Apr 5, 2017, at 01:06, mike stJohns &lt;<a href=3D"mailto:mstjo=
hns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast.net=
</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; .005 deaths per week per 1000<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Right, the 270 micromorts per year (~ 5 micromorts per week) you cited=
 would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting kil=
led ? a factor three less than the 1.5 % that my numbers result in, but not=
 off by a large factor.<br class=3D"gmail_msg">
&gt; (Still, I wonder where that factor three comes from.)<br class=3D"gmai=
l_msg">
&gt;<br class=3D"gmail_msg">
&gt; Luckily, we hit the other 98.5 % this week.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; (I?m not that worried by the ~ 15 micromorts of risk I personally was =
subjected to, given that I spent on the order of 250 microlives for the tim=
e that went into this meeting.<br class=3D"gmail_msg">
&gt; But my wife, who had been planning our wonderful vacation in Colombia =
earlier this year, definitely was.)<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Gr??e, Carsten<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 4<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 10:26:20 -0400<br class=3D"gmail_msg">
From: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"=
gmail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail=
_msg">
To: <a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">=
ietf@ietf.org</a><br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:cd5a3b9d-29dd-0d8b-b0a4-2a2465ea89b1@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">cd5a3b9d-29dd-0d8b-b0a4-2a24=
65ea89b1@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed<br class=3D"gmai=
l_msg">
<br class=3D"gmail_msg">
I meant to include (damn iPad):<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Carsten&#39;s original email was<br class=3D"gmail_msg">
&gt; Statistically, the chance of any IETFer being killed last week was abo=
ut 1.5 %.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&quot;Any IETFer being killed&quot; (I read the above as &quot;Any [given] =
IETFer&quot;)=C2=A0 is<br class=3D"gmail_msg">
the .00051% chance.=C2=A0 &quot;At least one IETFer&quot; is the .5% chance=
.=C2=A0 &quot;Anyone<br class=3D"gmail_msg">
in the IETF&quot; could mean either - precision is important and I still<br=
 class=3D"gmail_msg">
don&#39;t actually know which Carsten meant.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Later, Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
On 4/5/2017 9:49 AM, mike stJohns wrote:<br class=3D"gmail_msg">
&gt; Let&#39;s try this one more time<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; 27 deaths in 100 would be 27%<br class=3D"gmail_msg">
&gt; 27 deaths in 1000 would be 2.7%<br class=3D"gmail_msg">
&gt; 27 deaths in 10000 would be .27%<br class=3D"gmail_msg">
&gt; 27 deaths in 100000 would be a rate of .027%<br class=3D"gmail_msg">
&gt; The above are all expected deaths per year for the given population - =
so divide .027% by 52 to get .00051% per week.=C2=A0 That&#39;s roughly the=
 chance per individual to die during the week from murder.=C2=A0 =C2=A0That=
&#39;s *my* risk for a week of the IETF and that&#39;s what should matter t=
o each individual.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; If you take that and multiply it by the IETF population you get .005 e=
xpected deaths within the IETF for the entire week.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Now you&#39;re using the &quot;at least one&quot; criteria, which work=
s out to be 1-(1-.0000051)^1000 =3D .005 or .5% of at least one person dyin=
g in the week so your numbers are somewhat reasonable, but don&#39;t actual=
ly mean anything.=C2=A0 E.g this is basically the birthday paradox which gr=
ows the probability quickly with the size of the set.<br class=3D"gmail_msg=
">
&gt;<br class=3D"gmail_msg">
&gt;=C2=A0 =C2=A0I&#39;ll give you an example.=C2=A0 The death rate per 100=
0 in Germany per year for all causes is about 11.=C2=A0 That works out to a=
bout a 20% chance of at least one person dying in the IETF during the week =
from all causes including murder if we all lived in Germany.=C2=A0 =C2=A0Th=
e equivalent statistic for the US is 8 per 1000 which works out to 15% for =
the IETF for the week.=C2=A0 But we don&#39;t seem to be dropping at anywhe=
re close to that rate ( e.g. A death at the meting every 5 meetings).<br cl=
ass=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Death probabilities are *highly* dependent on the specific populations=
 you&#39;re looking at and actuaries get paid a lot of money to calculate t=
hem.=C2=A0 The actual probabilities for the IETF would benefit from affluen=
ce, age, medical care, education, location, etc.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Mike<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Sent from my iPad<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; On Apr 5, 2017, at 01:56, Carsten Bormann &lt;<a href=3D"mailt=
o:cabo@tzi.org" class=3D"gmail_msg" target=3D"_blank">cabo@tzi.org</a>&gt; =
wrote:<br class=3D"gmail_msg">
&gt;&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; On Apr 5, 2017, at 01:06, mike stJohns &lt;<a href=3D"mailto:m=
stjohns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast=
.net</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt;&gt; .005 deaths per week per 1000<br class=3D"gmail_msg">
&gt;&gt; Right, the 270 micromorts per year (~ 5 micromorts per week) you c=
ited would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting=
 killed ? a factor three less than the 1.5 % that my numbers result in, but=
 not off by a large factor.<br class=3D"gmail_msg">
&gt;&gt; (Still, I wonder where that factor three comes from.)<br class=3D"=
gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; Luckily, we hit the other 98.5 % this week.<br class=3D"gmail_msg"=
>
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; (I?m not that worried by the ~ 15 micromorts of risk I personally =
was subjected to, given that I spent on the order of 250 microlives for the=
 time that went into this meeting.<br class=3D"gmail_msg">
&gt;&gt; But my wife, who had been planning our wonderful vacation in Colom=
bia earlier this year, definitely was.)<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
&gt;&gt; Gr??e, Carsten<br class=3D"gmail_msg">
&gt;&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 5<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 08:13:47 -0700<br class=3D"gmail_msg">
From: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail=
_msg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<br class=3D"gmail_msg"=
>
To: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"gm=
ail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail_m=
sg">
Cc: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail_m=
sg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;, IETF &lt;<a href=3D"mai=
lto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">ietf@ietf.org</a>&=
gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:F51651E3-7668-4D00-8879-979680E19E38@gmai=
l.com" class=3D"gmail_msg" target=3D"_blank">F51651E3-7668-4D00-8879-979680=
E19E38@gmail.com</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br class=3D"gmail_=
msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&gt; On Apr 5, 2017, at 7:26 AM, Michael StJohns &lt;<a href=3D"mailto:mstj=
ohns@comcast.net" class=3D"gmail_msg" target=3D"_blank">mstjohns@comcast.ne=
t</a>&gt; wrote:<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I meant to include (damn iPad):<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Carsten&#39;s original email was<br class=3D"gmail_msg">
&gt;&gt; Statistically, the chance of any IETFer being killed last week was=
 about 1.5 %.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; &quot;Any IETFer being killed&quot; (I read the above as &quot;Any [gi=
ven] IETFer&quot;)=C2=A0 is the .00051% chance.=C2=A0 &quot;At least one IE=
TFer&quot; is the .5% chance.=C2=A0 &quot;Anyone in the IETF&quot; could me=
an either - precision is important and I still don&#39;t actually know whic=
h Carsten meant.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I am happy that no IETFer got killed.=C2=A0 We did have some heated debates=
 :-)<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Bob<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
-------------- next part --------------<br class=3D"gmail_msg">
A non-text attachment was scrubbed...<br class=3D"gmail_msg">
Name: signature.asc<br class=3D"gmail_msg">
Type: application/pgp-signature<br class=3D"gmail_msg">
Size: 496 bytes<br class=3D"gmail_msg">
Desc: Message signed with OpenPGP<br class=3D"gmail_msg">
URL: &lt;<a href=3D"https://mailarchive.ietf.org/arch/browse/ietf/attachmen=
ts/20170405/f09b94af/attachment.asc" rel=3D"noreferrer" class=3D"gmail_msg"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/browse/ietf/attachment=
s/20170405/f09b94af/attachment.asc</a>&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Message: 6<br class=3D"gmail_msg">
Date: Wed, 5 Apr 2017 11:17:29 -0400<br class=3D"gmail_msg">
From: Michael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" class=3D"=
gmail_msg" target=3D"_blank">mstjohns@comcast.net</a>&gt;<br class=3D"gmail=
_msg">
To: Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com" class=3D"gmail_m=
sg" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<br class=3D"gmail_msg">
Cc: IETF &lt;<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D=
"_blank">ietf@ietf.org</a>&gt;<br class=3D"gmail_msg">
Subject: Re: IAOC requesting input on (potential) meeting cities<br class=
=3D"gmail_msg">
Message-ID: &lt;<a href=3D"mailto:421b15b4-628c-d790-3c08-ce72cf725ab9@comc=
ast.net" class=3D"gmail_msg" target=3D"_blank">421b15b4-628c-d790-3c08-ce72=
cf725ab9@comcast.net</a>&gt;<br class=3D"gmail_msg">
Content-Type: text/plain; charset=3Dwindows-1252; format=3Dflowed<br class=
=3D"gmail_msg">
<br class=3D"gmail_msg">
On 4/5/2017 11:13 AM, Bob Hinden wrote:<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I am happy that no IETFer got killed.=C2=A0 We did have some heated de=
bates :-)<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Bob<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
I once saw Dave Clark after a particularly contentious side meeting at<br c=
lass=3D"gmail_msg">
an early IETF and said that I was glad I didn&#39;t see blood. His response=
<br class=3D"gmail_msg">
was classic Dave: &quot;It was the kind of meeting where the only blood cam=
e<br class=3D"gmail_msg">
from biting your tongue.&quot;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Mike<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
The IETF - 30 years of Standards by Combat!<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Subject: Digest Footer<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
_______________________________________________<br class=3D"gmail_msg">
ietf mailing list<br class=3D"gmail_msg">
<a href=3D"mailto:ietf@ietf.org" class=3D"gmail_msg" target=3D"_blank">ietf=
@ietf.org</a><br class=3D"gmail_msg">
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" rel=3D"noreferrer" c=
lass=3D"gmail_msg" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
ietf</a><br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
------------------------------<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
End of ietf Digest, Vol 107, Issue 14<br class=3D"gmail_msg">
*************************************<br class=3D"gmail_msg">
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-smartmail=
=3D"gmail_signature"><div dir=3D"ltr">Zack Cylinder<br><div>Cloudbakers</di=
v><div>Cloud Training Specialist</div></div></div>

--001a114444969862d0054c6ea839--


From nobody Wed Apr  5 10:52:26 2017
Return-Path: <aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498D912940E for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 1lbYp5uc5FX0 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:52:20 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C9C1126C7A for <ietf@ietf.org>; Wed,  5 Apr 2017 10:52:11 -0700 (PDT)
Received: from xct102cnc.rim.net ([10.65.161.202]) by mhs210cnc.rim.net with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Apr 2017 13:52:10 -0400
Received: from XCT111CNC.rim.net (10.65.161.211) by XCT102CNC.rim.net (10.65.161.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 5 Apr 2017 13:52:10 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT111CNC.rim.net ([::1]) with mapi id 14.03.0319.002; Wed, 5 Apr 2017 13:52:09 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Carsten Bormann <cabo@tzi.org>, mike stJohns <mstjohns@comcast.net>
CC: IETF <ietf@ietf.org>
Subject: RE: IAOC requesting input on (potential) meeting cities
Thread-Topic: IAOC requesting input on (potential) meeting cities
Thread-Index: AQHSqi0Mw1jFWAfNjUqpHilpEvYknKGvbx2AgASc5QCAAA/qgIAABIUAgAGtCoCAAAfYAIAAKc0AgAAfuACAAHKPgIAAJaYAgABb3+A=
Date: Wed, 5 Apr 2017 17:52:08 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD233A904062@XMB122CNC.rim.net>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org> <D50A7FA0.1A840%christer.holmberg@ericsson.com>
In-Reply-To: <D50A7FA0.1A840%christer.holmberg@ericsson.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.160.245]
Content-Type: text/plain; charset="windows-1257"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zXJE6rdvHMgKFAswusX7QLYovoI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 17:52:24 -0000

Most of all the homicides in Chicago take place in a few square miles in ce=
rtain areas a little outside the downtown district which is itself relative=
ly safe. As Christer says most of those incidents are related to narcotics =
and the associated gang turf wars.

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Wednesday, April 5, 2017 4:11 AM
To: Carsten Bormann <cabo@tzi.org>; mike stJohns <mstjohns@comcast.net>
Cc: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities

Chicago is a big city, and the murder rate varies widely between different =
areas. So, if you do your maths based on the numbers in the areas where IET=
Fers are likely to move around, and the kind of activities IETFers are like=
ly to participate in (much of the violence is related to gang/drug-related =
activities), I=B9m sure the result is going to be even smaller=D0=20





On 05/04/17 08:56, "ietf on behalf of Carsten Bormann"
<ietf-bounces@ietf.org on behalf of cabo@tzi.org> wrote:

>On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:
>>=20
>> .005 deaths per week per 1000
>
>Right, the 270 micromorts per year (~ 5 micromorts per week) you cited=20
>would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting=20
>killed =8B a factor three less than the 1.5 % that my numbers result in,=20
>but not off by a large factor.
>(Still, I wonder where that factor three comes from.)
>
>Luckily, we hit the other 98.5 % this week.
>
>(I=B9m not that worried by the ~ 15 micromorts of risk I personally was=20
>subjected to, given that I spent on the order of 250 microlives for the=20
>time that went into this meeting.
>But my wife, who had been planning our wonderful vacation in Colombia=20
>earlier this year, definitely was.)
>
>Gr=FC=DFe, Carsten
>


From nobody Wed Apr  5 10:58:52 2017
Return-Path: <bdamm@ssni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 749F1126C26 for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:58: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 KWUIlts_LCfS for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 10:58:49 -0700 (PDT)
Received: from it-ipdr-01.silverspringnet.com (it-ipdr-01.silverspringnet.com [74.121.22.27]) by ietfa.amsl.com (Postfix) with ESMTP id 94C40120326 for <ietf@ietf.org>; Wed,  5 Apr 2017 10:58:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2ACBACHL+VY/3MMOQpaAxkBAQEBAQEBAQEBAQcBAQEBAYMPAYElgQsHhiiZAoQEAQOTWyKCOoNGAoQpAQIBAQEBAQJrKIUVAQEBAQNJMAwEAgEIDgMEAQEBCR4HDyMUCQgCBAENBYl2AxatYocuCIM2AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZOhHCEViEmhR4FiimSR4ooiCqRPJN2V4EFJRYIGBWHGQF1iDyBDQEBAQ
X-IPAS-Result: A2ACBACHL+VY/3MMOQpaAxkBAQEBAQEBAQEBAQcBAQEBAYMPAYElgQsHhiiZAoQEAQOTWyKCOoNGAoQpAQIBAQEBAQJrKIUVAQEBAQNJMAwEAgEIDgMEAQEBCR4HDyMUCQgCBAENBYl2AxatYocuCIM2AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZOhHCEViEmhR4FiimSR4ooiCqRPJN2V4EFJRYIGBWHGQF1iDyBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.37,279,1488873600";  d="scan'208";a="5826577"
Received: from sfo-barrlb-01.silverspringnet.com (HELO mail.silverspringnet.com) ([10.57.12.115]) by it-ipdr-01.silverspringnet.com with ESMTP/TLS/AES256-SHA; 05 Apr 2017 10:58:49 -0700
Received: from sfo-ex13-04.silverspringnet.com (fdc2:c2cd:d343:390c:ad41:c0b5:cbaf:e1d9) by sfo-ex13-03.silverspringnet.com (fdc2:c2cd:d343:390c:4410:add9:7179:697d) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 5 Apr 2017 10:58:48 -0700
Received: from sfo-ex13-04.silverspringnet.com ([fe80::9029:bd6b:1ebf:9baa]) by sfo-ex13-04.silverspringnet.com ([fe80::9029:bd6b:1ebf:9baa%14]) with mapi id 15.00.1178.000; Wed, 5 Apr 2017 10:58:47 -0700
From: Benjamin Damm <bdamm@ssni.com>
To: Andrew Allen <aallen@blackberry.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Carsten Bormann <cabo@tzi.org>, "mike stJohns" <mstjohns@comcast.net>
CC: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Thread-Topic: IAOC requesting input on (potential) meeting cities
Thread-Index: AQHSqi0OxrGTq8NSskqE02UVFB2y96GvoWiAgASc5QCAAA/pgIAABIYAgAGtCYCAAAfZAIAAKcwAgAAfuQCAAHKOgIAAJaYAgACiVwD//4rk+g==
Date: Wed, 5 Apr 2017 17:58:47 +0000
Message-ID: <1491415127612.84497@ssni.com>
References: <149096990336.4276.3480662759931758139.idtracker@ietfa.amsl.com> <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <5DDF7585-8722-4C21-B998-CFD06A44EFE2@tzi.org> <7B3FF839-022B-4D58-96F9-1DEDEE0DA3C5@comcast.net> <162603E4-DE07-495B-B3A6-9F58D03D8DF8@tzi.org> <D50A7FA0.1A840%christer.holmberg@ericsson.com>, <BBF5DDFE515C3946BC18D733B20DAD233A904062@XMB122CNC.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233A904062@XMB122CNC.rim.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.57.12.115]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oTaN__jSqxj_NgQPFyHIDIf6NTg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 17:58:51 -0000

On my last day of the IETF I visited the Museum of Science and Industry aft=
er the IETF sessions were done and before my flight from Chicago Midway air=
port. The journey from the museum to Chicago Midway went through the area d=
escribed, which was evidenced by about 2 or 3km where every single home and=
 business had all windows covered in plywood. Uncomfortable, but fortunatel=
y not fatal.=0A=
=0A=
=0A=
Benjamin Damm=0A=
O: 669-770-4000=0A=
E: bdamm@ssni.com  www.ssni.com=0A=
=0A=
=0A=
________________________________________=0A=
From: ietf <ietf-bounces@ietf.org> on behalf of Andrew Allen <aallen@blackb=
erry.com>=0A=
Sent: Wednesday, April 5, 2017 10:52 AM=0A=
To: Christer Holmberg; Carsten Bormann; mike stJohns=0A=
Cc: IETF=0A=
Subject: RE: IAOC requesting input on (potential) meeting cities=0A=
=0A=
Most of all the homicides in Chicago take place in a few square miles in ce=
rtain areas a little outside the downtown district which is itself relative=
ly safe. As Christer says most of those incidents are related to narcotics =
and the associated gang turf wars.=0A=
=0A=
-----Original Message-----=0A=
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Christer Holmberg=0A=
Sent: Wednesday, April 5, 2017 4:11 AM=0A=
To: Carsten Bormann <cabo@tzi.org>; mike stJohns <mstjohns@comcast.net>=0A=
Cc: IETF <ietf@ietf.org>=0A=
Subject: Re: IAOC requesting input on (potential) meeting cities=0A=
=0A=
Chicago is a big city, and the murder rate varies widely between different =
areas. So, if you do your maths based on the numbers in the areas where IET=
Fers are likely to move around, and the kind of activities IETFers are like=
ly to participate in (much of the violence is related to gang/drug-related =
activities), I=B9m sure the result is going to be even smaller=8A=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
On 05/04/17 08:56, "ietf on behalf of Carsten Bormann"=0A=
<ietf-bounces@ietf.org on behalf of cabo@tzi.org> wrote:=0A=
=0A=
>On Apr 5, 2017, at 01:06, mike stJohns <mstjohns@comcast.net> wrote:=0A=
>>=0A=
>> .005 deaths per week per 1000=0A=
>=0A=
>Right, the 270 micromorts per year (~ 5 micromorts per week) you cited=0A=
>would lead to a ~ 0.5 % chance of anyone of the ~ 1000 IETFers getting=0A=
>killed =8B a factor three less than the 1.5 % that my numbers result in,=
=0A=
>but not off by a large factor.=0A=
>(Still, I wonder where that factor three comes from.)=0A=
>=0A=
>Luckily, we hit the other 98.5 % this week.=0A=
>=0A=
>(I=B9m not that worried by the ~ 15 micromorts of risk I personally was=0A=
>subjected to, given that I spent on the order of 250 microlives for the=0A=
>time that went into this meeting.=0A=
>But my wife, who had been planning our wonderful vacation in Colombia=0A=
>earlier this year, definitely was.)=0A=
>=0A=
>Gr=FC=DFe, Carsten=0A=
>=0A=
=0A=


From nobody Wed Apr  5 11:49:11 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656F512706D for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 11:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level: 
X-Spam-Status: No, score=-4.296 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, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 xVE60xJ3sxqe for <ietf@ietfa.amsl.com>; Wed,  5 Apr 2017 11:49:08 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805DB127A90 for <ietf@ietf.org>; Wed,  5 Apr 2017 11:49:08 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTP id 1EA50C00282B; Wed,  5 Apr 2017 11:49:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=50C1Do+9cPoSwE OB2WfOnf40+9M=; b=GlahX+LzJv/SJmBXMifXImgH3cviidD8XhsG95Pz9W/4t0 DTWB5XX2Ao01+ebF275g64fiiIuA2jCSJbhNGg+/3IefHTU1G76p1QOTK+hhgPLK 0LM5IeHOhY+herQzml29AGAE/a0dfmfNw7muakawQ5EUp71AzThhJEoHEX8EQ=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTPSA id 7F882C002828; Wed,  5 Apr 2017 11:49:07 -0700 (PDT)
Date: Wed, 5 Apr 2017 13:49:05 -0500
From: Nico Williams <nico@cryptonector.com>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: "Andrew G. Malis" <agmalis@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170405184904.GE4004@localhost>
References: <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <e70a5f90-02b1-7ec5-30dd-9cd7f20821b1@cisco.com> <b814561c-939a-51b8-b999-d08cad0c15bd@gmail.com> <CAA=duU3SgL8ZGV2YDv4SmbhBqSygYyECwYd93YUjMaD2Pf6F_g@mail.gmail.com> <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <518dd91b-a09e-651b-ec6f-15076a3cf8a0@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/32MZ_WLQDS47Itxml3w9Lp07JLg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 18:49:10 -0000

On Tue, Apr 04, 2017 at 03:50:50PM -0800, Melinda Shore wrote:
> Here, we're talking about uncertainty about whether or not Canadian
> ...

Uncertainty and a high rate of change without public comment/review
periods is actually concerning indeed.

It's nice to see this sort of thing:

http://thehill.com/policy/cybersecurity/327246-bipartisan-bill-would-end-warrantless-searches-of-digital-devices-at

though it's probably not going to pass right away, and it wouldn't
really protect non-U.S.-persons (since other reasons could still be used
to refuse entry).

I still think that we're not likely to see much impact on IETF
participants, but it's certainly fine to schedule fewer meetings in the
U.S. for the time being until we have more experience (possibly from
other conferences' sharing theirs).

Nico
-- 


From nobody Wed Apr  5 13:22:34 2017
Return-Path: <gunter@vandevelde.cc>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2FBC12948F; Wed,  5 Apr 2017 13:22:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gunter Van de Velde <gunter@vandevelde.cc>
To: <ops-dir@ietf.org>
Cc: draft-kivinen-802-15-ie.all@ietf.org, ietf@ietf.org
Subject: Opsdir early review of draft-kivinen-802-15-ie-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149142375166.21961.2375059231236243792@ietfa.amsl.com>
Date: Wed, 05 Apr 2017 13:22:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r1XbjblWRX0pq2VKWVn9zYk8a7M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 20:22:32 -0000

Reviewer: Scott Bradner
Review result: Ready

Clearing ops-dir state from "Serious Issues" to "No Issues" to solve
future confusion with OPS-DIR tool administration


From nobody Wed Apr  5 13:48:02 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9411294AF; Wed,  5 Apr 2017 13:47:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <secdir@ietf.org>
Cc: draft-ietf-httpbis-encryption-encoding.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Subject: Secdir last call review of draft-ietf-httpbis-encryption-encoding-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149142527327.21912.5654685591478038284@ietfa.amsl.com>
Date: Wed, 05 Apr 2017 13:47:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2b60awtoPaUy64Dpn4iamBIz1ak>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 20:47:53 -0000

Reviewer: Robert Sparks
Review result: Ready

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

Document : draft-ietf-httpbis-encryption-encoding-08

Summary: This document is ready for publication as Proposed Standard
(except perhaps for one recommendation)

This document defines a content encoding for encrypting the contents
of an HTTP message that
facilitates storing the encrypted contents and decrypting the content
for rendering incrementally
(before the full content is received). The draft is clear, and
implementation should be straightforward.
It's security considerations section is detailed.

I did not verify the math that went into the provided examples.

My only concern is that the document suggests it would be ok to use a
counter to provide a unique salt value
for each message. I suspect that provides the kind of information leak
the draft discusses avoiding.

I also pointed out a couple of nits to the editor, and those are
addressed already in his working copy (on github).


From nobody Wed Apr  5 15:32:54 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E0E127978; Wed,  5 Apr 2017 15:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 cYW9ZLF2jjCJ; Wed,  5 Apr 2017 15:32:50 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::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 5576A1294C8; Wed,  5 Apr 2017 15:32:43 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id p22so23910614qka.3; Wed, 05 Apr 2017 15:32:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yI0jB5gy9FBC1BAchxJ6qSMnSsEivOs4HzlVE5pTWzE=; b=VnYUbdIc+IGxcNj5F+dfvAka1rmR+h/hrxZNc+PR3TLqylBrA0zWk7HSICaylycrF1 M8O0SEMBDFJN6AqVb92S8qIuRi3jCwmYkyQDkpMJqdkH3PGBDZ7rzKc06XDN3TjIu+UW o8wCpT95U/oVJRY3Bqn2v5pkA7PfgBJRZBCJ0wyh+YXXG8YcP0I7FaXlmnfO/NL9W/al Q5nkEWoGuSqYa485/ixyCpw+JlqdOS2sx/Sctva0dadgEhQDHgGzSDIUsxe+F72/Vbci IDIRgkFlNd4ZNxxVCeuxcHMIotPBzuCB4EK3OfRPAYIeMXS0No1IYOB22XnUqcL80Dfj JOog==
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=yI0jB5gy9FBC1BAchxJ6qSMnSsEivOs4HzlVE5pTWzE=; b=XgZrNPLjka/38mL+Ojsa9Kw2A6RtrEqJSXHD6c8c0wj/Xjc8bgV/n2DMWt+7is10YM qV3804+uAOQ0B7mIm5DT2uu9O+fFJ3cPTKpw2MkOISImgV4nPJFHgB15qzpkGa4mznxj Z6kvHO0g8CT8LJznI/Q91QFMxjYHyQF35Cn/7mIZRL5p+uuT/dH7P9+gsCbS4T4OkC0v 6uQSvHcacUxdO5xHDuhq3w86vVN9+usvJiutiL8IyttZ3ZolvQ0/ra8pCm9o7HOYZgZe HInPfS+ELTrXIX2pOaWGZLA10R4Z19WnK1l1eQ3AfutEQexoskh03LEoNjUMK4x00SCy zfTw==
X-Gm-Message-State: AFeK/H3Wzjnvxt2kPTbR6IMYXMtr1eRwufPHXiOVW7pGYO8TuzItf/5m8xSrcJ44ZzOOinjEIL8ziKUA2p/x6w==
X-Received: by 10.55.104.88 with SMTP id d85mr8066225qkc.202.1491431562562; Wed, 05 Apr 2017 15:32:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Wed, 5 Apr 2017 15:32:42 -0700 (PDT)
In-Reply-To: <149142527327.21912.5654685591478038284@ietfa.amsl.com>
References: <149142527327.21912.5654685591478038284@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 6 Apr 2017 08:32:42 +1000
Message-ID: <CABkgnnU7qXVeCDxoRbG8i6GbxJTA6gRpyHH0Yf+h0eRAJ+WLxw@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-httpbis-encryption-encoding-08
To: Robert Sparks <rjsparks@nostrum.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MO6mmgBx2xUlRAhOE21ub0JwIqE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 22:32:52 -0000

On 6 April 2017 at 06:47, Robert Sparks <rjsparks@nostrum.com> wrote:
>
> My only concern is that the document suggests it would be ok to use a
> counter to provide a unique salt value
> for each message. I suspect that provides the kind of information leak
> the draft discusses avoiding.

Hi Robert, can you explain what sort of leakage you are concerned
about?  I mean, I can understand how you could construct the sequence
of resources that were encrypted using a counter for the salt, but I
don't know what that might imply.

That said, I think that the counter thing can be removed.  We require
128 bits of salt, which is a space that is large enough to select
randomly from in perpetuity.


From nobody Wed Apr  5 19:07:49 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8E21271DF; Wed,  5 Apr 2017 19:07:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Thomson <martin.thomson@gmail.com>
To: <art@ietf.org>
Cc: alto@ietf.org, ietf@ietf.org, draft-ietf-alto-multi-cost.all@ietf.org
Subject: Artart telechat review of draft-ietf-alto-multi-cost-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149144445494.22036.11923880719369865745@ietfa.amsl.com>
Date: Wed, 05 Apr 2017 19:07:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZH3Fyz1aErxJ-HR3uOP2d5gW-Cs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 02:07:35 -0000

Reviewer: Martin Thomson
Review result: Ready with Issues

Document: draft-ietf-alto-multi-cost-08
Date: 2017-04-06
Reviewer: Martin Thomson

This document describes how ALTO can be used to acquire cost maps with
multiple
cost metric instead of a single metric.

The document very carefully deals with backwards compatibility with
existing
ALTO servers and clients.  I don't anticipate many issues arising from
the
deployment of this protocol.

I started reading -07, but finished with -08.  I checked that the
issues I raise
still exist, but I'm not infallible.  Apologies if I get something
wrong.

Minor issues: I've identified a few issues that are more than nits,
these are
marked "IMPORTANT" below.


The abstract includes considerable justificiation.  An abstract only
needs to
describe the *what*, not the *why*.  Thus, what is there could be
simplified
considerably, e.g.,

   This document defines a new method for retrieving multiple cost
metrics in a
   single request for an ALTO filtered cost map.  It also defines
improvements
   to the constraints that can be used for filtered cost maps.

Section 1

The introduction uses a bunch of odd terms.  Some of these are
recognizable from
the ALTO specification, but some of the jargon seems unnecessary.  In
particular, "Internet View", "Provider Network region" and "Vector
costs".  All
of which I think that I understand, but they make the doc hard to
follow.

Generally, I found the introduction quite hard to follow, both for
that reason
and structurally.  The introduction could be a lot shorter and more
concise:

1. ALTO defines multiple cost types (and more are being defined).
2. Clients sometimes consume multiple cost types.
3. Requesting multiple cost types at the same time is more efficient
(for
   several reasons).
4. This document defines how to do that.
5. Separately, when multiple cost types are present, more
sophisticated
   filtering can improve efficiency further.
6. This document defines how to do that too.

Section 2

There are several items in the list here that are not used:
Application Client,
Network Service Provider, maybe more.  Please check and remove those
that don't apply.

The RFC 7285 section reference thing is unnecessary.

This document doesn't cite RFC 2119, but it uses the keywords.

Section 3.1

The example shows an empty cost-type, but the schema you define allows
it to be
absent.  You REALLY need to pick one.  I don't believe that this is a
compatibility issue: once you have determined that a client supports
multi-cost,
then you can do anything you like, just be clear about it.

Section 3.2

I found the argument about the ease of writing a parser to be quite
unconvincing.  However, a new media type that is largely the same as
the
existing media type won't necessarily result in code duplication.

Just say what it is you expect to happen and don't try to be
apologetic about
it.  What you have appears to be a workable design.

Section 3.5

This section is confusing.  You only need to say that you are not
altering full
cost map resources in any way and that clients need to use filtered
cost maps if
they want multiple costs at the same time.  (Obviously you could have,
but
creating multiple resources with the full combinatorial mess caused by
combining
many cost types is unwieldy.)  At a minimum, the second paragraph here
can be
removed.

Section 3.6.2

IMPORTANT: You don't define what happens when a client provides
"or-constraints"
and "constraints" at the same time.  There are several valid options,
but you
need to choose.

Section 3.6.3

It is probably worth explicitly noting that if "testable-cost-types"
does not
include values from "multi-cost-types", then those types can't be
included in
"constraints"/"or-constraints".

Please explain the default value for the index for the
"constraints"/"or-constraints" express in this section in addition to
where it
is hidden in a note later in the document.

Section 3.6.5

Uppercase for "must not" in the second paragraph.  (The "may" later in
the
paragraph might be better as "can".)

In the example, the resource named "filtered-multicost-map" is
provided for
legacy reasons only.  Why bother including "max-cost-types" and
"cost-type-names" at all when "filtered-cost-map-extended" includes
all that and
more?

Section 4.1.1

The definition of the schema here (and later) actually redefines the
object
completely.  I found that confusing initially.  It would be good to
identify the
*changes* from the base specification somehow.

Can testable-cost-type-names be present and empty if cost-constraints
is false?
The first part of the definition permits that, the second forbids it.

Section 4.1.2

The redefinition of PIDFilter is unnecessary.

IMPORTANT: pids is optional in RFC 7285.  Why the change?

I find the redefinition of the optionality of cost-type to be worthy
of special
note.

In the definition of "or-constraints", you use a "database query"
where words
would suffice.

Section 4.1.3

I find the choice of value for "cost-type" to be problematic.  It is a
string in
the base protocol, so changing to an empty object is likely to cause
more issues
than simply omitting it.

Section 4.2 contains mismatched braces/parens for section references.

Section 4.2.2

IMPORTANT: This provides a definition for ReqFilteredCostMap that is
very
different to that in the base specification.  I think that this should
have been
ReqEndpointCostMap.

As before, repeating the definition of EndpointFilter is unnecessary.

Section 4.2.3 - see comment on 4.1.3

Section 5

I would be more comfortable if the examples used obviously-spurious
metrics
(e.g., "cattle-head-count", "smell", "shoe-size", etc...) than these
metrics
that are pretty plausible.  More so when you claim that they are
widely valued,
which implies some sort of validity.

It should be relatively easy to populate Content-Length now that the
examples
are "final".

Section 5.1

You have unmatched braces in "meta" due to the comment.

Section 5.2

Do you want to show one of the examples as having no cost values at
all across
all the cost types?



From nobody Wed Apr  5 22:53:05 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AC94E12943D; Wed,  5 Apr 2017 22:52:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-httpbis-encryption-encoding.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Subject: Genart last call review of draft-ietf-httpbis-encryption-encoding-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
Date: Wed, 05 Apr 2017 22:52:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4L3MEKMcGUJ41Lnn9jSv45YuSj4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 05:52:49 -0000

Reviewer: Pete Resnick
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-httpbis-encryption-encoding-??
Reviewer: Pete Resnick
Review Date: 2017-04-05
IETF LC End Date: 2017-04-06
IESG Telechat date: 2017-04-13

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: Looks fine from a non-security-expert's
perspective. It is my duty to ask about keyid in section 2.1:

      A "keyid" parameter SHOULD be a UTF-8
      [RFC3629] encoded string, particularly where the identifier
might
      need to appear in a textual form.

I presume that simply means "might need to be rendered" and does not
include "might need to be typed in by someone", correct? The former is
easy; the latter probably requires a bit more text.


From nobody Thu Apr  6 02:44:51 2017
Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 608651293E4; Thu,  6 Apr 2017 02:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.697
X-Spam-Level: 
X-Spam-Status: No, score=-4.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, SPF_HELO_PASS=-0.001, 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=nokia.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 z9VMWphqXuoW; Thu,  6 Apr 2017 02:44:40 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10091.outbound.protection.outlook.com [40.107.1.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31040127B31; Thu,  6 Apr 2017 02:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ty2qw21hKkS5GMbsMLX9Z3oBZImmX/jsWU6KoM8POC0=; b=dyLBiXCDmuK+z1caEkf0UF52KkeXvEh+eUh3hEcBIF6oPAFwkwQeIyemT1sqsdmVug2vCIS10SMUcurAovgMqGkvxe7T3xSNXc+ANYb+O3aTK0TWCVxRu4FbtU71iHcpeFD3MadfkuirDZuvDACtW/NHisxRTJQPtQ/U8i5nrxo=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB2453.eurprd07.prod.outlook.com (10.168.75.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.8; Thu, 6 Apr 2017 09:44:37 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) with mapi id 15.01.1019.021; Thu, 6 Apr 2017 09:44:37 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Martin Thomson <martin.thomson@gmail.com>, "art@ietf.org" <art@ietf.org>
CC: "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Subject: RE: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Topic: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Index: AQHSrnqQeK8CFgpYuE64kjZYAubM4qG4F1CQ
Date: Thu, 6 Apr 2017 09:44:36 +0000
Message-ID: <DB6PR0701MB2454D5B2935448FFAE234C12950D0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com>
In-Reply-To: <149144445494.22036.11923880719369865745@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.27]
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB2453; 7:Wbk6gNXKv+vaGMZHY3U2CdDSgoz8YqQx1XWNBQvezsFYanZBj3f23hleRVX3IuGcg2rvemjDob2Vo3BhM/qOegYpJJGVFytN83gmXEZbVcpr18xsFB3gXTQJQzn6QEu8OKksLfBJZnu2cd56NFBOJgJM0yMr9oXq325IWcaFDhyRrZivmnNYNMj2No7k0h4FolrEHhxnBchfFG9FtCBQKqfdGcVZCa1CP4q5EtB7hpHkJB+XTknu4xz4URC9e3Zcu1agm1zbDCUL2WpPnQtFAeAXTmKqDjj79VsXO0WwP4RC8wQBq5c6NtTFK0HsTkHjeNxw9nX/8O+gdPlpeZZjbw==
x-ms-office365-filtering-correlation-id: 27756a60-56e2-4099-c426-08d47cd189fe
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:DB6PR0701MB2453; 
x-microsoft-antispam-prvs: <DB6PR0701MB2453B83CF19950CD9944210F950D0@DB6PR0701MB2453.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041248)(20161123562025)(20161123560025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(6072148); SRVR:DB6PR0701MB2453; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2453; 
x-forefront-prvs: 02698DF457
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39850400002)(39410400002)(39840400002)(39400400002)(39450400003)(13464003)(51444003)(377424004)(25786009)(8676002)(7696004)(39060400002)(38730400002)(54906002)(6246003)(8936002)(7736002)(77096006)(3660700001)(9686003)(55016002)(81166006)(305945005)(2501003)(74316002)(66066001)(4326008)(2950100002)(99286003)(229853002)(2900100001)(6436002)(76176999)(3846002)(6116002)(102836003)(86362001)(2906002)(50986999)(33656002)(5660300001)(3280700002)(230783001)(54356999)(122556002)(189998001)(53936002)(6506006)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2453; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2017 09:44:36.9104 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2453
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EATseLdV9gWu9XJ5i3IG3tGzJ14>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 09:44:43 -0000

SGVsbG8gTWFydGluLA0KDQpUaGFua3MgYSBsb3QgZm9yIHlvdXIgcmV2aWV3LiBUaGUgZHJhZnQg
d2lsbCBiZSB1cGRhdGVkIHNvIGFzIHRvIGFkZHJlc3MgdGhlbS4NCkJlc3QgcmVnYXJkcywNClNh
YmluZQ0KDQoNCj4+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+RnJvbTogTWFydGluIFRo
b21zb24gW21haWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb21dDQo+PlNlbnQ6IDA2IEFwcmls
IDIwMTcgMDQ6MDgNCj4+VG86IGFydEBpZXRmLm9yZw0KPj5DYzogYWx0b0BpZXRmLm9yZzsgaWV0
ZkBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1hbHRvLW11bHRpLWNvc3QuYWxsQGlldGYub3JnDQo+PlN1
YmplY3Q6IEFydGFydCB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hbHRvLW11bHRpLWNv
c3QtMDgNCj4+DQo+PlJldmlld2VyOiBNYXJ0aW4gVGhvbXNvbg0KPj5SZXZpZXcgcmVzdWx0OiBS
ZWFkeSB3aXRoIElzc3Vlcw0KPj4NCj4+RG9jdW1lbnQ6IGRyYWZ0LWlldGYtYWx0by1tdWx0aS1j
b3N0LTA4DQo+PkRhdGU6IDIwMTctMDQtMDYNCj4+UmV2aWV3ZXI6IE1hcnRpbiBUaG9tc29uDQo+
Pg0KPj5UaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBob3cgQUxUTyBjYW4gYmUgdXNlZCB0byBhY3F1
aXJlIGNvc3QgbWFwcyB3aXRoDQo+Pm11bHRpcGxlIGNvc3QgbWV0cmljIGluc3RlYWQgb2YgYSBz
aW5nbGUgbWV0cmljLg0KPj4NCj4+VGhlIGRvY3VtZW50IHZlcnkgY2FyZWZ1bGx5IGRlYWxzIHdp
dGggYmFja3dhcmRzIGNvbXBhdGliaWxpdHkgd2l0aCBleGlzdGluZw0KPj5BTFRPIHNlcnZlcnMg
YW5kIGNsaWVudHMuICBJIGRvbid0IGFudGljaXBhdGUgbWFueSBpc3N1ZXMgYXJpc2luZyBmcm9t
IHRoZQ0KPj5kZXBsb3ltZW50IG9mIHRoaXMgcHJvdG9jb2wuDQo+Pg0KPj5JIHN0YXJ0ZWQgcmVh
ZGluZyAtMDcsIGJ1dCBmaW5pc2hlZCB3aXRoIC0wOC4gIEkgY2hlY2tlZCB0aGF0IHRoZSBpc3N1
ZXMgSSByYWlzZQ0KPj5zdGlsbCBleGlzdCwgYnV0IEknbSBub3QgaW5mYWxsaWJsZS4gIEFwb2xv
Z2llcyBpZiBJIGdldCBzb21ldGhpbmcgd3JvbmcuDQo+Pg0KPj5NaW5vciBpc3N1ZXM6IEkndmUg
aWRlbnRpZmllZCBhIGZldyBpc3N1ZXMgdGhhdCBhcmUgbW9yZSB0aGFuIG5pdHMsIHRoZXNlIGFy
ZQ0KPj5tYXJrZWQgIklNUE9SVEFOVCIgYmVsb3cuDQo+Pg0KPj4NCj4+VGhlIGFic3RyYWN0IGlu
Y2x1ZGVzIGNvbnNpZGVyYWJsZSBqdXN0aWZpY2lhdGlvbi4gIEFuIGFic3RyYWN0IG9ubHkgbmVl
ZHMgdG8NCj4+ZGVzY3JpYmUgdGhlICp3aGF0Kiwgbm90IHRoZSAqd2h5Ki4gIFRodXMsIHdoYXQg
aXMgdGhlcmUgY291bGQgYmUgc2ltcGxpZmllZA0KPj5jb25zaWRlcmFibHksIGUuZy4sDQo+Pg0K
Pj4gICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBuZXcgbWV0aG9kIGZvciByZXRyaWV2aW5nIG11
bHRpcGxlIGNvc3QgbWV0cmljcyBpbg0KPj5hDQo+PiAgIHNpbmdsZSByZXF1ZXN0IGZvciBhbiBB
TFRPIGZpbHRlcmVkIGNvc3QgbWFwLiAgSXQgYWxzbyBkZWZpbmVzIGltcHJvdmVtZW50cw0KPj4g
ICB0byB0aGUgY29uc3RyYWludHMgdGhhdCBjYW4gYmUgdXNlZCBmb3IgZmlsdGVyZWQgY29zdCBt
YXBzLg0KPj4NCj4+U2VjdGlvbiAxDQo+Pg0KPj5UaGUgaW50cm9kdWN0aW9uIHVzZXMgYSBidW5j
aCBvZiBvZGQgdGVybXMuICBTb21lIG9mIHRoZXNlIGFyZSByZWNvZ25pemFibGUNCj4+ZnJvbSB0
aGUgQUxUTyBzcGVjaWZpY2F0aW9uLCBidXQgc29tZSBvZiB0aGUgamFyZ29uIHNlZW1zIHVubmVj
ZXNzYXJ5LiAgSW4NCj4+cGFydGljdWxhciwgIkludGVybmV0IFZpZXciLCAiUHJvdmlkZXIgTmV0
d29yayByZWdpb24iIGFuZCAiVmVjdG9yIGNvc3RzIi4NCj4+QWxsIG9mIHdoaWNoIEkgdGhpbmsg
dGhhdCBJIHVuZGVyc3RhbmQsIGJ1dCB0aGV5IG1ha2UgdGhlIGRvYyBoYXJkIHRvIGZvbGxvdy4N
Cj4+DQo+PkdlbmVyYWxseSwgSSBmb3VuZCB0aGUgaW50cm9kdWN0aW9uIHF1aXRlIGhhcmQgdG8g
Zm9sbG93LCBib3RoIGZvciB0aGF0IHJlYXNvbg0KPj5hbmQgc3RydWN0dXJhbGx5LiAgVGhlIGlu
dHJvZHVjdGlvbiBjb3VsZCBiZSBhIGxvdCBzaG9ydGVyIGFuZCBtb3JlDQo+PmNvbmNpc2U6DQo+
Pg0KPj4xLiBBTFRPIGRlZmluZXMgbXVsdGlwbGUgY29zdCB0eXBlcyAoYW5kIG1vcmUgYXJlIGJl
aW5nIGRlZmluZWQpLg0KPj4yLiBDbGllbnRzIHNvbWV0aW1lcyBjb25zdW1lIG11bHRpcGxlIGNv
c3QgdHlwZXMuDQo+PjMuIFJlcXVlc3RpbmcgbXVsdGlwbGUgY29zdCB0eXBlcyBhdCB0aGUgc2Ft
ZSB0aW1lIGlzIG1vcmUgZWZmaWNpZW50IChmb3INCj4+ICAgc2V2ZXJhbCByZWFzb25zKS4NCj4+
NC4gVGhpcyBkb2N1bWVudCBkZWZpbmVzIGhvdyB0byBkbyB0aGF0Lg0KPj41LiBTZXBhcmF0ZWx5
LCB3aGVuIG11bHRpcGxlIGNvc3QgdHlwZXMgYXJlIHByZXNlbnQsIG1vcmUgc29waGlzdGljYXRl
ZA0KPj4gICBmaWx0ZXJpbmcgY2FuIGltcHJvdmUgZWZmaWNpZW5jeSBmdXJ0aGVyLg0KPj42LiBU
aGlzIGRvY3VtZW50IGRlZmluZXMgaG93IHRvIGRvIHRoYXQgdG9vLg0KPj4NCj4+U2VjdGlvbiAy
DQo+Pg0KPj5UaGVyZSBhcmUgc2V2ZXJhbCBpdGVtcyBpbiB0aGUgbGlzdCBoZXJlIHRoYXQgYXJl
IG5vdCB1c2VkOg0KPj5BcHBsaWNhdGlvbiBDbGllbnQsDQo+Pk5ldHdvcmsgU2VydmljZSBQcm92
aWRlciwgbWF5YmUgbW9yZS4gIFBsZWFzZSBjaGVjayBhbmQgcmVtb3ZlIHRob3NlDQo+PnRoYXQg
ZG9uJ3QgYXBwbHkuDQo+Pg0KPj5UaGUgUkZDIDcyODUgc2VjdGlvbiByZWZlcmVuY2UgdGhpbmcg
aXMgdW5uZWNlc3NhcnkuDQo+Pg0KPj5UaGlzIGRvY3VtZW50IGRvZXNuJ3QgY2l0ZSBSRkMgMjEx
OSwgYnV0IGl0IHVzZXMgdGhlIGtleXdvcmRzLg0KPj4NCj4+U2VjdGlvbiAzLjENCj4+DQo+PlRo
ZSBleGFtcGxlIHNob3dzIGFuIGVtcHR5IGNvc3QtdHlwZSwgYnV0IHRoZSBzY2hlbWEgeW91IGRl
ZmluZSBhbGxvd3MgaXQNCj4+dG8gYmUgYWJzZW50LiAgWW91IFJFQUxMWSBuZWVkIHRvIHBpY2sg
b25lLiAgSSBkb24ndCBiZWxpZXZlIHRoYXQgdGhpcyBpcyBhDQo+PmNvbXBhdGliaWxpdHkgaXNz
dWU6IG9uY2UgeW91IGhhdmUgZGV0ZXJtaW5lZCB0aGF0IGEgY2xpZW50IHN1cHBvcnRzIG11bHRp
LQ0KPj5jb3N0LCB0aGVuIHlvdSBjYW4gZG8gYW55dGhpbmcgeW91IGxpa2UsIGp1c3QgYmUgY2xl
YXIgYWJvdXQgaXQuDQo+Pg0KPj5TZWN0aW9uIDMuMg0KPj4NCj4+SSBmb3VuZCB0aGUgYXJndW1l
bnQgYWJvdXQgdGhlIGVhc2Ugb2Ygd3JpdGluZyBhIHBhcnNlciB0byBiZSBxdWl0ZQ0KPj51bmNv
bnZpbmNpbmcuICBIb3dldmVyLCBhIG5ldyBtZWRpYSB0eXBlIHRoYXQgaXMgbGFyZ2VseSB0aGUg
c2FtZSBhcyB0aGUNCj4+ZXhpc3RpbmcgbWVkaWEgdHlwZSB3b24ndCBuZWNlc3NhcmlseSByZXN1
bHQgaW4gY29kZSBkdXBsaWNhdGlvbi4NCj4+DQo+Pkp1c3Qgc2F5IHdoYXQgaXQgaXMgeW91IGV4
cGVjdCB0byBoYXBwZW4gYW5kIGRvbid0IHRyeSB0byBiZSBhcG9sb2dldGljIGFib3V0DQo+Pml0
LiAgV2hhdCB5b3UgaGF2ZSBhcHBlYXJzIHRvIGJlIGEgd29ya2FibGUgZGVzaWduLg0KPj4NCj4+
U2VjdGlvbiAzLjUNCj4+DQo+PlRoaXMgc2VjdGlvbiBpcyBjb25mdXNpbmcuICBZb3Ugb25seSBu
ZWVkIHRvIHNheSB0aGF0IHlvdSBhcmUgbm90IGFsdGVyaW5nIGZ1bGwNCj4+Y29zdCBtYXAgcmVz
b3VyY2VzIGluIGFueSB3YXkgYW5kIHRoYXQgY2xpZW50cyBuZWVkIHRvIHVzZSBmaWx0ZXJlZCBj
b3N0IG1hcHMNCj4+aWYgdGhleSB3YW50IG11bHRpcGxlIGNvc3RzIGF0IHRoZSBzYW1lIHRpbWUu
ICAoT2J2aW91c2x5IHlvdSBjb3VsZCBoYXZlLCBidXQNCj4+Y3JlYXRpbmcgbXVsdGlwbGUgcmVz
b3VyY2VzIHdpdGggdGhlIGZ1bGwgY29tYmluYXRvcmlhbCBtZXNzIGNhdXNlZCBieQ0KPj5jb21i
aW5pbmcgbWFueSBjb3N0IHR5cGVzIGlzIHVud2llbGR5LikgIEF0IGEgbWluaW11bSwgdGhlIHNl
Y29uZA0KPj5wYXJhZ3JhcGggaGVyZSBjYW4gYmUgcmVtb3ZlZC4NCj4+DQo+PlNlY3Rpb24gMy42
LjINCj4+DQo+PklNUE9SVEFOVDogWW91IGRvbid0IGRlZmluZSB3aGF0IGhhcHBlbnMgd2hlbiBh
IGNsaWVudCBwcm92aWRlcyAib3ItDQo+PmNvbnN0cmFpbnRzIg0KPj5hbmQgImNvbnN0cmFpbnRz
IiBhdCB0aGUgc2FtZSB0aW1lLiAgVGhlcmUgYXJlIHNldmVyYWwgdmFsaWQgb3B0aW9ucywgYnV0
IHlvdQ0KPj5uZWVkIHRvIGNob29zZS4NCj4+DQo+PlNlY3Rpb24gMy42LjMNCj4+DQo+Pkl0IGlz
IHByb2JhYmx5IHdvcnRoIGV4cGxpY2l0bHkgbm90aW5nIHRoYXQgaWYgInRlc3RhYmxlLWNvc3Qt
dHlwZXMiDQo+PmRvZXMgbm90DQo+PmluY2x1ZGUgdmFsdWVzIGZyb20gIm11bHRpLWNvc3QtdHlw
ZXMiLCB0aGVuIHRob3NlIHR5cGVzIGNhbid0IGJlIGluY2x1ZGVkIGluDQo+PiJjb25zdHJhaW50
cyIvIm9yLWNvbnN0cmFpbnRzIi4NCj4+DQo+PlBsZWFzZSBleHBsYWluIHRoZSBkZWZhdWx0IHZh
bHVlIGZvciB0aGUgaW5kZXggZm9yIHRoZSAiY29uc3RyYWludHMiLyJvci0NCj4+Y29uc3RyYWlu
dHMiIGV4cHJlc3MgaW4gdGhpcyBzZWN0aW9uIGluIGFkZGl0aW9uIHRvIHdoZXJlIGl0IGlzIGhp
ZGRlbiBpbiBhIG5vdGUNCj4+bGF0ZXIgaW4gdGhlIGRvY3VtZW50Lg0KPj4NCj4+U2VjdGlvbiAz
LjYuNQ0KPj4NCj4+VXBwZXJjYXNlIGZvciAibXVzdCBub3QiIGluIHRoZSBzZWNvbmQgcGFyYWdy
YXBoLiAgKFRoZSAibWF5IiBsYXRlciBpbiB0aGUNCj4+cGFyYWdyYXBoIG1pZ2h0IGJlIGJldHRl
ciBhcyAiY2FuIi4pDQo+Pg0KPj5JbiB0aGUgZXhhbXBsZSwgdGhlIHJlc291cmNlIG5hbWVkICJm
aWx0ZXJlZC1tdWx0aWNvc3QtbWFwIiBpcyBwcm92aWRlZCBmb3INCj4+bGVnYWN5IHJlYXNvbnMg
b25seS4gIFdoeSBib3RoZXIgaW5jbHVkaW5nICJtYXgtY29zdC10eXBlcyIgYW5kICJjb3N0LXR5
cGUtDQo+Pm5hbWVzIiBhdCBhbGwgd2hlbiAiZmlsdGVyZWQtY29zdC1tYXAtZXh0ZW5kZWQiIGlu
Y2x1ZGVzIGFsbCB0aGF0IGFuZCBtb3JlPw0KPj4NCj4+U2VjdGlvbiA0LjEuMQ0KPj4NCj4+VGhl
IGRlZmluaXRpb24gb2YgdGhlIHNjaGVtYSBoZXJlIChhbmQgbGF0ZXIpIGFjdHVhbGx5IHJlZGVm
aW5lcyB0aGUgb2JqZWN0DQo+PmNvbXBsZXRlbHkuICBJIGZvdW5kIHRoYXQgY29uZnVzaW5nIGlu
aXRpYWxseS4gIEl0IHdvdWxkIGJlIGdvb2QgdG8gaWRlbnRpZnkgdGhlDQo+PipjaGFuZ2VzKiBm
cm9tIHRoZSBiYXNlIHNwZWNpZmljYXRpb24gc29tZWhvdy4NCj4+DQo+PkNhbiB0ZXN0YWJsZS1j
b3N0LXR5cGUtbmFtZXMgYmUgcHJlc2VudCBhbmQgZW1wdHkgaWYgY29zdC1jb25zdHJhaW50cyBp
cw0KPj5mYWxzZT8NCj4+VGhlIGZpcnN0IHBhcnQgb2YgdGhlIGRlZmluaXRpb24gcGVybWl0cyB0
aGF0LCB0aGUgc2Vjb25kIGZvcmJpZHMgaXQuDQo+Pg0KPj5TZWN0aW9uIDQuMS4yDQo+Pg0KPj5U
aGUgcmVkZWZpbml0aW9uIG9mIFBJREZpbHRlciBpcyB1bm5lY2Vzc2FyeS4NCj4+DQo+PklNUE9S
VEFOVDogcGlkcyBpcyBvcHRpb25hbCBpbiBSRkMgNzI4NS4gIFdoeSB0aGUgY2hhbmdlPw0KPj4N
Cj4+SSBmaW5kIHRoZSByZWRlZmluaXRpb24gb2YgdGhlIG9wdGlvbmFsaXR5IG9mIGNvc3QtdHlw
ZSB0byBiZSB3b3J0aHkgb2Ygc3BlY2lhbA0KPj5ub3RlLg0KPj4NCj4+SW4gdGhlIGRlZmluaXRp
b24gb2YgIm9yLWNvbnN0cmFpbnRzIiwgeW91IHVzZSBhICJkYXRhYmFzZSBxdWVyeSINCj4+d2hl
cmUgd29yZHMNCj4+d291bGQgc3VmZmljZS4NCj4+DQo+PlNlY3Rpb24gNC4xLjMNCj4+DQo+Pkkg
ZmluZCB0aGUgY2hvaWNlIG9mIHZhbHVlIGZvciAiY29zdC10eXBlIiB0byBiZSBwcm9ibGVtYXRp
Yy4gIEl0IGlzIGEgc3RyaW5nIGluIHRoZQ0KPj5iYXNlIHByb3RvY29sLCBzbyBjaGFuZ2luZyB0
byBhbiBlbXB0eSBvYmplY3QgaXMgbGlrZWx5IHRvIGNhdXNlIG1vcmUgaXNzdWVzDQo+PnRoYW4g
c2ltcGx5IG9taXR0aW5nIGl0Lg0KPj4NCj4+U2VjdGlvbiA0LjIgY29udGFpbnMgbWlzbWF0Y2hl
ZCBicmFjZXMvcGFyZW5zIGZvciBzZWN0aW9uIHJlZmVyZW5jZXMuDQo+Pg0KPj5TZWN0aW9uIDQu
Mi4yDQo+Pg0KPj5JTVBPUlRBTlQ6IFRoaXMgcHJvdmlkZXMgYSBkZWZpbml0aW9uIGZvciBSZXFG
aWx0ZXJlZENvc3RNYXAgdGhhdCBpcyB2ZXJ5DQo+PmRpZmZlcmVudCB0byB0aGF0IGluIHRoZSBi
YXNlIHNwZWNpZmljYXRpb24uICBJIHRoaW5rIHRoYXQgdGhpcyBzaG91bGQgaGF2ZSBiZWVuDQo+
PlJlcUVuZHBvaW50Q29zdE1hcC4NCj4+DQo+PkFzIGJlZm9yZSwgcmVwZWF0aW5nIHRoZSBkZWZp
bml0aW9uIG9mIEVuZHBvaW50RmlsdGVyIGlzIHVubmVjZXNzYXJ5Lg0KPj4NCj4+U2VjdGlvbiA0
LjIuMyAtIHNlZSBjb21tZW50IG9uIDQuMS4zDQo+Pg0KPj5TZWN0aW9uIDUNCj4+DQo+Pkkgd291
bGQgYmUgbW9yZSBjb21mb3J0YWJsZSBpZiB0aGUgZXhhbXBsZXMgdXNlZCBvYnZpb3VzbHktc3B1
cmlvdXMNCj4+bWV0cmljcyAoZS5nLiwgImNhdHRsZS1oZWFkLWNvdW50IiwgInNtZWxsIiwgInNo
b2Utc2l6ZSIsIGV0Yy4uLikgdGhhbiB0aGVzZQ0KPj5tZXRyaWNzIHRoYXQgYXJlIHByZXR0eSBw
bGF1c2libGUuICBNb3JlIHNvIHdoZW4geW91IGNsYWltIHRoYXQgdGhleSBhcmUNCj4+d2lkZWx5
IHZhbHVlZCwgd2hpY2ggaW1wbGllcyBzb21lIHNvcnQgb2YgdmFsaWRpdHkuDQo+Pg0KPj5JdCBz
aG91bGQgYmUgcmVsYXRpdmVseSBlYXN5IHRvIHBvcHVsYXRlIENvbnRlbnQtTGVuZ3RoIG5vdyB0
aGF0IHRoZQ0KPj5leGFtcGxlcyBhcmUgImZpbmFsIi4NCj4+DQo+PlNlY3Rpb24gNS4xDQo+Pg0K
Pj5Zb3UgaGF2ZSB1bm1hdGNoZWQgYnJhY2VzIGluICJtZXRhIiBkdWUgdG8gdGhlIGNvbW1lbnQu
DQo+Pg0KPj5TZWN0aW9uIDUuMg0KPj4NCj4+RG8geW91IHdhbnQgdG8gc2hvdyBvbmUgb2YgdGhl
IGV4YW1wbGVzIGFzIGhhdmluZyBubyBjb3N0IHZhbHVlcyBhdCBhbGwNCj4+YWNyb3NzIGFsbCB0
aGUgY29zdCB0eXBlcz8NCj4+DQoNCg==


From nobody Thu Apr  6 07:47:22 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A6F1294B9; Thu,  6 Apr 2017 07:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 2MZ4NyIdU-QA; Thu,  6 Apr 2017 07:47:13 -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 BDA8C129457; Thu,  6 Apr 2017 07:47:13 -0700 (PDT)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v36ElBKd026308 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 6 Apr 2017 09:47:12 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
Subject: Re: Secdir last call review of draft-ietf-httpbis-encryption-encoding-08
To: Martin Thomson <martin.thomson@gmail.com>
References: <149142527327.21912.5654685591478038284@ietfa.amsl.com> <CABkgnnU7qXVeCDxoRbG8i6GbxJTA6gRpyHH0Yf+h0eRAJ+WLxw@mail.gmail.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <1f550ddb-a279-ad2b-0599-c9ed2c95da09@nostrum.com>
Date: Thu, 6 Apr 2017 09:47:08 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnU7qXVeCDxoRbG8i6GbxJTA6gRpyHH0Yf+h0eRAJ+WLxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lAw_ImSrW-RJwZK4Pofva1Ew-Kc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 14:47:15 -0000

On 4/5/17 5:32 PM, Martin Thomson wrote:
> On 6 April 2017 at 06:47, Robert Sparks <rjsparks@nostrum.com> wrote:
>> My only concern is that the document suggests it would be ok to use a
>> counter to provide a unique salt value
>> for each message. I suspect that provides the kind of information leak
>> the draft discusses avoiding.
> Hi Robert, can you explain what sort of leakage you are concerned
> about?  I mean, I can understand how you could construct the sequence
> of resources that were encrypted using a counter for the salt, but I
> don't know what that might imply.
Things like these:

- A third party that could see that sequence would know if there were gaps.

- If creation or transmission time can be approximated (perhaps via file 
stats),
   the third party can more quickly assess the rate of creation, and 
have a strong
   idea of when to look for the next one.

Of course for both of those, the 3rd party would need to somehow know the
content came from the same source, but it's easy to see systems built 
using this
that would expose that.
>
> That said, I think that the counter thing can be removed.  We require
> 128 bits of salt, which is a space that is large enough to select
> randomly from in perpetuity.
That would be my personal preference.


From nobody Thu Apr  6 07:47:45 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81395129513; Thu,  6 Apr 2017 07:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level: 
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 un9mGXcoojcl; Thu,  6 Apr 2017 07:47:42 -0700 (PDT)
Received: from [IPv6:2001:420:270b:1250:5dca:678:694f:89fd] (unknown [IPv6:2001:420:270b:1250:5dca:678:694f:89fd]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id F2A4D1294B9; Thu,  6 Apr 2017 07:47:38 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7B3A66BF-EDC5-4770-B3FA-57BFB7047A41"
Reply-To: Chair Ietf <chair@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Highlights from IETF 98
Date: Thu, 6 Apr 2017 10:47:39 -0400
Message-Id: <3190B140-05C2-4894-B0AC-8D079387C671@ietf.org>
To: IETF Discussion <ietf@ietf.org>, 98all@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MTW_wK7bRWpdkMLaWeY1qIIaeoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 14:47:44 -0000

--Apple-Mail=_7B3A66BF-EDC5-4770-B3FA-57BFB7047A41
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99ve written a short blog post recapping a few highlights from =
IETF 98: https://www.ietf.org/blog/2017/04/highlights-from-ietf-98/ =
<https://www.ietf.org/blog/2017/04/highlights-from-ietf-98/>

Alissa Cooper, IETF Chair=

--Apple-Mail=_7B3A66BF-EDC5-4770-B3FA-57BFB7047A41
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; -webkit-line-break: after-white-space;" =
class=3D"">I=E2=80=99ve written a short blog post recapping a few =
highlights from IETF 98:&nbsp;<a =
href=3D"https://www.ietf.org/blog/2017/04/highlights-from-ietf-98/" =
class=3D"">https://www.ietf.org/blog/2017/04/highlights-from-ietf-98/</a><=
div class=3D""><br class=3D""></div><div class=3D"">Alissa Cooper, IETF =
Chair</div></body></html>=

--Apple-Mail=_7B3A66BF-EDC5-4770-B3FA-57BFB7047A41--


From nobody Thu Apr  6 10:00:01 2017
Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 297A6126CD8; Thu,  6 Apr 2017 10:00:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Rich Salz <rsalz@akamai.com>
To: <secdir@ietf.org>
Cc: draft-ietf-mmusic-dtls-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
Subject: Secdir last call review of draft-ietf-mmusic-dtls-sdp-22
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149149800009.21962.16244679330016077024@ietfa.amsl.com>
Date: Thu, 06 Apr 2017 10:00:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NYpnqjnzxGySLJeRGLZgi6TYzaU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 17:00:00 -0000

Reviewer: Rich Salz
Review result: Has Nits

The term "ufrag" should be explained, or at least have a reference on
its first use.  It seems important :)

I think the "fingerprint" reference should be moved up to the bullet
list in section 4, from the bullet list in 5.1

Sec 4 uses the term "cryptographic random function" which is not a
common security term.  (See
https://en.wikipedia.org/wiki/Cryptographically_secure_pseudorandom_number_generator)
 I would just say "strong random function"; it's the number of random
bits that counts.  Or use CSPRNG as the term.

In Sec 9, it seems like quoting all the old text is way too verbose. 
I would just say "replace with the following NEW TEXT"
If it's not replacing an entire section, then say "the nnn paragraphs
starting with xxxxx" or similar construct.




From nobody Thu Apr  6 11:37:23 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38B2E12741D; Thu,  6 Apr 2017 11:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hLeYD19iKbOu; Thu,  6 Apr 2017 11:37:07 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.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 86DE2127775; Thu,  6 Apr 2017 11:37:06 -0700 (PDT)
X-AuditID: c1b4fb2d-dadfe700000033e1-4c-58e68ace1958
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by  (Symantec Mail Security) with SMTP id F4.C3.13281.ECA86E85; Thu,  6 Apr 2017 20:37:04 +0200 (CEST)
Received: from ESESSMB102.ericsson.se ([169.254.2.218]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0339.000; Thu, 6 Apr 2017 20:37:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Rich Salz <rsalz@akamai.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: RE: Secdir last call review of draft-ietf-mmusic-dtls-sdp-22
Thread-Topic: Secdir last call review of draft-ietf-mmusic-dtls-sdp-22
Thread-Index: AQHSrvc7Q+l4Ggm5cUSsh7p7Glw+qqG4q/Pg
Date: Thu, 6 Apr 2017 18:37:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CB51809@ESESSMB102.ericsson.se>
References: <149149800009.21962.16244679330016077024@ietfa.amsl.com>
In-Reply-To: <149149800009.21962.16244679330016077024@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbE9SvdC17MIg2NtWhY77u5gs3i2cT6L xdTlj1ks/m/pZLH4sPAhiwOrx+QjC5g9liz5yRTAFMVlk5Kak1mWWqRvl8CVcfbfBJaCV0IV 525MZ25gXCPUxcjJISFgItHQ/Zili5GLQ0hgPaPE+mtH2SCcxYwSB16/Ye1i5OBgE7CQ6P6n DdIgIuAqsa33MzNIDbPAQkaJ72c/MYIkhIESk08eYIQocpNY8eAkG4RtJLH08ipmEJtFQEVi z+yHzCAzeQV8JX5OB5spJOAi8f9uHyuIzQk0prd9B5jNKCAm8f3UGiYQm1lAXOLWk/lMEEcL SCzZc54ZwhaVePn4HyuErSSx9vB2FpDxzAKaEut36UO0KkpM6X7IDmLzCghKnJz5hGUCo+gs JFNnIXTMQtIxC0nHAkaWVYyixanFxbnpRsZ6qUWZycXF+Xl6eaklmxiBEXRwy2/dHYyrXzse YhTgYFTi4U348SRCiDWxrLgy9xCjBAezkgiv+nugEG9KYmVValF+fFFpTmrxIUZpDhYlcV6H fRcihATSE0tSs1NTC1KLYLJMHJxSDYzafiEL/xjv2ey6MOeOtVybC8OW1eWnHzvdZj9+++zs G7M2x+xcYnMoui/zvUKcyMsX6455fb6n7z6nwDn/0JHv9r3/Hdjq/1248K9l8up625nFak2b 4w6E6Kmc1ubfayO6Zcuiee7yq4xCV82Xivcq+n06VL3U6M1TUaMFLqbSey6+7fedNrlSiaU4 I9FQi7moOBEAilxX65wCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VR_iOhYXO0xwi65FUk9agdn1XQA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 18:37:09 -0000

SGkgUmljaCwNCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldyENCg0KTm90ZSB0aGF0LCBiYXNlZCBv
biBkaXNjdXNzaW9ucyBpbiBDaGljYWdvLCB0aGUgZHJhZnQgd2lsbCBiZSBleHRlbmRlZCB0byBh
bHNvIGNvdmVyIFRMUyBhc3NvY2lhdGlvbnMuIFNvLCBpdCBtYXkgZW5kIHVwIG9uIHlvdXIgdGFi
bGUgYWdhaW4gYXQgc29tZSBwb2ludCA6KQ0KDQpOZXZlciB0aGUgbGVzcywgSSB3aWxsIHJlcGx5
IHRvIHlvdXIgY29tbWVudHMsIGJlY2F1c2Ugc29tZSBvZiB0aGVtIGFyZSBub3QgcmVsYXRlZCB0
byB0aGUgY2hhbmdlLg0KDQo+UmV2aWV3ZXI6IFJpY2ggU2Fseg0KPlJldmlldyByZXN1bHQ6IEhh
cyBOaXRzDQo+DQo+VGhlIHRlcm0gInVmcmFnIiBzaG91bGQgYmUgZXhwbGFpbmVkLCBvciBhdCBs
ZWFzdCBoYXZlIGEgcmVmZXJlbmNlIG9uIGl0cyBmaXJzdCB1c2UuICBJdCBzZWVtcyBpbXBvcnRh
bnQgOikNCg0KSSB3aWxsIGFkZCBhIHJlZmVyZW5jZSB0byBkcmFmdC01MjQ1YmlzLg0KDQo+SSB0
aGluayB0aGUgImZpbmdlcnByaW50IiByZWZlcmVuY2Ugc2hvdWxkIGJlIG1vdmVkIHVwIHRvIHRo
ZSBidWxsZXQgbGlzdCBpbiBzZWN0aW9uIDQsIGZyb20gdGhlIGJ1bGxldCBsaXN0IGluIDUuMQ0K
DQpJIGFtIG5vdCBzdXJlLiBUaGUgYnVsbGV0IGxpc3QgaW4gc2VjdGlvbiA0IHRhbGtzIGFib3V0
IHRoZSBmaW5nZXJwcmludCBpbiBnZW5lcmFsLCB3aGlsZSB0aGUgYnVsbGV0IGxpc3QgaW4gNS4x
IHRhbGtzIGFib3V0IHRoZSBmaW5nZXJwcmludCBhdHRyaWJ1dGUuDQoNCj5TZWMgNCB1c2VzIHRo
ZSB0ZXJtICJjcnlwdG9ncmFwaGljIHJhbmRvbSBmdW5jdGlvbiIgd2hpY2ggaXMgbm90IGEgY29t
bW9uIHNlY3VyaXR5IHRlcm0uICAoU2VlDQo+aHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kv
Q3J5cHRvZ3JhcGhpY2FsbHlfc2VjdXJlX3BzZXVkb3JhbmRvbV9udW1iZXJfZ2VuZXJhdG9yKQ0K
Pkkgd291bGQganVzdCBzYXkgInN0cm9uZyByYW5kb20gZnVuY3Rpb24iOyBpdCdzIHRoZSBudW1i
ZXIgb2YgcmFuZG9tIGJpdHMgdGhhdCBjb3VudHMuICBPciB1c2UgQ1NQUk5HIGFzIHRoZSB0ZXJt
Lg0KDQpJIHdpbGwgdXNlICJzdHJvbmcgcmFuZG9tIGZ1bmN0aW9uIi4NCg0KPkluIFNlYyA5LCBp
dCBzZWVtcyBsaWtlIHF1b3RpbmcgYWxsIHRoZSBvbGQgdGV4dCBpcyB3YXkgdG9vIHZlcmJvc2Uu
IA0KPkkgd291bGQganVzdCBzYXkgInJlcGxhY2Ugd2l0aCB0aGUgZm9sbG93aW5nIE5FVyBURVhU
Ig0KPklmIGl0J3Mgbm90IHJlcGxhY2luZyBhbiBlbnRpcmUgc2VjdGlvbiwgdGhlbiBzYXkgInRo
ZSBubm4gcGFyYWdyYXBocyBzdGFydGluZyB3aXRoIHh4eHh4IiBvciBzaW1pbGFyIGNvbnN0cnVj
dC4NCg0KVGhpcyBjb21lcyB1cCBldmVyeXRoaW5nIGEgc2VjdGlvbiBpcyB1cGRhdGVkLiBTb21l
IHBlb3BsZSBvbmx5IHdhbnQgdG8gdXBkYXRlZCBwYXJ0cywgd2hpbGUgb3RoZXJzIHdhbnQgdGhl
IHdob2xlIHVwZGF0ZWQgc2VjdGlvbiAtIG5vIG1hdHRlciBob3cgbXVjaCBvciBsaXR0bGUgaGFz
IGJlZW4gdXBkYXRlZC4gU28sIEknZCBsaWtlIHRvIGtlZXAgaXQgYXMgaXQgaXMuDQoNCk5vdGUs
IGhvd2V2ZXIsIHRoYXQgYmFzZWQgb24gdGhlIGdlbi1hcnQgcmV2aWV3IEkgd2lsbCBwbGFjZSB0
aGUgdXBkYXRlcyBvZiBlYWNoIGluZGl2aWR1YWwgc2VjdGlvbiBpbiBhIHNlcGFyYXRlIHN1YiBz
ZWN0aW9uIG9mIHRoZSBkcmFmdC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQo=


From nobody Thu Apr  6 11:39:21 2017
Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A32AE12949B; Thu,  6 Apr 2017 11:39:07 -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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 nh9lFdUhMNt8; Thu,  6 Apr 2017 11:39:05 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 027A112941C; Thu,  6 Apr 2017 11:39:01 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v36IaV8C003449; Thu, 6 Apr 2017 19:38:57 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=W9wYQnNEMLT7AxPFEue4BiMpLKjygKMbW64GWvb7WjE=; b=Yg1cPPPQrjaXgWEI00gk7vjIdckqRyXWPB7gWj0Wp/VyZLfjSFdhkrcNSx+qjXiA8W4f 3zy5vVXDDcKr3PIjQ5vE0am3CAqk8oBdqJk0igexx1DhxO/aOcsOajrxvFFL7ePHSpg9 AKBiyxiTkC35GkTCG+h0SnLkEyaolg4Uld3gKU3y4eO1a7nNy8WKcv6/UQz0cO1e5Exf 0K4tfRnRGPogx22qlacuAdUA3j99gArBffzSOaulCHO07yFIdGKP8yvWwNGwvpfGRhWX 2E//+lWJfC28ny0ZSbPDa9Af+LmhLP6PU8rPIK0z/EJbAo3TBbBHL+xM7rRSJVOnH4SJ JA== 
Received: from prod-mail-ppoint2 (a184-51-33-19.deploy.static.akamaitechnologies.com [184.51.33.19] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 29nrut0s7g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 06 Apr 2017 19:38:56 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v36IZqV4015275; Thu, 6 Apr 2017 14:38:56 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 29j7hujnc6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 06 Apr 2017 14:38:56 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 6 Apr 2017 14:38:53 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1178.000; Thu, 6 Apr 2017 14:38:53 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: RE: Secdir last call review of draft-ietf-mmusic-dtls-sdp-22
Thread-Topic: Secdir last call review of draft-ietf-mmusic-dtls-sdp-22
Thread-Index: AQHSrwTMt/3hOQnvJkaFTThgvFfUh6G4q8xQ
Date: Thu, 6 Apr 2017 18:38:52 +0000
Message-ID: <4f01bce56f4c4bf7b9d800b70d8cf9f5@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <149149800009.21962.16244679330016077024@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B4CB51809@ESESSMB102.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CB51809@ESESSMB102.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.153]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-06_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704060150
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-06_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704060150
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bD2HC7UR3OYNylrzNwUZ7JjOgGo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 18:39:08 -0000

PiBOb3RlIHRoYXQsIGJhc2VkIG9uIGRpc2N1c3Npb25zIGluIENoaWNhZ28sIHRoZSBkcmFmdCB3
aWxsIGJlIGV4dGVuZGVkIHRvIGFsc28NCj4gY292ZXIgVExTIGFzc29jaWF0aW9ucy4gU28sIGl0
IG1heSBlbmQgdXAgb24geW91ciB0YWJsZSBhZ2FpbiBhdCBzb21lIHBvaW50IDopDQoNCjopDQog
DQo+ID5JIHRoaW5rIHRoZSAiZmluZ2VycHJpbnQiIHJlZmVyZW5jZSBzaG91bGQgYmUgbW92ZWQg
dXAgdG8gdGhlIGJ1bGxldA0KPiA+bGlzdCBpbiBzZWN0aW9uIDQsIGZyb20gdGhlIGJ1bGxldCBs
aXN0IGluIDUuMQ0KPiANCj4gSSBhbSBub3Qgc3VyZS4gVGhlIGJ1bGxldCBsaXN0IGluIHNlY3Rp
b24gNCB0YWxrcyBhYm91dCB0aGUgZmluZ2VycHJpbnQgaW4gZ2VuZXJhbCwNCj4gd2hpbGUgdGhl
IGJ1bGxldCBsaXN0IGluIDUuMSB0YWxrcyBhYm91dCB0aGUgZmluZ2VycHJpbnQgYXR0cmlidXRl
Lg0KDQpBaCwgb2theS4gIFBlcmhhcHMgc29tZSB3b3JkaW5nIGNhbiAgY2xlYXIgdGhhdCB1cD8g
IE9yIG1heWJlICJmaW5nZXJwcmludCBhdHRyaWJ1dGUiIGFuZCwgd2hhdCwgImFzc29jaWF0aW9u
IGZpbmdlcnByaW50IiA/DQoNClRoYW5rcyBmb3IgcmVhZGluZy4NCg==


From nobody Thu Apr  6 15:28:17 2017
Return-Path: <alcaraz@lcc.uma.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E206E1294B4; Wed,  5 Apr 2017 14:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level: 
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 vIecovrxnv-J; Wed,  5 Apr 2017 14:33:36 -0700 (PDT)
Received: from correo2.satd.uma.es (correo.satd.uma.es [150.214.57.2]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705D4129463; Wed,  5 Apr 2017 14:33:36 -0700 (PDT)
Received: from sol10.lcc.uma.es (sol10.lcc.uma.es [150.214.108.1]) by correo2.satd.uma.es (Postfix) with ESMTP id F365311800E; Wed,  5 Apr 2017 23:33:28 +0200 (CEST)
Received: from webmail.lcc.uma.es (sol10.lcc.uma.es [150.214.108.1]) by sol10.lcc.uma.es (Postfix) with ESMTP id C5BD24B0079; Wed,  5 Apr 2017 23:33:28 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 05 Apr 2017 23:33:28 +0200
From: Cristina Alcaraz <alcaraz@lcc.uma.es>
To: undisclosed-recipients:;
Subject: CRITIS 2017 Call for Papers
Message-ID: <4be04fc27b54ad2e33b74571f7ae7ad0@lcc.uma.es>
X-Sender: alcaraz@lcc.uma.es
User-Agent: RoundCube Webmail/0.8.5
X-SATD-MailScanner-Information: Please contact the ISP for more information
X-SATD-MailScanner-ID: F365311800E.A6E9E
X-SATD-MailScanner: Found to be clean
X-SATD-MailScanner-SpamCheck: no es spam, SpamAssassin (almacenado, puntos=-2.387, requerido 6, autolearn=not spam, AWL -0.48, BAYES_00 -1.90, RP_MATCHES_RCVD -0.00, SPF_PASS -0.00)
X-SATD-MailScanner-From: alcaraz@lcc.uma.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4tAOBRi45WgaGfkCLYJ5gBm7vNQ>
X-Mailman-Approved-At: Thu, 06 Apr 2017 15:28:15 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 21:33:39 -0000

Dear Colleague,

we invite you to submit a contribution to CRITIS 2017, the International 
Conference on Critical (Information) Infrastructures Security.

This year the conference will take place in Lucca, a gorgeous 
Renaissance city in Tuscany, 9-11 October 2017.

Papers can be submitted via EasyChair; for poster contributions, 
submission can be limited to an extended abstract. All accepted 
contributions will be included in full length in the pre-proceedings 
that will appear at the time of the conference; accepted papers are 
planned to be published in the LNCS Springer-Verlag series.

Special attention will be devoted to young talents. To this purpose, a 
price (YCA: Young Critis Award) will be awarded to the best contribution 
presented by a young author.

On 12-13 October, the conference will be followed by two satellite 
workshops on Energy and Water.

For further details, please visit our website www.critis2017.org . We 
would appreciate you advertise the conference by the attached leaflet.

The organizers:

Cristina Alcaraz, Hypatia Nassopoulos,
Antonio Scala, Gregorio D’Agostino,
Grigore Havarneanu


From nobody Thu Apr  6 16:43:19 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7901296A8; Thu,  6 Apr 2017 16:43:17 -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 crCOzDrcwatp; Thu,  6 Apr 2017 16:43:15 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::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 CB29D129353; Thu,  6 Apr 2017 16:43:14 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id i34so49427719qtc.0; Thu, 06 Apr 2017 16:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XY6gqnWhTn9qsReIXslK7UK7sTSpxq4gnLVh5Zc6RyQ=; b=IXs8Tx0ub7UK0OB4YITtr333HwVVBQe3GylXLSEVj1PwjvwzjBP4yPJWycYN6XgyiV 0Dux0NuZLw8YKlmqTTQhcyr1B+lKR0j+UCDWA+5oumOOhCHnhFCOACUhHrL48zKMFX/C MDVfJRYQLbepcXP5Q0ixOZVsnjU+uMNNzIsxOdzo/LLUXqqxqHDF4hhKXqRqcRhJ9XFp nG7ezmuHbG7oDFhpaEwPIpIjY+vKDjyL3Rd0Sjx0tEdL67Y3qOi9D45ibQR82j45SP5l UYZAXnzr7fk0dIwQ66jcqFiSKwCY5nG87HMlTwwvLd5/UApEr00tmM9tQDTLsnGOy7RB J2cA==
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=XY6gqnWhTn9qsReIXslK7UK7sTSpxq4gnLVh5Zc6RyQ=; b=BDtmZi1F0N3528KOtvT+EfMAuOH1ErlzhX9ZdqtZUWn77b0oAE7U6te0++FFdJmLE7 KHUZEguSdYUdOcpQxO/2YVm2bY/adyiHlaNSXY63p6sajXpHLINTm2qkGzIAiLMOizh1 VHG9rp1TELy9F6B107rskp9KE3Y0mPuRkO5MJ39eT+xfUUzLVC9XlUCsemcXek+qAvZi MshnZh1xjuktJ1iDnQm91dn0BqFLzzTfVHcHyzxIIoWptKQOEQ60H3LqUEarnq3Zq374 tvk485vb+2qw1hjYN7BkKfyRyjPdimdSM3jSfQaHbPEp08wrYxm7B3i9rT1PSFPQ5Y+6 4k4Q==
X-Gm-Message-State: AFeK/H1Ny1rS5Vlhy6/OKpPsNwZg69/0729VUzyGlQorqIyY/0r5U1SfZCaRsnj0rewDHQ1OwzdFLm5l16iJFA==
X-Received: by 10.200.33.210 with SMTP id 18mr37476708qtz.159.1491522193900; Thu, 06 Apr 2017 16:43:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.203 with HTTP; Thu, 6 Apr 2017 16:43:13 -0700 (PDT)
In-Reply-To: <1f550ddb-a279-ad2b-0599-c9ed2c95da09@nostrum.com>
References: <149142527327.21912.5654685591478038284@ietfa.amsl.com> <CABkgnnU7qXVeCDxoRbG8i6GbxJTA6gRpyHH0Yf+h0eRAJ+WLxw@mail.gmail.com> <1f550ddb-a279-ad2b-0599-c9ed2c95da09@nostrum.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 7 Apr 2017 09:43:13 +1000
Message-ID: <CABkgnnVb+CZRnLMH-=so+XKFOGK+f2tWMZct5Yg2ADB6WepUQg@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-httpbis-encryption-encoding-08
To: Robert Sparks <rjsparks@nostrum.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f7cxjqQKWUTQ3VqvnOpYOM9czoI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 23:43:17 -0000

On 7 April 2017 at 00:47, Robert Sparks <rjsparks@nostrum.com> wrote:
>>
>> That said, I think that the counter thing can be removed.  We require
>> 128 bits of salt, which is a space that is large enough to select
>> randomly from in perpetuity.
>
> That would be my personal preference.

Sold.  https://github.com/httpwg/http-extensions/commit/8c31395609cdd2d1a91059fcbaa5a33fda622525


From nobody Thu Apr  6 20:25:08 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76911127058 for <ietf@ietfa.amsl.com>; Thu,  6 Apr 2017 20:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9vafmoV-xxc for <ietf@ietfa.amsl.com>; Thu,  6 Apr 2017 20:25:02 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 03DD2127077 for <ietf@ietf.org>; Thu,  6 Apr 2017 20:25:02 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id p22so53490606qka.3 for <ietf@ietf.org>; Thu, 06 Apr 2017 20:25:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=En967WCnFS8WvfJ4eR7fsh7lEOTWAnxJl8V3/AV3TTk=; b=dTAKVhzZ+WWNBhCd7nfQ54f8fXl+VYV2aQa3IXiBRrqAMLA7E7RJyk96tJ849hf+IB 1lJuayM9Je0BA9cJ3eoUddYdec9exhY0f3WEVO8RqglvRsrr4qYwpOIVzHYWlpGalYbj F9aSPmGGTEWUvIcwSmofVDdHCL0E991V7dhLrMzCoA6WoLq5O1N6P+qkAFr47jk6YGwD t0Y+RK2XG4CeMXsqqBTSx0BiI0efguooeTFFKKctLKKQm+5kxdMxPpBW5CPbM/G6msTo ForFtvYfsSJDEtbIEpHfZP7ZRSxejGCNBHlPU6uTBCKhBO2xqeXxwI+5Cocs70UeuKaQ PWsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=En967WCnFS8WvfJ4eR7fsh7lEOTWAnxJl8V3/AV3TTk=; b=Kyz/km00J9GiqHHCEsovFlV+/P8PnEhJouiz3qkROi7ZUqjHSLFHB6Oo37YjD7xg/X U97bvt5i2M0apQduKw16ppsjjA71KoBPN6BO7RdQjHpkOrv+PbPHNQDF50Q7OV3s2yOm JSpkB9gvOZVR4HgCdweqHQkJ3MyAC3G3D3xxeGew3C5DbDOEWXgykku6CV9xqGqpHey9 e5tHNRtzs/IpI8yEem74x8rKvcJXtT448FBfR5TezT9gQU7Oj3+e0flyq0lG43rY/UCR XZ+gwpdPwDoPkybA1bgBGjO++IxB/d7zRXKQ77EaP8s2OlR1znJkc6mT3iE2P/FGyTO0 AA8Q==
X-Gm-Message-State: AFeK/H03Owfw4N3yDaJSGP6H/WPJLguax0uSmraCxVtoRu/I4/g99AgCyF5DvU9BqA1fwxpJZbZLtpuNjzqnSg==
X-Received: by 10.55.136.2 with SMTP id k2mr38272542qkd.316.1491535500249; Thu, 06 Apr 2017 20:25:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.203 with HTTP; Thu, 6 Apr 2017 20:24:59 -0700 (PDT)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 7 Apr 2017 13:24:59 +1000
Message-ID: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
Subject: Review of draft-mm-wg-effect-encrypt-09
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DqDDGIvyumkNfZxz250Wl-tPBXw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 03:25:07 -0000

Draft: draft-mm-wg-effect-encrypt-09
Date: 2017-04-07

Overall

This document is unfocused and unclear in its intent.  It is filled with
unsubstantiated claims, misleading statements, bias, and implied recommendations
for bad practices.  I would oppose its publication in the current form.
Furthermore, I don't believe that small scale or editorial changes would be
sufficient to correct these problems.


Aside from weakening its utility and/or arguments, the lack of focus will allow
this document to be abused in various ways.  For instance, it might imply IETF
endorsement of the practices described in the document.  Given that the IETF has
published positions that in some cases reject these practices, this document
needs to be very precise with its claims.  In its current form, it is not nearly
careful enough.

If this document is going to be published as an RFC, then it needs to be very
clear about its intent and its position - or lack thereof - toward these
practices.  It might be possible to say that these practices were employed in
networks in the past and that encryption is reducing the viability of those
practices.  A value-neutral statement like that might be acceptable as long as
it were framed carefully.

What is problematic is the implicit argument that is presented.  This document
could easily be construed as the IETF legitimizing these practices.  This
includes things on which the IETF has published statements (see for example RFC
2804).

This steps firmly into to sticky mess that is the politics of encryption policy.
If the IETF is going to make a political statement with this document, then that
statement needs to be a lot better than this.

Furthermore, any statement needs to be consistent with previous statements,
where in this case that primarily means RFC 7258.  Right now it reads as an
attempt to dilute RFC 7258.

If this document were more clearly formulated as an even-handed treatment of
what happens today - without judgment - then it could be useful.  Here the model
of RFC 7754 is a good one.  It describes the different facets of a use case,
then the different practices that might be employed to achieve that goal.  For
each practice the pros, cons, and technical limitations are covered with an eye
to all involved parties.


The Real Purpose of this Document

I think that this is the real question that this document wants to ask is:

   In a world where we are forced to defend against pervasive monitoring by
   motivated and malicious actors, can we find a role for less pervasive
   monitoring by well-intentioned entities?

There is an interesting discussion to be had here, but I'm convinced after my
review that this document is the wrong vehicle for that discussion.  I'm also
inclined to suggest that this is the wrong question to ask in the first place.

To the extent that we have the tools necessary to protect against pervasive
monitoring, we have to accept that more-legitimate uses of monitoring are
collateral.  Mostly, that's just a function of the limitations of the imperfect
tools we have.

The value in this document is in the rather comprehensive collection of use
cases.  Sure, some we might not attribute much weight to, like wiretapping.
Others are frankly frightening and not just in the Orwellian sense.

The problems that are implied by the current practices of network operators is a
large vein of unexplored work for the community.  Spending effort on finding
better solutions to legitimate problems is worthwhile.

In other words, the right question might be:

   For each of these practices that we see today, are the use cases that
   motivate them legitimate and how might be implement alternative techniques
   that properly respect privacy and security?


Two- and Three- Party Interactions

A great many sections of the document are unclear about the relationships
between different actors.  It seems like many of the activities describe, which
are presented here as being beneficial, are performed by a third party without
the consent or involvement of the two communicating peers.  After all, those are
the cases where encryption most often interferes.

The assertion that some benefit is accrued to communicating peers as a result of
these actions is the constant subject of the text.  I observe that in most of
the cases listed in this document, the benefit is accrued primarily to the third
party.

Clarity around the arguments that the document makes with respect to benefits to
each of the involved parties is sorely lacking.

In addition to this, where benefits truly do accrue to communicating peers,
technical options that don't rely on privacy-invasive techniques are routinely
dismissed in an offhand fashion.  In this way, any moral imprimatur attributed
to the use case is used to justify the privacy-invasive method.


Document Structure

This document is very hard to read (and review).  Probably my biggest complaint
is that the sections are haphazardly organized.  They contain a mixture of use
cases (what does SP X want to do) and techniques (how do they do these things).
Material is duplicated between sections.  Sections cover 10 different use cases
while talking about techniques, then other sections talk about different
techniques whiles talking about a scenario.  This leads to a lot of repetition.

There are three axes that this document contemplates:

 - the techniques that are currently used in networks
 - the use cases that motivate these techniques
 - the deployment scenarios in which these use cases manifest

It would appear that the document attemps to start from the deployment
scenarios.  However, this causes use cases and techniques to be mixed.
Judicious use of cross-referencing might have made this arrangement tractable,
but there are virtually no cross references.


Section 1

I find the introduction of this document difficult to parse.  I think that what
it wants to say is pretty straightforward, but it manages this in quite an
obtuse way.  Here's what I think that it is trying to say:

1. The IETF (and the larger community) has reacted to revelations of pervasive
   monitoring by increasing the use of encryption.
2. That has been somewhat successful.
3. More encryption has an impact on some practices that network operators have
   become accustomed to employing.

Expressed in this way, you can see how you could make a value-neutral
statement.

On the first, you can definitely make an argument based on the documents that
the IETF have published.  However, it is a mistake here in assuming that the
IETF - or the revelations of global-scale surveillance - is directly responsible
for the uptick in adoption of cryptographic protection for Internet traffic.
This is something that the community as a whole has been working towards for
many years; these trends predate the actions this draft focuses on.  This is
particularly true for the hosted provider cases in Section 3, where business
motivations for protection are far stronger than any concerns over government
surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I don't
have to write a statement that will be labelled as having IETF consensus.

The immediate focus on opportunistic security is highly misleading, especially
in the web case.  The amount of opportunistically secured web traffic is
miniscule by global standards.  Since Firefox is the only browser to support OS
for the web, so adjust the following by market share: <https://mzl.la/2oc46ch>.

I understand that mail is more often opportunistically secured, and you will
hear the virtues of OS sung from the rooftops, but all evidence suggests that
this is just a transitory state.  Instant messaging is closer to the web case,
with the trend toward strong protections that include authentication.  Of
course, I don't believe that mail or instant messaging represent any significant
traffic volume, so you need to be very careful about the nature of the claims
that are being made.  It has to be that the volume of mail has to be a rounding
error when it comes to capacity planning for networks.

On the second point, when making claims about prevalence of encryption, I would
advise caution when citing statistics.  Here's the graph for the Mozilla figures
that I think are being cited <https://mzl.la/2obZjrb>. Here's a different graph
with a different number <https://mzl.la/2oc263J>.  This highlights the point
that statistics need to be carefully cited, because bare claims are difficult to
assess.  Methodology matters when it comes to these sorts of claims - are we
talking proportions of packets, requests, flows, or something else?
Furthermore, the citations in the document are made more difficult to assess by
being measured at very different times (where the two I cite here were made at
roughly the same point in time).

The statistics do support the notion that there is a significant amount of
encryption in use, but it would appear that the claim is that the amount of
encryption is *increasing*.  This is not an extraordinary claim, but no evidence
is offered in support of the claim.  It isn't a certain thing either.  From the
statistics that I have access to, there was a definite uptick in October of
2015, but the rate appears to be stable since then.

It appears that the remainder of the document is intended to address the third
of my points in some detail.  That's a good structure in theory, but see above.

I don't think that the "service provider" taxonomy works for this document.
Based solely on the structure of the document, the only service provider that
this document concerns itself with is the one who forwards the packets.  That
application service providers are involved as one of the endpoints is relevant
in some cases, but not all.  For that reason, I prefer "network operator" and to
use specific terms like "mail host" or "web server" as appropriate to the
context.


Section 2 (top section)

I like that the attacks on SMTP by network operators is highlighted here.

There's an implicit argument here that runs counter to established IETF
consensus.

   Some methods used by service providers are impacted by the use of encryption
   where middle boxes were in use to perform functions that range from load
   balancing techniques to monitoring for attacks or enabling "lawful
   intercept", such that described in [ETSI101331] and [CALEA] in the US.

This fails to remain neutral.  This implicitly makes a value-judgment about
relative morality/acceptability/value of certain practices.  What is
particularly insidious about this particular form is that it invites
interpretation that is subjectively coloured.  For instance, as a non-EU and
non-US citizen, I might consider the use of the particular lawful intercept
techniques offensive; thus I might interpret this as a spectrum between
inoffensive to offensive.  An employee of the US government might view this
somewhat differently and interpret this as a scale between low-value to
high-value.  I'm guessing here, but this is really just to highlight my point
about care.

A more serious concern is this statement:

   The loss of access to these fields may prompt undesirable security practices
   in order to gain access to the fields in unencrypted data flows.

I've read this argument before (see https://queue.acm.org/detail.cfm?id=2508864
for the long form), and it might even have an element of truth to it.  However,
it's not a statement that I personally attribute any real credibility to, and
nor do I think that it needs to be credited with any amount of seriousness.  I
certainly disagree with the IETF making any such statement.  It says that we are
collectively willing to bow in response to (anticipated) threats of violence.

Section 2.1

This is one of the few sections that talk about what it means to operate a
service as opposed to operate a network.

Overall, this section doesn't work particularly well.  The distinction between
integrated and standalone load balancing is an interesting division, but it
doesn't leverage this distinction well.  What causes a standalone load-balancer
to be necessary?  Is this something a network operator uses?  I see text on NFV
later, but it's far removed from the original text and it seems aspirational
rather than concrete.  On the other hand, many of the concerns in this document
simply don't apply to an integrated load balancer.

The amount of text on QUIC here is surprising.  Given how much of QUIC is
changing right now, we shouldn't publish a document that attempts to make claims
about what QUIC is or how it is operated.  This attempts to dive into the
details of QUIC connection migration in a way that presumes much about the
outcome of issues that the QUIC working group is still struggling with.

I would strongly recommend removing QUIC-specific language from this section and
the document as a whole.  We have an operational document in the QUIC working
group that would be a good venue to discuss some of these concerns.

Is this an oblique reference to (the much-loved) RFC 7974?

   Current protocols, such as TCP, allow the development of stateless integrated
   load balancers by availing such load balancers of additional plain text
   information in client-to-server packets.

Otherwise, I don't know what it means.

BTW, I like this parenthetical:

   (That said, care must be exercised to make sure that the information encoded
   by the endpoints is not sufficient to identify unique flows and facilitate
   Persistent Surveillance attack vector.)

I'm going to take this to the QUIC working group, because QUIC certainly doesn't
meet that bar right now.  It fully facilitates Persistent Surveillance in its
current form (proper noun?  I haven't really seen that term before, even though
it draws a neat parallel with Pervasive Surveillance).

Editorial:
* "pop" is a term of art that needs explanation.
* "QUIC?s", "network?s" - avoid smart quotes, and - more generally - the
  possessive form for the inanimate.
* "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".

Section 2.2

I think that this sums the situation up reasonably well.  It fails the
value-neutral test in a few ways though.  As I understand the situation,
surveying operates at many levels.  For accurate planning, models of endpoint
behaviour are used to determine things like whether loss or congestion is
affecting throughput.  Really good models require knowledge of what users are
attempting to do and the applications they are using (as mentioned, things like
browser version matter in these models).  For instance, it isn't enough to
understand that the user is trying to receive 720p video, you also have to know
that a 4k stream for the same content is available.

The degree to which these models are privacy-invasive is not even acknowledged.

Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect that
subtlety to be lost on many readers though.

Section 2.3.1

I find this sad, even if I can recognize the truth of it:

   A monitoring system could easily identify a specific browser,
   and by correlating other information, identify a specific user.

As a browser vendor, we don't consider this to be a feature, it's a bug.

Section 2.3.2.1

This is a strange section under which to put caching.  Caching is a use case
akin to compression.  I don't see it as belonging to the class of things that
rely on DPI.  You just intermediate the cleartext HTTP in the way that RFC 7230
recognizes.  Note that RFC 7230 explicitly does not endorse the practice of
transparent proxying for a range of reasons, not the least of which is the
complete lack of transparency (yep).

Section 2.3.2.2

Again, it's strange to see differential treatment under DPI.  I was fairly sure
that fingerprinting was used here as well.

Section 2.4

This section doesn't even attempt to recognize that applications are much better
now at scaling content to suit the device on which that content is intended to
be consumed.  It should.

This section should not represent compression as an unmitigated good.  I'm told
that significant damage can be done to video streams by "well-intentioned"
compression middleboxes.

Yet again I see a call back to the implicit threat of violence in "they will
adopt undesirable security practices".  Statements in that form have no place in
IETF RFCs.

Section 2.5

This mentions RFC 7754 then blithely ignores its primary conclusion. Generally,
The treatment in RFC 7754 of this subject is more even-handed.

The use of particular examples (betting, gambling, dating) shows cultural bias.

Jargon warning: "core network", "the mobile network" ("the"?)

Section 2.5.2

   This type of granular filtering could occur at the endpoint, however the
   ability to efficiently provide this as a service without new efficient
   management solutions for end point solutions impacts providers.

The initial premise here (up to the first comma) is the conclusion of RFC 7754.
I disagree with the conclusion, and I suspect so does RFC 7754.  In scenarios
where this matters, endpoints are routinely managed centrally.  The range of
options for this sort of management are plentiful and diverse.

Section 2.5.3

This describes a captive portal, which in the case where the service provider
has a relationship with their customers, seems like a poor solution.  See the
CAPPORT working group for ways in which people are actually working on a
solution to this problem.

Section 2.6

The capitalization of section headings is inconsistent here (and throughout).

Section 2.6.1

Isn't this a duplicate of Section 2.1?

Section 2.6.2

I can't parse this statement:

   Approved access to a network is a prerequisite to requests for Internet
   traffic - hence network access, including any authentication and
   authorization, is not impacted by encryption.

And then we get into zero rating, which is a hot-button topic.  No
acknowledgment given to the sensitivities on the subject, or even a superficial
exploration of the technical options that are available.

This text references a non-existent Appendix.

Section 2.6.5

This paragraph is strange.  It starts by describing what appears to be use cases
(are those scare quotes?).  It finishes by implying that these are attacks on
privacy (which they are).

What is "Non-Customer Proprietary Network Information"?  I hope that this isn't
an attempt to somehow privilege the information so that it seems less than
privacy-invasive.

Section 2.7

This is one of the areas that is most legitimately affected by increased
adoption of encryption.  I have no doubt that having detailed information about
the application and its use makes the process of troubleshooting easier.

This is the first mention in the document of network-based optimization.  Was
the section describing that cut from an earlier draft?

The use of websockets as a primary example is an odd one.  It's just not that
common.  For reference, we see >20% failure rates on encrypted websockets and
>50% failures in the clear; no one in their right mind would rely on websockets.
If the point is that HTTP is carrying more traffic (see
http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying just that
would be more effective.

Section 3

It would help if "hosted environments" was defined before diving in.

Section 3.1

The paragraph on DLP is ironically amusing.  Encryption exists to prevent
private information leakage, but the assertion here is that encryption is
hampering DLP attempts.

It's true that protection of intellectual property is an important business
goal, but this handling suggests an architecture that I'm fairly sure is counter
to established wisdom (see "SSL added and removed here :-)":
https://www.washingtonpost.com/rf/image_404h/2010-2019/WashingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg).
Worse, this casually dismisses a model that is actually more likely to work.
Malware encrypts too (https://arxiv.org/abs/1607.01639).

Section 3.1.1

Who is the customer here?

Why does the hosting provider need to monitor access?  They have the ability to
limit accesses, but this is suggesting that what happens within the envelope of
what they permit is important for them to know.  I'd be surprised if you could
show that this is true.  Hosting providers - in my experience - value their
ongoing business and would not jeapardize it by snooping on their customers.
It's different if the customer opts in to a security service, but that
demonstrates a cooperative situation, where the rest of this document is largely
concerned with adversarial uses of encryption.

Section 3.1.2

This is another example where the organization of the document could
be improved.

Again with the "SSL added and removed here :-)" recommendation.  PCI don't
permit that for good reason.

Section 3.2.1

I don't believe that monitoring of these types of application require cleartext
access.  There are two parties involved: the provider of the application and the
user of it.  The provider has most of the power here and can theoretically
design the system to allow whatever level of access they require.  To the extent
that the user needs protection from the application provider, that is a matter
of negotiation between them.

I don't see how the adversarial three-party situation presented in the rest of
the document applies in this situation.

Section 3.2.2

No real mention of the effect of encryption here, or is this just saying that
there is no issue here?

I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of the IETF
saying things like "PGP may be a front runner" though.

Section 3.3

There's certainly a lot of detail here, but I had a really hard time extracting
value from this section.  I can't see how data storage is fundamentally
different to the general case of an application provider.

Section 4.1.1

I appreciate the recognition that endpoint-based techniques work.  The
implication that this isn't the obvious solution, much less so.

Section 4.1.2

I'm confused about the purpose of this section.  This seems to be talking about
the sort of network-based methodologies an application provider might employ to
ensure that their application is working as intended.  Why would the application
provider not have access to detailed logging and usage metrics?

As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is cited no
fewer than three times in the same paragraph.  It makes some fairly bold claims
about its effect on privacy that I don't believe will hold up to analysis.

Section 4.1.3.1

This section correctly identifies the issue as one of shortcomings in logging,
not increased use of encryption.

I would have stopped there, but the section persists and ultimately references
RFC 7974, which is widely recognized as a monstrously bad idea (the IESG note is
fairly clear on this point).

Section 4.1.3.2

"HTTP/2", not "HTTP2".

I don't see how this section belongs in this document.  The 1:1 correlation
between actions and flows in HTTP was a mistake of the 1980s that we've spent a
lot of time on correcting (sometimes unsuccessfully, see pipelining).

Section 4.1.3.3

It's not a "service call" it's just a request.

Section 4.2

If the inclusion of a reference to RFC 7457 is to support a claim that TLS is
attacked, that's sailing far too close to an endorsement of attacks than I am
comfortable with.  However, I don't believe that any of the listed attacks
remain viable in modern applications.  What is most often the case is that a
trust anchor is installed on enterprise users' machines and new certificates are
minted as needed.  In other words, the host that is accessing the HTTPS site is
owned by the enterprise and modified so that it can comply with its policies.

When you recommend attack like this (to be clear, I would oppose publication of
text that does this), you need to acknowledge the downsides.  For example, MitM
devices routinely break connections, they hide the true security status of
communications from endpoints and users, they frequently implement weaker
versions of protocols, they often don't include the same degree of rigor in
things like certificate validation, and probably many more things that I can't
casually list off the cuff.

The discussion of caching here warrants a new section.

Section 5.1

s/effect/affect

No complaint here, just an advertisement for technical solutions that aren't
affected by increases in encryption.  Good, though I'm not sure if the section
meets the document's criteria for inclusion.

Section 5.3

No cititation for APWG.  Not an IETF working group from what I can see.

There's a presumption here that administrators need to perform these tasks.  Why
can't endpoints do this?  It would certainly be a whole lot less invasive that
way.  Take a look at how browsers implement checks for "bad" sites (which
include phishing sites).  These methods have some fairly significant privacy
safeguards without compromising on performance.

Section 5.5

See my comment about about endpoint-based methods.

Section 5.6

I believe that the spoofed source address problem is not relevant to this
document.  It's a fairly well understood problem.  That said, if we could wave a
magic wand and get BCP 38 deployed, that might be nice.

Section 6.1

As this says, it's fairly well understood that - for HTTP - SNI is used.  The
point that it is optional is interesting, but doesn't deserve the amount of
attention this section devotes to it.  The clients that don't include SNI are in
a diminishing minority.

That said, this doesn't pay any attention to another feature in HTTP/2:
connection coalescing.

Section 6.2

ALPN will be encrypted in TLS 1.3.

Section 6.3

This reads as a invitation to perform traffic analysis (a statement that I
oppose).  Note that we have added padding to most recent protocols (HTTP/2 and
TLS 1.3 in particular) to give endpoints the ability to resist this sort of
attack.

Note that block ciphers can add ~240 octets of discretionary padding per record.
That can be pretty effective if you are careful.

Section 7

This section is duplicative of much of the rest of the document.  I realize that
editing is hard, but see my earlier comments about structure.

It's obvious that this section is about QUIC.  That shows in several ways.  It's
nice how it doesn't say so out loud, but it leaks through in several confusing
ways.  See below.

Section 7.1

This section is purportedly about encrypted ACKs, which won't happen until we
get to QUIC.  But the points regarding proxies (b, c, d) are not prevented by
encrypted ACKs, they are prevented by encryption more generally.  Point e is
defeated by integrity protection of ACKs, not confidentiality protection.

I hope that the IETF never publishes draft-dolson-plus-middlebox-benefits; it
makes claims about the benefits of specific solutions for different use cases
with the goal of justifying those solutions.  At the same time, it fails to
recognize the existence of alternative, often superior, solutions for those use
cases.  In other words, it has many of the same issues as this document.

FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I don't
know how to close the gap between the privacy assurances I wish it had and the
privacy weaknesses it has.

The phrase "trusted proxies" is a dangerously misleading phrase.  The concept of
trust is - particularly in this context - frequently abused.

Sections 7.2 and 7.3

I'd be interested in learning about the justification for these features (again,
go back to my comment about to whom the benefit accrues, and I'd advise caution
not to make the trickle-down economics mistake of using second-order effects).
Personally, I'm not that sad that they are going to be negatively affected.

Section 7.2, Point d seems to be saying something about a multiplexed protocol,
not one that has an encrypted transport header (see above regarding QUIC).

All these points equally apply to HTTPS, which suggest that encrypted transport
headers is not the issue (unless by transport we mean HTTP).

Section 7.4

s/GPSR/GPRS/ ?

Section 8

I generally agree with the first statement here, but after having read the
document, I could take away some very different views on what the "problems at
hand" actually are.  I suspect that different people will have very different
takeaways.

The conclusion section of a document is not the right place to start introducing
new information, particularly information relevant to RFC 2804.

Not sure where this is going:

   Terrorists and criminals have been using encryption for many years.

Because it's disconnected from the remainder of the paragraph.  If you are going
to invoke the T-word, you had better have a strong argument to make.  On the
final sentence of that paragraph, the subject ("This") is unclear.


From nobody Thu Apr  6 20:26:55 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B897127058; Thu,  6 Apr 2017 20:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=microsoft.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 5iMFajAQ5Eqq; Thu,  6 Apr 2017 20:26:46 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0103.outbound.protection.outlook.com [104.47.34.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0341F129446; Thu,  6 Apr 2017 20:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GLFhJr/BFrNmaCDelZ1GM0u4CsbiBwY46ojzAcJXllU=; b=LQHj8c8Q/v7QbXLXxBdYOStPBzkkYYWAry5MWReG/2Dot0eD4cc/JASXi/VtHDBXdEpv/Vmc38rV7haMYbnMksU+M/vw6Tc2Z5vY21rpZO6IFNmYQ7aLYx8v3/YVdLQTLy2IPzxQr6TnPUlufAHdMU1eJm2xCpRvCzf5g/DkV2U=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2121.namprd03.prod.outlook.com (10.164.2.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Fri, 7 Apr 2017 03:26:44 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1019.019; Fri, 7 Apr 2017 03:26:44 +0000
From: Orit Levin <oritl@microsoft.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJA==
Date: Fri, 7 Apr 2017 03:26:44 +0000
Message-ID: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [73.157.101.212]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2121; 7:C1QK1mUv/ryjQAGMCyaaNd1PxAKsnpV/3x7xPYPH9XTcf5jQM5rWPb60DBT/QQ2IxYuQSBPkGMOdIqLppRytbOqbRoHi3/1muyQvt3Pditsl41HmkYKwrMlHWmD67oQGzjSFYQwG9SZpRyfCeUJeANx8ccXK4XqcYa5RIcrZurEINQJ3ukQPvFI2hEaEB4fIy1bkOrO9fq0Fi5lz+V8ni6FmsLbPNOcZRLikD+LlojAjuM94L+Ua/I284kf+TyT/1sMjRamLCEjCPIIjMNZl6jXscM1WEHEawztq9K4PxDVq0D2wMBVU+IFX1u63C7XoNh6ZhTsvt0eVEgAo0jzKwrgVTn2tznsBjqmSp7DKJlE=
x-ms-office365-filtering-correlation-id: 3cf57564-a829-4d97-c9ac-08d47d65ea6a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CY1PR0301MB2121; 
x-microsoft-antispam-prvs: <CY1PR0301MB21210C1857228026075CF4F0AD0C0@CY1PR0301MB2121.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(6072148); SRVR:CY1PR0301MB2121; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2121; 
x-forefront-prvs: 0270ED2845
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39840400002)(39400400002)(39860400002)(39850400002)(377424004)(2351001)(66066001)(8990500004)(5660300001)(53936002)(6506006)(38730400002)(110136004)(10090500001)(5005710100001)(77096006)(99286003)(5640700003)(6306002)(9686003)(7736002)(6436002)(2906002)(74316002)(55016002)(305945005)(10290500002)(2501003)(33656002)(230783001)(4326008)(3660700001)(102836003)(6916009)(3846002)(6116002)(7696004)(81166006)(50986999)(2900100001)(8936002)(54356999)(189998001)(8676002)(86362001)(25786009)(3280700002)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2121; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2017 03:26:44.1930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2121
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zHsO0R8V-161Q_mLcWMJLpmmmNw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 03:26:48 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-isis-mi-bis-02
Reviewer: Orit Levin
Review Date: 2017-04-06
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-13

Summary: This draft is "ready with issues" for publication.

Major issues: None.

Minor issues:

1. Add text explaining the reason (or reasons) for replacing the original R=
FC 6822 from 2012.=20
Reason: It is a "bis" draft and there is no mention about it in the text.
2. In Abstract, state clearly that this standard introduces the support for=
 instances vs. other already existing concepts also listed in the Abstract =
(i.e., circuits, adjacencies,  topologies, etc.).
Reason: The wording is not clear about what is the new feature vs. what are=
 the new benefits vs. what was the original baseline
3. Throughout the document, use "standard instance" instead of "IID =3D 0" =
or "IID #0".
Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are used =
interchangeably throughout the document. It seems that they all refer to th=
e same thing - the implementation of the original protocol without the conc=
ept of instances. Please, correct me if I am wrong.
4. In section 2 par 3, change "support" and "operates" to "MUST support" to=
 use requirements language.
5. In section 2 par 2, change "may" to either "can" or "MAY" to clarify the=
 intent.
6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the w=
ire. Explain the concept of the "standard interface" (see previous comment)=
.
Reason: It seems to me that IID #0 MUST never be used on the wire. Please, =
correct me if I am wrong.
7. In section 2.1, rephrase "marks ... by including" to "MUST include" to u=
se requirements language.
8. In section 2.4.1 par 2 second sentence, the sentence starting with "Howe=
ver" needs to be rewritten using standards language to explain its intent.=
=20
9. In section 2.5, replace "exists" with "MUST be performed".
10. In section 2.5.1, replace "only operates" with "MUST only be performed"=
.
11. In section 2.5.2, replace "This requires" with "It is REQUIRED".
12. In section 2.5.2 third sentence, after "inconsistent" insert "due to th=
eir configuration". Please, correct me if I am wrong.
13. In section 7 Security Considerations, discuss possible additional secur=
ity considerations (or the lack of them) related to the introduction of "in=
stances".
Reason: Beyond the normal IETF procedure, this is especially important beca=
use "multiple instances allow isolation of resources..." Can this isolation=
, if observed or interfered, be damaging beyond the previous "standard inte=
rface" situation.

Nits/editorial comments:
1. Compare (Diff) the current draft with the published RFC 6822. You will f=
ind that many of the editorial corrections got lost in the bis version. Omi=
tted corrections throughout the document include "instance-specific", " top=
ology (or topologies)", "Type-Length-Value" and others.
2. In Introduction par 4, either change the two "may" to capitals or replac=
e with "can" to clarify the intent.
3. In Introduction par 5, add references to where in the document the two m=
ethods are described. Also, consider changing "defined" to "described".
4. In Introduction par 7, move the last paragraph before listing the exampl=
es and adjust the text accordingly, for clarity.
5. In section 2.3, replace "normal" with "usual".
6. In section 2.6.1 first sentence, replace "not to cause" to "to avoid".


From nobody Thu Apr  6 21:53:24 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6F1E127B73 for <ietf@ietfa.amsl.com>; Thu,  6 Apr 2017 21:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, 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 fbjWN_qna2BP for <ietf@ietfa.amsl.com>; Thu,  6 Apr 2017 21:53:19 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (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 8395512702E for <ietf@ietf.org>; Thu,  6 Apr 2017 21:53:19 -0700 (PDT)
Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v374jZEH075346 for <ietf@ietf.org>; Fri, 7 Apr 2017 00:53:17 -0400
Received: from e17.ny.us.ibm.com (e17.ny.us.ibm.com [129.33.205.207]) by mx0a-001b2d01.pphosted.com with ESMTP id 29p23w59me-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 07 Apr 2017 00:53:16 -0400
Received: from localhost by e17.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 7 Apr 2017 00:53:15 -0400
Received: from b01cxnp23034.gho.pok.ibm.com (9.57.198.29) by e17.ny.us.ibm.com (146.89.104.204) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 7 Apr 2017 00:53:14 -0400
Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v374rDu944761134 for <ietf@ietf.org>; Fri, 7 Apr 2017 04:53:13 GMT
Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 95A3412403D for <ietf@ietf.org>; Fri,  7 Apr 2017 00:53:08 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTPS id 62A1B124051 for <ietf@ietf.org>; Fri,  7 Apr 2017 00:53:08 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v374rCFH024878 for <ietf@ietf.org>; Fri, 7 Apr 2017 00:53:12 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v374rCMH024861 for ietf@ietf.org; Fri, 7 Apr 2017 00:53:12 -0400
From: narten@us.ibm.com
Date: Fri, 07 Apr 2017 00:53:11 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17040704-0040-0000-0000-0000030AD3CE
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006891; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000208; SDB=6.00844110; UDB=6.00416051; IPR=6.00622407;  BA=6.00005274; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014944; XFM=3.00000013; UTC=2017-04-07 04:53:15
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17040704-0041-0000-0000-000006FED7F4
Message-Id: <201704070453.v374rCMH024861@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-07_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704070042
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fBSCxSp4OiZgAOuE_HFuXUYpWf4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 04:53:23 -0000

Total of 100 messages in the last 7 days.
 
script run at: Fri Apr  7 00:53:11 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.00% |    7 |  6.44% |    72174 | brian.e.carpenter@gmail.com
  6.00% |    6 |  6.85% |    76661 | robert@raszuk.net
  2.00% |    2 |  8.76% |    98129 | zack@cloudbakers.net
  4.00% |    4 |  6.41% |    71795 | suresh.krishnan@ericsson.com
  5.00% |    5 |  5.07% |    56745 | jordi.palet@consulintel.es
  4.00% |    4 |  5.61% |    62825 | martin.thomson@gmail.com
  4.00% |    4 |  3.90% |    43664 | lear@cisco.com
  4.00% |    4 |  3.36% |    37599 | mstjohns@comcast.net
  4.00% |    4 |  3.06% |    34303 | nico@cryptonector.com
  4.00% |    4 |  2.53% |    28305 | rsk@gsp.org
  3.00% |    3 |  2.00% |    22412 | cabo@tzi.org
  3.00% |    3 |  1.89% |    21123 | jared@puck.nether.net
  2.00% |    2 |  2.86% |    31980 | daedulus@btconnect.com
  1.00% |    1 |  3.77% |    42211 | laurent.ciavaglia@nokia-bell-labs.com
  2.00% |    2 |  2.12% |    23760 | melinda.shore@gmail.com
  2.00% |    2 |  1.77% |    19870 | bob.hinden@gmail.com
  2.00% |    2 |  1.63% |    18205 | christer.holmberg@ericsson.com
  2.00% |    2 |  1.53% |    17136 | stewart.bryant@gmail.com
  2.00% |    2 |  1.49% |    16714 | mcr+ietf@sandelman.ca
  2.00% |    2 |  1.35% |    15110 | rsalz@akamai.com
  2.00% |    2 |  1.22% |    13663 | rjsparks@nostrum.com
  2.00% |    2 |  0.93% |    10471 | acmorton@att.com
  1.00% |    1 |  1.50% |    16765 | ldaigle@thinkingcat.com
  1.00% |    1 |  1.47% |    16514 | sabine.randriamasy@nokia-bell-labs.com
  1.00% |    1 |  1.17% |    13121 | oritl@microsoft.com
  1.00% |    1 |  1.13% |    12677 | ynir.ietf@gmail.com
  1.00% |    1 |  1.07% |    11965 | spencerdawkins.ietf@gmail.com
  1.00% |    1 |  1.06% |    11825 | narten@us.ibm.com
  1.00% |    1 |  1.02% |    11470 | agmalis@gmail.com
  1.00% |    1 |  0.98% |    11025 | sarikaya2012@gmail.com
  1.00% |    1 |  0.95% |    10624 | jhw@google.com
  1.00% |    1 |  0.94% |    10522 | bdamm@ssni.com
  1.00% |    1 |  0.93% |    10405 | rwfranks@acm.org
  1.00% |    1 |  0.87% |     9729 | stephen.farrell@cs.tcd.ie
  1.00% |    1 |  0.87% |     9707 | huitema@huitema.net
  1.00% |    1 |  0.85% |     9487 | phill@hallambaker.com
  1.00% |    1 |  0.80% |     8906 | aallen@blackberry.com
  1.00% |    1 |  0.77% |     8568 | sbanks@encrypted.net
  1.00% |    1 |  0.74% |     8339 | andy@hxr.us
  1.00% |    1 |  0.72% |     8050 | paul@nohats.ca
  1.00% |    1 |  0.71% |     7950 | adrian@olddog.co.uk
  1.00% |    1 |  0.67% |     7470 | fgont@si6networks.com
  1.00% |    1 |  0.65% |     7276 | alcaraz@lcc.uma.es
  1.00% |    1 |  0.65% |     7269 | mrex@sap.com
  1.00% |    1 |  0.64% |     7163 | iad@ietf.org
  1.00% |    1 |  0.59% |     6659 | finlayson@live555.com
  1.00% |    1 |  0.59% |     6630 | chair@ietf.org
  1.00% |    1 |  0.59% |     6572 | johnl@taugh.com
  1.00% |    1 |  0.55% |     6112 | randy@psg.com
  1.00% |    1 |  0.53% |     5967 | dromasca@gmail.com
  1.00% |    1 |  0.52% |     5873 | presnick@qti.qualcomm.com
  1.00% |    1 |  0.50% |     5574 | jouni.nospam@gmail.com
  1.00% |    1 |  0.44% |     4876 | gunter@vandevelde.cc
--------+------+--------+----------+------------------------
100.00% |  100 |100.00% |  1119945 | Total


From nobody Fri Apr  7 06:58:49 2017
Return-Path: <prvs=12704cc6ce=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2368129465 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 06:58: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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FodWJARxTHRE for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 06:58:45 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CD8E1294CF for <ietf@ietf.org>; Fri,  7 Apr 2017 06:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491573515; x=1492178315; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=1xqaxzmMwsM/tjFhdVHeVZAIq QEUK4jyH6snZZxY6EE=; b=FC0EDSik4ZXUCa2NqHaS0iWx/bT7ldYFG9KCu+Rdj MmtB/fc7PTh5AZr9Pa4xaV+WWxZ+rWzLnOWGzFiJHX7Imz1Sskn3zi1RV8kx+Nze dzfTPmYjmLex6Y0Sm+3vYyf7FXuWppo6ovBvHmvUo/3iWUsT/rLB53zY39JfMGY5 IU=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=OebXxLKWEH6LGC9mKdEOhuQiY6hXIu0MmWrfsGyW0hEclNtnYpENzYP2/hrI hLc4rS6Isvyz+TB0a+b5+kIRnopKKOdA+i7h84JuPRKy36W4SjlYg9OdY O1lcJDlNFxsDBCBVllg85H5VId0K3Er84PXMkj+ASfkS7k1O+dgLfc=;
X-MDAV-Processed: mail.consulintel.es, Fri, 07 Apr 2017 15:58:35 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 07 Apr 2017 15:58:34 +0200
Received: from [84.88.5.118] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005404500.msg for <ietf@ietf.org>; Fri, 07 Apr 2017 15:58:34 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170407:md50005404500::Av5dJFBxRdI8VJUh:00000Eek
X-Return-Path: prvs=12704cc6ce=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Fri, 07 Apr 2017 15:58:30 +0200
Subject: Re: CRITIS 2017 Call for Papers
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <alcaraz@lcc.uma.es>
CC: IETF Discussion <ietf@ietf.org>
Message-ID: <FB10776D-505F-4354-8CE6-14D17EE0900B@consulintel.es>
Thread-Topic: CRITIS 2017 Call for Papers
References: <4be04fc27b54ad2e33b74571f7ae7ad0@lcc.uma.es>
In-Reply-To: <4be04fc27b54ad2e33b74571f7ae7ad0@lcc.uma.es>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XgJwavgHhGFbIUZo174Z95KnMaA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 13:58:48 -0000

Hi Cristina, all,

Speaking as IETF sergeant-at-arms.

This is a reminder that announcements of conferences, events, etc., aren=E2=
=80=99t allowed in this list.

See: https://tools.ietf.org/html/rfc3005

If anyone insist in doing so, your posting rights may be restricted.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Cristina Alcaraz <alcaraz@lcc=
.uma.es>
Responder a: <alcaraz@lcc.uma.es>
Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 23:33
Para: <undisclosed-recipients:;>
Asunto: CRITIS 2017 Call for Papers

    Dear Colleague,
   =20
    we invite you to submit a contribution to CRITIS 2017, the Internationa=
l=20
    Conference on Critical (Information) Infrastructures Security.
   =20
    This year the conference will take place in Lucca, a gorgeous=20
    Renaissance city in Tuscany, 9-11 October 2017.
   =20
    Papers can be submitted via EasyChair; for poster contributions,=20
    submission can be limited to an extended abstract. All accepted=20
    contributions will be included in full length in the pre-proceedings=20
    that will appear at the time of the conference; accepted papers are=20
    planned to be published in the LNCS Springer-Verlag series.
   =20
    Special attention will be devoted to young talents. To this purpose, a=
=20
    price (YCA: Young Critis Award) will be awarded to the best contributio=
n=20
    presented by a young author.
   =20
    On 12-13 October, the conference will be followed by two satellite=20
    workshops on Energy and Water.
   =20
    For further details, please visit our website www.critis2017.org . We=
=20
    would appreciate you advertise the conference by the attached leaflet.
   =20
    The organizers:
   =20
    Cristina Alcaraz, Hypatia Nassopoulos,
    Antonio Scala, Gregorio D=E2=80=99Agostino,
    Grigore Havarneanu
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Fri Apr  7 10:35:01 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA3C129435 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 10:34:59 -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 RRkuqSp2_aRz for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 10:34:54 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::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 6BD4C129557 for <ietf@ietf.org>; Fri,  7 Apr 2017 10:34:52 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id 81so72699560pgh.2 for <ietf@ietf.org>; Fri, 07 Apr 2017 10:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1NSr5CSQGsQ6LpHuLnhpkPNJlZaYcbXyg/g6vNpfsuk=; b=E2pr7zRwTTbjKc43ltj68TdIMa9n6Tg52jG8+pMNEpYlRxs7zHAGgqXxfT6JrnkfJu AJUys6+9GFidTW4bjHWUClmyk87GHveQ1GTvkj7ebGik7TuR5o8Uxbm2dRXVhCjxFQGS 8MMyFFFh7FqdbJMdjWELCQRAHrPxCS1qBuoQvsKF19TP72CzPQwtElatTdDJQ2tS2Sst Eu+LOLNqqptkwR/Z0SDhXba+WDmgH8Tc/kqtzzUiexo9oVMDAWiA8GWhY3R+lBbNUiK1 6vP2n70HPDT0m9kxcvNstPZg8rJivr6lq04xdsTvIKa3Q35XZcGpEi5jrw9MQhOeYmCE yZ4A==
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=1NSr5CSQGsQ6LpHuLnhpkPNJlZaYcbXyg/g6vNpfsuk=; b=nJrPGeQhUuxkRylLvAxdAR9xRwNGeqmxlA1OXrHeVEF7zNiqGdPZq2MIeazhM4IxLg pUKoXDxeFOu2ItRMmy+YPPSMJBQrATbOVsk6NU8ciyFAvQJoGut10RWOZsDzjiyYb4/U UroXWWyywqVu4154W6dNyYiB4oh81ZL5PnxZhxW704H1vx6FLrh/EETN+v2ycpQniCt2 O4VKUiuZToKwuR8lmHXHY17lQE+DyHne3egefWtgo9k2Q9UdueqjpVK0qgXtBa1dpOCu RdlytHeHbZ0GjLj+W6i33mL0S2uyEQ3HWyIupOxcGhxidojrbK7Q4Vs0UFkEyMM5s8yI SCGQ==
X-Gm-Message-State: AFeK/H0BSICOzSQH4T+sSLNm6D8o/J/gdfkGFyR0PvEwJKzHOcN/RRKRb6nyWVXPn+kg6aqkmOeqlRlb8DDN0Q==
X-Received: by 10.98.105.134 with SMTP id e128mr41098932pfc.19.1491586491146;  Fri, 07 Apr 2017 10:34:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.128.141 with HTTP; Fri, 7 Apr 2017 10:34:10 -0700 (PDT)
In-Reply-To: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 7 Apr 2017 13:34:10 -0400
Message-ID: <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s9XsYWE_HI-YTtJ2z4pdutskeqE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 17:35:00 -0000

Hello Martin,

Thanks for your review.  It seems that you have read version 8 or
earlier and not the current version, 9, from some of your suggestions
that have been corrected already.  Your review also reads to me that
additional context setting may help, but please note that some context
setting was improved in version 9.  We re-arranged some of the
sections per IESG review recommendations in the latest version as
well.

Perhaps you have additional language suggestions for context setting?

The abstract states:

   Increased use of encryption impacts operations for security and
   network management causing a shift in how these functions are
   performed.  In some cases, new methods to both monitor and protect
   data will evolve.  In other cases, the ability to monitor and
   troubleshoot could be eliminated.  This draft includes a collection
   of current security and network management functions that may be
   impacted by the shift to increased use of encryption.  This draft
   does not attempt to solve these problems, but rather document the
   current state to assist in the development of alternate options to
   achieve the intended purpose of the documented practices.

which is repeated again in the introduction, but slightly reworded.
The introduction also includes statements on the existing publications
related to encryption and I read them as not having any bias, but
rather supporting the existing documents that also had consensus.

A couple of comments and one question inline.

On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> Draft: draft-mm-wg-effect-encrypt-09
> Date: 2017-04-07
>
> Overall
>
> This document is unfocused and unclear in its intent.  It is filled with
> unsubstantiated claims, misleading statements, bias, and implied recommendations
> for bad practices.  I would oppose its publication in the current form.
> Furthermore, I don't believe that small scale or editorial changes would be
> sufficient to correct these problems.
>
>
> Aside from weakening its utility and/or arguments, the lack of focus will allow
> this document to be abused in various ways.  For instance, it might imply IETF
> endorsement of the practices described in the document.  Given that the IETF has
> published positions that in some cases reject these practices, this document
> needs to be very precise with its claims.  In its current form, it is not nearly
> careful enough.
>
> If this document is going to be published as an RFC, then it needs to be very
> clear about its intent and its position - or lack thereof - toward these
> practices.  It might be possible to say that these practices were employed in
> networks in the past and that encryption is reducing the viability of those
> practices.  A value-neutral statement like that might be acceptable as long as
> it were framed carefully.
>
> What is problematic is the implicit argument that is presented.  This document
> could easily be construed as the IETF legitimizing these practices.  This
> includes things on which the IETF has published statements (see for example RFC
> 2804).

See the abstract and introduction and summary.

>
> This steps firmly into to sticky mess that is the politics of encryption policy.
> If the IETF is going to make a political statement with this document, then that
> statement needs to be a lot better than this.
>
> Furthermore, any statement needs to be consistent with previous statements,
> where in this case that primarily means RFC 7258.  Right now it reads as an
> attempt to dilute RFC 7258.

Not at all.

>
> If this document were more clearly formulated as an even-handed treatment of
> what happens today - without judgment - then it could be useful.  Here the model
> of RFC 7754 is a good one.  It describes the different facets of a use case,
> then the different practices that might be employed to achieve that goal.  For
> each practice the pros, cons, and technical limitations are covered with an eye
> to all involved parties.
>
>
> The Real Purpose of this Document
>
> I think that this is the real question that this document wants to ask is:
>
>    In a world where we are forced to defend against pervasive monitoring by
>    motivated and malicious actors, can we find a role for less pervasive
>    monitoring by well-intentioned entities?
>
> There is an interesting discussion to be had here, but I'm convinced after my
> review that this document is the wrong vehicle for that discussion.  I'm also
> inclined to suggest that this is the wrong question to ask in the first place.
>
> To the extent that we have the tools necessary to protect against pervasive
> monitoring, we have to accept that more-legitimate uses of monitoring are
> collateral.  Mostly, that's just a function of the limitations of the imperfect
> tools we have.
>
> The value in this document is in the rather comprehensive collection of use
> cases.  Sure, some we might not attribute much weight to, like wiretapping.
> Others are frankly frightening and not just in the Orwellian sense.
>
> The problems that are implied by the current practices of network operators is a
> large vein of unexplored work for the community.  Spending effort on finding
> better solutions to legitimate problems is worthwhile.
>
> In other words, the right question might be:
>
>    For each of these practices that we see today, are the use cases that
>    motivate them legitimate and how might be implement alternative techniques
>    that properly respect privacy and security?
>
>
> Two- and Three- Party Interactions
>
> A great many sections of the document are unclear about the relationships
> between different actors.  It seems like many of the activities describe, which
> are presented here as being beneficial, are performed by a third party without
> the consent or involvement of the two communicating peers.  After all, those are
> the cases where encryption most often interferes.
>
> The assertion that some benefit is accrued to communicating peers as a result of
> these actions is the constant subject of the text.  I observe that in most of
> the cases listed in this document, the benefit is accrued primarily to the third
> party.
>
> Clarity around the arguments that the document makes with respect to benefits to
> each of the involved parties is sorely lacking.
>
> In addition to this, where benefits truly do accrue to communicating peers,
> technical options that don't rely on privacy-invasive techniques are routinely
> dismissed in an offhand fashion.  In this way, any moral imprimatur attributed
> to the use case is used to justify the privacy-invasive method.
>
>
> Document Structure
>
> This document is very hard to read (and review).  Probably my biggest complaint
> is that the sections are haphazardly organized.  They contain a mixture of use
> cases (what does SP X want to do) and techniques (how do they do these things).
> Material is duplicated between sections.  Sections cover 10 different use cases
> while talking about techniques, then other sections talk about different
> techniques whiles talking about a scenario.  This leads to a lot of repetition.
>
> There are three axes that this document contemplates:
>
>  - the techniques that are currently used in networks
>  - the use cases that motivate these techniques
>  - the deployment scenarios in which these use cases manifest
>
> It would appear that the document attemps to start from the deployment
> scenarios.  However, this causes use cases and techniques to be mixed.
> Judicious use of cross-referencing might have made this arrangement tractable,
> but there are virtually no cross references.
>
>
> Section 1
>
> I find the introduction of this document difficult to parse.  I think that what
> it wants to say is pretty straightforward, but it manages this in quite an
> obtuse way.  Here's what I think that it is trying to say:
>
> 1. The IETF (and the larger community) has reacted to revelations of pervasive
>    monitoring by increasing the use of encryption.
> 2. That has been somewhat successful.
> 3. More encryption has an impact on some practices that network operators have
>    become accustomed to employing.
>
> Expressed in this way, you can see how you could make a value-neutral
> statement.
>
> On the first, you can definitely make an argument based on the documents that
> the IETF have published.  However, it is a mistake here in assuming that the
> IETF - or the revelations of global-scale surveillance - is directly responsible
> for the uptick in adoption of cryptographic protection for Internet traffic.
> This is something that the community as a whole has been working towards for
> many years; these trends predate the actions this draft focuses on.  This is
> particularly true for the hosted provider cases in Section 3, where business
> motivations for protection are far stronger than any concerns over government
> surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I don't
> have to write a statement that will be labelled as having IETF consensus.
>
> The immediate focus on opportunistic security is highly misleading, especially
> in the web case.  The amount of opportunistically secured web traffic is
> miniscule by global standards.  Since Firefox is the only browser to support OS
> for the web, so adjust the following by market share: <https://mzl.la/2oc46ch>.
>
> I understand that mail is more often opportunistically secured, and you will
> hear the virtues of OS sung from the rooftops, but all evidence suggests that
> this is just a transitory state.  Instant messaging is closer to the web case,
> with the trend toward strong protections that include authentication.  Of
> course, I don't believe that mail or instant messaging represent any significant
> traffic volume, so you need to be very careful about the nature of the claims
> that are being made.  It has to be that the volume of mail has to be a rounding
> error when it comes to capacity planning for networks.
>
> On the second point, when making claims about prevalence of encryption, I would
> advise caution when citing statistics.  Here's the graph for the Mozilla figures
> that I think are being cited <https://mzl.la/2obZjrb>. Here's a different graph
> with a different number <https://mzl.la/2oc263J>.  This highlights the point
> that statistics need to be carefully cited, because bare claims are difficult to
> assess.  Methodology matters when it comes to these sorts of claims - are we
> talking proportions of packets, requests, flows, or something else?
> Furthermore, the citations in the document are made more difficult to assess by
> being measured at very different times (where the two I cite here were made at
> roughly the same point in time).

For the Mozilla statistics, Richard Barnes had reviewed the text after
providing the statistic as he wanted to make sure it was stated
clearly raising the same concerns you do about statistics.  Do you
have further text suggestions to clarify this statistic?

Thank you,
Kathleen

>
> The statistics do support the notion that there is a significant amount of
> encryption in use, but it would appear that the claim is that the amount of
> encryption is *increasing*.  This is not an extraordinary claim, but no evidence
> is offered in support of the claim.  It isn't a certain thing either.  From the
> statistics that I have access to, there was a definite uptick in October of
> 2015, but the rate appears to be stable since then.
>
> It appears that the remainder of the document is intended to address the third
> of my points in some detail.  That's a good structure in theory, but see above.
>
> I don't think that the "service provider" taxonomy works for this document.
> Based solely on the structure of the document, the only service provider that
> this document concerns itself with is the one who forwards the packets.  That
> application service providers are involved as one of the endpoints is relevant
> in some cases, but not all.  For that reason, I prefer "network operator" and to
> use specific terms like "mail host" or "web server" as appropriate to the
> context.
>
>
> Section 2 (top section)
>
> I like that the attacks on SMTP by network operators is highlighted here.
>
> There's an implicit argument here that runs counter to established IETF
> consensus.
>
>    Some methods used by service providers are impacted by the use of encryption
>    where middle boxes were in use to perform functions that range from load
>    balancing techniques to monitoring for attacks or enabling "lawful
>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>
> This fails to remain neutral.  This implicitly makes a value-judgment about
> relative morality/acceptability/value of certain practices.  What is
> particularly insidious about this particular form is that it invites
> interpretation that is subjectively coloured.  For instance, as a non-EU and
> non-US citizen, I might consider the use of the particular lawful intercept
> techniques offensive; thus I might interpret this as a spectrum between
> inoffensive to offensive.  An employee of the US government might view this
> somewhat differently and interpret this as a scale between low-value to
> high-value.  I'm guessing here, but this is really just to highlight my point
> about care.
>
> A more serious concern is this statement:
>
>    The loss of access to these fields may prompt undesirable security practices
>    in order to gain access to the fields in unencrypted data flows.
>
> I've read this argument before (see https://queue.acm.org/detail.cfm?id=2508864
> for the long form), and it might even have an element of truth to it.  However,
> it's not a statement that I personally attribute any real credibility to, and
> nor do I think that it needs to be credited with any amount of seriousness.  I
> certainly disagree with the IETF making any such statement.  It says that we are
> collectively willing to bow in response to (anticipated) threats of violence.
>
> Section 2.1
>
> This is one of the few sections that talk about what it means to operate a
> service as opposed to operate a network.
>
> Overall, this section doesn't work particularly well.  The distinction between
> integrated and standalone load balancing is an interesting division, but it
> doesn't leverage this distinction well.  What causes a standalone load-balancer
> to be necessary?  Is this something a network operator uses?  I see text on NFV
> later, but it's far removed from the original text and it seems aspirational
> rather than concrete.  On the other hand, many of the concerns in this document
> simply don't apply to an integrated load balancer.
>
> The amount of text on QUIC here is surprising.  Given how much of QUIC is
> changing right now, we shouldn't publish a document that attempts to make claims
> about what QUIC is or how it is operated.  This attempts to dive into the
> details of QUIC connection migration in a way that presumes much about the
> outcome of issues that the QUIC working group is still struggling with.
>
> I would strongly recommend removing QUIC-specific language from this section and
> the document as a whole.  We have an operational document in the QUIC working
> group that would be a good venue to discuss some of these concerns.
>
> Is this an oblique reference to (the much-loved) RFC 7974?
>
>    Current protocols, such as TCP, allow the development of stateless integrated
>    load balancers by availing such load balancers of additional plain text
>    information in client-to-server packets.
>
> Otherwise, I don't know what it means.
>
> BTW, I like this parenthetical:
>
>    (That said, care must be exercised to make sure that the information encoded
>    by the endpoints is not sufficient to identify unique flows and facilitate
>    Persistent Surveillance attack vector.)
>
> I'm going to take this to the QUIC working group, because QUIC certainly doesn't
> meet that bar right now.  It fully facilitates Persistent Surveillance in its
> current form (proper noun?  I haven't really seen that term before, even though
> it draws a neat parallel with Pervasive Surveillance).
>
> Editorial:
> * "pop" is a term of art that needs explanation.
> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - the
>   possessive form for the inanimate.
> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>
> Section 2.2
>
> I think that this sums the situation up reasonably well.  It fails the
> value-neutral test in a few ways though.  As I understand the situation,
> surveying operates at many levels.  For accurate planning, models of endpoint
> behaviour are used to determine things like whether loss or congestion is
> affecting throughput.  Really good models require knowledge of what users are
> attempting to do and the applications they are using (as mentioned, things like
> browser version matter in these models).  For instance, it isn't enough to
> understand that the user is trying to receive 720p video, you also have to know
> that a 4k stream for the same content is available.
>
> The degree to which these models are privacy-invasive is not even acknowledged.
>
> Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect that
> subtlety to be lost on many readers though.
>
> Section 2.3.1
>
> I find this sad, even if I can recognize the truth of it:
>
>    A monitoring system could easily identify a specific browser,
>    and by correlating other information, identify a specific user.
>
> As a browser vendor, we don't consider this to be a feature, it's a bug.
>
> Section 2.3.2.1
>
> This is a strange section under which to put caching.  Caching is a use case
> akin to compression.  I don't see it as belonging to the class of things that
> rely on DPI.  You just intermediate the cleartext HTTP in the way that RFC 7230
> recognizes.  Note that RFC 7230 explicitly does not endorse the practice of
> transparent proxying for a range of reasons, not the least of which is the
> complete lack of transparency (yep).
>
> Section 2.3.2.2
>
> Again, it's strange to see differential treatment under DPI.  I was fairly sure
> that fingerprinting was used here as well.
>
> Section 2.4
>
> This section doesn't even attempt to recognize that applications are much better
> now at scaling content to suit the device on which that content is intended to
> be consumed.  It should.
>
> This section should not represent compression as an unmitigated good.  I'm told
> that significant damage can be done to video streams by "well-intentioned"
> compression middleboxes.
>
> Yet again I see a call back to the implicit threat of violence in "they will
> adopt undesirable security practices".  Statements in that form have no place in
> IETF RFCs.
>
> Section 2.5
>
> This mentions RFC 7754 then blithely ignores its primary conclusion. Generally,
> The treatment in RFC 7754 of this subject is more even-handed.
>
> The use of particular examples (betting, gambling, dating) shows cultural bias.
>
> Jargon warning: "core network", "the mobile network" ("the"?)
>
> Section 2.5.2
>
>    This type of granular filtering could occur at the endpoint, however the
>    ability to efficiently provide this as a service without new efficient
>    management solutions for end point solutions impacts providers.
>
> The initial premise here (up to the first comma) is the conclusion of RFC 7754.
> I disagree with the conclusion, and I suspect so does RFC 7754.  In scenarios
> where this matters, endpoints are routinely managed centrally.  The range of
> options for this sort of management are plentiful and diverse.
>
> Section 2.5.3
>
> This describes a captive portal, which in the case where the service provider
> has a relationship with their customers, seems like a poor solution.  See the
> CAPPORT working group for ways in which people are actually working on a
> solution to this problem.
>
> Section 2.6
>
> The capitalization of section headings is inconsistent here (and throughout).
>
> Section 2.6.1
>
> Isn't this a duplicate of Section 2.1?
>
> Section 2.6.2
>
> I can't parse this statement:
>
>    Approved access to a network is a prerequisite to requests for Internet
>    traffic - hence network access, including any authentication and
>    authorization, is not impacted by encryption.
>
> And then we get into zero rating, which is a hot-button topic.  No
> acknowledgment given to the sensitivities on the subject, or even a superficial
> exploration of the technical options that are available.
>
> This text references a non-existent Appendix.
>
> Section 2.6.5
>
> This paragraph is strange.  It starts by describing what appears to be use cases
> (are those scare quotes?).  It finishes by implying that these are attacks on
> privacy (which they are).
>
> What is "Non-Customer Proprietary Network Information"?  I hope that this isn't
> an attempt to somehow privilege the information so that it seems less than
> privacy-invasive.
>
> Section 2.7
>
> This is one of the areas that is most legitimately affected by increased
> adoption of encryption.  I have no doubt that having detailed information about
> the application and its use makes the process of troubleshooting easier.
>
> This is the first mention in the document of network-based optimization.  Was
> the section describing that cut from an earlier draft?
>
> The use of websockets as a primary example is an odd one.  It's just not that
> common.  For reference, we see >20% failure rates on encrypted websockets and
>>50% failures in the clear; no one in their right mind would rely on websockets.
> If the point is that HTTP is carrying more traffic (see
> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying just that
> would be more effective.
>
> Section 3
>
> It would help if "hosted environments" was defined before diving in.
>
> Section 3.1
>
> The paragraph on DLP is ironically amusing.  Encryption exists to prevent
> private information leakage, but the assertion here is that encryption is
> hampering DLP attempts.
>
> It's true that protection of intellectual property is an important business
> goal, but this handling suggests an architecture that I'm fairly sure is counter
> to established wisdom (see "SSL added and removed here :-)":
> https://www.washingtonpost.com/rf/image_404h/2010-2019/WashingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg).
> Worse, this casually dismisses a model that is actually more likely to work.
> Malware encrypts too (https://arxiv.org/abs/1607.01639).
>
> Section 3.1.1
>
> Who is the customer here?
>
> Why does the hosting provider need to monitor access?  They have the ability to
> limit accesses, but this is suggesting that what happens within the envelope of
> what they permit is important for them to know.  I'd be surprised if you could
> show that this is true.  Hosting providers - in my experience - value their
> ongoing business and would not jeapardize it by snooping on their customers.
> It's different if the customer opts in to a security service, but that
> demonstrates a cooperative situation, where the rest of this document is largely
> concerned with adversarial uses of encryption.
>
> Section 3.1.2
>
> This is another example where the organization of the document could
> be improved.
>
> Again with the "SSL added and removed here :-)" recommendation.  PCI don't
> permit that for good reason.
>
> Section 3.2.1
>
> I don't believe that monitoring of these types of application require cleartext
> access.  There are two parties involved: the provider of the application and the
> user of it.  The provider has most of the power here and can theoretically
> design the system to allow whatever level of access they require.  To the extent
> that the user needs protection from the application provider, that is a matter
> of negotiation between them.
>
> I don't see how the adversarial three-party situation presented in the rest of
> the document applies in this situation.
>
> Section 3.2.2
>
> No real mention of the effect of encryption here, or is this just saying that
> there is no issue here?
>
> I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of the IETF
> saying things like "PGP may be a front runner" though.
>
> Section 3.3
>
> There's certainly a lot of detail here, but I had a really hard time extracting
> value from this section.  I can't see how data storage is fundamentally
> different to the general case of an application provider.
>
> Section 4.1.1
>
> I appreciate the recognition that endpoint-based techniques work.  The
> implication that this isn't the obvious solution, much less so.
>
> Section 4.1.2
>
> I'm confused about the purpose of this section.  This seems to be talking about
> the sort of network-based methodologies an application provider might employ to
> ensure that their application is working as intended.  Why would the application
> provider not have access to detailed logging and usage metrics?
>
> As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is cited no
> fewer than three times in the same paragraph.  It makes some fairly bold claims
> about its effect on privacy that I don't believe will hold up to analysis.
>
> Section 4.1.3.1
>
> This section correctly identifies the issue as one of shortcomings in logging,
> not increased use of encryption.
>
> I would have stopped there, but the section persists and ultimately references
> RFC 7974, which is widely recognized as a monstrously bad idea (the IESG note is
> fairly clear on this point).
>
> Section 4.1.3.2
>
> "HTTP/2", not "HTTP2".
>
> I don't see how this section belongs in this document.  The 1:1 correlation
> between actions and flows in HTTP was a mistake of the 1980s that we've spent a
> lot of time on correcting (sometimes unsuccessfully, see pipelining).
>
> Section 4.1.3.3
>
> It's not a "service call" it's just a request.
>
> Section 4.2
>
> If the inclusion of a reference to RFC 7457 is to support a claim that TLS is
> attacked, that's sailing far too close to an endorsement of attacks than I am
> comfortable with.  However, I don't believe that any of the listed attacks
> remain viable in modern applications.  What is most often the case is that a
> trust anchor is installed on enterprise users' machines and new certificates are
> minted as needed.  In other words, the host that is accessing the HTTPS site is
> owned by the enterprise and modified so that it can comply with its policies.
>
> When you recommend attack like this (to be clear, I would oppose publication of
> text that does this), you need to acknowledge the downsides.  For example, MitM
> devices routinely break connections, they hide the true security status of
> communications from endpoints and users, they frequently implement weaker
> versions of protocols, they often don't include the same degree of rigor in
> things like certificate validation, and probably many more things that I can't
> casually list off the cuff.
>
> The discussion of caching here warrants a new section.
>
> Section 5.1
>
> s/effect/affect
>
> No complaint here, just an advertisement for technical solutions that aren't
> affected by increases in encryption.  Good, though I'm not sure if the section
> meets the document's criteria for inclusion.
>
> Section 5.3
>
> No cititation for APWG.  Not an IETF working group from what I can see.
>
> There's a presumption here that administrators need to perform these tasks.  Why
> can't endpoints do this?  It would certainly be a whole lot less invasive that
> way.  Take a look at how browsers implement checks for "bad" sites (which
> include phishing sites).  These methods have some fairly significant privacy
> safeguards without compromising on performance.
>
> Section 5.5
>
> See my comment about about endpoint-based methods.
>
> Section 5.6
>
> I believe that the spoofed source address problem is not relevant to this
> document.  It's a fairly well understood problem.  That said, if we could wave a
> magic wand and get BCP 38 deployed, that might be nice.
>
> Section 6.1
>
> As this says, it's fairly well understood that - for HTTP - SNI is used.  The
> point that it is optional is interesting, but doesn't deserve the amount of
> attention this section devotes to it.  The clients that don't include SNI are in
> a diminishing minority.
>
> That said, this doesn't pay any attention to another feature in HTTP/2:
> connection coalescing.
>
> Section 6.2
>
> ALPN will be encrypted in TLS 1.3.
>
> Section 6.3
>
> This reads as a invitation to perform traffic analysis (a statement that I
> oppose).  Note that we have added padding to most recent protocols (HTTP/2 and
> TLS 1.3 in particular) to give endpoints the ability to resist this sort of
> attack.
>
> Note that block ciphers can add ~240 octets of discretionary padding per record.
> That can be pretty effective if you are careful.
>
> Section 7
>
> This section is duplicative of much of the rest of the document.  I realize that
> editing is hard, but see my earlier comments about structure.
>
> It's obvious that this section is about QUIC.  That shows in several ways.  It's
> nice how it doesn't say so out loud, but it leaks through in several confusing
> ways.  See below.
>
> Section 7.1
>
> This section is purportedly about encrypted ACKs, which won't happen until we
> get to QUIC.  But the points regarding proxies (b, c, d) are not prevented by
> encrypted ACKs, they are prevented by encryption more generally.  Point e is
> defeated by integrity protection of ACKs, not confidentiality protection.
>
> I hope that the IETF never publishes draft-dolson-plus-middlebox-benefits; it
> makes claims about the benefits of specific solutions for different use cases
> with the goal of justifying those solutions.  At the same time, it fails to
> recognize the existence of alternative, often superior, solutions for those use
> cases.  In other words, it has many of the same issues as this document.
>
> FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I don't
> know how to close the gap between the privacy assurances I wish it had and the
> privacy weaknesses it has.
>
> The phrase "trusted proxies" is a dangerously misleading phrase.  The concept of
> trust is - particularly in this context - frequently abused.
>
> Sections 7.2 and 7.3
>
> I'd be interested in learning about the justification for these features (again,
> go back to my comment about to whom the benefit accrues, and I'd advise caution
> not to make the trickle-down economics mistake of using second-order effects).
> Personally, I'm not that sad that they are going to be negatively affected.
>
> Section 7.2, Point d seems to be saying something about a multiplexed protocol,
> not one that has an encrypted transport header (see above regarding QUIC).
>
> All these points equally apply to HTTPS, which suggest that encrypted transport
> headers is not the issue (unless by transport we mean HTTP).
>
> Section 7.4
>
> s/GPSR/GPRS/ ?
>
> Section 8
>
> I generally agree with the first statement here, but after having read the
> document, I could take away some very different views on what the "problems at
> hand" actually are.  I suspect that different people will have very different
> takeaways.
>
> The conclusion section of a document is not the right place to start introducing
> new information, particularly information relevant to RFC 2804.
>
> Not sure where this is going:
>
>    Terrorists and criminals have been using encryption for many years.
>
> Because it's disconnected from the remainder of the paragraph.  If you are going
> to invoke the T-word, you had better have a strong argument to make.  On the
> final sentence of that paragraph, the subject ("This") is unclear.
>



-- 

Best regards,
Kathleen


From nobody Fri Apr  7 10:58:54 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F387129552; Fri,  7 Apr 2017 10:58:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Cc: draft-ietf-rtgwg-yang-key-chain.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
Subject: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
Date: Fri, 07 Apr 2017 10:58:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a1on1q5nqc9MloTilT0aBjcEKDQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 17:58:52 -0000

Reviewer: Matthew Miller
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rtgwg-yang-key-chain-17
Reviewer: Matthew A. Miller
Review Date: 2017-04-07
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-13

Summary:

This document is almost ready to be published as a Proposed Standard,
once the issues noted herein are resolved.

Major issues:

NONE

Minor issues:

* Forgive me for my limited knowledge of YANG, but is there a reason
key-strings are only representable as either a YANG string or
hex-string type, and not the YANG binary type?

* This document does not provide much guidance around AES key wrap
other than it can be used and the KEK is provided
out-of-band/-context.
For instance, AES key-wrapped key-strings probably require using
"hexidecimal-string".  Also, assuming I'm reading the model
correctly,
it appears this feature applies to the whole chain, which I think is
worth calling out.

* This document warns against using the "clear-text" algorithm, which
the
reader is lead to understand is for legacy implementation reasons.
However, is there not a similar concern with cryptographically weak
algorithms, such as md5 and (arguably) sha1?

Nits/editorial comments:

* In Section 3.2. "Key Chain Model Features", the word "of" is
missing
between "configuration" and "an" in the phrase "support configuration
an
acceptance tolerance".

Non-nits:

* I note that idnits is calling out some odd spacing issues, but I
think
they are safe to ignore.



From nobody Fri Apr  7 12:18:28 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BD112422F; Fri,  7 Apr 2017 12:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ipVQGICIvi_9; Fri,  7 Apr 2017 12:18:19 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 A690812420B; Fri,  7 Apr 2017 12:18:14 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id f133so53752382qke.2; Fri, 07 Apr 2017 12:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=vsBGIn124h9q4mOjT7bysbXceVf9QPowHFCBk970X68=; b=LDVuxi98H07lB3jX/jV8Up9w32w6/mHFstb8VkacnOMoqXt+B5LkOODgH4t4G6v+02 FMmggp9qNtj2/x1M0GnXFV5SI+ykN2Y5o/OfHrbHEShOoDFEWCBdtRrYwjrQqdJG2wh/ 3ztb/ACQBQTCCPiSLm4FNMrvneidTPY8UniB0vYeCRNWxONe/6mon7E2IUrES75OA0hI WrjWGVlayomTZVQjF+OrcbPT/e7gUAszCHs2uDd5z5IS7M3jtQj3q4uXGAbC2UZe898k WFsdKYrMJkLXFhnVl4Kxe9XuvIr3+uzCV38Ob8ZN5y9u+SWuryIr0KRnUpKmhygBdTqB AKAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=vsBGIn124h9q4mOjT7bysbXceVf9QPowHFCBk970X68=; b=gPLvaPj0uzaCpnCVlwt6I/yN/ApTcaoSEUUF/k4cXkIpaIuaBJmoGBzAJU0Uso1Qda 6dYhjb/fehQKKFdyhoH3CzafWyLqx5vVpTtrT4WsR5GZXlTKAUd1Q35Ak1868DK8Bvv/ YmDz0sPs2KdopcJF1hRCYUZAGmLK5GxCrypgvqW1OWoOgaQ+hYgikW31SVob7bacr452 XL2PW4a3V5xeq22ZPDy3y0vxJKbYUd4zSWbwdSSgCfz1zda4TdrxINtJJekTiP0oTxVa KPOiye1SE4VYUMvdf1GIoRuHA94wATodeoIQivJKTr0Ooh+AGe5fQA+cQ3KSeuURH35I 1MAg==
X-Gm-Message-State: AN3rC/53O4ngu7M3epUdpvi8TN9nd0JCFt5Yl3jmMX+xVd32ihqblPdB6eqgp0VKc8jxdg==
X-Received: by 10.55.149.70 with SMTP id x67mr8886265qkd.48.1491592693362; Fri, 07 Apr 2017 12:18:13 -0700 (PDT)
Received: from [172.19.42.52] ([2001:4878:8000:60:d87c:ba97:7d:2ca4]) by smtp.gmail.com with ESMTPSA id h6sm3616556qkd.56.2017.04.07.12.18.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Apr 2017 12:18:12 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: Re: Bad Attitude PechaKucha in Chicago
Date: Fri, 07 Apr 2017 15:18:10 -0400
Message-ID: <2B320218-25BD-4AE4-BE88-F70D6D5F50B7@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j6C8j04Z8cqfruR7t86y3FHAUvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 19:18:21 -0000

Thanks to all who attended and participated in the Chicago Bad Attitude 
PechaKucha.  There were several very amusing presentations.  Watch at 
http://snaggletooth.akam.ai/Chicago-videos/.  Again, special thanks to 
Tero Kivinen who recorded and edited the session video.

—aaron


From nobody Fri Apr  7 12:37:53 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C86D126CD8 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 12:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 hzMGdQQK8TU1 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 12:37:51 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C39C4128DE5 for <ietf@ietf.org>; Fri,  7 Apr 2017 12:37:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2425; q=dns/txt; s=iport; t=1491593870; x=1492803470; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=pbVUJGQkz7nfdqh/h6AHKeosFI4raM5vwd6EtioaVKo=; b=BhN1ayn+uzqwpbLkUBd6AsGy1q739BBCGZelgbKzSJxPRuNuF19PeGze SUKYP9N6qGPf6qX58D7ELoDHjEv8vlntY7oAAnGW9O2osjg7KpIiSIz/N bRdzkx7N37Akpd6gzDxVOwQu6enV2JAKIUf6vu0gOh0cx1JIMIxTakSFA w=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DEAQAx6udY/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBiSOKE3OQMh+VV4IPhiIChBwYAQIBAQEBAQEBayiFFgEFI2YLGCo?= =?us-ascii?q?CAlcGAQwIAQGKC6p9giaKawEBAQEBAQQBAQEBAQEBEg+IUwmCYodcgl8BBJx4g?= =?us-ascii?q?32CDYxOimOGXZN/HziBBSUWCBgVhx4+iW0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,167,1488844800";  d="asc'?scan'208";a="652003786"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 19:37:27 +0000
Received: from [10.61.229.24] ([10.61.229.24]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v37JbQYu031238; Fri, 7 Apr 2017 19:37:26 GMT
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>
Date: Fri, 7 Apr 2017 21:37:25 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kI9Gh8ipfoPFqG6W1OkQTkPuMR2mkUro1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bFWfVt_KCtE2ZMVT6wntbDXw2-4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 19:37:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--kI9Gh8ipfoPFqG6W1OkQTkPuMR2mkUro1
Content-Type: multipart/mixed; boundary="NfpqARJ5t0CdLmaSHkAhgeMqo4Ap8Mqcf";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
In-Reply-To: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>

--NfpqARJ5t0CdLmaSHkAhgeMqo4Ap8Mqcf
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 4/7/17 5:24 AM, Martin Thomson wrote:
> To the extent that we have the tools necessary to protect against perva=
sive
> monitoring, we have to accept that more-legitimate uses of monitoring a=
re
> collateral[...]

=2E.. DAMAGE.

You couldn't even say the word.=20

The whole point of the document is to expand upon the implications of
what operational practices are impacted in an encrypted world.  That
doesn't mean people should stop encrypting, but it does mean that we
should understand what is breaking.  To do otherwise is to stick our
heads in the sand.  Let's not do that.  And let's not question whether a
particular function is "legitimate" which ironically applies a value
judgment, something that you yourself complained about.

Better to focus on whether the impact of encryption has indeed been well
documented.

Eliot
ps: but I agree with your point about statistics.


--NfpqARJ5t0CdLmaSHkAhgeMqo4Ap8Mqcf--

--kI9Gh8ipfoPFqG6W1OkQTkPuMR2mkUro1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY5+p2AAoJEIe2a0bZ0nozFHgH/0KwLjMFK/P9reIY1Mb4KGDD
76JALadhsAcM5ygmLvJRzdygcHVBCJLOqWKD75esE8SEXnn86aXqrJuzqjxIRLlB
FLkTYG18EWOQYvxBCUnq9ld7rAjdyap8dKi60aPIL7kJEur+GgZIOZsfwIruwK4Z
88hvxGCgE3dApt8WFyh81bYF25CosUMHpJyFuQyJX9vrlT3fRHmNZayR7D7tgozy
YmOnaOS16aWpCVZ124gYfMMQEobRb+ejQTlkdNNxVWMzGndrmrjVnWFUpRt+LC+N
HugkQNgMpQMT+fnv1ds3+Zrax2C56SVrE+2CszAZkNm4MdEojoYmH2HVESv/8T4=
=xC9n
-----END PGP SIGNATURE-----

--kI9Gh8ipfoPFqG6W1OkQTkPuMR2mkUro1--


From nobody Fri Apr  7 13:12:44 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1498A128B88 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 13:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.086
X-Spam-Level: 
X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 TomIzGxNqJPA for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 13:12:33 -0700 (PDT)
Received: from nm30-vm6.bullet.mail.gq1.yahoo.com (nm30-vm6.bullet.mail.gq1.yahoo.com [98.136.216.197]) (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 389EE1243FE for <ietf@ietf.org>; Fri,  7 Apr 2017 13:12:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1491595952; bh=D9T/8R3pYgam/dKOxEw0JLrnGdGkAYpn4BIbg/nuNPU=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=Ck4TMDBdVsLFtz9NnwFgI0ane57mgoVsJw4KLaohUNsOo59byphm86Zs8zjuIX1Rvfnyiv17IGJNgMEAYENAZAilyTnR9xGwjKfT98Jm8WaB+FBOj0coIuouE9mmi2mWcjht2wOyCPBDmS4WTUmuVJX18vHz4DjWy6h/gBP6helcN4HATzaXudZCX5fY5/c9RSWNWvaiIyKH/6kaslUh1Oe7KqMGrbta7d/z6Nb7EzYw4mx4Zpd/Rzm11fldSyaRUPGCR2gwKDWW+yie2RVMMyuEnr1WjMpubU5AX1n9SjvIY/xPVnE/zrfzP8aqdJh5NhALpFPiYCxUmf/TYyhOTA==
Received: from [98.137.12.60] by nm30.bullet.mail.gq1.yahoo.com with NNFMP; 07 Apr 2017 20:12:32 -0000
Received: from [98.137.12.237] by tm5.bullet.mail.gq1.yahoo.com with NNFMP; 07 Apr 2017 20:12:32 -0000
Received: from [127.0.0.1] by omp1045.mail.gq1.yahoo.com with NNFMP; 07 Apr 2017 20:12:32 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 603164.73449.bm@omp1045.mail.gq1.yahoo.com
X-YMail-OSG: vpnsUb0VM1nOIXO36aAEYL1cwmJSwuJhxt0_7E.53ZMUSLbV2UDuRhl1f7e4BhB rLiP6gFw6joZrzLHLwcgqjvrv9nVySUH.U5fNvW0oRP3aEz4FTNbxosAV9Ofl5Npq10M6CCTLzph blJsb9AJ..BHOryg43OIMhTTf1SuGYL4jnOh9cOyKMjq56nIEHG8pXw9Dl5E31JRNXKDeYEsYNUm dCvMM7QrPXlQ2Qb4BeHIo.U_.vox.oZRahOmT37.DSHF5OIbOQaLXWV3WyYn7LUXQaqRSqBw6JbP Uja42Lw_WAkgFCtTebXDG_vMWHVOhqHinEJhrnczOfz_M1rhmPoE4b2yoEAlHsQOyB7GqQv8Fl5. h2EJxi8MJqRR7nXGj66W6C.ijZMqkPMHnWnc2ji00wfc3b3AJUbZ3xA4bbs_S_xn2CG04pKkmULS 5OuuBdcRkXaPnTQS89SuTxjI_P5gHw_3vuREwAOoN755khGCm_H_SiNGzccK5wi9de62G8MHKlsg wl4eSagUSQorR0V2NialYibW3zFf6Gn2X_PnJNzJD6ItHTzWddb1Pw3B5FdQpXnguFNabkol3KkA YCWI-
Received: from jws300007.mail.gq1.yahoo.com by sendmailws120.mail.gq1.yahoo.com; Fri, 07 Apr 2017 20:12:32 +0000; 1491595952.242
Date: Fri, 7 Apr 2017 20:12:31 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
Reply-To: <nalini.elkins@insidethestack.com>
To: <ietf@ietf.org>,  <98attendees@ietf.org>,  Aaron Falk <aaron.falk@gmail.com>
Message-ID: <1113175703.4050741.1491595951929@mail.yahoo.com>
Subject: Re: Bad Attitude PechaKucha in Chicago
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <1113175703.4050741.1491595951929.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9272 YahooMailBasic Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6UwJsaw-iR-bP20RNzLsnVu92ds>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:12:37 -0000

Aaron,

Thanks so much for starting a new tradition!

Always love the great fun to be had at the PechaKucha.


Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

--------------------------------------------
On Fri, 4/7/17, Aaron Falk <aaron.falk@gmail.com> wrote:

 Subject: Re: Bad Attitude PechaKucha in Chicago
 To: ietf@ietf.org, 98attendees@ietf.org
 Date: Friday, April 7, 2017, 12:18 PM
=20
 Thanks to all who attended and participated
 in the Chicago Bad Attitude=20
 PechaKucha.=C2=A0 There were several
 very amusing presentations.=C2=A0 Watch at=20
 http://snaggletooth.akam.ai/Chicago-videos/.
  Again, special thanks to=20
 Tero Kivinen who recorded and edited
 the session video.
=20
 =E2=80=94aaron
=20
=20


From nobody Fri Apr  7 13:25:41 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55D0E124BFA; Fri,  7 Apr 2017 13:24:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-isis-auto-conf.all@ietf.org, ietf@ietf.org, isis-wg@ietf.org
Subject: Genart last call review of draft-ietf-isis-auto-conf-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
Date: Fri, 07 Apr 2017 13:24:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_0Vnjk9duSK00ZTWr6KjKg1rV70>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:24:53 -0000

Reviewer: Robert Sparks
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-isis-auto-conf-04
Reviewer: Robert Sparks
Review Date: 2017-04-07
IETF LC End Date: 2017-04-10
IESG Telechat date: 2017-04-13

Summary: Ready for publication as Proposed Standard, but with 
one possible thing to add to the security consideration section

This document is clear and seems straightforward to implement. 

I think, however, there is an attack possibility you should call out 
in the security considerations section. As home routers are used 
as examples of elements that might use this protocol, consider 
the case of a malicious party wanting to deny service in that home.
A suborned device in the home could watch for the protocol, and
present a crafted packet to force the home router(s) to re-start
the autoconfiguration protocol continually (by claiming to be a
duplicate and being careful to make it the routers job to restart).
Having the md5 password configured would mitigate this attack.


From nobody Fri Apr  7 13:48:06 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2CE8127873; Fri,  7 Apr 2017 13:47:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
Subject: Genart last call review of draft-ietf-dnssd-mdns-dns-interop-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149159806986.11195.9301095647004982341@ietfa.amsl.com>
Date: Fri, 07 Apr 2017 13:47:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8yWPHoVovUwFhYVs8iafB0yexQM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:47:50 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dnssd-mdns-dns-interop-04
Reviewer: Robert Sparks
Review Date: 2017-04-07
IETF LC End Date: 2017-04-13
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as an Informational RFC






From nobody Fri Apr  7 13:55:46 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED6E120454; Fri,  7 Apr 2017 13:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 1T2rFpNogp1X; Fri,  7 Apr 2017 13:55:42 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D2412741D; Fri,  7 Apr 2017 13:55:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3134; q=dns/txt; s=iport; t=1491598540; x=1492808140; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9ewat/gfRoAbKiVjXknzPWDeArjRqHYiOXxr8iIbC7A=; b=J55A6aXL4JQ8UyHHGpoOcizvbC8+EipTscbfAqcf5ksm9OhA8ygbPopQ JClref6zDPCNlZ92MdGrfu7xiPad7n7TxU/k3E29gLZ/wRZpJWCgm81Xz Kc9n5xWPAob3f2hv9RXXQtNbh0kRKWQD0KkjGTsPg7pRON1IVneCYmreN w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAgDU++dY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHg1+KE5FElVeCDyqFeAIag0M/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMRRQwEAgEIDgMDAQEBAwIUDwMCAgIwFAEICAIEAQ0FCIoHDqp4giaKa?= =?us-ascii?q?gEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuFQ4RwhSSCOIJfBZx4AYZ/i0+CB4U?= =?us-ascii?q?uihSTfgEfOIEFWxWFHRyBY3WILIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,167,1488844800"; d="scan'208";a="228128711"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 20:55:39 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v37Ktc5h008945 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 20:55:39 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 15:55:38 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 15:55:38 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4Q
Date: Fri, 7 Apr 2017 20:55:38 +0000
Message-ID: <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
In-Reply-To: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O4LL_eZg9AYcdeIYsZ1CC8OpbBU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:55:45 -0000

Um9iZXJ0IC0NCg0KVGhhbnggZm9yIHRoZSByZXZpZXcuDQpSZXBseSBpbmxpbmUuDQoNCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogUm9iZXJ0IFNwYXJrcyBbbWFpbHRvOnJq
c3BhcmtzQG5vc3RydW0uY29tXQ0KPiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDE6MjUg
UE0NCj4gVG86IGdlbi1hcnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNv
bmYuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1Ympl
Y3Q6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYt
MDQNCj4gDQo+IFJldmlld2VyOiBSb2JlcnQgU3BhcmtzDQo+IFJldmlldyByZXN1bHQ6IFJlYWR5
IHdpdGggSXNzdWVzDQo+IA0KPiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZv
ciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldw0KPiBUZWFtIChHZW4tQVJUKSBy
ZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9y
DQo+IHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlr
ZSBhbnkgb3RoZXIgbGFzdCBjYWxsDQo+IGNvbW1lbnRzLg0KPiANCj4gRm9yIG1vcmUgaW5mb3Jt
YXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiANCj4gPGh0dHBzOi8vdHJhYy5pZXRmLm9y
Zy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+IA0KPiBEb2N1bWVudDogZHJhZnQtaWV0Zi1p
c2lzLWF1dG8tY29uZi0wNA0KPiBSZXZpZXdlcjogUm9iZXJ0IFNwYXJrcw0KPiBSZXZpZXcgRGF0
ZTogMjAxNy0wNC0wNw0KPiBJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA0LTEwDQo+IElFU0cgVGVs
ZWNoYXQgZGF0ZTogMjAxNy0wNC0xMw0KPiANCj4gU3VtbWFyeTogUmVhZHkgZm9yIHB1YmxpY2F0
aW9uIGFzIFByb3Bvc2VkIFN0YW5kYXJkLCBidXQgd2l0aCBvbmUgcG9zc2libGUNCj4gdGhpbmcg
dG8gYWRkIHRvIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9uIHNlY3Rpb24NCj4gDQo+IFRoaXMg
ZG9jdW1lbnQgaXMgY2xlYXIgYW5kIHNlZW1zIHN0cmFpZ2h0Zm9yd2FyZCB0byBpbXBsZW1lbnQu
DQo+IA0KPiBJIHRoaW5rLCBob3dldmVyLCB0aGVyZSBpcyBhbiBhdHRhY2sgcG9zc2liaWxpdHkg
eW91IHNob3VsZCBjYWxsIG91dCBpbiB0aGUNCj4gc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2Vj
dGlvbi4gQXMgaG9tZSByb3V0ZXJzIGFyZSB1c2VkIGFzIGV4YW1wbGVzIG9mDQo+IGVsZW1lbnRz
IHRoYXQgbWlnaHQgdXNlIHRoaXMgcHJvdG9jb2wsIGNvbnNpZGVyIHRoZSBjYXNlIG9mIGEgbWFs
aWNpb3VzIHBhcnR5DQo+IHdhbnRpbmcgdG8gZGVueSBzZXJ2aWNlIGluIHRoYXQgaG9tZS4NCj4g
QSBzdWJvcm5lZCBkZXZpY2UgaW4gdGhlIGhvbWUgY291bGQgd2F0Y2ggZm9yIHRoZSBwcm90b2Nv
bCwgYW5kIHByZXNlbnQgYQ0KPiBjcmFmdGVkIHBhY2tldCB0byBmb3JjZSB0aGUgaG9tZSByb3V0
ZXIocykgdG8gcmUtc3RhcnQgdGhlIGF1dG9jb25maWd1cmF0aW9uDQo+IHByb3RvY29sIGNvbnRp
bnVhbGx5IChieSBjbGFpbWluZyB0byBiZSBhIGR1cGxpY2F0ZSBhbmQgYmVpbmcgY2FyZWZ1bCB0
byBtYWtlDQo+IGl0IHRoZSByb3V0ZXJzIGpvYiB0byByZXN0YXJ0KS4NCj4gSGF2aW5nIHRoZSBt
ZDUgcGFzc3dvcmQgY29uZmlndXJlZCB3b3VsZCBtaXRpZ2F0ZSB0aGlzIGF0dGFjay4NCg0KW0xl
czpdIFRoZSBkcmFmdCBzYXlzIHR3byB0aGluZ3Mgd2hpY2ggYXJlIHJlbGV2YW50Og0KDQozLjUu
MS4gIEF1dGhlbnRpY2F0aW9uIFRMVg0KDQogICBJdCBpcyBSRUNPTU1FTkRFRCB0aGF0IElTLUlT
IHJvdXRlcnMgc3VwcG9ydGluZyB0aGlzIHNwZWNpZmljYXRpb24NCiAgIG9mZmVyIGFuIG9wdGlv
biB0byBleHBsaWNpdGx5IGNvbmZpZ3VyZSBhIHNpbmdsZSBwYXNzd29yZCBmb3IgSE1BQy0NCiAg
IE1ENSBhdXRoZW50aWNhdGlvbiBhcyBzcGVjaWZpZWQgaW5bUkZDNTMwNF0uDQoNCjQuICBTZWN1
cml0eSBDb25zaWRlcmF0aW9ucw0KDQogICBJbiBnZW5lcmFsLCB0aGUgdXNlIG9mIGF1dGhlbnRp
Y2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1dG8tDQogICBjb25maWd1cmF0aW9uIGFzIGl0
IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQoNCkl0IHNlZW1zIHRvIG1lIHRo
YXQgdGhlc2Ugc2VjdGlvbnMgYWRlcXVhdGVseSBjb3ZlciB5b3VyIHBvaW50Lg0KPz8/DQoNCiAg
ICBMZXMNCg0K


From nobody Fri Apr  7 14:18:40 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB5B128B91; Fri,  7 Apr 2017 14:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 EOG1fxzy8oYx; Fri,  7 Apr 2017 14:18:23 -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 7B27C1292D0; Fri,  7 Apr 2017 14:18:03 -0700 (PDT)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v37LHx4q031384 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 7 Apr 2017 16:18:00 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
Subject: Re: Genart last call review of draft-ietf-isis-auto-conf-04
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
Cc: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com>
Date: Fri, 7 Apr 2017 16:17:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l5kB563lH6Yti3kwSeiED1N2Tvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:18:32 -0000

On 4/7/17 3:55 PM, Les Ginsberg (ginsberg) wrote:
> Robert -
>
> Thanx for the review.
> Reply inline.
>
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Friday, April 07, 2017 1:25 PM
>> To: gen-art@ietf.org
>> Cc: draft-ietf-isis-auto-conf.all@ietf.org; ietf@ietf.org; isis-wg@ietf.org
>> Subject: Genart last call review of draft-ietf-isis-auto-conf-04
>>
>> Reviewer: Robert Sparks
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area Review
>> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
>> the IETF Chair.  Please treat these comments just like any other last call
>> comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-isis-auto-conf-04
>> Reviewer: Robert Sparks
>> Review Date: 2017-04-07
>> IETF LC End Date: 2017-04-10
>> IESG Telechat date: 2017-04-13
>>
>> Summary: Ready for publication as Proposed Standard, but with one possible
>> thing to add to the security consideration section
>>
>> This document is clear and seems straightforward to implement.
>>
>> I think, however, there is an attack possibility you should call out in the
>> security considerations section. As home routers are used as examples of
>> elements that might use this protocol, consider the case of a malicious party
>> wanting to deny service in that home.
>> A suborned device in the home could watch for the protocol, and present a
>> crafted packet to force the home router(s) to re-start the autoconfiguration
>> protocol continually (by claiming to be a duplicate and being careful to make
>> it the routers job to restart).
>> Having the md5 password configured would mitigate this attack.
> [Les:] The draft says two things which are relevant:
>
> 3.5.1.  Authentication TLV
>
>     It is RECOMMENDED that IS-IS routers supporting this specification
>     offer an option to explicitly configure a single password for HMAC-
>     MD5 authentication as specified in[RFC5304].
>
> 4.  Security Considerations
>
>     In general, the use of authentication is incompatible with auto-
>     configuration as it requires some manual configuration.
>
> It seems to me that these sections adequately cover your point.
> ???
They provide the mitigation. They do not call out the risk.

The current security considerations section says for wired networks, 
plugging into the wire is protection enough, and you don't need to use 
the authentication tlv.  I don't think that's true given the possibility 
of this attack. I suggest discussing the attack in the security 
considerations section and pointing to using the Authentication TLV with 
it's onerous bit of manual configuration as the mitigation.

>
>      Les
>


From nobody Fri Apr  7 14:30:58 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377131200C1; Fri,  7 Apr 2017 14:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 wsvwksPF2roP; Fri,  7 Apr 2017 14:30:28 -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 A5EA0127871; Fri,  7 Apr 2017 14:30:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5604; q=dns/txt; s=iport; t=1491600616; x=1492810216; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6TNYProto9lO+SJcnYZiGRBEYaDNB8tFLT112Bereuw=; b=Oc6eXDv1QXb3m/wp6tPE3xYbLUKSqX1U3XM16nZ3V2s1h7KWyxIky+fv fcRBukagGrhiBiG9w655o1mNYfE/HsCA5kt56PIFnMTuJyMUhTLlsZfR8 a/lRn5pEWHIVm15H55NhM8G9urDmS/PyAcjVup2/aZjc0uoXDzjYJ7isv c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAgCNBOhY/5hdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHg1+KE5FElVeCDyqFeAIag0Q/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMRRQwEAgEIDgMDAQEBAQICFA8DAgICMBQBCAgCBAENBQiKBw6qZoImi?= =?us-ascii?q?moBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYELhUOEcIUkgjiCXwWJKpNOAYZ/i0+?= =?us-ascii?q?CB4UuihSTfgEfOIEFWxWFHRyBY3WILIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="233901098"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 21:30:15 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v37LUFXN002047 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 21:30:15 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 16:30:14 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 16:30:14 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkA==
Date: Fri, 7 Apr 2017 21:30:14 +0000
Message-ID: <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com>
In-Reply-To: <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PdcDcYWig1TAG0nuRU1TUOzSYE0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:30:34 -0000

Um9iZXJ0IC0NCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBSb2JlcnQg
U3BhcmtzIFttYWlsdG86cmpzcGFya3NAbm9zdHJ1bS5jb21dDQo+IFNlbnQ6IEZyaWRheSwgQXBy
aWwgMDcsIDIwMTcgMjoxOCBQTQ0KPiBUbzogTGVzIEdpbnNiZXJnIChnaW5zYmVyZyk7IGdlbi1h
cnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBHZW5hcnQg
bGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+IA0KPiAN
Cj4gDQo+IE9uIDQvNy8xNyAzOjU1IFBNLCBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKSB3cm90ZToN
Cj4gPiBSb2JlcnQgLQ0KPiA+DQo+ID4gVGhhbnggZm9yIHRoZSByZXZpZXcuDQo+ID4gUmVwbHkg
aW5saW5lLg0KPiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206
IFJvYmVydCBTcGFya3MgW21haWx0bzpyanNwYXJrc0Bub3N0cnVtLmNvbV0NCj4gPj4gU2VudDog
RnJpZGF5LCBBcHJpbCAwNywgMjAxNyAxOjI1IFBNDQo+ID4+IFRvOiBnZW4tYXJ0QGlldGYub3Jn
DQo+ID4+IENjOiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBp
ZXRmLm9yZzsNCj4gPj4gaXNpcy13Z0BpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBHZW5hcnQgbGFz
dCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+ID4+DQo+ID4+
IFJldmlld2VyOiBSb2JlcnQgU3BhcmtzDQo+ID4+IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGgg
SXNzdWVzDQo+ID4+DQo+ID4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9y
IHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gPj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQp
IHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieQ0KPiA+PiB0aGUg
SUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVz
dCBsaWtlDQo+ID4+IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ID4+DQo+ID4+IEZv
ciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPj4NCj4gPj4gPGh0
dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+ID4+DQo+ID4+
IERvY3VtZW50OiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+ID4+IFJldmlld2VyOiBS
b2JlcnQgU3BhcmtzDQo+ID4+IFJldmlldyBEYXRlOiAyMDE3LTA0LTA3DQo+ID4+IElFVEYgTEMg
RW5kIERhdGU6IDIwMTctMDQtMTANCj4gPj4gSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA0LTEz
DQo+ID4+DQo+ID4+IFN1bW1hcnk6IFJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBQcm9wb3NlZCBT
dGFuZGFyZCwgYnV0IHdpdGggb25lDQo+ID4+IHBvc3NpYmxlIHRoaW5nIHRvIGFkZCB0byB0aGUg
c2VjdXJpdHkgY29uc2lkZXJhdGlvbiBzZWN0aW9uDQo+ID4+DQo+ID4+IFRoaXMgZG9jdW1lbnQg
aXMgY2xlYXIgYW5kIHNlZW1zIHN0cmFpZ2h0Zm9yd2FyZCB0byBpbXBsZW1lbnQuDQo+ID4+DQo+
ID4+IEkgdGhpbmssIGhvd2V2ZXIsIHRoZXJlIGlzIGFuIGF0dGFjayBwb3NzaWJpbGl0eSB5b3Ug
c2hvdWxkIGNhbGwgb3V0DQo+ID4+IGluIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0
aW9uLiBBcyBob21lIHJvdXRlcnMgYXJlIHVzZWQgYXMNCj4gPj4gZXhhbXBsZXMgb2YgZWxlbWVu
dHMgdGhhdCBtaWdodCB1c2UgdGhpcyBwcm90b2NvbCwgY29uc2lkZXIgdGhlIGNhc2UNCj4gPj4g
b2YgYSBtYWxpY2lvdXMgcGFydHkgd2FudGluZyB0byBkZW55IHNlcnZpY2UgaW4gdGhhdCBob21l
Lg0KPiA+PiBBIHN1Ym9ybmVkIGRldmljZSBpbiB0aGUgaG9tZSBjb3VsZCB3YXRjaCBmb3IgdGhl
IHByb3RvY29sLCBhbmQNCj4gPj4gcHJlc2VudCBhIGNyYWZ0ZWQgcGFja2V0IHRvIGZvcmNlIHRo
ZSBob21lIHJvdXRlcihzKSB0byByZS1zdGFydCB0aGUNCj4gPj4gYXV0b2NvbmZpZ3VyYXRpb24g
cHJvdG9jb2wgY29udGludWFsbHkgKGJ5IGNsYWltaW5nIHRvIGJlIGEgZHVwbGljYXRlDQo+ID4+
IGFuZCBiZWluZyBjYXJlZnVsIHRvIG1ha2UgaXQgdGhlIHJvdXRlcnMgam9iIHRvIHJlc3RhcnQp
Lg0KPiA+PiBIYXZpbmcgdGhlIG1kNSBwYXNzd29yZCBjb25maWd1cmVkIHdvdWxkIG1pdGlnYXRl
IHRoaXMgYXR0YWNrLg0KPiA+IFtMZXM6XSBUaGUgZHJhZnQgc2F5cyB0d28gdGhpbmdzIHdoaWNo
IGFyZSByZWxldmFudDoNCj4gPg0KPiA+IDMuNS4xLiAgQXV0aGVudGljYXRpb24gVExWDQo+ID4N
Cj4gPiAgICAgSXQgaXMgUkVDT01NRU5ERUQgdGhhdCBJUy1JUyByb3V0ZXJzIHN1cHBvcnRpbmcg
dGhpcyBzcGVjaWZpY2F0aW9uDQo+ID4gICAgIG9mZmVyIGFuIG9wdGlvbiB0byBleHBsaWNpdGx5
IGNvbmZpZ3VyZSBhIHNpbmdsZSBwYXNzd29yZCBmb3IgSE1BQy0NCj4gPiAgICAgTUQ1IGF1dGhl
bnRpY2F0aW9uIGFzIHNwZWNpZmllZCBpbltSRkM1MzA0XS4NCj4gPg0KPiA+IDQuICBTZWN1cml0
eSBDb25zaWRlcmF0aW9ucw0KPiA+DQo+ID4gICAgIEluIGdlbmVyYWwsIHRoZSB1c2Ugb2YgYXV0
aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCj4gPiAgICAgY29uZmlndXJh
dGlvbiBhcyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KPiA+DQo+ID4g
SXQgc2VlbXMgdG8gbWUgdGhhdCB0aGVzZSBzZWN0aW9ucyBhZGVxdWF0ZWx5IGNvdmVyIHlvdXIg
cG9pbnQuDQo+ID4gPz8/DQo+IFRoZXkgcHJvdmlkZSB0aGUgbWl0aWdhdGlvbi4gVGhleSBkbyBu
b3QgY2FsbCBvdXQgdGhlIHJpc2suDQo+IA0KPiBUaGUgY3VycmVudCBzZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBzZWN0aW9uIHNheXMgZm9yIHdpcmVkIG5ldHdvcmtzLCBwbHVnZ2luZw0KPiBpbnRv
IHRoZSB3aXJlIGlzIHByb3RlY3Rpb24gZW5vdWdoLCBhbmQgeW91IGRvbid0IG5lZWQgdG8gdXNl
IHRoZQ0KPiBhdXRoZW50aWNhdGlvbiB0bHYuICBJIGRvbid0IHRoaW5rIHRoYXQncyB0cnVlIGdp
dmVuIHRoZSBwb3NzaWJpbGl0eSBvZiB0aGlzIGF0dGFjay4NCj4gSSBzdWdnZXN0IGRpc2N1c3Np
bmcgdGhlIGF0dGFjayBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2VjdGlvbiBhbmQN
Cj4gcG9pbnRpbmcgdG8gdXNpbmcgdGhlIEF1dGhlbnRpY2F0aW9uIFRMViB3aXRoIGl0J3Mgb25l
cm91cyBiaXQgb2YgbWFudWFsDQo+IGNvbmZpZ3VyYXRpb24gYXMgdGhlIG1pdGlnYXRpb24uDQo+
IA0KW0xlczpdIElmIHlvdSBpbnNpc3QgSSBhbSBPSyB3aXRoIHRoaXMgLSBidXQgZnJhbmtseSB5
b3UgYXJlIHR3aXN0aW5nIG15IGFybS4gOi0pDQpTeXN0ZW0taWQgZHVwbGljYXRpb24gaXMgYSBw
cm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0IGF1dG9jb25maWcgZGVwbG95bWVu
dHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55IG5ldHdvcmsgdW50aWwgaXQgaXMg
cmVzb2x2ZWQuDQpUaGUgb25seSB0aGluZyBhdXRvY29uZmlnIGhhcyBhZGRlZCBpcyBhIHdheSB0
byByZXNvbHZlIHRoaXMgdy9vIG1hbnVhbCBpbnRlcnZlbnRpb24uIFRoaXMgaW4gbm8gd2F5IGlu
Y3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3IgdGhlIGRpc3J1cHRpb24gdGhlIGF0dGFja2Vy
IGNhbiBwcm9kdWNlLiAoWWVzIC0gSSBzdGF0ZSB0aGF0IHF1aXRlIGludGVudGlvbmFsbHkpLg0K
U28geW91IGFyZSBhc2tpbmcgdXMgdG8gcmVwZWF0IGEgZGlzY3Vzc2lvbiB3aGljaCBoYXMgYWxy
ZWFkeSBiZWVuIGhlbGQgaW4gdGhlIGNvbnRleHQgb2YgUkZDIDUzMDQgYW5kIFJGQyA1MzEwLg0K
DQpJdCB3b3VsZCBiZSBtb3JlIGFwcHJvcHJpYXRlIHRvIGFkZCB0aGUgbm9ybWFsIHJlZmVyZW5j
ZSB0byBSRkMgNTMwNC81MzEwIGluIHRoZSBTZWN1cml0eSBzZWN0aW9uIHRoYW4gd2hhdCB5b3Ug
cHJvcG9zZS4NCg0KICAgTGVzDQoNCj4gPg0KPiA+ICAgICAgTGVzDQo+ID4NCg0K


From nobody Fri Apr  7 14:45:08 2017
Return-Path: <aretana@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A20B128954; Fri,  7 Apr 2017 14:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 9IQu480dmgNU; Fri,  7 Apr 2017 14:44:49 -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 87669127867; Fri,  7 Apr 2017 14:44:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2054; q=dns/txt; s=iport; t=1491601479; x=1492811079; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ex9eRFrNp5aIHAeA9nV+XTDS3EGQEvumdwkHZtElj0k=; b=LRxgexDVFAFKGd6pT5dpWwcvxbv34BMAZbsHX8aqBd+XlXUwa7xLFjSm BPlJEc/nTc94lfEu1Z39rY2/BDNv/mln7CcDWle8WEh2XObpykD53r7bz OXEV4wYZOqYVHOk9v96kDiWWE8pJir0Gj8j/MMOftc9qvvHR6Humq8VNz A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgCgB+hY/5JdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTkUSVV4IPhiICGoNEPxgBAgEBAQEBAQFrKIUWAQQ?= =?us-ascii?q?BIxFFBQsCAQgaAiYCAgIwFRACBAENBYoHCKsJgiaKagEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAR2BC4VDggWCa4RWgwYugjEBBJYfhlkBklcKkTaTfgEfOIEFWxVSAYZ?= =?us-ascii?q?JdYgsgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="228460278"
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; 07 Apr 2017 21:44:38 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v37LicQ9023688 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 21:44:38 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 16:44:38 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 16:44:37 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeA
Date: Fri, 7 Apr 2017 21:44:37 +0000
Message-ID: <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
In-Reply-To: <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <70AB0C03D82FC941A35D0037BC501F0B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ABEROiR_pOwpcMjoUzKDK4mX4E8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:44:53 -0000

T24gNC83LzE3LCA1OjMwIFBNLCAiTGVzIEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5zYmVyZ0Bj
aXNjby5jb20+IHdyb3RlOg0KDQpMZXM6DQoNCkhpIQ0KDQo+IFN5c3RlbS1pZCBkdXBsaWNhdGlv
biBpcyBhIHByb2JsZW0gZm9yIGFueSBkZXBsb3ltZW50IC0gbm90IGp1c3QgYXV0b2NvbmZpZyAN
Cj4gZGVwbG95bWVudHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55IG5ldHdvcmsg
dW50aWwgaXQgaXMgcmVzb2x2ZWQuDQo+DQo+IFRoZSBvbmx5IHRoaW5nIGF1dG9jb25maWcgaGFz
IGFkZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28gbWFudWFsIA0KPiBpbnRlcnZlbnRp
b24uIFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3IgdGhlIGRp
c3J1cHRpb24gdGhlIA0KPiBhdHRhY2tlciBjYW4gcHJvZHVjZS4gKFllcyAtIEkgc3RhdGUgdGhh
dCBxdWl0ZSBpbnRlbnRpb25hbGx5KS4NCg0KSSBkb27igJl0IGtub3cgYWJvdXQgUm9iZXJ0LCBi
dXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291bGQgbGlrZSB0byBzZWUuDQoN
ClllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2ZSBhbHdheXMgYmVlbiBhIHBvdGVudGlhbCBw
cm9ibGVtLCBidXQgdGhpcyBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3IGRlLWR1cGxpY2F0aW9u
IG1lY2hhbmlzbSB0aGF0IHJlc3VsdHMgbm90IGp1c3QgaW4gdW5zeW5j4oCZZCBkYXRhYmFzZXMs
IGJ1dCBpbiByZXN0YXJ0aW5nIGFkamFjZW5jaWVzIOKAkyBzbyBhdCBsZWFzdCB0aGUgbWFuaWZl
c3RhdGlvbiBvZiB0aGUgcHJvYmxlbSBpcyBkaWZmZXJlbnQuDQoNCj4gU28geW91IGFyZSBhc2tp
bmcgdXMgdG8gcmVwZWF0IGEgZGlzY3Vzc2lvbiB3aGljaCBoYXMgYWxyZWFkeSBiZWVuIGhlbGQg
aW4gdGhlIGNvbnRleHQgb2YgDQo+IFJGQyA1MzA0IGFuZCBSRkMgNTMxMC4NCj4NCj4gSXQgd291
bGQgYmUgbW9yZSBhcHByb3ByaWF0ZSB0byBhZGQgdGhlIG5vcm1hbCByZWZlcmVuY2UgdG8gUkZD
IDUzMDQvNTMxMCBpbiB0aGUgDQo+IFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9w
b3NlLg0KDQpJIGRvbuKAmXQgdGhpbmsgaXQgaHVydHMgdG8gYWRkIGEgcmVmZXJlbmNlIHRvIHRo
b3NlIFJGQ3MsIGJ1dCB0aGV5IGFyZSBib3RoIGFib3V0IGFkZGluZyBhdXRoZW50aWNhdGlvbiDi
gJMgdGhlIHByb2JsZW0gaW4gdGhpcyBkb2N1bWVudCBpcyBleGFjZXJiYXRlZCBieSB0aGUgZmFj
dCB0aGF0IHRoZXJl4oCZcyBubyBhdXRoZW50aWNhdGlvbiBieSBkZWZhdWx0Lg0KDQpUaGUgbG93
ZXIgbGF5ZXIgYXV0aGVudGljYXRpb24gbWVjaGFuaXNtcyBhcmUgcXVpdGUgd2Vhaywgc3BlY2lh
bGx5IGtub3dpbmcgdGhhdCwgaWYgaW4gYSBob21lIGVudmlyb25tZW50LCBmb3IgZXhhbXBsZSwg
aXQgbWF5IGJlIHJlbGF0aXZlbHkgZWFzeSB0byBjb25uZWN0IHRvIHRoZSBXaUZpIG5ldHdvcmsu
DQoNCkFsdmFyby4NCg0KDQo=


From nobody Fri Apr  7 15:31:50 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAC7128B8E for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 JmRZMnmXeZsJ for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:31:29 -0700 (PDT)
Received: from mx36-42.antispamcloud.com (mx36-42.antispamcloud.com [209.126.121.30]) (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 C05B112714F for <ietf@ietf.org>; Fri,  7 Apr 2017 15:31:25 -0700 (PDT)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx36.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1cwcPc-0002zp-13 for ietf@ietf.org; Sat, 08 Apr 2017 00:31:25 +0200
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1cwcPZ-0002ml-3e for ietf@ietf.org; Fri, 07 Apr 2017 18:31:23 -0400
Received: (qmail 21848 invoked from network); 7 Apr 2017 22:31:19 -0000
Received: from unknown (HELO [192.168.1.100]) (Authenticated-user:_huitema@huitema.net@[172.56.42.160]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 7 Apr 2017 22:31:18 -0000
To: ietf@ietf.org
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <1055d237-bc13-4256-b2c9-8cdb6a051f36@huitema.net>
Date: Fri, 7 Apr 2017 15:31:02 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tRjemhPmvrkcBRqDaXrwuTBOeUdstdI5A"
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
X-Originating-IP: 168.144.250.245
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.12)
X-Recommended-Action: accept
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49EdlGitVsfXsrKty9N3esIJTugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXoPCVymTWz1uTkktataArLFRcOb18WfxGyg6Om6u4YYm9TyXzfF3J6jTvvI 6UncKfo5hjoyEb9Oq0NWpyO3vrfYy2h1mQR50Wwo5hSyeApVLD3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSB0ktSrwQbrgk6jfwMHIN4qnTFgIfDMShmlQFqCr5hA8xAXSGwpLGc/Znuh3MoIpK0tNqH1SeM PJJ05aeBYzCpn7bRF0J+AL6gRRwFcty0/RGJ+cv73CChOPjKA0/DVd83mzKXD5o/Ia+BqyQ7Q0nt IZ2PVtMHd8bHCmdzlxzVIEgwyGTHIAoNFX+jcW7DGmdE6eBVl9/A6GtGi+mfMSANmjLzCyMdOETT xDqixVDal2Zqxiuap5uKiBpffUsHYsfmrbtbs8GJuRKR6hnrta1usy6F/SOWlhnS7qkS/mOkSgAg eNjxIyqtWcsHzPElnaBFglzR8EKamCCPLRQqfIrw/klMQ2q4n8BL2ta15Q6ywoQ6tlBUQ0Dl04Q1 kcE1KDT0GyoCJJa3e874rwXXGPuEmSKg33smtlc64dR/aNUnR+kcQlvCYTspYJdGl64rm9ixxYJS vH1uwzGpXypuXzvU+afg30EnuC0exlTpeePYDi+Ke72V7y3QDXL8JTpxprEN
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8iAzvrzUKVGS0mBeZhDuh2MAAnI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 22:31:34 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tRjemhPmvrkcBRqDaXrwuTBOeUdstdI5A
Content-Type: multipart/mixed; boundary="vJet8Q5fqatrmqSjTAWIlupBJh7ngUlGg";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: ietf@ietf.org
Message-ID: <1055d237-bc13-4256-b2c9-8cdb6a051f36@huitema.net>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com>
 <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>
In-Reply-To: <8496267e-3d06-c8ef-3043-4041276dbda0@cisco.com>

--vJet8Q5fqatrmqSjTAWIlupBJh7ngUlGg
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 4/7/2017 12:37 PM, Eliot Lear wrote:
>
> On 4/7/17 5:24 AM, Martin Thomson wrote:
>> To the extent that we have the tools necessary to protect against perv=
asive
>> monitoring, we have to accept that more-legitimate uses of monitoring =
are
>> collateral[...]
> ... DAMAGE.
>
> You couldn't even say the word.=20
>
> The whole point of the document is to expand upon the implications of
> what operational practices are impacted in an encrypted world.  That
> doesn't mean people should stop encrypting, but it does mean that we
> should understand what is breaking.  To do otherwise is to stick our
> heads in the sand.  Let's not do that.  And let's not question whether =
a
> particular function is "legitimate" which ironically applies a value
> judgment, something that you yourself complained about.
>
> Better to focus on whether the impact of encryption has indeed been wel=
l
> documented.
Having read draft-mm-wg-effect-encrypt-10, I agree with Martin. This
draft is hard to read, and provides a confusing mix of business goals,
techniques, and complaints. My personal recommendation, like Martin's,
is that it would benefit from a thorough rewrite before publication.

I also agree with Martin's recommendation to leave QUIC out of this
business, since it is not standardized yet. The proper place for the
QUIC related text is in a contribution to the QUIC WG.

The draft presents a number of practices, but does not really articulate
practices and business goals. In fact, it starts from the practices,
instead of starting from the goals. My recommendation would be to start
by articulating the "business goals" such as Parental Control, Spam
Filtering, Phishing Prevention, Data Leak Prevention, Insertion of
Super-Cookies, Traffic Engineering, Traffic Prioritization, Data
Compression, Traffic Intercept, Censorship, or Load Balancing. The draft
could then explain how each of these goals are performed by a variety of
techniques, some of which are deployed on the end points, and some other
at various places in the network using a variety of techniques,
including header analysis and deep packet inspection. And then the draft
could have another section explaining how network-based techniques may
or may not be affected by the deployment of encryption.

As a bonus point, we could also note that many of the business goals are
somewhat controversial, and state the controversy.

But the current draft is too confusing for being endorsed by the IETF.

-- Christian Huitema






>
> Eliot
> ps: but I agree with your point about statistics.
>



--vJet8Q5fqatrmqSjTAWIlupBJh7ngUlGg--

--tRjemhPmvrkcBRqDaXrwuTBOeUdstdI5A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJY6BM1AAoJELba05IUOHVQlhIIAKXDxqKfYwIAI7kFjRPvOBtG
2mvi2SPeQQyzoA0PXueRrdgPoYeNbvJUlLqRN+nGpOg34+1BL0WUnolOeuCr4Fsq
SKYNX1YFgVm/UvsoTArejWf8XSQ7N7JzvHIGxpyoKNlhc7xACPH+Ezh/8dFeNspI
1GTjDzyfbfuejz+8r3GEFKYCz7NfrmtWWXTjqpsyoeYbOZOcGws0D2bACf0TXAFc
sbLGBPtNqMacC8RfLyRTYz8Fys8cUyxWLJ96mb51b7jhPRaYjEKKO/XAklJPMmvr
s6f4Jb85Q0q80s2fQYynEARTMIYhDG+t9DwMOMx0WAD5QAs1esPWWy1QBxuhu0o=
=YQdZ
-----END PGP SIGNATURE-----

--tRjemhPmvrkcBRqDaXrwuTBOeUdstdI5A--


From nobody Fri Apr  7 15:45:06 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE3112714F; Fri,  7 Apr 2017 15:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 D5bekc4kL0BF; Fri,  7 Apr 2017 15:44:32 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57780128B8E; Fri,  7 Apr 2017 15:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4000; q=dns/txt; s=iport; t=1491605067; x=1492814667; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=nHmSyAnRov0e8Q1BW7uMEdM0PAE08g0b0qFKipF0eik=; b=USNIDVuGyYmUm15unI9XvYbEK4IsdDjlFxVnSmTlszzkZ1ekapr9iO8x Cg6AIdoDeNCl0gu861bVSHIwLnlT9+gVxfJP9gsZCzG0L9W8gWOob/EYo zplLMMOHIPoyGq4XpLhujPqL/qsoa6LuxCKsZpxuZ4DIWgnce/r4l2aAW 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgACFehY/5pdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrgWwHg1+KE5FElVeCD4YiAhqDRD8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECASMRRQwEAgEIEQQBAQECAiYCAgIwFQgIAgQBDQUIiX8IqlyCJopqAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHYELhUOEcIdcgl8FnHgBkk6RSZN+AR84gQVbFYc?= =?us-ascii?q?cdYgsgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="230307470"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 22:44:26 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v37MiQsA022101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 22:44:26 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 17:44:25 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 17:44:25 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkIAAWZ6A//+58rA=
Date: Fri, 7 Apr 2017 22:44:25 +0000
Message-ID: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
In-Reply-To: <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gYG5N3NAXqhpf0EChMPmggxAeNo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 22:44:39 -0000

QWx2YXJvIC0NCg0KTm90IHN1cmUgaG93IGxvbmcgd2Ugc2hvdWxkIGRlYmF0ZSB0aGlzIGFzIHRo
ZSB0ZXh0IHlvdSBhcmUgYXNraW5nIGZvciBpcyBtb2Rlc3QgLSBidXQgb25lIG1vcmUgYXR0ZW1w
dCBvbiBteSBwYXJ0IC0gbm90IHNvIG11Y2ggdG8gZGViYXRlIHdoZXRoZXIgdG8gYWRkIHRleHQg
b3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4NCg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKQ0K
PiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDI6NDUgUE0NCj4gVG86IExlcyBHaW5zYmVy
ZyAoZ2luc2JlcmcpOyBSb2JlcnQgU3BhcmtzOyBnZW4tYXJ0QGlldGYub3JnDQo+IENjOiBkcmFm
dC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgaXNpcy13
Z0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJh
ZnQtaWV0Zi1pc2lzLWF1dG8tY29uZi0wNA0KPiANCj4gT24gNC83LzE3LCA1OjMwIFBNLCAiTGVz
IEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5zYmVyZ0BjaXNjby5jb20+IHdyb3RlOg0KPiANCj4g
TGVzOg0KPiANCj4gSGkhDQo+IA0KPiA+IFN5c3RlbS1pZCBkdXBsaWNhdGlvbiBpcyBhIHByb2Js
ZW0gZm9yIGFueSBkZXBsb3ltZW50IC0gbm90IGp1c3QNCj4gPiBhdXRvY29uZmlnIGRlcGxveW1l
bnRzLiBBbmQgaXQgd2lsbCBiZSBkaXNydXB0aXZlIGluIGFueSBuZXR3b3JrIHVudGlsIGl0IGlz
DQo+IHJlc29sdmVkLg0KPiA+DQo+ID4gVGhlIG9ubHkgdGhpbmcgYXV0b2NvbmZpZyBoYXMgYWRk
ZWQgaXMgYSB3YXkgdG8gcmVzb2x2ZSB0aGlzIHcvbw0KPiA+IG1hbnVhbCBpbnRlcnZlbnRpb24u
IFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3INCj4gPiB0aGUg
ZGlzcnVwdGlvbiB0aGUgYXR0YWNrZXIgY2FuIHByb2R1Y2UuIChZZXMgLSBJIHN0YXRlIHRoYXQg
cXVpdGUNCj4gaW50ZW50aW9uYWxseSkuDQo+IA0KPiBJIGRvbuKAmXQga25vdyBhYm91dCBSb2Jl
cnQsIGJ1dCB0aGF0IGlzIHBhcnQgb2YgdGhlIGRpc2N1c3Npb24gSSB3b3VsZCBsaWtlIHRvDQo+
IHNlZS4NCj4gDQo+IFllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2ZSBhbHdheXMgYmVlbiBh
IHBvdGVudGlhbCBwcm9ibGVtLCBidXQgdGhpcw0KPiBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3
IGRlLWR1cGxpY2F0aW9uIG1lY2hhbmlzbSB0aGF0IHJlc3VsdHMgbm90IGp1c3QNCj4gaW4gdW5z
eW5j4oCZZCBkYXRhYmFzZXMsIGJ1dCBpbiByZXN0YXJ0aW5nIGFkamFjZW5jaWVzIOKAkyBzbyBh
dCBsZWFzdCB0aGUNCj4gbWFuaWZlc3RhdGlvbiBvZiB0aGUgcHJvYmxlbSBpcyBkaWZmZXJlbnQu
DQo+IA0KW0xlczpdIFRoZSAicHJvYmxlbSIgZXhpc3RzIGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0
ZSBzeXN0ZW0taWRzIGV4aXN0LiBUaGUgcmVjb3ZlcnkgbWVjaGFuaXNtIGRvZXMgbm90IGludHJv
ZHVjZSBuZXcgcHJvYmxlbXMgLSBpdCBhY3R1YWxseSBhY3RzIHRvIG1pbmltaXplIHRoZSBkdXJh
dGlvbiBvZiB0aGUgcHJvYmxlbS4gT25lIGNvdWxkIGFyZ3VlIChhbmQgSSBhbSBOT1QgZG9pbmcg
c28pIHRoYXQgYXV0b21hdGVkIHJlc29sdXRpb24gY291bGQgYmUgYSBiZW5lZml0IGluIGFsbCBk
ZXBsb3ltZW50cy4gSSB0aGluayB0aGUgaXNzdWUgaW4gbm9uLWF1dG9jb25maWcgZGVwbG95bWVu
dHMgaXMgdGhhdCBzaW5jZSBzeXN0ZW1zIGhhdmUgYmVlbiBtYW51YWxseSBwcm92aXNpb25lZCB3
ZSBjYW5ub3QgYXNzdW1lIHRoYXQgbmV0d29yayBvcGVyYXRvcnMgd2FudCB1cyB0byBhdXRvbWF0
aWNhbGx5IGNoYW5nZSB0aGUgY29uZmlnIG9uIG9uZSBvZiB0aGVpciBib3hlcy4gVGhvdWdoLCB3
aG8ga25vd3MgLSBtYXliZSB3ZSB3aWxsIGdldCBhc2tlZCB0byB1c2UgdGhpcyBleHRlbnNpb24g
b3V0c2lkZSBvZiBhdXRvY29uZmlnIGRlcGxveW1lbnRzLiANCg0KSXQgaXMgbmVjZXNzYXJ5IHRv
IGhhdmUgc3VjaCBhIG1lY2hhbmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzIHNpbmNlIHRo
ZXJlIGlzIC0gYnkgZGVmYXVsdCAtIG5vIG1hbnVhbCBpbnRlcnZlbnRpb24uIEJ1dCB0byBjaGFy
YWN0ZXJpemUgdGhpcyBhcyBhZGRpbmcgcmlzayBpcyBpbmNvcnJlY3QgSU1PLg0KDQogIExlcw0K
DQoNCj4gPiBTbyB5b3UgYXJlIGFza2luZyB1cyB0byByZXBlYXQgYSBkaXNjdXNzaW9uIHdoaWNo
IGhhcyBhbHJlYWR5IGJlZW4NCj4gPiBoZWxkIGluIHRoZSBjb250ZXh0IG9mIFJGQyA1MzA0IGFu
ZCBSRkMgNTMxMC4NCj4gPg0KPiA+IEl0IHdvdWxkIGJlIG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRk
IHRoZSBub3JtYWwgcmVmZXJlbmNlIHRvIFJGQw0KPiA+IDUzMDQvNTMxMCBpbiB0aGUgU2VjdXJp
dHkgc2VjdGlvbiB0aGFuIHdoYXQgeW91IHByb3Bvc2UuDQo+IA0KPiBJIGRvbuKAmXQgdGhpbmsg
aXQgaHVydHMgdG8gYWRkIGEgcmVmZXJlbmNlIHRvIHRob3NlIFJGQ3MsIGJ1dCB0aGV5IGFyZSBi
b3RoDQo+IGFib3V0IGFkZGluZyBhdXRoZW50aWNhdGlvbiDigJMgdGhlIHByb2JsZW0gaW4gdGhp
cyBkb2N1bWVudCBpcyBleGFjZXJiYXRlZA0KPiBieSB0aGUgZmFjdCB0aGF0IHRoZXJl4oCZcyBu
byBhdXRoZW50aWNhdGlvbiBieSBkZWZhdWx0Lg0KPiANCj4gVGhlIGxvd2VyIGxheWVyIGF1dGhl
bnRpY2F0aW9uIG1lY2hhbmlzbXMgYXJlIHF1aXRlIHdlYWssIHNwZWNpYWxseQ0KPiBrbm93aW5n
IHRoYXQsIGlmIGluIGEgaG9tZSBlbnZpcm9ubWVudCwgZm9yIGV4YW1wbGUsIGl0IG1heSBiZSBy
ZWxhdGl2ZWx5DQo+IGVhc3kgdG8gY29ubmVjdCB0byB0aGUgV2lGaSBuZXR3b3JrLg0KPiANCj4g
QWx2YXJvLg0KPiANCg0K


From nobody Fri Apr  7 15:53:36 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BDB128DE7 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.144
X-Spam-Level: 
X-Spam-Status: No, score=-1.144 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, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=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 FrScHICT8AsV for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:53:24 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071092.outbound.protection.outlook.com [40.92.71.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80B0B128B93 for <ietf@ietf.org>; Fri,  7 Apr 2017 15:53:00 -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; bh=5z1Eg/NrwSuwLDhtxuQN86Epbj7/yr32JP4fQW8E7bk=; b=C1o1az4JEWQVhqPyi95UdUbuKmXqIipCfdz6TT/UOOHJ0eE0pcbVXrbgOo1tVpPl9zw+POa0CdIKI7RquyCdsxy5Bz9RQU/XFqa0MbWolpj/tfGQnQFENCGWQ+gSix6FnZ2eEVOlqxfwt1cD39BMVzI33TqhCTdzD2t6aW7+yHZqS7LPLL0xDAjaYrGxm0xcU07ZX1fasskAWZNJLeTsO02pKG2XJA15UvYP5e91pdfda+ztfIn7xBMknBHBXoc4oxmuxbBl6C6d/HhCsg9wJYC8sMBj+GlesLtnojTfqLkl7MiU2FB56P6Ko04/z05GSvOiUVE7GTVdOWfxLl+cGw==
Received: from AM5EUR03FT017.eop-EUR03.prod.protection.outlook.com (10.152.16.51) by AM5EUR03HT211.eop-EUR03.prod.protection.outlook.com (10.152.17.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Fri, 7 Apr 2017 22:52:58 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.53) by AM5EUR03FT017.mail.protection.outlook.com (10.152.16.89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Fri, 7 Apr 2017 22:52:58 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::bd5b:1ace:ba8d:6166]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::bd5b:1ace:ba8d:6166%19]) with mapi id 15.01.1005.023; Fri, 7 Apr 2017 22:52:58 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: [Int-area] IETF 98 Minutes
Thread-Topic: [Int-area] IETF 98 Minutes
Thread-Index: AQHSr+zFs09Kx+lURU6wQGRhCdNJqA==
Date: Fri, 7 Apr 2017 22:52:58 +0000
Message-ID: <AM4PR0401MB22414069AFBBD199F585B055BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAHLBt81aHb9BjDqy579mShMPcWET2nAwvd9uiM0zsnYbNLHqeg@mail.gmail.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:E8D92040BE72DBF15E8BBF893BB808FDA3B28D516E117E2F777C87006ED0385A; UpperCasedChecksum:C5AFCFA48CC91A2C5C5CDC6C6BD7564CC7CFE2C787ABFD7F0A20C4191F7781CC; SizeAsReceived:7855; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT211; 5:cfnWY/Eey4VTBnNyNT4tcz1o/pDQtSPphVhbIFPOcKTQL5K4zLspE12+JzHFKV0EK4eYGjHvQ+0DukI/34ele2XMqaCZEos9s2HjTlZnOMpMmSRnmhA7954YE7MEYg/R/ePZVozH55OqlQhPcie1qg==; 24:xNi4w17b8SNSOrocEITnfKpjl/v4Z4CYC7qgXWm6ybp0vsf07Px7yW1UFffywmND8ZYRIMR5jImh0sAKSKwNHHG4LPXO2NRMcReH9+MLgnY=; 7:NUnAsKiyVH5mvDn4W7KQBom9zmccAzCVYA0VZ1oXyXjAs8SEws7UOQLAJbVJdkwN1UINbwsx4Va/Z/SLq6McDpUA5zgXbtlLtIzFCKpDjUxAVHHY3crmdt1jW+zjEcrgLEtJyoQUW8OvxJwlAYvOGZos9q3VeDTrocNV+QDl47DJ9TRYqrz3Nj63BCnvtkRNPGuScfrAg4xIJfw6wXd/2GvNulzkWf6q+IugQNIDWLri6l/MRGeg83NPOZumn4v9yAUVx3rRLo6Agbt87IYTIBrw1i/QS4lDp+nAxvDyJGN668HTqnP99G6FC2g7KQTk
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT211; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 9de6011d-06a4-423c-9d34-08d47e08d5a9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:AM5EUR03HT211; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT211; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT211; 
x-forefront-prvs: 0270ED2845
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB22414069AFBBD199F585B055BD0C0AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2017 22:52:58.3320 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT211
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T1vFej8-mjyHmWjyf8PA85uQR8s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 22:53:26 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBbSW50
LWFyZWFdIElFVEYgOTggTWludXRlcw0KRnJvbTogS2hhbGVkIE9tYXINClRvOiBKdWFuIENhcmxv
cyBadW5pZ2EgLGludC1hcmVhQGlldGYub3JnDQpDQzogInN1cmVzaC5rcmlzaG5hbiIgLCJ3YXNz
aW0uaGFkZGFkIg0KDQoNCkhpLA0KDQo+IElQdjYgd2FzIDE5OTUgbm90IDE5OTguDQoNClRoZW4g
d2Ugc2hvdWxkIGJsYW1lIHRoZSBpZXRmIGFuZCB0aGUgSVB2NiBhdXRob3JzIGZvciB0aGUgd3Jv
bmcgaW5mb3JtYXRpb24gbGlzdGVkIGluIHRoZSBJUHY2IFJGQyAyNDYwLg0KDQpodHRwczovL3d3
dy5pZXRmLm9yZy9yZmMvcmZjMjQ2MC50eHQNCg0KQmVzdCwNCg0KS2hhbGVkIE9tYXINCg==

--_000_AM4PR0401MB22414069AFBBD199F585B055BD0C0AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <BE56FDF0E1B1FF4ABDA6B219DD6C4FBA@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gSUVURiA5
OCBNaW51dGVzPGJyPg0KRnJvbTogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWls
LmNvbT48YnI+DQpUbzogSnVhbiBDYXJsb3MgWnVuaWdhIDxqLmMuenVuaWdhQGllZWUub3JnPixp
bnQtYXJlYUBpZXRmLm9yZzxicj4NCkNDOiAmcXVvdDtzdXJlc2gua3Jpc2huYW4mcXVvdDsgPHN1
cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20+LCZxdW90O3dhc3NpbS5oYWRkYWQmcXVvdDsgPHdh
c3NpbS5oYWRkYWRAZXJpY3Nzb24uY29tPg0KPGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0
aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4
O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KSGksPGJyPg0K
PGJyPg0KJmd0OyBJUHY2IHdhcyAxOTk1IG5vdCAxOTk4Ljxicj4NCjxicj4NClRoZW4gd2Ugc2hv
dWxkIGJsYW1lIHRoZSBpZXRmIGFuZCB0aGUgSVB2NiBhdXRob3JzIGZvciB0aGUgd3JvbmcgaW5m
b3JtYXRpb24gbGlzdGVkIGluIHRoZSBJUHY2IFJGQyAyNDYwLjxicj4NCjxicj4NCmh0dHBzOi8v
d3d3LmlldGYub3JnL3JmYy9yZmMyNDYwLnR4dDxicj4NCjxicj4NCkJlc3QsPGJyPg0KPGJyPg0K
S2hhbGVkIE9tYXI8YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_AM4PR0401MB22414069AFBBD199F585B055BD0C0AM4PR0401MB2241_--


From nobody Fri Apr  7 15:54:19 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF28129496 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=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 LZi_E1_iHVjO for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 15:54:03 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-oln040092070090.outbound.protection.outlook.com [40.92.70.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3045129474 for <ietf@ietf.org>; Fri,  7 Apr 2017 15:53:43 -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; bh=Oby9xonRS+PMWEGnqj5z1xMc1bWFtSpeGhCrE9xsSSg=; b=hAJAHX3x9nLLrC33Rz832gyxo1zikwOOz0Qd2aypRfku+gb2WVG8RZgvJUkQlrvxDJOCfrO0iOv1A2P7Mfdz4CwQRxiPaQfhXYc0e0AGW5XWrE1h0OIDbpC8OoH/f8OrMBvThnDbb5lP0B6cFxI26h/bDq2DACWUEAbGX5kVV3qELm+Md0KuVK92t1DpdGJDVSo+67TStmK7KH5qRXeL81XnJAxa5359GI8dzwsdwZ0vVAgtkIc0DzvS+uG8wQBIwWP0DUtrH/DAfsuITPhKDaBdyxl5j60OECHrzfMBxdveKVCnK4A10ThKV5YFRCPB13BsiaU5bEq22EwY3xuQ0A==
Received: from AM5EUR03FT017.eop-EUR03.prod.protection.outlook.com (10.152.16.57) by AM5EUR03HT104.eop-EUR03.prod.protection.outlook.com (10.152.16.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Fri, 7 Apr 2017 22:53:41 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.53) by AM5EUR03FT017.mail.protection.outlook.com (10.152.16.89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Fri, 7 Apr 2017 22:53:42 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::bd5b:1ace:ba8d:6166]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::bd5b:1ace:ba8d:6166%19]) with mapi id 15.01.1005.023; Fri, 7 Apr 2017 22:53:41 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: [Int-area] IETF 98 Minutes
Thread-Topic: [Int-area] IETF 98 Minutes
Thread-Index: AQHSr+zFs09Kx+lURU6wQGRhCdNJqA==
Date: Fri, 7 Apr 2017 22:53:41 +0000
Message-ID: <AM4PR0401MB2241E1B2B3F831FA8931CBE2BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAHLBt81aHb9BjDqy579mShMPcWET2nAwvd9uiM0zsnYbNLHqeg@mail.gmail.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:6A376A7FDDAAFCDB8AEE776C35C155BC9DC20FE87C4C18D4E0D6915B074EB6F8; UpperCasedChecksum:42C1727C7416E52FD20DBED7CAA160FE621F4AED34069BF47D6BA1C550D4B6DA; SizeAsReceived:7791; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT104; 5:8Msabfq5mA34SClGcIZ8Mo+MuX724hLodHdhQYGFNSSH4L2gNTO6Ml51Y6R8DELKp2oiB3I4J3KLYEaOuaZRVtJeaDePidlNUhrYJP8jFxJqLqTeV+IbByJfg+ZDkS/4WA2PfyFGep0GeQu09DS2Ww==; 24:qtIJXSpzHwFun+4EOCCG5phAUC7T4DrS7G97Wv57GO9Y7tzEb0DcYsdSFASON8EP/hiduhRv/Ga7q1c4yJgQPeb53a3iELP+hl2aPBe+nDg=; 7:/G1RLx9bPFeZznS4AipjUczNzz1ShWkDeTQX4EDIXVUjnRpOhgnJ6h30BDqp+H5CgsxMEH2upBoSXAGwcZZ2AwGj8v8Le6To3gniobolV4nD0CorqiNFJqDKjw4BQnZQLBERQ3kTIsDfE5ACxk/K0ejH/8ij30Nc4TnjwPF/pfOEzuBV1ebj05RnW0l5is8M8VuHcThqz3mfPRfPVOd9CO9UOQm+z4d7eXb8ecfq745F4M+aTWPnHIbsh0MVAYWRY+aZiMihdRb0U6sTFz7u50MJZ4/AA6DIbCr71Fi5i/bIaA6sqqdSmAZbqMPB+1id
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT104; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: a7edefb8-ed15-4ae0-8663-08d47e08ef14
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:AM5EUR03HT104; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT104; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT104; 
x-forefront-prvs: 0270ED2845
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241E1B2B3F831FA8931CBE2BD0C0AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2017 22:53:41.6682 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT104
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EQb_Mp4VMunB7I8tGmGqjacODic>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 22:54:11 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBbSW50
LWFyZWFdIElFVEYgOTggTWludXRlcw0KRnJvbTogS2hhbGVkIE9tYXINClRvOiBpbnQtYXJlYQ0K
Q0M6DQoNCg0KU29tZXRoaW5nIGVsc2UgdG8gYWRkLCBpdCBpcyBub3QgbXkgcHJvYmxlbSB0aGF0
IHRoZSBleHRlbmRlZCBwaW5nIHByZXNlbnRlciBkaWRuJ3QgaGVhciBteSBxdWVzdGlvbiB3aGlj
aCBJIHJlcGVhdGVkIHR3byB0aW1lcyB0aHJvdWdoIHRoaXMgbWVldGljaG8gYW5kIGRpZG4ndCBn
ZXQgYW4gYW5zd2VyLCB3aWxsIGJlIGJldHRlciB0byBmaW5kIGEgcmVwbGFjZW1lbnQgZm9yIHRo
aXMgc2VydmljZSBmb3IgbWFraW5nIGEgc3VjY2Vzc2Z1bCByZW1vdGUgcHJlc2VudGF0aW9uIGFz
IG15IG1pY3JvcGhvbmUgd2FzIG11dGVkIHN1ZGRlbmx5IGR1cmluZyBwcmVzZW50aW5nIElQdjEw
IHNsaWRlcyBhbmQgd2FzIGVuYWJsZWQgc3VkZGVubHkgYXQgdGhlIGVuZCBvZiB0aGUgc2Vzc2lv
biBzbyBJIGdvdCBubyBjaGFuY2UgdG8gY29udGludWUgbXkgcmVtb3RlIHByZXNlbnRhdGlvbi4N
Cg0KUmVnLA0KDQpLaGFsZWQgT21hcg0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0t
LS0tLS0NClN1YmplY3Q6IFtJbnQtYXJlYV0gSUVURiA5OCBNaW51dGVzDQpGcm9tOiBKdWFuIENh
cmxvcyBadW5pZ2ENClRvOiBpbnQtYXJlYUBpZXRmLm9yZw0KQ0M6DQoNCg0KSGVsbG8sDQoNClRo
ZSBtaW51dGVzIG9mIHRoZSBJbnRBcmVhIG1lZXRpbmcgYXQgSUVURiA5OCBpbiBDaGljYWdvIGFy
ZSBoZXJlOg0KDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9taW51dGVzLTk4LWlu
dGFyZWEvDQoNClRoYW5rcyBhZ2FpbiB0byBJYW4gRmFycmVyIGZvciB0YWtpbmcgbm90ZXMgZHVy
aW5nIHRoZSBtZWV0aW5nLg0KDQpCZXN0LA0KDQpKdWFuIENhcmxvcyAmIFdhc3NpbQ0K

--_000_AM4PR0401MB2241E1B2B3F831FA8931CBE2BD0C0AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <E06B7E14A4ADE84ABC1F97B1EA0D614B@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gSUVURiA5
OCBNaW51dGVzPGJyPg0KRnJvbTogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWls
LmNvbT48YnI+DQpUbzogaW50LWFyZWEgPGludC1hcmVhQGlldGYub3JnPjxicj4NCkNDOiA8YnI+
DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1b3Rl
IiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFk
ZGluZy1sZWZ0OjFleCI+DQpTb21ldGhpbmcgZWxzZSB0byBhZGQsIGl0IGlzIG5vdCBteSBwcm9i
bGVtIHRoYXQgdGhlIGV4dGVuZGVkIHBpbmcgcHJlc2VudGVyIGRpZG4ndCBoZWFyIG15IHF1ZXN0
aW9uIHdoaWNoIEkgcmVwZWF0ZWQgdHdvIHRpbWVzIHRocm91Z2ggdGhpcyBtZWV0aWNobyBhbmQg
ZGlkbid0IGdldCBhbiBhbnN3ZXIsIHdpbGwgYmUgYmV0dGVyIHRvIGZpbmQgYSByZXBsYWNlbWVu
dCBmb3IgdGhpcyBzZXJ2aWNlIGZvciBtYWtpbmcgYSBzdWNjZXNzZnVsIHJlbW90ZQ0KIHByZXNl
bnRhdGlvbiBhcyBteSBtaWNyb3Bob25lIHdhcyBtdXRlZCBzdWRkZW5seSBkdXJpbmcgcHJlc2Vu
dGluZyBJUHYxMCBzbGlkZXMgYW5kIHdhcyBlbmFibGVkIHN1ZGRlbmx5IGF0IHRoZSBlbmQgb2Yg
dGhlIHNlc3Npb24gc28gSSBnb3Qgbm8gY2hhbmNlIHRvIGNvbnRpbnVlIG15IHJlbW90ZSBwcmVz
ZW50YXRpb24uPGJyPg0KPGJyPg0KUmVnLDxicj4NCjxicj4NCktoYWxlZCBPbWFyDQo8ZGl2IGNs
YXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0t
IE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBbSW50LWFyZWFdIElFVEYg
OTggTWludXRlczxicj4NCkZyb206IEp1YW4gQ2FybG9zIFp1bmlnYSA8ai5jLnp1bmlnYUBpZWVl
Lm9yZz48YnI+DQpUbzogaW50LWFyZWFAaWV0Zi5vcmc8YnI+DQpDQzogPGJyPg0KPGJyPg0KPGJy
IHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1h
cmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDox
ZXgiPg0KPGRpdiBkaXI9Imx0ciI+SGVsbG8sDQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGUg
bWludXRlcyBvZiB0aGUgSW50QXJlYSBtZWV0aW5nIGF0IElFVEYgOTggaW4gQ2hpY2FnbyBhcmUg
aGVyZTo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxhIGhyZWY9Imh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL21pbnV0ZXMtOTgtaW50YXJlYS8iPmh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL21pbnV0ZXMtOTgtaW50YXJlYS88L2E+PGJyPg0KPC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGFua3MgYWdhaW4gdG8gSWFuIEZhcnJlciBmb3IgdGFr
aW5nIG5vdGVzIGR1cmluZyB0aGUgbWVldGluZy48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2PkJlc3QsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5KdWFuIENhcmxvcyAmYW1w
OyBXYXNzaW08L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB2241E1B2B3F831FA8931CBE2BD0C0AM4PR0401MB2241_--


From nobody Fri Apr  7 19:57:25 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76653129353 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 19:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 aWzUAnnPH5cq for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 19:57:22 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-oln040092067064.outbound.protection.outlook.com [40.92.67.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F269C1292F4 for <ietf@ietf.org>; Fri,  7 Apr 2017 19:57:19 -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; bh=h/ZsZ2aNps871dEB/ri7O+xp0EXYxmQd3bNUghh79UY=; b=dWown/4xsnQzXGUyUJFFY3IGxl7EJUDd1qUuLk3Kw0MukGs1/6jHG0O/wsC/PR7aDI2t4Iy1xNfGI7zeQXBH0NVT1WBTieunSpdFBu2ffH5NTS3SBLghbsJlAqJQKCaCPAzXSJzSPuF+wgy5lufS6BAIV1Brtrbh45AO2ydb8gveWiip0g7XypXk/7EsoDc6xvNBAXUxwG+UglZSXlxkOT5DmGRXxg7ib3ufso6Nrur6mWhpEng2nZGcNid91JUgP0lk09pgLyTIlmBNiRE17VUC/NyMZJQPURGdj0eOgtqPEs+Jb/niRxBJHxxJKUgKdZRUNWY2Cem3h+YZ5DykBA==
Received: from HE1EUR02FT040.eop-EUR02.prod.protection.outlook.com (10.152.10.56) by HE1EUR02HT178.eop-EUR02.prod.protection.outlook.com (10.152.10.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1005.5; Sat, 8 Apr 2017 02:57:16 +0000
Received: from DB6PR0401MB2248.eurprd04.prod.outlook.com (10.152.10.51) by HE1EUR02FT040.mail.protection.outlook.com (10.152.11.92) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.5 via Frontend Transport; Sat, 8 Apr 2017 02:57:16 +0000
Received: from DB6PR0401MB2248.eurprd04.prod.outlook.com ([10.168.54.26]) by DB6PR0401MB2248.eurprd04.prod.outlook.com ([10.168.54.26]) with mapi id 15.01.1005.023; Sat, 8 Apr 2017 02:57:16 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: Fw: [Int-area] IETF 98 Minutes
Thread-Topic: Fw: [Int-area] IETF 98 Minutes
Thread-Index: AQHSr+zFs09Kx+lURU6wQGRhCdNJqA==
Date: Sat, 8 Apr 2017 02:57:16 +0000
Message-ID: <DB6PR0401MB224870CFC1D305AC777E4DBEBD0F0@DB6PR0401MB2248.eurprd04.prod.outlook.com>
References: <CACweHNCKRQDN7P1QRL6HqwE_vwo6+QCJo0toskdAod8oxPyLhA@mail.gmail.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:6A308FA101CEC9DC2AF0E3D39CCF2FB7F956A7AC3FEE0B317A807E4228F42CBA; UpperCasedChecksum:C48065D6CCF15B8BB93569107975CF06D14922BB382B51454B6BB36D3A4FFF33; SizeAsReceived:7753; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT178; 5:zhddw1Wz3bdYuccos9Don21y012Dd08BJorzKQ5JocbSKQgBnuawsGwtwg6zqDRsvS472XjKWYlsVYQjGIVAL8y2eag3fw7K90vNRaLukkZCTRhbXdMXDavtuJ2C7ptbGtqOZXNWeqe+cp/ovi6Cag==; 24:CBJz3HQCi/2wVVQf/k3ihPLc24C/Cmc+4jaE/2itOFpNGGVITMTE1o3WakYh2IpPBiyY6jMClQZxSA6IM5au+2rmDMreHn9ekm7xdWQcZ1Y=; 7:axuk30QvmHmjAaVU/8RBBynjBwKiNtBvEx9PjzVGujD2+eRCmPn90kFqZcANMFHKZNLjHyxmWbJCDcQlL05s6C/t0YWbZXosog510JLZJlWI1p8LDBm4z0KWKywx2LLbdcVLbgtg/iq1mIXGEn2Qv3ZYelBg8bVJ1Ui/fyLwSc/wEtpXV4DKeDWdtEHRwfUBvRo/qx4T3opaoKcquG/O7D1wXYSO6NtYdOM37aiBlQNSTGhne2sDWdVFbwpg6ew0gTVFsb+MtFJY2PIV1EC0td3x4wvAWEwgqC3IBbirBkso6W28z7wtSbqZ6OKPHVG2
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT178; H:DB6PR0401MB2248.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 556fb225-64c5-4b41-0c2a-08d47e2af63c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR02HT178; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR02HT178; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT178; 
x-forefront-prvs: 0271483E06
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB6PR0401MB224870CFC1D305AC777E4DBEBD0F0DB6PR0401MB2248_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2017 02:57:16.6342 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT178
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TT9219y4oM7DzJO19gFSNCYHJN8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 02:57:24 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBGdzog
W0ludC1hcmVhXSBJRVRGIDk4IE1pbnV0ZXMNCkZyb206IEtoYWxlZCBPbWFyDQpUbzogTWF0dGhl
dyBLZXJ3aW4NCkNDOiBpbnQtYXJlYQ0KDQoNCk9rLCBzbyByZWdhcmRsZXNzIGl0IHdhcyBwdWJs
aXNoZWQgaW4gIjE5OTgiIG9yIDE5OTUsIHRoZSBtaWdyYXRpb24gcHJvY2VzcyB0b29rIHNvIG11
Y2ggdGltZSBzaW5jZSB0aGVzZSBkYXRlcyB3aXRob3V0IGZ1bGwgbWlncmF0aW9uIHRpbGwgbm93
LCB0aGlzIGlzIHdoYXQgd2Ugc2hvdWxkIHRoaW5rIGFib3V0LCB0aGUgbG9uZyBvciBsb25nZXIg
dGltZSwgaXQgaXMgbm90IGEgaGlzdG9yeSBjbGFzcywgYW5kIEkgaGFkIG9ubHkgNSBtaW51dGVz
IGZvciB0aGUgd2hvbGUgSVB2MTAgcHJlc2VudGF0aW9uLg0KDQpBbnl3YXksIHRoZSBpbnRlcnJ1
cHRpb24gbWFkZSBmb3IgdGhpcyBtb2RpZmljYXRpb24gZ2l2ZXMgYSBiYWQgaW1wcmVzc2lvbiBh
Ym91dCB0aGUgbGV2ZWwgb2YgZGlzY3Vzc2lvbiBtYWRlIGF0IHRoaXMgaWV0ZiBtZWV0aW5nIGJ5
IHBhcnRpY2lwYW50cy4NCg0KVGhhbmtzIGZvciB0aGUgY29yZSBkaXNjdXNzaW9uLg0KDQpLSEFM
RUQgT01BUg0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6
IFJlOiBGdzogW0ludC1hcmVhXSBJRVRGIDk4IE1pbnV0ZXMNCkZyb206IE1hdHRoZXcgS2Vyd2lu
DQpUbzogS2hhbGVkIE9tYXINCkNDOg0KDQoNClJGQyAyNDYwIHdhcyBwdWJsaXNoZWQgaW4gMTk5
OC4NCg0KSXQgb2Jzb2xldGVkIFJGQyAxODgzLCB3aGljaCB3YXMgcHVibGlzaGVkIGluIDE5OTUu
DQoNClRoYXQgaW5mb3JtYXRpb24gaXMgYXZhaWxhYmxlIGluIHRoZSBkb2N1bWVudCBoZWFkZXIs
IGFuZCBpbiB0aGUgbWV0YWRhdGEgdGhhdCBjYW4gYmUgcXVlcmllZCBmcm9tIHRoZSBJRVRGIHRv
b2xzLg0KDQpPbiA4IEFwcmlsIDIwMTcgYXQgMDg6NTIsIEtoYWxlZCBPbWFyIDxlbmcua2hhbGVk
Lm9tYXJAaG90bWFpbC5jb208bWFpbHRvOmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4+IHdy
b3RlOg0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJl
OiBbSW50LWFyZWFdIElFVEYgOTggTWludXRlcw0KRnJvbTogS2hhbGVkIE9tYXINClRvOiBKdWFu
IENhcmxvcyBadW5pZ2EgLGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBpZXRmLm9y
Zz4NCkNDOiAic3VyZXNoLmtyaXNobmFuIiAsIndhc3NpbS5oYWRkYWQiDQoNCg0KSGksDQoNCj4g
SVB2NiB3YXMgMTk5NSBub3QgMTk5OC4NCg0KVGhlbiB3ZSBzaG91bGQgYmxhbWUgdGhlIGlldGYg
YW5kIHRoZSBJUHY2IGF1dGhvcnMgZm9yIHRoZSB3cm9uZyBpbmZvcm1hdGlvbiBsaXN0ZWQgaW4g
dGhlIElQdjYgUkZDIDI0NjAuDQoNCmh0dHBzOi8vd3d3LmlldGYub3JnL3JmYy9yZmMyNDYwLnR4
dA0KDQpCZXN0LA0KDQpLaGFsZWQgT21hcg0KDQoNCg0KLS0NCiAgTWF0dGhldyBLZXJ3aW4NCiAg
aHR0cDovL21hdHRoZXcua2Vyd2luLm5ldC5hdS8NCg==

--_000_DB6PR0401MB224870CFC1D305AC777E4DBEBD0F0DB6PR0401MB2248_
Content-Type: text/html; charset="utf-8"
Content-ID: <C2DD040D0AEC3F478F9B95047108B326@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEZ3OiBbSW50LWFyZWFdIElF
VEYgOTggTWludXRlczxicj4NCkZyb206IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90
bWFpbC5jb20+PGJyPg0KVG86IE1hdHRoZXcgS2Vyd2luIDxtYXR0aGV3QGtlcndpbi5uZXQuYXU+
PGJyPg0KQ0M6IGludC1hcmVhIDxpbnQtYXJlYUBpZXRmLm9yZz48YnI+DQo8YnI+DQo8YnIgdHlw
ZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2lu
OjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+
DQpPaywgc28gcmVnYXJkbGVzcyBpdCB3YXMgcHVibGlzaGVkIGluICZxdW90OzE5OTgmcXVvdDsg
b3IgMTk5NSwgdGhlIG1pZ3JhdGlvbiBwcm9jZXNzIHRvb2sgc28gbXVjaCB0aW1lIHNpbmNlIHRo
ZXNlIGRhdGVzIHdpdGhvdXQgZnVsbCBtaWdyYXRpb24gdGlsbCBub3csIHRoaXMgaXMgd2hhdCB3
ZSBzaG91bGQgdGhpbmsgYWJvdXQsIHRoZSBsb25nIG9yIGxvbmdlciB0aW1lLCBpdCBpcyBub3Qg
YSBoaXN0b3J5IGNsYXNzLCBhbmQgSSBoYWQgb25seSA1IG1pbnV0ZXMNCiBmb3IgdGhlIHdob2xl
IElQdjEwIHByZXNlbnRhdGlvbi48YnI+DQo8YnI+DQpBbnl3YXksIHRoZSBpbnRlcnJ1cHRpb24g
bWFkZSBmb3IgdGhpcyBtb2RpZmljYXRpb24gZ2l2ZXMgYSBiYWQgaW1wcmVzc2lvbiBhYm91dCB0
aGUgbGV2ZWwgb2YgZGlzY3Vzc2lvbiBtYWRlIGF0IHRoaXMgaWV0ZiBtZWV0aW5nIGJ5IHBhcnRp
Y2lwYW50cy48YnI+DQo8YnI+DQpUaGFua3MgZm9yIHRoZSBjb3JlIGRpc2N1c3Npb24uPGJyPg0K
PGJyPg0KS0hBTEVEIE9NQVI8YnI+DQo8ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVp
Z2h0OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08
YnI+DQpTdWJqZWN0OiBSZTogRnc6IFtJbnQtYXJlYV0gSUVURiA5OCBNaW51dGVzPGJyPg0KRnJv
bTogTWF0dGhldyBLZXJ3aW4gPG1hdHRoZXdAa2Vyd2luLm5ldC5hdT48YnI+DQpUbzogS2hhbGVk
IE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpDQzogPGJyPg0KPGJyPg0K
PGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9
Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVm
dDoxZXgiPg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHls
ZT0iZm9udC1mYW1pbHk6Z2VvcmdpYSxzZXJpZjtjb2xvcjojMDczNzYzIj5SRkMgMjQ2MCB3YXMg
cHVibGlzaGVkIGluIDE5OTguPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHls
ZT0iZm9udC1mYW1pbHk6Z2VvcmdpYSxzZXJpZjtjb2xvcjojMDczNzYzIj48YnI+DQo8L2Rpdj4N
CjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTpnZW9yZ2lhLHNl
cmlmO2NvbG9yOiMwNzM3NjMiPkl0IG9ic29sZXRlZCBSRkMgMTg4Mywgd2hpY2ggd2FzIHB1Ymxp
c2hlZCBpbiAxOTk1LjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZv
bnQtZmFtaWx5Omdlb3JnaWEsc2VyaWY7Y29sb3I6IzA3Mzc2MyI+PGJyPg0KPC9kaXY+DQo8ZGl2
IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6Z2VvcmdpYSxzZXJpZjtj
b2xvcjojMDczNzYzIj5UaGF0IGluZm9ybWF0aW9uIGlzIGF2YWlsYWJsZSBpbiB0aGUgZG9jdW1l
bnQgaGVhZGVyLCBhbmQgaW4gdGhlIG1ldGFkYXRhIHRoYXQgY2FuIGJlIHF1ZXJpZWQgZnJvbSB0
aGUgSUVURiB0b29scy48L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxi
cj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiA4IEFwcmlsIDIwMTcgYXQgMDg6NTIsIEto
YWxlZCBPbWFyIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmVuZy5raGFsZWQu
b21hckBob3RtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmVuZy5raGFsZWQub21hckBob3RtYWls
LmNvbTwvYT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxf
cXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xp
ZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXY+DQo8ZGl2IGNsYXNzPSJtXy0xOTA4MjcxOTYxNDUw
MzA5OTY1cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDoxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0t
IE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogW0ludC1hcmVhXSBJ
RVRGIDk4IE1pbnV0ZXM8YnI+DQpGcm9tOiBLaGFsZWQgT21hciA8dT48L3U+PGJyPg0KVG86IEp1
YW4gQ2FybG9zIFp1bmlnYSA8dT48L3U+LDxhIGhyZWY9Im1haWx0bzppbnQtYXJlYUBpZXRmLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPmludC1hcmVhQGlldGYub3JnPC9hPjxicj4NCkNDOiAmcXVvdDtz
dXJlc2gua3Jpc2huYW4mcXVvdDsgPHU+PC91PiwmcXVvdDt3YXNzaW0uaGFkZGFkJnF1b3Q7IDx1
PjwvdT48YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xh
c3M9Im1fLTE5MDgyNzE5NjE0NTAzMDk5NjVxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4
O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KSGksPGJyPg0K
PGJyPg0KJmd0OyBJUHY2IHdhcyAxOTk1IG5vdCAxOTk4Ljxicj4NCjxicj4NClRoZW4gd2Ugc2hv
dWxkIGJsYW1lIHRoZSBpZXRmIGFuZCB0aGUgSVB2NiBhdXRob3JzIGZvciB0aGUgd3JvbmcgaW5m
b3JtYXRpb24gbGlzdGVkIGluIHRoZSBJUHY2IFJGQyAyNDYwLjxicj4NCjxicj4NCjxhIGhyZWY9
Imh0dHBzOi8vd3d3LmlldGYub3JnL3JmYy9yZmMyNDYwLnR4dCIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vd3d3LmlldGYub3JnL3JmYy88d2JyPnJmYzI0NjAudHh0PC9hPjxicj4NCjxicj4NCkJl
c3QsPGJyPg0KPGJyPg0KS2hhbGVkIE9tYXI8YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnI+DQo8YnIgY2xlYXI9ImFsbCI+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KLS0gPGJyPg0KPGRpdiBjbGFzcz0iZ21haWxfc2lnbmF0dXJlIiBkYXRh
LXNtYXJ0bWFpbD0iZ21haWxfc2lnbmF0dXJlIj4NCjxkaXYgZGlyPSJsdHIiPiZuYnNwOyBNYXR0
aGV3IEtlcndpbjxicj4NCiZuYnNwOyA8YSBocmVmPSJodHRwOi8vbWF0dGhldy5rZXJ3aW4ubmV0
LmF1LyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9tYXR0aGV3Lmtlcndpbi5uZXQuYXUvPC9hPjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_DB6PR0401MB224870CFC1D305AC777E4DBEBD0F0DB6PR0401MB2248_--


From nobody Fri Apr  7 21:08:07 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8244129413 for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 21:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 TqocsJMh4yId for <ietf@ietfa.amsl.com>; Fri,  7 Apr 2017 21:08:03 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C758A12778E for <ietf@ietf.org>; Fri,  7 Apr 2017 21:08:03 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cwhfM-0001CO-Et; Sat, 08 Apr 2017 04:08:00 +0000
Date: Fri, 07 Apr 2017 21:07:59 -0700
Message-ID: <m2shljpmn4.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: ietf <ietf@ietf.org>
Subject: Re: Fw: [Int-area] IETF 98 Minutes
In-Reply-To: <AM4PR0401MB22414069AFBBD199F585B055BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAHLBt81aHb9BjDqy579mShMPcWET2nAwvd9uiM0zsnYbNLHqeg@mail.gmail.com> <AM4PR0401MB22414069AFBBD199F585B055BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8RshskIalWg0ZZZKkZE5kJ6XNJ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 04:08:06 -0000

>> IPv6 was 1995 not 1998.
> 
> Then we should blame the ietf and the IPv6 authors for the wrong
> information listed in the IPv6 RFC 2460.
> 
> https://www.ietf.org/rfc/rfc2460.txt

if it is indeed erronious, we would call it an "erratum" not "blame."

randy


From nobody Sat Apr  8 15:55:52 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5A912714F; Sat,  8 Apr 2017 15:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.623
X-Spam-Level: 
X-Spam-Status: No, score=-12.623 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 cXtyUZw2JLQz; Sat,  8 Apr 2017 15:55:40 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98F6F1250B8; Sat,  8 Apr 2017 15:55:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2806; q=dns/txt; s=iport; t=1491692140; x=1492901740; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zkVtu0DpB2Azi2hOQXUF+XPu8DkbyNAYSk2OO6g01JI=; b=e2S1wqGEecRZhBbvHwIf0oWaumhFFzA91H4dQs4rGQwESOPZ62Qms7w4 c8iZlU5/GiTXxY+XfEDVjHWbGmPQpeksgIvleBU6UDnlfFkqt+I7bp6HA SzJXzf8Q8SHffB0mJwXUsNXHxscCPPs+QETtu7qWpyCwbR5+cPf+9+Mz3 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAQCfaelY/4ENJK1CGhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNTYYELB41ykUCVV4IPLIV4AoNePxgBAgEBAQEBAQFrKIUWAQQ?= =?us-ascii?q?BeQULAgEIFDIyJQIEAQ0FCYl+CA4xqW+KXAEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?R2LQIJwgUIkhWUFkCuFdYZbAYZ/i1mBf4UuihSKNYlKAR84gQVbFYUdG4FjdQG?= =?us-ascii?q?Gb4EwgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,174,1488844800"; d="scan'208";a="409393167"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Apr 2017 22:55:39 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v38MtdX4015015 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 8 Apr 2017 22:55:39 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 8 Apr 2017 18:55:35 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Sat, 8 Apr 2017 18:55:36 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
Thread-Topic: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
Thread-Index: AQHSr8ihxBldHKjCb0K6BYj9/alinKG8FuQA
Date: Sat, 8 Apr 2017 22:55:35 +0000
Message-ID: <D50ED999.A7F47%acee@cisco.com>
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
In-Reply-To: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F3C8E32FD63BFD4A9794F21646ED72BA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lvakcGUY18t31u2YLT1IzksPGJA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 22:55:43 -0000

Hi Matt,

Thanks for the review.

On 4/7/17, 1:58 PM, "Matthew Miller" <linuxwolf+ietf@outer-planes.net>
wrote:

>Reviewer: Matthew Miller
>Review result: Almost Ready
>
>I am the assigned Gen-ART reviewer for this draft. The General Area
>Review Team (Gen-ART) reviews all IETF documents being processed
>by the IESG for the IETF Chair.  Please treat these comments just
>like any other last call comments.
>
>For more information, please see the FAQ at
>
><https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
>Document: draft-ietf-rtgwg-yang-key-chain-17
>Reviewer: Matthew A. Miller
>Review Date: 2017-04-07
>IETF LC End Date: 2017-04-07
>IESG Telechat date: 2017-04-13
>
>Summary:
>
>This document is almost ready to be published as a Proposed Standard,
>once the issues noted herein are resolved.
>
>Major issues:
>
>NONE
>
>Minor issues:
>
>* Forgive me for my limited knowledge of YANG, but is there a reason
>key-strings are only representable as either a YANG string or
>hex-string type, and not the YANG binary type?

Let me ask why I=B9d want to use this type? I can get all the entropy I wan=
t
with a hex string and implementations are familiar with this
representation. I=B9m not really fond of the obscure base64 representation
used by the YANG type and if one consults Benoit=B9s search tool, the type
is not widely used. http://www.yangcatalog.org/yang-search/yang-search.php

>
>* This document does not provide much guidance around AES key wrap
>other than it can be used and the KEK is provided
>out-of-band/-context.
>For instance, AES key-wrapped key-strings probably require using
>"hexidecimal-string".

Yes - I=B9ll add that.

>  Also, assuming I'm reading the model
>correctly,
>it appears this feature applies to the whole chain, which I think is
>worth calling out.

In YANG, if you support a feature, it is for the entire model.
The per-chain boolean indicates whether or not it is applies to all the
keys in that particular key-chain. I will clarify this.
>
>* This document warns against using the "clear-text" algorithm, which
>the
>reader is lead to understand is for legacy implementation reasons.
>However, is there not a similar concern with cryptographically weak
>algorithms, such as md5 and (arguably) sha1?

I can add something for MD5.
>
>Nits/editorial comments:
>
>* In Section 3.2. "Key Chain Model Features", the word "of" is
>missing
>between "configuration" and "an" in the phrase "support configuration
>an
>acceptance tolerance".

Good catch. I will fix.
>
>Non-nits:
>
>* I note that idnits is calling out some odd spacing issues, but I
>think
>they are safe to ignore.

Though the line numbers don=B9t match the draft, I was able to fix these.

Thanks,
Acee=20
>


From nobody Sat Apr  8 16:23:15 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF787127A90; Sat,  8 Apr 2017 16:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.623
X-Spam-Level: 
X-Spam-Status: No, score=-12.623 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 4UVmHQAUUMVV; Sat,  8 Apr 2017 16:23:06 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7DDC12420B; Sat,  8 Apr 2017 16:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5408; q=dns/txt; s=iport; t=1491693785; x=1492903385; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8FK1GC9Lg27AK7zkXUbx56DPCoNvG7sqneG5+zvCszM=; b=BXdUYocZTmRG5YcrPkQ8Iu2kl5Pai5GeOvnIN1Enl/bAgMtlPmd4Id7W 2x0bw81tBSd8FnH9nCi+dkY0blQ17rOZuv64UZe4Y1ulCZMaerx/JkOo6 u2lYTqrs6dszRxcwPKb/u5Ob2mmoGUfLmwc76GqLKSn67jUuAcdeDBtrf 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AVAQBxcOlY/4ENJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHjXKRQJVXgg8shXgCg14/GAECAQEBAQEBAWsohRUBAQE?= =?us-ascii?q?BAgE6PwUHBAIBCBEDAQEBHwkHMhQJCAEBBAENBQiJfwgOqgWKXAEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAR2GUIRwhB2GHgEEiSqMdoZbAYZ/gyuIJYIIVYRZihSIY4s?= =?us-ascii?q?cAR84gQVbFUGEWxyBY3UBiB+BDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,175,1488844800"; d="scan'208";a="407745201"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Apr 2017 23:23:04 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v38NN4va029812 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 8 Apr 2017 23:23:04 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 8 Apr 2017 18:23:04 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Sat, 8 Apr 2017 18:23:03 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Orit Levin <oritl@microsoft.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqg
Date: Sat, 8 Apr 2017 23:23:03 +0000
Message-ID: <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com>
In-Reply-To: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.67.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zVVrU7J7T_i9F3gtQVHZw5CeZVE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 23:23:08 -0000

Orit -

Thanx for the review.
Responses inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 06, 2017 8:27 PM
> To: gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-isis-mi-bis-02
> Reviewer: Orit Levin
> Review Date: 2017-04-06
> IETF LC End Date: 2017-04-07
> IESG Telechat date: 2017-04-13
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> 1. Add text explaining the reason (or reasons) for replacing the original=
 RFC
> 6822 from 2012.
> Reason: It is a "bis" draft and there is no mention about it in the text.

[Les:] Note that the latest revision of the draft correctly identifies the =
draft as obsoleting RFC 6822. Previous versions had incorrectly identified =
this as an update to RFC 6822.
This is then the new Standard for the IS-IS MI support.

There are two classes of future readers of this document:

a)Readers who are unfamiliar with RFC 6822. For them what changed between R=
FC 6822 and this document is irrelevant.=20

b)Readers who are familiar with RFC 6822. For them it is useful to know wha=
t changed - which is described in Appendix A.

In order not to distract readers of type "a" - as well as to provide an "un=
interrupted" description of the normative behavior I believe placement of t=
he change description in an Appendix improves the readability of the docume=
nt.

Does this make sense to you?

> 2. In Abstract, state clearly that this standard introduces the support f=
or
> instances vs. other already existing concepts also listed in the Abstract=
 (i.e.,
> circuits, adjacencies,  topologies, etc.).

[Les:] The Abstract currently says:

"This draft describes a mechanism that allows a single router to share
   one or more circuits among multiple Intermediate System To
   Intermediate System (IS-IS) routing protocol instances."

Previous to this extension, a router could have multiple instances of the I=
S-IS protocol, but multiple instance could not be run over the same interfa=
ce.=20
So we are not introducing "instances", but we are introducing the ability t=
o enable multiple instances on the same interface.

> Reason: The wording is not clear about what is the new feature vs. what a=
re
> the new benefits vs. what was the original baseline=20

>3. Throughout the
> document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are use=
d
> interchangeably throughout the document. It seems that they all refer to =
the
> same thing - the implementation of the original protocol without the conc=
ept
> of instances. Please, correct me if I am wrong.

[Les:]  I don't think this is possible without seriously compromising the d=
ocument. For example:

Section 2.1

" IID #0 is reserved for the standard instance supported by legacy
   systems. "

Changing this to  " Standard instance is reserved for the standard instance=
 ..."

Is clearly nonsensical.

Later in Section 2.1

"When the IID =3D 0, the list of supported ITIDs MUST NOT be present."

What is being discussed here is what is the correct behavior when an MI-cap=
able router sends a PDU associated IID #0 and includes the new IID TLV.=20
Replacing this with "When the standard instance..." loses the important poi=
nt that the value of the IID in the IID TLV in this case is "0".

Hope this helps clarify things.

> 4. In section 2 par 3, change "support" and "operates" to "MUST support" =
to
> use requirements language.

[Les:] I am on the fence as regards this change. Section 2 is an introducti=
on to the following sub-sections - which define the normative behavior. But=
 the introduction itself is not defining normative behavior - it is providi=
ng a context in which the protocol extensions defined in the following sub-=
sections can be understood.=20

I am more inclined to change the "MAY" used later in the same paragraph you=
 mention to "may" so it is consistent with the rest of this section.

???


> 5. In section 2 par 2, change "may" to either "can" or "MAY" to clarify t=
he
> intent.

[Les:] Did you mean Section 2.1 para 2?
If so I agree to the change.

> 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the=
 wire.

[Les:] There are numerous places in the document where the legal use of IID=
  #0 is discussed. I do not understand how a reader would conclude that IID=
 #0 is never sent on the wire.

> Explain the concept of the "standard interface" (see previous comment)

[Les:] There is no mention of "standard interface" - did you mean "standard=
 instance"?

If so, Section 1 paragraph 4 states:

"Legacy routers support the standard
   or zero instance of the protocol."

   Les


From nobody Sat Apr  8 20:53:19 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E798B128DE7; Sat,  8 Apr 2017 20:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level: 
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, 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 xcxBljahfKUU; Sat,  8 Apr 2017 20:53:16 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E112B126E3A; Sat,  8 Apr 2017 20:53:15 -0700 (PDT)
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2A03A29C9DC; Sun,  9 Apr 2017 12:53:13 +0900 (JST)
Received: by mail-oi0-f43.google.com with SMTP id l63so12047633oig.2; Sat, 08 Apr 2017 20:53:13 -0700 (PDT)
X-Gm-Message-State: AFeK/H2OnXmfqg2iRi8GkVofIn8CGqBPchEFjaGPCVLn+FBG2EFFtIbxtdm04TXPDmgJtSRRehr7j+cKhXazPw==
X-Received: by 10.202.97.6 with SMTP id v6mr11468290oib.214.1491709991791; Sat, 08 Apr 2017 20:53:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.38.132 with HTTP; Sat, 8 Apr 2017 20:53:11 -0700 (PDT)
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Sat, 8 Apr 2017 20:53:11 -0700
X-Gmail-Original-Message-ID: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
Message-ID: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
Subject: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: tsv-art@ietf.org
Cc: draft-ietf-core-coap-tcp-tls@ietf.org, core@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a113d4fee2b36e8054cb3ccb5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q95NELltcBUBCoCRE50KHtv2yHQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Apr 2017 03:53:18 -0000

--001a113d4fee2b36e8054cb3ccb5
Content-Type: text/plain; charset=UTF-8

Document: draft-ietf-core-coap-tcp-tls-07
Reviewer: Yoshifumi Nishida

I've reviewed this document as part of TSV-ART's ongoing effort to review
key IETF documents. These comments were written primarily for the transport
area directors, but are copied to the document's authors for their
information and to allow them to address any issues raised.When done at the
time of IETF Last Call, the authors should consider this review together
with any other last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Summary: This document is well-written. It is almost ready to be published
as a PS draft once the following points are addressed.

1: It is not clear how the protocol reacts the errors from transport layers
(e.g. connection failure).
   The protocol will just inform apps of the events and the app will decide
what to do or the protocol itself will do something?

2: There will be situations where the app layer is freezing while the
transport layer is still working. Since transport layers cannot detect this
type of failures, there should be some mechanisms for it somewhere in the
protocol or in the app layer.  The doc needs to address this point. For
example, what will happen when a PONG message is not returned for a certain
amount of time?

3: Since this draft defines new SZX value, I think the doc needs to update
RFC7959. This point should be clarified more in the doc.

--
Yoshi

--001a113d4fee2b36e8054cb3ccb5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-family:arial,helvetica,sans-serif=
">Document: draft-ietf-core-coap-tcp-tls-0</span><wbr style=3D"font-family:=
arial,helvetica,sans-serif"><span style=3D"font-family:arial,helvetica,sans=
-serif">7</span><br style=3D"font-family:arial,helvetica,sans-serif"><span =
style=3D"font-family:arial,helvetica,sans-serif">Reviewer: Yoshifumi Nishid=
a</span><font face=3D"arial, helvetica, sans-serif"><br></font></div><div><=
br></div><div><font face=3D"arial, helvetica, sans-serif">I&#39;ve reviewed=
 this document as part of TSV-ART&#39;s ongoing effort to review key IETF d=
ocuments. These comments were written primarily for the transport area dire=
ctors, but are copied to the document&#39;s authors for their information a=
nd to allow them to address any issues raised.When done at the time of IETF=
 Last Call, the authors should consider this review together with any other=
 last-call comments they receive. Please always CC=C2=A0<a href=3D"mailto:t=
sv-art@ietf.org" target=3D"_blank">tsv-art@ietf.org</a>=C2=A0if you reply t=
o or forward this review.<br></font></div><font face=3D"arial, helvetica, s=
ans-serif"><div><br></div></font><div><div><font face=3D"arial, helvetica, =
sans-serif">Summary:=C2=A0This document is well-written. It is almost ready=
 to be published as a PS draft once=C2=A0the following points are addressed=
.</font></div></div><div><font face=3D"arial, helvetica, sans-serif"><br></=
font></div><div><font face=3D"arial, helvetica, sans-serif">1: It is not cl=
ear how the protocol reacts the errors from transport layers (e.g. connecti=
on failure).</font></div><div><font face=3D"arial, helvetica, sans-serif">=
=C2=A0 =C2=A0The protocol will just inform apps of the events and the app w=
ill decide what to do or the protocol itself will do something?</font></div=
><div><font face=3D"arial, helvetica, sans-serif"><br></font></div><div><fo=
nt face=3D"arial, helvetica, sans-serif">2: There will be situations where =
the app layer is freezing while the transport layer is still working. Since=
 transport layers cannot detect this type of failures, there should be some=
 mechanisms for it somewhere in the protocol or in the app layer.=C2=A0 The=
 doc needs to address this point. For example, what will happen when a PONG=
 message is not returned for a certain amount of time?</font></div><div><fo=
nt face=3D"arial, helvetica, sans-serif">=C2=A0</font></div><div><font face=
=3D"arial, helvetica, sans-serif">3: Since this draft defines new SZX value=
, I think the doc needs to update RFC7959. This point should be clarified m=
ore in the doc.</font></div><div><font face=3D"arial, helvetica, sans-serif=
"><br></font></div><div><font face=3D"arial, helvetica, sans-serif">--</fon=
t></div><div><font face=3D"arial, helvetica, sans-serif">Yoshi</font></div>=
</div>

--001a113d4fee2b36e8054cb3ccb5--


From nobody Sat Apr  8 22:57:12 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCB5129417; Sat,  8 Apr 2017 22:57:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
Subject: Genart telechat review of draft-ietf-bess-evpn-vpws-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149171742319.3063.4555090995663652452@ietfa.amsl.com>
Date: Sat, 08 Apr 2017 22:57:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/egcbf4eYh-Df9F3qd6lHn9ykGh8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Apr 2017 05:57:03 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bess-evpn-vpws-??
Reviewer: Roni Even
Review Date: 2017-04-08
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-13

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

In section 1 second paragraph "[RFC7432] provides the ability " looks
like the reference is not a link to RFC7432.




From nobody Sun Apr  9 00:25:29 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD89A129456; Sun,  9 Apr 2017 00:25:27 -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 Or48n5sLs9Ea; Sun,  9 Apr 2017 00:25:26 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 83D3B129329; Sun,  9 Apr 2017 00:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v397PMHT000531; Sun, 9 Apr 2017 09:25:22 +0200 (CEST)
Received: from client-0060.vpn.uni-bremen.de (client-0060.vpn.uni-bremen.de [134.102.107.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w14bQ1yhBzDHdT; Sun,  9 Apr 2017 09:25:22 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
Date: Sun, 9 Apr 2017 09:25:21 +0200
Cc: tsv-art@ietf.org, draft-ietf-core-coap-tcp-tls@ietf.org, core@ietf.org, ietf@ietf.org
X-Mao-Original-Outgoing-Id: 513415521.674309-e6e2b439554923e512814b6ee2040d7e
Content-Transfer-Encoding: quoted-printable
Message-Id: <F715AB89-D9FA-414E-83F5-E29F0BBB0904@tzi.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G5xyB42vs73aRCg4gf-hi93sXFY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Apr 2017 07:25:28 -0000

Hi Yoshi,

thank you very much for your thoughtful review.

For now, let me pick one of your comments:

> 3: Since this draft defines new SZX value, I think the doc needs to =
update RFC7959. This point should be clarified more in the doc.

The spec does indeed define a new SZX value, for use with the =
environments this document is used in (reliable transports).  It does =
not change or add anything to the way RFC 7959 is used with the existing =
unreliable transports; as such it does not really update RFC 7959 as =
much as it does extend it for its own purposes.
(However, the same argument could be made for RFC 7641, which we do say =
we update.)

Maybe we are not making the point forcefully enough that SZX=3D7 is =
meant for use within this spec?
(Again, however: any other future COAP transports that have larger =
messages might pick up SZX=3D7 as well.)

I don=E2=80=99t have a strong opinion on how to populate the =
=E2=80=9Cupdates=E2=80=9D graph of RFCs in these boundary cases; it =
might help to get some more guidance here.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Apr  9 14:24:18 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C501C1293FC; Sun,  9 Apr 2017 14:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, 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 sJZ-ZfgyzHgm; Sun,  9 Apr 2017 14:24:15 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD04127A97; Sun,  9 Apr 2017 14:24:14 -0700 (PDT)
Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com [209.85.218.47]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 05AB129CC3C; Mon, 10 Apr 2017 06:24:12 +0900 (JST)
Received: by mail-oi0-f47.google.com with SMTP id g204so56639005oib.1; Sun, 09 Apr 2017 14:24:11 -0700 (PDT)
X-Gm-Message-State: AFeK/H2dD9jOkdWNRDjqiQIGTRG25G6qIOjQXAtG7c5+hoiOhdx4xfQlhLGz863SX3wjjH/k+OcdUQPSzgAjZw==
X-Received: by 10.157.45.163 with SMTP id g32mr29278825otb.274.1491773050374;  Sun, 09 Apr 2017 14:24:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.38.132 with HTTP; Sun, 9 Apr 2017 14:24:09 -0700 (PDT)
In-Reply-To: <F715AB89-D9FA-414E-83F5-E29F0BBB0904@tzi.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <F715AB89-D9FA-414E-83F5-E29F0BBB0904@tzi.org>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Sun, 9 Apr 2017 14:24:09 -0700
X-Gmail-Original-Message-ID: <CAO249yfRU+bPXf7yCOsg7yccijS=PwM22_2kZpG8qXBL4dBPCA@mail.gmail.com>
Message-ID: <CAO249yfRU+bPXf7yCOsg7yccijS=PwM22_2kZpG8qXBL4dBPCA@mail.gmail.com>
Subject: Re: [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Carsten Bormann <cabo@tzi.org>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, tsv-art@ietf.org,  draft-ietf-core-coap-tcp-tls@ietf.org, core@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c04fb4ac0d40c054cc27a04
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1nDCNt1iAMCT_rbTKRu6FjOu8bo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Apr 2017 21:24:17 -0000

--94eb2c04fb4ac0d40c054cc27a04
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Carsten,

On Sun, Apr 9, 2017 at 12:25 AM, Carsten Bormann <cabo@tzi.org> wrote:

> Hi Yoshi,
>
> thank you very much for your thoughtful review.
>
> For now, let me pick one of your comments:
>
> > 3: Since this draft defines new SZX value, I think the doc needs to
> update RFC7959. This point should be clarified more in the doc.
>
> The spec does indeed define a new SZX value, for use with the environment=
s
> this document is used in (reliable transports).  It does not change or ad=
d
> anything to the way RFC 7959 is used with the existing unreliable
> transports; as such it does not really update RFC 7959 as much as it does
> extend it for its own purposes.
> (However, the same argument could be made for RFC 7641, which we do say w=
e
> update.)
>
> Maybe we are not making the point forcefully enough that SZX=3D7 is meant
> for use within this spec?
> (Again, however: any other future COAP transports that have larger
> messages might pick up SZX=3D7 as well.)
>
> I don=E2=80=99t have a strong opinion on how to populate the =E2=80=9Cupd=
ates=E2=80=9D graph of
> RFCs in these boundary cases; it might help to get some more guidance her=
e.
>

Ok, I see the point. I don't have a strong opinion here either as I am not
a COAP expert.
It could be enough if the draft has more texts to articulate that it won't
cause conflict with unreliable transport COAP.
--
Yoshi

--94eb2c04fb4ac0d40c054cc27a04
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Carsten,<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Sun, Apr 9, 2017 at 12:25 AM, Carsten Bormann <span dir=
=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Yoshi,<br>
<br>
thank you very much for your thoughtful review.<br>
<br>
For now, let me pick one of your comments:<br>
<span class=3D""><br>
&gt; 3: Since this draft defines new SZX value, I think the doc needs to up=
date RFC7959. This point should be clarified more in the doc.<br>
<br>
</span>The spec does indeed define a new SZX value, for use with the enviro=
nments this document is used in (reliable transports).=C2=A0 It does not ch=
ange or add anything to the way RFC 7959 is used with the existing unreliab=
le transports; as such it does not really update RFC 7959 as much as it doe=
s extend it for its own purposes.<br>
(However, the same argument could be made for RFC 7641, which we do say we =
update.)<br>
<br>
Maybe we are not making the point forcefully enough that SZX=3D7 is meant f=
or use within this spec?<br>
(Again, however: any other future COAP transports that have larger messages=
 might pick up SZX=3D7 as well.)<br>
<br>
I don=E2=80=99t have a strong opinion on how to populate the =E2=80=9Cupdat=
es=E2=80=9D graph of RFCs in these boundary cases; it might help to get som=
e more guidance here.<br></blockquote><div><br></div><div>Ok, I see the poi=
nt. I don&#39;t have a strong opinion here either as I am not a COAP expert=
.=C2=A0<br></div><div>It could be enough if the draft has more texts to art=
iculate that it won&#39;t cause conflict with unreliable transport COAP.=C2=
=A0</div><div>--</div><div>Yoshi</div></div></div></div>

--94eb2c04fb4ac0d40c054cc27a04--


From nobody Sun Apr  9 21:07:14 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8905A129415; Sun,  9 Apr 2017 21:07:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mark Nottingham <mnot@mnot.net>
To: <art@ietf.org>
Cc: draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
Subject: Artart last call review of draft-ietf-core-coap-tcp-tls-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149179722452.3118.982908107963516290@ietfa.amsl.com>
Date: Sun, 09 Apr 2017 21:07:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MudiQNsyaCJ8fHvOHupYHHom7Iw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 04:07:05 -0000

Reviewer: Mark Nottingham
Review result: Not Ready

First, a general comment. I have been concerned about the duplication
of effort that COAP represents for some time, and that concern grows
significantly upon reading this draft. COAP is now specifying multiple
"bindings" to underlying application and transport protocols,
re-inventing message framing,  congestion control in UDP, etc. The
introduction justifies this development over the reuse of HTTP/2 (and
presumably QUIC, once available) based upon the relative availability
of implementations for constrained devices. Whether that remains true
will only be judged by the market -- unfortunately after all of the
cost of development and standardisation is sunk.

The introduction motivates the layering of COAP over WebSockets to
allow it to be used in a network that only allows external access
through a HTTP proxy. In fact, it is not necessary to use WebSockets
to do so; HTTP CONNECT provides a tunnel in this scenario. WebSockets
is a specialised protocol that allows bidirectional, stream-based
transport from a Web browser -- it is effectively TCP wrapped into the
Web browser's security model, to make doing so safe. Using it for
other purposes (i.e., non-browser use cases) isn't really appropriate.
I'd suggest either removing the WebSockets binding, or changing its
motivation in the Introduction.

Section 7 defines a number of new URI schemes for COAP protocols.
Syntactically, they use "+" to separate "coap" from the underlying
transport(-ish) protocol that they're bound to; e.g., "coap+tcp". This
syntax is allowed by RFC3986, but is unprecedented, and implies a
sub-syntax convention similar to those used in media types, etc. Is
there an expectation that other URI schemes starting with "coap+" are
reserved? 

Defining URI schemes that switch transport protocol based upon their
name deserves wider review as well; this has been a contentious topic
in the past, and it would be good to understand what tradeoffs are
being made by doing so. Locking identifiers into a specific transport
protocol sacrifices much of the power of URLs. Furthermore, creating
"coap+ws" to denote a specific protocol over WebSockets (which has its
own URI scheme) is questionable; taken to its natural conclusion,
we'll have a proliferation of URI schemes for things over WebSockets.
Will COAP take the same approach for HTTP?

I would suggest a wider discussion of these issues on art@ / uri@.

Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
URI, using a well-known URI in the "wss" scheme. However, "wss" is not
defined to use well-known URIs, so this is an invalid use. I'm not
sure how to address this, other than removing the WebSockets binding.

Section 8.1 makes it Mandatory to Implement the protocol without any
security ("NoSec"). This seems counter to best practice in the IETF,
but I'll defer to the Security Area review.



From nobody Mon Apr 10 02:47:09 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 760E412946D; Mon, 10 Apr 2017 02:46:50 -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 laIirY-Qwsht; Mon, 10 Apr 2017 02:46:48 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 6762B129469; Mon, 10 Apr 2017 02:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3A9kf6R029982; Mon, 10 Apr 2017 11:46:41 +0200 (CEST)
Received: from client-0078.vpn.uni-bremen.de (client-0078.vpn.uni-bremen.de [134.102.107.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w1lh10PjCzDJ1N; Mon, 10 Apr 2017 11:46:41 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149179722452.3118.982908107963516290@ietfa.amsl.com>
Date: Mon, 10 Apr 2017 11:46:40 +0200
Cc: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
X-Mao-Original-Outgoing-Id: 513510400.415103-770b8e04c4ebcf4e77d1fedbfcf44f5f
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rNlrjnTSPVfUPiFC9v83VQicXBE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 09:46:50 -0000

Hi Mark,

thank you for this thoughtful review.

This message will focus on a few technical points; I=E2=80=99ll leave =
aside the philosophical issues about whether the IETF should have a =
constrained node stack.

> WebSockets
> is a specialised protocol that allows bidirectional, stream-based
> transport from a Web browser -- it is effectively TCP wrapped into the
> Web browser's security model, to make doing so safe.

Indeed, that is the use case that was motivating this part.

> Using it for
> other purposes (i.e., non-browser use cases) isn't really appropriate.
> I'd suggest either removing the WebSockets binding, or changing its
> motivation in the Introduction.

I agree that the introduction should focus on the Browser use case and =
keep out of the firewall traversal jungle.

> Section 7 defines a number of new URI schemes for COAP protocols.
> Syntactically, they use "+" to separate "coap" from the underlying
> transport(-ish) protocol that they're bound to; e.g., "coap+tcp". This
> syntax is allowed by RFC3986, but is unprecedented, and implies a
> sub-syntax convention similar to those used in media types, etc. Is
> there an expectation that other URI schemes starting with "coap+" are
> reserved?=20

There is no such expectation.

We did have the discussion about reserved URI scheme prefixes in the =
IETF, and as I recall, the result was that there are none.  While it =
would be a bit weird to register a URI scheme starting with coap+ or =
coaps+ that is unrelated to CoAP, only the slightly boggled response =
from an expert review is in the way of that happening.

Would the scheme names be more palatable with a dash instead of a plus?
Careful choice of the scheme name mostly benefits the implementer, so it =
can be changed in the spec (at the cost of changing existing =
implementations).

> Defining URI schemes that switch transport protocol based upon their
> name deserves wider review as well; this has been a contentious topic
> in the past, and it would be good to understand what tradeoffs are
> being made by doing so. Locking identifiers into a specific transport
> protocol sacrifices much of the power of URLs.

The =E2=80=9Csiloing=E2=80=9D of URIs along schemes is indeed a problem, =
which started for CoAP with the separation of the coap:/coaps: name =
spaces.  The CoRE WG did not see it as its task to address this =
shortcoming.  So, for now, we=E2=80=99ll have to live with it; =
approaches such as draft-silverajan-core-coap-protocol-negotiation are =
trying to address its practicalities.

> Furthermore, creating
> "coap+ws" to denote a specific protocol over WebSockets (which has its
> own URI scheme) is questionable; taken to its natural conclusion,
> we'll have a proliferation of URI schemes for things over WebSockets.

I=E2=80=99m not sure that a proliferation will happen =E2=80=94 =
WebSockets is mostly used for tightly bound proprietary protocols =
between a JavaScript mobile code client and a server that provides this =
mobile code client.  On the other hand, deciding to never use URIs to =
refer to resources available over a WebSockets protocol strikes me as an =
unnecessary restriction.

> Will COAP take the same approach for HTTP?

Not sure what this question is leading into.
(We do have a defined relationship with HTTP, in RFC 7252 and RFC 8075.
But maybe this is about something different.)

> I would suggest a wider discussion of these issues on art@ / uri@.

Indeed, a wider discussion of these longstanding issues would be useful.
I=E2=80=99m not sure that waiting for their resolution is blocking this =
spec.

> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
> URI, using a well-known URI in the "wss" scheme. However, "wss" is not
> defined to use well-known URIs, so this is an invalid use.=20

This incorrect use of RFC 5785 is indeed embarrassing.  More about that =
later.

> Section 8.1 makes it Mandatory to Implement the protocol without any
> security ("NoSec"). This seems counter to best practice in the IETF,
> but I'll defer to the Security Area review.

Since it is the implementers who will decide whether they implement =
this, this co-author could live with making implementing NoSec =
completely optional.  (It will be anyway, in practice, at the level of =
what is actually configured.)  The important point(*) from the WG =
perspective here is that TLS is mandatory to implement, with the =
specifics depending on the security mode needed (cf. RFC 7925).  (Note =
also that there are other ways to provide security with CoAP.)

Gr=C3=BC=C3=9Fe, Carsten

(*) =
https://github.com/core-wg/coap-tcp-tls/commit/fe348f543fc45e981e38e935424=
2012afb28dc60


From nobody Mon Apr 10 03:07:34 2017
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94378129468; Mon, 10 Apr 2017 03:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 96M4Ogqjai1J; Mon, 10 Apr 2017 03:07:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3E5E129477; Mon, 10 Apr 2017 03:07:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEL10452; Mon, 10 Apr 2017 10:07:22 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 10 Apr 2017 11:07:21 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.121]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 10 Apr 2017 18:07:11 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90I1Qr5MFU/1kyZBIn9T3xh16G53MgAgAAGPoCAAANtAIAABASAgAAQtoCABGROEA==
Date: Mon, 10 Apr 2017 10:07:10 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
In-Reply-To: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.191.175]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.58EB595B.0077, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.121, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9ea5c2356683d7cef74a5744d7b6aa9a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SWPgNcbHpmiLk5EH8M6l-uqfqzk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 10:07:33 -0000

SGkgUm9iZXIsIEFsdmFybywgYW5kIExlcywNCg0KSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRo
ZW50aWNhdGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJhdGlvbiBh
cyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IExlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIFttYWlsdG86
Z2luc2JlcmdAY2lzY28uY29tXQ0KPiBTZW50OiBTYXR1cmRheSwgQXByaWwgMDgsIDIwMTcgNjo0
NCBBTQ0KPiBUbzogQWx2YXJvIFJldGFuYSAoYXJldGFuYSk7IFJvYmVydCBTcGFya3M7IGdlbi1h
cnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1YmplY3Q6IFJFOiBHZW5hcnQg
bGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+IA0KPiBB
bHZhcm8gLQ0KPiANCj4gTm90IHN1cmUgaG93IGxvbmcgd2Ugc2hvdWxkIGRlYmF0ZSB0aGlzIGFz
IHRoZSB0ZXh0IHlvdSBhcmUgYXNraW5nIGZvciBpcw0KPiBtb2Rlc3QgLSBidXQgb25lIG1vcmUg
YXR0ZW1wdCBvbiBteSBwYXJ0IC0gbm90IHNvIG11Y2ggdG8gZGViYXRlIHdoZXRoZXINCj4gdG8g
YWRkIHRleHQgb3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4N
Cj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBBbHZhcm8gUmV0
YW5hIChhcmV0YW5hKQ0KPiA+IFNlbnQ6IEZyaWRheSwgQXByaWwgMDcsIDIwMTcgMjo0NSBQTQ0K
PiA+IFRvOiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBp
ZXRmLm9yZw0KPiA+IENjOiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsg
aWV0ZkBpZXRmLm9yZzsNCj4gPiBpc2lzLXdnQGlldGYub3JnDQo+ID4gU3ViamVjdDogUmU6IEdl
bmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4g
Pg0KPiA+IE9uIDQvNy8xNywgNTozMCBQTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2lu
c2JlcmdAY2lzY28uY29tPg0KPiB3cm90ZToNCj4gPg0KPiA+IExlczoNCj4gPg0KPiA+IEhpIQ0K
PiA+DQo+ID4gPiBTeXN0ZW0taWQgZHVwbGljYXRpb24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVw
bG95bWVudCAtIG5vdCBqdXN0DQo+ID4gPiBhdXRvY29uZmlnIGRlcGxveW1lbnRzLiBBbmQgaXQg
d2lsbCBiZSBkaXNydXB0aXZlIGluIGFueSBuZXR3b3JrDQo+ID4gPiB1bnRpbCBpdCBpcw0KPiA+
IHJlc29sdmVkLg0KPiA+ID4NCj4gPiA+IFRoZSBvbmx5IHRoaW5nIGF1dG9jb25maWcgaGFzIGFk
ZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28NCj4gPiA+IG1hbnVhbCBpbnRlcnZlbnRp
b24uIFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3INCj4gPiA+
IHRoZSBkaXNydXB0aW9uIHRoZSBhdHRhY2tlciBjYW4gcHJvZHVjZS4gKFllcyAtIEkgc3RhdGUg
dGhhdCBxdWl0ZQ0KPiA+IGludGVudGlvbmFsbHkpLg0KPiA+DQo+ID4gSSBkb27igJl0IGtub3cg
YWJvdXQgUm9iZXJ0LCBidXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291bGQN
Cj4gPiBsaWtlIHRvIHNlZS4NCj4gPg0KPiA+IFllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2
ZSBhbHdheXMgYmVlbiBhIHBvdGVudGlhbCBwcm9ibGVtLCBidXQNCj4gPiB0aGlzIGRvY3VtZW50
IGludHJvZHVjZXMgYSBuZXcgZGUtZHVwbGljYXRpb24gbWVjaGFuaXNtIHRoYXQgcmVzdWx0cw0K
PiA+IG5vdCBqdXN0IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4gcmVzdGFydGluZyBh
ZGphY2VuY2llcyDigJMgc28gYXQNCj4gPiBsZWFzdCB0aGUgbWFuaWZlc3RhdGlvbiBvZiB0aGUg
cHJvYmxlbSBpcyBkaWZmZXJlbnQuDQo+ID4NCj4gW0xlczpdIFRoZSAicHJvYmxlbSIgZXhpc3Rz
IGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGV4aXN0LiBUaGUNCj4gcmVjb3Zl
cnkgbWVjaGFuaXNtIGRvZXMgbm90IGludHJvZHVjZSBuZXcgcHJvYmxlbXMgLSBpdCBhY3R1YWxs
eSBhY3RzIHRvDQo+IG1pbmltaXplIHRoZSBkdXJhdGlvbiBvZiB0aGUgcHJvYmxlbS4gT25lIGNv
dWxkIGFyZ3VlIChhbmQgSSBhbSBOT1QgZG9pbmcNCj4gc28pIHRoYXQgYXV0b21hdGVkIHJlc29s
dXRpb24gY291bGQgYmUgYSBiZW5lZml0IGluIGFsbCBkZXBsb3ltZW50cy4gSSB0aGluaw0KPiB0
aGUgaXNzdWUgaW4gbm9uLWF1dG9jb25maWcgZGVwbG95bWVudHMgaXMgdGhhdCBzaW5jZSBzeXN0
ZW1zIGhhdmUgYmVlbg0KPiBtYW51YWxseSBwcm92aXNpb25lZCB3ZSBjYW5ub3QgYXNzdW1lIHRo
YXQgbmV0d29yayBvcGVyYXRvcnMgd2FudCB1cyB0bw0KPiBhdXRvbWF0aWNhbGx5IGNoYW5nZSB0
aGUgY29uZmlnIG9uIG9uZSBvZiB0aGVpciBib3hlcy4gVGhvdWdoLCB3aG8ga25vd3MgLQ0KPiBt
YXliZSB3ZSB3aWxsIGdldCBhc2tlZCB0byB1c2UgdGhpcyBleHRlbnNpb24gb3V0c2lkZSBvZiBh
dXRvY29uZmlnDQo+IGRlcGxveW1lbnRzLg0KPiANCj4gSXQgaXMgbmVjZXNzYXJ5IHRvIGhhdmUg
c3VjaCBhIG1lY2hhbmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzIHNpbmNlDQo+IHRoZXJl
IGlzIC0gYnkgZGVmYXVsdCAtIG5vIG1hbnVhbCBpbnRlcnZlbnRpb24uIEJ1dCB0byBjaGFyYWN0
ZXJpemUgdGhpcyBhcw0KPiBhZGRpbmcgcmlzayBpcyBpbmNvcnJlY3QgSU1PLg0KDQpbQmluZ10g
SSBhZ3JlZSB3aXRoIExlcyB0aGF0IHN5cy1pZCBkdXBsaWNhdGlvbiBhdHRhY2sgaXMgbm90IGFu
ICJhZGRpbmciIHJpc2suIA0KQnV0IG1heWJlIHdlIGNvdWxkIGFkZCBhIGJpdCBtb3JlIHRleHQg
dG8gZXhwbGFpbiB3aHkgdGhpcyBkb2N1bWVudCBSRUNPTU1ORUQgdG8gaW1wbGVtZW50IEF1dGgg
VExWLg0KDQpQcm9wb3NlZCBhZGRlZCB0ZXh0IGluIDMuNS4xIChBdXRoZW50aWNhdGlvbiBUTFYp
IGFzIGJlbG93Og0KIlRoZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdp
dGggYXV0by1jb25maWd1cmF0aW9uIGFzIGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3Vy
YXRpb24uIEhvd2V2ZXIsIHRoZXJlIG1pZ2h0IGJlIHNvbWUgdXNlcnMgd291bGQgbGlrZSB0byBw
YXkgdGhlIGVmZm9ydCBvZiBtYW51YWwgY29uZmlndXJhdGlvbiB0byBtaXRpZ2F0ZSBzb21lIHNl
Y3VyaXR5IGF0dGFjayAoZS5nLiBhIG1hbGljaW91cyBub2RlIGNyYWZ0cyBwYWNrZXQgdG8gaW50
ZW50aW9uYWxseSBjYXVzZSB0aGUgU3lzLUlEIGR1cGxpY2F0aW9uIHByb2NlZHVyZSBjb250aW51
b3VzbHkpLiANClRodXMsIGl0IGlzIFJFQ09NTUVORUQgdGhhdCBJUy1JUy4uLiAodGhlIHNhbWUg
YXMgZXhpc3RpbmcgdGV4dCkuDQoNCkRvIHlvdSB0aGluayBpdCdzIE9LPw0KDQpCZXN0IHJlZ2Fy
ZHMsDQpCaW5nDQoNCg0KPiAgIExlcw0KPiANCj4gDQo+ID4gPiBTbyB5b3UgYXJlIGFza2luZyB1
cyB0byByZXBlYXQgYSBkaXNjdXNzaW9uIHdoaWNoIGhhcyBhbHJlYWR5IGJlZW4NCj4gPiA+IGhl
bGQgaW4gdGhlIGNvbnRleHQgb2YgUkZDIDUzMDQgYW5kIFJGQyA1MzEwLg0KPiA+ID4NCj4gPiA+
IEl0IHdvdWxkIGJlIG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRkIHRoZSBub3JtYWwgcmVmZXJlbmNl
IHRvIFJGQw0KPiA+ID4gNTMwNC81MzEwIGluIHRoZSBTZWN1cml0eSBzZWN0aW9uIHRoYW4gd2hh
dCB5b3UgcHJvcG9zZS4NCj4gPg0KPiA+IEkgZG9u4oCZdCB0aGluayBpdCBodXJ0cyB0byBhZGQg
YSByZWZlcmVuY2UgdG8gdGhvc2UgUkZDcywgYnV0IHRoZXkgYXJlDQo+ID4gYm90aCBhYm91dCBh
ZGRpbmcgYXV0aGVudGljYXRpb24g4oCTIHRoZSBwcm9ibGVtIGluIHRoaXMgZG9jdW1lbnQgaXMN
Cj4gPiBleGFjZXJiYXRlZCBieSB0aGUgZmFjdCB0aGF0IHRoZXJl4oCZcyBubyBhdXRoZW50aWNh
dGlvbiBieSBkZWZhdWx0Lg0KPiA+DQo+ID4gVGhlIGxvd2VyIGxheWVyIGF1dGhlbnRpY2F0aW9u
IG1lY2hhbmlzbXMgYXJlIHF1aXRlIHdlYWssIHNwZWNpYWxseQ0KPiA+IGtub3dpbmcgdGhhdCwg
aWYgaW4gYSBob21lIGVudmlyb25tZW50LCBmb3IgZXhhbXBsZSwgaXQgbWF5IGJlDQo+ID4gcmVs
YXRpdmVseSBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0d29yay4NCj4gPg0KPiA+IEFs
dmFyby4NCj4gPg0KDQo=


From nobody Mon Apr 10 07:16:21 2017
Return-Path: <aretana@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF53129490; Mon, 10 Apr 2017 07:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 tMM-UZAi4tUL; Mon, 10 Apr 2017 07:16:19 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F10A4120046; Mon, 10 Apr 2017 07:16:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4570; q=dns/txt; s=iport; t=1491833779; x=1493043379; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=EGQwcp4QM1rFNIujrx+RuG12lA7XCiJQMGZR87lV+Nw=; b=lUfmynmkorf05IpOLxFePHga4fht6zG+AUYkiK5DhyeW8WovkUoJsedT xZG12Ht0Gx8KDLhrp1/Nd5Bg9ErulKjZ0Fd2reHNRjJo6VU2ORGf77ehz YcsZHj2mrzOYV+UTajJ+IX6+cCElcLMfQHQm32ZDf4IHjG5tcGnJr9xCv Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DGAQC+kutY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrgWwHg1+KE5FGlVeCD4YkAhqDQj8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECASMRRQwEAgEIEQQBAQECAiYCAgIwFQgIAgQBDQWKBwipEoImimMBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEdgQuFRYIFgmuEVoMGLoIxAQSWIIZbAZJYkUGTfwE?= =?us-ascii?q?fOIEFWxVSAYZIdYhSgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="228984776"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2017 14:16:18 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v3AEGHUM014097 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 14:16:18 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 09:16:17 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 09:16:17 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeAgABTw4CAA+X3AA==
Date: Mon, 10 Apr 2017 14:16:17 +0000
Message-ID: <624A5B5B-6BCA-4FA0-A344-42AAE3A57F15@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
In-Reply-To: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <71EA5EFDB308D34ABDDCECFD2184C4F9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HMuKGRh5udxGPc42L037xGVqk0g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 14:16:20 -0000

TGVzOg0KDQpIaSENCg0KVGhlIHJpc2sgaXMgbm90IGluIHRoZSBtZWNoYW5pc20gaXRzZWxmLCBh
c3N1bWluZyB0d28gcm91dGVycyB3aXRoIHRoZSBjb3JyZWN0IGltcGxlbWVudGF0aW9uLg0KDQpU
aGUgcmlzayBpcyBpbiB0aGUgZmFjdCB0aGF0IGEgY29tcHJvbWlzZWQgcm91dGVyIGNhbiBjcmFm
dCBhIHBhY2tldCB0byBmb3JjZSB0aGUgYXV0by1jb25maWcgcm91dGVycyB0byBjb250aW51b3Vz
bHkgcmVzdGFydC4gICBBbGwgd2XigJlyZSBhc2tpbmcgZm9yIGlzIGEgcmVjb2duaXRpb24gdGhh
dCB0aGUgcmlzayBleGlzdHMuDQoNClRoYW5rcyENCg0KQWx2YXJvLg0KDQoNCg0KDQpPbiA0Lzcv
MTcsIDY6NDQgUE0sICJMZXMgR2luc2JlcmcgKGdpbnNiZXJnKSIgPGdpbnNiZXJnQGNpc2NvLmNv
bT4gd3JvdGU6DQoNCkFsdmFybyAtDQoNCk5vdCBzdXJlIGhvdyBsb25nIHdlIHNob3VsZCBkZWJh
dGUgdGhpcyBhcyB0aGUgdGV4dCB5b3UgYXJlIGFza2luZyBmb3IgaXMgbW9kZXN0IC0gYnV0IG9u
ZSBtb3JlIGF0dGVtcHQgb24gbXkgcGFydCAtIG5vdCBzbyBtdWNoIHRvIGRlYmF0ZSB3aGV0aGVy
IHRvIGFkZCB0ZXh0IG9yIG5vdCAtIGJ1dCB0byBjb21lIHRvIGEgY29tbW9uIHVuZGVyc3RhbmRp
bmcuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQWx2YXJvIFJldGFu
YSAoYXJldGFuYSkNCj4gU2VudDogRnJpZGF5LCBBcHJpbCAwNywgMjAxNyAyOjQ1IFBNDQo+IFRv
OiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBpZXRmLm9y
Zw0KPiBDYzogZHJhZnQtaWV0Zi1pc2lzLWF1dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0
Zi5vcmc7IGlzaXMtd2dAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4gDQo+IE9uIDQvNy8xNywg
NTozMCBQTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2luc2JlcmdAY2lzY28uY29tPiB3
cm90ZToNCj4gDQo+IExlczoNCj4gDQo+IEhpIQ0KPiANCj4gPiBTeXN0ZW0taWQgZHVwbGljYXRp
b24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0DQo+ID4gYXV0b2Nv
bmZpZyBkZXBsb3ltZW50cy4gQW5kIGl0IHdpbGwgYmUgZGlzcnVwdGl2ZSBpbiBhbnkgbmV0d29y
ayB1bnRpbCBpdCBpcw0KPiByZXNvbHZlZC4NCj4gPg0KPiA+IFRoZSBvbmx5IHRoaW5nIGF1dG9j
b25maWcgaGFzIGFkZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28NCj4gPiBtYW51YWwg
aW50ZXJ2ZW50aW9uLiBUaGlzIGluIG5vIHdheSBpbmNyZWFzZXMgdGhlIHZ1bG5lcmFiaWxpdHkg
bm9yDQo+ID4gdGhlIGRpc3J1cHRpb24gdGhlIGF0dGFja2VyIGNhbiBwcm9kdWNlLiAoWWVzIC0g
SSBzdGF0ZSB0aGF0IHF1aXRlDQo+IGludGVudGlvbmFsbHkpLg0KPiANCj4gSSBkb27igJl0IGtu
b3cgYWJvdXQgUm9iZXJ0LCBidXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291
bGQgbGlrZSB0bw0KPiBzZWUuDQo+IA0KPiBZZXMsIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGhhdmUg
YWx3YXlzIGJlZW4gYSBwb3RlbnRpYWwgcHJvYmxlbSwgYnV0IHRoaXMNCj4gZG9jdW1lbnQgaW50
cm9kdWNlcyBhIG5ldyBkZS1kdXBsaWNhdGlvbiBtZWNoYW5pc20gdGhhdCByZXN1bHRzIG5vdCBq
dXN0DQo+IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4gcmVzdGFydGluZyBhZGphY2Vu
Y2llcyDigJMgc28gYXQgbGVhc3QgdGhlDQo+IG1hbmlmZXN0YXRpb24gb2YgdGhlIHByb2JsZW0g
aXMgZGlmZmVyZW50Lg0KPiANCltMZXM6XSBUaGUgInByb2JsZW0iIGV4aXN0cyBhcyBsb25nIGFz
IHRoZSBkdXBsaWNhdGUgc3lzdGVtLWlkcyBleGlzdC4gVGhlIHJlY292ZXJ5IG1lY2hhbmlzbSBk
b2VzIG5vdCBpbnRyb2R1Y2UgbmV3IHByb2JsZW1zIC0gaXQgYWN0dWFsbHkgYWN0cyB0byBtaW5p
bWl6ZSB0aGUgZHVyYXRpb24gb2YgdGhlIHByb2JsZW0uIE9uZSBjb3VsZCBhcmd1ZSAoYW5kIEkg
YW0gTk9UIGRvaW5nIHNvKSB0aGF0IGF1dG9tYXRlZCByZXNvbHV0aW9uIGNvdWxkIGJlIGEgYmVu
ZWZpdCBpbiBhbGwgZGVwbG95bWVudHMuIEkgdGhpbmsgdGhlIGlzc3VlIGluIG5vbi1hdXRvY29u
ZmlnIGRlcGxveW1lbnRzIGlzIHRoYXQgc2luY2Ugc3lzdGVtcyBoYXZlIGJlZW4gbWFudWFsbHkg
cHJvdmlzaW9uZWQgd2UgY2Fubm90IGFzc3VtZSB0aGF0IG5ldHdvcmsgb3BlcmF0b3JzIHdhbnQg
dXMgdG8gYXV0b21hdGljYWxseSBjaGFuZ2UgdGhlIGNvbmZpZyBvbiBvbmUgb2YgdGhlaXIgYm94
ZXMuIFRob3VnaCwgd2hvIGtub3dzIC0gbWF5YmUgd2Ugd2lsbCBnZXQgYXNrZWQgdG8gdXNlIHRo
aXMgZXh0ZW5zaW9uIG91dHNpZGUgb2YgYXV0b2NvbmZpZyBkZXBsb3ltZW50cy4gDQoNCkl0IGlz
IG5lY2Vzc2FyeSB0byBoYXZlIHN1Y2ggYSBtZWNoYW5pc20gaW4gYXV0b2NvbmZpZyBkZXBsb3lt
ZW50cyBzaW5jZSB0aGVyZSBpcyAtIGJ5IGRlZmF1bHQgLSBubyBtYW51YWwgaW50ZXJ2ZW50aW9u
LiBCdXQgdG8gY2hhcmFjdGVyaXplIHRoaXMgYXMgYWRkaW5nIHJpc2sgaXMgaW5jb3JyZWN0IElN
Ty4NCg0KICBMZXMNCg0KDQo+ID4gU28geW91IGFyZSBhc2tpbmcgdXMgdG8gcmVwZWF0IGEgZGlz
Y3Vzc2lvbiB3aGljaCBoYXMgYWxyZWFkeSBiZWVuDQo+ID4gaGVsZCBpbiB0aGUgY29udGV4dCBv
ZiBSRkMgNTMwNCBhbmQgUkZDIDUzMTAuDQo+ID4NCj4gPiBJdCB3b3VsZCBiZSBtb3JlIGFwcHJv
cHJpYXRlIHRvIGFkZCB0aGUgbm9ybWFsIHJlZmVyZW5jZSB0byBSRkMNCj4gPiA1MzA0LzUzMTAg
aW4gdGhlIFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9wb3NlLg0KPiANCj4gSSBk
b27igJl0IHRoaW5rIGl0IGh1cnRzIHRvIGFkZCBhIHJlZmVyZW5jZSB0byB0aG9zZSBSRkNzLCBi
dXQgdGhleSBhcmUgYm90aA0KPiBhYm91dCBhZGRpbmcgYXV0aGVudGljYXRpb24g4oCTIHRoZSBw
cm9ibGVtIGluIHRoaXMgZG9jdW1lbnQgaXMgZXhhY2VyYmF0ZWQNCj4gYnkgdGhlIGZhY3QgdGhh
dCB0aGVyZeKAmXMgbm8gYXV0aGVudGljYXRpb24gYnkgZGVmYXVsdC4NCj4gDQo+IFRoZSBsb3dl
ciBsYXllciBhdXRoZW50aWNhdGlvbiBtZWNoYW5pc21zIGFyZSBxdWl0ZSB3ZWFrLCBzcGVjaWFs
bHkNCj4ga25vd2luZyB0aGF0LCBpZiBpbiBhIGhvbWUgZW52aXJvbm1lbnQsIGZvciBleGFtcGxl
LCBpdCBtYXkgYmUgcmVsYXRpdmVseQ0KPiBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0
d29yay4NCj4gDQo+IEFsdmFyby4NCj4gDQoNCg0KDQo=


From nobody Mon Apr 10 07:34:35 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783B4129517; Mon, 10 Apr 2017 07:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 W5WtRQmjywyn; Mon, 10 Apr 2017 07:34:23 -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 7B5EE1294FF; Mon, 10 Apr 2017 07:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8618; q=dns/txt; s=iport; t=1491834862; x=1493044462; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vstBV/U16TJ6DMdvjG3CEx/IpzoXE6F+oszkcq3mfXY=; b=D0Q2ZqZEQvqKqEaIJ7c139GyHW0T4w0iWmKZsDvwr7/CqG0HbEMMiah5 QTZejN0IC6WJk8L5csblhgOtzMYDF+UerYWPVVrMUGmowij3h+X60cD/y d4+/6fhgA3W38PFVJRCZhGmkgNeSY6kbhErrLaCUm+MJtrBAcOXAK2kWc c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DGAQDClutY/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTkUaVV4IPhiQCGoNFPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBIxFFBQcEAgEIEQQBAQECAiMDAgICMBQBCAgCBAENBQiJfwipEIImimMBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdgQuFRYRwh1yCXwWcewGST5FKk38BHzhKO1s?= =?us-ascii?q?Vhxt1iFKBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="13171601"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2017 14:34:21 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v3AEYLcJ001665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 14:34:21 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 09:34:20 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 09:34:20 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkIAAWZ6A//+58rCABDovAP//9BHw
Date: Mon, 10 Apr 2017 14:34:20 +0000
Message-ID: <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.67.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1t9fDQdLaJ0ibUeIbHVI9z6F4-w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 14:34:24 -0000

QmluZy9Sb2JlcnQvQWx2YXJvIC0NCg0KSGVyZSBpcyB0aGUgZXhpc3RpbmcgdGV4dCBvZiB0aGUg
U2VjdXJpdHkgU2VjdGlvbjoNCg0KICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRoZW50aWNh
dGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJhdGlvbiBhcyBpdCBy
ZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQogICBGb3Igd2lyZWQgZGVwbG95
bWVudCwgdGhlIHdpcmVkIGNvbm5lY3Rpb24gaXRzZWxmIGNvdWxkIGJlIGNvbnNpZGVyZWQNCiAg
IGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53YW50ZWQgcm91dGVycyBh
cmUgdXN1YWxseQ0KICAgbm90IGFibGUgdG8gY29ubmVjdCAoaS5lLiB0aGVyZSBpcyBzb21lIGtp
bmQgb2YgcGh5c2ljYWwgc2VjdXJpdHkgaW4NCiAgIHBsYWNlIHByZXZlbnRpbmcgdGhlIGNvbm5l
Y3Rpb24gb2Ygcm9ndWUgZGV2aWNlcyk7IGZvciB3aXJlbGVzcw0KICAgZGVwbG95bWVudCwgdGhl
IGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dlcg0KICAgd2lyZWxl
c3MgbGluayBsYXllci4iDQoNCg0KUHJvcG9zZWQgcmV2aXNpb246DQoNCiJJbiB0aGUgYWJzZW5j
ZSBvZiBjcnlwdG9ncmFwaGljIGF1dGhlbnRpY2F0aW9uIGl0IGlzIHBvc3NpYmxlIGZvciBhbiBh
dHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZw0KIHRoZXJlIGlzIGEg
ZHVwbGljYXRlIHN5c3RlbS1pZC4gVGhpcyBtYXkgdHJpZ2dlciBhdXRvbWF0aWMgcmVzdGFydCBv
ZiB0aGUgcHJvdG9jb2wgdXNpbmcgdGhlIGR1cGxpY2F0ZS1pZA0KcmVzb2x1dGlvbiBwcm9jZWR1
cmVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudC4gDQoNCk5vdGUgdGhhdCB0aGUgdXNlIG9mIGF1
dGhlbnRpY2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1dG8tDQpjb25maWd1cmF0aW9uIGFz
IGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQoNCiAgIEZvciB3aXJlZCBk
ZXBsb3ltZW50LCB0aGUgd2lyZWQgY29ubmVjdGlvbiBpdHNlbGYgY291bGQgYmUgY29uc2lkZXJl
ZA0KICAgYXMgYW4gaW1wbGljaXQgYXV0aGVudGljYXRpb24gaW4gdGhhdCB1bndhbnRlZCByb3V0
ZXJzIGFyZSB1c3VhbGx5DQogICBub3QgYWJsZSB0byBjb25uZWN0IChpLmUuIHRoZXJlIGlzIHNv
bWUga2luZCBvZiBwaHlzaWNhbCBzZWN1cml0eSBpbg0KICAgcGxhY2UgcHJldmVudGluZyB0aGUg
Y29ubmVjdGlvbiBvZiByb2d1ZSBkZXZpY2VzKTsgZm9yIHdpcmVsZXNzDQogICBkZXBsb3ltZW50
LCB0aGUgYXV0aGVudGljYXRpb24gY291bGQgYmUgYWNoaWV2ZWQgYXQgdGhlIGxvd2VyDQogICB3
aXJlbGVzcyBsaW5rIGxheWVyLiINCg0KPz8/DQoNCiAgIExlcw0KDQoNCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogTGl1YmluZyAoTGVvKSBbbWFpbHRvOmxlby5saXViaW5n
QGh1YXdlaS5jb21dDQo+IFNlbnQ6IE1vbmRheSwgQXByaWwgMTAsIDIwMTcgMzowNyBBTQ0KPiBU
bzogTGVzIEdpbnNiZXJnIChnaW5zYmVyZyk7IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpOyBSb2Jl
cnQgU3BhcmtzOyBnZW4tDQo+IGFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1pc2lzLWF1
dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGlzaXMtd2dAaWV0Zi5vcmcNCj4g
U3ViamVjdDogUkU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1h
dXRvLWNvbmYtMDQNCj4gDQo+IEhpIFJvYmVyLCBBbHZhcm8sIGFuZCBMZXMsDQo+IA0KPiBJbiBn
ZW5lcmFsLCB0aGUgdXNlIG9mIGF1dGhlbnRpY2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1
dG8tDQo+ICAgIGNvbmZpZ3VyYXRpb24gYXMgaXQgcmVxdWlyZXMgc29tZSBtYW51YWwgY29uZmln
dXJhdGlvbi4NCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBM
ZXMgR2luc2JlcmcgKGdpbnNiZXJnKSBbbWFpbHRvOmdpbnNiZXJnQGNpc2NvLmNvbV0NCj4gPiBT
ZW50OiBTYXR1cmRheSwgQXByaWwgMDgsIDIwMTcgNjo0NCBBTQ0KPiA+IFRvOiBBbHZhcm8gUmV0
YW5hIChhcmV0YW5hKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBpZXRmLm9yZw0KPiA+IENjOiBk
cmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4g
PiBpc2lzLXdnQGlldGYub3JnDQo+ID4gU3ViamVjdDogUkU6IEdlbmFydCBsYXN0IGNhbGwgcmV2
aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4gPg0KPiA+IEFsdmFybyAtDQo+
ID4NCj4gPiBOb3Qgc3VyZSBob3cgbG9uZyB3ZSBzaG91bGQgZGViYXRlIHRoaXMgYXMgdGhlIHRl
eHQgeW91IGFyZSBhc2tpbmcgZm9yDQo+ID4gaXMgbW9kZXN0IC0gYnV0IG9uZSBtb3JlIGF0dGVt
cHQgb24gbXkgcGFydCAtIG5vdCBzbyBtdWNoIHRvIGRlYmF0ZQ0KPiA+IHdoZXRoZXIgdG8gYWRk
IHRleHQgb3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4NCj4g
Pg0KPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiA+IEZyb206IEFsdmFybyBS
ZXRhbmEgKGFyZXRhbmEpDQo+ID4gPiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDI6NDUg
UE0NCj4gPiA+IFRvOiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2Vu
LWFydEBpZXRmLm9yZw0KPiA+ID4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGll
dGYub3JnOyBpZXRmQGlldGYub3JnOw0KPiA+ID4gaXNpcy13Z0BpZXRmLm9yZw0KPiA+ID4gU3Vi
amVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRv
LWNvbmYtMDQNCj4gPiA+DQo+ID4gPiBPbiA0LzcvMTcsIDU6MzAgUE0sICJMZXMgR2luc2Jlcmcg
KGdpbnNiZXJnKSIgPGdpbnNiZXJnQGNpc2NvLmNvbT4NCj4gPiB3cm90ZToNCj4gPiA+DQo+ID4g
PiBMZXM6DQo+ID4gPg0KPiA+ID4gSGkhDQo+ID4gPg0KPiA+ID4gPiBTeXN0ZW0taWQgZHVwbGlj
YXRpb24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0DQo+ID4gPiA+
IGF1dG9jb25maWcgZGVwbG95bWVudHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55
IG5ldHdvcmsNCj4gPiA+ID4gdW50aWwgaXQgaXMNCj4gPiA+IHJlc29sdmVkLg0KPiA+ID4gPg0K
PiA+ID4gPiBUaGUgb25seSB0aGluZyBhdXRvY29uZmlnIGhhcyBhZGRlZCBpcyBhIHdheSB0byBy
ZXNvbHZlIHRoaXMgdy9vDQo+ID4gPiA+IG1hbnVhbCBpbnRlcnZlbnRpb24uIFRoaXMgaW4gbm8g
d2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eQ0KPiA+ID4gPiBub3IgdGhlIGRpc3J1cHRp
b24gdGhlIGF0dGFja2VyIGNhbiBwcm9kdWNlLiAoWWVzIC0gSSBzdGF0ZSB0aGF0DQo+ID4gPiA+
IHF1aXRlDQo+ID4gPiBpbnRlbnRpb25hbGx5KS4NCj4gPiA+DQo+ID4gPiBJIGRvbuKAmXQga25v
dyBhYm91dCBSb2JlcnQsIGJ1dCB0aGF0IGlzIHBhcnQgb2YgdGhlIGRpc2N1c3Npb24gSQ0KPiA+
ID4gd291bGQgbGlrZSB0byBzZWUuDQo+ID4gPg0KPiA+ID4gWWVzLCBkdXBsaWNhdGUgc3lzdGVt
LWlkcyBoYXZlIGFsd2F5cyBiZWVuIGEgcG90ZW50aWFsIHByb2JsZW0sIGJ1dA0KPiA+ID4gdGhp
cyBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3IGRlLWR1cGxpY2F0aW9uIG1lY2hhbmlzbSB0aGF0
IHJlc3VsdHMNCj4gPiA+IG5vdCBqdXN0IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4g
cmVzdGFydGluZyBhZGphY2VuY2llcyDigJMgc28NCj4gPiA+IGF0IGxlYXN0IHRoZSBtYW5pZmVz
dGF0aW9uIG9mIHRoZSBwcm9ibGVtIGlzIGRpZmZlcmVudC4NCj4gPiA+DQo+ID4gW0xlczpdIFRo
ZSAicHJvYmxlbSIgZXhpc3RzIGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGV4
aXN0Lg0KPiA+IFRoZSByZWNvdmVyeSBtZWNoYW5pc20gZG9lcyBub3QgaW50cm9kdWNlIG5ldyBw
cm9ibGVtcyAtIGl0IGFjdHVhbGx5DQo+ID4gYWN0cyB0byBtaW5pbWl6ZSB0aGUgZHVyYXRpb24g
b2YgdGhlIHByb2JsZW0uIE9uZSBjb3VsZCBhcmd1ZSAoYW5kIEkNCj4gPiBhbSBOT1QgZG9pbmcN
Cj4gPiBzbykgdGhhdCBhdXRvbWF0ZWQgcmVzb2x1dGlvbiBjb3VsZCBiZSBhIGJlbmVmaXQgaW4g
YWxsIGRlcGxveW1lbnRzLiBJDQo+ID4gdGhpbmsgdGhlIGlzc3VlIGluIG5vbi1hdXRvY29uZmln
IGRlcGxveW1lbnRzIGlzIHRoYXQgc2luY2Ugc3lzdGVtcw0KPiA+IGhhdmUgYmVlbiBtYW51YWxs
eSBwcm92aXNpb25lZCB3ZSBjYW5ub3QgYXNzdW1lIHRoYXQgbmV0d29yaw0KPiBvcGVyYXRvcnMN
Cj4gPiB3YW50IHVzIHRvIGF1dG9tYXRpY2FsbHkgY2hhbmdlIHRoZSBjb25maWcgb24gb25lIG9m
IHRoZWlyIGJveGVzLg0KPiA+IFRob3VnaCwgd2hvIGtub3dzIC0gbWF5YmUgd2Ugd2lsbCBnZXQg
YXNrZWQgdG8gdXNlIHRoaXMgZXh0ZW5zaW9uDQo+ID4gb3V0c2lkZSBvZiBhdXRvY29uZmlnIGRl
cGxveW1lbnRzLg0KPiA+DQo+ID4gSXQgaXMgbmVjZXNzYXJ5IHRvIGhhdmUgc3VjaCBhIG1lY2hh
bmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzDQo+ID4gc2luY2UgdGhlcmUgaXMgLSBieSBk
ZWZhdWx0IC0gbm8gbWFudWFsIGludGVydmVudGlvbi4gQnV0IHRvDQo+ID4gY2hhcmFjdGVyaXpl
IHRoaXMgYXMgYWRkaW5nIHJpc2sgaXMgaW5jb3JyZWN0IElNTy4NCj4gDQo+IFtCaW5nXSBJIGFn
cmVlIHdpdGggTGVzIHRoYXQgc3lzLWlkIGR1cGxpY2F0aW9uIGF0dGFjayBpcyBub3QgYW4gImFk
ZGluZyIgcmlzay4NCj4gQnV0IG1heWJlIHdlIGNvdWxkIGFkZCBhIGJpdCBtb3JlIHRleHQgdG8g
ZXhwbGFpbiB3aHkgdGhpcyBkb2N1bWVudA0KPiBSRUNPTU1ORUQgdG8gaW1wbGVtZW50IEF1dGgg
VExWLg0KPiANCj4gUHJvcG9zZWQgYWRkZWQgdGV4dCBpbiAzLjUuMSAoQXV0aGVudGljYXRpb24g
VExWKSBhcyBiZWxvdzoNCj4gIlRoZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRp
YmxlIHdpdGggYXV0by1jb25maWd1cmF0aW9uIGFzIGl0DQo+IHJlcXVpcmVzIHNvbWUgbWFudWFs
IGNvbmZpZ3VyYXRpb24uIEhvd2V2ZXIsIHRoZXJlIG1pZ2h0IGJlIHNvbWUgdXNlcnMNCj4gd291
bGQgbGlrZSB0byBwYXkgdGhlIGVmZm9ydCBvZiBtYW51YWwgY29uZmlndXJhdGlvbiB0byBtaXRp
Z2F0ZSBzb21lDQo+IHNlY3VyaXR5IGF0dGFjayAoZS5nLiBhIG1hbGljaW91cyBub2RlIGNyYWZ0
cyBwYWNrZXQgdG8gaW50ZW50aW9uYWxseSBjYXVzZSB0aGUNCj4gU3lzLUlEIGR1cGxpY2F0aW9u
IHByb2NlZHVyZSBjb250aW51b3VzbHkpLg0KPiBUaHVzLCBpdCBpcyBSRUNPTU1FTkVEIHRoYXQg
SVMtSVMuLi4gKHRoZSBzYW1lIGFzIGV4aXN0aW5nIHRleHQpLg0KPiANCj4gRG8geW91IHRoaW5r
IGl0J3MgT0s/DQo+IA0KPiBCZXN0IHJlZ2FyZHMsDQo+IEJpbmcNCj4gDQo+IA0KPiA+ICAgTGVz
DQo+ID4NCj4gPg0KPiA+ID4gPiBTbyB5b3UgYXJlIGFza2luZyB1cyB0byByZXBlYXQgYSBkaXNj
dXNzaW9uIHdoaWNoIGhhcyBhbHJlYWR5IGJlZW4NCj4gPiA+ID4gaGVsZCBpbiB0aGUgY29udGV4
dCBvZiBSRkMgNTMwNCBhbmQgUkZDIDUzMTAuDQo+ID4gPiA+DQo+ID4gPiA+IEl0IHdvdWxkIGJl
IG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRkIHRoZSBub3JtYWwgcmVmZXJlbmNlIHRvIFJGQw0KPiA+
ID4gPiA1MzA0LzUzMTAgaW4gdGhlIFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9w
b3NlLg0KPiA+ID4NCj4gPiA+IEkgZG9u4oCZdCB0aGluayBpdCBodXJ0cyB0byBhZGQgYSByZWZl
cmVuY2UgdG8gdGhvc2UgUkZDcywgYnV0IHRoZXkNCj4gPiA+IGFyZSBib3RoIGFib3V0IGFkZGlu
ZyBhdXRoZW50aWNhdGlvbiDigJMgdGhlIHByb2JsZW0gaW4gdGhpcyBkb2N1bWVudA0KPiA+ID4g
aXMgZXhhY2VyYmF0ZWQgYnkgdGhlIGZhY3QgdGhhdCB0aGVyZeKAmXMgbm8gYXV0aGVudGljYXRp
b24gYnkgZGVmYXVsdC4NCj4gPiA+DQo+ID4gPiBUaGUgbG93ZXIgbGF5ZXIgYXV0aGVudGljYXRp
b24gbWVjaGFuaXNtcyBhcmUgcXVpdGUgd2Vhaywgc3BlY2lhbGx5DQo+ID4gPiBrbm93aW5nIHRo
YXQsIGlmIGluIGEgaG9tZSBlbnZpcm9ubWVudCwgZm9yIGV4YW1wbGUsIGl0IG1heSBiZQ0KPiA+
ID4gcmVsYXRpdmVseSBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0d29yay4NCj4gPiA+
DQo+ID4gPiBBbHZhcm8uDQo+ID4gPg0KDQo=


From nobody Mon Apr 10 08:13:34 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105B1129537; Mon, 10 Apr 2017 08:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] 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 eQLBoLUiGrgH; Mon, 10 Apr 2017 08:13:16 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 7189E1294F6; Mon, 10 Apr 2017 08:13:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.20.181; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
In-Reply-To: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
Subject: RE: [I2nsf] Review of draft-ietf-i2nsf-problem-and-use-cases-11
Date: Mon, 10 Apr 2017 11:08:04 -0400
Message-ID: <00fb01d2b20c$4182ab80$c4880280$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGutpg0SXJzXob6/wPiGXgr+oPIOqHd3kAA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DnG-irBQdiFkEi2cWo3qXs0Z-HY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 15:13:20 -0000

Dale: 

Thank you for the review.  Please see my comments below. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Tuesday, March 14, 2017 6:17 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Review of draft-ietf-i2nsf-problem-and-use-cases-11

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair.  Please treat these comments just like any other last call
comments.

Document:  draft-ietf-i2nsf-problem-and-use-cases-11
Reviewer:  Dale R. Worley
Review Date:  2017-03-14
IETF LC End Date:  2017-03-22
IESG Telechat date:  [unknown]

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

>1.  Introduction
>
> This document describes the problem statement for Interface to
> Network Security Functions (I2NSF) as well as some I2NSF use cases.
> A summary of the state of the art in the industry and IETF which is
> relevant to I2NSF work is documented in
>  [I-D.hares-i2nsf-gap-analysis].

>The content of these sentences is very good, but the construction seems to
be peculiar.  The document doesn't *describe* the problem statement, the
document *is* a statement.  Similarly, hares-i2nsf-gap-analysis *is* a
summary of the state of the art.  >So I would use
>
> This document is the problem statement for Interface to Network
> Security Functions (I2NSF) as well as some I2NSF use cases.  A
> summary of the state of the art in the industry and IETF which is
> relevant to I2NSF work is [I-D.hares-i2nsf-gap-analysis].

Dale 

>But maybe you'll prefer to ask the RFC Editor.
>
> This document also briefly describes the
> following use cases summarized by
> [I-D.pastor-i2nsf-merged-use-cases]:
>
>This sentence should start a new paragraph, as it's not connected to the
sentences before it.

Thank you for finding these errors.  I also needed to change
I-D.hares-i2nsf-gap-analysis to draft-ietf-i2nsf-gap-analysis. 


>3.  Problem Space
>
> The following sub-section describes ...
>s/sub-section describes/sub-sections describe/

Thank you - sorry to have missed it. 

>3.1.1.  Diverse Types of Security Functions
>
> NSFs by different vendors can have
>  different features and have different interfaces.
>
>It might be worth mentioning somewhere what seems to be a convention:
>the document (or at least, section 3.1) is largely oriented toward "service
providers" who sell comprehensive network services (including security
functions) to "customers", but who in turn buy security functions from
"vendors".  Perhaps this could be ?>entered as terminology in section 2.
>
>The reason I mention this is that my background is as an end-user (which is
common in the IETF), so the term "service provider"
>Triggers in my mind the idea "someone I buy something from".  And the term
"vendor" triggers the *same* idea.  But in this draft, the default reader is
a "service provider" and "vendor" is *not* the same thing.

I've added this text: Security Service Provider:  A provider of security
services to the customers (end-users or enterprises) using NSF equipment
purchased from vendors or created by the service provider. 

>This point started to confuse me at the beginning of section 3.1.6.
>
>  Security Functions in a Demilitarized Zone (DMZ):   Examples of this
>   function are firewall/ACLs, IDS/IPS, one or all of AAA services
>    NAT, forwarding proxies, and application filtering.
> The phrase "one or all of AAA services NAT" seems to be incorrect.  I
suspect there's supposed to be a comma before NAT.

Good catch.  I will fix. 

>   Security gateways and VPN concentrators:    Examples of these
>     functions are; IPsec gateways, Secure VPN concentrators that
>    handle bridging secure VPNs, and Secure VPN controllers for data
>    flows.

> Unless "Secure VPN" is a name in itself, "secure" shouldn't be
capitalized.

Good point.  I will fix. 

> 3.1.2.  Diverse Interfaces to Control and Monitor NSFs
>
>   A challenge for monitoring is that an NSF cannot monitor what it
>   cannot view.  Therefore, enabling a security function (e.g., firewall
>   [I-D.ietf-opsawg-firewalls]) does not mean that a network is
>   protected.  As such, it is necessary to have a mechanism to monitor
>  and provide execution status of NSFs to security and compliance
>   management tools.  There exist various network security monitoring
>   vendor-specific interfaces for forensics and troubleshooting.

> This paragraph seems awkward.  Each sentence is reasonable, but the
connection between them is not clear to me. 
>  Perhaps the third sentence has the meaning "... it is necesary to have a
mechanism ...to verify that the NSF is seeing the traffic that is intended".
>The last sentence contains "network security monitoring vendor-specific
interfaces" which is awkward.  Perhaps
>
> There exist various vendor-specific interfaces for network security
> monitoring, forensics, and troubleshooting.

New paragraph is below.   Is it better

New/
A challenge for monitoring prior to mitigation of a security intrusion
is that an NSF cannot monitor what it cannot view. Therefore, enabling a 
 security function to mitigate an intrusion 
 (e.g., firewall <xref target="I-D.ietf-opsawg-firewalls"></xref>) 
 does not mean that a network is protected if there is no monitoring
feedback.  
  As such, it is necessary to have a mechanism
  to monitor and provide execution status of NSFs to security and
  compliance management tools. There exist various network security
  monitoring vendor-specific interfaces for forensics and
  troubleshooting, but an industry standard interface could 
  provide monitoring across avariety of NSFs.
/

 

3.1.4.  More Demand to Control NSFs Dynamically

>   The Security Service Providers ...

>The capitalization of "security service providers" is inconsistent.
> Some times all three words are capitalized, and some times they're not.
Thanks for catching this - I will fix it. 

3.1.5.  Demand for Multi-Tenancy to Control and Monitor NSFs

>   Service providers may need several operational units to control and
 >  monitor the NSFs, especially when NSFs become distributed and
 >  virtualized.
>
> You may want to explain what an "operational unit" is.  As far as I can
tell, neither "unit" nor "operational" (in this sense) is used elsewhere in
this draft.

Thanks for catching this vagueness. 
The point the service provides may have to deploy multiple controllers. 

How about: 

Service providers may need to deploy several NSF controllers to control and
monitor the NSFs, especially when NSFs become distributed and
virtualized.

>3.1.7.  Lack of Mechanism for NSFs to Utilize External Profiles
>  Many security functions depend on signature files or profiles to
>   perform (e.g., IPS/IDS signatures, DDos Open Threat Signaling
> (DOTS) filters).  
>I think the words "to perform" should be removed.  The sentence makes more
sense to me without those.  Or, if there is a meaning that needs to be
specified, "to perform" probably >isn't the right choice.  "to work" makes
sense in this place, but is an informal usage.  Perhaps "to function".

[removed "to perform") 

>   Today, the construction and use of black list databases
>  can be a win-win strategy for all parties involved.
>"win-win strategy" is a hackneyed phrase.  This is better

 > Today, the construction and use of black list databases
  > can be beneficial for all parties involved.

>However, it's not clear to me what additional information is carried by
"for all parties involved".  And for that matter, is "today"
>important here?
>I suspect that you mean something like this:
>
 > Today, black list databases can be beneficial, and in the future
 > there might be open source signatures/profiles ...

> 
>   (e.g., by Snort, Suricata, Bro and Kisnet)
>
>s/Kisnet/Kismet/
>"Snort, Suricata, Bro and Kisnet" reads like a reference -- I had to look
them up to discover that they are IDS software!
>
>But there needs to be some connection between a list of IDS software
systems and "open source signatures/profiles".  Perhaps:
>
> Today, black list databases can be beneficial, and in the future
>   there might be open source signatures/profiles distributed as part
>  of IDS systems (e.g. Snort, Suricata, Bro and Kisnet).

All good comments, but my recollection was the WG wanted to underscore the
strategy was good for all parties. 
Therefore, here's the new paragraph


New/
Today, black list databases can be a beneficial 
 strategy for all parties involved, but in the future there might be 
 open Source-provided signature/profiles distributed as part of IDS systems
(e.g., by Snort, Suricata, Bro and Kismet).
/
--
>There is a need to have a standard envelope (i.e., the format) to
 > allow NSFs to use external profiles.
>This is awkward.  Perhaps
 > There is a need to have a standard format to allow NSFs to use
 > external profiles.

This part hit many discussions.  How about

New/ There is a need to have a standard envelope (i.e., a message format) to

allow NSFs to use external profiles./ 

>3.1.8.  Lack of Mechanisms to Accept External Alerts to Trigger ...
>
> I2NSF controller(s) would manage the changing to the affected
>  policies ...
> This could be simplified to "I2NSF controller(s) would change the affected
policies ...".

New/  I2NSF  controller(s) would control any changes to affected policies
          (e.g., forwarding and routing, filtering, etc.)./

>The I2NSF controls the change (whether others change the policies or not). 
>  By monitoring the network alerts from DDoS ...
>Probably s/DDoS/DOTS/.
>
>   ... I2NSF
> can feed an alerts analytics engine that could recognize attacks so
> the I2NSF can enforce the appropriate policies.
>  Here, "I2NSF" is being used as a noun, whereas the previous usage is that
it is an adjective, and "I2NSF controller(s)" would be used.

New/
By monitoring the network alerts regarding DDoS attacks (e.g. from DOTS
servers or clients), 
the I2NSF controller(s) can feed an alerts analytics engine
that could recognize attacks so the I2NSF can enforce the
appropriate policies. 
/


>   ... provide information to the client ...
>
>I think this is clearer if s/the client/its clients/.  "client" is used
with two meanings, one is "customer" (e.g., in the definition of "Bespoke"),
and more commonly as "software client".  > If you say "[the controller's]
clients", it is clear that you're using the second meaning.

New/ DDoS mitigation is enhanced if the provider's network security
          controller can monitor, analyze, and investigate the abnormal
events
          and provide information to the customer or change the network
          configuration automatically
/

>3.1.9.  Lack of Mechanism for Dynamic Key Distribution to NSFs
>
> There is a need for a controller to distribute various keys to
> distributed NSFs.  To distribute various keys, the keys must be
>  created and managed.

>Perhaps combine these as
>
>   There is a need for a controller to create, manage, and distribute
>  various keys to distributed NSFs.

I've made this change. 


>   In addition, keys may be used to secure
>  the protocol and messages in the core routing infrastructure (see
>  [RFC4948])

>Probably s/protocol/protocols/.
>
I've made this change. 

>   If a device had an abstract key table
>  maintained by security services, a device could use these keys for
>  routing and seurity devices.
>
>s/seurity/security/
>
>Typical English usage in this situation is "it could use ..."; because "it"
is the subject of the second clause, it is presupposed to be the same as the
subject of the first clause.

New sentences: 
/ If a device had an abstract  key table maintained by security services, it
could use these 
keys for routing and security devices.  /

>   Conceptually, there must be an interface defined for routing/
>  signaling protocols to make requests for automated key management
>  when it is being used, and to notify the protocols when keys become
 >  available in the key table.  One potential use of such an interface
>   is to manage IPsec security associations on SDN networks.
>I think you need to add a subject in "... and for XXX to notify the
protocols ..." for clarity, the omitted noun could be "interface" or
"protocols".

Grammatically - I disagree .  The clauses "to make request...." and "to
notify" are infinitive clauses which modify the direct object (an interface)
which are linked together in a list.  
However, rather than debate this syntax with others - I've changed the
syntax to a cl

New/ 
Conceptually, there must be an interface defined for routing/signaling
protocols 
  that can:  a) make requests for automated key management when it is being
used. and 
   b) notify the protocols when keys become available in the key table. 
/


>The last sentence seems redundant, as security associations have been
discussed at the beginning of 3.1.9.  Is there a particular reason to point
out IPsec at this point (since many >secured protocols need keys)?

The WG felt it needed an example here.   If it is OK, I'm going to leave
this in for another round of editing. 

> If protocols share
>     common mechanisms for authentication (e.g., TCP Authentication
>     Option [RFC5925]), then the same mapping may be reused.

>This sentence starts with "protocols [that] share common mechanisms"
>but then mentions only one protocol.  Do you mean

  >     If several protocols share a
  >    common mechanism for authentication (e.g., TCP Authentication
  >   Option [RFC5925]), then the same mapping may be used for all
  >   usages of that mechanism.


Thank you.  I've changed to this sentence. 


>   3.  Automated Key management needs to support both symmetric keys and
>     group keys via the abstract key service provided by items 1 and
 >     2.
>s/Key/key/

--Thank you. 

>I think "via the abstract key service provided by items 1 and 2" is
redundant here.

It may be redundant, but as I recall it was important to some of the
authors. 
--------------

3.2.  Challenges Facing Customers

>   o  Which critical communications are to be preserved during critical
>     events and which hosts are continue service,
>
>"are continue service" seems to be incorrect in some way.

New/Which critical communications are to be preserved during
            critical events and which hosts will continue services over the
network,/


>   o  What signaling information is passed to a controller that during a
>     Distributed Denial of Service in order to ask for mitigation
>     services (within the scope DOTS working group),
> "that" should be removed, I think.

Removed. 

>3.2.2.  Today's Control Requests are Vendor Specific
>
> Without a standard technical
> standard interface that provides a clear technical characterization,
>  the service provider faces many challenges:

>Should "standard technical standard interface" be "standard interface"
>or "standardized interface"?

>Standardized interface. 
> No standard technical characterization, APIs, or Interface
>I think you want a colon after this phrase to parallel the other items in
the list.

Thank you. 

>   Managing by scripts de-jour:    The current practices rely upon the
>      use of scripts that generate other scripts which automatically run
>  to upload or download configuration changes, log information and
>    other things.  These scripts have to be adjusted each time an
>    implementation from a different vendor technology is enabled on a
>    provider side.
> The phrase "on a provider side" doesn't read well.  Perhaps "by a service
provider"?

3.3.  Lack of Standard Interface to Inject Feedback to NSF

>   The following sub-section describes the problems and challenges
>  facing customers and security service providers when some or all of
> the security functions are no longer physically hosted by the
> customer's adminstrative domain.
>s/adminstrative/administrative/

Note: Sentence was removed. 

>   As more sophisticated threats arise, enterprises, vendors, and
>   service providers have to rely on each other to achieve optimal
> protection.  Cyber Threat Alliance (CTA,
> http://cyberthreatalliance.org/) is one of those initiatives that aim
> at combining efforts conducted by multiple organizations.

>This paragraph doesn't fit well in the flow of the text.  The second
sentence seems like it's basically a reference, and the link should be put
down in the references.  But I think the >point resembles the discussion in
3.1.7, that you want to enable organizations to pass among themselves new
profiles, which the customers or service providers can insert into NSFs > in
a simple way.  Perhaps

>   As more sophisticated threats arise, protection will depend
> on enterprises, vendors, and service providers being able to
>  cooperate to develop optimal profiles, e.g., through initiatives
>   like [CTA].  

>and then combine with the paragraph which follows:
>
 > The standard interface to provide security profiles to the NSF should
 > interwork with the formats which exchange security profiles between
>  organizations.

3.5.  Difficulty to Validate Policies across Multiple Domains

  >As discussed in the previous four sections, both service providers ...

>Probably s/sections/sub-sections/.
>   ... and customers have needs to express policies and profiles ...
>
>s/needs/need/
>
 > This section and the next section (section 3.6) xamine what ...
>s/xamine/examine/

> (Have you spell-checked this draft?) 

Not this one.  I'm afraid I rushed the -11 out in response to query.  I
lived to regret this fact. 
>
>
>   ... happens in two specific network scnearios: ...

s/scnearios/scenarios/

> a) multi-domain control of
 >  security devices hosted on virtual and non-virtual ...
>There is a noun missing after "virtual and non-virtual".

Noun is NSFs 

>   Hosted security service may instantiate NSFs in Virtual Machines
>
>
>You probably don't want to capitalize "virtual machines" here.

Changed. 


>   To set-up this cross-domain service, the security controller must be
>  able to communicate with NSFs and/or controllers within its domain
>  and across domains to negatiate for the services needed.

> s/set-up/set up/  ("set up" is a verb (more or less), "set-up" is the
action of setting up or the thing which is set up.)

The text should be "to set up" an infinitive verb setting up an infinitive
clause, or it can be considered a prepositional phrase "to set up ..." 
Anyway, thank you for the editing. 

s/negatiate/negotiate/

3.6.  Software-Defined Networks

>   Software-Defined Networks have changed the landscape of data center
>   designs by introducing overlay networks deployed over ToR switches
>  that connect to a hypervisor.

>You probably should spell out "ToR switch"; "top of rack switch" is not yet
listed in Wikipedia as a meaning of "ToR".


Start here
-----------------
4.1.  Basic Framework

> Integrity of the NSF:   by ensuring that the NSF is not
> compromised;

>  Isolation:   by ensuring the execution of the NSF is self-contained
 >   for privacy requirements in multi-tenancy scenarios.
>   Provenance of NSF:    Customers may need to be provided with strict
>      guarantees about the origin of the NSF, its status (e.g.,
>    available, idle, down, and others), and feedback mechanisms so
>    that a customer may be able to check that a given NSF or set of
>    NSFs properly conform to the the customer's requirements and
>    subsequent configuration tasks.
>The punctuation and capitalization is inconsistent between the list items
here.  I suggest changing the first two to (more or less)\
>sentences:
>
> Integrity of the NSF:   Ensuring that the NSF is not compromised.
>
> Isolation:   Ensuring the execution of the NSF is self-contained
>    for privacy requirements in multi-tenancy scenarios.
>
>?Probably s/Provenance of NSF/Provenance of the NSF/.
>
> In order to achieve this, the security controller may collect
> security measurements and share them with an independent and trusted
> third party (via Interface 1) in order to allow for attestation of
> NSF functions using the third party added information.
>
>Would this really be via Interface 1?  It looks like Interface 1 only goes
to the customer's client, not a 3rd party service, and it is used for
passing security requests.  This is made clearer in the next paragraph, but
it would probably be better to only say that there needs to be an interface
to 3rd parties for services like this, and it may be a variant of Interface
1 or it may be a distinct interface.

Dale: While this make be clearer, it was the WGs final comments.   I'll see
what the IESG says. 


>4.2.  Access Networks

>   Figure 3 shows how these virtual
>  access nodes for different types of customers connect connect through
>  virtual access nodes an NSF.
> s/connect connect/connect/
>The grammar of the sentence needs fixing also somewhere near "nodes an
NSF".

Sue: Fixed 

 > These use cases define the interaction between the operator and the
> vNSFs through automated interfaces, typically by means of
> Business- to-Business (B2B) communications.
>Dale: Is "Business-to-Business (B2B) communications" a technical term?  
> It doesn't seem to me to convey any additional information, since most of
the usages envision that NSFs may be provided by outside vendors, so pretty
much any communication with an NSF may be business-to-business
communication.

New/These use cases define the interaction between the operator and the
        vNSFs through automated interfaces which support the business
communications
        between customer and provider or between two business entities./

> Service Provider:   Service requests for policies that protect ...
>
>There isn't a "Service Provider" illustrated in the figure.  
>I assume that the Service Provider looks much like the other three cases, 
>since those look very much like each other, but some sort of
> illustration should be provided.  Especially if the Service Provider 
> has further customers (presumably further to the left in the figure), that
would be a more complex architecture.

Sue: Service Provider added to the network 

 >  ... may want to get
  > their dedicated NSFs (most likely vNSFs) for direct control purposes.
>This is rather informal usage.  Perhaps better:

>   ... may want to contract separately for dedicated NSFs ...

Sue: Thank you - changed. 

>  In this case, here are the steps to associate vNSFs to specific
> customers:
>There are two cases discussed in the paragraph before this sentence, 
>and it's not obvious which one this sentence is connected to via "In this
case".  
>Or does it apply to both?  If it applies to the second case only, 
>I suggest splitting the last two sentences off as a separate paragraph. 
 >If this sentence applies to all cases in this subsection, I suggest
removing "In this case".

Done - split off the second 2 sentences. 

>4.3.  Cloud Data Center Scenario
>
> The on-demand, dynamic nature of security service delivery
> essentially encourages that the network security "devices" be in
> software or virtual form factors, rather than in a physical appliance
>  form.

>I think you want to s/form factors/forms/.  (The phrase "form factor"
>seems to be abused to mean many things.)

Done - corrected to "forms" 

 >  Another example is that IPS/
 > IDS services for investment banking and non-banking traffic may be
 > separated for regulatory reasons.

> Is "investment banking" specific here, or does this statement also apply
to "banking" generally?  Or is "non-banking traffic" really
"non-investment-banking traffic" (in which case calling it "other traffic"
is probably better)?

Sue: Good point.  
New /
Another  example is that IPS/IDS services which splits traffic into
investment banking traffic and other data traffic to comply with 
regulatory restrictions for transfer of investment banking information/

>4.3.2.  Firewall Policy Deployment Automation
>
> Even though most vendors support similar firewall features, the
> actual rule configuration keywords are different from vendors to
> vendors, making it difficult for automation.
>
>Probably s/actual rule/specific rule/ or even just "specific".

Sue: 
New/
Even though most vendors support similar firewall features, the
          specific rule configuration keywords are different from vendors to
          vendors, making it difficult for automation.
/

4.3.3.  Client-Specific Security Policy in Cloud VPNs

/   Clients of service provider-operated cloud data centers not only need
/ to secure Virtual Private Networks (VPNs), but also [X] virtual security
/ functions that apply the clients' security policies.  
/There's an understood verb at the location marked [X].  I think it's
supposed to be "to secure", and if so, the usage is correct.  But it's hard
to read, so I think it would be better to not omit the verb.

Sue: You are right. The negation in the sentence makes this difficult. 

New /Clients of service provider-operated cloud data centers 
          need to secure Virtual Private Networks (VPNs) and virtual
          security functions that apply the clients' security policies./

Now the direct objection into a list (VPNs + virtual security functions).


4.4.  Preventing Distributed DoS, Malware and Botnet attacks

>   Many networks such as Internet of
>  Things (IoT) networks, Information-Centric Networks (ICN), Content
> Delivery Networks (CDN), Voice over IP packet networks (VoIP), and
> Voice over LTE (VoLTE) are also exposed to such attacks.
>
>This seems to be just a specialization of the preceding sentences.
>Does it add more information?  
>(E.g., perhaps there are special considerations for each of these types of
networks, in which case it might be useful to state that.)

Changed to:/
 Many networks
which carry groups of information (such as Internet of Things (IoT)
networks, 
Information-Centric Networks (ICN),  Content Delivery Networks (CDN), 
Voice over IP packet networks (VoIP), and Voice over LTE (VoLTE))
are also exposed to such remote attacks.  There are many examples of 
remote attacks on these networks, but the following examples will illustrate
the 
issues. A malware attack on an IoT network which carries sensor readings and
instructions may attempt to 
alter the sensor instructions in order to disable a key sensor. 
A malware attack VoIP or VoLTE  networks is software that attempts to place
unauthorized 
 long-distance calls. Botnets may overwhelm nodes in ICN and CDN networks so
that 
the networks cannot pass critical data.  
/

4.5.  Regulatory and Compliance Security Policies

  >Organizations are not only supposed to protect their networks against
   >attacks, but they should also adhere to various industry 
   >regulations:
>It's probably better to s/should also/must also/!

Thanks for noticing. 

7.  Security Considerations

>Having a secure access to control and monitor NSFs is crucial for
> hosted security services.
>Probably s/a secure/secure/.

>   Therefore, proper secure communication
> channels have to be carefully specified for carrying controlling and
> monitoring traffic between the NSFs and their management entity (or
> entities).

>I think you can condense this to "management entity(ies)", but you probably
should talk to the RFC Editor about it.

I will ask the RFC Editor about this point. 


>>   In addition, the Flow security policies specified by customers can
>> conflict with providers' internal security policies which may allow
>>   unauthorized traffic or unauthorized changes to flow polices (e.g.
>> customers changing flow policies that do not belong to them).
>I don't think you want to capitalize "flow" here.

Agreed, 

>It's not clear to me what "which may allow unauthorized ..." applies to.
It seems like there's an important issue in just
>   In addition, the Flow security policies specified by customers can
>  conflict with providers' internal security policies
>
>It seems that solving I2NSF requires a clear understanding of how the
customer's policies and the provider's policies interact.  (I would think
something is allowed only if both policies allow it, but the reality may be
more complex.)

>The rest of the sentence seems redundant given the discussion in the rest
of document.
>
> Therefore, it is crucial to have proper AAA [RFC2904] to authorize
> access to the network and access to the I2NSF management stream.
>
>It seems to me that this is a rather generalized need for I2NSF, and not
connected to the previous sentences.  So I would omit "Therefore"
>and put it as a separate paragraph.

Good catch. 


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


From nobody Mon Apr 10 09:05:20 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1543412957C for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 09:05:13 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.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 stA-DCv5TNIO for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 09:05:11 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::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 9451C12956D for <ietf@ietf.org>; Mon, 10 Apr 2017 09:05:07 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id g204so13043617oib.2 for <ietf@ietf.org>; Mon, 10 Apr 2017 09:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=UPM72sq92ZDu4opqFNzUO6qFYswQGFh9okmQcjhj6qA=; b=JYO9gr/R36dtSc3aBjtpSL1iQgWymi8w5R95X11Xr+9rZaduwz1qw6VMFoiscJZo+T oPFRGTFSenS39Oer5CfRZQzj8CxqucSRY9lFMzy4zlK5idSUP5lWPYvAzW5zAfd73JV5 Rf4oIk7yWf8hzl0GwiiWf3B4TFONrCt0dkUkyEY9unu0stuxFj9CydYSweAKUqLn974Z kDOWwY1iosHGDfmsQW+GtnjvN3i6+9J6mJ60n/Hep5S35pFRUC/12ndpu2lZxHgd1nyN lI6KUjgAuy+yOEOVKEsnx1QNeHwQSasIt/E5og3ksXcUD1Selkp1PpwQimfe0eVMZCA8 Ny2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=UPM72sq92ZDu4opqFNzUO6qFYswQGFh9okmQcjhj6qA=; b=qsCo0u8DM8ulHnLf5sDeNhvpzxXfodjRyPsZkrYpazqMCSl0j6GZmMrGW41QSxhT7C DKrtWJMydc6eBYl595waUQfTWQWZCWsbDuKMkBvbxqbYWwdXZYqEtBgA3d4TsHHYu0pU cMhN3SUxtkCmgEPz+Ft8ZurYknwYANR+mGTN0ksdHX7mVoTLSJtXsEq3qa4Zf3YedAnW 2E/GLmFoHRoIqlI8HjmbMx2x7WjXx6UdTHP8Vm9kHRLmG2Ct0g+lU5WabwGnHHIcFN8f mNdu+w6Wfz4z+CkYiYiimlpqi0l/nhiYhfngk8LFi6121MKc+gOh55SDt+fMwxnwbGzb Vzyw==
X-Gm-Message-State: AN3rC/6PMSuqrtgxYhMKE4H2jisNcFxGkm60auESNBL3AIVe9yNxpjeaFTyoVI6saLt+Nw==
X-Received: by 10.202.96.132 with SMTP id u126mr1797762oib.183.1491840306789;  Mon, 10 Apr 2017 09:05:06 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id y198sm6407011oie.8.2017.04.10.09.05.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 09:05:05 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
Subject: Re: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
To: "Acee Lindem (acee)" <acee@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com> <D50ED999.A7F47%acee@cisco.com>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <6f34a4cc-6492-a354-f257-412b0f5e84a1@outer-planes.net>
Date: Mon, 10 Apr 2017 10:05:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <D50ED999.A7F47%acee@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NJr0XIIoJ0p8zSU1Twvwq01N1HY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 16:05:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c
Content-Type: multipart/mixed; boundary="L4swmtKLJ5mrwTLR8UO1A3aCKF4QSjA3w";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: "Acee Lindem (acee)" <acee@cisco.com>, "gen-art@ietf.org"
 <gen-art@ietf.org>
Cc: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org"
 <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org"
 <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Message-ID: <6f34a4cc-6492-a354-f257-412b0f5e84a1@outer-planes.net>
Subject: Re: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
 <D50ED999.A7F47%acee@cisco.com>
In-Reply-To: <D50ED999.A7F47%acee@cisco.com>

--L4swmtKLJ5mrwTLR8UO1A3aCKF4QSjA3w
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Thanks for responding Acee, I look forward to the next revision.

Responses inline ...


- m&m

Matthew A. Miller

On 17/04/08 16:55, Acee Lindem (acee) wrote:
> Hi Matt,
>=20
> Thanks for the review.
>=20
> On 4/7/17, 1:58 PM, "Matthew Miller" <linuxwolf+ietf@outer-planes.net>
> wrote:
>=20
>> Reviewer: Matthew Miller
>> Review result: Almost Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-rtgwg-yang-key-chain-17
>> Reviewer: Matthew A. Miller
>> Review Date: 2017-04-07
>> IETF LC End Date: 2017-04-07
>> IESG Telechat date: 2017-04-13
>>
>> Summary:
>>
>> This document is almost ready to be published as a Proposed Standard,
>> once the issues noted herein are resolved.
>>
>> Major issues:
>>
>> NONE
>>
>> Minor issues:
>>
>> * Forgive me for my limited knowledge of YANG, but is there a reason
>> key-strings are only representable as either a YANG string or
>> hex-string type, and not the YANG binary type?
>=20
> Let me ask why I=C2=B9d want to use this type? I can get all the entrop=
y I want
> with a hex string and implementations are familiar with this
> representation. I=C2=B9m not really fond of the obscure base64 represen=
tation
> used by the YANG type and if one consults Benoit=C2=B9s search tool, th=
e type
> is not widely used. http://www.yangcatalog.org/yang-search/yang-search.=
php
>=20

Thanks for explaining.  I asked because (more) efficient transfer of
binary data has come up for other textual formats (read: JSON), and the
rough consensus was for base64.  That said, if the community is already
fine with hex, then I consider this a non-issue.

>>
>> * This document does not provide much guidance around AES key wrap
>> other than it can be used and the KEK is provided
>> out-of-band/-context.
>> For instance, AES key-wrapped key-strings probably require using
>> "hexidecimal-string".
>=20
> Yes - I=C2=B9ll add that.
>=20

Thanks.

>>  Also, assuming I'm reading the model
>> correctly,
>> it appears this feature applies to the whole chain, which I think is
>> worth calling out.
>=20
> In YANG, if you support a feature, it is for the entire model.
> The per-chain boolean indicates whether or not it is applies to all the=

> keys in that particular key-chain. I will clarify this.
>>
>> * This document warns against using the "clear-text" algorithm, which
>> the
>> reader is lead to understand is for legacy implementation reasons.
>> However, is there not a similar concern with cryptographically weak
>> algorithms, such as md5 and (arguably) sha1?
>=20
> I can add something for MD5.

Thanks.  I know I said arguably sha1, but at the apps layer it is
considered weak with in-the-wild tools able to produce collisions, which
leads to the minimum being sha256.

I would consider including a note about sha1 and md5, but I understand
that maybe operational realities are such that sha256 is not widely
deployed for these devices, or its not otherwise seen as a problem yet.

>>
>> Nits/editorial comments:
>>
>> * In Section 3.2. "Key Chain Model Features", the word "of" is
>> missing
>> between "configuration" and "an" in the phrase "support configuration
>> an
>> acceptance tolerance".
>=20
> Good catch. I will fix.
>>
>> Non-nits:
>>
>> * I note that idnits is calling out some odd spacing issues, but I
>> think
>> they are safe to ignore.
>=20
> Though the line numbers don=C2=B9t match the draft, I was able to fix t=
hese.
>=20
> Thanks,
> Acee=20
>>
>=20


--L4swmtKLJ5mrwTLR8UO1A3aCKF4QSjA3w--

--QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCgAGBQJY6602AAoJEOz0ck4QngW72r0H/1bMTPltgvYGOnyVUPmK95U/
dIj0sFlmyQpfaiiSnNgdBOw5mzkKsbyaaYdfBcCn+nI2HVc8o6rF+oLSREXYUywM
ZQ5AIU8lCmfVSQRald7QTk+AyWFrtsjNclwNaqy3yzYmq2I4XF3meP69w6T9TSce
bajwM47C6DebrWSvyBf94uc8pMcVIqXtcSeOLywJkvX4oU0NoIY/ejU7WMQZKwM5
sbrb/2YjXCtHaXwlKxJi+SRyeTaNY+wyLgN5PELNXNG5jtbwAF+PWiJFLWCC8Bos
dfq1bGQs18D1jJ0bCrd4iLHV1jcTO+tuwZMraKAXiXVdTJZTydGBOSeZwJ5piOY=
=JxPb
-----END PGP SIGNATURE-----

--QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c--


From nobody Mon Apr 10 09:31:36 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09034129562; Mon, 10 Apr 2017 09:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 cCvon_4EYswA; Mon, 10 Apr 2017 09:31:17 -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 1B777129566; Mon, 10 Apr 2017 09:31:08 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id r203so154162158oib.3; Mon, 10 Apr 2017 09:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2JVZHc7hX/az4HfFf4s/+OtOczCIPY/kINpgO+x1xLY=; b=aYHzaOqE6IdE7AZP0LWcfGKEJzk9y8hpXDBTm3BQIxnJsEg/dnuYReBqZgOqz6Gfg3 nSNSgPnuXSuOG+ECIyiHs3oD6ia3FhY0jXFw3C9ZsUHBLatAxuBF4WtdxotkuAm/5oCn n3pbQRkgof8OGAijQnv0c+Z2KO0dgKB7AoxRljC670z1LGI6lq/3LWyWXfR0IHFg0lbf VvIKT6NW+b8xL0qCVe5jlEu5fE7h7Vt/hemgWkLs1VkmSjvFEZcHh+E/zOwYjh+yGuUd 1d1tZ11zMiTSNrBHbaOL25iL6OExb3ALDAgqwFGOWhFVvoLiw5EaF5ZaFoG/FvZo9Sez htlA==
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=2JVZHc7hX/az4HfFf4s/+OtOczCIPY/kINpgO+x1xLY=; b=sWk/qx9m+BhKbiyrAjrQbBwMethVyz3twUqeldFMiZ+7HrqisQOk1053VUUPMZczkC DdDBiPu55usNMYW3tR4M5T8E0XA8xHZTZtRbaE/IevBprTabNv1AvA80fiYuHhpTt45X 6Iprgv7dp6NolJSYt+LBKTCJlK2bdbkDuRII1aoeCk9fTM1OTH8vTG+u/yP1wBN5Hk/6 +CIqX/h1mmS9pKnhTSKgq/PZxRrYu3YAClq/ukEIvp0D7UCzUwvcD4P+QaLX+x+z0JwX tSHkRwW8bKGs06EZRmaE+vwd7W+X71REfJuxCcFdoY+oVeb86AcAdV1dKHm+o0InVR0n Ta+Q==
X-Gm-Message-State: AN3rC/6gT0KGlwt/WiJy82/b56hNaEnWoO3+cgXaTTeFvO2O7PboiLgS25BfALbrH6Yudb6wP7IjCmlTr4PD1A==
X-Received: by 10.157.42.82 with SMTP id t76mr5477307ota.40.1491841867253; Mon, 10 Apr 2017 09:31:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.39.165 with HTTP; Mon, 10 Apr 2017 09:31:06 -0700 (PDT)
In-Reply-To: <CA+RyBmWLezQVyq+d5OZD3fM5-4EN-qCVTAJ-_LGX+4KmKUCTWA@mail.gmail.com>
References: <148977726052.13049.17633302885192133866@ietfa.amsl.com> <CA+RyBmWLezQVyq+d5OZD3fM5-4EN-qCVTAJ-_LGX+4KmKUCTWA@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 10 Apr 2017 09:31:06 -0700
Message-ID: <CA+RyBmWdwf55No_BELKz4TKHiMC-KzGKbmdJNS3zOBRNtiMmag@mail.gmail.com>
Subject: Re: Review of draft-ietf-ippm-twamp-time-format-05
To: Jon Mitchell <jrmitche@puck.nether.net>
Cc: ops-dir@ietf.org, draft-ietf-ippm-twamp-time-format.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Content-Type: multipart/alternative; boundary=001a113d09de8f0dbb054cd28017
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yodFC_1JDyI7yvEAuJsWcqqGIps>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 16:31:19 -0000

--001a113d09de8f0dbb054cd28017
Content-Type: text/plain; charset=UTF-8

Hi Jon,
apologies for the extended delay to address your comment. I'd like to add
the following just before the Section 2.1:

   Implementations of OWAMP and/or TWAMP MAY provide a configuration
   knob to bypass the timestamp format negotiation process and to use
   the locally configured values instead.

Hope it captures the idea of and addresses your comment.

Regards,
Greg


On Mon, Mar 20, 2017 at 10:34 AM, Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Jon,
> thank you for kind consideration of the draft and thoughtful comment.
> Indeed, TWAMP Test, and the time stamp format to be used, may be controlled
> by means other than TWAMP Control, e.g., local configurable knob exposed
> via data model or CLI. I'll work on text updates for the next version.
>
> Regards,
> Greg
>
> On Fri, Mar 17, 2017 at 2:01 PM, Jon Mitchell <jrmitche@puck.nether.net>
> wrote:
>
>> Reviewer: Jon Mitchell
>> Review result: Has Nits
>>
>> I have reviewed this document as part of the Operational directorate's
>>
>> ongoing effort to review all IETF documents being processed by the
>> IESG.  These
>> comments were written with the intent of improving the operational
>> aspects of the
>> IETF drafts. Comments that are not addressed in last call may be
>> included in AD reviews
>> during the IESG review.  Document editors and WG chairs should treat
>> these comments
>> just like any other last call comments.
>>
>> Ready with Nits - this draft adds the ability to use PTP timestamps as
>> an alternative to NTP timestamps for active performance measurement
>> protocols OWAMP and TWAMP.  Although this draft does a good job of
>> discussing interoperability for both sides of the session having or
>> not having support for this operational capability, in several places
>> it states that if a send/receiver support this capability it must be
>> set to 1 in the flags.  However, only for TWAMP Light mode, this seems
>> configurable.  This may just be my interpretation, but it probably
>> should state that local implementations MAY provide a configurable
>> knob to not negotiate PTPv2 timestamps in section 2.1 and 2.2 even if
>> the capability is supported by the implementation.
>>
>>
>>
>

--001a113d09de8f0dbb054cd28017
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Jon,<div>apologies for the extended delay to address yo=
ur comment. I&#39;d like to add the following just before the Section 2.1:<=
/div><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Implementations of OWAMP and/or TWAMP MAY provide a configurati=
on
   knob to bypass the timestamp format negotiation process and to use
   the locally configured values instead.
</pre></div><div>Hope it captures the idea of and addresses your comment.</=
div><div><br></div><div>Regards,</div><div>Greg</div><div><br></div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Mar 20, 20=
17 at 10:34 AM, Greg Mirsky <span dir=3D"ltr">&lt;<a href=3D"mailto:gregimi=
rsky@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi Jon,<div>thank you=
 for kind consideration of the draft and thoughtful comment. Indeed, TWAMP =
Test, and the time stamp format to be used, may be controlled by means othe=
r than TWAMP Control, e.g., local configurable knob exposed via data model =
or CLI. I&#39;ll work on text updates for the next version.</div><div><br><=
/div><div>Regards,</div><div>Greg</div></div><div class=3D"HOEnZb"><div cla=
ss=3D"h5"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri,=
 Mar 17, 2017 at 2:01 PM, Jon Mitchell <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:jrmitche@puck.nether.net" target=3D"_blank">jrmitche@puck.nether.net</a=
>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Jon Mitchel=
l<br>
Review result: Has Nits<br>
<br>
I have reviewed this document as part of the Operational directorate&#39;s<=
br>
<br>
ongoing effort to review all IETF documents being processed by the<br>
IESG.=C2=A0 These<br>
comments were written with the intent of improving the operational<br>
aspects of the<br>
IETF drafts. Comments that are not addressed in last call may be<br>
included in AD reviews<br>
during the IESG review.=C2=A0 Document editors and WG chairs should treat<b=
r>
these comments<br>
just like any other last call comments.<br>
<br>
Ready with Nits - this draft adds the ability to use PTP timestamps as<br>
an alternative to NTP timestamps for active performance measurement<br>
protocols OWAMP and TWAMP.=C2=A0 Although this draft does a good job of<br>
discussing interoperability for both sides of the session having or<br>
not having support for this operational capability, in several places<br>
it states that if a send/receiver support this capability it must be<br>
set to 1 in the flags.=C2=A0 However, only for TWAMP Light mode, this seems=
<br>
configurable.=C2=A0 This may just be my interpretation, but it probably<br>
should state that local implementations MAY provide a configurable<br>
knob to not negotiate PTPv2 timestamps in section 2.1 and 2.2 even if<br>
the capability is supported by the implementation.<br>
<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a113d09de8f0dbb054cd28017--


From nobody Mon Apr 10 10:32:40 2017
Return-Path: <aretana@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06FC1294EC; Mon, 10 Apr 2017 10:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Ndt6fal-EbCI; Mon, 10 Apr 2017 10:32:32 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4ED012947E; Mon, 10 Apr 2017 10:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2094; q=dns/txt; s=iport; t=1491845549; x=1493055149; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ilKWlMmlgb0EuOMIUmF06s8jkmHQOgPCZo0Kx+dFWHw=; b=SXFt2KXtQrOv5pNVuc1/OssVYEsI9BT1wHprifpRpVxkb5ErG+ZVVtzF SKPNbj62jpge/AZrMjgWI1x6Izc//Z7lPSGKOA1qf2SaKk93XA/J/3kkX xigCLaClhA6jBqqvSDruGYo1yEYw+CH9klCmXGr1OZze8kLuiDs2d2+UU A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DEAQBiwOtY/49dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTpx+CD4YkAhqDTT8YAQIBAQEBAQEBayiFFgYjEUU?= =?us-ascii?q?QAgEIGgImAgICMBUQAgQBDQWKD6kMgiaKfQEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?R2BC4VFggWCa4dcLoIxAQSWIIZbAZJYkUGTfwEfOEo7WxVSAYZIdYhSgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="229072990"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2017 17:32:28 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3AHWSsC029910 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 17:32:28 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 12:32:28 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 12:32:28 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Liubing (Leo)" <leo.liubing@huawei.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeAgABTw4CAA+NsAIAASqUA///utoA=
Date: Mon, 10 Apr 2017 17:32:27 +0000
Message-ID: <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
In-Reply-To: <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BCEC487E835CFC4387DBE1CB06065FF2@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uINYedQYURVnLenllYQb8C_R2kE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 17:32:34 -0000

V29ya3MgZm9yIG1lIQ0KDQpUaGFua3MhDQoNCkFsdmFyby4NCg0KDQoNCg0KDQpPbiA0LzEwLzE3
LCAxMDozNCBBTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2luc2JlcmdAY2lzY28uY29t
PiB3cm90ZToNCg0KQmluZy9Sb2JlcnQvQWx2YXJvIC0NCg0KSGVyZSBpcyB0aGUgZXhpc3Rpbmcg
dGV4dCBvZiB0aGUgU2VjdXJpdHkgU2VjdGlvbjoNCg0KICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBv
ZiBhdXRoZW50aWNhdGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJh
dGlvbiBhcyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQogICBGb3Ig
d2lyZWQgZGVwbG95bWVudCwgdGhlIHdpcmVkIGNvbm5lY3Rpb24gaXRzZWxmIGNvdWxkIGJlIGNv
bnNpZGVyZWQNCiAgIGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53YW50
ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KICAgbm90IGFibGUgdG8gY29ubmVjdCAoaS5lLiB0aGVy
ZSBpcyBzb21lIGtpbmQgb2YgcGh5c2ljYWwgc2VjdXJpdHkgaW4NCiAgIHBsYWNlIHByZXZlbnRp
bmcgdGhlIGNvbm5lY3Rpb24gb2Ygcm9ndWUgZGV2aWNlcyk7IGZvciB3aXJlbGVzcw0KICAgZGVw
bG95bWVudCwgdGhlIGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dl
cg0KICAgd2lyZWxlc3MgbGluayBsYXllci4iDQoNCg0KUHJvcG9zZWQgcmV2aXNpb246DQoNCiJJ
biB0aGUgYWJzZW5jZSBvZiBjcnlwdG9ncmFwaGljIGF1dGhlbnRpY2F0aW9uIGl0IGlzIHBvc3Np
YmxlIGZvciBhbiBhdHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZw0K
dGhlcmUgaXMgYSBkdXBsaWNhdGUgc3lzdGVtLWlkLiBUaGlzIG1heSB0cmlnZ2VyIGF1dG9tYXRp
YyByZXN0YXJ0IG9mIHRoZSBwcm90b2NvbCB1c2luZyB0aGUgZHVwbGljYXRlLWlkDQpyZXNvbHV0
aW9uIHByb2NlZHVyZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50LiANCg0KTm90ZSB0aGF0IHRo
ZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCmNvbmZp
Z3VyYXRpb24gYXMgaXQgcmVxdWlyZXMgc29tZSBtYW51YWwgY29uZmlndXJhdGlvbi4NCg0KICAg
Rm9yIHdpcmVkIGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0c2VsZiBjb3VsZCBi
ZSBjb25zaWRlcmVkDQogICBhcyBhbiBpbXBsaWNpdCBhdXRoZW50aWNhdGlvbiBpbiB0aGF0IHVu
d2FudGVkIHJvdXRlcnMgYXJlIHVzdWFsbHkNCiAgIG5vdCBhYmxlIHRvIGNvbm5lY3QgKGkuZS4g
dGhlcmUgaXMgc29tZSBraW5kIG9mIHBoeXNpY2FsIHNlY3VyaXR5IGluDQogICBwbGFjZSBwcmV2
ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJvZ3VlIGRldmljZXMpOyBmb3Igd2lyZWxlc3MNCiAg
IGRlcGxveW1lbnQsIHRoZSBhdXRoZW50aWNhdGlvbiBjb3VsZCBiZSBhY2hpZXZlZCBhdCB0aGUg
bG93ZXINCiAgIHdpcmVsZXNzIGxpbmsgbGF5ZXIuIg0KDQo/Pz8NCg0KDQoNCg0K


From nobody Mon Apr 10 10:36:12 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE319129A96; Mon, 10 Apr 2017 10:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 zk1vo9YZg61H; Mon, 10 Apr 2017 10:35:57 -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 8A16E1294EC; Mon, 10 Apr 2017 10:35:52 -0700 (PDT)
Received: from unescapeable.local ([148.87.66.203]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v3AHZgY8051381 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 10 Apr 2017 12:35:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [148.87.66.203] claimed to be unescapeable.local
Subject: Re: Genart last call review of draft-ietf-isis-auto-conf-04
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Liubing (Leo)" <leo.liubing@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com> <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
Cc: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
Date: Mon, 10 Apr 2017 13:35:39 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fo1GMf0o5pRKG9JfjXibgSviQ6o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 17:35:58 -0000

+1


On 4/10/17 1:32 PM, Alvaro Retana (aretana) wrote:
> Works for me!
>
> Thanks!
>
> Alvaro.
>
>
>
>
>
> On 4/10/17, 10:34 AM, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com> wrote:
>
> Bing/Robert/Alvaro -
>
> Here is the existing text of the Security Section:
>
>    "In general, the use of authentication is incompatible with auto-
>     configuration as it requires some manual configuration.
>
>     For wired deployment, the wired connection itself could be considered
>     as an implicit authentication in that unwanted routers are usually
>     not able to connect (i.e. there is some kind of physical security in
>     place preventing the connection of rogue devices); for wireless
>     deployment, the authentication could be achieved at the lower
>     wireless link layer."
>
>
> Proposed revision:
>
> "In the absence of cryptographic authentication it is possible for an attacker to inject  a PDU falsely indicating
> there is a duplicate system-id. This may trigger automatic restart of the protocol using the duplicate-id
> resolution procedures defined in this document.
>
> Note that the use of authentication is incompatible with auto-
> configuration as it requires some manual configuration.
>
>     For wired deployment, the wired connection itself could be considered
>     as an implicit authentication in that unwanted routers are usually
>     not able to connect (i.e. there is some kind of physical security in
>     place preventing the connection of rogue devices); for wireless
>     deployment, the authentication could be achieved at the lower
>     wireless link layer."
>
> ???
>
>
>
>


From nobody Mon Apr 10 11:06:01 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4911294E7 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:05:59 -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_50=0.8, RCVD_IN_DNSWL_MED=-2.3, 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 fMbqcMaASG6H for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:05:58 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 E88211296B0 for <ietf@ietf.org>; Mon, 10 Apr 2017 11:05:57 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v3AI5uPG017352 for <ietf@ietf.org>; Mon, 10 Apr 2017 14:05:56 -0400 (EDT)
Date: Mon, 10 Apr 2017 14:05:55 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170410180555.GA20454@gsp.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iCGcYHYcOE2rvV7ePhf_nA5cdM4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 18:06:00 -0000

On Wed, Apr 05, 2017 at 12:37:34PM +0200, Carsten Bormann wrote:
> On Apr 4, 2017, at 23:15, Rich Kulawiec <rsk@gsp.org> wrote:
> > 
> > the Wall
> > Street Journal is reporting today that a new set of procedures under
> > consideration will include demanding the phone passwords from *all*
> > foreigners entering the US.
> 
> https://www.wsj.com/articles/trump-administration-considers-far-reaching-steps-for-extreme-vetting-1491303602?mod=e2tw
> 
> Whoa.  *Not stable*.


The Guardian is now reporting that not only will passwords be demanded, but so
will financial information and that travelers may face ideological questioning:

	UK tourists to US may get asked to hand in passwords or be denied entry
	https://www.theguardian.com/us-news/2017/apr/09/uk-tourists-to-us-may-get-asked-to-hand-in-passwords-or-be-denied-entry

Further, as the secondary headline says:

	Although mitigation options exist, lawyers warn attempts to
	protect personal data may be seen as "probable cause" for searching

---rsk



From nobody Mon Apr 10 11:28:11 2017
Return-Path: <prvs=12734d7f60=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4794E1296B0 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:28: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oaepXS_Z7lKv for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:28:06 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E96E112947E for <ietf@ietf.org>; Mon, 10 Apr 2017 11:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491848883; x=1492453683; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=RjTFYvvwV/CcjSeo5bi8wExdD afzsGUU8Ey0Vn/4/Pk=; b=RaF/hAsIO73ki5v7pjnNsjpc9EH6HSvsNZ8ISjOKx jlQ1TzBdEQKeVQrXA9SIIdbIvo5hwiGIxxFYMoLRSnXaZsOf06ysOOCTvE0g6i2C JKWS+gB8gOR9ScDVRrTtB8iyePD/O9mXli4RZvpuKAq13rigFlqBRqxXKrkXmRuf 2A=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=RAeOfvtifZOPGA7XB3xiNuNapiIt29ZqAJGGwu83PSBepV8n9iOmjN3cGkSk P6HK4uN/nl1iDRqustWIfymmZEz/U73pxQHIqJXwX70PzojDiLdUJbve3 YUt00nP+q0AQGkWAqXTx5e1mgGfnUta3XZcIKq970PM63NbUaJFYjc=;
X-MDAV-Processed: mail.consulintel.es, Mon, 10 Apr 2017 20:28:03 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 10 Apr 2017 20:28:02 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005405795.msg for <ietf@ietf.org>; Mon, 10 Apr 2017 20:28:01 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170410:md50005405795::W9We3GG5tb3rCuxW:00002cq6
X-Return-Path: prvs=12734d7f60=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Mon, 10 Apr 2017 20:27:58 +0200
Subject: Re: IAOC -- looking for committee volunteers
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>, <iaoc@ietf.org>
Message-ID: <4D708CA7-AFE6-4023-9591-B781DE576655@consulintel.es>
Thread-Topic: IAOC -- looking for committee volunteers
References: <149149603842.22056.14285846839847949929.idtracker@ietfa.amsl.com>
In-Reply-To: <149149603842.22056.14285846839847949929.idtracker@ietfa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ofYgialjF5kYWn9KJuE9oFHiWVs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 18:28:08 -0000

Once more, as I indicated in November last year. I fail to see ANY RFC that=
 confirms that the IAOC itself is empowered by the community to select more=
 committee members in a very obscure way, and as Leslie indicated based on =
=E2=80=9Cpersonell decisions=E2=80=9D. Clearly not transparent at all.

Why, if committees need more participants, which I understand because the i=
ncrease of the workload, and knowing already since several months ago that =
this is a thread, and that the NomCom have candidates to participate.

We have got an opportunity to ask the NomCom to work on extra candidates si=
nce some people was appointed already in November.

If there is no RFC allowing it, clearly this is a decision that MUST be app=
ealed, as it is totally against the IETF spirit.

Regards,
Jordi
=20

-----Mensaje original-----
De: IETF-Announce <ietf-announce-bounces@ietf.org> en nombre de IAOC Chair =
<iaoc-chair@ietf.org>
Responder a: <ietf@ietf.org>, <iaoc@ietf.org>
Fecha: jueves, 6 de abril de 2017, 18:27
Para: IETF Announcement List <ietf-announce@ietf.org>
Asunto: IAOC -- looking for committee volunteers

    The IAOC has a handful of committees to support its work [1].  The role=
 of an IAOC Committee is to develop materials and make recommendations for =
IAOC decisions. Chair and membership in committees is constituted annually;=
 we will be undertaking that at the IAOC retreat scheduled for late April t=
his year.
   =20
    At this time, the IAOC is again interested in broadening non-IAOC membe=
r participation in its committees, if there are one or 2 interested and sui=
table community members for each committee.   Note that all committees deal=
 in business sensitive materials, and may require signing a non-disclosure =
agreement.
   =20
    Please see the charters of the individual committees for further detail=
 [1].    Committees for which we are considering additional people are:
   =20
    	. Finance Committee
    	. Legal Committee
    	. Meetings Committee
    	. Technology Management Committee
    	. RFP Committee
            . Sponsorship Committee (in formation)
   =20
   =20
    We ask those interested to volunteer by sending a message stating their=
 committee of interest and relevant experience for that committee to iaoc@i=
etf.org, by April 20, 2017.  The IAOC will review candidates with the aim o=
f appointing any new members by late April.
   =20
    Thanks,
   =20
    Leslie, for the IAOC.
   =20
    [1] https://iaoc.ietf.org/committees.html
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Apr 10 11:55:08 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7DE1273B1 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:55:06 -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 tC1YB_bQzlk2 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 11:55:05 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 EC9A01200DF for <ietf@ietf.org>; Mon, 10 Apr 2017 11:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3AIsnup011850; Mon, 10 Apr 2017 20:54:49 +0200 (CEST)
Received: from client-0078.vpn.uni-bremen.de (client-0078.vpn.uni-bremen.de [134.102.107.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w1zrT2nwxzDJJQ; Mon, 10 Apr 2017 20:54:49 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20170410180555.GA20454@gsp.org>
Date: Mon, 10 Apr 2017 20:54:48 +0200
Cc: IETF <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 513543288.726994-6fb4483c8e974364d608408fc74c9c28
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5q4nUsT2oCaR5zZnaP0dCQnxQDg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 18:55:06 -0000

Another salient passage from the article:

=E2=80=9CIn the short to medium term, I think the answer is going to be =
avoiding all but absolutely essential travel to the United States,=E2=80=9D=
 Hall [a UK lawyer] added. =E2=80=9CI=E2=80=99m aware of at least one =
conference on cyber security and ethical hacking which switched to =
Toronto at short notice because of these concerns.=E2=80=9D

When I returned from Chicago, my wife (also a computer science =
professor) asked me:=20
=E2=80=9CSo how was the final visit you will ever have made to the =
USA?=E2=80=9D
She may have been more right than I thought at the time.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Apr 10 14:06:05 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1CA5129AF1 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 14:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6o1gEcA8-ygI for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 14:05:56 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::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 7180B129AE7 for <ietf@ietf.org>; Mon, 10 Apr 2017 14:05:53 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id h125so77240340lfe.0 for <ietf@ietf.org>; Mon, 10 Apr 2017 14:05:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uY+ZWiMTikzHKGLahLoIrIXGPDdbwXLyIc00qcaOi6Q=; b=uOVY/GNVaAq+QJ5J1C3ItfPcHrqoMnIa4f5yR4XJLxUn7Pvo+cVWp3HCi70hlUJceS iX2pXvhtduymvXnOQhQP0sFJjMgiQvTv0B67jUB9C7BFmWtzNgsKEbQ+iHD5fmau5XU/ PqKn74Vy4kK6xDSmz+E0L4RzOulRmdIGBh8d4jiZIjO4cHNZcXYIWiPy1/+YlYRN639D LxaQkrA/0BUNg2W/rjX19Ku1iv8InvDskIbhiwV1a+wKXhx4AyHPtja2/Ffcg3j0FhSj NGJl4mx7Zfp+ZjiTU/mYIGsib4qAVizGyLhYCprHjy5C8BAjOL3a42oRfxrqSaTe7ncJ wv7g==
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=uY+ZWiMTikzHKGLahLoIrIXGPDdbwXLyIc00qcaOi6Q=; b=CvYqClbPr+9of2KMNLOk83aWeN23JqUhWtiSjL4oAW2FZBYiE+lq6otERIFOwr55sc 16huuaoz6LyrGkA7Chv/eiriEN6Oh7tqynTdxqG/j0o75b/4jLmDHB2iZ2Yz7nPz/bkB S0UJK175Ft9fdugV037gJGsGs0sr2k0vACTX1Qc0hVEdEQVwpBK5cvBGEkg9o2v4kXHI g0dh+GAJq52Cq03msAkYNUmEJbzjZQseQNd063gJM8zOtH+faaGaCr/0MZdb3XYTlmva vT2vXKLEsp63xX9XLwaoXT8HAzCsM1lStYIWBGVyRtQG0AO2wYHEOR/xC3yqalH10gIE VT7Q==
X-Gm-Message-State: AFeK/H3AqQM0j/4b+7S5GduUwoBwd/SDArfPMeRSP6LylMhFkAEpsCyKbKG98kokPVyejB/aZBt/T1H42Kwriw==
X-Received: by 10.25.76.193 with SMTP id z184mr15733327lfa.43.1491858351243; Mon, 10 Apr 2017 14:05:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.5 with HTTP; Mon, 10 Apr 2017 14:05:49 -0700 (PDT)
Received: by 10.46.83.5 with HTTP; Mon, 10 Apr 2017 14:05:49 -0700 (PDT)
In-Reply-To: <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 11 Apr 2017 07:05:49 +1000
Message-ID: <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114b060c14c8e2054cd6572d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6dBVElerIA38Ql992_45_g1ZQG8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 21:06:02 -0000

--001a114b060c14c8e2054cd6572d
Content-Type: text/plain; charset=UTF-8

I most certainly reviewed 09. I haven't reviewed the diff. I doubt that it
would change my opinion on the macro - level problems.

On 8 Apr. 2017 3:34 am, "Kathleen Moriarty" <
kathleen.moriarty.ietf@gmail.com> wrote:

Hello Martin,

Thanks for your review.  It seems that you have read version 8 or
earlier and not the current version, 9, from some of your suggestions
that have been corrected already.  Your review also reads to me that
additional context setting may help, but please note that some context
setting was improved in version 9.  We re-arranged some of the
sections per IESG review recommendations in the latest version as
well.

Perhaps you have additional language suggestions for context setting?

The abstract states:

   Increased use of encryption impacts operations for security and
   network management causing a shift in how these functions are
   performed.  In some cases, new methods to both monitor and protect
   data will evolve.  In other cases, the ability to monitor and
   troubleshoot could be eliminated.  This draft includes a collection
   of current security and network management functions that may be
   impacted by the shift to increased use of encryption.  This draft
   does not attempt to solve these problems, but rather document the
   current state to assist in the development of alternate options to
   achieve the intended purpose of the documented practices.

which is repeated again in the introduction, but slightly reworded.
The introduction also includes statements on the existing publications
related to encryption and I read them as not having any bias, but
rather supporting the existing documents that also had consensus.

A couple of comments and one question inline.

On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> Draft: draft-mm-wg-effect-encrypt-09
> Date: 2017-04-07
>
> Overall
>
> This document is unfocused and unclear in its intent.  It is filled with
> unsubstantiated claims, misleading statements, bias, and implied
recommendations
> for bad practices.  I would oppose its publication in the current form.
> Furthermore, I don't believe that small scale or editorial changes would
be
> sufficient to correct these problems.
>
>
> Aside from weakening its utility and/or arguments, the lack of focus will
allow
> this document to be abused in various ways.  For instance, it might imply
IETF
> endorsement of the practices described in the document.  Given that the
IETF has
> published positions that in some cases reject these practices, this
document
> needs to be very precise with its claims.  In its current form, it is not
nearly
> careful enough.
>
> If this document is going to be published as an RFC, then it needs to be
very
> clear about its intent and its position - or lack thereof - toward these
> practices.  It might be possible to say that these practices were
employed in
> networks in the past and that encryption is reducing the viability of
those
> practices.  A value-neutral statement like that might be acceptable as
long as
> it were framed carefully.
>
> What is problematic is the implicit argument that is presented.  This
document
> could easily be construed as the IETF legitimizing these practices.  This
> includes things on which the IETF has published statements (see for
example RFC
> 2804).

See the abstract and introduction and summary.

>
> This steps firmly into to sticky mess that is the politics of encryption
policy.
> If the IETF is going to make a political statement with this document,
then that
> statement needs to be a lot better than this.
>
> Furthermore, any statement needs to be consistent with previous
statements,
> where in this case that primarily means RFC 7258.  Right now it reads as
an
> attempt to dilute RFC 7258.

Not at all.

>
> If this document were more clearly formulated as an even-handed treatment
of
> what happens today - without judgment - then it could be useful.  Here
the model
> of RFC 7754 is a good one.  It describes the different facets of a use
case,
> then the different practices that might be employed to achieve that
goal.  For
> each practice the pros, cons, and technical limitations are covered with
an eye
> to all involved parties.
>
>
> The Real Purpose of this Document
>
> I think that this is the real question that this document wants to ask is:
>
>    In a world where we are forced to defend against pervasive monitoring
by
>    motivated and malicious actors, can we find a role for less pervasive
>    monitoring by well-intentioned entities?
>
> There is an interesting discussion to be had here, but I'm convinced
after my
> review that this document is the wrong vehicle for that discussion.  I'm
also
> inclined to suggest that this is the wrong question to ask in the first
place.
>
> To the extent that we have the tools necessary to protect against
pervasive
> monitoring, we have to accept that more-legitimate uses of monitoring are
> collateral.  Mostly, that's just a function of the limitations of the
imperfect
> tools we have.
>
> The value in this document is in the rather comprehensive collection of
use
> cases.  Sure, some we might not attribute much weight to, like
wiretapping.
> Others are frankly frightening and not just in the Orwellian sense.
>
> The problems that are implied by the current practices of network
operators is a
> large vein of unexplored work for the community.  Spending effort on
finding
> better solutions to legitimate problems is worthwhile.
>
> In other words, the right question might be:
>
>    For each of these practices that we see today, are the use cases that
>    motivate them legitimate and how might be implement alternative
techniques
>    that properly respect privacy and security?
>
>
> Two- and Three- Party Interactions
>
> A great many sections of the document are unclear about the relationships
> between different actors.  It seems like many of the activities describe,
which
> are presented here as being beneficial, are performed by a third party
without
> the consent or involvement of the two communicating peers.  After all,
those are
> the cases where encryption most often interferes.
>
> The assertion that some benefit is accrued to communicating peers as a
result of
> these actions is the constant subject of the text.  I observe that in
most of
> the cases listed in this document, the benefit is accrued primarily to
the third
> party.
>
> Clarity around the arguments that the document makes with respect to
benefits to
> each of the involved parties is sorely lacking.
>
> In addition to this, where benefits truly do accrue to communicating
peers,
> technical options that don't rely on privacy-invasive techniques are
routinely
> dismissed in an offhand fashion.  In this way, any moral imprimatur
attributed
> to the use case is used to justify the privacy-invasive method.
>
>
> Document Structure
>
> This document is very hard to read (and review).  Probably my biggest
complaint
> is that the sections are haphazardly organized.  They contain a mixture
of use
> cases (what does SP X want to do) and techniques (how do they do these
things).
> Material is duplicated between sections.  Sections cover 10 different use
cases
> while talking about techniques, then other sections talk about different
> techniques whiles talking about a scenario.  This leads to a lot of
repetition.
>
> There are three axes that this document contemplates:
>
>  - the techniques that are currently used in networks
>  - the use cases that motivate these techniques
>  - the deployment scenarios in which these use cases manifest
>
> It would appear that the document attemps to start from the deployment
> scenarios.  However, this causes use cases and techniques to be mixed.
> Judicious use of cross-referencing might have made this arrangement
tractable,
> but there are virtually no cross references.
>
>
> Section 1
>
> I find the introduction of this document difficult to parse.  I think
that what
> it wants to say is pretty straightforward, but it manages this in quite an
> obtuse way.  Here's what I think that it is trying to say:
>
> 1. The IETF (and the larger community) has reacted to revelations of
pervasive
>    monitoring by increasing the use of encryption.
> 2. That has been somewhat successful.
> 3. More encryption has an impact on some practices that network operators
have
>    become accustomed to employing.
>
> Expressed in this way, you can see how you could make a value-neutral
> statement.
>
> On the first, you can definitely make an argument based on the documents
that
> the IETF have published.  However, it is a mistake here in assuming that
the
> IETF - or the revelations of global-scale surveillance - is directly
responsible
> for the uptick in adoption of cryptographic protection for Internet
traffic.
> This is something that the community as a whole has been working towards
for
> many years; these trends predate the actions this draft focuses on.  This
is
> particularly true for the hosted provider cases in Section 3, where
business
> motivations for protection are far stronger than any concerns over
government
> surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I
don't
> have to write a statement that will be labelled as having IETF consensus.
>
> The immediate focus on opportunistic security is highly misleading,
especially
> in the web case.  The amount of opportunistically secured web traffic is
> miniscule by global standards.  Since Firefox is the only browser to
support OS
> for the web, so adjust the following by market share: <
https://mzl.la/2oc46ch>.
>
> I understand that mail is more often opportunistically secured, and you
will
> hear the virtues of OS sung from the rooftops, but all evidence suggests
that
> this is just a transitory state.  Instant messaging is closer to the web
case,
> with the trend toward strong protections that include authentication.  Of
> course, I don't believe that mail or instant messaging represent any
significant
> traffic volume, so you need to be very careful about the nature of the
claims
> that are being made.  It has to be that the volume of mail has to be a
rounding
> error when it comes to capacity planning for networks.
>
> On the second point, when making claims about prevalence of encryption, I
would
> advise caution when citing statistics.  Here's the graph for the Mozilla
figures
> that I think are being cited <https://mzl.la/2obZjrb>. Here's a different
graph
> with a different number <https://mzl.la/2oc263J>.  This highlights the
point
> that statistics need to be carefully cited, because bare claims are
difficult to
> assess.  Methodology matters when it comes to these sorts of claims - are
we
> talking proportions of packets, requests, flows, or something else?
> Furthermore, the citations in the document are made more difficult to
assess by
> being measured at very different times (where the two I cite here were
made at
> roughly the same point in time).

For the Mozilla statistics, Richard Barnes had reviewed the text after
providing the statistic as he wanted to make sure it was stated
clearly raising the same concerns you do about statistics.  Do you
have further text suggestions to clarify this statistic?

Thank you,
Kathleen

>
> The statistics do support the notion that there is a significant amount of
> encryption in use, but it would appear that the claim is that the amount
of
> encryption is *increasing*.  This is not an extraordinary claim, but no
evidence
> is offered in support of the claim.  It isn't a certain thing either.
>From the
> statistics that I have access to, there was a definite uptick in October
of
> 2015, but the rate appears to be stable since then.
>
> It appears that the remainder of the document is intended to address the
third
> of my points in some detail.  That's a good structure in theory, but see
above.
>
> I don't think that the "service provider" taxonomy works for this
document.
> Based solely on the structure of the document, the only service provider
that
> this document concerns itself with is the one who forwards the packets.
That
> application service providers are involved as one of the endpoints is
relevant
> in some cases, but not all.  For that reason, I prefer "network operator"
and to
> use specific terms like "mail host" or "web server" as appropriate to the
> context.
>
>
> Section 2 (top section)
>
> I like that the attacks on SMTP by network operators is highlighted here.
>
> There's an implicit argument here that runs counter to established IETF
> consensus.
>
>    Some methods used by service providers are impacted by the use of
encryption
>    where middle boxes were in use to perform functions that range from
load
>    balancing techniques to monitoring for attacks or enabling "lawful
>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>
> This fails to remain neutral.  This implicitly makes a value-judgment
about
> relative morality/acceptability/value of certain practices.  What is
> particularly insidious about this particular form is that it invites
> interpretation that is subjectively coloured.  For instance, as a non-EU
and
> non-US citizen, I might consider the use of the particular lawful
intercept
> techniques offensive; thus I might interpret this as a spectrum between
> inoffensive to offensive.  An employee of the US government might view
this
> somewhat differently and interpret this as a scale between low-value to
> high-value.  I'm guessing here, but this is really just to highlight my
point
> about care.
>
> A more serious concern is this statement:
>
>    The loss of access to these fields may prompt undesirable security
practices
>    in order to gain access to the fields in unencrypted data flows.
>
> I've read this argument before (see https://queue.acm.org/detail.
cfm?id=2508864
> for the long form), and it might even have an element of truth to it.
However,
> it's not a statement that I personally attribute any real credibility to,
and
> nor do I think that it needs to be credited with any amount of
seriousness.  I
> certainly disagree with the IETF making any such statement.  It says that
we are
> collectively willing to bow in response to (anticipated) threats of
violence.
>
> Section 2.1
>
> This is one of the few sections that talk about what it means to operate a
> service as opposed to operate a network.
>
> Overall, this section doesn't work particularly well.  The distinction
between
> integrated and standalone load balancing is an interesting division, but
it
> doesn't leverage this distinction well.  What causes a standalone
load-balancer
> to be necessary?  Is this something a network operator uses?  I see text
on NFV
> later, but it's far removed from the original text and it seems
aspirational
> rather than concrete.  On the other hand, many of the concerns in this
document
> simply don't apply to an integrated load balancer.
>
> The amount of text on QUIC here is surprising.  Given how much of QUIC is
> changing right now, we shouldn't publish a document that attempts to make
claims
> about what QUIC is or how it is operated.  This attempts to dive into the
> details of QUIC connection migration in a way that presumes much about the
> outcome of issues that the QUIC working group is still struggling with.
>
> I would strongly recommend removing QUIC-specific language from this
section and
> the document as a whole.  We have an operational document in the QUIC
working
> group that would be a good venue to discuss some of these concerns.
>
> Is this an oblique reference to (the much-loved) RFC 7974?
>
>    Current protocols, such as TCP, allow the development of stateless
integrated
>    load balancers by availing such load balancers of additional plain text
>    information in client-to-server packets.
>
> Otherwise, I don't know what it means.
>
> BTW, I like this parenthetical:
>
>    (That said, care must be exercised to make sure that the information
encoded
>    by the endpoints is not sufficient to identify unique flows and
facilitate
>    Persistent Surveillance attack vector.)
>
> I'm going to take this to the QUIC working group, because QUIC certainly
doesn't
> meet that bar right now.  It fully facilitates Persistent Surveillance in
its
> current form (proper noun?  I haven't really seen that term before, even
though
> it draws a neat parallel with Pervasive Surveillance).
>
> Editorial:
> * "pop" is a term of art that needs explanation.
> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - the
>   possessive form for the inanimate.
> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>
> Section 2.2
>
> I think that this sums the situation up reasonably well.  It fails the
> value-neutral test in a few ways though.  As I understand the situation,
> surveying operates at many levels.  For accurate planning, models of
endpoint
> behaviour are used to determine things like whether loss or congestion is
> affecting throughput.  Really good models require knowledge of what users
are
> attempting to do and the applications they are using (as mentioned,
things like
> browser version matter in these models).  For instance, it isn't enough to
> understand that the user is trying to receive 720p video, you also have
to know
> that a 4k stream for the same content is available.
>
> The degree to which these models are privacy-invasive is not even
acknowledged.
>
> Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect
that
> subtlety to be lost on many readers though.
>
> Section 2.3.1
>
> I find this sad, even if I can recognize the truth of it:
>
>    A monitoring system could easily identify a specific browser,
>    and by correlating other information, identify a specific user.
>
> As a browser vendor, we don't consider this to be a feature, it's a bug.
>
> Section 2.3.2.1
>
> This is a strange section under which to put caching.  Caching is a use
case
> akin to compression.  I don't see it as belonging to the class of things
that
> rely on DPI.  You just intermediate the cleartext HTTP in the way that
RFC 7230
> recognizes.  Note that RFC 7230 explicitly does not endorse the practice
of
> transparent proxying for a range of reasons, not the least of which is the
> complete lack of transparency (yep).
>
> Section 2.3.2.2
>
> Again, it's strange to see differential treatment under DPI.  I was
fairly sure
> that fingerprinting was used here as well.
>
> Section 2.4
>
> This section doesn't even attempt to recognize that applications are much
better
> now at scaling content to suit the device on which that content is
intended to
> be consumed.  It should.
>
> This section should not represent compression as an unmitigated good.
I'm told
> that significant damage can be done to video streams by "well-intentioned"
> compression middleboxes.
>
> Yet again I see a call back to the implicit threat of violence in "they
will
> adopt undesirable security practices".  Statements in that form have no
place in
> IETF RFCs.
>
> Section 2.5
>
> This mentions RFC 7754 then blithely ignores its primary conclusion.
Generally,
> The treatment in RFC 7754 of this subject is more even-handed.
>
> The use of particular examples (betting, gambling, dating) shows cultural
bias.
>
> Jargon warning: "core network", "the mobile network" ("the"?)
>
> Section 2.5.2
>
>    This type of granular filtering could occur at the endpoint, however
the
>    ability to efficiently provide this as a service without new efficient
>    management solutions for end point solutions impacts providers.
>
> The initial premise here (up to the first comma) is the conclusion of RFC
7754.
> I disagree with the conclusion, and I suspect so does RFC 7754.  In
scenarios
> where this matters, endpoints are routinely managed centrally.  The range
of
> options for this sort of management are plentiful and diverse.
>
> Section 2.5.3
>
> This describes a captive portal, which in the case where the service
provider
> has a relationship with their customers, seems like a poor solution.  See
the
> CAPPORT working group for ways in which people are actually working on a
> solution to this problem.
>
> Section 2.6
>
> The capitalization of section headings is inconsistent here (and
throughout).
>
> Section 2.6.1
>
> Isn't this a duplicate of Section 2.1?
>
> Section 2.6.2
>
> I can't parse this statement:
>
>    Approved access to a network is a prerequisite to requests for Internet
>    traffic - hence network access, including any authentication and
>    authorization, is not impacted by encryption.
>
> And then we get into zero rating, which is a hot-button topic.  No
> acknowledgment given to the sensitivities on the subject, or even a
superficial
> exploration of the technical options that are available.
>
> This text references a non-existent Appendix.
>
> Section 2.6.5
>
> This paragraph is strange.  It starts by describing what appears to be
use cases
> (are those scare quotes?).  It finishes by implying that these are
attacks on
> privacy (which they are).
>
> What is "Non-Customer Proprietary Network Information"?  I hope that this
isn't
> an attempt to somehow privilege the information so that it seems less than
> privacy-invasive.
>
> Section 2.7
>
> This is one of the areas that is most legitimately affected by increased
> adoption of encryption.  I have no doubt that having detailed information
about
> the application and its use makes the process of troubleshooting easier.
>
> This is the first mention in the document of network-based optimization.
Was
> the section describing that cut from an earlier draft?
>
> The use of websockets as a primary example is an odd one.  It's just not
that
> common.  For reference, we see >20% failure rates on encrypted websockets
and
>>50% failures in the clear; no one in their right mind would rely on
websockets.
> If the point is that HTTP is carrying more traffic (see
> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
just that
> would be more effective.
>
> Section 3
>
> It would help if "hosted environments" was defined before diving in.
>
> Section 3.1
>
> The paragraph on DLP is ironically amusing.  Encryption exists to prevent
> private information leakage, but the assertion here is that encryption is
> hampering DLP attempts.
>
> It's true that protection of intellectual property is an important
business
> goal, but this handling suggests an architecture that I'm fairly sure is
counter
> to established wisdom (see "SSL added and removed here :-)":
> https://www.washingtonpost.com/rf/image_404h/2010-2019/
WashingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-
EXPLOITATION1383148810.jpg).
> Worse, this casually dismisses a model that is actually more likely to
work.
> Malware encrypts too (https://arxiv.org/abs/1607.01639).
>
> Section 3.1.1
>
> Who is the customer here?
>
> Why does the hosting provider need to monitor access?  They have the
ability to
> limit accesses, but this is suggesting that what happens within the
envelope of
> what they permit is important for them to know.  I'd be surprised if you
could
> show that this is true.  Hosting providers - in my experience - value
their
> ongoing business and would not jeapardize it by snooping on their
customers.
> It's different if the customer opts in to a security service, but that
> demonstrates a cooperative situation, where the rest of this document is
largely
> concerned with adversarial uses of encryption.
>
> Section 3.1.2
>
> This is another example where the organization of the document could
> be improved.
>
> Again with the "SSL added and removed here :-)" recommendation.  PCI don't
> permit that for good reason.
>
> Section 3.2.1
>
> I don't believe that monitoring of these types of application require
cleartext
> access.  There are two parties involved: the provider of the application
and the
> user of it.  The provider has most of the power here and can theoretically
> design the system to allow whatever level of access they require.  To the
extent
> that the user needs protection from the application provider, that is a
matter
> of negotiation between them.
>
> I don't see how the adversarial three-party situation presented in the
rest of
> the document applies in this situation.
>
> Section 3.2.2
>
> No real mention of the effect of encryption here, or is this just saying
that
> there is no issue here?
>
> I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of
the IETF
> saying things like "PGP may be a front runner" though.
>
> Section 3.3
>
> There's certainly a lot of detail here, but I had a really hard time
extracting
> value from this section.  I can't see how data storage is fundamentally
> different to the general case of an application provider.
>
> Section 4.1.1
>
> I appreciate the recognition that endpoint-based techniques work.  The
> implication that this isn't the obvious solution, much less so.
>
> Section 4.1.2
>
> I'm confused about the purpose of this section.  This seems to be talking
about
> the sort of network-based methodologies an application provider might
employ to
> ensure that their application is working as intended.  Why would the
application
> provider not have access to detailed logging and usage metrics?
>
> As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is
cited no
> fewer than three times in the same paragraph.  It makes some fairly bold
claims
> about its effect on privacy that I don't believe will hold up to analysis.
>
> Section 4.1.3.1
>
> This section correctly identifies the issue as one of shortcomings in
logging,
> not increased use of encryption.
>
> I would have stopped there, but the section persists and ultimately
references
> RFC 7974, which is widely recognized as a monstrously bad idea (the IESG
note is
> fairly clear on this point).
>
> Section 4.1.3.2
>
> "HTTP/2", not "HTTP2".
>
> I don't see how this section belongs in this document.  The 1:1
correlation
> between actions and flows in HTTP was a mistake of the 1980s that we've
spent a
> lot of time on correcting (sometimes unsuccessfully, see pipelining).
>
> Section 4.1.3.3
>
> It's not a "service call" it's just a request.
>
> Section 4.2
>
> If the inclusion of a reference to RFC 7457 is to support a claim that
TLS is
> attacked, that's sailing far too close to an endorsement of attacks than
I am
> comfortable with.  However, I don't believe that any of the listed attacks
> remain viable in modern applications.  What is most often the case is
that a
> trust anchor is installed on enterprise users' machines and new
certificates are
> minted as needed.  In other words, the host that is accessing the HTTPS
site is
> owned by the enterprise and modified so that it can comply with its
policies.
>
> When you recommend attack like this (to be clear, I would oppose
publication of
> text that does this), you need to acknowledge the downsides.  For
example, MitM
> devices routinely break connections, they hide the true security status of
> communications from endpoints and users, they frequently implement weaker
> versions of protocols, they often don't include the same degree of rigor
in
> things like certificate validation, and probably many more things that I
can't
> casually list off the cuff.
>
> The discussion of caching here warrants a new section.
>
> Section 5.1
>
> s/effect/affect
>
> No complaint here, just an advertisement for technical solutions that
aren't
> affected by increases in encryption.  Good, though I'm not sure if the
section
> meets the document's criteria for inclusion.
>
> Section 5.3
>
> No cititation for APWG.  Not an IETF working group from what I can see.
>
> There's a presumption here that administrators need to perform these
tasks.  Why
> can't endpoints do this?  It would certainly be a whole lot less invasive
that
> way.  Take a look at how browsers implement checks for "bad" sites (which
> include phishing sites).  These methods have some fairly significant
privacy
> safeguards without compromising on performance.
>
> Section 5.5
>
> See my comment about about endpoint-based methods.
>
> Section 5.6
>
> I believe that the spoofed source address problem is not relevant to this
> document.  It's a fairly well understood problem.  That said, if we could
wave a
> magic wand and get BCP 38 deployed, that might be nice.
>
> Section 6.1
>
> As this says, it's fairly well understood that - for HTTP - SNI is used.
The
> point that it is optional is interesting, but doesn't deserve the amount
of
> attention this section devotes to it.  The clients that don't include SNI
are in
> a diminishing minority.
>
> That said, this doesn't pay any attention to another feature in HTTP/2:
> connection coalescing.
>
> Section 6.2
>
> ALPN will be encrypted in TLS 1.3.
>
> Section 6.3
>
> This reads as a invitation to perform traffic analysis (a statement that I
> oppose).  Note that we have added padding to most recent protocols
(HTTP/2 and
> TLS 1.3 in particular) to give endpoints the ability to resist this sort
of
> attack.
>
> Note that block ciphers can add ~240 octets of discretionary padding per
record.
> That can be pretty effective if you are careful.
>
> Section 7
>
> This section is duplicative of much of the rest of the document.  I
realize that
> editing is hard, but see my earlier comments about structure.
>
> It's obvious that this section is about QUIC.  That shows in several
ways.  It's
> nice how it doesn't say so out loud, but it leaks through in several
confusing
> ways.  See below.
>
> Section 7.1
>
> This section is purportedly about encrypted ACKs, which won't happen
until we
> get to QUIC.  But the points regarding proxies (b, c, d) are not
prevented by
> encrypted ACKs, they are prevented by encryption more generally.  Point e
is
> defeated by integrity protection of ACKs, not confidentiality protection.
>
> I hope that the IETF never publishes draft-dolson-plus-middlebox-benefits;
it
> makes claims about the benefits of specific solutions for different use
cases
> with the goal of justifying those solutions.  At the same time, it fails
to
> recognize the existence of alternative, often superior, solutions for
those use
> cases.  In other words, it has many of the same issues as this document.
>
> FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I
don't
> know how to close the gap between the privacy assurances I wish it had
and the
> privacy weaknesses it has.
>
> The phrase "trusted proxies" is a dangerously misleading phrase.  The
concept of
> trust is - particularly in this context - frequently abused.
>
> Sections 7.2 and 7.3
>
> I'd be interested in learning about the justification for these features
(again,
> go back to my comment about to whom the benefit accrues, and I'd advise
caution
> not to make the trickle-down economics mistake of using second-order
effects).
> Personally, I'm not that sad that they are going to be negatively
affected.
>
> Section 7.2, Point d seems to be saying something about a multiplexed
protocol,
> not one that has an encrypted transport header (see above regarding QUIC).
>
> All these points equally apply to HTTPS, which suggest that encrypted
transport
> headers is not the issue (unless by transport we mean HTTP).
>
> Section 7.4
>
> s/GPSR/GPRS/ ?
>
> Section 8
>
> I generally agree with the first statement here, but after having read the
> document, I could take away some very different views on what the
"problems at
> hand" actually are.  I suspect that different people will have very
different
> takeaways.
>
> The conclusion section of a document is not the right place to start
introducing
> new information, particularly information relevant to RFC 2804.
>
> Not sure where this is going:
>
>    Terrorists and criminals have been using encryption for many years.
>
> Because it's disconnected from the remainder of the paragraph.  If you
are going
> to invoke the T-word, you had better have a strong argument to make.  On
the
> final sentence of that paragraph, the subject ("This") is unclear.
>



--

Best regards,
Kathleen

--001a114b060c14c8e2054cd6572d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I most certainly reviewed 09. I haven&#39;t reviewed the =
diff. I doubt that it would change my opinion on the macro - level problems=
.=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 8=
 Apr. 2017 3:34 am, &quot;Kathleen Moriarty&quot; &lt;<a href=3D"mailto:kat=
hleen.moriarty.ietf@gmail.com">kathleen.moriarty.ietf@gmail.com</a>&gt; wro=
te:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Martin,<br>
<br>
Thanks for your review.=C2=A0 It seems that you have read version 8 or<br>
earlier and not the current version, 9, from some of your suggestions<br>
that have been corrected already.=C2=A0 Your review also reads to me that<b=
r>
additional context setting may help, but please note that some context<br>
setting was improved in version 9.=C2=A0 We re-arranged some of the<br>
sections per IESG review recommendations in the latest version as<br>
well.<br>
<br>
Perhaps you have additional language suggestions for context setting?<br>
<br>
The abstract states:<br>
<br>
=C2=A0 =C2=A0Increased use of encryption impacts operations for security an=
d<br>
=C2=A0 =C2=A0network management causing a shift in how these functions are<=
br>
=C2=A0 =C2=A0performed.=C2=A0 In some cases, new methods to both monitor an=
d protect<br>
=C2=A0 =C2=A0data will evolve.=C2=A0 In other cases, the ability to monitor=
 and<br>
=C2=A0 =C2=A0troubleshoot could be eliminated.=C2=A0 This draft includes a =
collection<br>
=C2=A0 =C2=A0of current security and network management functions that may =
be<br>
=C2=A0 =C2=A0impacted by the shift to increased use of encryption.=C2=A0 Th=
is draft<br>
=C2=A0 =C2=A0does not attempt to solve these problems, but rather document =
the<br>
=C2=A0 =C2=A0current state to assist in the development of alternate option=
s to<br>
=C2=A0 =C2=A0achieve the intended purpose of the documented practices.<br>
<br>
which is repeated again in the introduction, but slightly reworded.<br>
The introduction also includes statements on the existing publications<br>
related to encryption and I read them as not having any bias, but<br>
rather supporting the existing documents that also had consensus.<br>
<br>
A couple of comments and one question inline.<br>
<div class=3D"elided-text"><br>
On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson<br>
&lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com</a=
>&gt; wrote:<br>
&gt; Draft: draft-mm-wg-effect-encrypt-09<br>
&gt; Date: 2017-04-07<br>
&gt;<br>
&gt; Overall<br>
&gt;<br>
&gt; This document is unfocused and unclear in its intent.=C2=A0 It is fill=
ed with<br>
&gt; unsubstantiated claims, misleading statements, bias, and implied recom=
mendations<br>
&gt; for bad practices.=C2=A0 I would oppose its publication in the current=
 form.<br>
&gt; Furthermore, I don&#39;t believe that small scale or editorial changes=
 would be<br>
&gt; sufficient to correct these problems.<br>
&gt;<br>
&gt;<br>
&gt; Aside from weakening its utility and/or arguments, the lack of focus w=
ill allow<br>
&gt; this document to be abused in various ways.=C2=A0 For instance, it mig=
ht imply IETF<br>
&gt; endorsement of the practices described in the document.=C2=A0 Given th=
at the IETF has<br>
&gt; published positions that in some cases reject these practices, this do=
cument<br>
&gt; needs to be very precise with its claims.=C2=A0 In its current form, i=
t is not nearly<br>
&gt; careful enough.<br>
&gt;<br>
&gt; If this document is going to be published as an RFC, then it needs to =
be very<br>
&gt; clear about its intent and its position - or lack thereof - toward the=
se<br>
&gt; practices.=C2=A0 It might be possible to say that these practices were=
 employed in<br>
&gt; networks in the past and that encryption is reducing the viability of =
those<br>
&gt; practices.=C2=A0 A value-neutral statement like that might be acceptab=
le as long as<br>
&gt; it were framed carefully.<br>
&gt;<br>
&gt; What is problematic is the implicit argument that is presented.=C2=A0 =
This document<br>
&gt; could easily be construed as the IETF legitimizing these practices.=C2=
=A0 This<br>
&gt; includes things on which the IETF has published statements (see for ex=
ample RFC<br>
&gt; 2804).<br>
<br>
</div>See the abstract and introduction and summary.<br>
<div class=3D"quoted-text"><br>
&gt;<br>
&gt; This steps firmly into to sticky mess that is the politics of encrypti=
on policy.<br>
&gt; If the IETF is going to make a political statement with this document,=
 then that<br>
&gt; statement needs to be a lot better than this.<br>
&gt;<br>
&gt; Furthermore, any statement needs to be consistent with previous statem=
ents,<br>
&gt; where in this case that primarily means RFC 7258.=C2=A0 Right now it r=
eads as an<br>
&gt; attempt to dilute RFC 7258.<br>
<br>
</div>Not at all.<br>
<div class=3D"elided-text"><br>
&gt;<br>
&gt; If this document were more clearly formulated as an even-handed treatm=
ent of<br>
&gt; what happens today - without judgment - then it could be useful.=C2=A0=
 Here the model<br>
&gt; of RFC 7754 is a good one.=C2=A0 It describes the different facets of =
a use case,<br>
&gt; then the different practices that might be employed to achieve that go=
al.=C2=A0 For<br>
&gt; each practice the pros, cons, and technical limitations are covered wi=
th an eye<br>
&gt; to all involved parties.<br>
&gt;<br>
&gt;<br>
&gt; The Real Purpose of this Document<br>
&gt;<br>
&gt; I think that this is the real question that this document wants to ask=
 is:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 In a world where we are forced to defend against pervasiv=
e monitoring by<br>
&gt;=C2=A0 =C2=A0 motivated and malicious actors, can we find a role for le=
ss pervasive<br>
&gt;=C2=A0 =C2=A0 monitoring by well-intentioned entities?<br>
&gt;<br>
&gt; There is an interesting discussion to be had here, but I&#39;m convinc=
ed after my<br>
&gt; review that this document is the wrong vehicle for that discussion.=C2=
=A0 I&#39;m also<br>
&gt; inclined to suggest that this is the wrong question to ask in the firs=
t place.<br>
&gt;<br>
&gt; To the extent that we have the tools necessary to protect against perv=
asive<br>
&gt; monitoring, we have to accept that more-legitimate uses of monitoring =
are<br>
&gt; collateral.=C2=A0 Mostly, that&#39;s just a function of the limitation=
s of the imperfect<br>
&gt; tools we have.<br>
&gt;<br>
&gt; The value in this document is in the rather comprehensive collection o=
f use<br>
&gt; cases.=C2=A0 Sure, some we might not attribute much weight to, like wi=
retapping.<br>
&gt; Others are frankly frightening and not just in the Orwellian sense.<br=
>
&gt;<br>
&gt; The problems that are implied by the current practices of network oper=
ators is a<br>
&gt; large vein of unexplored work for the community.=C2=A0 Spending effort=
 on finding<br>
&gt; better solutions to legitimate problems is worthwhile.<br>
&gt;<br>
&gt; In other words, the right question might be:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 For each of these practices that we see today, are the us=
e cases that<br>
&gt;=C2=A0 =C2=A0 motivate them legitimate and how might be implement alter=
native techniques<br>
&gt;=C2=A0 =C2=A0 that properly respect privacy and security?<br>
&gt;<br>
&gt;<br>
&gt; Two- and Three- Party Interactions<br>
&gt;<br>
&gt; A great many sections of the document are unclear about the relationsh=
ips<br>
&gt; between different actors.=C2=A0 It seems like many of the activities d=
escribe, which<br>
&gt; are presented here as being beneficial, are performed by a third party=
 without<br>
&gt; the consent or involvement of the two communicating peers.=C2=A0 After=
 all, those are<br>
&gt; the cases where encryption most often interferes.<br>
&gt;<br>
&gt; The assertion that some benefit is accrued to communicating peers as a=
 result of<br>
&gt; these actions is the constant subject of the text.=C2=A0 I observe tha=
t in most of<br>
&gt; the cases listed in this document, the benefit is accrued primarily to=
 the third<br>
&gt; party.<br>
&gt;<br>
&gt; Clarity around the arguments that the document makes with respect to b=
enefits to<br>
&gt; each of the involved parties is sorely lacking.<br>
&gt;<br>
&gt; In addition to this, where benefits truly do accrue to communicating p=
eers,<br>
&gt; technical options that don&#39;t rely on privacy-invasive techniques a=
re routinely<br>
&gt; dismissed in an offhand fashion.=C2=A0 In this way, any moral imprimat=
ur attributed<br>
&gt; to the use case is used to justify the privacy-invasive method.<br>
&gt;<br>
&gt;<br>
&gt; Document Structure<br>
&gt;<br>
&gt; This document is very hard to read (and review).=C2=A0 Probably my big=
gest complaint<br>
&gt; is that the sections are haphazardly organized.=C2=A0 They contain a m=
ixture of use<br>
&gt; cases (what does SP X want to do) and techniques (how do they do these=
 things).<br>
&gt; Material is duplicated between sections.=C2=A0 Sections cover 10 diffe=
rent use cases<br>
&gt; while talking about techniques, then other sections talk about differe=
nt<br>
&gt; techniques whiles talking about a scenario.=C2=A0 This leads to a lot =
of repetition.<br>
&gt;<br>
&gt; There are three axes that this document contemplates:<br>
&gt;<br>
&gt;=C2=A0 - the techniques that are currently used in networks<br>
&gt;=C2=A0 - the use cases that motivate these techniques<br>
&gt;=C2=A0 - the deployment scenarios in which these use cases manifest<br>
&gt;<br>
&gt; It would appear that the document attemps to start from the deployment=
<br>
&gt; scenarios.=C2=A0 However, this causes use cases and techniques to be m=
ixed.<br>
&gt; Judicious use of cross-referencing might have made this arrangement tr=
actable,<br>
&gt; but there are virtually no cross references.<br>
&gt;<br>
&gt;<br>
&gt; Section 1<br>
&gt;<br>
&gt; I find the introduction of this document difficult to parse.=C2=A0 I t=
hink that what<br>
&gt; it wants to say is pretty straightforward, but it manages this in quit=
e an<br>
&gt; obtuse way.=C2=A0 Here&#39;s what I think that it is trying to say:<br=
>
&gt;<br>
&gt; 1. The IETF (and the larger community) has reacted to revelations of p=
ervasive<br>
&gt;=C2=A0 =C2=A0 monitoring by increasing the use of encryption.<br>
&gt; 2. That has been somewhat successful.<br>
&gt; 3. More encryption has an impact on some practices that network operat=
ors have<br>
&gt;=C2=A0 =C2=A0 become accustomed to employing.<br>
&gt;<br>
&gt; Expressed in this way, you can see how you could make a value-neutral<=
br>
&gt; statement.<br>
&gt;<br>
&gt; On the first, you can definitely make an argument based on the documen=
ts that<br>
&gt; the IETF have published.=C2=A0 However, it is a mistake here in assumi=
ng that the<br>
&gt; IETF - or the revelations of global-scale surveillance - is directly r=
esponsible<br>
&gt; for the uptick in adoption of cryptographic protection for Internet tr=
affic.<br>
&gt; This is something that the community as a whole has been working towar=
ds for<br>
&gt; many years; these trends predate the actions this draft focuses on.=C2=
=A0 This is<br>
&gt; particularly true for the hosted provider cases in Section 3, where bu=
siness<br>
&gt; motivations for protection are far stronger than any concerns over gov=
ernment<br>
&gt; surveillance.=C2=A0 Yeah, that&#39;s a subjective view, but I&#39;m ju=
st reviewing, I don&#39;t<br>
&gt; have to write a statement that will be labelled as having IETF consens=
us.<br>
&gt;<br>
&gt; The immediate focus on opportunistic security is highly misleading, es=
pecially<br>
&gt; in the web case.=C2=A0 The amount of opportunistically secured web tra=
ffic is<br>
&gt; miniscule by global standards.=C2=A0 Since Firefox is the only browser=
 to support OS<br>
&gt; for the web, so adjust the following by market share: &lt;<a href=3D"h=
ttps://mzl.la/2oc46ch" rel=3D"noreferrer" target=3D"_blank">https://mzl.la/=
2oc46ch</a>&gt;.<br>
&gt;<br>
&gt; I understand that mail is more often opportunistically secured, and yo=
u will<br>
&gt; hear the virtues of OS sung from the rooftops, but all evidence sugges=
ts that<br>
&gt; this is just a transitory state.=C2=A0 Instant messaging is closer to =
the web case,<br>
&gt; with the trend toward strong protections that include authentication.=
=C2=A0 Of<br>
&gt; course, I don&#39;t believe that mail or instant messaging represent a=
ny significant<br>
&gt; traffic volume, so you need to be very careful about the nature of the=
 claims<br>
&gt; that are being made.=C2=A0 It has to be that the volume of mail has to=
 be a rounding<br>
&gt; error when it comes to capacity planning for networks.<br>
&gt;<br>
&gt; On the second point, when making claims about prevalence of encryption=
, I would<br>
&gt; advise caution when citing statistics.=C2=A0 Here&#39;s the graph for =
the Mozilla figures<br>
&gt; that I think are being cited &lt;<a href=3D"https://mzl.la/2obZjrb" re=
l=3D"noreferrer" target=3D"_blank">https://mzl.la/2obZjrb</a>&gt;. Here&#39=
;s a different graph<br>
&gt; with a different number &lt;<a href=3D"https://mzl.la/2oc263J" rel=3D"=
noreferrer" target=3D"_blank">https://mzl.la/2oc263J</a>&gt;.=C2=A0 This hi=
ghlights the point<br>
&gt; that statistics need to be carefully cited, because bare claims are di=
fficult to<br>
&gt; assess.=C2=A0 Methodology matters when it comes to these sorts of clai=
ms - are we<br>
&gt; talking proportions of packets, requests, flows, or something else?<br=
>
&gt; Furthermore, the citations in the document are made more difficult to =
assess by<br>
&gt; being measured at very different times (where the two I cite here were=
 made at<br>
&gt; roughly the same point in time).<br>
<br>
</div>For the Mozilla statistics, Richard Barnes had reviewed the text afte=
r<br>
providing the statistic as he wanted to make sure it was stated<br>
clearly raising the same concerns you do about statistics.=C2=A0 Do you<br>
have further text suggestions to clarify this statistic?<br>
<br>
Thank you,<br>
Kathleen<br>
<div class=3D"elided-text"><br>
&gt;<br>
&gt; The statistics do support the notion that there is a significant amoun=
t of<br>
&gt; encryption in use, but it would appear that the claim is that the amou=
nt of<br>
&gt; encryption is *increasing*.=C2=A0 This is not an extraordinary claim, =
but no evidence<br>
&gt; is offered in support of the claim.=C2=A0 It isn&#39;t a certain thing=
 either.=C2=A0 From the<br>
&gt; statistics that I have access to, there was a definite uptick in Octob=
er of<br>
&gt; 2015, but the rate appears to be stable since then.<br>
&gt;<br>
&gt; It appears that the remainder of the document is intended to address t=
he third<br>
&gt; of my points in some detail.=C2=A0 That&#39;s a good structure in theo=
ry, but see above.<br>
&gt;<br>
&gt; I don&#39;t think that the &quot;service provider&quot; taxonomy works=
 for this document.<br>
&gt; Based solely on the structure of the document, the only service provid=
er that<br>
&gt; this document concerns itself with is the one who forwards the packets=
.=C2=A0 That<br>
&gt; application service providers are involved as one of the endpoints is =
relevant<br>
&gt; in some cases, but not all.=C2=A0 For that reason, I prefer &quot;netw=
ork operator&quot; and to<br>
&gt; use specific terms like &quot;mail host&quot; or &quot;web server&quot=
; as appropriate to the<br>
&gt; context.<br>
&gt;<br>
&gt;<br>
&gt; Section 2 (top section)<br>
&gt;<br>
&gt; I like that the attacks on SMTP by network operators is highlighted he=
re.<br>
&gt;<br>
&gt; There&#39;s an implicit argument here that runs counter to established=
 IETF<br>
&gt; consensus.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Some methods used by service providers are impacted by th=
e use of encryption<br>
&gt;=C2=A0 =C2=A0 where middle boxes were in use to perform functions that =
range from load<br>
&gt;=C2=A0 =C2=A0 balancing techniques to monitoring for attacks or enablin=
g &quot;lawful<br>
&gt;=C2=A0 =C2=A0 intercept&quot;, such that described in [ETSI101331] and =
[CALEA] in the US.<br>
&gt;<br>
&gt; This fails to remain neutral.=C2=A0 This implicitly makes a value-judg=
ment about<br>
&gt; relative morality/acceptability/value of certain practices.=C2=A0 What=
 is<br>
&gt; particularly insidious about this particular form is that it invites<b=
r>
&gt; interpretation that is subjectively coloured.=C2=A0 For instance, as a=
 non-EU and<br>
&gt; non-US citizen, I might consider the use of the particular lawful inte=
rcept<br>
&gt; techniques offensive; thus I might interpret this as a spectrum betwee=
n<br>
&gt; inoffensive to offensive.=C2=A0 An employee of the US government might=
 view this<br>
&gt; somewhat differently and interpret this as a scale between low-value t=
o<br>
&gt; high-value.=C2=A0 I&#39;m guessing here, but this is really just to hi=
ghlight my point<br>
&gt; about care.<br>
&gt;<br>
&gt; A more serious concern is this statement:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The loss of access to these fields may prompt undesirable=
 security practices<br>
&gt;=C2=A0 =C2=A0 in order to gain access to the fields in unencrypted data=
 flows.<br>
&gt;<br>
&gt; I&#39;ve read this argument before (see <a href=3D"https://queue.acm.o=
rg/detail.cfm?id=3D2508864" rel=3D"noreferrer" target=3D"_blank">https://qu=
eue.acm.org/detail.<wbr>cfm?id=3D2508864</a><br>
&gt; for the long form), and it might even have an element of truth to it.=
=C2=A0 However,<br>
&gt; it&#39;s not a statement that I personally attribute any real credibil=
ity to, and<br>
&gt; nor do I think that it needs to be credited with any amount of serious=
ness.=C2=A0 I<br>
&gt; certainly disagree with the IETF making any such statement.=C2=A0 It s=
ays that we are<br>
&gt; collectively willing to bow in response to (anticipated) threats of vi=
olence.<br>
&gt;<br>
&gt; Section 2.1<br>
&gt;<br>
&gt; This is one of the few sections that talk about what it means to opera=
te a<br>
&gt; service as opposed to operate a network.<br>
&gt;<br>
&gt; Overall, this section doesn&#39;t work particularly well.=C2=A0 The di=
stinction between<br>
&gt; integrated and standalone load balancing is an interesting division, b=
ut it<br>
&gt; doesn&#39;t leverage this distinction well.=C2=A0 What causes a standa=
lone load-balancer<br>
&gt; to be necessary?=C2=A0 Is this something a network operator uses?=C2=
=A0 I see text on NFV<br>
&gt; later, but it&#39;s far removed from the original text and it seems as=
pirational<br>
&gt; rather than concrete.=C2=A0 On the other hand, many of the concerns in=
 this document<br>
&gt; simply don&#39;t apply to an integrated load balancer.<br>
&gt;<br>
&gt; The amount of text on QUIC here is surprising.=C2=A0 Given how much of=
 QUIC is<br>
&gt; changing right now, we shouldn&#39;t publish a document that attempts =
to make claims<br>
&gt; about what QUIC is or how it is operated.=C2=A0 This attempts to dive =
into the<br>
&gt; details of QUIC connection migration in a way that presumes much about=
 the<br>
&gt; outcome of issues that the QUIC working group is still struggling with=
.<br>
&gt;<br>
&gt; I would strongly recommend removing QUIC-specific language from this s=
ection and<br>
&gt; the document as a whole.=C2=A0 We have an operational document in the =
QUIC working<br>
&gt; group that would be a good venue to discuss some of these concerns.<br=
>
&gt;<br>
&gt; Is this an oblique reference to (the much-loved) RFC 7974?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Current protocols, such as TCP, allow the development of =
stateless integrated<br>
&gt;=C2=A0 =C2=A0 load balancers by availing such load balancers of additio=
nal plain text<br>
&gt;=C2=A0 =C2=A0 information in client-to-server packets.<br>
&gt;<br>
&gt; Otherwise, I don&#39;t know what it means.<br>
&gt;<br>
&gt; BTW, I like this parenthetical:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 (That said, care must be exercised to make sure that the =
information encoded<br>
&gt;=C2=A0 =C2=A0 by the endpoints is not sufficient to identify unique flo=
ws and facilitate<br>
&gt;=C2=A0 =C2=A0 Persistent Surveillance attack vector.)<br>
&gt;<br>
&gt; I&#39;m going to take this to the QUIC working group, because QUIC cer=
tainly doesn&#39;t<br>
&gt; meet that bar right now.=C2=A0 It fully facilitates Persistent Surveil=
lance in its<br>
&gt; current form (proper noun?=C2=A0 I haven&#39;t really seen that term b=
efore, even though<br>
&gt; it draws a neat parallel with Pervasive Surveillance).<br>
&gt;<br>
&gt; Editorial:<br>
&gt; * &quot;pop&quot; is a term of art that needs explanation.<br>
&gt; * &quot;QUIC?s&quot;, &quot;network?s&quot; - avoid smart quotes, and =
- more generally - the<br>
&gt;=C2=A0 =C2=A0possessive form for the inanimate.<br>
&gt; * &quot;QUIC&#39;s server-generated flow IDs&quot; -&gt; &quot;QUIC&#3=
9;s connection IDs&quot;.<br>
&gt;<br>
&gt; Section 2.2<br>
&gt;<br>
&gt; I think that this sums the situation up reasonably well.=C2=A0 It fail=
s the<br>
&gt; value-neutral test in a few ways though.=C2=A0 As I understand the sit=
uation,<br>
&gt; surveying operates at many levels.=C2=A0 For accurate planning, models=
 of endpoint<br>
&gt; behaviour are used to determine things like whether loss or congestion=
 is<br>
&gt; affecting throughput.=C2=A0 Really good models require knowledge of wh=
at users are<br>
&gt; attempting to do and the applications they are using (as mentioned, th=
ings like<br>
&gt; browser version matter in these models).=C2=A0 For instance, it isn&#3=
9;t enough to<br>
&gt; understand that the user is trying to receive 720p video, you also hav=
e to know<br>
&gt; that a 4k stream for the same content is available.<br>
&gt;<br>
&gt; The degree to which these models are privacy-invasive is not even ackn=
owledged.<br>
&gt;<br>
&gt; Nit: Did you realize that &quot;well-intentioned&quot; is a euphemism?=
=C2=A0 I&#39;d expect that<br>
&gt; subtlety to be lost on many readers though.<br>
&gt;<br>
&gt; Section 2.3.1<br>
&gt;<br>
&gt; I find this sad, even if I can recognize the truth of it:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 A monitoring system could easily identify a specific brow=
ser,<br>
&gt;=C2=A0 =C2=A0 and by correlating other information, identify a specific=
 user.<br>
&gt;<br>
&gt; As a browser vendor, we don&#39;t consider this to be a feature, it&#3=
9;s a bug.<br>
&gt;<br>
&gt; Section 2.3.2.1<br>
&gt;<br>
&gt; This is a strange section under which to put caching.=C2=A0 Caching is=
 a use case<br>
&gt; akin to compression.=C2=A0 I don&#39;t see it as belonging to the clas=
s of things that<br>
&gt; rely on DPI.=C2=A0 You just intermediate the cleartext HTTP in the way=
 that RFC 7230<br>
&gt; recognizes.=C2=A0 Note that RFC 7230 explicitly does not endorse the p=
ractice of<br>
&gt; transparent proxying for a range of reasons, not the least of which is=
 the<br>
&gt; complete lack of transparency (yep).<br>
&gt;<br>
&gt; Section 2.3.2.2<br>
&gt;<br>
&gt; Again, it&#39;s strange to see differential treatment under DPI.=C2=A0=
 I was fairly sure<br>
&gt; that fingerprinting was used here as well.<br>
&gt;<br>
&gt; Section 2.4<br>
&gt;<br>
&gt; This section doesn&#39;t even attempt to recognize that applications a=
re much better<br>
&gt; now at scaling content to suit the device on which that content is int=
ended to<br>
&gt; be consumed.=C2=A0 It should.<br>
&gt;<br>
&gt; This section should not represent compression as an unmitigated good.=
=C2=A0 I&#39;m told<br>
&gt; that significant damage can be done to video streams by &quot;well-int=
entioned&quot;<br>
&gt; compression middleboxes.<br>
&gt;<br>
&gt; Yet again I see a call back to the implicit threat of violence in &quo=
t;they will<br>
&gt; adopt undesirable security practices&quot;.=C2=A0 Statements in that f=
orm have no place in<br>
&gt; IETF RFCs.<br>
&gt;<br>
&gt; Section 2.5<br>
&gt;<br>
&gt; This mentions RFC 7754 then blithely ignores its primary conclusion. G=
enerally,<br>
&gt; The treatment in RFC 7754 of this subject is more even-handed.<br>
&gt;<br>
&gt; The use of particular examples (betting, gambling, dating) shows cultu=
ral bias.<br>
&gt;<br>
&gt; Jargon warning: &quot;core network&quot;, &quot;the mobile network&quo=
t; (&quot;the&quot;?)<br>
&gt;<br>
&gt; Section 2.5.2<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This type of granular filtering could occur at the endpoi=
nt, however the<br>
&gt;=C2=A0 =C2=A0 ability to efficiently provide this as a service without =
new efficient<br>
&gt;=C2=A0 =C2=A0 management solutions for end point solutions impacts prov=
iders.<br>
&gt;<br>
&gt; The initial premise here (up to the first comma) is the conclusion of =
RFC 7754.<br>
&gt; I disagree with the conclusion, and I suspect so does RFC 7754.=C2=A0 =
In scenarios<br>
&gt; where this matters, endpoints are routinely managed centrally.=C2=A0 T=
he range of<br>
&gt; options for this sort of management are plentiful and diverse.<br>
&gt;<br>
&gt; Section 2.5.3<br>
&gt;<br>
&gt; This describes a captive portal, which in the case where the service p=
rovider<br>
&gt; has a relationship with their customers, seems like a poor solution.=
=C2=A0 See the<br>
&gt; CAPPORT working group for ways in which people are actually working on=
 a<br>
&gt; solution to this problem.<br>
&gt;<br>
&gt; Section 2.6<br>
&gt;<br>
&gt; The capitalization of section headings is inconsistent here (and throu=
ghout).<br>
&gt;<br>
&gt; Section 2.6.1<br>
&gt;<br>
&gt; Isn&#39;t this a duplicate of Section 2.1?<br>
&gt;<br>
&gt; Section 2.6.2<br>
&gt;<br>
&gt; I can&#39;t parse this statement:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Approved access to a network is a prerequisite to request=
s for Internet<br>
&gt;=C2=A0 =C2=A0 traffic - hence network access, including any authenticat=
ion and<br>
&gt;=C2=A0 =C2=A0 authorization, is not impacted by encryption.<br>
&gt;<br>
&gt; And then we get into zero rating, which is a hot-button topic.=C2=A0 N=
o<br>
&gt; acknowledgment given to the sensitivities on the subject, or even a su=
perficial<br>
&gt; exploration of the technical options that are available.<br>
&gt;<br>
&gt; This text references a non-existent Appendix.<br>
&gt;<br>
&gt; Section 2.6.5<br>
&gt;<br>
&gt; This paragraph is strange.=C2=A0 It starts by describing what appears =
to be use cases<br>
&gt; (are those scare quotes?).=C2=A0 It finishes by implying that these ar=
e attacks on<br>
&gt; privacy (which they are).<br>
&gt;<br>
&gt; What is &quot;Non-Customer Proprietary Network Information&quot;?=C2=
=A0 I hope that this isn&#39;t<br>
&gt; an attempt to somehow privilege the information so that it seems less =
than<br>
&gt; privacy-invasive.<br>
&gt;<br>
&gt; Section 2.7<br>
&gt;<br>
&gt; This is one of the areas that is most legitimately affected by increas=
ed<br>
&gt; adoption of encryption.=C2=A0 I have no doubt that having detailed inf=
ormation about<br>
&gt; the application and its use makes the process of troubleshooting easie=
r.<br>
&gt;<br>
&gt; This is the first mention in the document of network-based optimizatio=
n.=C2=A0 Was<br>
&gt; the section describing that cut from an earlier draft?<br>
&gt;<br>
&gt; The use of websockets as a primary example is an odd one.=C2=A0 It&#39=
;s just not that<br>
&gt; common.=C2=A0 For reference, we see &gt;20% failure rates on encrypted=
 websockets and<br>
&gt;&gt;50% failures in the clear; no one in their right mind would rely on=
 websockets.<br>
&gt; If the point is that HTTP is carrying more traffic (see<br>
&gt; <a href=3D"http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.=
pdf" rel=3D"noreferrer" target=3D"_blank">http://conferences.sigcomm.<wbr>o=
rg/hotnets/2010/papers/a6-<wbr>popa.pdf</a>) saying just that<br>
&gt; would be more effective.<br>
&gt;<br>
&gt; Section 3<br>
&gt;<br>
&gt; It would help if &quot;hosted environments&quot; was defined before di=
ving in.<br>
&gt;<br>
&gt; Section 3.1<br>
&gt;<br>
&gt; The paragraph on DLP is ironically amusing.=C2=A0 Encryption exists to=
 prevent<br>
&gt; private information leakage, but the assertion here is that encryption=
 is<br>
&gt; hampering DLP attempts.<br>
&gt;<br>
&gt; It&#39;s true that protection of intellectual property is an important=
 business<br>
&gt; goal, but this handling suggests an architecture that I&#39;m fairly s=
ure is counter<br>
&gt; to established wisdom (see &quot;SSL added and removed here :-)&quot;:=
<br>
&gt; <a href=3D"https://www.washingtonpost.com/rf/image_404h/2010-2019/Wash=
ingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg"=
 rel=3D"noreferrer" target=3D"_blank">https://www.washingtonpost.<wbr>com/r=
f/image_404h/2010-2019/<wbr>WashingtonPost/2013/10/30/<wbr>Local/Images/GOO=
GLE-CLOUD-<wbr>EXPLOITATION1383148810.jpg</a>).<br>
&gt; Worse, this casually dismisses a model that is actually more likely to=
 work.<br>
&gt; Malware encrypts too (<a href=3D"https://arxiv.org/abs/1607.01639" rel=
=3D"noreferrer" target=3D"_blank">https://arxiv.org/abs/1607.<wbr>01639</a>=
).<br>
&gt;<br>
&gt; Section 3.1.1<br>
&gt;<br>
&gt; Who is the customer here?<br>
&gt;<br>
&gt; Why does the hosting provider need to monitor access?=C2=A0 They have =
the ability to<br>
&gt; limit accesses, but this is suggesting that what happens within the en=
velope of<br>
&gt; what they permit is important for them to know.=C2=A0 I&#39;d be surpr=
ised if you could<br>
&gt; show that this is true.=C2=A0 Hosting providers - in my experience - v=
alue their<br>
&gt; ongoing business and would not jeapardize it by snooping on their cust=
omers.<br>
&gt; It&#39;s different if the customer opts in to a security service, but =
that<br>
&gt; demonstrates a cooperative situation, where the rest of this document =
is largely<br>
&gt; concerned with adversarial uses of encryption.<br>
&gt;<br>
&gt; Section 3.1.2<br>
&gt;<br>
&gt; This is another example where the organization of the document could<b=
r>
&gt; be improved.<br>
&gt;<br>
&gt; Again with the &quot;SSL added and removed here :-)&quot; recommendati=
on.=C2=A0 PCI don&#39;t<br>
&gt; permit that for good reason.<br>
&gt;<br>
&gt; Section 3.2.1<br>
&gt;<br>
&gt; I don&#39;t believe that monitoring of these types of application requ=
ire cleartext<br>
&gt; access.=C2=A0 There are two parties involved: the provider of the appl=
ication and the<br>
&gt; user of it.=C2=A0 The provider has most of the power here and can theo=
retically<br>
&gt; design the system to allow whatever level of access they require.=C2=
=A0 To the extent<br>
&gt; that the user needs protection from the application provider, that is =
a matter<br>
&gt; of negotiation between them.<br>
&gt;<br>
&gt; I don&#39;t see how the adversarial three-party situation presented in=
 the rest of<br>
&gt; the document applies in this situation.<br>
&gt;<br>
&gt; Section 3.2.2<br>
&gt;<br>
&gt; No real mention of the effect of encryption here, or is this just sayi=
ng that<br>
&gt; there is no issue here?<br>
&gt;<br>
&gt; I don&#39;t see the point of the PGP/Dark Mail paragraph.=C2=A0 I&#39;=
d be leery of the IETF<br>
&gt; saying things like &quot;PGP may be a front runner&quot; though.<br>
&gt;<br>
&gt; Section 3.3<br>
&gt;<br>
&gt; There&#39;s certainly a lot of detail here, but I had a really hard ti=
me extracting<br>
&gt; value from this section.=C2=A0 I can&#39;t see how data storage is fun=
damentally<br>
&gt; different to the general case of an application provider.<br>
&gt;<br>
&gt; Section 4.1.1<br>
&gt;<br>
&gt; I appreciate the recognition that endpoint-based techniques work.=C2=
=A0 The<br>
&gt; implication that this isn&#39;t the obvious solution, much less so.<br=
>
&gt;<br>
&gt; Section 4.1.2<br>
&gt;<br>
&gt; I&#39;m confused about the purpose of this section.=C2=A0 This seems t=
o be talking about<br>
&gt; the sort of network-based methodologies an application provider might =
employ to<br>
&gt; ensure that their application is working as intended.=C2=A0 Why would =
the application<br>
&gt; provider not have access to detailed logging and usage metrics?<br>
&gt;<br>
&gt; As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is =
cited no<br>
&gt; fewer than three times in the same paragraph.=C2=A0 It makes some fair=
ly bold claims<br>
&gt; about its effect on privacy that I don&#39;t believe will hold up to a=
nalysis.<br>
&gt;<br>
&gt; Section 4.1.3.1<br>
&gt;<br>
&gt; This section correctly identifies the issue as one of shortcomings in =
logging,<br>
&gt; not increased use of encryption.<br>
&gt;<br>
&gt; I would have stopped there, but the section persists and ultimately re=
ferences<br>
&gt; RFC 7974, which is widely recognized as a monstrously bad idea (the IE=
SG note is<br>
&gt; fairly clear on this point).<br>
&gt;<br>
&gt; Section 4.1.3.2<br>
&gt;<br>
&gt; &quot;HTTP/2&quot;, not &quot;HTTP2&quot;.<br>
&gt;<br>
&gt; I don&#39;t see how this section belongs in this document.=C2=A0 The 1=
:1 correlation<br>
&gt; between actions and flows in HTTP was a mistake of the 1980s that we&#=
39;ve spent a<br>
&gt; lot of time on correcting (sometimes unsuccessfully, see pipelining).<=
br>
&gt;<br>
&gt; Section 4.1.3.3<br>
&gt;<br>
&gt; It&#39;s not a &quot;service call&quot; it&#39;s just a request.<br>
&gt;<br>
&gt; Section 4.2<br>
&gt;<br>
&gt; If the inclusion of a reference to RFC 7457 is to support a claim that=
 TLS is<br>
&gt; attacked, that&#39;s sailing far too close to an endorsement of attack=
s than I am<br>
&gt; comfortable with.=C2=A0 However, I don&#39;t believe that any of the l=
isted attacks<br>
&gt; remain viable in modern applications.=C2=A0 What is most often the cas=
e is that a<br>
&gt; trust anchor is installed on enterprise users&#39; machines and new ce=
rtificates are<br>
&gt; minted as needed.=C2=A0 In other words, the host that is accessing the=
 HTTPS site is<br>
&gt; owned by the enterprise and modified so that it can comply with its po=
licies.<br>
&gt;<br>
&gt; When you recommend attack like this (to be clear, I would oppose publi=
cation of<br>
&gt; text that does this), you need to acknowledge the downsides.=C2=A0 For=
 example, MitM<br>
&gt; devices routinely break connections, they hide the true security statu=
s of<br>
&gt; communications from endpoints and users, they frequently implement wea=
ker<br>
&gt; versions of protocols, they often don&#39;t include the same degree of=
 rigor in<br>
&gt; things like certificate validation, and probably many more things that=
 I can&#39;t<br>
&gt; casually list off the cuff.<br>
&gt;<br>
&gt; The discussion of caching here warrants a new section.<br>
&gt;<br>
&gt; Section 5.1<br>
&gt;<br>
&gt; s/effect/affect<br>
&gt;<br>
&gt; No complaint here, just an advertisement for technical solutions that =
aren&#39;t<br>
&gt; affected by increases in encryption.=C2=A0 Good, though I&#39;m not su=
re if the section<br>
&gt; meets the document&#39;s criteria for inclusion.<br>
&gt;<br>
&gt; Section 5.3<br>
&gt;<br>
&gt; No cititation for APWG.=C2=A0 Not an IETF working group from what I ca=
n see.<br>
&gt;<br>
&gt; There&#39;s a presumption here that administrators need to perform the=
se tasks.=C2=A0 Why<br>
&gt; can&#39;t endpoints do this?=C2=A0 It would certainly be a whole lot l=
ess invasive that<br>
&gt; way.=C2=A0 Take a look at how browsers implement checks for &quot;bad&=
quot; sites (which<br>
&gt; include phishing sites).=C2=A0 These methods have some fairly signific=
ant privacy<br>
&gt; safeguards without compromising on performance.<br>
&gt;<br>
&gt; Section 5.5<br>
&gt;<br>
&gt; See my comment about about endpoint-based methods.<br>
&gt;<br>
&gt; Section 5.6<br>
&gt;<br>
&gt; I believe that the spoofed source address problem is not relevant to t=
his<br>
&gt; document.=C2=A0 It&#39;s a fairly well understood problem.=C2=A0 That =
said, if we could wave a<br>
&gt; magic wand and get BCP 38 deployed, that might be nice.<br>
&gt;<br>
&gt; Section 6.1<br>
&gt;<br>
&gt; As this says, it&#39;s fairly well understood that - for HTTP - SNI is=
 used.=C2=A0 The<br>
&gt; point that it is optional is interesting, but doesn&#39;t deserve the =
amount of<br>
&gt; attention this section devotes to it.=C2=A0 The clients that don&#39;t=
 include SNI are in<br>
&gt; a diminishing minority.<br>
&gt;<br>
&gt; That said, this doesn&#39;t pay any attention to another feature in HT=
TP/2:<br>
&gt; connection coalescing.<br>
&gt;<br>
&gt; Section 6.2<br>
&gt;<br>
&gt; ALPN will be encrypted in TLS 1.3.<br>
&gt;<br>
&gt; Section 6.3<br>
&gt;<br>
&gt; This reads as a invitation to perform traffic analysis (a statement th=
at I<br>
&gt; oppose).=C2=A0 Note that we have added padding to most recent protocol=
s (HTTP/2 and<br>
&gt; TLS 1.3 in particular) to give endpoints the ability to resist this so=
rt of<br>
&gt; attack.<br>
&gt;<br>
&gt; Note that block ciphers can add ~240 octets of discretionary padding p=
er record.<br>
&gt; That can be pretty effective if you are careful.<br>
&gt;<br>
&gt; Section 7<br>
&gt;<br>
&gt; This section is duplicative of much of the rest of the document.=C2=A0=
 I realize that<br>
&gt; editing is hard, but see my earlier comments about structure.<br>
&gt;<br>
&gt; It&#39;s obvious that this section is about QUIC.=C2=A0 That shows in =
several ways.=C2=A0 It&#39;s<br>
&gt; nice how it doesn&#39;t say so out loud, but it leaks through in sever=
al confusing<br>
&gt; ways.=C2=A0 See below.<br>
&gt;<br>
&gt; Section 7.1<br>
&gt;<br>
&gt; This section is purportedly about encrypted ACKs, which won&#39;t happ=
en until we<br>
&gt; get to QUIC.=C2=A0 But the points regarding proxies (b, c, d) are not =
prevented by<br>
&gt; encrypted ACKs, they are prevented by encryption more generally.=C2=A0=
 Point e is<br>
&gt; defeated by integrity protection of ACKs, not confidentiality protecti=
on.<br>
&gt;<br>
&gt; I hope that the IETF never publishes draft-dolson-plus-middlebox-<wbr>=
benefits; it<br>
&gt; makes claims about the benefits of specific solutions for different us=
e cases<br>
&gt; with the goal of justifying those solutions.=C2=A0 At the same time, i=
t fails to<br>
&gt; recognize the existence of alternative, often superior, solutions for =
those use<br>
&gt; cases.=C2=A0 In other words, it has many of the same issues as this do=
cument.<br>
&gt;<br>
&gt; FWIW, also be OK if draft-thomson-http-bc never went anywhere as well;=
 I don&#39;t<br>
&gt; know how to close the gap between the privacy assurances I wish it had=
 and the<br>
&gt; privacy weaknesses it has.<br>
&gt;<br>
&gt; The phrase &quot;trusted proxies&quot; is a dangerously misleading phr=
ase.=C2=A0 The concept of<br>
&gt; trust is - particularly in this context - frequently abused.<br>
&gt;<br>
&gt; Sections 7.2 and 7.3<br>
&gt;<br>
&gt; I&#39;d be interested in learning about the justification for these fe=
atures (again,<br>
&gt; go back to my comment about to whom the benefit accrues, and I&#39;d a=
dvise caution<br>
&gt; not to make the trickle-down economics mistake of using second-order e=
ffects).<br>
&gt; Personally, I&#39;m not that sad that they are going to be negatively =
affected.<br>
&gt;<br>
&gt; Section 7.2, Point d seems to be saying something about a multiplexed =
protocol,<br>
&gt; not one that has an encrypted transport header (see above regarding QU=
IC).<br>
&gt;<br>
&gt; All these points equally apply to HTTPS, which suggest that encrypted =
transport<br>
&gt; headers is not the issue (unless by transport we mean HTTP).<br>
&gt;<br>
&gt; Section 7.4<br>
&gt;<br>
&gt; s/GPSR/GPRS/ ?<br>
&gt;<br>
&gt; Section 8<br>
&gt;<br>
&gt; I generally agree with the first statement here, but after having read=
 the<br>
&gt; document, I could take away some very different views on what the &quo=
t;problems at<br>
&gt; hand&quot; actually are.=C2=A0 I suspect that different people will ha=
ve very different<br>
&gt; takeaways.<br>
&gt;<br>
&gt; The conclusion section of a document is not the right place to start i=
ntroducing<br>
&gt; new information, particularly information relevant to RFC 2804.<br>
&gt;<br>
&gt; Not sure where this is going:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Terrorists and criminals have been using encryption for m=
any years.<br>
&gt;<br>
&gt; Because it&#39;s disconnected from the remainder of the paragraph.=C2=
=A0 If you are going<br>
&gt; to invoke the T-word, you had better have a strong argument to make.=
=C2=A0 On the<br>
&gt; final sentence of that paragraph, the subject (&quot;This&quot;) is un=
clear.<br>
&gt;<br>
<br>
<br>
<br>
</div><font color=3D"#888888">--<br>
<br>
Best regards,<br>
Kathleen<br>
</font></blockquote></div><br></div>

--001a114b060c14c8e2054cd6572d--


From nobody Mon Apr 10 15:01:54 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B44128B38 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 15:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 3qtyrj3rL4A2 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 15:01:52 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 538A7126CF6 for <ietf@ietf.org>; Mon, 10 Apr 2017 15:01:52 -0700 (PDT)
Received: from [192.168.3.130] (c-73-222-64-208.hsd1.ca.comcast.net [73.222.64.208]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3AM43Dc031258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 10 Apr 2017 15:04:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491861844; bh=p9EWvfzT3vsTy/C4lYE7xm36MGXiy4v/yneqbl+vpLM=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=B45FiVcIUqVSiNdpIkIS+baF/48FePJXAh3o3d7QRi8YNbzAMkyJzlnjeIVWjBqRl UCNGgkNJf5zcKT4n6zYc+10AD4Wm6GfcSA8fqR9jb6iWxJNuC/r6Tnrv3/ZnuYzU9s qCqC1EN41vd7tB5R2UR1JhyjvEcMuTIZVx5FpcgM=
Subject: Re: IAOC requesting input on (potential) meeting cities
To: IETF <ietf@ietf.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
Date: Mon, 10 Apr 2017 15:01:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7mt-pi5uUhmRnhM4VacMD7cnffI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 22:01:54 -0000

On 4/10/2017 11:54 AM, Carsten Bormann wrote:
> “In the short to medium term, I think the answer is going to be avoiding all but absolutely essential travel to the United States,” Hall [a UK lawyer] added. “I’m aware of at least one conference on cyber security and ethical hacking which switched to Toronto at short notice because of these concerns.”


That is, arguably looking like the safest, reasonable line of advice.

However for an organization like the IETF that seeks to meet in a 
variety of places around the globe, things could get even more 
challenging if there is a pattern of retaliatory actions by other 
countries, against visitors from the US.

(This is separate from the existing concern for long-term visitors to 
the US' question of leaving for a meeting and having problems returning 
to the US.)

It is fast looking as if the ability to sustain a large and very 
well-attended network of interconnected remote hubs might become a 
necessity rather than merely an appealing alternative...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 10 17:39:45 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37EC91293F8; Mon, 10 Apr 2017 17:39:27 -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_HELO_PASS=-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 u01rQ2Qe3umb; Mon, 10 Apr 2017 17:39:25 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 0CB501294C4; Mon, 10 Apr 2017 17:39:24 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2753B22E253; Mon, 10 Apr 2017 20:39:21 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
Date: Tue, 11 Apr 2017 10:39:18 +1000
Cc: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xcMJMUXHJA6UbETYHBJ0vbvVv1I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 00:39:27 -0000

Hi Carsten,

Couple of quic responses below.

On 10 Apr 2017, at 7:46 pm, Carsten Bormann <cabo@tzi.org> wrote:

> I agree that the introduction should focus on the Browser use case and =
keep out of the firewall traversal jungle.

OK. Just curious -- is there a strong motivation here? It seems very odd =
to tunnel HTTP-like semantics over a custom UDP protocol (COAP) over =
WebSockets over HTTP again, rather than just using HTTP (which AIUI you =
already have a mapping to).


>> Section 7 defines a number of new URI schemes for COAP protocols.
>> Syntactically, they use "+" to separate "coap" from the underlying
>> transport(-ish) protocol that they're bound to; e.g., "coap+tcp". =
This
>> syntax is allowed by RFC3986, but is unprecedented, and implies a
>> sub-syntax convention similar to those used in media types, etc. Is
>> there an expectation that other URI schemes starting with "coap+" are
>> reserved?=20
>=20
> There is no such expectation.
>=20
> We did have the discussion about reserved URI scheme prefixes in the =
IETF, and as I recall, the result was that there are none.  While it =
would be a bit weird to register a URI scheme starting with coap+ or =
coaps+ that is unrelated to CoAP, only the slightly boggled response =
from an expert review is in the way of that happening.
>=20
> Would the scheme names be more palatable with a dash instead of a =
plus?
> Careful choice of the scheme name mostly benefits the implementer, so =
it can be changed in the spec (at the cost of changing existing =
implementations).

OK. I'm mostly noting this in case other folks feel that this is a bad =
precedent for URI schemes; I think the bigger concern is the one below.


>> Defining URI schemes that switch transport protocol based upon their
>> name deserves wider review as well; this has been a contentious topic
>> in the past, and it would be good to understand what tradeoffs are
>> being made by doing so. Locking identifiers into a specific transport
>> protocol sacrifices much of the power of URLs.
>=20
> The =E2=80=9Csiloing=E2=80=9D of URIs along schemes is indeed a =
problem, which started for CoAP with the separation of the coap:/coaps: =
name spaces.  The CoRE WG did not see it as its task to address this =
shortcoming.  So, for now, we=E2=80=99ll have to live with it; =
approaches such as draft-silverajan-core-coap-protocol-negotiation are =
trying to address its practicalities.

By defining multiple URI schemes for different transports of the same =
protocol, the WG has taken a position as to what the solution is. I'm =
finding it difficult to square this with the continuing characterisation =
of CORE as "RESTful".


>> Furthermore, creating
>> "coap+ws" to denote a specific protocol over WebSockets (which has =
its
>> own URI scheme) is questionable; taken to its natural conclusion,
>> we'll have a proliferation of URI schemes for things over WebSockets.
>=20
> I=E2=80=99m not sure that a proliferation will happen =E2=80=94 =
WebSockets is mostly used for tightly bound proprietary protocols =
between a JavaScript mobile code client and a server that provides this =
mobile code client.  On the other hand, deciding to never use URIs to =
refer to resources available over a WebSockets protocol strikes me as an =
unnecessary restriction.
>=20
>> Will COAP take the same approach for HTTP?
>=20
> Not sure what this question is leading into.
> (We do have a defined relationship with HTTP, in RFC 7252 and RFC =
8075.
> But maybe this is about something different.)

I mean to ask whether there will be a need for a "coap+http" URI scheme; =
it seems like a logical conclusion of the approach taken here.=20


>> I would suggest a wider discussion of these issues on art@ / uri@.
>=20
> Indeed, a wider discussion of these longstanding issues would be =
useful.
> I=E2=80=99m not sure that waiting for their resolution is blocking =
this spec.
>=20
>> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
>> URI, using a well-known URI in the "wss" scheme. However, "wss" is =
not
>> defined to use well-known URIs, so this is an invalid use.=20
>=20
> This incorrect use of RFC 5785 is indeed embarrassing.  More about =
that later.

OK. The other obvious path is to opt wss:// (and ws://?) into RFC5785, =
but I think that would take a separate RFC that updates their scheme =
registrations. Not sure whether there would be any pushback in that =
community (but I can't see any immediate reason why there would be).


>> Section 8.1 makes it Mandatory to Implement the protocol without any
>> security ("NoSec"). This seems counter to best practice in the IETF,
>> but I'll defer to the Security Area review.
>=20
> Since it is the implementers who will decide whether they implement =
this, this co-author could live with making implementing NoSec =
completely optional.  (It will be anyway, in practice, at the level of =
what is actually configured.)  The important point(*) from the WG =
perspective here is that TLS is mandatory to implement, with the =
specifics depending on the security mode needed (cf. RFC 7925).  (Note =
also that there are other ways to provide security with CoAP.)

Ack. Again, this was mostly a note to bring it to others' attention; the =
use of the phrase "Mandatory to Implement" when applied to "no security" =
just seems odd.

Cheers,

>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> (*) =
https://github.com/core-wg/coap-tcp-tls/commit/fe348f543fc45e981e38e935424=
2012afb28dc60
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Mon Apr 10 18:26:17 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF23129417; Mon, 10 Apr 2017 18:26:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-grow-bgp-reject.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-grow-bgp-reject-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
Date: Mon, 10 Apr 2017 18:26:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MIUwAn-_tqOaf0qdbIIFDKcEp_c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 01:26:16 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-grow-bgp-reject-04
Reviewer:  Dale R. Worley
Review Date:  2017-04-10
IETF LC End Date:  2017-04-18
IESG Telechat date:  not scheduled

Summary:  This draft is basically ready for publication, but has nits
that should be fixed before publication.

This is the shortest draft I've ever reviewed.  There are only 41
lines of text that contain technical content.

My knowledge of BGP is quite limited, so I cannot review the
desirability of this solution.  I assume that the routing and
operations community has fully considered that question.

I find the wording of section 2 to be poor:

   2.  Solution Requirements

   The following requirements apply to the solution described in this
   document:

   o  Software MUST consider any routes ineligible for route
selection
      (section 9.1.1 [RFC4271]), if no import policy was configured
for
      the EBGP peer.

   o  Software MUST NOT advertise any routes to an EBGP peer, if no
      export policy was configured.

   o  Software SHOULD fall back to an "import nothing" and "export
      nothing" mode following failure of internal components, such as
a
      policy engine.

   o  Software MUST operate in this mode by default.

   o  Software MAY provide a configuration option to disable this
      security capability.

First, section 2 isn't the requirements for the solution, but the
requirements *on BGP speakers* constitute the solution itself.
Second, "software" seems to be a misnomer for "BGP speaker". 
(Compare
with RFC 4271.)  Third, the interaction of the final item with the
2119 words in the preceding items is awkward.  Fourth, it seems that
"routes" in the first item should be qualified by "advertised by an
EBGP peer".  In all cases, what is intended is clear, but the words
don't seem to say it well.

Revising the phrasing, I get:

   2.  Solution

   The following requirements apply to all BGP speakers:

   o A BGP speaker MUST consider any routes advertised by an EBGP
peer
      ineligible for route selection (section 9.1.1 [RFC4271]), if no
      import policy was configured for the peer.

   o  A BGP speaker MUST NOT advertise any routes to an EBGP peer, if
no
      export policy was configured.

   o  A BGP speaker SHOULD fall back to an "import nothing" and
"export
      nothing" mode following failure of internal components, such as
a
      policy engine.

   o  A BGP speaker MAY provide a configuration option to disable the
      preceding behaviors, but it MUST implement them by default.



From nobody Mon Apr 10 18:45:02 2017
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF5C11293F2; Mon, 10 Apr 2017 18:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 5rDaruX32T6A; Mon, 10 Apr 2017 18:44:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A749D128BB7; Mon, 10 Apr 2017 18:44:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEM15405; Tue, 11 Apr 2017 01:44:45 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 11 Apr 2017 02:44:44 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.121]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Tue, 11 Apr 2017 09:44:40 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90I1Qr5MFU/1kyZBIn9T3xh16G53MgAgAAGPoCAAANtAIAABASAgAAQtoCABGROEP//ycMAgAAxw4CAAADlgIABDlAA
Date: Tue, 11 Apr 2017 01:44:40 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED881A@nkgeml514-mbs.china.huawei.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com> <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com> <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
In-Reply-To: <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.191.175]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.58EC350E.0015, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.121, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9ea5c2356683d7cef74a5744d7b6aa9a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8P8KO87KUlGLTAlOPhTlL7Se9jA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 01:44:53 -0000

SGkgTGVzLCBSb2JlcnQgYW5kIEFsdmFybywNCg0KVGhhbmtzIGZvciBMZXMnIHByb3Bvc2VkIHRl
eHQuIEknbGwgdXBkYXRlIGl0IGFjY29yZGluZ2x5Lg0KDQpCLlIuDQpCaW5nDQoNCg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBSb2JlcnQgU3BhcmtzIFttYWlsdG86cmpz
cGFya3NAbm9zdHJ1bS5jb21dDQo+IFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDExLCAyMDE3IDE6MzYg
QU0NCj4gVG86IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpOyBMZXMgR2luc2JlcmcgKGdpbnNiZXJn
KTsgTGl1YmluZyAoTGVvKTsNCj4gZ2VuLWFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1p
c2lzLWF1dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGlzaXMtd2dAaWV0Zi5v
cmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYt
aXNpcy1hdXRvLWNvbmYtMDQNCj4gDQo+ICsxDQo+IA0KPiANCj4gT24gNC8xMC8xNyAxOjMyIFBN
LCBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKSB3cm90ZToNCj4gPiBXb3JrcyBmb3IgbWUhDQo+ID4N
Cj4gPiBUaGFua3MhDQo+ID4NCj4gPiBBbHZhcm8uDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0K
PiA+IE9uIDQvMTAvMTcsIDEwOjM0IEFNLCAiTGVzIEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5z
YmVyZ0BjaXNjby5jb20+DQo+IHdyb3RlOg0KPiA+DQo+ID4gQmluZy9Sb2JlcnQvQWx2YXJvIC0N
Cj4gPg0KPiA+IEhlcmUgaXMgdGhlIGV4aXN0aW5nIHRleHQgb2YgdGhlIFNlY3VyaXR5IFNlY3Rp
b246DQo+ID4NCj4gPiAgICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRoZW50aWNhdGlvbiBp
cyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KPiA+ICAgICBjb25maWd1cmF0aW9uIGFzIGl0IHJl
cXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQo+ID4NCj4gPiAgICAgRm9yIHdpcmVk
IGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0c2VsZiBjb3VsZCBiZQ0KPiBjb25z
aWRlcmVkDQo+ID4gICAgIGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53
YW50ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KPiA+ICAgICBub3QgYWJsZSB0byBjb25uZWN0IChp
LmUuIHRoZXJlIGlzIHNvbWUga2luZCBvZiBwaHlzaWNhbCBzZWN1cml0eSBpbg0KPiA+ICAgICBw
bGFjZSBwcmV2ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJvZ3VlIGRldmljZXMpOyBmb3Igd2ly
ZWxlc3MNCj4gPiAgICAgZGVwbG95bWVudCwgdGhlIGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFj
aGlldmVkIGF0IHRoZSBsb3dlcg0KPiA+ICAgICB3aXJlbGVzcyBsaW5rIGxheWVyLiINCj4gPg0K
PiA+DQo+ID4gUHJvcG9zZWQgcmV2aXNpb246DQo+ID4NCj4gPiAiSW4gdGhlIGFic2VuY2Ugb2Yg
Y3J5cHRvZ3JhcGhpYyBhdXRoZW50aWNhdGlvbiBpdCBpcyBwb3NzaWJsZSBmb3IgYW4NCj4gPiBh
dHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZyB0aGVyZSBpcyBhIGR1
cGxpY2F0ZQ0KPiA+IHN5c3RlbS1pZC4gVGhpcyBtYXkgdHJpZ2dlciBhdXRvbWF0aWMgcmVzdGFy
dCBvZiB0aGUgcHJvdG9jb2wgdXNpbmcgdGhlDQo+IGR1cGxpY2F0ZS1pZCByZXNvbHV0aW9uIHBy
b2NlZHVyZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50Lg0KPiA+DQo+ID4gTm90ZSB0aGF0IHRo
ZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCj4gPiBj
b25maWd1cmF0aW9uIGFzIGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQo+
ID4NCj4gPiAgICAgRm9yIHdpcmVkIGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0
c2VsZiBjb3VsZCBiZQ0KPiBjb25zaWRlcmVkDQo+ID4gICAgIGFzIGFuIGltcGxpY2l0IGF1dGhl
bnRpY2F0aW9uIGluIHRoYXQgdW53YW50ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KPiA+ICAgICBu
b3QgYWJsZSB0byBjb25uZWN0IChpLmUuIHRoZXJlIGlzIHNvbWUga2luZCBvZiBwaHlzaWNhbCBz
ZWN1cml0eSBpbg0KPiA+ICAgICBwbGFjZSBwcmV2ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJv
Z3VlIGRldmljZXMpOyBmb3Igd2lyZWxlc3MNCj4gPiAgICAgZGVwbG95bWVudCwgdGhlIGF1dGhl
bnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dlcg0KPiA+ICAgICB3aXJlbGVz
cyBsaW5rIGxheWVyLiINCj4gPg0KPiA+ID8/Pw0KPiA+DQo+ID4NCj4gPg0KPiA+DQoNCg==


From nobody Mon Apr 10 20:09:13 2017
Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF2DA129AF3 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_HTML_ATTACH=0.01, 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 ERndGmbfCVRg for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:08:59 -0700 (PDT)
Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) (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 13230129A9F for <ietf@ietf.org>; Mon, 10 Apr 2017 20:08:52 -0700 (PDT)
Received: by mail-wm0-f52.google.com with SMTP id u2so50664441wmu.0 for <ietf@ietf.org>; Mon, 10 Apr 2017 20:08:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HugrvemqyWmSo0guDatVZqsttkVxqSDItpXFpYQGOmw=; b=hF4igtPsaT58gXWfEAhXVqWdc6oqEC17k0MuMCOYWw/c2Y6LpcuNIhlIJhugSiFXto Cq0aCwkHy0pmmCt2twUvyFB3/dc1h1cWSSHSSwOlTertBb6+KtRUw2EFy1Jv4pksA2tn Re9y3jr97FiHGu9Iwg5MYOo/0M/qD1HQMXlyNt5pchvFDyWu6Su8QrBByjy5eKrYnVxy r9QBAg95IidvXnkqFJGhPyS+7F47PafZcS/xaOFizlKWLRvTzhPBQnW57/KRGQpKy6nk P9uCOmKrN8MMqWTsr6X2TBM2/bTYDGpmXsSKoIAVhXE8eeBPxEA0VDy2lTHivmJQSGVv 7E8Q==
X-Gm-Message-State: AN3rC/4mTNv2XkXIX3ne5CvYKFe53Ymki/hSKlUBHY1WRcdtOqaXGpiL 20gl9N26xbeR8g==
X-Received: by 10.28.66.77 with SMTP id p74mr13233357wma.107.1491880131345; Mon, 10 Apr 2017 20:08:51 -0700 (PDT)
Received: from localhost ([89.248.135.158]) by smtp.gmail.com with ESMTPSA id r5sm19672249wra.50.2017.04.10.20.08.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 20:08:49 -0700 (PDT)
Date: Tue, 11 Apr 2017 05:08:47 +0200
From: Job Snijders <job@ntt.net>
To: Dale Worley <worley@ariadne.com>
Cc: gen-art@ietf.org, draft-ietf-grow-bgp-reject.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-bgp-reject-04
Message-ID: <20170411030847.vxjgzavkwkj2ge2j@Vurt.local>
References: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="zhmrpzekvruzsstz"
Content-Disposition: inline
In-Reply-To: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5txQeT8Kor5eLWvKarqfvhfWOcA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 03:09:02 -0000

--zhmrpzekvruzsstz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Dear Dale, 

I'd be happy to incorporate these changes. I appreciate that you
clarified the text.

Attached is an easy-to-read html rfcdiff which contains Dale Worley's
proposed changes verbatim. Unless someone speaks up against this
proposal, I'll upload this as a new -05 revision somewhere in the next
few days.

Kind regards,

Job

On Mon, Apr 10, 2017 at 06:26:16PM -0700, Dale Worley wrote:
> Reviewer: Dale Worley
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft.  The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Document:  draft-ietf-grow-bgp-reject-04
> Reviewer:  Dale R. Worley
> Review Date:  2017-04-10
> IETF LC End Date:  2017-04-18
> IESG Telechat date:  not scheduled
> 
> Summary:  This draft is basically ready for publication, but has nits
> that should be fixed before publication.
> 
> This is the shortest draft I've ever reviewed.  There are only 41
> lines of text that contain technical content.
> 
> My knowledge of BGP is quite limited, so I cannot review the
> desirability of this solution.  I assume that the routing and
> operations community has fully considered that question.
> 
> I find the wording of section 2 to be poor:
> 
>    2.  Solution Requirements
> 
>    The following requirements apply to the solution described in this
>    document:
> 
>    o  Software MUST consider any routes ineligible for route selection
>       (section 9.1.1 [RFC4271]), if no import policy was configured
>       for the EBGP peer.
> 
>    o  Software MUST NOT advertise any routes to an EBGP peer, if no
>       export policy was configured.
> 
>    o  Software SHOULD fall back to an "import nothing" and "export
>       nothing" mode following failure of internal components, such as
>       a policy engine.
> 
>    o  Software MUST operate in this mode by default.
> 
>    o  Software MAY provide a configuration option to disable this
>       security capability.
> 
> First, section 2 isn't the requirements for the solution, but the
> requirements *on BGP speakers* constitute the solution itself.
> Second, "software" seems to be a misnomer for "BGP speaker".  (Compare
> with RFC 4271.)  Third, the interaction of the final item with the
> 2119 words in the preceding items is awkward.  Fourth, it seems that
> "routes" in the first item should be qualified by "advertised by an
> EBGP peer".  In all cases, what is intended is clear, but the words
> don't seem to say it well.
> 
> Revising the phrasing, I get:
> 
>    2.  Solution
> 
>    The following requirements apply to all BGP speakers:
> 
>    o A BGP speaker MUST consider any routes advertised by an EBGP peer
>      ineligible for route selection (section 9.1.1 [RFC4271]), if no
>      import policy was configured for the peer.
> 
>    o  A BGP speaker MUST NOT advertise any routes to an EBGP peer, if
>       no export policy was configured.
> 
>    o  A BGP speaker SHOULD fall back to an "import nothing" and
>       "export nothing" mode following failure of internal components,
>       such as a policy engine.
> 
>    o  A BGP speaker MAY provide a configuration option to disable the
>       preceding behaviors, but it MUST implement them by default.

--zhmrpzekvruzsstz
Content-Type: text/html; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-grow-bgp-reject-05-from-4.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Darwin Vurt.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:45:33 PST 2017; root:xnu-3789.51.2~1/RELEASE_X86_64 x86_64 --> 
<!-- Using awk: /usr/local/bin/gawk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 3.1.5, GNU MP 6.1.2) --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (GNU wdiff) 1.2.2 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-grow-bgp-reject-04.txt - draft-ietf-grow-bgp-reject-05.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-grow-bgp-reject-04.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-grow-bgp-reject-05.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Global Routing Operations                                       J. Mauch</td><td> </td><td class="right">Global Routing Operations                                       J. Mauch</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                    Akamai</td><td> </td><td class="right">Internet-Draft                                                    Akamai</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Standards Track                             J. Snijders</td><td> </td><td class="right">Intended status: Standards Track                             J. Snijders</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">September 28, 2017</span>                                          NTT</td><td> </td><td class="rblock">Expires: <span class="insert">October 13, 2017  </span>                                          NTT</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                              G. Hankins</td><td> </td><td class="right">                                                              G. Hankins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                                   Nokia</td><td> </td><td class="right">                                                                   Nokia</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                          <span class="delete">March 27</span>, 2017</td><td> </td><td class="rblock">                                                          <span class="insert">April 11</span>, 2017</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">        Default EBGP Route Propagation Behavior Without Policies</td><td> </td><td class="right">        Default EBGP Route Propagation Behavior Without Policies</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-grow-bgp-reject-0<span class="delete">4</span></td><td> </td><td class="rblock">                     draft-ietf-grow-bgp-reject-0<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines the default behavior of a BGP speaker when</td><td> </td><td class="right">   This document defines the default behavior of a BGP speaker when</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   there is no import or export policy associated with an External BGP</td><td> </td><td class="right">   there is no import or export policy associated with an External BGP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   session.</td><td> </td><td class="right">   session.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 41</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 41</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">September 28</span>, 2017.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">October 13</span>, 2017.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right">   carefully, as they describe your rights and restrictions with respect</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to this document.  Code Components extracted from this document must</td><td> </td><td class="right">   to this document.  Code Components extracted from this document must</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   include Simplified BSD License text as described in Section 4.e of</td><td> </td><td class="right">   include Simplified BSD License text as described in Section 4.e of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Trust Legal Provisions and are provided without warranty as</td><td> </td><td class="right">   the Trust Legal Provisions and are provided without warranty as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described in the Simplified BSD License.</td><td> </td><td class="right">   described in the Simplified BSD License.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2</td><td> </td><td class="right">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Solution <span class="delete">Requirements</span> . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="rblock">   2.  Solution <span class="insert"> . . . . . .</span> . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 3, line 5</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 3, line 5</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interconnected, the risk of a misbehaving BGP speaker poses</td><td> </td><td class="right">   interconnected, the risk of a misbehaving BGP speaker poses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   significant risks to Internet routing.</td><td> </td><td class="right">   significant risks to Internet routing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This specification intends to improve this situation by requiring the</td><td> </td><td class="right">   This specification intends to improve this situation by requiring the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   explicit configuration of a BGP import and export policy for any</td><td> </td><td class="right">   explicit configuration of a BGP import and export policy for any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   External BGP (EBGP) session such as customers, peers, or</td><td> </td><td class="right">   External BGP (EBGP) session such as customers, peers, or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   confederation boundaries for all enabled address families.  When this</td><td> </td><td class="right">   confederation boundaries for all enabled address families.  When this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   solution is implemented, BGP speakers do not accept or send routes</td><td> </td><td class="right">   solution is implemented, BGP speakers do not accept or send routes</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   without policies configured on EBGP sessions.</td><td> </td><td class="right">   without policies configured on EBGP sessions.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">2.  Solution<span class="delete"> Requirements</span></td><td> </td><td class="rblock">2.  Solution</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   The following requirements apply to <span class="delete">the solution described in this</span></td><td> </td><td class="rblock">   The following requirements apply to <span class="insert">all BGP speakers:</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   document:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software MUST consider any routes ineligible for route selection</span></td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker MUST consider any routes advertised by an EBGP peer</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      (section 9.1.1 [RFC4271]), if no import policy was configured for</td><td> </td><td class="right">      (section 9.1.1 [RFC4271]), if no import policy was configured for</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      the <span class="delete">EBGP </span>peer.</td><td> </td><td class="rblock">      the peer.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software</span> MUST NOT advertise any routes to an EBGP peer, if no</td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> MUST NOT advertise any routes to an EBGP peer, if no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      export policy was configured.</td><td> </td><td class="right">      export policy was configured.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software</span> SHOULD fall back to an "import nothing" and "export</td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> SHOULD fall back to an "import nothing" and "export</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      nothing" mode following failure of internal components, such as a</td><td> </td><td class="right">      nothing" mode following failure of internal components, such as a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      policy engine.</td><td> </td><td class="right">      policy engine.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software MUST operate in this mode by default.</span></td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> MAY provide a configuration option to disable <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"><span class="insert">      preceding behaviors, but it MUST implement them by default.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Software</span> MAY provide a configuration option to disable <span class="delete">this</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      security capability.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">3.  Acknowledgments</td><td> </td><td class="right">3.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The authors would like to thank the following people for their</td><td> </td><td class="right">   The authors would like to thank the following people for their</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   comments, support and review: Shane Amante, Christopher Morrow,</td><td> </td><td class="right">   comments, support and review: Shane Amante, Christopher Morrow,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td> </td><td class="right">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas <span class="delete">Bagdonas and</span> Donald</td><td> </td><td class="rblock">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas <span class="insert">Bagdonas,</span> Donald</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Smith.</span></td><td> </td><td class="rblock">   <span class="insert">Smith, and Dale Worley.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.  Security Considerations</td><td> </td><td class="right">4.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document addresses a basic routing security issue caused by</td><td> </td><td class="right">   This document addresses a basic routing security issue caused by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   permissive default routing policy configurations.  Operators need</td><td> </td><td class="right">   permissive default routing policy configurations.  Operators need</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementers to address this problem with more secure defaults to</td><td> </td><td class="right">   implementers to address this problem with more secure defaults to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mitigate collateral damage on Internet routing.  Inadvertent or</td><td> </td><td class="right">   mitigate collateral damage on Internet routing.  Inadvertent or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   adversarial advertisements cause business impact that can be</td><td> </td><td class="right">   adversarial advertisements cause business impact that can be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mitigated by a secure default behavior.</td><td> </td><td class="right">   mitigated by a secure default behavior.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 13 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>18 lines changed or deleted</i></th><th><i> </i></th><th><i>15 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--zhmrpzekvruzsstz--


From nobody Mon Apr 10 20:47:47 2017
Return-Path: <lloyd.wood@yahoo.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A254E128D40 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.798
X-Spam-Level: 
X-Spam-Status: No, score=-3.798 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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=yahoo.co.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 l5NEdlO4Y05I for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:47:44 -0700 (PDT)
Received: from nm11-vm3.bullet.mail.ir2.yahoo.com (nm11-vm3.bullet.mail.ir2.yahoo.com [212.82.96.164]) (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 37891124BFA for <ietf@ietf.org>; Mon, 10 Apr 2017 20:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1491882461; bh=tAWx9edMCxEWadmZM5ONWBxRrdauxj1dne5D2uuU8A8=;  h=Date:From:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=bue7rs4+UBgXx9PpTQI4xmR/4l02cx+iSsAe7Du5Z/DT6D1LqSrwAPWXqYforS69+O14dSmUammx4pDYfMCf1zE/F7A8Rj9UFokLXUqi6WcvFnf/6bg3swC0kmPRQyksousWT1I2qqtVEgDu8CSkZSJYtQ+M2ELs8w8U8va+lm2XRNmNBC798opB0WvzQ7XlfDyuPCtjbBhs6heTe+TQWwbfpKwqqrZQdUxmqj2zmZB8NILzXvG7tOFvTEtNOLFhQXyqJyABzoBpBPjrAcXHI3eS6dC7Wx0XgG2csKvhIeQzlJ2nWH/M3CuLfauBeRy4pZY5SPrPtIi0Mzdopw6DVA==
Received: from [212.82.98.58] by nm11.bullet.mail.ir2.yahoo.com with NNFMP; 11 Apr 2017 03:47:41 -0000
Received: from [212.82.98.73] by tm11.bullet.mail.ir2.yahoo.com with NNFMP; 11 Apr 2017 03:47:41 -0000
Received: from [127.0.0.1] by omp1010.mail.ir2.yahoo.com with NNFMP; 11 Apr 2017 03:47:41 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 597966.55124.bm@omp1010.mail.ir2.yahoo.com
X-YMail-OSG: 0_uOSIAVM1mPMlz0XW7uH3GzjZtZgjXhuuCVW.y7.mvQ_JpMNRIAq3et8RHrtCA aS2B9fkeJqzytnCjXMisc5lKze342uCNNJCo.fwr6wlzDgMcMTvDFqPCFwcEdsrjqU5XXMByPaVF C8Hq8p.5NzxWsAU8CJJnY.nTz7mzTFM.4X5XZIjf5YUW0z.xpHIFSx9IKPWi7t23M_vBA7zldeeK i7nPPD9gbXbQwojPfJ8g2pxGZ7ydDEJvPpi2toPVxaJk1vtu7yquPrsiO01mu6ioDAFEltoZZDLh wDklOzSIUT2cTz4omYBNnzDr3zdEz4RVQCWMHhl2RaiPkJtvrMrxCrLdhj7_GW47o6l1sEgT5eba rkvpSm_ux3S8jxD0RyDsIycy_Idp5WhXsuby3YCst_zjikRlox.ggPk5LYnQnJ3PMKlH2Oa3a6QP uLe3JM.HzT2UxHv1v4ZUI3K.YPCF8sBBo17tmQwLWYz3iUzQGPySiLEQujSa5p94yta0TgGcWUvz G8JIYklJesXhsk4_JboQbPmn8BbNJQhhNuzcVD3WSaQDlC7sPlAnkNZesn.KRi2T93zHb
Received: from jws700018.mail.ir2.yahoo.com by sendmailws106.mail.ir2.yahoo.com; Tue, 11 Apr 2017 03:47:41 +0000; 1491882461.086
Date: Tue, 11 Apr 2017 03:47:30 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Randy Bush <randy@psg.com>, Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: ietf <ietf@ietf.org>
Message-ID: <184069059.241822.1491882450970@mail.yahoo.com>
In-Reply-To: <m2shljpmn4.wl-randy@psg.com>
References: <CAHLBt81aHb9BjDqy579mShMPcWET2nAwvd9uiM0zsnYbNLHqeg@mail.gmail.com> <AM4PR0401MB22414069AFBBD199F585B055BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com> <m2shljpmn4.wl-randy@psg.com>
Subject: Re: Fw: [Int-area] IETF 98 Minutes
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_241821_936991642.1491882450968"
X-Mailer: WebService/1.1.9374 YahooMailIosMobile Raven/37662 CFNetwork/811.4.18 Darwin/16.5.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rTAhc2LGvdkp7qt3Z5_765wiBqY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 03:47:46 -0000

------=_Part_241821_936991642.1491882450968
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px =
#715FFA solid !important; padding-left:1ex !important; background-color:whi=
te !important; } What?
RFC 1883 - Internet Protocol, Version 6 (IPv6) Specification=C2=A0
rfc2460=C2=A0

 =20
| =20
|   | =20
RFC 1883 - Internet Protocol, Version 6 (IPv6) Specification
=20
By Hinden, R.
=20
This document specifies version 6 of the Internet Protocol (IPv6), also som=
etimes referred to as IP Next Generation or IPng. [STANDARDS- TRACK]
  |   |

  |

=20
RFC2460, published 1998, clearly says at the top that it obsoletes rfc1883,=
 which was published in 1995.
and the ietf would call a singular error an "errata" - sigh.

kids these days.

Lloyd Woodlloyd.wood@yahoo.co.uk

On Saturday, April 8, 2017, 2:08 pm, Randy Bush <randy@psg.com> wrote:

>> IPv6 was 1995 not 1998.
>=20
> Then we should blame the ietf and the IPv6 authors for the wrong
> information listed in the IPv6 RFC 2460.
>=20
> https://www.ietf.org/rfc/rfc2460.txt

if it is indeed erronious, we would call it an "erratum" not "blame."

randy





------=_Part_241821_936991642.1491882450968
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html xmlns=3D"http://www.w3.org/1999/xhtml" xmlns:v=3D"urn:schemas-microso=
ft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office"><head><!--[=
if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>=
96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><bo=
dy>
<style type=3D"text/css" scoped> blockquote, div.yahoo_quoted { margin-left=
: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex =
!important; background-color:white !important; } </style>What?<div><br></di=
v><div><a href=3D"https://tools.ietf.org/html/rfc1883" target=3D"_blank" cl=
ass=3D"enhancr2_A68A059C-58B8-4205-90D4-94DF647D949D">RFC 1883 - Internet P=
rotocol, Version 6 (IPv6) Specification</a>&nbsp;</div><div><br></div><div>=
rfc2460&nbsp;<br><div><br></div><div id=3D"enhancr2_A68A059C-58B8-4205-90D4=
-94DF647D949D" class=3D"yahoo-link-enhancr-card yahoo-link-enhancr-cardSize=
-medium yahoo-link-enhancr-cardType-yenhancr yahoo-link-enhancr-cardCategor=
y-article yahoo-link-enhancr-not-allow-cover ymail-preserve-class ymail-pre=
serve-style yahoo-link-enhancr-no-image" style=3D"max-width:400px;font-fami=
ly:'Helvetica Neue', Helvetica, Arial, sans-serif;" contenteditable=3D"fals=
e" data-url=3D"https://tools.ietf.org/html/rfc1883" data-type=3D"LINK_ENHAN=
CR_ATTACHMENT_TYPE_INLINE" data-category=3D"article" data-embed-url=3D"" da=
ta-size=3D"medium">
    <a href=3D"https://tools.ietf.org/html/rfc1883" style=3D"text-decoratio=
n:none !important; color: #000 !important" class=3D"yahoo-enhancr-cardlink"=
 target=3D"_blank" rel=3D"noreferrer">
        <table class=3D"card-wrapper" cellpadding=3D"0" cellspacing=3D"0" b=
order=3D"0" style=3D"max-width:400px;">
            <tbody><tr>
            <td width=3D"400">
                <table class=3D"card-info" cellpadding=3D"0" cellspacing=3D=
"0" border=3D"0" width=3D"100%" style=3D"background:#fff;max-width:400px;bo=
rder:1px solid #e0e4e9;border-bottom:3px solid #000000;">
                    <tbody><tr>
                        <td style=3D"vertical-align:top;padding:16px 0 16px=
 12px;">
                        </td>
                       =20
                        <td style=3D"vertical-align:middle;padding:16px 12p=
x;width:99%;">
                            <h2 class=3D"card-title" style=3D"margin:0 0 4p=
x 0;font-size:16px;font-family:'Helvetica Neue', Helvetica, Arial, sans-ser=
if;">RFC 1883 - Internet Protocol, Version 6 (IPv6) Specification</h2>
                                <p class=3D"card-richinfo-primary" style=3D=
"font-size:11px;line-height:15px;color:#999;">By Hinden, R.</p>
                            <p class=3D"card-description" style=3D"font-siz=
e:11px;line-height:15px;color:#999;">This document specifies version 6 of t=
he Internet Protocol (IPv6), also sometimes referred to as IP Next Generati=
on or IPng. [STANDARDS- TRACK]</p>
                        </td>
                       =20
                        <td style=3D"text-align:right;padding:16px 12px 16p=
x 0;">
                        </td>
                    </tr>
                </tbody></table>
            </td>
            </tr>
        </tbody></table>
    </a>
</div><div><br></div>RFC2460, published 1998, clearly says at the top that =
it obsoletes rfc1883, which was published in 1995.</div><div><br></div><div=
>and the ietf would call a singular error an "errata" - sigh.<br><br>kids t=
hese days.<br><br>Lloyd Wood<div>lloyd.wood@yahoo.co.uk</div><br><p class=
=3D"yahoo-quoted-begin" style=3D"font-size: 15px; color: #715FFA; padding-t=
op: 15px; margin-top: 0">On Saturday, April 8, 2017, 2:08 pm, Randy Bush &l=
t;randy@psg.com&gt; wrote:</p><blockquote class=3D"iosymail"><div dir=3D"lt=
r"><div class=3D"yqt9429603297" id=3D"yqtfd41188">&gt;&gt; IPv6 was 1995 no=
t 1998.<br clear=3D"none">&gt; <br clear=3D"none">&gt; Then we should blame=
 the ietf and the IPv6 authors for the wrong<br clear=3D"none">&gt; informa=
tion listed in the IPv6 RFC 2460.<br clear=3D"none">&gt; <br clear=3D"none"=
>&gt; <a shape=3D"rect" href=3D"https://www.ietf.org/rfc/rfc2460.txt" targe=
t=3D"_blank">https://www.ietf.org/rfc/rfc2460.txt</a></div><br clear=3D"non=
e"><br clear=3D"none">if it is indeed erronious, we would call it an "errat=
um" not "blame."<br clear=3D"none"><br clear=3D"none">randy<div class=3D"yq=
t9429603297" id=3D"yqtfd53979"><br clear=3D"none"><br clear=3D"none"></div>=
</div><blockquote></blockquote></blockquote></div>
</body></html>
------=_Part_241821_936991642.1491882450968--


From nobody Mon Apr 10 20:49:56 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ADADC129A9F; Mon, 10 Apr 2017 20:49:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mark Nottingham <mnot@mnot.net>
To: <art@ietf.org>
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
Subject: Artart last call review of draft-ietf-core-links-json-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149188258769.15738.17473942496982365590@ietfa.amsl.com>
Date: Mon, 10 Apr 2017 20:49:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fiq_PjWfJ-Pimg1HiKJG6wUJERA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 03:49:48 -0000

Reviewer: Mark Nottingham
Review result: Ready with Issues

This specification is a relatively straightforward mapping of the
format described in RFC6690 (itself a serialisation of RFC5988bis
links) into JSON and CBOR. I don't have deep knowledge of CBOR, but
given the editorship of the document, I trust it's seen adequate
review in that regard.

The only potential issue is how this is achieved. Rather than defining
two new serialisations of RFC5988bis links (into JSON and CBOR), it
describes how to re-serialise RFC6690 documents into JSON and CBOR.
This means that any constraints upon RFC6690 documents are also
mirrored into these formats; e.g., the target IRI is constrained to be
a URI in 6690, and therefore can also only be a URI in JSON and CBOR,
despite these formats' ability to easily convey non-ASCII content.

In other words, the specification currently defines these link formats
in terms of the Link header (as defined in section 5 of RFC5988) --
along with all of the foibles of HTTP header syntax -- rather than
their abstract model (defined in Section 3).

Whether or not this is a problem depends on what's desired; if 6690 is
seen as effectively a profile of 5988, then it makes sense to express
it in those terms. If the full range of links capable of being
expressed in 5988 is desired, creating new serialisations of 5988
links (without a hop through 6690) is preferable.

If the current approach is kept, it'd be nice to clarify this
situation a bit in the Introduction.



From nobody Mon Apr 10 20:55:24 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D7A127866 for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:55:23 -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 nINWrUlUbLEL for <ietf@ietfa.amsl.com>; Mon, 10 Apr 2017 20:55:17 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 C7C41126B71 for <ietf@ietf.org>; Mon, 10 Apr 2017 20:55:16 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id s16so42534078pfs.0 for <ietf@ietf.org>; Mon, 10 Apr 2017 20:55:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=18pQSezVamMJm2HY616mxLLqLkBY3nqcgpjE43B+82I=; b=VDjP4sjR7o7SxfSB/pPFZZopjvzxSOMGmpyp2gl02JbwZ09bb9UI1HzKSChHvTsmi/ qXWXTeLMpsKqhvL+MVudePpi7MH5nnfnBXl7TluBd1CTZxPv6Z1d7aV1IP1WQZuvevaG AyLvtJpFtIa1bqHAY5HYeCByU3fcfwxlQrFo8hqEhc8iItY1w9kAfHu4IMR7FCTC98K/ dax2x7Dlt19kLyluiOo3yp+OQ7t4d4E3qAMXdoWyZyapGkV4Nuck7oVXh0AsbrnyKaw1 v461k2YD0mlOPoRPY/cd57zfQPovc0SaWJP8SWTAnxmdKRk9N3mBDDcGxXtlDyyo320x Exkw==
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=18pQSezVamMJm2HY616mxLLqLkBY3nqcgpjE43B+82I=; b=jJIvawx3HEc8DadXBbIymX+COS4ByONgk1FEd65/295NGFS+aXy0XnZp5/PV+dd0I9 MgGEOIumErHs1tWZa/pm+keO1qZOJ8L1Pw9ra4z56zRqfETdX2fEA0NKV9voMMJnTmtB 1PQFupZQA0UpwOX8Ua6s1Gri2e4WiowMwg1o9o0bRy3dKXwvkAMZJTKZwrrbZ9sNfcd7 oYahdMK6iLliUrNDeGVaNBQXQxY0yynNTbdhaTqepubSbIXc0146lvbzUWMeKrYzMr3T vo3wPejkFw/xBRJI/VTcOew5ZpeVcZtGDKFKwsMJBNv377Xs0reCS6gm0XS3hTcomzBm +IRg==
X-Gm-Message-State: AFeK/H2rvzFwNn7QcqNilDEj3o3WShNiHyrytZ+iwW0I9XgB1iWrBjzZU0WYbGEHmQt7/r1yFnhk9gT8sR3mAg==
X-Received: by 10.84.142.133 with SMTP id 5mr73095592plx.129.1491882915136; Mon, 10 Apr 2017 20:55:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.128.131 with HTTP; Mon, 10 Apr 2017 20:54:34 -0700 (PDT)
In-Reply-To: <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 10 Apr 2017 23:54:34 -0400
Message-ID: <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Martin Thomson <martin.thomson@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nLs-goMaT2rf3ts3_0Q8jFk43kE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 03:55:23 -0000

Hi Martin,

We went through your comments one more time to make sure any
technical/substantive comments are addressed.  Please see the
discussion inline.


On Mon, Apr 10, 2017 at 5:05 PM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> I most certainly reviewed 09. I haven't reviewed the diff. I doubt that it
> would change my opinion on the macro - level problems.

My mistake, I thought the acronym you corrected was in version 9.

>
> On 8 Apr. 2017 3:34 am, "Kathleen Moriarty"
> <kathleen.moriarty.ietf@gmail.com> wrote:
>
> Hello Martin,
>
> Thanks for your review.  It seems that you have read version 8 or
> earlier and not the current version, 9, from some of your suggestions
> that have been corrected already.  Your review also reads to me that
> additional context setting may help, but please note that some context
> setting was improved in version 9.  We re-arranged some of the
> sections per IESG review recommendations in the latest version as
> well.
>
> Perhaps you have additional language suggestions for context setting?
>
> The abstract states:
>
>    Increased use of encryption impacts operations for security and
>    network management causing a shift in how these functions are
>    performed.  In some cases, new methods to both monitor and protect
>    data will evolve.  In other cases, the ability to monitor and
>    troubleshoot could be eliminated.  This draft includes a collection
>    of current security and network management functions that may be
>    impacted by the shift to increased use of encryption.  This draft
>    does not attempt to solve these problems, but rather document the
>    current state to assist in the development of alternate options to
>    achieve the intended purpose of the documented practices.
>
> which is repeated again in the introduction, but slightly reworded.
> The introduction also includes statements on the existing publications
> related to encryption and I read them as not having any bias, but
> rather supporting the existing documents that also had consensus.
>
> A couple of comments and one question inline.
>
> On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
>> Draft: draft-mm-wg-effect-encrypt-09
>> Date: 2017-04-07
>>
>> Overall
>>
>> This document is unfocused and unclear in its intent.  It is filled with
>> unsubstantiated claims, misleading statements, bias, and implied
>> recommendations
>> for bad practices.  I would oppose its publication in the current form.
>> Furthermore, I don't believe that small scale or editorial changes would
>> be
>> sufficient to correct these problems.
>>
>>
>> Aside from weakening its utility and/or arguments, the lack of focus will
>> allow
>> this document to be abused in various ways.  For instance, it might imply
>> IETF
>> endorsement of the practices described in the document.  Given that the
>> IETF has
>> published positions that in some cases reject these practices, this
>> document
>> needs to be very precise with its claims.  In its current form, it is not
>> nearly
>> careful enough.

This paragraph is all speculation about an unfortunate future.
We could speculate that the operator, security and app communities
come together to work out solutions after reading this doc,
which is part of our intent.

>>
>> If this document is going to be published as an RFC, then it needs to be
>> very
>> clear about its intent and its position - or lack thereof - toward these
>> practices.  It might be possible to say that these practices were employed
>> in
>> networks in the past and that encryption is reducing the viability of
>> those
>> practices.  A value-neutral statement like that might be acceptable as
>> long as
>> it were framed carefully.

The document conveys that message everywhere. The words contributed were
changed in many places to remove any implication that the current practices
are "requirements" or even "needs".

The abstract and introduction contain value neutral statements like
what you are suggesting already.  We actually say the practices may be
eliminated, going further than your request as that may be the case.

The only change I could see in the abstract would be the following:

   Increased use of encryption impacts operations for security and
   network management causing a shift in how these functions are
   performed.  In some cases, new methods to both monitor and protect
   data will evolve.  In other cases, the ability to monitor and
   troubleshoot could be eliminated.  This draft includes a collection
   of current security and network management functions that may be
   impacted by the shift to increased use of encryption and encryption
that is designed prevent interception.  This draft
   does not attempt to solve these problems, but rather document the
   current state to assist in the development of alternate options to
   achieve the intended purpose of the documented practices when possible.

Do you have additional suggestions?  Or is the phrasing read
differently than we intended by stating functions may be eliminated?
We thought that was very clear to your points.

>>
>> What is problematic is the implicit argument that is presented.  This
>> document
>> could easily be construed as the IETF legitimizing these practices.  This
>> includes things on which the IETF has published statements (see for
>> example RFC
>> 2804).
>
> See the abstract and introduction and summary.
>
>>
>> This steps firmly into to sticky mess that is the politics of encryption
>> policy.
>> If the IETF is going to make a political statement with this document,
>> then that
>> statement needs to be a lot better than this.

The intent of this document is to help operators as these changes
continue.  It is to make sure we are not ignoring the impact of the
changes the IETF has with our decision (which are supported in this
document).  This document is intended to assist operators.  By
explaining the functions being performed, some have already been
provided alternate methods to achieve their goals.  We have also
received quite a bit of positive feedback from operators - that this
document helped them come back to the discussion and to approach a
world with more encryption or sessions that can't be intercepted (TLS
1.3, TCPinc, QUIC, etc.).

>>
>> Furthermore, any statement needs to be consistent with previous
>> statements,
>> where in this case that primarily means RFC 7258.  Right now it reads as
>> an
>> attempt to dilute RFC 7258.
>
> Not at all.

It does not read that way to many people who strongly support RFC
7258, including Stephen who was our sponsoring AD (and was for 7258).
Can you give specific sections where it sounds like we are weakening
RFC 7258 so we can change that specific wording?

>
>>
>> If this document were more clearly formulated as an even-handed treatment
>> of
>> what happens today - without judgment - then it could be useful.  Here the
>> model
>> of RFC 7754 is a good one.  It describes the different facets of a use
>> case,
>> then the different practices that might be employed to achieve that goal.
>> For
>> each practice the pros, cons, and technical limitations are covered with
>> an eye
>> to all involved parties.
>>

Version 8 to 9 had some edits to remove statements with used terms
like 'need'.  We may have missed a couple, we'll check the ones you
pointed out.  There are also numerous statements that are explicitly
in support of RFC7258.  These are in the abstract, introduction,
summary and sprinkled throughout the document.

Apparently, RFC 7754 goes further than our scope. We are not describing:
"... the different practices that might be employed to achieve that goal."

>>
>> The Real Purpose of this Document
>>
>> I think that this is the real question that this document wants to ask is:
>>
>>    In a world where we are forced to defend against pervasive monitoring
>> by
>>    motivated and malicious actors, can we find a role for less pervasive
>>    monitoring by well-intentioned entities?

The document aims to help operators by giving them a chance to discuss
the impact.  It opens the
door to conversation so they can find new ways to achieve the same
goals (better performance for customers for instance or monitoring
services that have been requested - web content, DLP), which may mean
endpoint solutions are needed or filtering limited to hostnames for
now until other mechanisms are developed (likely at the application
layer).

For enterprises, application and host level solutions are
fine as many organizations have employees sign away their rights to
privacy.  I would never check FaceBook from work for instance or
access any site of a personal nature.  This is why we broke out the
sections by the type of network or SP, their options are different
with and without encryption.

QUESTION: Would it help to add some text like the first paragraph into
the introduction?  - This document aims to...

>>
>> There is an interesting discussion to be had here, but I'm convinced after
>> my
>> review that this document is the wrong vehicle for that discussion.

RFCs are the vehicles the IETF has found most useful in talking to the world.

>>  I'm
>> also
>> inclined to suggest that this is the wrong question to ask in the first
>> place.

We can't ignore the problems resulting from the changes, we the IETF
make, to improve privacy and security.  While we agree it is a positive
thing to improve these functions, we (the IETF) should also help with
the wake we
leave in our path.  Otherwise, we can't expect people to play along
with the protocol specifications the IETF publishes.

It's much more than an "interesting discussion" to many operators.
Some are required by law to use these practices to protect privacy.

There are many questions to ask, some of which have already been
answered. For example, RFC 7258 asked 'How can we deal with
pervasive monitoring' and answered it through the same IETF
consensus process this document has already gone through.

>>
>> To the extent that we have the tools necessary to protect against
>> pervasive
>> monitoring, we have to accept that more-legitimate uses of monitoring are
>> collateral.  Mostly, that's just a function of the limitations of the
>> imperfect
>> tools we have.
>>
>> The value in this document is in the rather comprehensive collection of
>> use
>> cases.  Sure, some we might not attribute much weight to, like
>> wiretapping.
>> Others are frankly frightening and not just in the Orwellian sense.
>>
>> The problems that are implied by the current practices of network
>> operators is a
>> large vein of unexplored work for the community.  Spending effort on
>> finding
>> better solutions to legitimate problems is worthwhile.

Right, so we started by documenting them *before* the collateral damage appears.

>>
>> In other words, the right question might be:
>>
>>    For each of these practices that we see today, are the use cases that
>>    motivate them legitimate and how might be implement alternative
>> techniques
>>    that properly respect privacy and security?
>>

Yes, this is the point of the document and it's stated in several places.

>>
>> Two- and Three- Party Interactions
>>
>> A great many sections of the document are unclear about the relationships
>> between different actors.  It seems like many of the activities describe,
>> which
>> are presented here as being beneficial, are performed by a third party
>> without
>> the consent or involvement of the two communicating peers.  After all,
>> those are
>> the cases where encryption most often interferes.
>>

As the draft says, some of the methods will be eliminated.

>> The assertion that some benefit is accrued to communicating peers as a
>> result of
>> these actions is the constant subject of the text.  I observe that in most
>> of
>> the cases listed in this document, the benefit is accrued primarily to the
>> third
>> party.

Operators by their nature have different privacy concerns than their end
users. Operators by their nature want to accrue benefits. This document
doesn't change the balance; instead, it tells them how to deal with privacy
that has already been applied.  While we agree with your statement and think
it's important to build privacy and privacy options into IETF protocols,
operators often don't care, despite the many RFCs we have published
telling them that they should care. We still need to engage them so we can
have this discussion.

The "third party" is likely the only one receiving a trouble call,
and there is benefit for all parties when the trouble is cleared.

>>
>> Clarity around the arguments that the document makes with respect to
>> benefits to
>> each of the involved parties is sorely lacking.
>>
>> In addition to this, where benefits truly do accrue to communicating
>> peers,
>> technical options that don't rely on privacy-invasive techniques are
>> routinely
>> dismissed in an offhand fashion.  In this way, any moral imprimatur
>> attributed
>> to the use case is used to justify the privacy-invasive method.
>>

Without specific comments, the above are all subjective statements and
we have responded to them.

>>
>> Document Structure
>>
>> This document is very hard to read (and review).  Probably my biggest
>> complaint
>> is that the sections are haphazardly organized.  They contain a mixture of
>> use
>> cases (what does SP X want to do) and techniques (how do they do these
>> things).
>> Material is duplicated between sections.  Sections cover 10 different use
>> cases
>> while talking about techniques, then other sections talk about different
>> techniques whiles talking about a scenario.  This leads to a lot of
>> repetition.
>>
>> There are three axes that this document contemplates:
>>
>>  - the techniques that are currently used in networks
>>  - the use cases that motivate these techniques
>>  - the deployment scenarios in which these use cases manifest
>>
>> It would appear that the document attemps to start from the deployment
>> scenarios.  However, this causes use cases and techniques to be mixed.
>> Judicious use of cross-referencing might have made this arrangement
>> tractable,
>> but there are virtually no cross references.
>>

The above is stylistic in nature.  We've already made changes to the
format to address specific comments in IESG review. A complete
re-write is not appropriate at this point in the draft lifecycle.
That's not the point of IESG review.

>>
>> Section 1
>>
>> I find the introduction of this document difficult to parse.  I think that
>> what
>> it wants to say is pretty straightforward, but it manages this in quite an
>> obtuse way.  Here's what I think that it is trying to say:
>>
>> 1. The IETF (and the larger community) has reacted to revelations of
>> pervasive
>>    monitoring by increasing the use of encryption.
>> 2. That has been somewhat successful.
>> 3. More encryption has an impact on some practices that network operators
>> have
>>    become accustomed to employing.
>>
>> Expressed in this way, you can see how you could make a value-neutral
>> statement.
>>
>> On the first, you can definitely make an argument based on the documents
>> that
>> the IETF have published.  However, it is a mistake here in assuming that
>> the
>> IETF - or the revelations of global-scale surveillance - is directly
>> responsible
>> for the uptick in adoption of cryptographic protection for Internet
>> traffic.

The abstract is value neutral right now.

The increase or changes are not just about PM.  We are making
TLS 1.3 so that it cannot be intercepted (I agree with this move of
course as we should make our protocols strong and adhere to
established IETF principles)?  Or the efforts of TCPInc and
QUIC?  We do directly affect the use of encryption and the types of
encryption that are deployed.  We work with the vendor communities in
publishing deprecation drafts as well.  All of these efforts got
additional energy from the PM work and that's a good thing.  Events
trigger increases in security and it's fine to acknowledge that.  The
introduction states:

   In response to pervasive monitoring revelations and the IETF
   consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
   are underway to increase encryption of Internet traffic.  Session
   encryption helps to prevent both passive and active attacks on
   transport protocols;

We could change it to say:

   In response to pervasive monitoring revelations and the IETF
   consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
   are underway to improve and increase encryption of Internet traffic.  Session
   encryption helps to prevent both passive and active attacks on
   transport protocols;

The second sentence mentions passive and active attacks here as that
hits on the prevention of active attacks - improving session
encryption protocols helps with this.

>> This is something that the community as a whole has been working towards
>> for
>> many years; these trends predate the actions this draft focuses on.  This
>> is
>> particularly true for the hosted provider cases in Section 3, where
>> business
>> motivations for protection are far stronger than any concerns over
>> government
>> surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I
>> don't
>> have to write a statement that will be labelled as having IETF consensus.

Section 3 already makes this point very clear (full text for the intro
to that section):

3.  Encryption in Hosting SP Environments

   Hosted environments have had varied requirements in the past for
   encryption, with many businesses choosing to use these services
   primarily for data and applications that are not business or privacy
   sensitive.  A shift prior to the revelations on surveillance/passive
   monitoring began where businesses were asking for hosted environments
   to provide higher levels of security so that additional applications
   and service could be hosted externally.  Businesses understanding the
   threats of monitoring in hosted environments only increased that
   pressure to provide more secure access and session encryption to
   protect the management of hosted environments as well as for the data
   and applications.

>>
>> The immediate focus on opportunistic security is highly misleading,
>> especially
>> in the web case.  The amount of opportunistically secured web traffic is
>> miniscule by global standards.  Since Firefox is the only browser to
>> support OS
>> for the web, so adjust the following by market share:
>> <https://mzl.la/2oc46ch>.

You'll need to cite text that is leading you to this conclusion as I
don't read it as being specific to OS, rather that OS is explained so
operators understand it in the mix of encryption options.

>>
>> I understand that mail is more often opportunistically secured, and you
>> will
>> hear the virtues of OS sung from the rooftops, but all evidence suggests
>> that
>> this is just a transitory state.  Instant messaging is closer to the web
>> case,
>> with the trend toward strong protections that include authentication.  Of
>> course, I don't believe that mail or instant messaging represent any
>> significant
>> traffic volume, so you need to be very careful about the nature of the
>> claims
>> that are being made.  It has to be that the volume of mail has to be a
>> rounding
>> error when it comes to capacity planning for networks.
>>
>> On the second point, when making claims about prevalence of encryption, I
>> would
>> advise caution when citing statistics.  Here's the graph for the Mozilla
>> figures
>> that I think are being cited <https://mzl.la/2obZjrb>. Here's a different
>> graph
>> with a different number <https://mzl.la/2oc263J>.  This highlights the
>> point
>> that statistics need to be carefully cited, because bare claims are
>> difficult to
>> assess.  Methodology matters when it comes to these sorts of claims - are
>> we
>> talking proportions of packets, requests, flows, or something else?
>> Furthermore, the citations in the document are made more difficult to
>> assess by
>> being measured at very different times (where the two I cite here were
>> made at
>> roughly the same point in time).
>
> For the Mozilla statistics, Richard Barnes had reviewed the text after
> providing the statistic as he wanted to make sure it was stated
> clearly raising the same concerns you do about statistics.  Do you
> have further text suggestions to clarify this statistic?
>

>
>>
>> The statistics do support the notion that there is a significant amount of
>> encryption in use, but it would appear that the claim is that the amount
>> of
>> encryption is *increasing*.  This is not an extraordinary claim, but no
>> evidence
>> is offered in support of the claim.  It isn't a certain thing either.
>> From the
>> statistics that I have access to, there was a definite uptick in October
>> of
>> 2015, but the rate appears to be stable since then.
>>
>> It appears that the remainder of the document is intended to address the
>> third
>> of my points in some detail.  That's a good structure in theory, but see
>> above.
>>
>> I don't think that the "service provider" taxonomy works for this
>> document.
>> Based solely on the structure of the document, the only service provider
>> that
>> this document concerns itself with is the one who forwards the packets.
>> That
>> application service providers are involved as one of the endpoints is
>> relevant
>> in some cases, but not all.  For that reason, I prefer "network operator"
>> and to
>> use specific terms like "mail host" or "web server" as appropriate to the
>> context.
>>

Those are subjective comments, so we'll put those aside.

>>
>> Section 2 (top section)
>>
>> I like that the attacks on SMTP by network operators is highlighted here.

We tried to have balance and had other attacks by operators in
previous versions, but only articles that are not stable references
for them and were asked to remove them in AD review.

>>
>> There's an implicit argument here that runs counter to established IETF
>> consensus.
>>
>>    Some methods used by service providers are impacted by the use of
>> encryption
>>    where middle boxes were in use to perform functions that range from
>> load
>>    balancing techniques to monitoring for attacks or enabling "lawful
>>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>>
>> This fails to remain neutral.

The functions are impacted, so how would you suggest we word this
text?  It doesn't endorse the functions, just says they are impacted.
We are open to suggested text.  Similar to how we describe 'attacks'
by operators to break encryption or use RSA private keys.  We do have
text in both directions on this and your review is complimentary of
the ones that fit your dialog, but are also not value neutral.  Mind
you, I am constantly reviewing RFCs and making sure TLS best practices
are considered and questioning the use of deprecated crypto or not-yet
but should be deprecated crypto.

>> This implicitly makes a value-judgment
>> about
>> relative morality/acceptability/value of certain practices.

We have statements in both directions in the document as you point out
above with one of them.

>>  What is
>> particularly insidious about this particular form is that it invites
>> interpretation that is subjectively coloured.  For instance, as a non-EU
>> and
>> non-US citizen, I might consider the use of the particular lawful
>> intercept
>> techniques offensive; thus I might interpret this as a spectrum between
>> inoffensive to offensive.  An employee of the US government might view
>> this
>> somewhat differently and interpret this as a scale between low-value to
>> high-value.  I'm guessing here, but this is really just to highlight my
>> point
>> about care.
>>
>> A more serious concern is this statement:
>>
>>    The loss of access to these fields may prompt undesirable security
>> practices
>>    in order to gain access to the fields in unencrypted data flows.
>>

But this is true and we've seen operators do things like prevent
STARTTLS.  This isn't a good thing and we need to ack that this has
happened.  We need to help operators figure out how they help users in
new ways and understand that some of the functions they perform
currently (TLS 1.2) won't work in the future.

This text got re-worded during AD review, I believe.  The intent is to
say that this is not good - the practices are called out as
undesirable.  How would you suggest it be re-phrased and we can check
back with Stephen to see if he agrees.

>> I've read this argument before (see
>> https://queue.acm.org/detail.cfm?id=2508864
>> for the long form), and it might even have an element of truth to it.
>> However,
>> it's not a statement that I personally attribute any real credibility to,
>> and
>> nor do I think that it needs to be credited with any amount of
>> seriousness.  I
>> certainly disagree with the IETF making any such statement.  It says that
>> we are
>> collectively willing to bow in response to (anticipated) threats of
>> violence.

Prior to AD review, there was a reference in the text to the practices
being bad and stating that regulators and the media helped to correct
this behavior.  The problem here may be the evolution of the
text and lack of reference now since we couldn't find a stable
reference.  Do you have a wording suggestion?

>>
>> Section 2.1
>>
>> This is one of the few sections that talk about what it means to operate a
>> service as opposed to operate a network.
>>
>> Overall, this section doesn't work particularly well.  The distinction
>> between
>> integrated and standalone load balancing is an interesting division, but
>> it
>> doesn't leverage this distinction well.  What causes a standalone
>> load-balancer
>> to be necessary?  Is this something a network operator uses?  I see text
>> on NFV
>> later, but it's far removed from the original text and it seems
>> aspirational
>> rather than concrete.  On the other hand, many of the concerns in this
>> document
>> simply don't apply to an integrated load balancer.
>>
>> The amount of text on QUIC here is surprising.  Given how much of QUIC is
>> changing right now, we shouldn't publish a document that attempts to make
>> claims
>> about what QUIC is or how it is operated.  This attempts to dive into the
>> details of QUIC connection migration in a way that presumes much about the
>> outcome of issues that the QUIC working group is still struggling with.
>>
>> I would strongly recommend removing QUIC-specific language from this
>> section and
>> the document as a whole.  We have an operational document in the QUIC
>> working
>> group that would be a good venue to discuss some of these concerns.

While we read this as  more of a substantive remark, the text on
load balancers and QUIC were added per Mirja's IESG review.  We would
need to check with her about making any changes here.  They were
specific additions that were requested.

Further, it is only IETF QUIC that is in active development.
Google QUIC (referred to as GQUIC in IETF discussions) is a more
stable experiment now.

>>
>> Is this an oblique reference to (the much-loved) RFC 7974?
>>
>>    Current protocols, such as TCP, allow the development of stateless
>> integrated
>>    load balancers by availing such load balancers of additional plain text
>>    information in client-to-server packets.
>>
>> Otherwise, I don't know what it means.
>>
>> BTW, I like this parenthetical:
>>
>>    (That said, care must be exercised to make sure that the information
>> encoded
>>    by the endpoints is not sufficient to identify unique flows and
>> facilitate
>>    Persistent Surveillance attack vector.)
>>
>> I'm going to take this to the QUIC working group, because QUIC certainly
>> doesn't
>> meet that bar right now.  It fully facilitates Persistent Surveillance in
>> its
>> current form (proper noun?  I haven't really seen that term before, even
>> though
>> it draws a neat parallel with Pervasive Surveillance).
>>

OK, let us know what you hear back.  These changes were in response to
the sponsoring AD's request of that work.

>> Editorial:
>> * "pop" is a term of art that needs explanation.
>> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - the
>>   possessive form for the inanimate.
>> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".

Thanks for the nit corrections.

>>
>> Section 2.2
>>
>> I think that this sums the situation up reasonably well.  It fails the
>> value-neutral test in a few ways though.  As I understand the situation,
>> surveying operates at many levels.  For accurate planning, models of
>> endpoint
>> behaviour are used to determine things like whether loss or congestion is
>> affecting throughput.  Really good models require knowledge of what users
>> are
>> attempting to do and the applications they are using (as mentioned, things
>> like
>> browser version matter in these models).  For instance, it isn't enough to
>> understand that the user is trying to receive 720p video, you also have to
>> know
>> that a 4k stream for the same content is available.

Sure, that's why we broke the draft down by operator type.  Some
functions are shifting and the responsibilities for operators will
shift with these changes.

>>
>> The degree to which these models are privacy-invasive is not even
>> acknowledged.

Suggest text please.  The abstract and intro were meant to set the
context for the document.  Some of the functions will be eliminated -
and that's fine, it is what it is, but operators need to adapt and
deal with the change.  We should help them so we all get to a better
place with improved privacy for users and increased security.  By not
helping them, we do not get closer to solving these problems.

Try to consider the operators perspective here. They are used to knowing
what SI has been exposed by knowing video format
or browser type that has been in the clear for years.  Understanding
the practices
helps make it possible for apps/ops/security/transport to come together to
reach better solutions.

>>
>> Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect
>> that
>> subtlety to be lost on many readers though.
>>
>> Section 2.3.1
>>
>> I find this sad, even if I can recognize the truth of it:
>>
>>    A monitoring system could easily identify a specific browser,
>>    and by correlating other information, identify a specific user.
>>
>> As a browser vendor, we don't consider this to be a feature, it's a bug.
>>
>> Section 2.3.2.1
>>
>> This is a strange section under which to put caching.  Caching is a use
>> case
>> akin to compression.  I don't see it as belonging to the class of things
>> that
>> rely on DPI.  You just intermediate the cleartext HTTP in the way that RFC
>> 7230
>> recognizes.  Note that RFC 7230 explicitly does not endorse the practice
>> of
>> transparent proxying for a range of reasons, not the least of which is the
>> complete lack of transparency (yep).


This was organized per IESG review.

>>
>> Section 2.3.2.2
>>
>> Again, it's strange to see differential treatment under DPI.  I was fairly
>> sure
>> that fingerprinting was used here as well.
>>
>> Section 2.4
>>
>> This section doesn't even attempt to recognize that applications are much
>> better
>> now at scaling content to suit the device on which that content is
>> intended to
>> be consumed.  It should.

The reason for that is that there has been a useful dialog between application
designers and network providers over time, beginning with app designers
saying "what do you mean the network has errors and delay? this works
fine in my lab...".  The contributors viewed that as well understood
and far back
in time, so not necessary to mention.

If you think there should be text to this point, please suggest some.

>>
>> This section should not represent compression as an unmitigated good.  I'm
>> told
>> that significant damage can be done to video streams by "well-intentioned"
>> compression middleboxes.

Please suggest text.

>>
>> Yet again I see a call back to the implicit threat of violence in "they
>> will
>> adopt undesirable security practices".  Statements in that form have no
>> place in
>> IETF RFCs.

This was edited text per review and agreed upon (I think in the AD
review).  Suggest alternate
text and we'll go back to the other person.

>>
>> Section 2.5
>>
>> This mentions RFC 7754 then blithely ignores its primary conclusion.
>> Generally,
>> The treatment in RFC 7754 of this subject is more even-handed.
>>
>> The use of particular examples (betting, gambling, dating) shows cultural
>> bias.

subjective review again, but 7754 cites examples too.

>>
>> Jargon warning: "core network", "the mobile network" ("the"?)
>>
>> Section 2.5.2
>>
>>    This type of granular filtering could occur at the endpoint, however
>> the
>>    ability to efficiently provide this as a service without new efficient
>>    management solutions for end point solutions impacts providers.
>>
>> The initial premise here (up to the first comma) is the conclusion of RFC
>> 7754.
>> I disagree with the conclusion, and I suspect so does RFC 7754.  In
>> scenarios
>> where this matters, endpoints are routinely managed centrally.  The range
>> of
>> options for this sort of management are plentiful and diverse.

Sure, but there is an impact and it's okay to ack that and assist with
these alternate options.  If you have text to suggest, please do so.

>>
>> Section 2.5.3
>>
>> This describes a captive portal, which in the case where the service
>> provider
>> has a relationship with their customers, seems like a poor solution.  See
>> the
>> CAPPORT working group for ways in which people are actually working on a
>> solution to this problem.
>>
>> Section 2.6
>>
>> The capitalization of section headings is inconsistent here (and
>> throughout).
>>
>> Section 2.6.1
>>
>> Isn't this a duplicate of Section 2.1?
>>
>> Section 2.6.2
>>
>> I can't parse this statement:
>>
>>    Approved access to a network is a prerequisite to requests for Internet
>>    traffic - hence network access, including any authentication and
>>    authorization, is not impacted by encryption.
>>
>> And then we get into zero rating, which is a hot-button topic.  No
>> acknowledgment given to the sensitivities on the subject, or even a
>> superficial
>> exploration of the technical options that are available.

Please suggest text.  This was updated in IESG review.

>>
>> This text references a non-existent Appendix.


Fixed. It's section 7 now.

>>
>> Section 2.6.5
>>
>> This paragraph is strange.  It starts by describing what appears to be use
>> cases
>> (are those scare quotes?).  It finishes by implying that these are attacks
>> on
>> privacy (which they are).
>>
>> What is "Non-Customer Proprietary Network Information"?  I hope that this
>> isn't
>> an attempt to somehow privilege the information so that it seems less than
>> privacy-invasive.
>>
>> Section 2.7
>>
>> This is one of the areas that is most legitimately affected by increased
>> adoption of encryption.  I have no doubt that having detailed information
>> about
>> the application and its use makes the process of troubleshooting easier.
>>
>> This is the first mention in the document of network-based optimization.
>> Was
>> the section describing that cut from an earlier draft?
>>
>> The use of websockets as a primary example is an odd one.  It's just not
>> that
>> common.  For reference, we see >20% failure rates on encrypted websockets
>> and
>>>50% failures in the clear; no one in their right mind would rely on
>>> websockets.
>> If the point is that HTTP is carrying more traffic (see
>> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
>> just that
>> would be more effective.

"in their right mind" . That isn't helpful.  Operators submitted text
to explain what they are doing and how it's impacted.  How about
proposing text to help in that vein.

>>
>> Section 3
>>
>> It would help if "hosted environments" was defined before diving in.
>>
>> Section 3.1
>>
>> The paragraph on DLP is ironically amusing.  Encryption exists to prevent
>> private information leakage, but the assertion here is that encryption is
>> hampering DLP attempts.
>>
>> It's true that protection of intellectual property is an important
>> business
>> goal, but this handling suggests an architecture that I'm fairly sure is
>> counter
>> to established wisdom (see "SSL added and removed here :-)":
>>
>> https://www.washingtonpost.com/rf/image_404h/2010-2019/WashingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg).
>> Worse, this casually dismisses a model that is actually more likely to
>> work.
>> Malware encrypts too (https://arxiv.org/abs/1607.01639).

The section talks about the end points being the better place for this already.

>>
>> Section 3.1.1
>>
>> Who is the customer here?
>>
>> Why does the hosting provider need to monitor access?  They have the
>> ability to
>> limit accesses, but this is suggesting that what happens within the
>> envelope of
>> what they permit is important for them to know.  I'd be surprised if you
>> could
>> show that this is true.  Hosting providers - in my experience - value
>> their
>> ongoing business and would not jeapardize it by snooping on their
>> customers.
>> It's different if the customer opts in to a security service, but that
>> demonstrates a cooperative situation, where the rest of this document is
>> largely
>> concerned with adversarial uses of encryption.

This is describing the cooperative scenario.  The service is hosted,
so maybe the definition of hosted would have helped you.

>>
>> Section 3.1.2
>>
>> This is another example where the organization of the document could
>> be improved.
>>
>> Again with the "SSL added and removed here :-)" recommendation.  PCI don't
>> permit that for good reason.

I don't read the following text in this section as a recommendation or
endorsement.  Is there a tweak you think that should be made as I'm
not seeing the problem your describing. This is just describing what
they do and stating that it will be impacted and then the truth that
the functions may no longer be possible - not stating that it is good
or bad, just the fact that it won't be possible.

   The use of tools that
   perform SSL/TLS decryption are impacted by the increased use of
   encryption that prevents interception.  Alternate methods to acheive
   the goals of these functions may be necessary and in some cases, the
   functions may no longer persist in a pervasively encrypted Internet.

>>
>> Section 3.2.1
>>
>> I don't believe that monitoring of these types of application require
>> cleartext
>> access.  There are two parties involved: the provider of the application
>> and the
>> user of it.  The provider has most of the power here and can theoretically
>> design the system to allow whatever level of access they require.  To the
>> extent
>> that the user needs protection from the application provider, that is a
>> matter
>> of negotiation between them.
>>
>> I don't see how the adversarial three-party situation presented in the
>> rest of
>> the document applies in this situation.

Sure, there is a shift in how many functions will be performed
happening and this is documenting that shift.  Much moves to the
application.  We are helping to document the changes.

>>
>> Section 3.2.2
>>
>> No real mention of the effect of encryption here, or is this just saying
>> that
>> there is no issue here?
>>
>> I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of the
>> IETF
>> saying things like "PGP may be a front runner" though.
>>

This was added per EKR in IESG review.

>> Section 3.3
>>
>> There's certainly a lot of detail here, but I had a really hard time
>> extracting
>> value from this section.  I can't see how data storage is fundamentally
>> different to the general case of an application provider.

They figured out how to increase encryption and manage their hosted
environments.  There were adjustments made and they've been
successful.

>>
>> Section 4.1.1
>>
>> I appreciate the recognition that endpoint-based techniques work.  The
>> implication that this isn't the obvious solution, much less so.

This isn't a technical comment, but we'll revisit the text to see if a
wording change can help.

>>
>> Section 4.1.2
>>
>> I'm confused about the purpose of this section.  This seems to be talking
>> about
>> the sort of network-based methodologies an application provider might
>> employ to
>> ensure that their application is working as intended.  Why would the
>> application
>> provider not have access to detailed logging and usage metrics?

The problem cited to us is that logging is sorely lacking.  This needs
to be pointed out and fixed as it is too much for the operator to deal
with given the large number of applications running in their
environments.

>>
>> As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is
>> cited no
>> fewer than three times in the same paragraph.  It makes some fairly bold
>> claims
>> about its effect on privacy that I don't believe will hold up to analysis.
>>
>> Section 4.1.3.1
>>
>> This section correctly identifies the issue as one of shortcomings in
>> logging,
>> not increased use of encryption.

Right, a key point in this document - other methods will have to be
used and an obvious one is logging.  However, logging needs to improve
for that to be possible.

>>
>> I would have stopped there, but the section persists and ultimately
>> references
>> RFC 7974, which is widely recognized as a monstrously bad idea (the IESG
>> note is
>> fairly clear on this point).

Thanks for catching that.  We can drop this text.

>>
>> Section 4.1.3.2
>>
>> "HTTP/2", not "HTTP2".

Fixed.

>>
>> I don't see how this section belongs in this document.  The 1:1
>> correlation
>> between actions and flows in HTTP was a mistake of the 1980s that we've
>> spent a
>> lot of time on correcting (sometimes unsuccessfully, see pipelining).
>>
>> Section 4.1.3.3
>>
>> It's not a "service call" it's just a request.
>>
>> Section 4.2
>>
>> If the inclusion of a reference to RFC 7457 is to support a claim that TLS
>> is
>> attacked, that's sailing far too close to an endorsement of attacks than I
>> am
>> comfortable with.  However, I don't believe that any of the listed attacks
>> remain viable in modern applications.  What is most often the case is that
>> a
>> trust anchor is installed on enterprise users' machines and new
>> certificates are
>> minted as needed.  In other words, the host that is accessing the HTTPS
>> site is
>> owned by the enterprise and modified so that it can comply with its
>> policies.
>>
>> When you recommend attack like this (to be clear, I would oppose
>> publication of
>> text that does this), you need to acknowledge the downsides.  For example,
>> MitM
>> devices routinely break connections, they hide the true security status of
>> communications from endpoints and users, they frequently implement weaker
>> versions of protocols, they often don't include the same degree of rigor
>> in
>> things like certificate validation, and probably many more things that I
>> can't
>> casually list off the cuff.

Please suggest text.

>>
>> The discussion of caching here warrants a new section.
>>
>> Section 5.1
>>
>> s/effect/affect
>>

Thanks, we'll fix this.

>> No complaint here, just an advertisement for technical solutions that
>> aren't
>> affected by increases in encryption.  Good, though I'm not sure if the
>> section
>> meets the document's criteria for inclusion.
>>
>> Section 5.3
>>
>> No cititation for APWG.  Not an IETF working group from what I can see.

We'll add that, thanks.

>>
>> There's a presumption here that administrators need to perform these
>> tasks.  Why
>> can't endpoints do this?  It would certainly be a whole lot less invasive
>> that
>> way.  Take a look at how browsers implement checks for "bad" sites (which
>> include phishing sites).  These methods have some fairly significant
>> privacy
>> safeguards without compromising on performance.

A lot will move to the endpoints, but things like logging need to
improve and we need to get application developers to do a better job
so that there is no reason for someone to want to try to intercept
traffic for troubleshooting.  Operators see this as an insurmountable
problem.  We need to help.

>>
>> Section 5.5
>>
>> See my comment about about endpoint-based methods.

Already agree with this point.

>>
>> Section 5.6
>>
>> I believe that the spoofed source address problem is not relevant to this
>> document.  It's a fairly well understood problem.  That said, if we could
>> wave a
>> magic wand and get BCP 38 deployed, that might be nice.
>>
>> Section 6.1
>>
>> As this says, it's fairly well understood that - for HTTP - SNI is used.
>> The
>> point that it is optional is interesting, but doesn't deserve the amount
>> of
>> attention this section devotes to it.  The clients that don't include SNI
>> are in
>> a diminishing minority.

Text was aded per EKR's review.

>>
>> That said, this doesn't pay any attention to another feature in HTTP/2:
>> connection coalescing.

Please suggest text if this should be included.

>>
>> Section 6.2
>>
>> ALPN will be encrypted in TLS 1.3.

Noted.  Thanks.

>>
>> Section 6.3
>>
>> This reads as a invitation to perform traffic analysis (a statement that I
>> oppose).  Note that we have added padding to most recent protocols (HTTP/2
>> and
>> TLS 1.3 in particular) to give endpoints the ability to resist this sort
>> of
>> attack.
>>
>> Note that block ciphers can add ~240 octets of discretionary padding per
>> record.
>> That can be pretty effective if you are careful.

I believe this text was added through the IESG review.  I don't see
the problem with the text you are citing, so could you suggest
alternate text?

>>
>> Section 7
>>
>> This section is duplicative of much of the rest of the document.  I
>> realize that
>> editing is hard, but see my earlier comments about structure.

This text was the appendix, but moved to section 7 per IESG review and
discuss.  It was the mobile operator view.

>>
>> It's obvious that this section is about QUIC.  That shows in several ways.
>> It's
>> nice how it doesn't say so out loud, but it leaks through in several
>> confusing
>> ways.  See below.
>>
>> Section 7.1
>>
>> This section is purportedly about encrypted ACKs, which won't happen until
>> we
>> get to QUIC.  But the points regarding proxies (b, c, d) are not prevented
>> by
>> encrypted ACKs, they are prevented by encryption more generally.  Point e
>> is
>> defeated by integrity protection of ACKs, not confidentiality protection.
>>
>> I hope that the IETF never publishes draft-dolson-plus-middlebox-benefits;
>> it
>> makes claims about the benefits of specific solutions for different use
>> cases
>> with the goal of justifying those solutions.  At the same time, it fails
>> to
>> recognize the existence of alternative, often superior, solutions for
>> those use
>> cases.  In other words, it has many of the same issues as this document.

I think this is an early document and expect it will get some
revision.  This was added into our document per Mirja's IESG review.
They are documenting middle boxes that use 5-tuples.  That point isn't
clear until the summary.  I provided some light feedback, but could
provide more to help them improve the document.  I think it's fine to
document these things and then figure out how we can do better with
IETF agreed upon protocol design intentions (end-to-end and assisting
to improve user's privacy as well as the security of sessions.

>>
>> FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I
>> don't
>> know how to close the gap between the privacy assurances I wish it had and
>> the
>> privacy weaknesses it has.
>>
>> The phrase "trusted proxies" is a dangerously misleading phrase.  The
>> concept of
>> trust is - particularly in this context - frequently abused.

That's why the quotes were there, but this has been re-phrased in 10 -
see the SecDir review.

>>
>> Sections 7.2 and 7.3
>>
>> I'd be interested in learning about the justification for these features
>> (again,
>> go back to my comment about to whom the benefit accrues, and I'd advise
>> caution
>> not to make the trickle-down economics mistake of using second-order
>> effects).
>> Personally, I'm not that sad that they are going to be negatively
>> affected.
>>
>> Section 7.2, Point d seems to be saying something about a multiplexed
>> protocol,
>> not one that has an encrypted transport header (see above regarding QUIC).
>>
>> All these points equally apply to HTTPS, which suggest that encrypted
>> transport
>> headers is not the issue (unless by transport we mean HTTP).

Again, section 7 was changed in IESG review and added into the body of
the document per Mirja's discuss since the mobile operator is
important to include.

>>
>> Section 7.4
>>
>> s/GPSR/GPRS/ ?

Fixed.  I thought this was fixed in 9, hence me thinking you read the
wrong version.

>>
>> Section 8
>>
>> I generally agree with the first statement here, but after having read the
>> document, I could take away some very different views on what the
>> "problems at
>> hand" actually are.  I suspect that different people will have very
>> different
>> takeaways.
>>
>> The conclusion section of a document is not the right place to start
>> introducing
>> new information, particularly information relevant to RFC 2804.

Should we move this to the introduction perhaps to help with context setting?

>>
>> Not sure where this is going:
>>
>>    Terrorists and criminals have been using encryption for many years.
>>
>> Because it's disconnected from the remainder of the paragraph.  If you are
>> going
>> to invoke the T-word, you had better have a strong argument to make.  On
>> the
>> final sentence of that paragraph, the subject ("This") is unclear.
>>

Sure, the point was that their use of encryption is not a
justification argue any of the improvements to crypto for the general
population.  Incident handlers know full well that encryption has been
in place for a long time by these users.  Essentially, it's not an argument that
hold muster.

>
>
>
> --
>
> Best regards,
> Kathleen
>
>



-- 

Best regards,
Kathleen & Al


From nobody Tue Apr 11 00:34:14 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9E1128954; Tue, 11 Apr 2017 00:33:55 -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, RCVD_IN_DNSWL_MED=-2.3, 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 Em0Bphy2FgcI; Tue, 11 Apr 2017 00:33:52 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 7D55F1272E1; Tue, 11 Apr 2017 00:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3B7XiVi016689; Tue, 11 Apr 2017 09:33:44 +0200 (CEST)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w2Jh80fd0zDGv9; Tue, 11 Apr 2017 09:33:44 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149188258769.15738.17473942496982365590@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 09:33:43 +0200
Cc: art@ietf.org, ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 513588823.52644-849855f363bc0cd0868f57315eaebce9
Content-Transfer-Encoding: quoted-printable
Message-Id: <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fcPe61DabuNbhLtOPfQgRlhCjJo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 07:33:55 -0000

Hi Mark,

thank you a lot for another thoughtful review.

I don=E2=80=99t have an opinion yet on what we should do here, so I=E2=80=99=
ll supply some more background first.

The present spec is first and foremost intended to round-trip with RFC =
6690, which is indeed stuck a bit on HTTP Link header field syntax.  =
However, the way this is used in practice is not meant to inherit the =
complexities of HTTP header field coding.  E.g., for CoRE Resource =
Directory and its DNS-SD compatibility, we want to represent a DNS-SD =
instance identifier (which is UTF-8) as a link attribute.  This is not a =
problem in JSON or CBOR, but also not in the way RFC 6690 is being used, =
i.e. as a UTF-8 based format.

I haven=E2=80=99t checked yet what 5988bis brings to the table and how =
to track this in 6690 or possibly a 6690bis.  There is no point in Big =
Web and Thing Web diverging here, so we should follow the lead.  But =
maybe that would touch both 6690 and the present document once 5988bis =
is done.

More importantly, we haven=E2=80=99t really put a lot of thinking into =
IRI support.  The CoAP data type =E2=80=9Cstring=E2=80=9D which is used =
for URI components such as Uri-Path is UTF-8, so we could embrace them =
by extending the rules in section 6 of RFC 7252 to cover IRIs.  I=E2=80=99=
m sure that, in practice, CoAP implementations already do this =E2=80=94 =
it is not distinguishable in the CoAP packet whether the (decomposed) =
CoAP Uri components have been derived from URIs or IRIs.  But the =
metadata formats (6690 and its JSON/CBOR representations; various other =
JSON and CBOR based formats, e.g. from OCF) are still based on RFC 3986 =
URIs, except where they also use the CoAP decomposed form (e.g., CORAL).

While this is outside the scope of the CoRE WG, I personally would like =
to explore how link-format+cbor/+json could be useful for the Big Web.  =
If embracing IRIs there is all we need to make this happen, maybe that =
can be added with a warning that IRIs have to be converted back to URIs =
for 6690 link-format.

Gr=C3=BC=C3=9Fe, Carsten


> On Apr 11, 2017, at 05:49, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Reviewer: Mark Nottingham
> Review result: Ready with Issues
>=20
> This specification is a relatively straightforward mapping of the
> format described in RFC6690 (itself a serialisation of RFC5988bis
> links) into JSON and CBOR. I don't have deep knowledge of CBOR, but
> given the editorship of the document, I trust it's seen adequate
> review in that regard.
>=20
> The only potential issue is how this is achieved. Rather than defining
> two new serialisations of RFC5988bis links (into JSON and CBOR), it
> describes how to re-serialise RFC6690 documents into JSON and CBOR.
> This means that any constraints upon RFC6690 documents are also
> mirrored into these formats; e.g., the target IRI is constrained to be
> a URI in 6690, and therefore can also only be a URI in JSON and CBOR,
> despite these formats' ability to easily convey non-ASCII content.
>=20
> In other words, the specification currently defines these link formats
> in terms of the Link header (as defined in section 5 of RFC5988) --
> along with all of the foibles of HTTP header syntax -- rather than
> their abstract model (defined in Section 3).
>=20
> Whether or not this is a problem depends on what's desired; if 6690 is
> seen as effectively a profile of 5988, then it makes sense to express
> it in those terms. If the full range of links capable of being
> expressed in 5988 is desired, creating new serialisations of 5988
> links (without a hop through 6690) is preferable.
>=20
> If the current approach is kept, it'd be nice to clarify this
> situation a bit in the Introduction.
>=20
>=20
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>=20


From nobody Tue Apr 11 01:15:26 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880DA1292FD for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 nn8vlgB8FSzp for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:15:23 -0700 (PDT)
Received: from relais-inet.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 08935129408 for <ietf@ietf.org>; Tue, 11 Apr 2017 01:15:23 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 24428C05E4; Tue, 11 Apr 2017 10:15:21 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.66]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id F0420C0079; Tue, 11 Apr 2017 10:15:19 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf%19]) with mapi id 14.03.0319.002; Tue, 11 Apr 2017 10:15:19 +0200
From: <mohamed.boucadair@orange.com>
To: Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AdKym8EY4i6VvDHuQjir6aepfU3ztw==
Date: Tue, 11 Apr 2017 08:15:19 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QIBhtT1WPXQQZYPyhke-Uxlq0AU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 08:15:24 -0000

SGkgTWFydGluLCBhbGwsIA0KDQpJIGhhdmUgYSBjb21tZW50IGFib3V0IHRoaXMgcGFydGljdWxh
ciBwYXJ0IG9mIHlvdXIgcmV2aWV3Lg0KDQpQbGVhc2Ugc2VlIGlubGluZS4gDQoNCkNoZWVycywN
Ck1lZA0KDQo+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiBEZcKgOiBpZXRmIFttYWls
dG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBEZSBsYSBwYXJ0IGRlIE1hcnRpbiBUaG9tc29uDQo+
IEVudm95w6nCoDogdmVuZHJlZGkgNyBhdnJpbCAyMDE3IDA1OjI1DQo+IMOAwqA6IGlldGZAaWV0
Zi5vcmcNCj4gT2JqZXTCoDogUmV2aWV3IG9mIGRyYWZ0LW1tLXdnLWVmZmVjdC1lbmNyeXB0LTA5
DQo+IA0KPiANCj4gSSBob3BlIHRoYXQgdGhlIElFVEYgbmV2ZXIgcHVibGlzaGVzIGRyYWZ0LWRv
bHNvbi1wbHVzLW1pZGRsZWJveC1iZW5lZml0czsNCj4gaXQNCj4gbWFrZXMgY2xhaW1zIGFib3V0
IHRoZSBiZW5lZml0cyBvZiBzcGVjaWZpYyBzb2x1dGlvbnMgZm9yIGRpZmZlcmVudCB1c2UNCj4g
Y2FzZXMNCj4gd2l0aCB0aGUgZ29hbCBvZiBqdXN0aWZ5aW5nIHRob3NlIHNvbHV0aW9ucy4NCg0K
W01lZF0gSSdtIGFmcmFpZCB0aGlzIGlzIHNwZWN1bGF0aW5nIGFib3V0IHRoZSBpbnRlbnQgb2Yg
ZHJhZnQtZG9sc29uLiBBc3N1cmVkIHRoaXMgaXMgbm90IHRoZSBwdXJwb3NlIG9mIHRoYXQgZG9j
dW1lbnQuIFRoZSBtb3RpdmF0aW9uIGlzIHRvIGRvY3VtZW50IGN1cnJlbnQgcHJhY3RpY2VzIHdp
dGhvdXQgaW5jbHVkaW5nIGFueSByZWNvbW1lbmRhdGlvbiBvciBjbGFpbWluZyB0aGVzZSBzb2x1
dGlvbnMgYXJlIHN1cGVyaW9yIHRvIG90aGVycy4gVGhlcmUgaXMgYSBuZWVkIHRvIHVuZGVyc3Rh
bmQgdGhlIG1vdGl2YXRpb25zIHdoeSBvcGVyYXRvcnMgbmVlZCB0byBlbmFibGUgc29tZSBvZiB0
aGVzZSBmZWF0dXJlcy4gRm9yIGV4YW1wbGUsIG1lYW5zIHRvIGhlbHAgb24tcGF0aCBkZXZpY2Vz
IGV4ZWN1dGluZyB0aGVpciBzZXJ2aWNlIGFyZSBuZWVkZWQgZm9yIG5ldHdvcmsgb3BlcmF0aW9u
IHB1cnBvc2VzIChlLmcuLCBwcm90ZWN0IGEgbmV0d29yaywgZGV0ZWN0IGNvdmVyIGNoYW5uZWxz
LCBoZWxwIHNlbGVjdGluZyB0aGUgcG9ydGlvbiBvZiB0cmFmZmljIHRvIGJlIGZpbHRlcmVkIHJh
dGhlciB0aGFuIGRpcmVjdGluZyBhbGwgdGhlIHRyYWZmaWMgdG8gYSBibGFjayBob2xlIGR1cmlu
ZyBhdHRhY2tzLCBldGMuKS4gDQoNCk9mIGNvdXJzZSwgYXV0aG9ycyBvZiBkcmFmdC1kb2xzb24g
dW5kZXJzdGFuZCB0aGVyZSBhcmUgZGVwbG95bWVudCBjYXNlcyB3aGVyZSBtaWRkbGVib3hlcyBt
YXkgbm90IGJlIHJlcXVpcmVkIGF0IGFsbC4gVGhlaXIgcHJlc2VuY2UgbWF5IGV2ZW4gYmUgYSBz
b3VyY2Ugb2YgdHJvdWJsZSBpZiBiYWRseSB0d2Vha2VkLCBmb3IgZXhhbXBsZS4gVGhhdOKAmXMg
YW4gZXZpZGVuY2UuIA0KDQpBdXRob3JzIG9mIGRyYWZ0LWRvbHNvbiBkb2VzIG5vdCBjbGFpbSBt
aWRkbGVib3hlcyBpcyB0aGUgb25seSB3YXkgdG8gbWVldCB0aGUgdGVjaG5pY2FsIG9iamVjdGl2
ZXMgbGlzdGVkIGluIHRoZSBkcmFmdCwgYnV0IHRoZXkgYXJlIGRvY3VtZW50aW5nIHNhbXBsZSBm
ZWF0dXJlcyB0aGF0IGFyZSBuZWVkZWQgdG8gYmUgc3VwcG9ydGVkIGF0IHRoZSBuZXR3b3JrIHNp
ZGUuIA0KDQpTb2x1dGlvbiBkZXNpZ25lcnMgY2FuIHJlZmVyIHRvIGRyYWZ0LWRvbHNvbiB0byBl
eHBsaWNpdCBob3cgdGhleSBzb2x2ZSBhIHBhcnRpY3VsYXIgcHJvYmxlbSB3aXRob3V0IHJlcXVp
cmluZyBzZXJ2aWNlcyBmcm9tIGFuIG9uLXBhdGggZGV2aWNlLg0KDQoNCiAgQXQgdGhlIHNhbWUg
dGltZSwgaXQgZmFpbHMNCj4gdG8NCj4gcmVjb2duaXplIHRoZSBleGlzdGVuY2Ugb2YgYWx0ZXJu
YXRpdmUsDQoNCltNZWRdIEl0IGRvZXMgbm90IGRvIHNvIGJlY2F1c2UgaXQgaXMgb3V0IG9mIHNj
b3BlLiBCZWZvcmUgZGlzY3Vzc2luZyBhbHRlcm5hdGl2ZXMsIHdlIG5lZWQgZmlyc3QgdG8gdW5k
ZXJzdGFuZCB0aGUgZ29hbHMgdGhhdCBtb3RpdmF0ZWQgY3VycmVudCBwcmFjdGljZXMuIEZ1dHVy
ZSBkb2N1bWVudHMgY2FuIHJlZmVyIHRvIGRyYWZ0LWRvbHNvbiB0byBkZXNjcmliZSBhbHRlcm5h
dGl2ZXMuICANCg0KIG9mdGVuIHN1cGVyaW9yLA0KDQpbTWVkXSBJIGRvbid0IHNlZSBob3cgeW91
IGVuZGVkIHRvIHN1Y2ggY29uY2x1c2lvbiBhcyBhIGdlbmVyYWwgc3RhdGVtZW50IHdpdGhvdXQg
ZXZlbiBsb29raW5nIGF0IHRoZSBuZWVkcyEgSXQgbWF5IGJlIHRlbXB0aW5nIHRvIGFzaywgZm9y
IGV4YW1wbGUsIHdoYXQgYXJlIHRoZXNlIHN1cGVyaW9yIGFsdGVybmF0aXZlcyB0byBoZWxwIG9w
ZXJhdG9ycyBkZXRlY3QgYW5kIG1pdGlnYXRlIEREb1MsIGJ1dCBhcyBtZW50aW9uZWQgYWJvdmUs
IGl0IGlzIGVhcmx5IGF0IHRoaXMgc3RhZ2UgdG8gZGlzY3VzcyB0aGVzZSBhbHRlcm5hdGUgc29s
dXRpb25zLiAgIA0KDQogc29sdXRpb25zIGZvcg0KPiB0aG9zZSB1c2UNCj4gY2FzZXMuICBJbiBv
dGhlciB3b3JkcywgaXQgaGFzIG1hbnkgb2YgdGhlIHNhbWUgaXNzdWVzIGFzIHRoaXMgZG9jdW1l
bnQuDQo+IA0K


From nobody Tue Apr 11 01:51:26 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492CC1200F1 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=cs.tcd.ie
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 u6KvCqGNE021 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 01:51:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED15D120727 for <ietf@ietf.org>; Tue, 11 Apr 2017 01:51:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E6568BE4D; Tue, 11 Apr 2017 09:51:16 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R6flA7Jv3qQS; Tue, 11 Apr 2017 09:51:15 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3BCB5BE47; Tue, 11 Apr 2017 09:51:15 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491900675; bh=UfRYkuClog0+CheGPTaMNxHqz+9OPVU0DVqxIjYb6Jg=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=AjMVakXk/QWDyzsGyfpBq5O6uC3LxFS3i7NlzCjLN/Srye8JZDdKDpaXqVFwCr5JK ZuG2bOOl97GQx/WujUQPT18/lk6vEUmPPgvrXiSEg4ur6S3/LLYNZuBz3BN6TnNgOb lGdxMrwNZSpbyGjxGFwbKjI+QNvBA6dVBDnLiCnc=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
Date: Tue, 11 Apr 2017 09:51:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QU5DrroLB7f46CBMdIHothGu8PP5JWLVs"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7p4J082moEf7uKoKKU2KMkHx7Rs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 08:51:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--QU5DrroLB7f46CBMdIHothGu8PP5JWLVs
Content-Type: multipart/mixed; boundary="kNOLmIL2CjkuntLebWmT3RiafJR5LUHqr";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>,
 "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org"
 <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Message-ID: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>

--kNOLmIL2CjkuntLebWmT3RiafJR5LUHqr
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Med,

On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>> I hope that the IETF never publishes
>> draft-dolson-plus-middlebox-benefits; it makes claims about the
>> benefits of specific solutions for different use cases with the
>> goal of justifying those solutions.

> [Med] I'm afraid this is speculating about the intent of
> draft-dolson. Assured this is not the purpose of that document. The
> motivation is to document current practices without including any
> recommendation or claiming these solutions are superior to others.

Just to note that I completely agree with Martin's interpretation
of the thrust of this draft and I totally fail to see how your
argument above can be justified given that draft title, abstract
and even filename (and also the content;-). When the abstract
says "This document summarizes benefits" then I cannot interpret
that as other than being intended to justify the uses described.

A fairly thorough re-write to aim to describe the pros and cons
would be a different and more useful document. Similarly a draft
that strives to neutrally describe existing reality could maybe
be useful (*) but one that only describes middlebox friends with
"benefits" is not IMO beneficial ;-)

Cheers,
S.

(*) That is the argument for draft-mm-effect-encrypt, for which I
do support publication (apparently in disagreement with Martin in
that case:-)





--kNOLmIL2CjkuntLebWmT3RiafJR5LUHqr--

--QU5DrroLB7f46CBMdIHothGu8PP5JWLVs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7JkCAAoJEC88hzaAX42iF2QH/2eHiHbW93kiBioZFugYf9Ek
rBLuCMtAyqWmgEAV492P3oL6gxWPK2YGyOmEcGYF1GXX6G7aMYdDynFaOc5G1Bj5
4TVIeGvVcFjP4JQbfyWCzTKd8FtsaKXQGzbRD+7wq1k8ZtJe9MvPu2ahjUH2Xj/G
+vr/TEqIpP4aYrEMP3cbtaydp/3HYYSFbz7zE0VdE2V++Jeqw6y0VtNpH8Nhhqok
m1ahVE87bFjiCM/k46XdnpP32fGKoFtz7B2PWXGxTXPAcxEJkPWeO/M4j9MjeFZ+
+CS9w0VowUjkIj50kp6JDdbbsqUm6ZZWD8bQRtxndhFLcTyJjSmKvzX4Je6LWpQ=
=O6JG
-----END PGP SIGNATURE-----

--QU5DrroLB7f46CBMdIHothGu8PP5JWLVs--


From nobody Tue Apr 11 02:55:34 2017
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DA4127071; Tue, 11 Apr 2017 02:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=metaswitch.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 7BvvnbrPFPXB; Tue, 11 Apr 2017 02:55:21 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0094.outbound.protection.outlook.com [104.47.38.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C36129329; Tue, 11 Apr 2017 02:55:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=b9HETZbL8j2CzLb+MsfxZDwMCVL8Zj5oXcgY7WjUSBg=; b=mLpJtzmhimVYec0Yt8UKwjjGIb6RM6v4uTyACslRrFs3uO+5NuqWcwwzGHv5Dt5vLJsz26SIQyTpufPyIFhwyAtF+MSkfpXIfi50v6IVcYg1tAiZWHX1kUTXyIsXMsBiK6dBBs0SSDmKoTAAB/5vlgHM02V0s6XfnnPmRJbHQHA=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 09:55:18 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 09:55:18 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Joel Halpern <jmh@joelhalpern.com>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM898qSTLMFhq0+xLX5nlZUWFKG/9CxQ
Date: Tue, 11 Apr 2017 09:55:17 +0000
Message-ID: <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.com; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [86.132.76.121]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1910; 7:0KiugvFB4MZ2dcC02gs2lCwTptPiz2jonC9SPkwJtsETaNkPehF/npjBNqjXJWQ6PXEp5DoVXQ8SWLQBRq0f3Y71QrqjFChqFMKCSwgheCp08lerPqlhKsnd2f2YUkXKBq+EfNQsTIcfqRIPM8AVZab3wyIxA0s8beJxU0lpY6cVcnsqPeJEepFcIKy9HD7AE9BKk6E+P+tWqXxuxgLeCyvfLTN4L0OL4UBPqwluLzWHSlhgkXTZ7My5IuE4OMOxBWy8x79LzSxrn844ZFzd/jZCMbSl1PqwTqXoEJF9t53wJJWQoFkfRpPpY8IghlK48bjUawtjcnnOMq6SuOhOGw==
x-ms-office365-filtering-correlation-id: aa5b51c7-e4b9-48b7-7e47-08d480c0dc1e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR0201MB1910; 
x-microsoft-antispam-prvs: <BY2PR0201MB1910CD25773FDB0DA09950F384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:BY2PR0201MB1910; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1910; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39450400003)(39840400002)(66654002)(51914003)(13464003)(37854004)(86362001)(81166006)(8676002)(3280700002)(3660700001)(110136004)(33656002)(8936002)(189998001)(25786009)(5660300001)(4326008)(2906002)(53546009)(6436002)(230783001)(102836003)(2900100001)(6116002)(122556002)(38730400002)(3846002)(229853002)(2950100002)(54356999)(76176999)(6916009)(305945005)(50986999)(66066001)(7696004)(6506006)(77096006)(54906002)(99286003)(55016002)(53936002)(74316002)(6246003)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1910; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 09:55:17.7351 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1910
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M-FyReRLO4EjPx3-_3wAMMYbt18>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 09:55:24 -0000

SGkgSm9lbA0KDQpNYW55IHRoYW5rcyBmb3IgdGhlc2UgY29tbWVudHMuICBJJ20gcGlja2luZyB1
cCB0aGlzIHRocmVhZCBhbmQgcmVwbHlpbmcgYXMgUENFIHdvcmtpbmcgZ3JvdXAgY2hhaXIsIGFz
IHRoZSBhdXRob3JzIGFyZSB1bmF2YWlsYWJsZS4gIEkgYXBvbG9naXNlIGZvciB0aGUgZGVsYXku
DQoNClBsZWFzZSBzZWUgbXkgcHJvcG9zZWQgcmVzb2x1dGlvbnMgaW5saW5lIGJlbG93LCBtYXJr
ZWQgd2l0aCAiSm9uPiINCg0KQmVzdCByZWdhcmRzDQpKb24NCg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogSm9lbCBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNv
bV0gDQpTZW50OiAxNyBGZWJydWFyeSAyMDE3IDAzOjM4DQpUbzogZ2VuLWFydEBpZXRmLm9yZw0K
Q2M6IGRyYWZ0LWlldGYtcGNlLXN0YXRlZnVsLXBjZS5hbGxAaWV0Zi5vcmc7IHBjZUBpZXRmLm9y
ZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmV2aWV3IG9mIGRyYWZ0LWlldGYtcGNlLXN0YXRl
ZnVsLXBjZS0xOA0KDQpSZXZpZXdlcjogSm9lbCBIYWxwZXJuDQpSZXZpZXcgcmVzdWx0OiBSZWFk
eSB3aXRoIElzc3Vlcw0KDQo8c25pcD4NCg0KPT09PQ0KDQpNaW5vciBpc3N1ZXM6DQogICBBdCB0
aGUgZW5kIG9mIHNlY3Rpb24gNS40LCB0aGUgdGV4dCB0YWxrcyBhYm91dCBhIFBDRSBhY2NlcHRp
bmcgc3RhdHVzIHVwZGF0ZXMgZXZlbiBpZiB0aGUgIHN0YXRlZnVsIGNhcGFiaWxpdHkgaGFzIG5v
dCBiZWVuIG5lZ290aWF0ZWQuICBXaGljaCBpcyBmaW5lLiAgQnV0IGFzIHdyaXR0ZW4sIHRoZSB0
ZXh0IHNlZW1zIHRvIHNheSB0aGF0IGRvaW5nIHNvIG1lYW5zIHRoYXQgdGhlIFBDRSB3aWxsIGJl
IGFibGUgdG8gImJ1aWxkIGFuZCBtYWludGFpbiBhbiB1cCB0byBkYXRlIHZpZXcgb2YgdGhlIHN0
YXRlIG9mIHRoZSBQQ0MncyBMU1BzIi4gIEhvd2V2ZXIsIGlmIHRoZSBjYXBhYmlsaXR5IGhhcyBu
b3QgYmVlbiBuZWdvdGlhdGVkLCBJIGRvIG5vdCBzZWUgaG93IHRoZSBQQ0UgY2FuIGNvdW50IG9u
IGdldHRpbmcgZnVsbCBhbmQgdGltZWx5IHN0YXRlIHJlcG9ydHMuICBUcnlpbmcgdG8gaW5mZXIg
d2h5IGEgUENDIGlzIHNlbmRpbmcgc3VjaCBhIHJlcG9ydCBpbiB0aGUgYWJzZW5jZSBvZiB0aGUg
YWdyZWVtZW50IHNlZW1zIHByb2JsZW1hdGljLg0KDQpKb24+IEkgYWdyZWUuICBJIHByb3Bvc2Ug
dGhhdCB3ZSBkZWxldGUgdGhpcyBzZW50ZW5jZToNCiIgTm90ZSB0aGF0IGV2ZW4gaWYgdGhlIHVw
ZGF0ZQ0KICAgY2FwYWJpbGl0eSBoYXMgbm90IGJlZW4gYWR2ZXJ0aXNlZCwgYSBQQ0UgY2FuIHN0
aWxsIGFjY2VwdCBMU1AgU3RhdHVzDQogICBSZXBvcnRzIGZyb20gYSBQQ0MgYW5kIGJ1aWxkIGFu
ZCBtYWludGFpbiBhbiB1cCB0byBkYXRlIHZpZXcgb2YgdGhlDQogICBzdGF0ZSBvZiB0aGUgUEND
J3MgTFNQcy4gIg0KDQo9PT09DQoNCiAgICBUaGlzIGNvbW1lbnQgbWF5IGJlIGEgbWlzdW5kZXJz
dGFuZGluZyBvciBtaXMtZXhwZWN0YXRpb24gb24gbXkgcGFydC4gIEkgd291bGQgaGF2ZSBleHBl
Y3RlZCBvbmUgb2YgdGhlIHdheXMgbyB1c2luZyBhbiBhY3RpdmUgUENFIGlzIHRvIGhhdmUgdGhl
IFBDRSBkZWNpZGUgKHVuZGVyIHN1aXRhYmxlIGNpcmN1bXN0YW5jZXMpIHRoYXQgYW4gTFNQIGlz
IG5lZWRlZCBiZXR3ZWVuIHR3byBQQ0NzLiAgQXMgZmFyIGFzIEkgY2FuIHRlbGwsIHRoZSB0ZXh0
IGluIHNlY3Rpb24NCjUuOC4yIGFuZCA1LjguMyBwcm9oaWJpdHMgdGhhdC4gIEEgUENFIGlzIG9u
bHkgYWxsb3dlZCB0byBzZW5kIGFuIExTUCBVcGRhdGUgUmVxdWVzdCAoaW4gYSBQQ1VwZCBtZXNz
YWdlKSBmb3IgYW4gTFNQIHRoYXQgaGFzIGJlZW4gZGVsZWdhdGVkIHRvIGl0LiAgQXQgdGhhdCBw
b2ludCBJIHRob3VnaHQgdGhhdCBhIFBDQyBjb3VsZCBkZWxlZ2F0ZSBhIGJsb2NrIG9mIHVuc2V0
dXAgTFNQcyB0byB0aGUgUENFLiAgQnV0IHRoZW4gbG9va2luZyBhdCA1LjguMiwgdGhlIHRleHQg
c3RhdGVzIHRoYXQgZm9yIGVhY2ggZGVsZWdhdGlvbiwgdGhlIFBDQyBtdXN0IHJlcXVlc3QgYW4g
aW5pdGlhbCBwYXRoLiAgVGhhdCBzZWVtcyB0byBwcm9oaWJpdCBkZWxlZ2F0aW5nIGEgYmxvY2sg
b2YgTFNQcyBmb3IgZnV0dXJlIHVwZGF0ZXMuICBJcyB0aGUgaW50ZW50aW9uIHRvIHByb2hpYml0
IHRoZSBkcml2aW5nIG9mIExTUCBjcmVhdGlvbiBmcm9tIHRoZSBQQ0U/DQoNCkpvbj4gWWVzLCB0
aGUgaW50ZW50aW9uIGlzIHRoYXQgdGhlIFBDRSBkb2VzIG5vdCBkcml2ZSBjcmVhdGlvbiBvZiB0
aGUgTFNQcy4gIFRoYXQgYmVoYXZpb3VyIGlzIGFsbG93ZWQgYnV0IGlzIGRlc2NyaWJlZCBieSBh
IHNlcGFyYXRlIGRyYWZ0IChkcmFmdC1pZXRmLXBjZS1wY2UtaW5pdGlhdGVkLWxzcCkuICBJIHBy
b3Bvc2UgdG8gY2xhcmlmeSB0aGlzIGluIHRoZSBpbnRyb2R1Y3Rpb24gdG8gdGhlIGRyYWZ0LCBz
byB0aGF0IGZ1dHVyZSByZWFkZXJzIGRvbid0IGdldCBjYXVnaHQgYnkgdGhlIHNhbWUgbWlzLWV4
cGVjdGF0aW9uLiAgV2UnbGwgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBzZWN0aW9uIDEsIGFu
ZCBhZGQgYW4gaW5mb3JtYXRpdmUgcmVmZXJlbmNlIHRvIGRyYWZ0LWlldGYtcGNlLXBjZS1pbml0
aWF0ZWQtbHNwLiAgT0s/DQoNCk5FVw0KICAgVGhlIGV4dGVuc2lvbnMgdGhhdCB0aGlzIGRvY3Vt
ZW50IGRlc2NyaWJlcyBkbyBub3QgcGVybWl0IHRoZQ0KICAgUENFIHRvIGRyaXZlIGNyZWF0aW9u
IG9mIGFuIExTUC4gIFRoZSBjb21wYW5pb24gZG9jdW1lbnQNCiAgIFtJLUQuIGlldGYtcGNlLXBj
ZS1pbml0aWF0ZWQtbHNwXSBzcGVjaWZpZXMgUENFLWluaXRpYXRlZCBMU1AgY3JlYXRpb24uDQoN
Cj09PT0NCg0KICAgIEkgaGF2ZSBsb29rZWQgYnV0IEkgY2FuIG5vdCBmaW5kIHRoZSB0ZXh0IGV4
cGxhaW5pbmcgdGhlIHNpZ25pZmljYW5jZSBhbmQgdXNlIG9mIHRoZSBTeW1ib2xpYyBwYXRoIG5h
bWUuICBJdCBpcyBtYW5kYXRlZCBieSB0aGUgZHJhZnQuICBUaGVyZSBzZWVtcyB0byBiZSBhbiBp
bXBsaWNpdCBhc3N1bXB0aW9uIHRhaHQgaXQgaXMgbmVlZGVkIGJ5IHRoZSBQQ0UuICBJZiB0aGUg
ZXhwbGFuYXRpb24gb2YgaG93IG9yIHdoeSBpdCBpcyBuZWVkZWQgaXMgbm90IHByZXNlbnQsIGl0
IHNob3VsZCBiZS4NCg0KSm9uPiBBZ3JlZWQuICBTZXZlcmFsIG9mIG91ciByZXZpZXdlcnMgaGF2
ZSBwaWNrZWQgdXAgb24gdGhpcy4gIEkgdGhpbmsgd2Ugc2hvdWxkIGNsYXJpZnkgdGhpcyBpbiBz
ZWN0aW9uIDcuMy4yICJTeW1ib2xpYyBQYXRoIE5hbWUgVExWIi4NCg0KT0xEDQogICBFYWNoIExT
UCAocGF0aCkgTVVTVCBoYXZlIGEgc3ltYm9saWMgbmFtZSB0aGF0IGlzIHVuaXF1ZSBpbiB0aGUg
UENDLg0KICAgVGhpcyBzeW1ib2xpYyBwYXRoIG5hbWUgTVVTVCByZW1haW4gY29uc3RhbnQgdGhy
b3VnaG91dCBhbiBMU1Ancw0KICAgbGlmZXRpbWUsIHdoaWNoIG1heSBzcGFuIGFjcm9zcyBtdWx0
aXBsZSBjb25zZWN1dGl2ZSBQQ0VQIHNlc3Npb25zDQogICBhbmQvb3IgUENDIHJlc3RhcnRzLiAg
VGhlIHN5bWJvbGljIHBhdGggbmFtZSBNQVkgYmUgc3BlY2lmaWVkIGJ5IGFuDQogICBvcGVyYXRv
ciBpbiBhIFBDQydzIGNvbmZpZ3VyYXRpb24uICBJZiB0aGUgb3BlcmF0b3IgZG9lcyBub3Qgc3Bl
Y2lmeQ0KICAgYSB1bmlxdWUgc3ltYm9saWMgbmFtZSBmb3IgYSBwYXRoLCB0aGUgUENDIE1VU1Qg
YXV0by1nZW5lcmF0ZSBvbmUuDQoNCiAgIFRoZSBTWU1CT0xJQy1QQVRILU5BTUUgVExWIE1VU1Qg
YmUgaW5jbHVkZWQgaW4gdGhlIExTUCBvYmplY3QgaW4gdGhlDQogICBMU1AgU3RhdGUgUmVwb3J0
IChQQ1JwdCkgbWVzc2FnZSB3aGVuIGR1cmluZyBhIGdpdmVuIFBDRVAgc2Vzc2lvbiBhbg0KICAg
TFNQIGlzIGZpcnN0IHJlcG9ydGVkIHRvIGEgUENFLiAgQSBQQ0Mgc2VuZHMgdG8gYSBQQ0UgdGhl
IGZpcnN0IExTUA0KICAgU3RhdGUgUmVwb3J0IGVpdGhlciBkdXJpbmcgU3RhdGUgU3luY2hyb25p
emF0aW9uLCBvciB3aGVuIGEgbmV3IExTUA0KICAgaXMgY29uZmlndXJlZCBhdCB0aGUgUENDLiAg
VGhlIHN5bWJvbGljIHBhdGggbmFtZSBNQVkgYmUgaW5jbHVkZWQgaW4NCiAgIHRoZSBMU1Agb2Jq
ZWN0IGluIHN1YnNlcXVlbnQgTFNQIFN0YXRlIFJlcG9ydHMgZm9yIHRoZSBMU1AuDQoNCiAgIDxz
bmlwPg0KDQogICBTeW1ib2xpYyBQYXRoIE5hbWUgKHZhcmlhYmxlKTogc3ltYm9saWMgbmFtZSBm
b3IgdGhlIExTUCwgdW5pcXVlIGluDQogICB0aGUgUENDLg0KDQpORVcNCiAgIEVhY2ggTFNQIE1V
U1QgaGF2ZSBhIHN5bWJvbGljIHBhdGggbmFtZSB0aGF0IGlzIHVuaXF1ZSBpbiB0aGUgUENDLg0K
ICAgVGhlIHN5bWJvbGljIHBhdGggbmFtZSBpcyBhIGh1bWFuLXJlYWRhYmxlIHN0cmluZyB0aGF0
IGlkZW50aWZpZXMgYW4NCiAgIExTUCBpbiB0aGUgbmV0d29yay4gIFRoZSBzeW1ib2xpYyBwYXRo
IG5hbWUgTVVTVCByZW1haW4gY29uc3RhbnQNCiAgIHRocm91Z2hvdXQgYW4gTFNQJ3MgbGlmZXRp
bWUsIHdoaWNoIG1heSBzcGFuIGFjcm9zcyBtdWx0aXBsZQ0KICAgY29uc2VjdXRpdmUgUENFUCBz
ZXNzaW9ucyBhbmQvb3IgUENDIHJlc3RhcnRzLiAgVGhlIHN5bWJvbGljIHBhdGgNCiAgIG5hbWUg
TUFZIGJlIHNwZWNpZmllZCBieSBhbiBvcGVyYXRvciBpbiBhIFBDQydzIGNvbmZpZ3VyYXRpb24u
ICBJZiB0aGUNCiAgIG9wZXJhdG9yIGRvZXMgbm90IHNwZWNpZnkgYSB1bmlxdWUgc3ltYm9saWMg
bmFtZSBmb3IgYW4gTFNQLCB0aGVuIHRoZQ0KICAgUENDIE1VU1QgYXV0by1nZW5lcmF0ZSBvbmUu
ICAgDQoNCiAgIFRoZSBQQ0UgdXNlcyB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGFzIGEgc3RhYmxl
IGlkZW50aWZpZXIgZm9yIHRoZSBMU1AuDQogICBJZiB0aGUgUENFUCBzZXNzaW9uIHJlc3RhcnRz
LCBvciB0aGUgUENDIHJlc3RhcnRzLCBvciB0aGUgUENDIHJlLWRlbGVnYXRlcw0KICAgdGhlIExT
UCB0byBhIGRpZmZlcmVudCBQQ0UsIHRoZSBzeW1ib2xpYyBwYXRoIG5hbWUgZm9yIHRoZSBMU1Ag
cmVtYWlucw0KICAgY29uc3RhbnQgYW5kIGNhbiBiZSB1c2VkIHRvIGNvcnJlbGF0ZSBhY3Jvc3Mg
dGhlIFBDRVAgc2Vzc2lvbiBpbnN0YW5jZXMuDQoNCiAgIFRoZSBvdGhlciBwcm90b2NvbCBpZGVu
dGlmaWVycyBmb3IgdGhlIExTUCBjYW5ub3QgcmVsaWFibHkgYmUgdXNlZCB0bw0KICAgaWRlbnRp
ZnkgdGhlIExTUCBhY3Jvc3MgbXVsdGlwbGUgUENFUCBzZXNzaW9ucywgZm9yIHRoZSBmb2xsb3dp
bmcgcmVhc29ucy4NCiAgIC0gIFRoZSBQTFNQLUlEIGlzIHVuaXF1ZSBvbmx5IHdpdGhpbiB0aGUg
c2NvcGUgb2YgYSBzaW5nbGUgUENFUCBzZXNzaW9uLg0KICAgLSAgVGhlIExTUC1JREVOVElGSUVS
UyBUTFYgaXMgb25seSBndWFyYW50ZWVkIHRvIGJlIHByZXNlbnQgZm9yIExTUHMgDQogICAgICB0
aGF0IGFyZSBzaWduYWxsZWQgd2l0aCBSU1ZQLVRFLg0KDQogICBUaGUgU1lNQk9MSUMtUEFUSC1O
QU1FIFRMViBNVVNUIGJlIGluY2x1ZGVkIGluIHRoZSBMU1Agb2JqZWN0IGluIHRoZQ0KICAgTFNQ
IFN0YXRlIFJlcG9ydCAoUENScHQpIG1lc3NhZ2Ugd2hlbiBkdXJpbmcgYSBnaXZlbiBQQ0VQIHNl
c3Npb24gYW4NCiAgIExTUCBpcyBmaXJzdCByZXBvcnRlZCB0byBhIFBDRS4gIEEgUENDIHNlbmRz
IHRvIGEgUENFIHRoZSBmaXJzdCBMU1ANCiAgIFN0YXRlIFJlcG9ydCBlaXRoZXIgZHVyaW5nIFN0
YXRlIFN5bmNocm9uaXphdGlvbiwgb3Igd2hlbiBhIG5ldyBMU1ANCiAgIGlzIGNvbmZpZ3VyZWQg
YXQgdGhlIFBDQy4NCg0KICAgVGhlIGluaXRpYWwgUENScHQgY3JlYXRlcyBhIGJpbmRpbmcgYmV0
d2VlbiB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGFuZA0KICAgdGhlIFBMU1AtSUQgZm9yIHRoZSBM
U1Agd2hpY2ggbGFzdHMgZm9yIHRoZSBkdXJhdGlvbiBvZiB0aGUgUENFUCBzZXNzaW9uLg0KICAg
VGhlIFBDQyBNQVkgb21pdCB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGZyb20gc3Vic2VxdWVudCBM
U1AgU3RhdGUNCiAgIFJlcG9ydHMgZm9yIHRoYXQgTFNQIG9uIHRoYXQgUENFUCBzZXNzaW9uLCBh
bmQganVzdCBnaXZlIHRoZSBQTFNQLUlELg0KDQogICA8c25pcD4NCg0KICAgU3ltYm9saWMgUGF0
aCBOYW1lICh2YXJpYWJsZSk6IHN5bWJvbGljIG5hbWUgZm9yIHRoZSBMU1AsIHVuaXF1ZSBpbg0K
ICAgdGhlIFBDQy4gIEl0IFNIT1VMRCBiZSBhIHN0cmluZyBvZiBwcmludGFibGUgQVNDSUkgY2hh
cmFjdGVycyBhbmQgU0hPVUxEDQogICBiZSBOVUxMLXRlcm1pbmF0ZWQuICBUaGUgU3ltYm9saWMg
UGF0aCBOYW1lIChpbmNsdWRpbmcgaXRzIE5VTEwNCiAgIHRlcm1pbmF0b3IpIE1VU1QgYmUgcGFk
ZGVkIHRvIDQtYnl0ZXMgYWxpZ25tZW50OyB0aGUgcGFkZGluZyBpdHNlbGYNCiAgIE1VU1QgTk9U
IGJlIGluY2x1ZGVkIGluIHRoZSBMZW5ndGggZmllbGQuDQoNCkVORCBORVcNCg0KPT09PQ0KDQpO
aXRzL2VkaXRvcmlhbCBjb21tZW50czogDQogICAgU2hvdWxkIHRoZSB0ZXh0IG9uIHRoZSBTIGJp
dCBpbiBzZWN0aW9uIDcuMyAodGhlIExTUCBPYmplY3QNCmRlZmluaXRpb24pIG5vdGUgdGhhdCBp
dCBzaG91bGQgYmUgc2V0IHRvIDAgb24gYWxsIG1lc3NhZ2VzIHNlbnQgYnkgdGhlIFBDRT8gIFNo
b3VsZCB0aGF0IGFsc28gYmUgc3RhdGVkIGZvciB0aGUgUiBiaXQ/ICBBbmQgdGhlIE8gYml0cz8N
Cg0KSm9uPiBZZXMuICBXZSB3aWxsIGFkZCBhIG5vdGUgdG8gdGhlIGRlc2NyaXB0aW9uIG9mIHRo
ZXNlIGZpZWxkcy4NCg0KPT09PQ0KDQogIFNlY3Rpb24gOS4yIHNlZW1zIHZlcnkgb2RkLiAgSXQg
c3RhdGVzIHRoYXQgdGhlIElFVEYgIlNIT1VMRCIgZG8gc29tZSBhZGRpdGlvbmFsIHdvcmsuICBJ
IHVuZGVyc3RhbmQgd2h5IHRlaCB3b3JrIGlzIG5lZWRlZC4gIEJ1dCB0aGlzIGRvZXMgbm90IHNl
ZW0gdG8gbWF0Y2ggdGhlIFJGQyAyMTE5IG1lYW5pbmcgb2YgU0hPVUxEIGFzIGl0IGRvZXMgbm90
IGFwcGx5IHRvIGVpdGVociB0aGUgaW1wbGVtZW50b3Igb3IgdGhlIGltcGxlbWVudGF0aW9uLg0K
DQpKb24+IEkgYWdyZWUgLSB0aGlzIGlzIGluY29ycmVjdCB1c2Ugb2YgU0hPVUxELiAgSXQgYWxz
byByZWZlcmVuY2VzIHRoZSBNSUIgd2l0aG91dCBldmVuIG1lbnRpb25pbmcgdGhlIFlBTkcsIHdo
aWNoIGlzIGEgc3ltcHRvbSBvZiB0aGlzIGRvY3VtZW50J3MgYWR2YW5jZWQgYWdlLiAgV2UnbGwg
Y2hhbmdlIHRoaXMgYXMgZm9sbG93cyAoYW5kIGFkZCB0d28gaW5mb3JtYXRpdmUgcmVmZXJlbmNl
cykuDQoNCk5FVw0KICAgVGhlIFBDRVAgWUFORyBtb2R1bGUgW0ktRC5pZXRmLXBjZS1wY2VwLXlh
bmddIHNob3VsZCBpbmNsdWRlDQogICAtICBhZHZlcnRpc2VkIHN0YXRlZnVsIGNhcGFiaWxpdGll
cyBhbmQgc3luY2hyb25pemF0aW9uIHN0YXR1cyBwZXIgUENFUCBzZXNzaW9uDQogICAtICB0aGUg
ZGVsZWdhdGlvbiBzdGF0dXMgb2YgZWFjaCBjb25maWd1cmVkIExTUC4NCg0KICAgVGhlIFBDRVAg
TUlCIFtSRkM3NDIwXSBjb3VsZCBhbHNvIGJlIHVwZGF0ZWQgdG8gaW5jbHVkZSB0aGlzIGluZm9y
bWF0aW9uLg0KDQo9PT09DQoNCg==


From nobody Tue Apr 11 03:46:46 2017
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E54AC127078; Tue, 11 Apr 2017 03:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=metaswitch.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 NyxZt0gFjSPL; Tue, 11 Apr 2017 03:46:36 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0137.outbound.protection.outlook.com [104.47.34.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56EF51252BA; Tue, 11 Apr 2017 03:46:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5M81vJxfm0mcU96jGXIWE8jVWZTU5bII4o55ElfSyZs=; b=OALb//c1EW4UEw2qA2w+yisSpO58XR/dUW2XqwblMn4Wa8aEDWfuJEiFx/bOfJh5OuGtt0NSscriZ8g8j1myFzv7uWLSzE/oDUkCyNcwNmQR7s600aAUDcfT6pjPMSZl6z1Fei7yOB3K4MzdWop5UURlBkht4FCGtpBbmwwWtoQ=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1911.namprd02.prod.outlook.com (10.163.75.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 10:46:34 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 10:46:34 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-pce-stateful-pce@ietf.org" <draft-ietf-pce-stateful-pce@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>
Subject: RE: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP Extensions for Stateful PCE) to Proposed Standard
Thread-Topic: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP Extensions for Stateful PCE) to Proposed Standard
Thread-Index: AQFxcgmRJRd+l0rmBvxaEPG5ui9ti6IuXg9wgFQXdRA=
Date: Tue, 11 Apr 2017 10:46:34 +0000
Message-ID: <BY2PR0201MB1910BB462CDBE981F27B249984000@BY2PR0201MB1910.namprd02.prod.outlook.com>
References: <148711263433.10090.8026814862201890553.idtracker@ietfa.amsl.com> <0a3201d288a1$632ecf50$298c6df0$@olddog.co.uk>
In-Reply-To: <0a3201d288a1$632ecf50$298c6df0$@olddog.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: olddog.co.uk; dkim=none (message not signed) header.d=none;olddog.co.uk; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [82.132.227.234]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1911; 7:K+ds32KYHe8j+1372VPUSIPkKQMDKv7n4QyptKbRvf8qZAyIbkkGQyl5j8PPwvPpVT4v693FNOCYn5/qcGyEkx5PDBpRww3kIepzOfAbSXUyrKM5zotMNpnMujXgex7tlZwj5FKLS0imZZXL9gI5W1p6JrEGt8ouqk21u7NGrKLLiQQy/LgvXFzqFKg0kFXffkl6lFf7ICtZfZ1SD8wzNM8/xrWlae5TSKh3HT9kHYPwjWmjApNs1aySP1oJPoz19h+7vQZb+LJE9wXEKfxFPbAQCjmvyq7XyY2usHZx4yv4LmBM34Vo/pQqD3iqHWkou2Cwgm3q9aSRvQJDtLwneA==
x-ms-office365-filtering-correlation-id: bd94dff3-0342-426d-df85-08d480c805cc
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR0201MB1911; 
x-microsoft-antispam-prvs: <BY2PR0201MB1911EDE69679ED6430C881BB84000@BY2PR0201MB1911.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(6072148); SRVR:BY2PR0201MB1911; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1911; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39400400002)(39410400002)(37854004)(13464003)(66654002)(54094003)(51914003)(55016002)(38730400002)(229853002)(54906002)(86362001)(99286003)(33656002)(9686003)(3280700002)(8936002)(2900100001)(230783001)(7696004)(8676002)(3660700001)(81166006)(2906002)(77096006)(3846002)(6436002)(6506006)(102836003)(2950100002)(6116002)(6246003)(66066001)(4326008)(305945005)(76176999)(53546009)(25786009)(2501003)(74316002)(54356999)(7736002)(50986999)(53936002)(189998001)(5660300001)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1911; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 10:46:34.2987 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1911
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kzpZcAa9uGL_Zad9nWW7M9NSZcI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 10:46:38 -0000

Hi Adrian

Many thanks for these comments.  I'm picking up this thread and replying as=
 PCE working group chair, as the authors are unavailable.  I apologise for =
the delay.

Please see my proposed resolutions inline below, marked with "Jon>"

Best regards
Jon


-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
Sent: 16 February 2017 22:10
To: ietf@ietf.org
Cc: draft-ietf-pce-stateful-pce@ietf.org; pce@ietf.org; pce-chairs@ietf.org
Subject: RE: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP Ex=
tensions for Stateful PCE) to Proposed Standard

IETF last call

I have read and commented on this document during its production by the PCE=
 working group. It constitutes a missing piece of the puzzle that we starte=
d with RFC 4655.

The publication of this work as an RFC is long overdue to the point that im=
plementers have become confused over the last couple of years about whether=
 it would ever be published.

However, on re-reading this final version, I notice a few points.
Nothing major.

Thanks for the work,
Adrian

---
             =20
The reference to [I-D.ietf-pce-stateful-pce-app] is for some terms that are=
 fundamental to understanding this document.  It needs to be a normative re=
ference.

Jon> ACK. Should be RFC 8051.

---

3.1.3 has...
   Note that existing configuration tools and protocols can be used to
   set LSP state.
...which is true, but is lacking references for the inquisitive mind.

Just need some form of "(such as, ....)"

Jon> "... , such as a Command Line Interface (CLI) tool."

---

In the RBNF in section 6 there is some mismatch between hyphen and undersco=
re. Not only is there a mixture of uses, but sometime the same construct is=
 named in different ways (e.g., in 6.1 you have <actual_attribute_list> and=
 <actual_attribute-list>)

Jon> ACK, will tidy this up.

---

In 6.2, would it help show consistency with 6.1 and remove potential confus=
ion if

      <path>::=3D <intended_path><attribute-list>

read

      <path>::=3D <intended_path><intended-attribute-list>

Jon> ACK

---

The use of TBD in the document to flag where IANA allocations need to be up=
dated in the document is going to cause the RFC editor additional work and =
is error prone. What you should probably do is use TBD1, TBD2, etc. in the =
text and then include those flags in the IANA considerations sections.

However (!) I note that early allocation has been done for most of the code=
 points. So...
- The IANA section should refer to this and ask IANA to confirm those
  allocations and update the registry to point to this document when it
  is an RFC
- The actual numbers can be filled in in place of all the TBDs
- It would help the reader/coder if you pointed forward to the new
  registries (for example, from 7.3.3 to 8.9)

Jon> ACK although having me do it is equally error prone ;-)

---

7.3.2 Symbolic Path Name

You need to give some clues!
Is this supposed to be printable?
Is this in a particular character set?
Is it supposed to be null terminated (which would mean that if it was a mul=
tiple of 4 octets you'd need another four octets of pad)

Jon> This was also raised by others - here is my proposed resolution.

OLD
   Each LSP (path) MUST have a symbolic name that is unique in the PCC.
   This symbolic path name MUST remain constant throughout an LSP's
   lifetime, which may span across multiple consecutive PCEP sessions
   and/or PCC restarts.  The symbolic path name MAY be specified by an
   operator in a PCC's configuration.  If the operator does not specify
   a unique symbolic name for a path, the PCC MUST auto-generate one.

   The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
   LSP State Report (PCRpt) message when during a given PCEP session an
   LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
   State Report either during State Synchronization, or when a new LSP
   is configured at the PCC.  The symbolic path name MAY be included in
   the LSP object in subsequent LSP State Reports for the LSP.

   <snip>

   Symbolic Path Name (variable): symbolic name for the LSP, unique in
   the PCC.

NEW
   Each LSP MUST have a symbolic path name that is unique in the PCC.
   The symbolic path name is a human-readable string that identifies an
   LSP in the network.  The symbolic path name MUST remain constant
   throughout an LSP's lifetime, which may span across multiple
   consecutive PCEP sessions and/or PCC restarts.  The symbolic path
   name MAY be specified by an operator in a PCC's configuration.  If the
   operator does not specify a unique symbolic name for an LSP, then the
   PCC MUST auto-generate one.  =20

   The PCE uses the symbolic path name as a stable identifier for the LSP.
   If the PCEP session restarts, or the PCC restarts, or the PCC re-delegat=
es
   the LSP to a different PCE, the symbolic path name for the LSP remains
   constant and can be used to correlate across the PCEP session instances.

   The other protocol identifiers for the LSP cannot reliably be used to
   identify the LSP across multiple PCEP sessions, for the following reason=
s.
   -  The PLSP-ID is unique only within the scope of a single PCEP session.
   -  The LSP-IDENTIFIERS TLV is only guaranteed to be present for LSPs=20
      that are signalled with RSVP-TE.

   The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
   LSP State Report (PCRpt) message when during a given PCEP session an
   LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
   State Report either during State Synchronization, or when a new LSP
   is configured at the PCC.

   The initial PCRpt creates a binding between the symbolic path name and
   the PLSP-ID for the LSP which lasts for the duration of the PCEP session=
.
   The PCC MAY omit the symbolic path name from subsequent LSP State
   Reports for that LSP on that PCEP session, and just give the PLSP-ID.

   <snip>

   Symbolic Path Name (variable): symbolic name for the LSP, unique in
   the PCC.  It SHOULD be a string of printable ASCII characters and SHOULD
   be NULL-terminated.  The Symbolic Path Name (including its NULL
   terminator) MUST be padded to 4-bytes alignment; the padding itself
   MUST NOT be included in the Length field.

END NEW


---

7.3.4
While 2205 is technically a good enough reference for the ERROR_SPEC object=
, I wonder if the reader will automatically be aware of the additional work=
 on that object in 3471, 4201, and 4920.

Jon> Did you mean 3473 instead of 3471?  I don't think it's necessary to ex=
haustively list all RFCs that make use of ERROR_SPEC.  None of these RFCs u=
pdates 2205.


> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of The IESG
> Sent: 14 February 2017 22:51
> To: IETF-Announce
> Cc: draft-ietf-pce-stateful-pce@ietf.org; pce@ietf.org;=20
> pce-chairs@ietf.org
> Subject: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP
Extensions for
> Stateful PCE) to Proposed Standard
>=20
>=20
> The IESG has received a request from the Path Computation Element WG
> (pce) to consider the following document:
> - 'PCEP Extensions for Stateful PCE'
>   <draft-ietf-pce-stateful-pce-18.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2017-02-28. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.


From nobody Tue Apr 11 04:11:48 2017
Return-Path: <prvs=1274da9a4c=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC5B1275AB for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:11: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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jkh6Cb5zdWR for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:11:44 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 037A6127869 for <ietf@ietf.org>; Tue, 11 Apr 2017 04:11:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491909102; x=1492513902; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=DTy3YKkrP6capTMY8hanBo2PJ cE+yqkmmzGa1vtQtjw=; b=Rc26aSafYTFfC5Zju6GzOVvJSPjK+JjeXZB+59LfA 5rCP5aMfELUDb97MQTLnr9U1Sl2UvikqyrJwshhWRsA7YYyJmixNIwXIO+krHgFP FwAwxb9a7BQCyUz+Zdu2WNmD0xnVyLQpoYRMIC6W3ahzfv/yvdTwxOpzIFebTc6t Dk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=cQEMfNUsFzrwHAUm+6LgrXlmzIMs2yaFrDVU488E2G42O6FfFIERvI9KsBJK kZg0E25IJmsxSLRwMPT1vxKZYOMXsKUIO+kbAxyxZyHuXdbMw3NdIVdA8 e1Fy2MYnhJN5WyUiJLOPWcQosd+R9mjyddVrly7tpUCyDEBcTDCNs8=;
X-MDAV-Processed: mail.consulintel.es, Tue, 11 Apr 2017 13:11:42 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 11 Apr 2017 13:11:41 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005406170.msg for <ietf@ietf.org>; Tue, 11 Apr 2017 13:11:41 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170411:md50005406170::m9L8mJG6l5YcjY8H:0000F8f/
X-Return-Path: prvs=1274da9a4c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Tue, 11 Apr 2017 13:11:34 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>, <iaoc@ietf.org>
Message-ID: <22EB34C2-CF25-4E18-8185-47F27363A6AD@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es>
In-Reply-To: <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jVzR4ZtBLCaZu9nexVPCpiVUeUA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 11:11:46 -0000

Can we get an answer from the IAOC to the questions below?

If we cancel San Francisco, how much that is going to cost to the IETF for =
each of two planned meetings?

Can we cancel the actual hotel contract considering the new US situation? I=
f not, has this been considered for new contracts to avoid this problem?

Otherwise there is any reason that can justify the lack of transparency in =
this?

Regards,
Jordi
=20

-----Mensaje original-----
De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 10:26
Para: <iaoc@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    One important question here, same as we had in the case of Singapore.
   =20
    If we cancel San Francisco, how much that is going to cost to the IETF =
for each of two planned meetings?
   =20
    Furthermore, can the IAOC respond to this:
   =20
    Can we cancel the actual hotel contract considering the new US situatio=
n? If not, has this been considered for new contracts to avoid this problem=
?
   =20
    I think the relevant information in the contract need to be disclosed a=
nd have it now on the table, otherwise we will be wasting the time discussi=
ng possibilities that are actually impossible to assume for the IETF =E2=80=
=A6
   =20
    My general position is:
    1) I will prefer not cancelling already planned meetings.
    2) I will prefer not =E2=80=9Cblocking=E2=80=9D any regions or countrie=
s from future meetings, including US.
    3) However, for already contracted meetings, if this is going to cost I=
ETF thousands of dollars, we can=E2=80=99t afford that.
    4) We must work with authorities to avoid people being banned for atten=
ding the meetings.
   =20
    Maybe I=E2=80=99ve missed responses to some of my answers already, in a=
ny case, can the IAOC provide urgently those with a complete summary of the=
 situation?
   =20
    Regards,
    Jordi
    =20
   =20
    -----Mensaje original-----
    De: Eliot Lear <lear@cisco.com>
    Responder a: <lear@cisco.com>
    Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 6:39
    Para: Nico Williams <nico@cryptonector.com>, Yoav Nir <ynir.ietf@gmail.=
com>
    CC: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel=
.es>, Jared Mauch <jared@puck.nether.net>
    Asunto: Re: IAOC requesting input on (potential) meeting cities
   =20
        Nico,
       =20
        On 4/5/17 12:10 AM, Nico Williams wrote:
        > I do suspect that the U.S. will be a more difficult location for =
more
        > attendees than other locations.  Certainly the news we all see is=
 not
        > encouraging as to hosting IETF meetings in the U.S.  This I don't=
 deny.
        > Though it's also possible that this is becoming a self-reinforcin=
g meme
        > and that we're just not seeing incidents in other countries in th=
e news.
        > In any case, the U.S. certainly does not have a monopoly on the b=
order
        > harasment business.
       =20
        Certainly people have had trouble getting into other countries, mos=
t
        notably Canada where an IAB member was refused entry.  But this isn=
't
        just news.  It is a series of declarations by the U.S. government o=
f
        their intentions, and the IAOC has to plan ahead.  That's why Jared=
's
        request for data is simply not tenable *at this stage*.  If it turn=
s out
        that things aren't so bad, the IAOC can react accordingly.  However=
, as
        I wrote in my original email, there is now good reason to believe t=
hat
        things will get worse, due to the European Parliament=E2=80=99s dec=
ision to
        require visas from U.S. citizens.
       =20
        > Some people may wish to boycott the U.S. by refusing to host even=
ts
        > there.  There is some precedent for such a boycott.  For example,=
 some
        > time back an obscure agency of the Texas state government decided=
 to
        > guard its surplus budget by policing public drunkenness at hotel =
bars,
        > which led to a number of conferences pulling out of Texas, and th=
e
        > ensuing bad PR led the legislature to rein in said agency.
        >
        > However, at the scale of a state/province the politics of boycott=
s is
        > generally not partisan, but at a national/global scale it tends t=
o be
        > rankly partisan, and boycotts may not be productive and may be di=
visive,
        > and should be approached with care.  Here "care" means: get some
        > evidence of negative impact on participation. =20
       =20
        We ALREADY have evidence, as some people couldn't make Chicago, and=
 said
        so on this very list (and, by the way, were shamefully attacked and
        dismissed (no, it certainly wasn't you)).  What we don't have is an
        understanding of the order of magnitude of the impact, and that is =
going
        to be very hard to gather in so  fluid a situation with so long a
        lookahead.  The point, by the way, as I see it, is not to punish th=
e
        U.S. but to hold a successful meeting (that is what the mtgvenue dr=
aft
        states as well).
       =20
        > Reducing frequency of
        > U.S. meetings is not a boycott, and is something the IETF has bee=
n doing
        > for a long time anyways.  Further reducing that frequency in the =
short
        > term would be perfectly fine, though it would also reduce opportu=
nities
        > for gather the stats we really need to make a sound, non-partisan
        > decision to boycott if the stats warrant it.
        >
       =20
        Turn this around: suppose we do keep the meeting in San Francisco, =
for
        instance, and some number of people cannot get there for whatever
        reason, or cannot otherwise function on an equal footing.  Would th=
e
        IAOC then be attacked for having ignored the vast number of warning=
s
        that have been signaled?
       =20
        Eliot
       =20
       =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Apr 11 04:48:11 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A90E129467 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 TuGxzXB32r5t for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:48:08 -0700 (PDT)
Received: from relais-inet.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 BAD8112945D for <ietf@ietf.org>; Tue, 11 Apr 2017 04:48:06 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id CE9F72069A; Tue, 11 Apr 2017 13:48:04 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.2]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 8F676C006B; Tue, 11 Apr 2017 13:47:49 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0319.002; Tue, 11 Apr 2017 13:47:49 +0200
From: <mohamed.boucadair@orange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSsqDJ4CrS2IjNNEiDISRRkDKmOqG/4Emg
Date: Tue, 11 Apr 2017 11:47:48 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
In-Reply-To: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DWiq4zaaqmHy3x1E53ExRo-aAfU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 11:48:10 -0000

SGkgU3RlcGhlbiwgDQoNClBsZWFzZSBzZWUgaW5saW5lLg0KDQpDaGVlcnMsDQpNZWQNCg0KPiAt
LS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDogU3RlcGhlbiBGYXJyZWxsIFttYWls
dG86c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZV0NCj4gRW52b3nDqcKgOiBtYXJkaSAxMSBhdnJp
bCAyMDE3IDEwOjUxDQo+IMOAwqA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE47IE1hcnRpbiBU
aG9tc29uOyBpZXRmQGlldGYub3JnDQo+IENjwqA6IGRyYWZ0LWRvbHNvbi1wbHVzLW1pZGRsZWJv
eC1iZW5lZml0c0B0b29scy5pZXRmLm9yZw0KPiBPYmpldMKgOiBSZTogZHJhZnQtZG9sc29uLXBs
dXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmlldyBvZiBkcmFmdC0NCj4gbW0td2ct
ZWZmZWN0LWVuY3J5cHQtMDkpDQo+IA0KPiANCj4gSGkgTWVkLA0KPiANCj4gT24gMTEvMDQvMTcg
MDk6MTUsIG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20gd3JvdGU6DQo+ID4+IEkgaG9wZSB0
aGF0IHRoZSBJRVRGIG5ldmVyIHB1Ymxpc2hlcw0KPiA+PiBkcmFmdC1kb2xzb24tcGx1cy1taWRk
bGVib3gtYmVuZWZpdHM7IGl0IG1ha2VzIGNsYWltcyBhYm91dCB0aGUNCj4gPj4gYmVuZWZpdHMg
b2Ygc3BlY2lmaWMgc29sdXRpb25zIGZvciBkaWZmZXJlbnQgdXNlIGNhc2VzIHdpdGggdGhlDQo+
ID4+IGdvYWwgb2YganVzdGlmeWluZyB0aG9zZSBzb2x1dGlvbnMuDQo+IA0KPiA+IFtNZWRdIEkn
bSBhZnJhaWQgdGhpcyBpcyBzcGVjdWxhdGluZyBhYm91dCB0aGUgaW50ZW50IG9mDQo+ID4gZHJh
ZnQtZG9sc29uLiBBc3N1cmVkIHRoaXMgaXMgbm90IHRoZSBwdXJwb3NlIG9mIHRoYXQgZG9jdW1l
bnQuIFRoZQ0KPiA+IG1vdGl2YXRpb24gaXMgdG8gZG9jdW1lbnQgY3VycmVudCBwcmFjdGljZXMg
d2l0aG91dCBpbmNsdWRpbmcgYW55DQo+ID4gcmVjb21tZW5kYXRpb24gb3IgY2xhaW1pbmcgdGhl
c2Ugc29sdXRpb25zIGFyZSBzdXBlcmlvciB0byBvdGhlcnMuDQo+IA0KPiBKdXN0IHRvIG5vdGUg
dGhhdCBJIGNvbXBsZXRlbHkgYWdyZWUgd2l0aCBNYXJ0aW4ncyBpbnRlcnByZXRhdGlvbg0KPiBv
ZiB0aGUgdGhydXN0IG9mIHRoaXMgZHJhZnQgYW5kIEkgdG90YWxseSBmYWlsIHRvIHNlZSBob3cg
eW91cg0KPiBhcmd1bWVudCBhYm92ZSBjYW4gYmUganVzdGlmaWVkIGdpdmVuIHRoYXQgZHJhZnQg
dGl0bGUsIGFic3RyYWN0DQo+IGFuZCBldmVuIGZpbGVuYW1lIChhbmQgYWxzbyB0aGUgY29udGVu
dDstKS4NCg0KW01lZF0gImJlbmVmaWNpYWwiIGlzIGRlcml2ZWQgZnJvbSB0aGUgaW5pdGlhbCBy
ZXF1ZXN0IHRoYXQgbW90aXZhdGVkIHRoaXMgZHJhZnQgKGV4Y2VycHQgZnJvbSB0aGUgYWJzdHJh
Y3QpOg0KDQogICBBdCBJRVRGOTcsIGF0IGEgbWVldGluZyByZWdhcmRpbmcgdGhlIFBhdGggTGF5
ZXIgVURQIFN1YnN0cmF0ZSAoUExVUykNCiAgIHByb3RvY29sLCBhIHJlcXVlc3Qgd2FzIG1hZGUg
Zm9yIGRvY3VtZW50YXRpb24gYWJvdXQgdGhlIGJlbmVmaXRzDQogICAgICAgICAgICAgXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl4NCiAgIHRo
YXQgbWlnaHQgYmUgcHJvdmlkZWQgYnkgcGVybWl0dGluZyBtaWRkbGVib3hlcyB0byBoYXZlIHNv
bWUNCiAgIF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eDQogICB2aXNpYmlsaXR5IHRvIHRyYW5zcG9ydC1sYXllciBpbmZvcm1hdGlv
bi4NCiAgIF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXg0KDQogV2hl
biB0aGUgYWJzdHJhY3QNCj4gc2F5cyAiVGhpcyBkb2N1bWVudCBzdW1tYXJpemVzIGJlbmVmaXRz
IiB0aGVuIEkgY2Fubm90IGludGVycHJldA0KPiB0aGF0IGFzIG90aGVyIHRoYW4gYmVpbmcgaW50
ZW5kZWQgdG8ganVzdGlmeSB0aGUgdXNlcyBkZXNjcmliZWQuDQoNCltNZWRdIEkgd291bGQgcHJl
ZmVyIGlmIHdlIGNhbiBhdm9pZCB0byAiaW50ZXJwcmV0IiwgYnV0IHJhaXNlIHF1ZXN0aW9ucyB0
byB0aGUgYXV0aG9ycyBpZiB0aGVyZSBpcyBhIGRvdWJ0LiBUaGUgZG9jdW1lbnQgZG9lcyBub3Qg
cHJvdmlkZSBhIHJlY29tbWVuZGF0aW9uIG9yIGNsYWltcyB0aGlzIGlzIHRoZSBvbmx5IHdheSB0
byBhY2hpZXZlIHRoZSB0ZWNobmljYWwgZ29hbHMuIEl0IGRvZXMgb25seSByZWZsZWN0IHNvbWUg
ZGVwbG95bWVudCByZWFsaXR5IHRvZ2V0aGVyIHdpdGggc29tZSBtb3RpdmF0aW9ucy4gICANCg0K
PiANCj4gQSBmYWlybHkgdGhvcm91Z2ggcmUtd3JpdGUgdG8gYWltIHRvIGRlc2NyaWJlIHRoZSBw
cm9zIGFuZCBjb25zDQo+IHdvdWxkIGJlIGEgZGlmZmVyZW50IGFuZCBtb3JlIHVzZWZ1bCBkb2N1
bWVudC4NCg0KW01lZF0gVGhlcmUgYXJlIGFscmVhZHkgbWFueSBSRkNzIHRoYXQgZGlzY3VzcyB0
aGUgaXNzdWVzL2NvbnMgKEkgY2FuIGNpdGUgdGhpcyBSRkMgSSBjby1hdXRob3JlZCBodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjI2OSBmb3IgdGhlIENHTiBjYXNlKS4gV2hhdCBpcyBu
ZWVkZWQgSU1ITyBpcyBzb21ldGhpbmcgZWxzZTogdW5kZXJzdGFuZCB0aGUgcmVxdWlyZW1lbnRz
IHRoYXQgbGVkIHRvIGRlcGxveSBzb21lIG9mIHRoZXNlIGZ1bmN0aW9ucy4gIA0KDQogU2ltaWxh
cmx5IGEgZHJhZnQNCj4gdGhhdCBzdHJpdmVzIHRvIG5ldXRyYWxseSBkZXNjcmliZSBleGlzdGlu
ZyByZWFsaXR5IGNvdWxkIG1heWJlDQo+IGJlIHVzZWZ1bCAoKikNCg0KW01lZF0gVGhpcyBpcyB0
aGUgaW50ZW50IG9mIGRyYWZ0LWRvbHNvbi4NCg0KIGJ1dCBvbmUgdGhhdCBvbmx5IGRlc2NyaWJl
cyBtaWRkbGVib3ggZnJpZW5kcyB3aXRoDQo+ICJiZW5lZml0cyIgaXMgbm90IElNTyBiZW5lZmlj
aWFsIDstKQ0KDQpbTWVkXSBUaGUgaW50ZW50IGlzIG5vdCB0byAic2VsbCBzb21ldGhpbmciIGJ1
dCB0byB1bmRlcnN0YW5kIHRoZSB0ZWNobmljYWwgbmVlZHMgc28gdGhhdCBob3BlZnVsbHkgd2Ug
Y2FuIGhhdmUgYSByZWZlcmVuY2UgZm9yIGZ1dHVyZSBzb2x1dGlvbi1vcmllbnRlZCBkaXNjdXNz
aW9ucy4gDQpJZiBhIGdpdmVuIGZ1bmN0aW9uIGNhbiBiZSBwcm92aWRlZCB3aXRob3V0IGludm9s
dmluZyBhbiBvbi1wYXRoIGRldmljZSwgdGhpcyB3b3VsZCBiZSBncmVhdCBmb3Igb3BlcmF0b3Jz
IChvcHRpbWl6ZSBDQVBFWC9PUEVYIGlzIG91ciBtb3R0bykuICAgICAgDQoNCj4gDQo+IENoZWVy
cywNCj4gUy4NCj4gDQo+ICgqKSBUaGF0IGlzIHRoZSBhcmd1bWVudCBmb3IgZHJhZnQtbW0tZWZm
ZWN0LWVuY3J5cHQsIGZvciB3aGljaCBJDQo+IGRvIHN1cHBvcnQgcHVibGljYXRpb24gKGFwcGFy
ZW50bHkgaW4gZGlzYWdyZWVtZW50IHdpdGggTWFydGluIGluDQo+IHRoYXQgY2FzZTotKQ0KPiAN
Cj4gDQo+IA0KDQo=


From nobody Tue Apr 11 05:03:25 2017
Return-Path: <ddolson@sandvine.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB43D1298A1 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 05:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 aaMXIQ4blvHA for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 05:03:06 -0700 (PDT)
Received: from mail1.sandvine.com (mail1.sandvine.com [64.7.137.165]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F29912951F for <ietf@ietf.org>; Tue, 11 Apr 2017 05:03:06 -0700 (PDT)
Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by WTL-EXCHP-3.sandvine.com ([::1]) with mapi id 14.03.0319.002; Tue, 11 Apr 2017 08:03:04 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AdKym8EY4i6VvDHuQjir6aepfU3ztwAJoxYAAAYqoQD//8E2LQ==
Date: Tue, 11 Apr 2017 12:03:04 +0000
Message-ID: <20170411120303.5128273.2297.7062@sandvine.com>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>, <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3q4myL9x2Px1IugPDa6Tzw_Gft0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 12:03:09 -0000

UmVnYXJkaW5nICJiZW5lZml0cyIsIHRoZXNlIGRldmljZXMgY2xlYXJseSBoYXZlIHBlcmNlaXZl
ZCBiZW5lZml0cyB0byB0aG9zZSB3aG8gZGVwbG95IHRoZW0uIE15IHZpZXcgaXMgdGhhdCB0aGUg
ZG9jdW1lbnQgc2hvdWxkIGV4cGxhaW4gdGhhdCBwZXJzcGVjdGl2ZSBmb3IgcmVhZGVycyB3aG8g
bGFjayB0aGUgb3BlcmF0b3IgcGVyc3BlY3RpdmUuDQpUaGUgaW50ZW50IHdhcyBub3QgdG8gbWFu
ZGF0ZSBvciByZWNvbW1lbmQgZGVwbG95bWVudHMuDQoNCkRhdmlkIERvbHNvbg0K4oCODQogIE9y
aWdpbmFsIE1lc3NhZ2UNCkZyb206IG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20NClNlbnQ6
IFR1ZXNkYXksIEFwcmlsIDExLCAyMDE3IDc6NDggQU0NClRvOiBTdGVwaGVuIEZhcnJlbGw7IE1h
cnRpbiBUaG9tc29uOyBpZXRmQGlldGYub3JnDQpDYzogZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxl
Ym94LWJlbmVmaXRzQHRvb2xzLmlldGYub3JnDQpTdWJqZWN0OiBSRTogZHJhZnQtZG9sc29uLXBs
dXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmlldyBvZiBkcmFmdC1tbS13Zy1lZmZl
Y3QtZW5jcnlwdC0wOSkNCg0KDQpIaSBTdGVwaGVuLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0K
Q2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlIDogU3Rl
cGhlbiBGYXJyZWxsIFttYWlsdG86c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZV0NCj4gRW52b3nD
qSA6IG1hcmRpIDExIGF2cmlsIDIwMTcgMTA6NTENCj4gw4AgOiBCT1VDQURBSVIgTW9oYW1lZCBJ
TVQvT0xOOyBNYXJ0aW4gVGhvbXNvbjsgaWV0ZkBpZXRmLm9yZw0KPiBDYyA6IGRyYWZ0LWRvbHNv
bi1wbHVzLW1pZGRsZWJveC1iZW5lZml0c0B0b29scy5pZXRmLm9yZw0KPiBPYmpldCA6IFJlOiBk
cmFmdC1kb2xzb24tcGx1cy1taWRkbGVib3gtYmVuZWZpdHMgKHdhcyBSRTogUmV2aWV3IG9mIGRy
YWZ0LQ0KPiBtbS13Zy1lZmZlY3QtZW5jcnlwdC0wOSkNCj4NCj4NCj4gSGkgTWVkLA0KPg0KPiBP
biAxMS8wNC8xNyAwOToxNSwgbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSB3cm90ZToNCj4g
Pj4gSSBob3BlIHRoYXQgdGhlIElFVEYgbmV2ZXIgcHVibGlzaGVzDQo+ID4+IGRyYWZ0LWRvbHNv
bi1wbHVzLW1pZGRsZWJveC1iZW5lZml0czsgaXQgbWFrZXMgY2xhaW1zIGFib3V0IHRoZQ0KPiA+
PiBiZW5lZml0cyBvZiBzcGVjaWZpYyBzb2x1dGlvbnMgZm9yIGRpZmZlcmVudCB1c2UgY2FzZXMg
d2l0aCB0aGUNCj4gPj4gZ29hbCBvZiBqdXN0aWZ5aW5nIHRob3NlIHNvbHV0aW9ucy4NCj4NCj4g
PiBbTWVkXSBJJ20gYWZyYWlkIHRoaXMgaXMgc3BlY3VsYXRpbmcgYWJvdXQgdGhlIGludGVudCBv
Zg0KPiA+IGRyYWZ0LWRvbHNvbi4gQXNzdXJlZCB0aGlzIGlzIG5vdCB0aGUgcHVycG9zZSBvZiB0
aGF0IGRvY3VtZW50LiBUaGUNCj4gPiBtb3RpdmF0aW9uIGlzIHRvIGRvY3VtZW50IGN1cnJlbnQg
cHJhY3RpY2VzIHdpdGhvdXQgaW5jbHVkaW5nIGFueQ0KPiA+IHJlY29tbWVuZGF0aW9uIG9yIGNs
YWltaW5nIHRoZXNlIHNvbHV0aW9ucyBhcmUgc3VwZXJpb3IgdG8gb3RoZXJzLg0KPg0KPiBKdXN0
IHRvIG5vdGUgdGhhdCBJIGNvbXBsZXRlbHkgYWdyZWUgd2l0aCBNYXJ0aW4ncyBpbnRlcnByZXRh
dGlvbg0KPiBvZiB0aGUgdGhydXN0IG9mIHRoaXMgZHJhZnQgYW5kIEkgdG90YWxseSBmYWlsIHRv
IHNlZSBob3cgeW91cg0KPiBhcmd1bWVudCBhYm92ZSBjYW4gYmUganVzdGlmaWVkIGdpdmVuIHRo
YXQgZHJhZnQgdGl0bGUsIGFic3RyYWN0DQo+IGFuZCBldmVuIGZpbGVuYW1lIChhbmQgYWxzbyB0
aGUgY29udGVudDstKS4NCg0KW01lZF0gImJlbmVmaWNpYWwiIGlzIGRlcml2ZWQgZnJvbSB0aGUg
aW5pdGlhbCByZXF1ZXN0IHRoYXQgbW90aXZhdGVkIHRoaXMgZHJhZnQgKGV4Y2VycHQgZnJvbSB0
aGUgYWJzdHJhY3QpOg0KDQogICBBdCBJRVRGOTcsIGF0IGEgbWVldGluZyByZWdhcmRpbmcgdGhl
IFBhdGggTGF5ZXIgVURQIFN1YnN0cmF0ZSAoUExVUykNCiAgIHByb3RvY29sLCBhIHJlcXVlc3Qg
d2FzIG1hZGUgZm9yIGRvY3VtZW50YXRpb24gYWJvdXQgdGhlIGJlbmVmaXRzDQogICAgICAgICAg
ICAgXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl4NCiAgIHRoYXQgbWlnaHQgYmUgcHJvdmlkZWQgYnkgcGVybWl0dGluZyBtaWRkbGVib3hlcyB0
byBoYXZlIHNvbWUNCiAgIF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXl5eDQogICB2aXNpYmlsaXR5IHRvIHRyYW5zcG9ydC1sYXllciBp
bmZvcm1hdGlvbi4NCiAgIF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xg0KDQogV2hlbiB0aGUgYWJzdHJhY3QNCj4gc2F5cyAiVGhpcyBkb2N1bWVudCBzdW1tYXJpemVz
IGJlbmVmaXRzIiB0aGVuIEkgY2Fubm90IGludGVycHJldA0KPiB0aGF0IGFzIG90aGVyIHRoYW4g
YmVpbmcgaW50ZW5kZWQgdG8ganVzdGlmeSB0aGUgdXNlcyBkZXNjcmliZWQuDQoNCltNZWRdIEkg
d291bGQgcHJlZmVyIGlmIHdlIGNhbiBhdm9pZCB0byAiaW50ZXJwcmV0IiwgYnV0IHJhaXNlIHF1
ZXN0aW9ucyB0byB0aGUgYXV0aG9ycyBpZiB0aGVyZSBpcyBhIGRvdWJ0LiBUaGUgZG9jdW1lbnQg
ZG9lcyBub3QgcHJvdmlkZSBhIHJlY29tbWVuZGF0aW9uIG9yIGNsYWltcyB0aGlzIGlzIHRoZSBv
bmx5IHdheSB0byBhY2hpZXZlIHRoZSB0ZWNobmljYWwgZ29hbHMuIEl0IGRvZXMgb25seSByZWZs
ZWN0IHNvbWUgZGVwbG95bWVudCByZWFsaXR5IHRvZ2V0aGVyIHdpdGggc29tZSBtb3RpdmF0aW9u
cy4NCg0KPg0KPiBBIGZhaXJseSB0aG9yb3VnaCByZS13cml0ZSB0byBhaW0gdG8gZGVzY3JpYmUg
dGhlIHByb3MgYW5kIGNvbnMNCj4gd291bGQgYmUgYSBkaWZmZXJlbnQgYW5kIG1vcmUgdXNlZnVs
IGRvY3VtZW50Lg0KDQpbTWVkXSBUaGVyZSBhcmUgYWxyZWFkeSBtYW55IFJGQ3MgdGhhdCBkaXNj
dXNzIHRoZSBpc3N1ZXMvY29ucyAoSSBjYW4gY2l0ZSB0aGlzIFJGQyBJIGNvLWF1dGhvcmVkIGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MjY5IGZvciB0aGUgQ0dOIGNhc2UpLiBXaGF0
IGlzIG5lZWRlZCBJTUhPIGlzIHNvbWV0aGluZyBlbHNlOiB1bmRlcnN0YW5kIHRoZSByZXF1aXJl
bWVudHMgdGhhdCBsZWQgdG8gZGVwbG95IHNvbWUgb2YgdGhlc2UgZnVuY3Rpb25zLg0KDQogU2lt
aWxhcmx5IGEgZHJhZnQNCj4gdGhhdCBzdHJpdmVzIHRvIG5ldXRyYWxseSBkZXNjcmliZSBleGlz
dGluZyByZWFsaXR5IGNvdWxkIG1heWJlDQo+IGJlIHVzZWZ1bCAoKikNCg0KW01lZF0gVGhpcyBp
cyB0aGUgaW50ZW50IG9mIGRyYWZ0LWRvbHNvbi4NCg0KIGJ1dCBvbmUgdGhhdCBvbmx5IGRlc2Ny
aWJlcyBtaWRkbGVib3ggZnJpZW5kcyB3aXRoDQo+ICJiZW5lZml0cyIgaXMgbm90IElNTyBiZW5l
ZmljaWFsIDstKQ0KDQpbTWVkXSBUaGUgaW50ZW50IGlzIG5vdCB0byAic2VsbCBzb21ldGhpbmci
IGJ1dCB0byB1bmRlcnN0YW5kIHRoZSB0ZWNobmljYWwgbmVlZHMgc28gdGhhdCBob3BlZnVsbHkg
d2UgY2FuIGhhdmUgYSByZWZlcmVuY2UgZm9yIGZ1dHVyZSBzb2x1dGlvbi1vcmllbnRlZCBkaXNj
dXNzaW9ucy4NCklmIGEgZ2l2ZW4gZnVuY3Rpb24gY2FuIGJlIHByb3ZpZGVkIHdpdGhvdXQgaW52
b2x2aW5nIGFuIG9uLXBhdGggZGV2aWNlLCB0aGlzIHdvdWxkIGJlIGdyZWF0IGZvciBvcGVyYXRv
cnMgKG9wdGltaXplIENBUEVYL09QRVggaXMgb3VyIG1vdHRvKS4NCg0KPg0KPiBDaGVlcnMsDQo+
IFMuDQo+DQo+ICgqKSBUaGF0IGlzIHRoZSBhcmd1bWVudCBmb3IgZHJhZnQtbW0tZWZmZWN0LWVu
Y3J5cHQsIGZvciB3aGljaCBJDQo+IGRvIHN1cHBvcnQgcHVibGljYXRpb24gKGFwcGFyZW50bHkg
aW4gZGlzYWdyZWVtZW50IHdpdGggTWFydGluIGluDQo+IHRoYXQgY2FzZTotKQ0KPg0KPg0KPg0K
DQo=


From nobody Tue Apr 11 05:13:57 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6280D129A9E for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 05:13: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, 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 jqd4lZq4GomA for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 05:13:51 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 27B8F129AB3 for <ietf@ietf.org>; Tue, 11 Apr 2017 05:13:48 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id c45so86452272qtb.1 for <ietf@ietf.org>; Tue, 11 Apr 2017 05:13:48 -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 :content-transfer-encoding:message-id:references:to; bh=ORqTBHEwJnTtOGSrt1YuOUlq0K4Q2ESVr0VDySwBq6Y=; b=kfaMuV+NdCgyX18duuf1MeIEshWkBhnv3Uh2GqQ/656wK6+hbwAeq5SasvHvriHIsK Sq7Z+dseL303az3t0WB9iS6GknDjUKIPbp+zE0Xw77ygRU1ro6Oyhj9k4dAzLIHelPCW 3AoJ7gA6/3JULD5+BQsoVWYvjzjZ629XkuAAV4KQB5smWrozDX+vPhL+OJL5s3wiqFMI eEKj/bYCzQlikqSDkVw6e5erWLOxP9elZxu+i2mO6OayOQLKh9o1J18QfWiX+9gZfgY0 x3oPqYqlEIJe6RPr2lZ9XdMZllZTxcSfrvuTvMu0BKG6tnMTLyVwN/IcAe5aL4xf4YCj Aa+w==
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 :content-transfer-encoding:message-id:references:to; bh=ORqTBHEwJnTtOGSrt1YuOUlq0K4Q2ESVr0VDySwBq6Y=; b=cJR/jXoPEX6wXomViu3/7aE2VqFxKmMirdOtqgFE9ceOs9T2QVwPHJwFOPeNxhcmQD VfjGeUdlJPKsDgNDCnJ6RKbxupOuJut4Pp7K50Q/3fVKeG8rZZ9J1sx7xHPjPU0spohL WI3Lkjo2Pm9y+QZ2EyNaH43pXR10l8PgMqa+80ARWkQt0JsyFCz8GVkFyYZDQVCGI/6f V62WGHhQRIeAWawVCee+drkeD//nJ/3UVnRnuSPBu9X0CXMKgGaALFv2+353hlkYAa37 YQ2uFDiRXXnP70fK6hZMDiinhc07QAHkKKm4GmMsJ+zq40qEhuojbGQ7ahFczpDLXHlj 9Y0g==
X-Gm-Message-State: AN3rC/4Jicz2sn/Fbj7/BZZOZjOL4bdKqH8gQzAYY0oCk+dhA6TEGeWzouhT8Z8ExbwcuA==
X-Received: by 10.200.4.44 with SMTP id v44mr16066577qtg.135.1491912825175; Tue, 11 Apr 2017 05:13:45 -0700 (PDT)
Received: from [192.168.1.13] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id h23sm10883146qtc.49.2017.04.11.05.13.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 05:13:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
Date: Tue, 11 Apr 2017 08:13:43 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C5D3A94-1888-4927-B701-BF6F7DF1B585@gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HFWtosJfLL9N0tZEQrlG6szvg7A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 12:13:55 -0000

I received a correction...

Sent from my iPhone

> On Apr 10, 2017, at 11:54 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gm=
ail.com> wrote:
>=20
> Hi Martin,
>=20
> We went through your comments one more time to make sure any
> technical/substantive comments are addressed.  Please see the
> discussion inline.
>=20
>=20
> On Mon, Apr 10, 2017 at 5:05 PM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
>> I most certainly reviewed 09. I haven't reviewed the diff. I doubt that i=
t
>> would change my opinion on the macro - level problems.
>=20
> My mistake, I thought the acronym you corrected was in version 9.
>=20
>>=20
>> On 8 Apr. 2017 3:34 am, "Kathleen Moriarty"
>> <kathleen.moriarty.ietf@gmail.com> wrote:
>>=20
>> Hello Martin,
>>=20
>> Thanks for your review.  It seems that you have read version 8 or
>> earlier and not the current version, 9, from some of your suggestions
>> that have been corrected already.  Your review also reads to me that
>> additional context setting may help, but please note that some context
>> setting was improved in version 9.  We re-arranged some of the
>> sections per IESG review recommendations in the latest version as
>> well.
>>=20
>> Perhaps you have additional language suggestions for context setting?
>>=20
>> The abstract states:
>>=20
>>   Increased use of encryption impacts operations for security and
>>   network management causing a shift in how these functions are
>>   performed.  In some cases, new methods to both monitor and protect
>>   data will evolve.  In other cases, the ability to monitor and
>>   troubleshoot could be eliminated.  This draft includes a collection
>>   of current security and network management functions that may be
>>   impacted by the shift to increased use of encryption.  This draft
>>   does not attempt to solve these problems, but rather document the
>>   current state to assist in the development of alternate options to
>>   achieve the intended purpose of the documented practices.
>>=20
>> which is repeated again in the introduction, but slightly reworded.
>> The introduction also includes statements on the existing publications
>> related to encryption and I read them as not having any bias, but
>> rather supporting the existing documents that also had consensus.
>>=20
>> A couple of comments and one question inline.
>>=20
>> On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson
>> <martin.thomson@gmail.com> wrote:
>>> Draft: draft-mm-wg-effect-encrypt-09
>>> Date: 2017-04-07
>>>=20
>>> Overall
>>>=20
>>> This document is unfocused and unclear in its intent.  It is filled with=

>>> unsubstantiated claims, misleading statements, bias, and implied
>>> recommendations
>>> for bad practices.  I would oppose its publication in the current form.
>>> Furthermore, I don't believe that small scale or editorial changes would=

>>> be
>>> sufficient to correct these problems.
>>>=20
>>>=20
>>> Aside from weakening its utility and/or arguments, the lack of focus wil=
l
>>> allow
>>> this document to be abused in various ways.  For instance, it might impl=
y
>>> IETF
>>> endorsement of the practices described in the document.  Given that the
>>> IETF has
>>> published positions that in some cases reject these practices, this
>>> document
>>> needs to be very precise with its claims.  In its current form, it is no=
t
>>> nearly
>>> careful enough.
>=20
> This paragraph is all speculation about an unfortunate future.
> We could speculate that the operator, security and app communities
> come together to work out solutions after reading this doc,
> which is part of our intent.
>=20
>>>=20
>>> If this document is going to be published as an RFC, then it needs to be=

>>> very
>>> clear about its intent and its position - or lack thereof - toward these=

>>> practices.  It might be possible to say that these practices were employ=
ed
>>> in
>>> networks in the past and that encryption is reducing the viability of
>>> those
>>> practices.  A value-neutral statement like that might be acceptable as
>>> long as
>>> it were framed carefully.
>=20
> The document conveys that message everywhere. The words contributed were
> changed in many places to remove any implication that the current practice=
s
> are "requirements" or even "needs".
>=20
> The abstract and introduction contain value neutral statements like
> what you are suggesting already.  We actually say the practices may be
> eliminated, going further than your request as that may be the case.
>=20
> The only change I could see in the abstract would be the following:
>=20
>   Increased use of encryption impacts operations for security and
>   network management causing a shift in how these functions are
>   performed.  In some cases, new methods to both monitor and protect
>   data will evolve.  In other cases, the ability to monitor and
>   troubleshoot could be eliminated.  This draft includes a collection
>   of current security and network management functions that may be
>   impacted by the shift to increased use of encryption and encryption
> that is designed prevent interception.  This draft
>   does not attempt to solve these problems, but rather document the
>   current state to assist in the development of alternate options to
>   achieve the intended purpose of the documented practices when possible.
>=20
> Do you have additional suggestions?  Or is the phrasing read
> differently than we intended by stating functions may be eliminated?
> We thought that was very clear to your points.
>=20
>>>=20
>>> What is problematic is the implicit argument that is presented.  This
>>> document
>>> could easily be construed as the IETF legitimizing these practices.  Thi=
s
>>> includes things on which the IETF has published statements (see for
>>> example RFC
>>> 2804).
>>=20
>> See the abstract and introduction and summary.
>>=20
>>>=20
>>> This steps firmly into to sticky mess that is the politics of encryption=

>>> policy.
>>> If the IETF is going to make a political statement with this document,
>>> then that
>>> statement needs to be a lot better than this.
>=20
> The intent of this document is to help operators as these changes
> continue.  It is to make sure we are not ignoring the impact of the
> changes the IETF has with our decision (which are supported in this
> document).  This document is intended to assist operators.  By
> explaining the functions being performed, some have already been
> provided alternate methods to achieve their goals.  We have also
> received quite a bit of positive feedback from operators - that this
> document helped them come back to the discussion and to approach a
> world with more encryption or sessions that can't be intercepted (TLS
> 1.3, TCPinc, QUIC, etc.).
>=20
>>>=20
>>> Furthermore, any statement needs to be consistent with previous
>>> statements,
>>> where in this case that primarily means RFC 7258.  Right now it reads as=

>>> an
>>> attempt to dilute RFC 7258.
>>=20
>> Not at all.
>=20
> It does not read that way to many people who strongly support RFC
> 7258, including Stephen who was our sponsoring AD (and was for 7258).

Stephen was the co-author.  I should have checked that, but it was late when=
 I hit send.

Kathleen=20
> Can you give specific sections where it sounds like we are weakening
> RFC 7258 so we can change that specific wording?
>=20
>>=20
>>>=20
>>> If this document were more clearly formulated as an even-handed treatmen=
t
>>> of
>>> what happens today - without judgment - then it could be useful.  Here t=
he
>>> model
>>> of RFC 7754 is a good one.  It describes the different facets of a use
>>> case,
>>> then the different practices that might be employed to achieve that goal=
.
>>> For
>>> each practice the pros, cons, and technical limitations are covered with=

>>> an eye
>>> to all involved parties.
>>>=20
>=20
> Version 8 to 9 had some edits to remove statements with used terms
> like 'need'.  We may have missed a couple, we'll check the ones you
> pointed out.  There are also numerous statements that are explicitly
> in support of RFC7258.  These are in the abstract, introduction,
> summary and sprinkled throughout the document.
>=20
> Apparently, RFC 7754 goes further than our scope. We are not describing:
> "... the different practices that might be employed to achieve that goal."=

>=20
>>>=20
>>> The Real Purpose of this Document
>>>=20
>>> I think that this is the real question that this document wants to ask i=
s:
>>>=20
>>>   In a world where we are forced to defend against pervasive monitoring
>>> by
>>>   motivated and malicious actors, can we find a role for less pervasive
>>>   monitoring by well-intentioned entities?
>=20
> The document aims to help operators by giving them a chance to discuss
> the impact.  It opens the
> door to conversation so they can find new ways to achieve the same
> goals (better performance for customers for instance or monitoring
> services that have been requested - web content, DLP), which may mean
> endpoint solutions are needed or filtering limited to hostnames for
> now until other mechanisms are developed (likely at the application
> layer).
>=20
> For enterprises, application and host level solutions are
> fine as many organizations have employees sign away their rights to
> privacy.  I would never check FaceBook from work for instance or
> access any site of a personal nature.  This is why we broke out the
> sections by the type of network or SP, their options are different
> with and without encryption.
>=20
> QUESTION: Would it help to add some text like the first paragraph into
> the introduction?  - This document aims to...
>=20
>>>=20
>>> There is an interesting discussion to be had here, but I'm convinced aft=
er
>>> my
>>> review that this document is the wrong vehicle for that discussion.
>=20
> RFCs are the vehicles the IETF has found most useful in talking to the wor=
ld.
>=20
>>> I'm
>>> also
>>> inclined to suggest that this is the wrong question to ask in the first
>>> place.
>=20
> We can't ignore the problems resulting from the changes, we the IETF
> make, to improve privacy and security.  While we agree it is a positive
> thing to improve these functions, we (the IETF) should also help with
> the wake we
> leave in our path.  Otherwise, we can't expect people to play along
> with the protocol specifications the IETF publishes.
>=20
> It's much more than an "interesting discussion" to many operators.
> Some are required by law to use these practices to protect privacy.
>=20
> There are many questions to ask, some of which have already been
> answered. For example, RFC 7258 asked 'How can we deal with
> pervasive monitoring' and answered it through the same IETF
> consensus process this document has already gone through.
>=20
>>>=20
>>> To the extent that we have the tools necessary to protect against
>>> pervasive
>>> monitoring, we have to accept that more-legitimate uses of monitoring ar=
e
>>> collateral.  Mostly, that's just a function of the limitations of the
>>> imperfect
>>> tools we have.
>>>=20
>>> The value in this document is in the rather comprehensive collection of
>>> use
>>> cases.  Sure, some we might not attribute much weight to, like
>>> wiretapping.
>>> Others are frankly frightening and not just in the Orwellian sense.
>>>=20
>>> The problems that are implied by the current practices of network
>>> operators is a
>>> large vein of unexplored work for the community.  Spending effort on
>>> finding
>>> better solutions to legitimate problems is worthwhile.
>=20
> Right, so we started by documenting them *before* the collateral damage ap=
pears.
>=20
>>>=20
>>> In other words, the right question might be:
>>>=20
>>>   For each of these practices that we see today, are the use cases that
>>>   motivate them legitimate and how might be implement alternative
>>> techniques
>>>   that properly respect privacy and security?
>>>=20
>=20
> Yes, this is the point of the document and it's stated in several places.
>=20
>>>=20
>>> Two- and Three- Party Interactions
>>>=20
>>> A great many sections of the document are unclear about the relationship=
s
>>> between different actors.  It seems like many of the activities describe=
,
>>> which
>>> are presented here as being beneficial, are performed by a third party
>>> without
>>> the consent or involvement of the two communicating peers.  After all,
>>> those are
>>> the cases where encryption most often interferes.
>>>=20
>=20
> As the draft says, some of the methods will be eliminated.
>=20
>>> The assertion that some benefit is accrued to communicating peers as a
>>> result of
>>> these actions is the constant subject of the text.  I observe that in mo=
st
>>> of
>>> the cases listed in this document, the benefit is accrued primarily to t=
he
>>> third
>>> party.
>=20
> Operators by their nature have different privacy concerns than their end
> users. Operators by their nature want to accrue benefits. This document
> doesn't change the balance; instead, it tells them how to deal with privac=
y
> that has already been applied.  While we agree with your statement and thi=
nk
> it's important to build privacy and privacy options into IETF protocols,
> operators often don't care, despite the many RFCs we have published
> telling them that they should care. We still need to engage them so we can=

> have this discussion.
>=20
> The "third party" is likely the only one receiving a trouble call,
> and there is benefit for all parties when the trouble is cleared.
>=20
>>>=20
>>> Clarity around the arguments that the document makes with respect to
>>> benefits to
>>> each of the involved parties is sorely lacking.
>>>=20
>>> In addition to this, where benefits truly do accrue to communicating
>>> peers,
>>> technical options that don't rely on privacy-invasive techniques are
>>> routinely
>>> dismissed in an offhand fashion.  In this way, any moral imprimatur
>>> attributed
>>> to the use case is used to justify the privacy-invasive method.
>>>=20
>=20
> Without specific comments, the above are all subjective statements and
> we have responded to them.
>=20
>>>=20
>>> Document Structure
>>>=20
>>> This document is very hard to read (and review).  Probably my biggest
>>> complaint
>>> is that the sections are haphazardly organized.  They contain a mixture o=
f
>>> use
>>> cases (what does SP X want to do) and techniques (how do they do these
>>> things).
>>> Material is duplicated between sections.  Sections cover 10 different us=
e
>>> cases
>>> while talking about techniques, then other sections talk about different=

>>> techniques whiles talking about a scenario.  This leads to a lot of
>>> repetition.
>>>=20
>>> There are three axes that this document contemplates:
>>>=20
>>> - the techniques that are currently used in networks
>>> - the use cases that motivate these techniques
>>> - the deployment scenarios in which these use cases manifest
>>>=20
>>> It would appear that the document attemps to start from the deployment
>>> scenarios.  However, this causes use cases and techniques to be mixed.
>>> Judicious use of cross-referencing might have made this arrangement
>>> tractable,
>>> but there are virtually no cross references.
>>>=20
>=20
> The above is stylistic in nature.  We've already made changes to the
> format to address specific comments in IESG review. A complete
> re-write is not appropriate at this point in the draft lifecycle.
> That's not the point of IESG review.
>=20
>>>=20
>>> Section 1
>>>=20
>>> I find the introduction of this document difficult to parse.  I think th=
at
>>> what
>>> it wants to say is pretty straightforward, but it manages this in quite a=
n
>>> obtuse way.  Here's what I think that it is trying to say:
>>>=20
>>> 1. The IETF (and the larger community) has reacted to revelations of
>>> pervasive
>>>   monitoring by increasing the use of encryption.
>>> 2. That has been somewhat successful.
>>> 3. More encryption has an impact on some practices that network operator=
s
>>> have
>>>   become accustomed to employing.
>>>=20
>>> Expressed in this way, you can see how you could make a value-neutral
>>> statement.
>>>=20
>>> On the first, you can definitely make an argument based on the documents=

>>> that
>>> the IETF have published.  However, it is a mistake here in assuming that=

>>> the
>>> IETF - or the revelations of global-scale surveillance - is directly
>>> responsible
>>> for the uptick in adoption of cryptographic protection for Internet
>>> traffic.
>=20
> The abstract is value neutral right now.
>=20
> The increase or changes are not just about PM.  We are making
> TLS 1.3 so that it cannot be intercepted (I agree with this move of
> course as we should make our protocols strong and adhere to
> established IETF principles)?  Or the efforts of TCPInc and
> QUIC?  We do directly affect the use of encryption and the types of
> encryption that are deployed.  We work with the vendor communities in
> publishing deprecation drafts as well.  All of these efforts got
> additional energy from the PM work and that's a good thing.  Events
> trigger increases in security and it's fine to acknowledge that.  The
> introduction states:
>=20
>   In response to pervasive monitoring revelations and the IETF
>   consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
>   are underway to increase encryption of Internet traffic.  Session
>   encryption helps to prevent both passive and active attacks on
>   transport protocols;
>=20
> We could change it to say:
>=20
>   In response to pervasive monitoring revelations and the IETF
>   consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
>   are underway to improve and increase encryption of Internet traffic.  Se=
ssion
>   encryption helps to prevent both passive and active attacks on
>   transport protocols;
>=20
> The second sentence mentions passive and active attacks here as that
> hits on the prevention of active attacks - improving session
> encryption protocols helps with this.
>=20
>>> This is something that the community as a whole has been working towards=

>>> for
>>> many years; these trends predate the actions this draft focuses on.  Thi=
s
>>> is
>>> particularly true for the hosted provider cases in Section 3, where
>>> business
>>> motivations for protection are far stronger than any concerns over
>>> government
>>> surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I=

>>> don't
>>> have to write a statement that will be labelled as having IETF consensus=
.
>=20
> Section 3 already makes this point very clear (full text for the intro
> to that section):
>=20
> 3.  Encryption in Hosting SP Environments
>=20
>   Hosted environments have had varied requirements in the past for
>   encryption, with many businesses choosing to use these services
>   primarily for data and applications that are not business or privacy
>   sensitive.  A shift prior to the revelations on surveillance/passive
>   monitoring began where businesses were asking for hosted environments
>   to provide higher levels of security so that additional applications
>   and service could be hosted externally.  Businesses understanding the
>   threats of monitoring in hosted environments only increased that
>   pressure to provide more secure access and session encryption to
>   protect the management of hosted environments as well as for the data
>   and applications.
>=20
>>>=20
>>> The immediate focus on opportunistic security is highly misleading,
>>> especially
>>> in the web case.  The amount of opportunistically secured web traffic is=

>>> miniscule by global standards.  Since Firefox is the only browser to
>>> support OS
>>> for the web, so adjust the following by market share:
>>> <https://mzl.la/2oc46ch>.
>=20
> You'll need to cite text that is leading you to this conclusion as I
> don't read it as being specific to OS, rather that OS is explained so
> operators understand it in the mix of encryption options.
>=20
>>>=20
>>> I understand that mail is more often opportunistically secured, and you
>>> will
>>> hear the virtues of OS sung from the rooftops, but all evidence suggests=

>>> that
>>> this is just a transitory state.  Instant messaging is closer to the web=

>>> case,
>>> with the trend toward strong protections that include authentication.  O=
f
>>> course, I don't believe that mail or instant messaging represent any
>>> significant
>>> traffic volume, so you need to be very careful about the nature of the
>>> claims
>>> that are being made.  It has to be that the volume of mail has to be a
>>> rounding
>>> error when it comes to capacity planning for networks.
>>>=20
>>> On the second point, when making claims about prevalence of encryption, I=

>>> would
>>> advise caution when citing statistics.  Here's the graph for the Mozilla=

>>> figures
>>> that I think are being cited <https://mzl.la/2obZjrb>. Here's a differen=
t
>>> graph
>>> with a different number <https://mzl.la/2oc263J>.  This highlights the
>>> point
>>> that statistics need to be carefully cited, because bare claims are
>>> difficult to
>>> assess.  Methodology matters when it comes to these sorts of claims - ar=
e
>>> we
>>> talking proportions of packets, requests, flows, or something else?
>>> Furthermore, the citations in the document are made more difficult to
>>> assess by
>>> being measured at very different times (where the two I cite here were
>>> made at
>>> roughly the same point in time).
>>=20
>> For the Mozilla statistics, Richard Barnes had reviewed the text after
>> providing the statistic as he wanted to make sure it was stated
>> clearly raising the same concerns you do about statistics.  Do you
>> have further text suggestions to clarify this statistic?
>>=20
>=20
>>=20
>>>=20
>>> The statistics do support the notion that there is a significant amount o=
f
>>> encryption in use, but it would appear that the claim is that the amount=

>>> of
>>> encryption is *increasing*.  This is not an extraordinary claim, but no
>>> evidence
>>> is offered in support of the claim.  It isn't a certain thing either.
>>> =46rom the
>>> statistics that I have access to, there was a definite uptick in October=

>>> of
>>> 2015, but the rate appears to be stable since then.
>>>=20
>>> It appears that the remainder of the document is intended to address the=

>>> third
>>> of my points in some detail.  That's a good structure in theory, but see=

>>> above.
>>>=20
>>> I don't think that the "service provider" taxonomy works for this
>>> document.
>>> Based solely on the structure of the document, the only service provider=

>>> that
>>> this document concerns itself with is the one who forwards the packets.
>>> That
>>> application service providers are involved as one of the endpoints is
>>> relevant
>>> in some cases, but not all.  For that reason, I prefer "network operator=
"
>>> and to
>>> use specific terms like "mail host" or "web server" as appropriate to th=
e
>>> context.
>>>=20
>=20
> Those are subjective comments, so we'll put those aside.
>=20
>>>=20
>>> Section 2 (top section)
>>>=20
>>> I like that the attacks on SMTP by network operators is highlighted here=
.
>=20
> We tried to have balance and had other attacks by operators in
> previous versions, but only articles that are not stable references
> for them and were asked to remove them in AD review.
>=20
>>>=20
>>> There's an implicit argument here that runs counter to established IETF
>>> consensus.
>>>=20
>>>   Some methods used by service providers are impacted by the use of
>>> encryption
>>>   where middle boxes were in use to perform functions that range from
>>> load
>>>   balancing techniques to monitoring for attacks or enabling "lawful
>>>   intercept", such that described in [ETSI101331] and [CALEA] in the US.=

>>>=20
>>> This fails to remain neutral.
>=20
> The functions are impacted, so how would you suggest we word this
> text?  It doesn't endorse the functions, just says they are impacted.
> We are open to suggested text.  Similar to how we describe 'attacks'
> by operators to break encryption or use RSA private keys.  We do have
> text in both directions on this and your review is complimentary of
> the ones that fit your dialog, but are also not value neutral.  Mind
> you, I am constantly reviewing RFCs and making sure TLS best practices
> are considered and questioning the use of deprecated crypto or not-yet
> but should be deprecated crypto.
>=20
>>> This implicitly makes a value-judgment
>>> about
>>> relative morality/acceptability/value of certain practices.
>=20
> We have statements in both directions in the document as you point out
> above with one of them.
>=20
>>> What is
>>> particularly insidious about this particular form is that it invites
>>> interpretation that is subjectively coloured.  For instance, as a non-EU=

>>> and
>>> non-US citizen, I might consider the use of the particular lawful
>>> intercept
>>> techniques offensive; thus I might interpret this as a spectrum between
>>> inoffensive to offensive.  An employee of the US government might view
>>> this
>>> somewhat differently and interpret this as a scale between low-value to
>>> high-value.  I'm guessing here, but this is really just to highlight my
>>> point
>>> about care.
>>>=20
>>> A more serious concern is this statement:
>>>=20
>>>   The loss of access to these fields may prompt undesirable security
>>> practices
>>>   in order to gain access to the fields in unencrypted data flows.
>>>=20
>=20
> But this is true and we've seen operators do things like prevent
> STARTTLS.  This isn't a good thing and we need to ack that this has
> happened.  We need to help operators figure out how they help users in
> new ways and understand that some of the functions they perform
> currently (TLS 1.2) won't work in the future.
>=20
> This text got re-worded during AD review, I believe.  The intent is to
> say that this is not good - the practices are called out as
> undesirable.  How would you suggest it be re-phrased and we can check
> back with Stephen to see if he agrees.
>=20
>>> I've read this argument before (see
>>> https://queue.acm.org/detail.cfm?id=3D2508864
>>> for the long form), and it might even have an element of truth to it.
>>> However,
>>> it's not a statement that I personally attribute any real credibility to=
,
>>> and
>>> nor do I think that it needs to be credited with any amount of
>>> seriousness.  I
>>> certainly disagree with the IETF making any such statement.  It says tha=
t
>>> we are
>>> collectively willing to bow in response to (anticipated) threats of
>>> violence.
>=20
> Prior to AD review, there was a reference in the text to the practices
> being bad and stating that regulators and the media helped to correct
> this behavior.  The problem here may be the evolution of the
> text and lack of reference now since we couldn't find a stable
> reference.  Do you have a wording suggestion?
>=20
>>>=20
>>> Section 2.1
>>>=20
>>> This is one of the few sections that talk about what it means to operate=
 a
>>> service as opposed to operate a network.
>>>=20
>>> Overall, this section doesn't work particularly well.  The distinction
>>> between
>>> integrated and standalone load balancing is an interesting division, but=

>>> it
>>> doesn't leverage this distinction well.  What causes a standalone
>>> load-balancer
>>> to be necessary?  Is this something a network operator uses?  I see text=

>>> on NFV
>>> later, but it's far removed from the original text and it seems
>>> aspirational
>>> rather than concrete.  On the other hand, many of the concerns in this
>>> document
>>> simply don't apply to an integrated load balancer.
>>>=20
>>> The amount of text on QUIC here is surprising.  Given how much of QUIC i=
s
>>> changing right now, we shouldn't publish a document that attempts to mak=
e
>>> claims
>>> about what QUIC is or how it is operated.  This attempts to dive into th=
e
>>> details of QUIC connection migration in a way that presumes much about t=
he
>>> outcome of issues that the QUIC working group is still struggling with.
>>>=20
>>> I would strongly recommend removing QUIC-specific language from this
>>> section and
>>> the document as a whole.  We have an operational document in the QUIC
>>> working
>>> group that would be a good venue to discuss some of these concerns.
>=20
> While we read this as  more of a substantive remark, the text on
> load balancers and QUIC were added per Mirja's IESG review.  We would
> need to check with her about making any changes here.  They were
> specific additions that were requested.
>=20
> Further, it is only IETF QUIC that is in active development.
> Google QUIC (referred to as GQUIC in IETF discussions) is a more
> stable experiment now.
>=20
>>>=20
>>> Is this an oblique reference to (the much-loved) RFC 7974?
>>>=20
>>>   Current protocols, such as TCP, allow the development of stateless
>>> integrated
>>>   load balancers by availing such load balancers of additional plain tex=
t
>>>   information in client-to-server packets.
>>>=20
>>> Otherwise, I don't know what it means.
>>>=20
>>> BTW, I like this parenthetical:
>>>=20
>>>   (That said, care must be exercised to make sure that the information
>>> encoded
>>>   by the endpoints is not sufficient to identify unique flows and
>>> facilitate
>>>   Persistent Surveillance attack vector.)
>>>=20
>>> I'm going to take this to the QUIC working group, because QUIC certainly=

>>> doesn't
>>> meet that bar right now.  It fully facilitates Persistent Surveillance i=
n
>>> its
>>> current form (proper noun?  I haven't really seen that term before, even=

>>> though
>>> it draws a neat parallel with Pervasive Surveillance).
>>>=20
>=20
> OK, let us know what you hear back.  These changes were in response to
> the sponsoring AD's request of that work.
>=20
>>> Editorial:
>>> * "pop" is a term of art that needs explanation.
>>> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - the=

>>>  possessive form for the inanimate.
>>> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>=20
> Thanks for the nit corrections.
>=20
>>>=20
>>> Section 2.2
>>>=20
>>> I think that this sums the situation up reasonably well.  It fails the
>>> value-neutral test in a few ways though.  As I understand the situation,=

>>> surveying operates at many levels.  For accurate planning, models of
>>> endpoint
>>> behaviour are used to determine things like whether loss or congestion i=
s
>>> affecting throughput.  Really good models require knowledge of what user=
s
>>> are
>>> attempting to do and the applications they are using (as mentioned, thin=
gs
>>> like
>>> browser version matter in these models).  For instance, it isn't enough t=
o
>>> understand that the user is trying to receive 720p video, you also have t=
o
>>> know
>>> that a 4k stream for the same content is available.
>=20
> Sure, that's why we broke the draft down by operator type.  Some
> functions are shifting and the responsibilities for operators will
> shift with these changes.
>=20
>>>=20
>>> The degree to which these models are privacy-invasive is not even
>>> acknowledged.
>=20
> Suggest text please.  The abstract and intro were meant to set the
> context for the document.  Some of the functions will be eliminated -
> and that's fine, it is what it is, but operators need to adapt and
> deal with the change.  We should help them so we all get to a better
> place with improved privacy for users and increased security.  By not
> helping them, we do not get closer to solving these problems.
>=20
> Try to consider the operators perspective here. They are used to knowing
> what SI has been exposed by knowing video format
> or browser type that has been in the clear for years.  Understanding
> the practices
> helps make it possible for apps/ops/security/transport to come together to=

> reach better solutions.
>=20
>>>=20
>>> Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect=

>>> that
>>> subtlety to be lost on many readers though.
>>>=20
>>> Section 2.3.1
>>>=20
>>> I find this sad, even if I can recognize the truth of it:
>>>=20
>>>   A monitoring system could easily identify a specific browser,
>>>   and by correlating other information, identify a specific user.
>>>=20
>>> As a browser vendor, we don't consider this to be a feature, it's a bug.=

>>>=20
>>> Section 2.3.2.1
>>>=20
>>> This is a strange section under which to put caching.  Caching is a use
>>> case
>>> akin to compression.  I don't see it as belonging to the class of things=

>>> that
>>> rely on DPI.  You just intermediate the cleartext HTTP in the way that R=
FC
>>> 7230
>>> recognizes.  Note that RFC 7230 explicitly does not endorse the practice=

>>> of
>>> transparent proxying for a range of reasons, not the least of which is t=
he
>>> complete lack of transparency (yep).
>=20
>=20
> This was organized per IESG review.
>=20
>>>=20
>>> Section 2.3.2.2
>>>=20
>>> Again, it's strange to see differential treatment under DPI.  I was fair=
ly
>>> sure
>>> that fingerprinting was used here as well.
>>>=20
>>> Section 2.4
>>>=20
>>> This section doesn't even attempt to recognize that applications are muc=
h
>>> better
>>> now at scaling content to suit the device on which that content is
>>> intended to
>>> be consumed.  It should.
>=20
> The reason for that is that there has been a useful dialog between applica=
tion
> designers and network providers over time, beginning with app designers
> saying "what do you mean the network has errors and delay? this works
> fine in my lab...".  The contributors viewed that as well understood
> and far back
> in time, so not necessary to mention.
>=20
> If you think there should be text to this point, please suggest some.
>=20
>>>=20
>>> This section should not represent compression as an unmitigated good.  I=
'm
>>> told
>>> that significant damage can be done to video streams by "well-intentione=
d"
>>> compression middleboxes.
>=20
> Please suggest text.
>=20
>>>=20
>>> Yet again I see a call back to the implicit threat of violence in "they
>>> will
>>> adopt undesirable security practices".  Statements in that form have no
>>> place in
>>> IETF RFCs.
>=20
> This was edited text per review and agreed upon (I think in the AD
> review).  Suggest alternate
> text and we'll go back to the other person.
>=20
>>>=20
>>> Section 2.5
>>>=20
>>> This mentions RFC 7754 then blithely ignores its primary conclusion.
>>> Generally,
>>> The treatment in RFC 7754 of this subject is more even-handed.
>>>=20
>>> The use of particular examples (betting, gambling, dating) shows cultura=
l
>>> bias.
>=20
> subjective review again, but 7754 cites examples too.
>=20
>>>=20
>>> Jargon warning: "core network", "the mobile network" ("the"?)
>>>=20
>>> Section 2.5.2
>>>=20
>>>   This type of granular filtering could occur at the endpoint, however
>>> the
>>>   ability to efficiently provide this as a service without new efficient=

>>>   management solutions for end point solutions impacts providers.
>>>=20
>>> The initial premise here (up to the first comma) is the conclusion of RFC=

>>> 7754.
>>> I disagree with the conclusion, and I suspect so does RFC 7754.  In
>>> scenarios
>>> where this matters, endpoints are routinely managed centrally.  The rang=
e
>>> of
>>> options for this sort of management are plentiful and diverse.
>=20
> Sure, but there is an impact and it's okay to ack that and assist with
> these alternate options.  If you have text to suggest, please do so.
>=20
>>>=20
>>> Section 2.5.3
>>>=20
>>> This describes a captive portal, which in the case where the service
>>> provider
>>> has a relationship with their customers, seems like a poor solution.  Se=
e
>>> the
>>> CAPPORT working group for ways in which people are actually working on a=

>>> solution to this problem.
>>>=20
>>> Section 2.6
>>>=20
>>> The capitalization of section headings is inconsistent here (and
>>> throughout).
>>>=20
>>> Section 2.6.1
>>>=20
>>> Isn't this a duplicate of Section 2.1?
>>>=20
>>> Section 2.6.2
>>>=20
>>> I can't parse this statement:
>>>=20
>>>   Approved access to a network is a prerequisite to requests for Interne=
t
>>>   traffic - hence network access, including any authentication and
>>>   authorization, is not impacted by encryption.
>>>=20
>>> And then we get into zero rating, which is a hot-button topic.  No
>>> acknowledgment given to the sensitivities on the subject, or even a
>>> superficial
>>> exploration of the technical options that are available.
>=20
> Please suggest text.  This was updated in IESG review.
>=20
>>>=20
>>> This text references a non-existent Appendix.
>=20
>=20
> Fixed. It's section 7 now.
>=20
>>>=20
>>> Section 2.6.5
>>>=20
>>> This paragraph is strange.  It starts by describing what appears to be u=
se
>>> cases
>>> (are those scare quotes?).  It finishes by implying that these are attac=
ks
>>> on
>>> privacy (which they are).
>>>=20
>>> What is "Non-Customer Proprietary Network Information"?  I hope that thi=
s
>>> isn't
>>> an attempt to somehow privilege the information so that it seems less th=
an
>>> privacy-invasive.
>>>=20
>>> Section 2.7
>>>=20
>>> This is one of the areas that is most legitimately affected by increased=

>>> adoption of encryption.  I have no doubt that having detailed informatio=
n
>>> about
>>> the application and its use makes the process of troubleshooting easier.=

>>>=20
>>> This is the first mention in the document of network-based optimization.=

>>> Was
>>> the section describing that cut from an earlier draft?
>>>=20
>>> The use of websockets as a primary example is an odd one.  It's just not=

>>> that
>>> common.  For reference, we see >20% failure rates on encrypted websocket=
s
>>> and
>>>> 50% failures in the clear; no one in their right mind would rely on
>>>> websockets.
>>> If the point is that HTTP is carrying more traffic (see
>>> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
>>> just that
>>> would be more effective.
>=20
> "in their right mind" . That isn't helpful.  Operators submitted text
> to explain what they are doing and how it's impacted.  How about
> proposing text to help in that vein.
>=20
>>>=20
>>> Section 3
>>>=20
>>> It would help if "hosted environments" was defined before diving in.
>>>=20
>>> Section 3.1
>>>=20
>>> The paragraph on DLP is ironically amusing.  Encryption exists to preven=
t
>>> private information leakage, but the assertion here is that encryption i=
s
>>> hampering DLP attempts.
>>>=20
>>> It's true that protection of intellectual property is an important
>>> business
>>> goal, but this handling suggests an architecture that I'm fairly sure is=

>>> counter
>>> to established wisdom (see "SSL added and removed here :-)":
>>>=20
>>> https://www.washingtonpost.com/rf/image_404h/2010-2019/WashingtonPost/20=
13/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg).
>>> Worse, this casually dismisses a model that is actually more likely to
>>> work.
>>> Malware encrypts too (https://arxiv.org/abs/1607.01639).
>=20
> The section talks about the end points being the better place for this alr=
eady.
>=20
>>>=20
>>> Section 3.1.1
>>>=20
>>> Who is the customer here?
>>>=20
>>> Why does the hosting provider need to monitor access?  They have the
>>> ability to
>>> limit accesses, but this is suggesting that what happens within the
>>> envelope of
>>> what they permit is important for them to know.  I'd be surprised if you=

>>> could
>>> show that this is true.  Hosting providers - in my experience - value
>>> their
>>> ongoing business and would not jeapardize it by snooping on their
>>> customers.
>>> It's different if the customer opts in to a security service, but that
>>> demonstrates a cooperative situation, where the rest of this document is=

>>> largely
>>> concerned with adversarial uses of encryption.
>=20
> This is describing the cooperative scenario.  The service is hosted,
> so maybe the definition of hosted would have helped you.
>=20
>>>=20
>>> Section 3.1.2
>>>=20
>>> This is another example where the organization of the document could
>>> be improved.
>>>=20
>>> Again with the "SSL added and removed here :-)" recommendation.  PCI don=
't
>>> permit that for good reason.
>=20
> I don't read the following text in this section as a recommendation or
> endorsement.  Is there a tweak you think that should be made as I'm
> not seeing the problem your describing. This is just describing what
> they do and stating that it will be impacted and then the truth that
> the functions may no longer be possible - not stating that it is good
> or bad, just the fact that it won't be possible.
>=20
>   The use of tools that
>   perform SSL/TLS decryption are impacted by the increased use of
>   encryption that prevents interception.  Alternate methods to acheive
>   the goals of these functions may be necessary and in some cases, the
>   functions may no longer persist in a pervasively encrypted Internet.
>=20
>>>=20
>>> Section 3.2.1
>>>=20
>>> I don't believe that monitoring of these types of application require
>>> cleartext
>>> access.  There are two parties involved: the provider of the application=

>>> and the
>>> user of it.  The provider has most of the power here and can theoretical=
ly
>>> design the system to allow whatever level of access they require.  To th=
e
>>> extent
>>> that the user needs protection from the application provider, that is a
>>> matter
>>> of negotiation between them.
>>>=20
>>> I don't see how the adversarial three-party situation presented in the
>>> rest of
>>> the document applies in this situation.
>=20
> Sure, there is a shift in how many functions will be performed
> happening and this is documenting that shift.  Much moves to the
> application.  We are helping to document the changes.
>=20
>>>=20
>>> Section 3.2.2
>>>=20
>>> No real mention of the effect of encryption here, or is this just saying=

>>> that
>>> there is no issue here?
>>>=20
>>> I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of t=
he
>>> IETF
>>> saying things like "PGP may be a front runner" though.
>>>=20
>=20
> This was added per EKR in IESG review.
>=20
>>> Section 3.3
>>>=20
>>> There's certainly a lot of detail here, but I had a really hard time
>>> extracting
>>> value from this section.  I can't see how data storage is fundamentally
>>> different to the general case of an application provider.
>=20
> They figured out how to increase encryption and manage their hosted
> environments.  There were adjustments made and they've been
> successful.
>=20
>>>=20
>>> Section 4.1.1
>>>=20
>>> I appreciate the recognition that endpoint-based techniques work.  The
>>> implication that this isn't the obvious solution, much less so.
>=20
> This isn't a technical comment, but we'll revisit the text to see if a
> wording change can help.
>=20
>>>=20
>>> Section 4.1.2
>>>=20
>>> I'm confused about the purpose of this section.  This seems to be talkin=
g
>>> about
>>> the sort of network-based methodologies an application provider might
>>> employ to
>>> ensure that their application is working as intended.  Why would the
>>> application
>>> provider not have access to detailed logging and usage metrics?
>=20
> The problem cited to us is that logging is sorely lacking.  This needs
> to be pointed out and fixed as it is too much for the operator to deal
> with given the large number of applications running in their
> environments.
>=20
>>>=20
>>> As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is
>>> cited no
>>> fewer than three times in the same paragraph.  It makes some fairly bold=

>>> claims
>>> about its effect on privacy that I don't believe will hold up to analysi=
s.
>>>=20
>>> Section 4.1.3.1
>>>=20
>>> This section correctly identifies the issue as one of shortcomings in
>>> logging,
>>> not increased use of encryption.
>=20
> Right, a key point in this document - other methods will have to be
> used and an obvious one is logging.  However, logging needs to improve
> for that to be possible.
>=20
>>>=20
>>> I would have stopped there, but the section persists and ultimately
>>> references
>>> RFC 7974, which is widely recognized as a monstrously bad idea (the IESG=

>>> note is
>>> fairly clear on this point).
>=20
> Thanks for catching that.  We can drop this text.
>=20
>>>=20
>>> Section 4.1.3.2
>>>=20
>>> "HTTP/2", not "HTTP2".
>=20
> Fixed.
>=20
>>>=20
>>> I don't see how this section belongs in this document.  The 1:1
>>> correlation
>>> between actions and flows in HTTP was a mistake of the 1980s that we've
>>> spent a
>>> lot of time on correcting (sometimes unsuccessfully, see pipelining).
>>>=20
>>> Section 4.1.3.3
>>>=20
>>> It's not a "service call" it's just a request.
>>>=20
>>> Section 4.2
>>>=20
>>> If the inclusion of a reference to RFC 7457 is to support a claim that T=
LS
>>> is
>>> attacked, that's sailing far too close to an endorsement of attacks than=
 I
>>> am
>>> comfortable with.  However, I don't believe that any of the listed attac=
ks
>>> remain viable in modern applications.  What is most often the case is th=
at
>>> a
>>> trust anchor is installed on enterprise users' machines and new
>>> certificates are
>>> minted as needed.  In other words, the host that is accessing the HTTPS
>>> site is
>>> owned by the enterprise and modified so that it can comply with its
>>> policies.
>>>=20
>>> When you recommend attack like this (to be clear, I would oppose
>>> publication of
>>> text that does this), you need to acknowledge the downsides.  For exampl=
e,
>>> MitM
>>> devices routinely break connections, they hide the true security status o=
f
>>> communications from endpoints and users, they frequently implement weake=
r
>>> versions of protocols, they often don't include the same degree of rigor=

>>> in
>>> things like certificate validation, and probably many more things that I=

>>> can't
>>> casually list off the cuff.
>=20
> Please suggest text.
>=20
>>>=20
>>> The discussion of caching here warrants a new section.
>>>=20
>>> Section 5.1
>>>=20
>>> s/effect/affect
>>>=20
>=20
> Thanks, we'll fix this.
>=20
>>> No complaint here, just an advertisement for technical solutions that
>>> aren't
>>> affected by increases in encryption.  Good, though I'm not sure if the
>>> section
>>> meets the document's criteria for inclusion.
>>>=20
>>> Section 5.3
>>>=20
>>> No cititation for APWG.  Not an IETF working group from what I can see.
>=20
> We'll add that, thanks.
>=20
>>>=20
>>> There's a presumption here that administrators need to perform these
>>> tasks.  Why
>>> can't endpoints do this?  It would certainly be a whole lot less invasiv=
e
>>> that
>>> way.  Take a look at how browsers implement checks for "bad" sites (whic=
h
>>> include phishing sites).  These methods have some fairly significant
>>> privacy
>>> safeguards without compromising on performance.
>=20
> A lot will move to the endpoints, but things like logging need to
> improve and we need to get application developers to do a better job
> so that there is no reason for someone to want to try to intercept
> traffic for troubleshooting.  Operators see this as an insurmountable
> problem.  We need to help.
>=20
>>>=20
>>> Section 5.5
>>>=20
>>> See my comment about about endpoint-based methods.
>=20
> Already agree with this point.
>=20
>>>=20
>>> Section 5.6
>>>=20
>>> I believe that the spoofed source address problem is not relevant to thi=
s
>>> document.  It's a fairly well understood problem.  That said, if we coul=
d
>>> wave a
>>> magic wand and get BCP 38 deployed, that might be nice.
>>>=20
>>> Section 6.1
>>>=20
>>> As this says, it's fairly well understood that - for HTTP - SNI is used.=

>>> The
>>> point that it is optional is interesting, but doesn't deserve the amount=

>>> of
>>> attention this section devotes to it.  The clients that don't include SN=
I
>>> are in
>>> a diminishing minority.
>=20
> Text was aded per EKR's review.
>=20
>>>=20
>>> That said, this doesn't pay any attention to another feature in HTTP/2:
>>> connection coalescing.
>=20
> Please suggest text if this should be included.
>=20
>>>=20
>>> Section 6.2
>>>=20
>>> ALPN will be encrypted in TLS 1.3.
>=20
> Noted.  Thanks.
>=20
>>>=20
>>> Section 6.3
>>>=20
>>> This reads as a invitation to perform traffic analysis (a statement that=
 I
>>> oppose).  Note that we have added padding to most recent protocols (HTTP=
/2
>>> and
>>> TLS 1.3 in particular) to give endpoints the ability to resist this sort=

>>> of
>>> attack.
>>>=20
>>> Note that block ciphers can add ~240 octets of discretionary padding per=

>>> record.
>>> That can be pretty effective if you are careful.
>=20
> I believe this text was added through the IESG review.  I don't see
> the problem with the text you are citing, so could you suggest
> alternate text?
>=20
>>>=20
>>> Section 7
>>>=20
>>> This section is duplicative of much of the rest of the document.  I
>>> realize that
>>> editing is hard, but see my earlier comments about structure.
>=20
> This text was the appendix, but moved to section 7 per IESG review and
> discuss.  It was the mobile operator view.
>=20
>>>=20
>>> It's obvious that this section is about QUIC.  That shows in several way=
s.
>>> It's
>>> nice how it doesn't say so out loud, but it leaks through in several
>>> confusing
>>> ways.  See below.
>>>=20
>>> Section 7.1
>>>=20
>>> This section is purportedly about encrypted ACKs, which won't happen unt=
il
>>> we
>>> get to QUIC.  But the points regarding proxies (b, c, d) are not prevent=
ed
>>> by
>>> encrypted ACKs, they are prevented by encryption more generally.  Point e=

>>> is
>>> defeated by integrity protection of ACKs, not confidentiality protection=
.
>>>=20
>>> I hope that the IETF never publishes draft-dolson-plus-middlebox-benefit=
s;
>>> it
>>> makes claims about the benefits of specific solutions for different use
>>> cases
>>> with the goal of justifying those solutions.  At the same time, it fails=

>>> to
>>> recognize the existence of alternative, often superior, solutions for
>>> those use
>>> cases.  In other words, it has many of the same issues as this document.=

>=20
> I think this is an early document and expect it will get some
> revision.  This was added into our document per Mirja's IESG review.
> They are documenting middle boxes that use 5-tuples.  That point isn't
> clear until the summary.  I provided some light feedback, but could
> provide more to help them improve the document.  I think it's fine to
> document these things and then figure out how we can do better with
> IETF agreed upon protocol design intentions (end-to-end and assisting
> to improve user's privacy as well as the security of sessions.
>=20
>>>=20
>>> FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I=

>>> don't
>>> know how to close the gap between the privacy assurances I wish it had a=
nd
>>> the
>>> privacy weaknesses it has.
>>>=20
>>> The phrase "trusted proxies" is a dangerously misleading phrase.  The
>>> concept of
>>> trust is - particularly in this context - frequently abused.
>=20
> That's why the quotes were there, but this has been re-phrased in 10 -
> see the SecDir review.
>=20
>>>=20
>>> Sections 7.2 and 7.3
>>>=20
>>> I'd be interested in learning about the justification for these features=

>>> (again,
>>> go back to my comment about to whom the benefit accrues, and I'd advise
>>> caution
>>> not to make the trickle-down economics mistake of using second-order
>>> effects).
>>> Personally, I'm not that sad that they are going to be negatively
>>> affected.
>>>=20
>>> Section 7.2, Point d seems to be saying something about a multiplexed
>>> protocol,
>>> not one that has an encrypted transport header (see above regarding QUIC=
).
>>>=20
>>> All these points equally apply to HTTPS, which suggest that encrypted
>>> transport
>>> headers is not the issue (unless by transport we mean HTTP).
>=20
> Again, section 7 was changed in IESG review and added into the body of
> the document per Mirja's discuss since the mobile operator is
> important to include.
>=20
>>>=20
>>> Section 7.4
>>>=20
>>> s/GPSR/GPRS/ ?
>=20
> Fixed.  I thought this was fixed in 9, hence me thinking you read the
> wrong version.
>=20
>>>=20
>>> Section 8
>>>=20
>>> I generally agree with the first statement here, but after having read t=
he
>>> document, I could take away some very different views on what the
>>> "problems at
>>> hand" actually are.  I suspect that different people will have very
>>> different
>>> takeaways.
>>>=20
>>> The conclusion section of a document is not the right place to start
>>> introducing
>>> new information, particularly information relevant to RFC 2804.
>=20
> Should we move this to the introduction perhaps to help with context setti=
ng?
>=20
>>>=20
>>> Not sure where this is going:
>>>=20
>>>   Terrorists and criminals have been using encryption for many years.
>>>=20
>>> Because it's disconnected from the remainder of the paragraph.  If you a=
re
>>> going
>>> to invoke the T-word, you had better have a strong argument to make.  On=

>>> the
>>> final sentence of that paragraph, the subject ("This") is unclear.
>>>=20
>=20
> Sure, the point was that their use of encryption is not a
> justification argue any of the improvements to crypto for the general
> population.  Incident handlers know full well that encryption has been
> in place for a long time by these users.  Essentially, it's not an argumen=
t that
> hold muster.
>=20
>>=20
>>=20
>>=20
>> --
>>=20
>> Best regards,
>> Kathleen
>>=20
>>=20
>=20
>=20
>=20
> --=20
>=20
> Best regards,
> Kathleen & Al


From nobody Tue Apr 11 06:34:13 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86291129BC1 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 06:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, 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 Qnu5Jy71O_6X for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 06:34:05 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::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 B4429129BA5 for <ietf@ietf.org>; Tue, 11 Apr 2017 06:34:05 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id t68so2094812iof.0 for <ietf@ietf.org>; Tue, 11 Apr 2017 06:34:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=aLsyKDSvjtLcA+MMneOxmd26Lk+RymQS/H8jyPy/Dnc=; b=OO2NCL8iMcP2inJtQYtTMztNxgZ5GH+w0SeDgLFnhFgoNxSEudZFElsI8ioi7gTIXw UGQ83ghz/rZja1LVnWrTlVjMVS23z7Z+i5dEm7nJojywcqpG4u57xMyldcDtVM3oxKpL 4ApPMWt4xAVb/KSrKshcIrngxAlQD6uVB23fNkD+b49dEIhTIpWKCPzndrXQGbMeIHvg SiRF0qbKgG4rbfSxP1Ntjj22NeAYiKR3mrLINZ56ShD2bAtf34B4+rL5y/rgYOG7lx3A DjgFpTeqE7cyt4SxzMvxhNVUipPS6FDDMTSSIPrsZM1g2fuFGZMbpFMhhTDq3qqkMqz7 ljfA==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=aLsyKDSvjtLcA+MMneOxmd26Lk+RymQS/H8jyPy/Dnc=; b=tiaTw+nhtpDVg7Kq0vxyjVSjtmy27BPIy/o/4waPPgga/nRvCSrTOKMUIea9rk5DWX h/4HWrFKKVhPQHVLsVyoGYFsSC1xz6h6AZoo+hLgHNVKyoZNdfHunP7r+b22/MBdWaD8 G/Llo90/szYRmki/tVd5LJmnoAy2k618qlVzwCcj7vReCkwKLf2M4C68duTDrxUA+QrG WndUasujMG/o6+oaPGg6t21otCoTkE0xSoSaiXp7VckXK3k3qKNZAxend/f52eSx0eGW 5Z1QcKDFWEDn/ZeYZSSZYUVCGM2pkJFo9b0/c0+Ww6zdTYFNJzKx6CY1RReGDbmpR/Rk rS+w==
X-Gm-Message-State: AN3rC/5BIzQEHt/iEOC1YLTzINzvVeJqkIn2If6xG5PjvjtHvyWnRmPaMPuztNF1UrFv+A==
X-Received: by 10.107.142.207 with SMTP id q198mr1176951iod.99.1491917645077;  Tue, 11 Apr 2017 06:34:05 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id o72sm899260ite.10.2017.04.11.06.34.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 06:34:04 -0700 (PDT)
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: Dave Dolson <ddolson@sandvine.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <36f11093-8283-dbcc-68d5-0c7f4267988c@gmail.com>
Date: Wed, 12 Apr 2017 01:33:59 +1200
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: <20170411120303.5128273.2297.7062@sandvine.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JAy_yo8D_6R-JfBVANsFUiErao8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 13:34:08 -0000

On 12/04/2017 00:03, Dave Dolson wrote:
> Regarding "benefits", these devices clearly have perceived benefits to =
those who deploy them. My view is that the document should explain that p=
erspective for readers who lack the operator perspective.
> The intent was not to mandate or recommend deployments.

I'm not against facts, which was one of the reasons that I co-authored
RFC 3234. But in that document we worked hard to be as neutral as
possible. Revisiting the topic 15 years later seems like a good idea,
and focussing on transport-layer snooping is fine. But the tone would
need to be very neutral and the draft would need to present pros
and cons for this to be published by the IETF, I think. The topic is
one of the major ongoing tussles and the IETF needs to be completely
objective.

"This document advocates for transport connections to be measured and
managed by the network..."

That's opinion. We may describe, but we shouldn't advocate. Give the
doucment a good scrub to eliminate all advocacy, perhaps, and mention
the downsides for each upside?

One downside that doesn't seem to be mentioned is *finding* the transport=

layer information. That will become increasingly difficult in future.

BTW I don't see ECMP or load balancing listed in section 3. Those
seem to be major applications of transport layer snooping.

   Brian

>=20
> David Dolson
> =E2=80=8E
>   Original Message
> From: mohamed.boucadair@orange.com
> Sent: Tuesday, April 11, 2017 7:48 AM
> To: Stephen Farrell; Martin Thomson; ietf@ietf.org
> Cc: draft-dolson-plus-middlebox-benefits@tools.ietf.org
> Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of dr=
aft-mm-wg-effect-encrypt-09)
>=20
>=20
> Hi Stephen,
>=20
> Please see inline.
>=20
> Cheers,
> Med
>=20
>> -----Message d'origine-----
>> De : Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>> Envoy=C3=A9 : mardi 11 avril 2017 10:51
>> =C3=80 : BOUCADAIR Mohamed IMT/OLN; Martin Thomson; ietf@ietf.org
>> Cc : draft-dolson-plus-middlebox-benefits@tools.ietf.org
>> Objet : Re: draft-dolson-plus-middlebox-benefits (was RE: Review of dr=
aft-
>> mm-wg-effect-encrypt-09)
>>
>>
>> Hi Med,
>>
>> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>>>> I hope that the IETF never publishes
>>>> draft-dolson-plus-middlebox-benefits; it makes claims about the
>>>> benefits of specific solutions for different use cases with the
>>>> goal of justifying those solutions.
>>
>>> [Med] I'm afraid this is speculating about the intent of
>>> draft-dolson. Assured this is not the purpose of that document. The
>>> motivation is to document current practices without including any
>>> recommendation or claiming these solutions are superior to others.
>>
>> Just to note that I completely agree with Martin's interpretation
>> of the thrust of this draft and I totally fail to see how your
>> argument above can be justified given that draft title, abstract
>> and even filename (and also the content;-).
>=20
> [Med] "beneficial" is derived from the initial request that motivated t=
his draft (excerpt from the abstract):
>=20
>    At IETF97, at a meeting regarding the Path Layer UDP Substrate (PLUS=
)
>    protocol, a request was made for documentation about the benefits
>              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    that might be provided by permitting middleboxes to have some
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    visibility to transport-layer information.
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20
>  When the abstract
>> says "This document summarizes benefits" then I cannot interpret
>> that as other than being intended to justify the uses described.
>=20
> [Med] I would prefer if we can avoid to "interpret", but raise question=
s to the authors if there is a doubt. The document does not provide a rec=
ommendation or claims this is the only way to achieve the technical goals=
=2E It does only reflect some deployment reality together with some motiv=
ations.
>=20
>>
>> A fairly thorough re-write to aim to describe the pros and cons
>> would be a different and more useful document.
>=20
> [Med] There are already many RFCs that discuss the issues/cons (I can c=
ite this RFC I co-authored https://tools.ietf.org/html/rfc6269 for the CG=
N case). What is needed IMHO is something else: understand the requiremen=
ts that led to deploy some of these functions.
>=20
>  Similarly a draft
>> that strives to neutrally describe existing reality could maybe
>> be useful (*)
>=20
> [Med] This is the intent of draft-dolson.
>=20
>  but one that only describes middlebox friends with
>> "benefits" is not IMO beneficial ;-)
>=20
> [Med] The intent is not to "sell something" but to understand the techn=
ical needs so that hopefully we can have a reference for future solution-=
oriented discussions.
> If a given function can be provided without involving an on-path device=
, this would be great for operators (optimize CAPEX/OPEX is our motto).
>=20
>>
>> Cheers,
>> S.
>>
>> (*) That is the argument for draft-mm-effect-encrypt, for which I
>> do support publication (apparently in disagreement with Martin in
>> that case:-)
>>
>>
>>
>=20


From nobody Tue Apr 11 06:45:06 2017
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D293129BCE; Tue, 11 Apr 2017 06:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=metaswitch.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 P_QUd0Y4h55K; Tue, 11 Apr 2017 06:44:53 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0130.outbound.protection.outlook.com [104.47.36.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B774129BBE; Tue, 11 Apr 2017 06:44:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eQX7AgOlcaaYMqSHak2xEHMxyfkt+8t5N7bVcmhND3A=; b=TVKGdJda0h1Xf5ojPCrShw/k0GxtC6ygt2FMHAWxMMMwJtXYuxuWXTLVJ5DM5X9s9SfJ0o22N1L3yeuk8aKXPoyYo9wjSKOotCPxIONspq327nJTHKZMG6Lr8NY2bOthv+BPIZTWEWVoebunZ2f4OJymTP4nHq9vzkEWuxqXc1Y=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 13:44:50 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 13:44:50 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Lionel Morand <lionel.morand@orange.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSnjojD8qJebPVvkunBA8z9I/80aHAL9TQ
Date: Tue, 11 Apr 2017 13:44:50 +0000
Message-ID: <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com>
In-Reply-To: <148965756308.14230.13426886469262710918@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: orange.com; dkim=none (message not signed) header.d=none;orange.com; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [82.132.227.234]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1910; 7:RsDWGHeykqXzHTluMZGbBlisjd4iQRCVYkkg0UNrKcs4b0Lc8sS1ZAZdXe6EMJF0sVBsDtkVgNB/Ybf4+wGxw3mf5KWia9ku2ZtW/QCGh2MxSqeJmdEEl5ccQPZXIkcFynWE2Mheu7fdjN+aJJHENYEGafp9djjEnhDTVxyt3qcCwM1gVEuM+QnCbQci+7s0ERqqtoymw8r0TSXjviQm4WIBew4bVR7MmE9erBUOLSDsik7R5Czsoy9u1A+DxmMuZA3hGmI/6/NYlWSApSQQth8hNcyXcrMEIXu87qDue0h46M96TDbUcixvxGsCYc7BGHgDLHmiZvshrrJ/FoRjyQ==
x-ms-office365-filtering-correlation-id: 57d13176-0407-4ce6-d464-08d480e0ed07
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BY2PR0201MB1910; 
x-microsoft-antispam-prvs: <BY2PR0201MB1910DBB12AE1A910A1EE66B884000@BY2PR0201MB1910.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506)(18271650672692);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123562025)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(6072148); SRVR:BY2PR0201MB1910; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1910; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39450400003)(39410400002)(13464003)(66654002)(6116002)(122556002)(2900100001)(102836003)(3846002)(38730400002)(9686003)(230783001)(2501003)(6436002)(77096006)(6506006)(6246003)(99286003)(53946003)(7736002)(74316002)(54906002)(55016002)(53936002)(2950100002)(54356999)(76176999)(229853002)(7696004)(66066001)(305945005)(50986999)(33656002)(8936002)(8676002)(81166006)(86362001)(3660700001)(3280700002)(4326008)(2906002)(53546009)(189998001)(25786009)(5660300001)(559001)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1910; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 13:44:50.0952 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1910
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LG5MoUZBFcdewcU0CO5-WVKw4rU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 13:44:57 -0000

SGkgTGlvbmVsDQoNCk1hbnkgdGhhbmtzIGZvciBhIHZlcnkgdGhvcm91Z2ggcmV2aWV3LiAgSSdt
IHBpY2tpbmcgdXAgdGhpcyB0aHJlYWQgYW5kIHJlcGx5aW5nIGFzIFBDRSB3b3JraW5nIGdyb3Vw
IGNoYWlyLCBhcyB0aGUgYXV0aG9ycyBhcmUgdW5hdmFpbGFibGUuICBJIGFwb2xvZ2lzZSBmb3Ig
dGhlIGRlbGF5Lg0KDQpQbGVhc2Ugc2VlIG15IHByb3Bvc2VkIHJlc29sdXRpb25zIGlubGluZSBi
ZWxvdywgbWFya2VkIHdpdGggIkpvbj4iDQoNCkJlc3QgcmVnYXJkcw0KSm9uDQoNCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IExpb25lbCBNb3JhbmQgW21haWx0bzpsaW9uZWwu
bW9yYW5kQG9yYW5nZS5jb21dDQpTZW50OiAxNiBNYXJjaCAyMDE3IDA5OjQ2DQpUbzogb3BzLWRp
ckBpZXRmLm9yZw0KQ2M6IGRyYWZ0LWlldGYtcGNlLXN0YXRlZnVsLXBjZS5hbGxAaWV0Zi5vcmc7
IHBjZUBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmV2aWV3IG9mIGRyYWZ0LWll
dGYtcGNlLXN0YXRlZnVsLXBjZS0xOA0KDQpSZXZpZXdlcjogTGlvbmVsIE1vcmFuZA0KUmV2aWV3
IHJlc3VsdDogSGFzIElzc3Vlcw0KDQpJIGhhdmUgcmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBw
YXJ0IG9mIHRoZSBPcGVyYXRpb25hbCBkaXJlY3RvcmF0ZSdzIG9uZ29pbmcgZWZmb3J0IHRvIHJl
dmlldyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZSBJRVNHLiAgVGhl
c2UgY29tbWVudHMgd2VyZSB3cml0dGVuIHdpdGggdGhlIGludGVudCBvZiBpbXByb3ZpbmcgdGhl
IG9wZXJhdGlvbmFsIGFzcGVjdHMgb2YgdGhlIElFVEYgZHJhZnRzLiBDb21tZW50cyB0aGF0IGFy
ZSBub3QgYWRkcmVzc2VkIGluIGxhc3QgY2FsbCBtYXkgYmUgaW5jbHVkZWQgaW4gQUQgcmV2aWV3
cyBkdXJpbmcgdGhlIElFU0cgcmV2aWV3LiAgRG9jdW1lbnQgZWRpdG9ycyBhbmQgV0cgY2hhaXJz
IHNob3VsZCB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0IGxpa2UgYW55IG90aGVyIGxhc3QgY2Fs
bCBjb21tZW50cy4NCg0KSSd2ZSBwb2ludGVkIG91dCBzb21lICJpc3N1ZXMiIHRoYXQgbWlnaHQg
bm90IGJlIHJlYWwgaXNzdWVzIGZvciBwZW9wbGUgaW52b2x2ZWQgaW4gUENFIGJ1dCB0aGF0IGNv
dWxkIGJlIGF0IGxlYXN0IGNsYXJpZmllZCBmb3IgcmVhZGVycyBvZiB0aGlzIGRvY3VtZW50LiBE
ZXRhaWxlZCBjb21tZW50cyBhcmUgcHJvdmlkZWQgYmVsb3cuDQoNClJlZ2FyZHMsDQoNCkxpb25l
bA0KDQoqKioqKioqKioqKioqKioqKioqKg0KMi4gIFRlcm1pbm9sb2d5DQoNCiAgIFRoaXMgZG9j
dW1lbnQgdXNlcyB0aGUgZm9sbG93aW5nIHRlcm1zIGRlZmluZWQgaW4gW1JGQzU0NDBdOiBQQ0Ms
DQogICBQQ0UsIFBDRVAgUGVlciwgUENFUCBTcGVha2VyLg0KDQogICBUaGlzIGRvY3VtZW50IHVz
ZXMgdGhlIGZvbGxvd2luZyB0ZXJtcyBkZWZpbmVkIGluIFtSRkM0NjU1XTogVEVELg0KDQogICBU
aGlzIGRvY3VtZW50IHVzZXMgdGhlIGZvbGxvd2luZyB0ZXJtcyBkZWZpbmVkIGluIFtSRkMzMDMx
XTogTFNQLg0KDQogICBUaGlzIGRvY3VtZW50IHVzZXMgdGhlIGZvbGxvd2luZyB0ZXJtcyBkZWZp
bmVkIGluDQogICBbSS1ELmlldGYtcGNlLXN0YXRlZnVsLXBjZS1hcHBdOiBTdGF0ZWZ1bCBQQ0Us
IFBhc3NpdmUgU3RhdGVmdWwgUENFLA0KICAgQWN0aXZlIFN0YXRlZnVsIFBDRSwgRGVsZWdhdGlv
biwgTFNQIFN0YXRlIERhdGFiYXNlLg0KDQpbTE1dIEkgZGlkbid0IGZpbmQgYSBjbGVhciBkZWZp
bml0aW9uIG9mIHRoZSBMU1Agc3RhdGUsIGV4Y2VwdCB0aHJvdWdoIHRoZSBkZWZpbml0aW9uIG9m
IHRoZSBMU1AgU3RhdGUgZGF0YWJhc2UgaW4gaWV0Zi1wY2Utc3RhdGVmdWwtcGNlLWFwcCwgaS5l
Lg0KDQogICBUaGUgc2Vjb25kIGlzIHRoZSBMU1ANCiAgIFN0YXRlIERhdGFiYXNlIChMU1AtREIp
LCBpbiB3aGljaCBhIFBDRSBzdG9yZXMgYXR0cmlidXRlcyBvZiBhbGwNCiAgIGFjdGl2ZSBMU1Bz
IGluIHRoZSBuZXR3b3JrLCBzdWNoIGFzIHRoZWlyIHBhdGhzIHRocm91Z2ggdGhlIG5ldHdvcmss
DQogICBiYW5kd2lkdGgvcmVzb3VyY2UgdXNhZ2UsIHN3aXRjaGluZyB0eXBlcyBhbmQgTFNQIGNv
bnN0cmFpbnRzLg0KDQpBcyB0aGlzIGRvY3VtZW50IGhlYXZpbHkgcmVsaWVzIG9uIHRoaXMgTFNQ
IHN0YXRlIGNvbmNlcHQsIGl0IGNvdWxkIGJlIHVzZWZ1bCB0byAocmUtKWRlZmluZSBpdCBpbiB0
aGlzIGRvY3VtZW50IG9yIHRvIGZpbmQgYSBjb3JyZWN0IHJlZmVyZW5jZSBmb3IgaXQuDQoNCkpv
bj4gVGhlIGRlZmluaXRpb24gb2YgTFNQIFN0YXRlIERhdGFiYXNlIGdpdmVuIGJ5IGRyYWZ0LWll
dGYtcGNlLXN0YXRlZnVsLWFwcCAobm93IFJGQyA4MDUxKSBkb2VzIGNvbnRhaW4gYSBwcmV0dHkg
Z29vZCBkZXNjcmlwdGlvbiBvZiB0aGUgTFNQIFN0YXRlICgicGF0aHMgdGhyb3VnaCB0aGUgbmV0
d29yaywgYmFuZHdpZHRoL3Jlc291cmNlIHVzYWdlLCBzd2l0Y2hpbmcgdHlwZXMgYW5kIExTUCBj
b25zdHJhaW50cyAiKS4gIEkga25vdyBpdCdzIHdyaXR0ZW4gaW5mb3JtYWxseSAoInN1Y2ggYXMu
Li4iKSBidXQgSSB0aGluayBpdCdzIGdvb2QgZW5vdWdoLg0KDQo9PT09PQ0KDQozLjIuICBPYmpl
Y3RpdmVzDQoNCiAgIFRoZSBvYmplY3RpdmVzIGZvciB0aGUgcHJvdG9jb2wgZXh0ZW5zaW9ucyB0
byBzdXBwb3J0IHN0YXRlZnVsIFBDRQ0KICAgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgYXJl
IGFzIGZvbGxvd3M6DQoNClsuLi5dDQoNCiAgIG8gIEFsbG93IGEgUENDIHRvIGRlbGVnYXRlIGNv
bnRyb2wgb2YgaXRzIExTUHMgdG8gYW4gYWN0aXZlDQpzdGF0ZWZ1bA0KICAgICAgUENFIHN1Y2gg
dGhhdCBhIGdpdmVuIExTUCBpcyB1bmRlciB0aGUgY29udHJvbCBvZiBhIHNpbmdsZSBQQ0UNCmF0
DQogICAgICBhbnkgZ2l2ZW4gdGltZS4gIEEgUENDIG1heSByZXZva2UgdGhpcyBkZWxlZ2F0aW9u
IGF0IGFueSB0aW1lDQogICAgICBkdXJpbmcgdGhlIGxpZmV0aW1lIG9mIHRoZSBMU1AuICBJZiBM
U1AgZGVsZWdhdGlvbiBpcyByZXZva2VkDQogICAgICB3aGlsZSB0aGUgUENFUCBzZXNzaW9uIGlz
IHVwLCB0aGUgUENDIE1VU1Qgbm90aWZ5IHRoZSBQQ0UgYWJvdXQNCiAgICAgIHRoZSByZXZvY2F0
aW9uLiAgQSBQQ0UgbWF5IHJldHVybiBhbiBMU1AgZGVsZWdhdGlvbiBhdCBhbnkNCnBvaW50DQog
ICAgICBkdXJpbmcgdGhlIGxpZmV0aW1lIG9mIHRoZSBQQ0VQIHNlc3Npb24uDQoNCltMTV0gSSdt
IGFzc3VtaW5nIHRoYXQgdGhlIFBDRSByZXR1cm5pbmcgdGhlIGRlbGVnYXRpb24gaGFzIGFsc28g
dG8NCm5vdGlmeSB0aGUgUENDLiBJZiBzbywgbWF5YmU6DQoNCiAgICAgInRoZSBJZiBMU1AgZGVs
ZWdhdGlvbiBpcyByZXR1cm5lZCBieSB0aGUgUENFIHdoaWxlIHRoZSBQQ0VQDQogICAgICBzZXNz
aW9uIGlzIHVwLCB0aGUgUENFIE1VU1Qgbm90aWZ5IHRoZSBQQ0UgYWJvdXQgdGhlDQpyZXZvY2F0
aW9uLiINCg0KW0xNXSB0aGUgYnVsbGV0IHBvaW50IGNvdWxkIGJlIHRoZW4gc3BsaXR0ZWQgaW50
byB0d28gYnVsbGV0cywgb25lIGZvcg0KUENDLCBvbmUgZm9yIFBDRS4NCg0KSm9uPiBBQ0suICBU
aGlzIHdvdWxkIHByb2JhYmx5IGJlIGJlc3QgYXMgdHdvIHN1Yi1idWxsZXRzLg0KDQo9PT09DQoN
CjUuNC4gIENhcGFiaWxpdHkgQWR2ZXJ0aXNlbWVudA0KDQogICBEdXJpbmcgUENFUCBJbml0aWFs
aXphdGlvbiBQaGFzZSwgUENFUCBTcGVha2VycyAoUENFIG9yIFBDQykNCiAgIGFkdmVydGlzZSB0
aGVpciBzdXBwb3J0IG9mIHN0YXRlZnVsIFBDRVAgZXh0ZW5zaW9ucy4gIEEgUENFUA0KU3BlYWtl
cg0KICAgaW5jbHVkZXMgdGhlICJTdGF0ZWZ1bCBQQ0UgQ2FwYWJpbGl0eSIgVExWLCBkZXNjcmli
ZWQgaW4NCiAgIFNlY3Rpb24gNy4xLjEsIGluIHRoZSBPUEVOIE9iamVjdCB0byBhZHZlcnRpc2Ug
aXRzIHN1cHBvcnQgZm9yDQpQQ0VQDQogICBzdGF0ZWZ1bCBleHRlbnNpb25zLiAgVGhlIFN0YXRl
ZnVsIENhcGFiaWxpdHkgVExWIGluY2x1ZGVzIHRoZQ0KJ0xTUA0KICAgVXBkYXRlJyBGbGFnIHRo
YXQgaW5kaWNhdGVzIHdoZXRoZXIgdGhlIFBDRVAgU3BlYWtlciBzdXBwb3J0cyBMU1ANCiAgIHBh
cmFtZXRlciB1cGRhdGVzLg0KDQogICBUaGUgcHJlc2VuY2Ugb2YgdGhlIFN0YXRlZnVsIFBDRSBD
YXBhYmlsaXR5IFRMViBpbiBQQ0MncyBPUEVODQpPYmplY3QNCiAgIGluZGljYXRlcyB0aGF0IHRo
ZSBQQ0MgaXMgd2lsbGluZyB0byBzZW5kIExTUCBTdGF0ZSBSZXBvcnRzDQp3aGVuZXZlcg0KICAg
TFNQIHBhcmFtZXRlcnMgb3Igb3BlcmF0aW9uYWwgc3RhdHVzIGNoYW5nZXMuDQoNCiAgIFRoZSBw
cmVzZW5jZSBvZiB0aGUgU3RhdGVmdWwgUENFIENhcGFiaWxpdHkgVExWIGluIFBDRSdzIE9QRU4N
Cm1lc3NhZ2UNCiAgIGluZGljYXRlcyB0aGF0IHRoZSBQQ0UgaXMgaW50ZXJlc3RlZCBpbiByZWNl
aXZpbmcgTFNQIFN0YXRlDQpSZXBvcnRzDQogICB3aGVuZXZlciBMU1AgcGFyYW1ldGVycyBvciBv
cGVyYXRpb25hbCBzdGF0dXMgY2hhbmdlcy4NCg0KW0xNXSBpcyBpdCAid2lsbGluZy9pbnRlcmVz
dGVkIGZvciIgb3IganVzdCBhIGNhcGFiaWxpdHkgaW5kaWNhdGlvbj8NCkl0IGlzIG5vdCB0aGUg
c2FtZSB0aGluZyBmcm9tIGEgcHJvY2VkdXJlIHBvaW50IG9mIHZpZXcuDQoNCkpvbj4gSXQgaXMg
IndpbGxpbmcgLyBpbnRlcmVzdGVkIGZvciIgYXMgd3JpdHRlbiAtIGl0J3Mgbm90IGp1c3QgYSBj
YXBhYmlsaXR5LiAgSWYgdGhlIFRMViBpcyBpbmNsdWRlZCBpbiBlYWNoIE9QRU4gbWVzc2FnZSB0
aGVuIHRoZSBMU1Agc3RhdGUgaXMgc3luY2hyb25pemVkIGF1dG9tYXRpY2FsbHkuICBJZiBhIGRl
dmljZSBoYXMgdGhlIGNhcGFiaWxpdHkgYnV0IGRvZXMgbm90IHdhbnQgdG8gZG8gaXQgZm9yIHNv
bWUgcmVhc29uIHRoZW4gaXQgb21pdHMgdGhlIFRMVi4NCg0KPT09PT0NCg0KICAgVGhlIFBDRVAg
ZXh0ZW5zaW9ucyBmb3Igc3RhdGVmdWwgUENFcyBNVVNUIE5PVCBiZSB1c2VkIGlmIG9uZSBvcg0K
Ym90aA0KICAgUENFUCBTcGVha2VycyBoYXZlIG5vdCBpbmNsdWRlZCB0aGUgU3RhdGVmdWwgUENF
IENhcGFiaWxpdHkgVExWIGluDQogICB0aGVpciByZXNwZWN0aXZlIE9QRU4gbWVzc2FnZS4gIElm
IHRoZSBQQ0VQIFNwZWFrZXIgb24gdGhlIFBDQw0KICAgc3VwcG9ydHMgdGhlIGV4dGVuc2lvbnMg
b2YgdGhpcyBkcmFmdCBidXQgZGlkIG5vdCBhZHZlcnRpc2UgdGhpcw0KICAgY2FwYWJpbGl0eSwg
dGhlbiB1cG9uIHJlY2VpcHQgb2YgUENVcGQgbWVzc2FnZSBmcm9tIHRoZSBQQ0UsIGl0DQpNVVNU
DQogICBnZW5lcmF0ZSBhIFBDRXJyIHdpdGggZXJyb3ItdHlwZSAxOSAoSW52YWxpZCBPcGVyYXRp
b24pLA0KZXJyb3ItdmFsdWUNCiAgIDIgKEF0dGVtcHRlZCBMU1AgVXBkYXRlIFJlcXVlc3QgaWYg
dGhlIHN0YXRlZnVsIFBDRSBjYXBhYmlsaXR5IHdhcw0KICAgbm90IGFkdmVydGlzZWQpKHNlZSBT
ZWN0aW9uIDguNSkgYW5kIGl0IFNIT1VMRCB0ZXJtaW5hdGUgdGhlIFBDRVANCiAgIHNlc3Npb24u
ICBJZiB0aGUgUENFUCBTcGVha2VyIG9uIHRoZSBQQ0Ugc3VwcG9ydHMgdGhlIGV4dGVuc2lvbnMN
Cm9mDQogICB0aGlzIGRyYWZ0IGJ1dCBkaWQgbm90IGFkdmVydGlzZSB0aGlzIGNhcGFiaWxpdHks
IHRoZW4gdXBvbg0KcmVjZWlwdA0KICAgb2YgYSBQQ1JwdCBtZXNzYWdlIGZyb20gdGhlIFBDQywg
aXQgTVVTVCBnZW5lcmF0ZSBhIFBDRXJyIHdpdGgNCmVycm9yLQ0KICAgdHlwZSAxOSAoSW52YWxp
ZCBPcGVyYXRpb24pLCBlcnJvci12YWx1ZSA1IChBdHRlbXB0ZWQgTFNQIFN0YXRlDQogICBSZXBv
cnQgaWYgYWN0aXZlIHN0YXRlZnVsIFBDRSBjYXBhYmlsaXR5IHdhcyBub3QgYWR2ZXJ0aXNlZCkg
KHNlZQ0KICAgU2VjdGlvbiA4LjUpIGFuZCBpdCBTSE9VTEQgdGVybWluYXRlIHRoZSBQQ0VQIHNl
c3Npb24uDQoNCltMTV0gd2h5IHRoZSByZWNvbW1lbmRhdGlvbiBmb3IgY2xvc2luZyB0aGUgc2Vz
c2lvbiBpZiBhbiBleHBsaWNpdA0KZXJyb3IgaXMgc2VudCBiYWNrPyBUaGUgc2Vzc2lvbiBjb3Vs
ZCByZW1haW4gb3BlbiBpLmUuIGV4Y2VwdCBzdGF0ZWZ1bA0KUENFUCBleHRlbnNpb25zLGV2ZXJ5
dGhpbmcgZWxzZSB3b3VsZCBiZSBmaW5lLiBJZiB0aGUgc2Vzc2lvbg0KdGVybWluYXRpb24gaXMg
dGhlIHJpZ2h0IHRoaW5nIHRvIGRvLCBhcyB3ZSBhcmUgaW4gYSBjbGVhciBlcnJvciBjYXNlDQoo
YXMgdGhlIFBDRVAgc3BlYWtlciBzaG91bGQgbm90IHNlbmQgdGhlIHJlcG9ydCBvciB0aGUgdXBk
YXRlKSwgdGhlDQpTSE9VTEQgc2hvdWxkIHByb2JhYmx5IGJlIGEgTVVTVCBoZWUuDQoNCkpvbj4g
QXMgeW91IHNheSwgdGhlIHNlc3Npb24gY291bGQgbGltcCBvbiBpZiB0aGUgaW1wbGVtZW50YXRp
b24gZGVlbXMgaXQgbmVjZXNzYXJ5LCBidXQgdGhpcyBtaWdodCBsZWFkIHRvIGxvdHMgb2Ygc3B1
cmlvdXMgbWVzc2FnZXMgYW5kIGVycm9yIGxvZ3MgYXQgYm90aCBlbmRzLCBzbyBpdCBpcyBwcm9i
YWJseSBub3QgYSBnb29kIGlkZWEuICBXZSBkb24ndCB3YW50IHRvIG91dHJpZ2h0IGZvcmJpZCB0
aGlzLCBoZW5jZSB0aGUgU0hPVUxELg0KDQo9PT09PQ0KDQpbTE1dIElzIHRoZXJlIGFueSByZWFz
b24gdG8gdXNlIGEgc3BlY2lmaWMgZXJyb3IgaW4gc3VjaCBhIGNhc2U/IFRoZQ0KUENFIGNvdWxk
IGp1c3QgYmVoYXZlIGFzIGEgUENFIG5vdCBzdXBwb3J0aW5nIHRoZSBmZWF0dXJlLiBXaHkgaXMg
aXQNCmltcG9ydGFudCBmb3IgdGhlIHN1cHBvcnRpbmcgUENFUCBzcGVha2VyIHRvIG1ha2UgdGhl
IGRpZmZlcmVuY2U/IFRoZQ0KZ2VuZXJpYyBiZWhhdmlvciBkZXNjcmliZWQgaW4gUkZDNTQ0MCBp
cyBub3QgZW5vdWdoPw0KDQpKb24+IEkgdGhpbmsgaXQncyBqdXN0IHRoYXQgdGhlIHNwZWNpZmlj
IGVycm9yIGNvZGUgbWF5IGFpZCBpbiBkaWFnbm9zaW5nIHRoZSBwcm9ibGVtIHF1aWNrbHkuDQoN
Cj09PT09DQoNCltMTV0gYWN0aXZlL3Bhc3NpdmUgbW9kZSBhcmUgbm90ICBhZHZlcnRpemVkIGlu
IFBDRVAuDQpzL2lmIGFjdGl2ZSBzdGF0ZWZ1bCBQQ0UgY2FwYWJpbGl0eSB3YXMgbm90IGFkdmVy
dGlzZWQvaWYgc3RhdGVmdWwgUENFDQpjYXBhYmlsaXR5IHdhcyBub3QgYWR2ZXJ0aXNlZA0KDQpK
b24+IEFDSw0KDQo9PT09PQ0KDQo+RnJvbSBSRkM1NDQwOiAiNi45LiAgUmVjZXB0aW9uIG9mIFVu
a25vd24gTWVzc2FnZXMNCg0KICAgQSBQQ0VQIGltcGxlbWVudGF0aW9uIHRoYXQgcmVjZWl2ZXMg
YW4gdW5yZWNvZ25pemVkIFBDRVAgbWVzc2FnZQ0KTVVTVA0KICAgc2VuZCBhIFBDRXJyIG1lc3Nh
Z2Ugd2l0aCBFcnJvci12YWx1ZT0yIChjYXBhYmlsaXR5IG5vdA0Kc3VwcG9ydGVkKS4NCg0KICAg
SWYgYSBQQ0MvUENFIHJlY2VpdmVzIHVucmVjb2duaXplZCBtZXNzYWdlcyBhdCBhIHJhdGUgZXF1
YWwgb3INCiAgIGdyZWF0ZXIgdGhhbiBNQVgtVU5LTk9XTi1NRVNTQUdFUyB1bmtub3duIG1lc3Nh
Z2UgcmVxdWVzdHMgcGVyDQogICBtaW51dGUsIHRoZSBQQ0MvUENFIE1VU1Qgc2VuZCBhIFBDRVAg
Q0xPU0UgbWVzc2FnZSB3aXRoIGNsb3NlDQogICB2YWx1ZT0iUmVjZXB0aW9uIG9mIGFuIHVuYWNj
ZXB0YWJsZSBudW1iZXIgb2YgdW5rbm93biBQQ0VQDQptZXNzYWdlIi4NCiAgIEEgUkVDT01NRU5E
RUQgdmFsdWUgZm9yIE1BWC1VTktOT1dOLU1FU1NBR0VTIGlzIDUuICBUaGUgUENDL1BDRQ0KTVVT
VA0KICAgY2xvc2UgdGhlIFRDUCBzZXNzaW9uIGFuZCBNVVNUIE5PVCBzZW5kIGFueSBmdXJ0aGVy
IFBDRVAgbWVzc2FnZXMNCm9uDQogICB0aGUgUENFUCBzZXNzaW9uLiINCg0KW0xNXSBJZiBpdCBp
cyB0aGUgY2FzZSwgdGhlIGVycm9yIGhhbmRsaW5nIHdvdWxkIGJlIHRoZSBzYW1lIGJldHdlZW4g
YQ0KUENFUCBzcGVha2VyIHN1cHBvcnRpbmcgdGhlIGZlYXR1cmUgYnV0IG5vdCBhZHZlcnRpemlu
ZyBpdCBhbmQgYSBQQ0VQDQpzcGVha2VyIG5vdCBzdXBwb3J0aW5nIHRoZSBmZWF0dXJlLiBBbmQg
aXQgd291bGQgbm90IGJlIHBvc3NpYmxlDQpwb3NzaWJsZSB0byB1c2UgdGhlIHNwZWNpZmljIGVy
cm9yIHJlc3BvbnNlcyB0byBpbmZlciB0aGUgY2FwYWJpbGl0eQ0Kc3VwcG9ydGVkIGJ5IHRoZSBv
dGhlciBub2RlLg0KDQpKb24+IEknbSBub3Qgc3VyZSB3aGljaCBwYXJ0IG9mIHRoZSBkcmFmdCB5
b3UgYXJlIGNvbW1lbnRpbmcgb24sIGJ1dCBJIGRpc2FncmVlIHdpdGggdGhlIHByZW1pc2UuIElm
IGEgUENFUCBzcGVha2VyIHN1cHBvcnRzIHRoZXNlIGV4dGVuc2lvbnMgYnV0IGRvZXMgbm90IGFk
dmVydGlzZSB0aGUgY2FwYWJpbGl0eSwgdGhlbiB0aGUgbWVzc2FnZXMgYXJlIG5vdCB1bmtub3du
IHRvIGl0LCBpdCBqdXN0IGRvZXMgbm90IHdhbnQgdG8gc2VlIHRoZW0uICBTbyBpdCBpcyBmcmVl
IHRvIGhhbmRsZSB0aGUgZXJyb3IgZGlmZmVyZW50bHkgdG8gdGhlIGRlZmF1bHQgUkZDIDU0NDAg
Y2FzZS4NCg0KPT09PT0NCg0KICAgTm90ZSB0aGF0IGV2ZW4gaWYgdGhlIHVwZGF0ZQ0KICAgY2Fw
YWJpbGl0eSBoYXMgbm90IGJlZW4gYWR2ZXJ0aXNlZCwgYSBQQ0UgY2FuIHN0aWxsIGFjY2VwdCBM
U1ANClN0YXR1cw0KICAgUmVwb3J0cyBmcm9tIGEgUENDIGFuZCBidWlsZCBhbmQgbWFpbnRhaW4g
YW4gdXAgdG8gZGF0ZSB2aWV3IG9mDQp0aGUNCiAgIHN0YXRlIG9mIHRoZSBQQ0MncyBMU1BzLg0K
DQpbTE1dIEkgZG9uJ3QgdW5kZXJzYW5kLiBJcyBpdCBub3QgaW4gY29udHJhZGljdGlvbiB3aXRo
DQoNCiAgIklmIHRoZSBQQ0VQIFNwZWFrZXIgb24gdGhlIFBDRSBzdXBwb3J0cyB0aGUgZXh0ZW5z
aW9ucyBvZg0KICAgdGhpcyBkcmFmdCBidXQgZGlkIG5vdCBhZHZlcnRpc2UgdGhpcyBjYXBhYmls
aXR5LCB0aGVuIHVwb24NCnJlY2VpcHQNCiAgIG9mIGEgUENScHQgbWVzc2FnZSBmcm9tIHRoZSBQ
Q0MsIGl0IE1VU1QgZ2VuZXJhdGUgYSBQQ0VyciB3aXRoDQplcnJvci0NCiAgIHR5cGUgMTkgKElu
dmFsaWQgT3BlcmF0aW9uKSwgZXJyb3ItdmFsdWUgNSAoQXR0ZW1wdGVkIExTUCBTdGF0ZQ0KICAg
UmVwb3J0IGlmIGFjdGl2ZSBzdGF0ZWZ1bCBQQ0UgY2FwYWJpbGl0eSB3YXMgbm90IGFkdmVydGlz
ZWQpIChzZWUNCiAgIFNlY3Rpb24gOC41KSBhbmQgaXQgU0hPVUxEIHRlcm1pbmF0ZSB0aGUgUENF
UCBzZXNzaW9uLiINCg0KT3IgZG9lcyBpdCBtZWFuIHRoYXQgdGhlcmUgaXMgYW5vdGhlciB3YXkg
dGhhbiBQQ1JwdCBtZXNzYWdlIGZvciB0aGUNClBDQyB0byBzZW5kIExTUCBzdGF0dXMgcmVwb3J0
cyB0byB0aGUgUENFPw0KDQpKb24+IEFDSy4gIEkgdGhpbmsgdGhhdCB0aGUgc3RhdGVtZW50IGlu
IHRoZSBkcmFmdCBpcyBib2d1cyBhbmQgSSBwcm9wb3NlIHRvIGRlbGV0ZSB0aGlzIHNlbnRlbmNl
IGZyb20gaXQuDQoNCj09PT09DQoNCltMTV0gSW4gdGhpcyBzZWN0aW9uLCBpdCBpcyBub3QgZGVz
Y3JpYmVkIGhvdyBub24tc3VwcG9ydGluZyBQQ0VQDQpzcGVha2VyIHdpbGwgaGFubGRlZCB0aGUg
bmV3IFRMVi4gSXQgY291bGQgYmUgc2FpZCB0aGF0IHVucmVjb2duaXplZA0KVExWcyB3aWxsIGJl
IGlnbm9yZWQgKGFzIHBlciBSRkM1NDQwKSBhbmQgT1BFTiBtZXNzYWdlcyB3aWxsIGJlDQpoYW5k
bGVkIGFzIHBlciBSRkM1NDQwIChpZiB0aGUgY29tbWVudCBhYm92ZSBpcyBhY2NlcHRlZCkuDQoN
Ckpvbj4gQnV0IEkgZG9uJ3QgdGhpbmsgd2UgbmVlZCB0byBzcGVjaWZ5IGhvdyBhIG5vbi1zdXBw
b3J0aW5nIHNwZWFrZXIgd2lsbCBiZWhhdmUuICBSRkMgNTQ0MCBhbHJlYWR5IGRvZXMgdGhhdC4N
Cg0KPT09PT0NCg0KW0xNXSBXb3VsZCBpdCBiZSB1c2VmdWwgdG8gZGlzY292ZXIgKHVzaW5nIGFu
b3RoZXIgVExWKSB3aGV0aGVyIHRoZQ0KUENFIGlzIGFuIGFjdGl2ZS9wYXNzaXZlIHN0YXRlZnVs
IFBDRSwgYXMgaW4gSUdQLWJhc2VkIGNhcGFiaWxpdGllcw0KZGlzY292ZXJ5IG1lY2hhbmlzbT8N
Cg0KSm9uPiBUaGlzIGNhbiBiZSBpbmZlcnJlZCBpbW1lZGlhdGVseSBmcm9tIHRoZSBVIGZsYWcg
aW4gdGhlIFNUQVRFRlVMLVBDRS1DQVBBQklMSVRZIFRMVi4gIFBhc3NpdmUgbW9kZSBpcyBzeW5v
bnltb3VzIHdpdGggbm90IHNlbmRpbmcgLyBoYW5kbGluZyBQQ1VwZCBtZXNzYWdlcy4NCg0KPT09
PT0NCg0KNS41LiAgSUdQIEV4dGVuc2lvbnMgZm9yIFN0YXRlZnVsIFBDRSBDYXBhYmlsaXRpZXMg
QWR2ZXJ0aXNlbWVudA0KDQogICBXaGVuIFBDQ3MgYXJlIExTUnMgcGFydGljaXBhdGluZyBpbiB0
aGUgSUdQIChPU1BGIG9yIElTLUlTKSwgYW5kDQpQQ0VzDQogICBhcmUgZWl0aGVyIExTUnMgb3Ig
c2VydmVycyBhbHNvIHBhcnRpY2lwYXRpbmcgaW4gdGhlIElHUCwgYW4NCiAgIGVmZmVjdGl2ZSBt
ZWNoYW5pc20gZm9yIFBDRSBkaXNjb3Zlcnkgd2l0aGluIGFuIElHUCByb3V0aW5nIGRvbWFpbg0K
ICAgY29uc2lzdHMgb2YgdXRpbGl6aW5nIElHUCBhZHZlcnRpc2VtZW50cy4NCg0KWy4uLl0NCg0K
ICAgTm90ZSB0aGF0IHdoaWxlIGFjdGl2ZSBhbmQgcGFzc2l2ZSBzdGF0ZWZ1bCBQQ0UgY2FwYWJp
bGl0aWVzIG1heQ0KYmUNCiAgIGFkdmVydGlzZWQgZHVyaW5nIGRpc2NvdmVyeSwgUENFUCBTcGVh
a2VycyB0aGF0IHdpc2ggdG8gdXNlDQpzdGF0ZWZ1bA0KICAgUENFUCBNVVNUIG5lZ290aWF0ZSBz
dGF0ZWZ1bCBQQ0VQIGNhcGFiaWxpdGllcyBkdXJpbmcgUENFUCBzZXNzaW9uDQogICBzZXR1cCwg
YXMgc3BlY2lmaWVkIGluIHRoZSBjdXJyZW50IGRvY3VtZW50LiAgQSBQQ0MgTUFZIGluaXRpYXRl
DQogICBzdGF0ZWZ1bCBQQ0VQIGNhcGFiaWxpdHkgbmVnb3RpYXRpb24gYXQgUENFUCBzZXNzaW9u
IHNldHVwIGV2ZW4gaWYNCml0DQogICBkaWQgbm90IHJlY2VpdmUgYW55IElHUCBQQ0UgY2FwYWJp
bGl0eSBhZHZlcnRpc2VtZW50cy4NCg0KW0xNXSBBcyBzYWlkIGFib3ZlLCBhbiBhcyBzdGF0ZWQg
aW4gc2VjdGlvbiA1LjQ6DQogICJUaGUgUENFUCBleHRlbnNpb25zIGZvciBzdGF0ZWZ1bCBQQ0Vz
IE1VU1QgTk9UIGJlIHVzZWQgaWYgb25lIG9yDQpib3RoDQogICBQQ0VQIFNwZWFrZXJzIGhhdmUg
bm90IGluY2x1ZGVkIHRoZSBTdGF0ZWZ1bCBQQ0UgQ2FwYWJpbGl0eSBUTFYgaW4NCiAgIHRoZWly
IHJlc3BlY3RpdmUgT1BFTiBtZXNzYWdlLiINCg0KV2hhdCBpcyB0aGUgcmVhbCBhZGRlZC12YWx1
ZSBvZiB0aGlzIElHUC1iYXNlZCBtZWNoYW5pc20/IE9ubHkgdG8gYmUNCmFibGUgdG8gaWRlbnRp
ZnkgYWN0aXZlIFBDRS9wYXNzaXZlIFBDRSBtb2RlPw0KDQpKb24+IFllcywgY29ycmVjdC4gIFRo
ZSBQQ0MgbWF5IHByZWZlciB0byB1c2UgYW4gYWN0aXZlIHN0YXRlZnVsIFBDRSwgb3IgbWF5IHdh
bnQgdG8gYXZvaWQgdXNpbmcgb25lLg0KDQo9PT09PQ0KDQo1LjYuICBTdGF0ZSBTeW5jaHJvbml6
YXRpb24NCg0KW0xNXSAiU3RhdGUiIGNvdWxkIGJlIG1pc2xlYWRpbmcuICJMU1AgU3RhdGUgU3lu
YyIgd291bGQgYmUgbW9yZQ0KYXBwcm9yaWF0ZS9hY2N1cmF0ZSBJIHRoaW5rLg0KDQpKb24+IEJ1
dCB0aGUgdmVyeSBmaXJzdCBzZW50ZW5jZSBiZWxvdyBjbGVhcnMgdGhpcyB1cCBpbW1lZGlhdGVs
eSwgc28gSSBkb24ndCB0aGluayBpdCdzIHdvcnRoIGNoYW5naW5nIG5vdy4NCg0KPT09PT0NCg0K
ICAgVGhlIHB1cnBvc2Ugb2YgU3RhdGUgU3luY2hyb25pemF0aW9uIGlzIHRvIHByb3ZpZGUgYQ0K
Y2hlY2twb2ludC1pbi0NCiAgIHRpbWUgc3RhdGUgcmVwbGljYSBvZiBhIFBDQydzIExTUCBzdGF0
ZSBpbiBhIFBDRS4gIFN0YXRlDQogICBTeW5jaHJvbml6YXRpb24gaXMgcGVyZm9ybWVkIGltbWVk
aWF0ZWx5IGFmdGVyIHRoZSBJbml0aWFsaXphdGlvbg0KICAgcGhhc2UgKFtSRkM1NDQwXSkuDQoN
CiAgIER1cmluZyBTdGF0ZSBTeW5jaHJvbml6YXRpb24sIGEgUENDIGZpcnN0IHRha2VzIGEgc25h
cHNob3Qgb2YgdGhlDQogICBzdGF0ZSBvZiBpdHMgTFNQcyBzdGF0ZSwgdGhlbiBzZW5kcyB0aGUg
c25hcHNob3QgdG8gYSBQQ0UgaW4gYQ0KICAgc2VxdWVuY2Ugb2YgTFNQIFN0YXRlIFJlcG9ydHMu
ICBFYWNoIExTUCBTdGF0ZSBSZXBvcnQgc2VudCBkdXJpbmcNCiAgIFN0YXRlIFN5bmNocm9uaXph
dGlvbiBoYXMgdGhlIFNZTkMgRmxhZyBpbiB0aGUgTFNQIE9iamVjdCBzZXQgdG8NCjEuDQogICBU
aGUgc2V0IG9mIExTUHMgZm9yIHdoaWNoIHN0YXRlIGlzIHN5bmNocm9uaXplZCB3aXRoIGEgUENF
IGlzDQogICBkZXRlcm1pbmVkIGJ5IGFkdmVydGlzZWQgc3RhdGVmdWwgUENFUCBjYXBhYmlsaXRp
ZXMgYW5kIFBDQydzDQpsb2NhbA0KICAgY29uZmlndXJhdGlvbiAoc2VlIG1vcmUgZGV0YWlscyBp
biBTZWN0aW9uIDkuMSkuDQoNCltMTV0gSXQgc2VlbXMgdGhhdCA6DQoNCiAgICJUaGUgc2V0IG9m
IExTUHMgZm9yIHdoaWNoIHN0YXRlIGlzIHN5bmNocm9uaXplZCINCg0Kc2hvdWxkIGJlOg0KDQog
ICAiVGhlIHNldCBvZiBMU1BzIGZvciB3aGljaCBzdGF0ZSBpcyB0byBiZSBzeW5jaHJvbml6ZWQi
DQoNCkpvbj4gVG8gbXkgbWluZCB0aGV5IGNhcnJ5IHRoZSBzYW1lIG1lYW5pbmcuDQoNCj09PT09
DQoNCltMTV0gSSBkb24ndCBzZWUgaG93IHRoZSAiYWR2ZXJ0aXNlZCBzdGF0ZWZ1bCBQQ0VQIGNh
cGFiaWxpdGllcyIgaGF2ZQ0KYW4gZWZmZWN0IG9uIHRoZSBzZXQgb2YgTFNQIHRvIHN5bmNocm9u
aXplLiBUaGUgY2FwYWJpbGl0aWVzIGFkdiBpcw0Kb25seSB1c2VkIHRvIGRpc2NvdmVyIHN0YXRl
ZnVsIFBDRSBjYXBhYmlsaXRpZXMgYW5kIHNlZSBpZiB0aGUgcmVsYXRlZA0KUENFUCBleHRlbnNp
b25zIGNhbiBiZSB1c2VkLiBUaGUgaWRlbnRpZmljYXRpb24gb2YgdGhlIExTUHMgdG8NCnN5bmNo
cm9uaXplIHNlZW1zIHRvIGJlIG9ubHkgYmFzZWQgb24gcG9saWNpZXMgY29uZmlndXJlZCBpbiB0
aGUgUENDLg0KDQpKb24+IEFncmVlIHRoaXMgaXMgY29uZnVzaW5nLiBPdGhlciBkb2N1bWVudHMg
ZG8gZGVmaW5lIGNhcGFiaWxpdGllcyB0aGF0IGFmZmVjdCB0aGUgc2V0IG9mIExTUCB0byBzeW5j
aHJvbml6ZSBlLmcuIFtJLUQuaWV0Zi1wY2Utc3RhdGVmdWwtc3luYy1vcHRpbWl6YXRpb25zXSB3
aGljaCBhbGxvd3MgYSBzdWJzZXQgdG8gYmUgcmVzeW5jZWQgaWYgc3RhdGUgaXMgcmV0YWluZWQg
YWNyb3NzIGEgUENFUCBzZXNzaW9uIHJlc2V0LiAgSG93IGFib3V0IHdlIGNoYW5nZSB0aGlzOg0K
DQpPTEQNCiAgIFRoZSBzZXQgb2YgTFNQcyBmb3Igd2hpY2ggc3RhdGUgaXMgc3luY2hyb25pemVk
IHdpdGggYSBQQ0UgaXMNCiAgIGRldGVybWluZWQgYnkgYWR2ZXJ0aXNlZCBzdGF0ZWZ1bCBQQ0VQ
IGNhcGFiaWxpdGllcyBhbmQgUENDJ3MgbG9jYWwNCiAgIGNvbmZpZ3VyYXRpb24gKHNlZSBtb3Jl
IGRldGFpbHMgaW4gU2VjdGlvbiA5LjEpLg0KTkVXDQogICBUaGUgc2V0IG9mIExTUHMgZm9yIHdo
aWNoIHN0YXRlIGlzIHN5bmNocm9uaXplZCB3aXRoIGEgUENFIGlzDQogICBkZXRlcm1pbmVkIGJ5
IHRoZSBQQ0MncyBsb2NhbCBjb25maWd1cmF0aW9uIChzZWUgbW9yZSBkZXRhaWxzIGluIFNlY3Rp
b24gOS4xKQ0KICAgYW5kIE1BWSBhbHNvIGJlIGRldGVybWluZWQgYnkgc3RhdGVmdWwgUENFUCBj
YXBhYmlsaXRpZXMgZGVmaW5lZA0KICAgaW4gb3RoZXIgZG9jdW1lbnRzLCBzdWNoIGFzIFtJLUQu
aWV0Zi1wY2Utc3RhdGVmdWwtc3luYy1vcHRpbWl6YXRpb25zXS4NCkVORCBORVcNCg0KPT09PT0N
Cg0KICAgVGhlIGVuZCBvZiBzeW5jaHJvbml6YXRpb24gbWFya2VyIGlzIGEgUENScHQgbWVzc2Fn
ZSB3aXRoIHRoZSBTWU5DDQogICBGbGFnIHNldCB0byAwIGZvciBhbiBMU1AgT2JqZWN0IHdpdGgg
UExTUC1JRCBlcXVhbCB0byB0aGUgcmVzZXJ2ZWQNCiAgIHZhbHVlIDAgKHNlZSBTZWN0aW9uIDcu
MykuICBJbiB0aGlzIGNhc2UsIHRoZSBMU1AgT2JqZWN0IFNIT1VMRA0KTk9UDQogICBpbmNsdWRl
IHRoZSBTWU1CT0xJQy1QQVRILU5BTUUgVExWIGFuZCBTSE9VTEQgaW5jbHVkZSB0aGUgTFNQLQ0K
ICAgSURFTlRJRklFUlMgVExWIHdpdGggdGhlIHNwZWNpYWwgdmFsdWUgb2YgYWxsIHplcm9lcy4g
IFRoZSBQQ1JwdA0KICAgbWVzc2FnZSBNVVNUIGluY2x1ZGUgYW4gZW1wdHkgRVJPIGFzIGl0cyBp
bnRlbmRlZCBwYXRoIGFuZCBTSE9VTEQNCk5PVA0KICAgaW5jbHVkZSB0aGUgb3B0aW9uYWwgUlJP
IG9iamVjdCBmb3IgaXRzIGFjdHVhbCBwYXRoLg0KDQpbTE1dIFdoYXQgaXMgdGhlIHJlYXNvbiBm
b3IgdGhlIHVzZSBvZiAiU0hPVUxEIiBoZXJlLCBpbnN0ZWFkIG9mDQoiTVVTVCI/DQoNCiAgIElm
IHRoZSBQQ0MgaGFzDQogICBubyBzdGF0ZSB0byBzeW5jaHJvbml6ZSwgaXQgU0hPVUxEIG9ubHkg
c2VuZCB0aGUgZW5kIG9mDQogICBzeW5jaHJvbml6YXRpb24gbWFya2VyLg0KDQpbTE1dIElzIGl0
IHdoZW4gdGhlcmUgaXMgbm8gYWN0aXZlIExTUD8gSWYgaXQgaXMsIGl0IGNvdWxkIGJlIHVzZWZ1
bA0KdG8gY2xhcmlmeSBpdC4gQW5kIGl0IGlzIG1heWJlIG5vdCBzbyByZWxhdGVkIHRvIHRoZSB0
ZXh0IGp1c3QgYmVmb3JlLg0KSXQgY291bGQgYmUgY2xhcmlmaWVkIGluIGEgc2VwYXJhdGUgcGFy
YWdyYXBoLg0KDQpKb24+IEFzIGRpc2N1c3NlZCBhYm92ZSwgbG9jYWwgcG9saWN5IHBsdXMgY2Fw
YWJpbGl0aWVzIG1heSBhZmZlY3QgdGhlIHNldCBvZiBMU1BzIHRoYXQgYXJlIHN5bmNocm9uaXpl
ZC4gIFNvIEkgdGhpbmsgIm5vIHN0YXRlIHRvIHN5bmNocm9uaXplIiBpcyBtb3JlIGFjY3VyYXRl
IHRoYXQgIm5vIGFjdGl2ZSBMU1BzIi4NCg0KPT09PQ0KDQogICBBIFBDRSBTSE9VTEQgTk9UIHNl
bmQgUENVcGQgbWVzc2FnZXMgdG8gYSBQQ0MgYmVmb3JlIFN0YXRlDQogICBTeW5jaHJvbml6YXRp
b24gaXMgY29tcGxldGUuICBBIFBDQyBTSE9VTEQgTk9UIHNlbmQgUENSZXEgbWVzc2FnZXMNCnRv
DQogICBhIFBDRSBiZWZvcmUgU3RhdGUgU3luY2hyb25pemF0aW9uIGlzIGNvbXBsZXRlLiAgVGhp
cyBpcyB0byBhbGxvdw0KdGhlDQogICBQQ0UgdG8gZ2V0IHRoZSBiZXN0IHBvc3NpYmxlIHZpZXcg
b2YgdGhlIG5ldHdvcmsgYmVmb3JlIGl0IHN0YXJ0cw0KICAgY29tcHV0aW5nIG5ldyBwYXRocy4N
Cg0KW0xNXSBpdCBpcyBvYnZpb3VzbHkgYXNzdW1lZCB0aGF0IHRoaXMgcmVxdWlyZW1lbnQgaXMg
dHJ1ZSBmb3IgUENDL1BDRQ0KZXhwbGljaXRseSBhZHZlcnRpemluZyBzdXBwb3J0IG9mIHN0YXRl
ZnVsIFBDRSBjYXBhYmlsaXR5Lg0KDQoNCiAgIElmIHRoZSBQQ0MgZW5jb3VudGVycyBhIHByb2Js
ZW0gd2hpY2ggcHJldmVudHMgaXQgZnJvbSBjb21wbGV0aW5nDQp0aGUNCiAgIHN0YXRlIHRyYW5z
ZmVyLCBpdCBNVVNUIHNlbmQgYSBQQ0VyciBtZXNzYWdlIHdpdGggZXJyb3ItdHlwZSAyMA0KKExT
UA0KICAgU3RhdGUgU3luY2hyb25pemF0aW9uIEVycm9yKSBhbmQgZXJyb3ItdmFsdWUgNSAoaW5k
aWNhdGluZyBhbg0KICAgaW50ZXJuYWwgUENDIGVycm9yKSB0byB0aGUgUENFIGFuZCB0ZXJtaW5h
dGUgdGhlIHNlc3Npb24uDQoNCltMTV0gcy9zdGF0ZSB0cmFuc2Zlci9MU1Agc3RhdGUgc3luY2hv
cm5pemF0aW9uDQoNCkpvbj4gQUNLDQoNCj09PT09DQoNCjUuNy4xLiAgRGVsZWdhdGluZyBhbiBM
U1ANCg0KICAgQSBQQ0MgZGVsZWdhdGVzIGFuIExTUCB0byBhIFBDRSBieSBzZXR0aW5nIHRoZSBE
ZWxlZ2F0ZSBmbGFnIGluDQpMU1ANCiAgIFN0YXRlIFJlcG9ydCB0byAxLiAgSWYgdGhlIFBDRSBk
b2VzIG5vdCBhY2NlcHQgdGhlIExTUCBEZWxlZ2F0aW9uLA0KaXQNCiAgIE1VU1QgaW1tZWRpYXRl
bHkgcmVzcG9uZCB3aXRoIGFuIGVtcHR5IExTUCBVcGRhdGUgUmVxdWVzdCB3aGljaA0KaGFzDQog
ICB0aGUgRGVsZWdhdGUgZmxhZyBzZXQgdG8gMC4gIElmIHRoZSBQQ0UgYWNjZXB0cyB0aGUgTFNQ
DQpEZWxlZ2F0aW9uLA0KICAgaXQgTVVTVCBzZXQgdGhlIERlbGVnYXRlIGZsYWcgdG8gMSB3aGVu
IGl0IHNlbmRzIGFuIExTUCBVcGRhdGUNCiAgIFJlcXVlc3QgZm9yIHRoZSBkZWxlZ2F0ZWQgTFNQ
IChub3RlIHRoYXQgdGhpcyBtYXkgb2NjdXIgYXQgYSBsYXRlcg0KICAgdGltZSkuICBUaGUgUENF
IE1BWSBhbHNvIGltbWVkaWF0ZWx5IGFja25vd2xlZGdlIGEgZGVsZWdhdGlvbiBieQ0KICAgc2Vu
ZGluZyBhbiBlbXB0eSBMU1AgVXBkYXRlIFJlcXVlc3Qgd2hpY2ggaGFzIHRoZSBEZWxlZ2F0ZSBm
bGFnDQpzZXQNCiAgIHRvIDEuDQoNCltMTV0gaWYgdGhlIGRlbGVnYXRpb24gaXMgbm90IGFjZWVw
dGVkIGJ5IHRoZSBQQ0UsIEkgYXNzdW1lIHRoYXQgdGhlDQpQQ0Mgc2hvdWxkIG5vdCBzZXQgdGhl
IERlbGVnYXRlIGZsYWcgaW4gc3Vic2VxdWVudCBMU1Agc3RhdGUgcmVwb3J0Lg0KSWYgaXQgaXMs
IHRoaXMgY291bGQgYmUgY2xhcmlmaWVkIHNvbWV3aGVyZSBpbiB0aGlzIHNlY3Rpb24uDQoNCkpv
bj4gSSBkb24ndCB0aGluayB0aGlzIG1lYW5zIHRoZSBkZWxlZ2F0aW9uIGlzIHBlcm1hbmVudGx5
IHJlZnVzZWQgLSBJIHRoZSBQQ0MgY291bGQgc3RpbGwgcmV0cnkgdGhlIGRlbGVnYXRpb24uDQoN
Cj09PT09DQoNClsuLl0NCg0KICAgTm90ZSB0aGF0IGZvciBhbiBMU1AgdG8gcmVtYWluIGRlbGVn
YXRlZCB0byBhIFBDRSwgdGhlIFBDQyBNVVNUDQpzZXQNCiAgIHRoZSBEZWxlZ2F0ZSBmbGFnIHRv
IDEgb24gZWFjaCBMU1AgU3RhdHVzIFJlcG9ydCBzZW50IHRvIHRoZSBQQ0UuDQoNCltMTV0gcy9l
YWNoIExTUCBTdGF0dXMgUmVwb3J0L2VhY2ggTFNQIFN0YXRlIFJlcG9ydCBmb3IgdGhpcyBMU1Au
DQoNCkpvbj4gQUNLDQoNCj09PT09DQoNCjUuNy4yLjEuICBFeHBsaWNpdCBSZXZvY2F0aW9uDQoN
CiAgIFdoZW4gYSBQQ0MgZGVjaWRlcyB0aGF0IGEgUENFIGlzIG5vIGxvbmdlciBwZXJtaXR0ZWQg
dG8gbW9kaWZ5IGFuDQogICBMU1AsIGl0IHJldm9rZXMgdGhhdCBMU1AncyBkZWxlZ2F0aW9uIHRv
IHRoZSBQQ0UuICBBIFBDQyBtYXkNCnJldm9rZQ0KICAgYW4gTFNQIGRlbGVnYXRpb24gYXQgYW55
IHRpbWUgZHVyaW5nIHRoZSBMU1AncyBsaWZlIHRpbWUuICBBIFBDQw0KICAgcmV2b2tpbmcgYW4g
TFNQIGRlbGVnYXRpb24gTUFZIGltbWVkaWF0ZWx5IGNsZWFyIHRoZSBMU1Agc3RhdGUNCiAgIHBy
b3ZpZGVkIGJ5IHRoZSBQQ0UsIGJ1dCB0byBhdm9pZCB0cmFmZmljIGxvc3MsIGl0IFNIT1VMRCBk
byBzbyBpbg0KYQ0KICAgbWFrZS1iZWZvcmUtYnJlYWsgZmFzaGlvbi4NCg0KW0xNXSBBZnRlciBQ
Q0UgZGVsZWdhdGlvbiByZXZvY2F0aW9uLCBpcyB0aGVyZSByZWFsbHkgYSByZXF1aXJlbWVudA0K
Zm9yIExTUCBzdGF0ZSBjbGVhbi11cD8gVGhlIHJldm9jYXRpb24gaXMgdXNlZCB0byByZW1vdmUg
dGhlDQphdXRob3JpemF0aW9uIG9mIExTUCBzdGF0ZSB1cGRhdGUgdG8gdGhlIFBDRSBidXQgSSBk
b24ndCBzZWUgd2h5IHRoZQ0KUENDIHdvdWxkIGNsZWFyIExTUCBzdGF0ZSBhZnRlciByZXZvY2F0
aW9uLiBUaGUgTFNQIHN0YXRlIGNhbiBiZQ0KdXBkYXRlZCB1c2luZyBvcGVyYXRvci1kZWZpbmVk
IGRlZmF1bHQgcGFyYW1ldGVycywgcmlnaHQ/DQoNCkpvbj4gQ29ycmVjdCwgdGhpcyB0ZXh0IG1l
YW5zIHRvIHNheSB0aGF0IHRoZSBQQ0MgIk1BWSByZW1vdmUgdGhlIHVwZGF0ZWQgcGFyYW1ldGVy
cyBwcm92aWRlZCBieSB0aGUgUENFIGFuZCByZXZlcnQgdG8gdGhlIG9wZXJhdG9yLWRlZmluZWQg
cGFyYW1ldGVycyIuICBJIHdpbGwgdXBkYXRlIHRoZSB0ZXh0Lg0KDQo9PT09PQ0KDQogICBJZiB0
aGUgUENDIGhhcyByZWNlaXZlZCBidXQgbm90IHlldCBhY3RlZA0KICAgb24gUENVcGQgbWVzc2Fn
ZXMgZnJvbSB0aGUgUENFIGZvciB0aGUgTFNQIHdob3NlIGRlbGVnYXRpb24gaXMNCmJlaW5nDQog
ICByZXZva2VkLCB0aGVuIGl0IFNIT1VMRCBpZ25vcmUgdGhlc2UgUENVcGQgbWVzc2FnZXMgd2hl
bg0KcHJvY2Vzc2luZw0KICAgdGhlIG1lc3NhZ2UgcXVldWUuICBBbGwgZWZmZWN0cyBvZiBhbGwg
bWVzc2FnZXMgZm9yIHdoaWNoDQpwcm9jZXNzaW5nDQogICBzdGFydGVkIGJlZm9yZSB0aGUgcmV2
b2NhdGlvbiB0b29rIHBsYWNlIE1VU1QgYmUgYWxsb3dlZCB0bw0KY29tcGxldGUNCiAgIGFuZCB0
aGUgcmVzdWx0IE1VU1QgYmUgZ2l2ZW4gdGhlIHNhbWUgdHJlYXRtZW50IGFzIGFueSBMU1AgdGhh
dA0KaGFkDQogICBiZWVuIHByZXZpb3VzbHkgZGVsZWdhdGVkIHRvIHRoZSBQQ0UgKGUuZy4gdGhl
IHN0YXRlIE1BWSBiZQ0KICAgaW1tZWRpYXRlbHkgY2xlYXJlZCkuDQoNCltMTV0gSWYgSSBjb3Jy
ZWN0bHkgdW5kZXJzdG9vZCB0aGUgdGV4dCBhYm92ZSwgYWZ0ZXIgcmV2b2NhdGlvbiBvZiB0aGUN
ClBDRSBkZWxlZ2F0aW9uLA0KLSBhbnkgUENVcGQgc2hvdWxkIGJlIHJlamVjdGVkIGFuZCBub3Qg
aWdub3JlZA0KLSB0aGUgTFNQIHN0YXRlKHMpIHRoYXQgd2FzIGRlbGVnYXRlZCB0byB0aGUgUENF
IGNhbm5vdCBiZSBjaGFuZ2VkDQp1bnRpbCBhbGwgdGhlIG1lc3NhZ2VzIGluIHRoZSBtZXNzYWdl
IHF1ZXVlIGhhdmUgYmVlbiBwcm9jZXNzZWQuDQoNCklmIEknbSBjb3JyZWN0LCB0aGUgdGV4dCBh
Ym92ZSBjb3VsZCBiZSBjbGFyaWZpZWQuDQoNCkpvbj4gTm8sIHRoZSBzdGF0ZW1lbnQgaXM6DQot
IGFueSBQQ1VwZCB3aGljaCB0aGUgUENDIHN0YXJ0ZWQgcHJvY2Vzc2luZyBiZWZvcmUgcmV2b2Nh
dGlvbiB0b29rIHBsYWNlIFNIT1VMRCBiZSBwcm9jZXNzZWQgdG8gY29tcGxldGlvbiBiZWZvcmUg
dGhlIFBDRS1wcm92aWRlZCBzdGF0ZSBpcyByZW1vdmVkDQotIGFsbCBvdGhlciBQQ1VwZCBTSE9V
TEQgYmUgaWdub3JlZC4NCg0KPT09PT0NCg0KICAgQW55IGZ1cnRoZXIgUENVcGQgbWVzc2FnZXMg
ZnJvbSB0aGUgUENFIGFyZQ0KICAgaGFuZGxlZCBhY2NvcmRpbmcgdG8gdGhlIFBDVXBkIHByb2Nl
ZHVyZXMgZGVzY3JpYmVkIGluIHRoaXMNCmRvY3VtZW50Lg0KDQpbTE1dIE5vdCB1bmRlcnN0b29k
LiBGdXJ0aGVyIFBDVXBkICJ3aWxsIHJlc3VsdCBpbiB0aGUgUENDIHNlbmRpbmcgYQ0KUENFcnIg
bWVzc2FnZSIgYXMgc2FpZCBhZnRlciB0aGUgZmlndXJlLg0KDQpKb24+IFlvdSdyZSBjb3JyZWN0
Lg0KDQo9PT09PQ0KDQo1LjcuMi4yLiAgUmV2b2NhdGlvbiBvbiBSZWRlbGVnYXRpb24gVGltZW91
dA0KDQogICBXaGVuIGEgUENDJ3MgUENFUCBzZXNzaW9uIHdpdGggYSBQQ0UgdGVybWluYXRlcyB1
bmV4cGVjdGVkbHksIHRoZQ0KUENDDQogICBNVVNUIHdhaXQgdGhlIHRpbWUgaW50ZXJ2YWwgc3Bl
Y2lmaWVkIGluIFJlZGVsZWdhdGlvbiBUaW1lb3V0DQogICBJbnRlcnZhbCBiZWZvcmUgcmV2b2tp
bmcgTFNQIGRlbGVnYXRpb25zIHRvIHRoYXQgUENFIGFuZA0KYXR0ZW1wdGluZw0KICAgdG8gcmVk
ZWxlZ2F0ZSBMU1BzIHRvIGFuIGFsdGVybmF0ZSBQQ0UuICBJZiBhIFBDRVAgc2Vzc2lvbiB3aXRo
DQp0aGUNCiAgIG9yaWdpbmFsIFBDRSBjYW4gYmUgcmVlc3RhYmxpc2hlZCBiZWZvcmUgdGhlIFJl
ZGVsZWdhdGlvbiBUaW1lb3V0DQogICBJbnRlcnZhbCB0aW1lciBleHBpcmVzLCBMU1AgZGVsZWdh
dGlvbnMgdG8gdGhlIFBDRSByZW1haW4gaW50YWN0Lg0KDQpbTE1dIEluIGNhc2Ugb2YgUENFUCBz
ZXNzaW9uIGludGVycnVwdGlvbiwgaXMgdGhlcmUgYSByZXF1aXJlbWVudCBmb3INCnRoZSBQQ0Ug
dG8gdXBkYXRlIGRlbGVnYXRlZCBMU1Agc3RhdGVzIGluIG9yZGVyIHRvIGVuc3VyZSB0aGUNCnN5
bmNocm9uaXphdGlvbiBiZXR3ZWVuIHN0YXRlcyBpbiB0aGUgUENFIGFuZCBpbiB0aGUgUENDPw0K
DQpKb24+IE9uY2UgdGhlIFBDRVAgc2Vzc2lvbiBpcyByZS1lc3RhYmxpc2hlZCwgdGhlIFBDQyB3
aWxsIGF1ZGl0IGFsbCBjdXJyZW50IHN0YXRlIHRvIHRoZSBQQ0UsIGFuZCB0aGVuIHRoZSBQQ0Ug
aXMgZnJlZSB0byB1cGRhdGUgYW55IGRlbGVnYXRlZCBMU1AgaWYgaXQgZmluZHMgYSBtaXNtYXRj
aCBiZXR3ZWVuIGl0cyBkZXNpcmVkIHN0YXRlIGFuZCB0aGUgY3VycmVudCBMU1Agc3RhdGUuDQoN
Cj09PT09DQoNCiAgIExpa2V3aXNlLCB3aGVuIGEgUENDJ3MgUENFUCBzZXNzaW9uIHdpdGggYSBQ
Q0UgdGVybWluYXRlcw0KICAgdW5leHBlY3RlZGx5LCB0aGUgUENDIE1VU1Qgd2FpdCBmb3IgdGhl
IFN0YXRlIFRpbWVvdXQgSW50ZXJ2YWwNCmJlZm9yZQ0KICAgZmx1c2hpbmcgYW55IExTUCBzdGF0
ZSBhc3NvY2lhdGVkIHdpdGggdGhhdCBQQ0UuDQoNCltMTV0gaXQgc2hvdWxkIGJlIGNsYXJpZmll
ZCB0aGF0IHRoZSAiZmx1c2hpbmciIGFwcGxpZXMgb25seSBpZiB0aGVyZQ0KaXMgbm8gb3RoZXIg
UENFLiBPdGhlcndpc2UsIHNlZSBzZWN0aW9uIDUuNy40DQoNCkpvbj4gQUNLDQoNCj09PT09DQoN
CiAgIE5vdGUgdGhhdCB0aGUgU3RhdGUNCiAgIFRpbWVvdXQgSW50ZXJ2YWwgdGltZXIgbWF5IGV4
cGlyZSBiZWZvcmUgdGhlIFBDQyBoYXMgcmVkZWxlZ2F0ZWQNCnRoZQ0KICAgTFNQcyB0byBhbm90
aGVyIFBDRSwgZm9yIGV4YW1wbGUgaWYgYSBQQ0MgaXMgbm90IGNvbm5lY3RlZCB0byBhbnkNCiAg
IGFjdGl2ZSBzdGF0ZWZ1bCBQQ0Ugb3IgaWYgbm8gY29ubmVjdGVkIGFjdGl2ZSBzdGF0ZWZ1bCBQ
Q0UgYWNjZXB0cw0KICAgdGhlIGRlbGVnYXRpb24uDQoNCltMTV0gTm90IHN1cmUgdG8gdW5kZXJz
dGFuZC4gSXMgaXQgImlmIGEgUENDIGlzIG5vdCBjb25uZWN0ZWQgdG8gYW55DQpPVEhFUiBhY3Rp
dmUgc3RhdGVmdWwgUENFIG9yIGlmIG5vIE9USEVSIGNvbm5lY3RlZCBhY3RpdmUgc3RhdGVmdWwg
UENFDQphY2NlcHRzIHRoZSBkZWxlZ2F0aW9uPw0KDQpKb24+IFllcyB0aGF0J3MgcmlnaHQsIGJ1
dCB0aGUgd29yZCAib3RoZXIiIHNlZW1zIHJlZHVuZGFudCB0byBtZS4gIFRoZSBvcmlnaW5hbCBz
ZXNzaW9uIGhhcyBkaXNjb25uZWN0ZWQgYWxyZWFkeSBzbyBpdCBpcyBhdXRvbWF0aWNhbGx5IGV4
Y2x1ZGVkIGJ5IHRoaXMgc2VudGVuY2UuDQoNCj09PT09PQ0KDQogICBJbiB0aGlzIGNhc2UsIHRo
ZSBQQ0MgTVVTVCBmbHVzaCBhbnkgTFNQIHN0YXRlIHNldA0KICAgYnkgdGhlIFBDRSB1cG9uIGV4
cGlyYXRpb24gb2YgdGhlIFN0YXRlIFRpbWVvdXQgSW50ZXJ2YWwgYW5kDQpyZXZlcnQNCiAgIHRv
IG9wZXJhdG9yLWRlZmluZWQgZGVmYXVsdCBwYXJhbWV0ZXJzIG9yIGJlaGF2aW9ycy4gIFRoaXMN
Cm9wZXJhdGlvbg0KICAgU0hPVUxEIGJlIGRvbmUgaW4gYSBtYWtlLWJlZm9yZS1icmVhayBmYXNo
aW9uLg0KDQpbTE1dIEkgdGhpbmsgaXQgaXMgaW1wb3J0YW50IHRvIG1ha2UgdGhlIGRpc3RpbmN0
aW9uIGJldHdlZW4gUENDIHdpdGgNCm9ubHkgb25lIFBDRSBhbmQgUENDIHdpdGggTiBQQ0UuIFRo
ZSAiTm90ZSB0aGF0IiBjb3VsZCBiZSBwdXQgaW4gYQ0Kc2VwYXJhdGUgc2VjdGlvbi4NCg0KSm9u
PiBUaGlzIHNlbnRlbmNlIGFwcGxpZXMgdG8gYm90aCBjYXNlcyAtIGlmIHRoZSBMU1AgY2FuJ3Qg
YmUgcmVkZWxlZ2F0ZWQgKGVpdGhlciBiZWNhdXNlIHRoZXJlIHdhcyBvbmx5IDEgUENFIG9yIGJl
Y2F1c2UgdGhlIG90aGVyIE4tMSBQQ0VzIGhhdmUgcmVmdXNlZCB0aGUgZGVsZWdhdGlvbikgdGhl
biB0aGlzIGlzIHdoYXQgdGhlIFBDQyBtdXN0IGRvLiAgSSBkb24ndCBzZWUgd2h5IHdlIG5lZWQg
dG8gZGlzdGluZ3Vpc2ggdGhlc2UgY2FzZXMuDQoNCj09PT09DQoNCiAgIFRoZSBTdGF0ZSBUaW1l
b3V0IEludGVydmFsIE1VU1QgYmUgZ3JlYXRlciB0aGFuIG9yIGVxdWFsIHRvIHRoZQ0KICAgUmVk
ZWxlZ2F0aW9uIFRpbWVvdXQgSW50ZXJ2YWwgYW5kIE1BWSBiZSBzZXQgdG8gaW5maW5pdHkgKG1l
YW5pbmcNCiAgIHRoYXQgdW50aWwgdGhlIFBDQyBzcGVjaWZpY2FsbHkgdGFrZXMgYWN0aW9uIHRv
IGNoYW5nZSB0aGUNCnBhcmFtZXRlcnMNCiAgIHNldCBieSB0aGUgUENFLCB0aGV5IHdpbGwgcmVt
YWluIGludGFjdCkuDQoNCltMTV0gcmVhZGluZyAidGhlIFN0YXRlIFRpbWVvdXQgSW50ZXJ2YWwg
dGltZXIgbWF5IGV4cGlyZSBiZWZvcmUgdGhlDQpQQ0MgaGFzIHJlZGVsZWdhdGVkIHRoZSBMU1Bz
IHRvIGFub3RoZXIgUENFIiBjb3VsZCBiZSB1bmRlcnN0b29kIGFzDQpTVEkgdGltZXIgPCBSVEkg
dGltZXIuIEFuZCBoZXJlLCBpdCBpcyBzdGF0ZWQgU1RJIHRpbWVyID49IFJUSSB0aW1lci4NCkRl
cGVuZGluZyBvbiB0aGUgY2xhcmlmaWNhdGlvbiBvbiB0aGUgcHJldmlvdXMgY29tbWVudCwgdGhp
cyB0ZXh0DQpjb3VsZCBiZSBhbHNvIGNsYXJpZmllZCAob3Igbm90KQ0KDQpKb24+IFRoZSBQQ0Mg
c3RhcnRzIHJlZGVsZWdhdGluZyB0aGUgTFNQIHdoZW4gdGhlIFJUSSB0aW1lciBleHBpcmVzIGJ1
dCB0aGlzIGlzIG5vdCBpbnN0YW50YW5lb3VzLiAgSXQgaXMgcG9zc2libGUgdGhhdCB0aGUgU1RJ
IHRpbWVyIGV4cGlyZXMgYmVmb3JlIHJlZGVsZWdhdGlvbiBoYXMgc3VjY2VlZGVkLiAgU28gSSBk
b24ndCB0aGluayB0aGVyZSdzIGEgY29udHJhZGljdGlvbi4NCg0KPT09PT0NCg0KNS43LjMuICBS
ZXR1cm5pbmcgYSBEZWxlZ2F0aW9uDQoNCiAgIEluIG9yZGVyIHRvIGtlZXAgYSBkZWxlZ2F0aW9u
LCBhIFBDRSBNVVNUIHNldCB0aGUgRGVsZWdhdGUgZmxhZyB0bw0KMQ0KICAgb24gZWFjaCBMU1Ag
VXBkYXRlIFJlcXVlc3Qgc2VudCB0byB0aGUgUENDLiAgQSBQQ0UgdGhhdCBubyBsb25nZXINCiAg
IHdpc2hlcyB0byB1cGRhdGUgYW4gTFNQJ3MgcGFyYW1ldGVycyBTSE9VTEQgcmV0dXJuIHRoZSBM
U1ANCmRlbGVnYXRpb24NCiAgIGJhY2sgdG8gdGhlIFBDQyBieSBzZW5kaW5nIGFuIGVtcHR5IExT
UCBVcGRhdGUgUmVxdWVzdCB3aGljaCBoYXMNCnRoZQ0KICAgRGVsZWdhdGUgZmxhZyBzZXQgdG8g
MC4gIElmIGEgUENDIHJlY2VpdmVzIGFuIExTUCBVcGRhdGUgUmVxdWVzdA0Kd2l0aA0KICAgdGhl
IERlbGVnYXRlIGZsYWcgc2V0IHRvIDAgKHdoZXRoZXIgdGhlIExTUCBVcGRhdGUgUmVxdWVzdCBp
cw0KZW1wdHkNCiAgIG9yIG5vdCksIGl0IE1VU1QgdHJlYXQgdGhpcyBhcyBhIGRlbGVnYXRpb24g
cmV0dXJuLg0KDQogICAgICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgICAg
Ky0rLSsNCiAgICAgICAgICAgICAgICAgICAgIHxQQ0N8ICAgICAgICAgICAgICAgICAgICB8UENF
fA0KICAgICAgICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICAgICstKy0rDQog
ICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICAg
ICAgICAgICAgICAgICAgIHwtLS1QQ1JwdCwgRGVsZWdhdGU9MS0tLT58IExTUCBkZWxlZ2F0ZWQN
CiAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgIC4gICAgICAgICAgIHwNCiAgICAg
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgIC4gICAgICAgICAgIHwNCiAgICAgICAgICAg
ICAgICAgICAgICAgfCAgICAgICAgICAgIC4gICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAg
ICAgICAgfDwtLVBDVXBkLCBEZWxlZ2F0ZT0wLS0tLXwgRGVsZWdhdGlvbiByZXR1cm5lZA0KICAg
ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAg
ICAgICAgICAgICAgICB8LS0tUENScHQsIERlbGVnYXRlPTAtLS0+fCBObyBkZWxlZ2F0aW9uIGZv
cg0KTFNQDQogICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICB8
DQoNCiAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSA2OiBSZXR1cm5pbmcgYSBEZWxlZ2F0aW9u
DQoNCiAgIElmIGEgUENDIGNhbm5vdCBkZWxlZ2F0ZSBhbiBMU1AgdG8gYSBQQ0UgKGZvciBleGFt
cGxlLCBpZiBhIFBDQyBpcw0KICAgbm90IGNvbm5lY3RlZCB0byBhbnkgYWN0aXZlIHN0YXRlZnVs
IFBDRSBvciBpZiBubyBjb25uZWN0ZWQgYWN0aXZlDQogICBzdGF0ZWZ1bCBQQ0UgYWNjZXB0cyB0
aGUgZGVsZWdhdGlvbiksIHRoZSBMU1AgZGVsZWdhdGlvbiBvbiB0aGUNClBDQw0KICAgd2lsbCB0
aW1lIG91dCB3aXRoaW4gYSBjb25maWd1cmFibGUgUmVkZWxlZ2F0aW9uIFRpbWVvdXQgSW50ZXJ2
YWwNCmFuZA0KICAgdGhlIFBDQyBNVVNUIGZsdXNoIGFueSBMU1Agc3RhdGUgc2V0IGJ5IGEgUENF
IGF0IHRoZSBleHBpcmF0aW9uIG9mDQogICB0aGUgU3RhdGUgVGltZW91dCBJbnRlcnZhbC4NCg0K
W0xNXSBzYW1lIGNvbW1lbnQ6IGlzIGl0ICJmb3IgZXhhbXBsZSwgaWYgYSBQQ0MgaXMgbm90IGNv
bm5lY3RlZCB0bw0KYW55IE9USEVSIGFjdGl2ZSBzdGF0ZWZ1bCBQQ0Ugb3IgaWYgbm8gT1RIRVIg
Y29ubmVjdGVkIGFjdGl2ZSBzdGF0ZWZ1bA0KUENFIGFjY2VwdHMgdGhlIGRlbGVnYXRpb24iPw0K
DQpKb24+IEFzIGJlZm9yZSwgeWVzLCBhbmQgSSBkb24ndCB0aGluayB0aGUgd29yZCAib3RoZXIi
IGFkZHMgYW55dGhpbmcuDQoNCj09PT09DQoNCltMTV0gInRoZSBQQ0MgTVVTVCBmbHVzaCBhbnkg
TFNQIHN0YXRlIHNldCIgc2hvdWxkIGJlIGNvbXBsZXRlZCBieQ0KImFuZCByZXZlcnQgdG8gb3Bl
cmF0b3ItZGVmaW5lZCBkZWZhdWx0IHBhcmFtZXRlcnMgb3IgYmVoYXZpb3JzIiwNCnJpZ2h0Pw0K
DQpKb24+IENvcnJlY3QsIHdpbGwgdXBkYXRlLg0KDQo9PT09PQ0KDQo1LjcuNS4gIFJlZGVsZWdh
dGlvbiBvbiBQQ0UgRmFpbHVyZQ0KDQpbLi4uXQ0KDQogICBJZiB0aGUgUENFIGNyYXNoZXMgYnV0
IHJlY292ZXJzIHdpdGhpbiB0aGUgUmVkZWxlZ2F0aW9uIFRpbWVvdXQsDQpib3RoDQogICB0aGUg
ZGVsZWdhdGlvbiBzdGF0ZSBhbmQgdGhlIExTUCBzdGF0ZSBhcmUga2VwdCBpbnRhY3QuDQoNCltM
TV0gIlJlY292ZXIiIGhlcmUgc2VlbXMgdG8gYmUgYXNzb2NpYXRlZCB3aXRoIHRoZSBQQ0VQIHNl
c3Npb24gKGFzDQpsaW5rZWQgdG8gdGhlIFJlZGVsZWdhdGlvbiBUaW1lb3V0KSwgbm90IHdpdGgg
dGhlIExTUCBzdGF0ZXMNCm1haW50YWluZWQgYnkgdGhlIFBDRS4NCg0KSm9uPiBDb3JyZWN0DQoN
Cj09PT09DQoNCltMTV0gSG93IGNhbiB0aGUgUENDIGJlIGVuc3VyZWQgdGhhdCB0aGUgUENFIGhh
cyBub3QgYmVlbiBpbXBhY3RlZCBieQ0KdGhlIHN0b3AvcmVzdGFydCBhbmQgdGhhdCBMU1Agc3Rh
dGVzIGFyZSBpbnRhY3Q/IElzIHRoZXJlIGFueSBuZWVkIGZvcg0KYSBzYW5pdHkgY2hlY2s/DQoN
Ckpvbj4gVGhlIHNhbml0eSBjaGVjayBoYXBwZW5zIHdoZW4gdGhlIFBDQyBhdWRpdHMgYWxsIGl0
cyBMU1Agc3RhdGUgdG8gdGhlIFBDRSBhZnRlciB0aGUgc2Vzc2lvbiByZXN0YXJ0cy4NCg0KPT09
PT0NCg0KICAgSWYgdGhlIFBDRSBjcmFzaGVzIGJ1dCBkb2VzIG5vdCByZWNvdmVyIHdpdGhpbiB0
aGUgUmVkZWxlZ2F0aW9uDQogICBUaW1lb3V0LCB0aGUgZGVsZWdhdGlvbiBzdGF0ZSBpcyByZXR1
cm5lZCB0byB0aGUgUENDLiAgSWYgdGhlIFBDQw0KY2FuDQogICByZWRlbGVnYXRlIHRoZSBMU1Bz
IHRvIGFub3RoZXIgUENFLCBhbmQgdGhhdCBQQ0UgYWNjZXB0cyB0aGUNCiAgIGRlbGVnYXRpb25z
LCB0aGVyZSB3aWxsIGJlIG5vIGNoYW5nZSBpbiBMU1Agc3RhdGUuICBJZiB0aGUgUENDDQpjYW5u
b3QNCiAgIHJlZGVsZWdhdGUgdGhlIExTUHMgdG8gYW5vdGhlciBQQ0UsIHRoZW4gdXBvbiBleHBp
cmF0aW9uIG9mIHRoZQ0KU3RhdGUNCiAgIFRpbWVvdXQgSW50ZXJ2YWwsIHRoZSBzdGF0ZSBzZXQg
YnkgdGhlIFBDRSBpcyBmbHVzaGVkLCB3aGljaCBtYXkNCiAgIGNhdXNlIGNoYW5nZSBpbiB0aGUg
TFNQIHN0YXRlLg0KDQpbTE1dIHRoZSBsYXN0IHNlbnRlbmNlIGlzIGRpZmZpY3VsdCB0byB1bmRl
cnN0YW5kLiBIb3cgdG8gdW5kZXJzdGFuZA0KImZsdXNoIHRoZSBzdGF0ZSBNQVkgY2F1c2UgY2hh
bmdlIGluIHRoZSBMU1Agc3RhdGUiPyBJdCB3b3VsZCBsaWtlDQp0YWxraW5nIGFib3V0IHR3byBk
aWZmZXJlbnQgc3RhdGVzIGluIHRoZSBQQ0MuDQoNCkpvbj4gSSB0aGluayBpdCBqdXN0IG1lYW5z
IHRoYXQgdGhlIExTUCByZXZlcnRzIHRvIG9wZXJhdG9yIGNvbmZpZ3VyZWQgcGFyYW1ldGVycywg
YXMgZGlzY3Vzc2VkIGVsc2V3aGVyZS4gIEknbGwgY2xhcmlmeSBpdC4NCg0KPT09PT0NCg0KW0xN
XSBhYm91dCAiZmx1c2hlZCIsIHNob3VsZCB3ZSBhZGQgImFuZCByZXZlcnQgdG8gb3BlcmF0b3It
ZGVmaW5lZA0KZGVmYXVsdCBwYXJhbWV0ZXJzIG9yIGJlaGF2aW9ycyI/DQoNCkpvbj4gWWVzLg0K
DQo9PT09PQ0KDQpbLi4uXQ0KDQogICBJZiB0aGVyZSBpcyBhIHN0YW5kYnkgUENFLCB0aGUgUmVk
ZWxlZ2F0aW9uIFRpbWVvdXQgbWF5IGJlIHNldCB0bw0KMA0KICAgdGhyb3VnaCBwb2xpY3kgb24g
dGhlIFBDQywgY2F1c2luZyB0aGUgTFNQcyB0byBiZSByZWRlbGVnYXRlZA0KICAgaW1tZWRpYXRl
bHkgdG8gdGhlIFBDQywgd2hpY2ggY2FuIGRlbGVnYXRlIHRoZW0gaW1tZWRpYXRlbHkgdG8gdGhl
DQogICBzdGFuZGJ5IFBDRS4gIEFzc3VtaW5nIHRoZSBTdGF0ZSBUaW1lb3V0IEludGVydmFsIGlz
IGdyZWF0ZXIgdGhhbg0KdGhlDQogICBSZWRlbGVnYXRpb24gVGltZW91dCwgYW5kIGFzc3VtaW5n
IHRoZSBzdGFuZGJ5IFBDRSB0YWtlcyBzaW1pbGFyDQogICBkZWNpc2lvbnMgYXMgdGhlIGZhaWxl
ZCBQQ0UsIHRoZSBMU1Agc3RhdGUgd2lsbCBiZSBrZXB0IGludGFjdC4NCg0KW0xNXSB0aGUgZmly
c3QgImFzc3VtaW5nIiBpcyBub3QgYW4gYXNzdW1wdGlvbiBidXQgYSByZXF1aXJlbWVudCwNCmFj
Y29yZGluZyB0byAiVGhlIFN0YXRlIFRpbWVvdXQgSW50ZXJ2YWwgTVVTVCBiZSBncmVhdGVyIHRo
YW4gb3IgZXF1YWwNCnRvIHRoZSBSZWRlbGVnYXRpb24gVGltZW91dCBJbnRlcnZhbCINCg0KSm9u
PiBXZSBjb3VsZCBoYXZlIFNUSSA9IFJUSSwgb3IgU1RJIHZlcnkgY2xvc2UgdG8gUlRJLCBpbiB3
aGljaCBjYXNlIGl0IGlzIGEgcmFjZSBiZXR3ZWVuIHJlZGVsZWdhdGlvbiBjb21wbGV0aW5nIGFu
ZCBzdGF0ZSB0aW1lb3V0IGV4cGlyaW5nLg0KVG8gbWFrZSB0aGlzIGNsZWFyZXIgSSB3aWxsIGNo
YW5nZSBpdCB0byAiQXNzdW1pbmcgdGhhdCB0aGUgUENDIGNhbiByZWRlbGVnYXRlIHRoZSBMU1Ag
dG8gdGhlIHN0YW5kYnkgUENFIHdpdGhpbiB0aGUgU3RhdGUgVGltZW91dCBJbnRlcnZhbCwgYW5k
Li4uIg0KDQo9PT09PQ0KDQo1LjguMS4gIFBhc3NpdmUgU3RhdGVmdWwgUENFIFBhdGggQ29tcHV0
YXRpb24gUmVxdWVzdC9SZXNwb25zZQ0KDQogICAgICAgICAgICAgICAgICAgICArLSstKyAgICAg
ICAgICAgICAgICAgICAgKy0rLSsNCiAgICAgICAgICAgICAgICAgICAgIHxQQ0N8ICAgICAgICAg
ICAgICAgICAgICB8UENFfA0KICAgICAgICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAg
ICAgICAgICstKy0rDQogICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICAgICB8DQogICAxKSBQYXRoIGNvbXB1dGF0aW9uIHwtLS0tLSBQQ1JlcSBtZXNzYWdlIC0tLT58
DQogICAgICByZXF1ZXN0IHNlbnQgdG8gIHwgICAgICAgICAgICAgICAgICAgICAgICB8MikgUGF0
aCBjb21wdXRhdGlvbg0KICAgICAgUENFICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
ICAgICAgfCAgIHJlcXVlc3QgcmVjZWl2ZWQsDQogICAgICAgICAgICAgICAgICAgICAgIHwgICAg
ICAgICAgICAgICAgICAgICAgICB8ICAgcGF0aCBjb21wdXRlZA0KICAgICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICB8
PC0tLS0gUENSZXAgbWVzc2FnZSAtLS0tfDMpIENvbXB1dGVkIHBhdGhzDQogICAgICAgICAgICAg
ICAgICAgICAgIHwgICAgIChQb3NpdGl2ZSByZXBseSkgICB8ICAgc2VudCB0byB0aGUgUENDDQog
ICAgICAgICAgICAgICAgICAgICAgIHwgICAgIChOZWdhdGl2ZSByZXBseSkgICB8DQogICA0KSBM
U1AgU3RhdHVzIGNoYW5nZXwgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICBldmVudCAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAg
ICAgIHwgICAgICAgICAgICAgICAgICAgICAgICB8DQogICA1KSBMU1AgU3RhdHVzIFJlcG9ydHwt
LS0tLSBQQ1JwdCBtZXNzYWdlIC0tLT58DQogICAgICBzZW50IHRvIGFsbCAgICAgIHwgICAgICAg
ICAgICAuICAgICAgICAgICB8DQogICAgICBzdGF0ZWZ1bCBQQ0VzICAgIHwgICAgICAgICAgICAu
ICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAuICAgICAg
ICAgICB8DQogICA2KSBSZXBlYXQgZm9yIGVhY2ggIHwtLS0tLSBQQ1JwdCBtZXNzYWdlIC0tLT58
DQogICAgICBMU1Agc3RhdHVzIGNoYW5nZXwgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAg
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICB8DQoNCiAgICAgRmln
dXJlIDc6IFBhc3NpdmUgU3RhdGVmdWwgUENFIFBhdGggQ29tcHV0YXRpb24gUmVxdWVzdC9SZXNw
b25zZQ0KDQpbTE1dIGluIHRoZSBmaWd1cmUsIHBsZWFzZSB1c2UgInN0YXRlIiBpbnN0ZWFkIG9m
ICJzdGF0dXMiDQoNCkpvbj4gQUNLDQoNCj09PT09DQoNCjcuMS4gIE9QRU4gT2JqZWN0DQoNCiAg
IFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBvbmUgbmV3IG9wdGlvbmFsIFRMVnMgZm9yIHVzZSBpbiB0
aGUgT1BFTg0KICAgT2JqZWN0Lg0KDQpzL29uZSBuZXcgb3B0aW9uYWwgVExWcy9vbmUgbmV3IG9w
dGlvbmFsIFRMVg0KDQpKb24+IEFDSw0KDQo9PT09PQ0KDQo3LjIuICBTUlAgT2JqZWN0DQoNCiAg
IFRoZSBTUlAgKFN0YXRlZnVsIFBDRSBSZXF1ZXN0IFBhcmFtZXRlcnMpIG9iamVjdCBNVVNUIGJl
IGNhcnJpZWQNCiAgIHdpdGhpbiBQQ1VwZCBtZXNzYWdlcyBhbmQgTUFZIGJlIGNhcnJpZWQgd2l0
aGluIFBDUnB0IGFuZCBQQ0Vycg0KICAgbWVzc2FnZXMuICBUaGUgU1JQIG9iamVjdCBpcyB1c2Vk
IHRvIGNvcnJlbGF0ZSBiZXR3ZWVuIHVwZGF0ZQ0KICAgcmVxdWVzdHMgc2VudCBieSB0aGUgUENF
IGFuZCB0aGUgZXJyb3IgcmVwb3J0cyBhbmQgc3RhdGUgcmVwb3J0cw0Kc2VudA0KICAgYnkgdGhl
IFBDQy4NCg0KW0xNXSBTaG91bGQgd2UgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCBhdCB0aGUgZW5k
IG9mIHRoZSBzZWN0aW9uPw0KDQogICJPcHRpb25hbCBUTFZzIG1heSBiZSBpbmNsdWRlZCB3aXRo
aW4gdGhlIFNSUCBvYmplY3QgYm9keS4gVGhlDQogICBzcGVjaWZpY2F0aW9uIG9mIHN1Y2ggVExW
cyBpcyBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LiINCg0KSm9uPiBZZXMgLSB3
aWxsIGFkZCBpdCB3aXRoIGEgIk1BWSIuDQoNCj09PT09DQoNCjcuMy4gIExTUCBPYmplY3QNCg0K
Wy4uLl0NCg0KICAgVExWcyB0aGF0IG1heSBiZSBpbmNsdWRlZCBpbiB0aGUgTFNQIE9iamVjdCBh
cmUgZGVzY3JpYmVkIGluIHRoZQ0KICAgZm9sbG93aW5nIHNlY3Rpb25zLg0KDQpbTE1dIEkgdGhp
bmsgdGhhdCBpdCBpcyBwb3NzaWJsZSB0byBhZGQgZXh0cmEgb3B0aW9uYWwgVExWLCBub3QNCmRl
ZmluZWQgaW4gdGhpcyBkb2N1bWVudC4gVGhpcyBzaG91bGQgYmUgY2xhcmlmaWVkIGlmIEknbSBj
b3JyZWN0Lg0KDQpKb24+IFllcy4NCg0K


From nobody Tue Apr 11 06:46:53 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B30BB129BDB; Tue, 11 Apr 2017 06:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_HELO_PASS=-0.001, 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=joelhalpern.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 jXdOEFNL8p86; Tue, 11 Apr 2017 06:46:44 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 6A976128959; Tue, 11 Apr 2017 06:46:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4FF6F660F4E; Tue, 11 Apr 2017 06:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1491918376; bh=g+awUG1ihLZdm/bQrQ+bYZcmiRU4/2424sOMGePZAFo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Wf5z3wteOmmJ/Xqt6AL8fA02HaMZS0cWKcqeHmekaOOi3ByU/v1BdlcWSYIsIP4Ix rNOSSJDK/5E3QKbXyES/OiaSW6nqJ++/yEOZFhs5FFASpfe4vbe9AUQkIot24sRFI+ foon+aGB7rkrdjaaUtzlrYF7mYmzVeAn68AcvkQ0=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 802DD660F54; Tue, 11 Apr 2017 06:46:15 -0700 (PDT)
Subject: Re: Review of draft-ietf-pce-stateful-pce-18
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <2598a1a7-a5b1-fb4d-4ea5-8ecb33e58321@joelhalpern.com>
Date: Tue, 11 Apr 2017 09:46:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EWUsS_TZzZ_gpTrr1CccDw_E31o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 13:46:46 -0000

Thank you Jonathan.  Those changes sufficiently address my concerns.
Yours,
Joel

On 4/11/17 5:55 AM, Jonathan Hardwick wrote:
> Hi Joel
>
> Many thanks for these comments.  I'm picking up this thread and replying as PCE working group chair, as the authors are unavailable.  I apologise for the delay.
>
> Please see my proposed resolutions inline below, marked with "Jon>"
>
> Best regards
> Jon
>
>
> -----Original Message-----
> From: Joel Halpern [mailto:jmh@joelhalpern.com]
> Sent: 17 February 2017 03:38
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: Review of draft-ietf-pce-stateful-pce-18
>
> Reviewer: Joel Halpern
> Review result: Ready with Issues
>
> <snip>
>
> ====
>
> Minor issues:
>    At the end of section 5.4, the text talks about a PCE accepting status updates even if the  stateful capability has not been negotiated.  Which is fine.  But as written, the text seems to say that doing so means that the PCE will be able to "build and maintain an up to date view of the state of the PCC's LSPs".  However, if the capability has not been negotiated, I do not see how the PCE can count on getting full and timely state reports.  Trying to infer why a PCC is sending such a report in the absence of the agreement seems problematic.
>
> Jon> I agree.  I propose that we delete this sentence:
> " Note that even if the update
>    capability has not been advertised, a PCE can still accept LSP Status
>    Reports from a PCC and build and maintain an up to date view of the
>    state of the PCC's LSPs. "
>
> ====
>
>     This comment may be a misunderstanding or mis-expectation on my part.  I would have expected one of the ways o using an active PCE is to have the PCE decide (under suitable circumstances) that an LSP is needed between two PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Update Request (in a PCUpd message) for an LSP that has been delegated to it.  At that point I thought that a PCC could delegate a block of unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states that for each delegation, the PCC must request an initial path.  That seems to prohibit delegating a block of LSPs for future updates.  Is the intention to prohibit the driving of LSP creation from the PCE?
>
> Jon> Yes, the intention is that the PCE does not drive creation of the LSPs.  That behaviour is allowed but is described by a separate draft (draft-ietf-pce-pce-initiated-lsp).  I propose to clarify this in the introduction to the draft, so that future readers don't get caught by the same mis-expectation.  We'll add the following text to section 1, and add an informative reference to draft-ietf-pce-pce-initiated-lsp.  OK?
>
> NEW
>    The extensions that this document describes do not permit the
>    PCE to drive creation of an LSP.  The companion document
>    [I-D. ietf-pce-pce-initiated-lsp] specifies PCE-initiated LSP creation.
>
> ====
>
>     I have looked but I can not find the text explaining the significance and use of the Symbolic path name.  It is mandated by the draft.  There seems to be an implicit assumption taht it is needed by the PCE.  If the explanation of how or why it is needed is not present, it should be.
>
> Jon> Agreed.  Several of our reviewers have picked up on this.  I think we should clarify this in section 7.3.2 "Symbolic Path Name TLV".
>
> OLD
>    Each LSP (path) MUST have a symbolic name that is unique in the PCC.
>    This symbolic path name MUST remain constant throughout an LSP's
>    lifetime, which may span across multiple consecutive PCEP sessions
>    and/or PCC restarts.  The symbolic path name MAY be specified by an
>    operator in a PCC's configuration.  If the operator does not specify
>    a unique symbolic name for a path, the PCC MUST auto-generate one.
>
>    The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
>    LSP State Report (PCRpt) message when during a given PCEP session an
>    LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
>    State Report either during State Synchronization, or when a new LSP
>    is configured at the PCC.  The symbolic path name MAY be included in
>    the LSP object in subsequent LSP State Reports for the LSP.
>
>    <snip>
>
>    Symbolic Path Name (variable): symbolic name for the LSP, unique in
>    the PCC.
>
> NEW
>    Each LSP MUST have a symbolic path name that is unique in the PCC.
>    The symbolic path name is a human-readable string that identifies an
>    LSP in the network.  The symbolic path name MUST remain constant
>    throughout an LSP's lifetime, which may span across multiple
>    consecutive PCEP sessions and/or PCC restarts.  The symbolic path
>    name MAY be specified by an operator in a PCC's configuration.  If the
>    operator does not specify a unique symbolic name for an LSP, then the
>    PCC MUST auto-generate one.
>
>    The PCE uses the symbolic path name as a stable identifier for the LSP.
>    If the PCEP session restarts, or the PCC restarts, or the PCC re-delegates
>    the LSP to a different PCE, the symbolic path name for the LSP remains
>    constant and can be used to correlate across the PCEP session instances.
>
>    The other protocol identifiers for the LSP cannot reliably be used to
>    identify the LSP across multiple PCEP sessions, for the following reasons.
>    -  The PLSP-ID is unique only within the scope of a single PCEP session.
>    -  The LSP-IDENTIFIERS TLV is only guaranteed to be present for LSPs
>       that are signalled with RSVP-TE.
>
>    The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
>    LSP State Report (PCRpt) message when during a given PCEP session an
>    LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
>    State Report either during State Synchronization, or when a new LSP
>    is configured at the PCC.
>
>    The initial PCRpt creates a binding between the symbolic path name and
>    the PLSP-ID for the LSP which lasts for the duration of the PCEP session.
>    The PCC MAY omit the symbolic path name from subsequent LSP State
>    Reports for that LSP on that PCEP session, and just give the PLSP-ID.
>
>    <snip>
>
>    Symbolic Path Name (variable): symbolic name for the LSP, unique in
>    the PCC.  It SHOULD be a string of printable ASCII characters and SHOULD
>    be NULL-terminated.  The Symbolic Path Name (including its NULL
>    terminator) MUST be padded to 4-bytes alignment; the padding itself
>    MUST NOT be included in the Length field.
>
> END NEW
>
> ====
>
> Nits/editorial comments:
>     Should the text on the S bit in section 7.3 (the LSP Object
> definition) note that it should be set to 0 on all messages sent by the PCE?  Should that also be stated for the R bit?  And the O bits?
>
> Jon> Yes.  We will add a note to the description of these fields.
>
> ====
>
>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some additional work.  I understand why teh work is needed.  But this does not seem to match the RFC 2119 meaning of SHOULD as it does not apply to eitehr the implementor or the implementation.
>
> Jon> I agree - this is incorrect use of SHOULD.  It also references the MIB without even mentioning the YANG, which is a symptom of this document's advanced age.  We'll change this as follows (and add two informative references).
>
> NEW
>    The PCEP YANG module [I-D.ietf-pce-pcep-yang] should include
>    -  advertised stateful capabilities and synchronization status per PCEP session
>    -  the delegation status of each configured LSP.
>
>    The PCEP MIB [RFC7420] could also be updated to include this information.
>
> ====
>


From nobody Tue Apr 11 07:55:22 2017
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F29012E8FA; Tue, 11 Apr 2017 07:55:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Wesley Eddy <wes@mti-systems.com>
To: <tsv-art@ietf.org>
Cc: ipsec@ietf.org, draft-ietf-ipsecme-tcp-encaps.all@ietf.org, ietf@ietf.org
Subject: Tsvart last call review of draft-ietf-ipsecme-tcp-encaps-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149192250152.15649.6637923996602707175@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 07:55:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JRxHFwFNOoaBW3g1elkjf8Ch5Aw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 14:55:02 -0000

Reviewer: Wesley Eddy
Review result: On the Right Track

This document is clear and well-written.  It can easily be implemented
based on the description.

There are a few additional issues that should be considered with
advice to implementers in Section 12 on performance considerations:
1) Invisibility of packet loss - Inner protocols that require packet
losses as a signal of congestion (e.g. TCP) will have a challenge due
to not being able to see any packet losses since the outer TCP will
repair them (unless sending into a full outer TCP socket buffer shows
up back to the inner TCP as a packet loss?).
2) Nesting of ECN -  Inner TCP connections will not be able to use
effectively ECN on the portion of the path covered by the outer TCP
connection.
3) Impact of congestion response on aggregate - The general "TCP in
TCP" problem is mentioned, and is mostly appropriate for a single
flow.  If an aggregate of flows is sharing the same outer TCP
connection, there may be additional concerns about how the congestion
response behavior impacts an aggregate of flows, since it may cause a
shared delay spike even to low-rate flows rather than distributing
losses proportional to per-flow throughput.
4) Additional potential for bufferbloat - Since TCP does not bound
latency, some applications in the IPsec-protected aggregate could
drive latency of the shared connection up and impact the aggregate of
flows that may include real-time applications.  The socket buffer for
the outer TCP connection might need to be limited in size to ensure
some bounds?

Not addressing these could lead to poor experiences in deployment, if
implementations make wrong assumptions or fail to consider them.

In the security considerations section, there are several RFCs on
mechanisms to increase robustness to RST attacks and SYN floods that
could be mentioned if it's worthwhile.


From nobody Tue Apr 11 08:00:38 2017
Return-Path: <julien.meuric@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168751293DF; Tue, 11 Apr 2017 08:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.534
X-Spam-Level: 
X-Spam-Status: No, score=-3.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 dDO4i3LbfIEa; Tue, 11 Apr 2017 08:00:26 -0700 (PDT)
Received: from r-mail1.rd.orange.com (r-mail1.rd.orange.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id A7B1112EA95; Tue, 11 Apr 2017 08:00:25 -0700 (PDT)
Received: from r-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 62CDFA44270; Tue, 11 Apr 2017 17:00:24 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail1.rd.orange.com (Postfix) with ESMTP id 4730CA4426F; Tue, 11 Apr 2017 17:00:24 +0200 (CEST)
Received: from [10.193.71.173] (10.193.71.173) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.319.2; Tue, 11 Apr 2017 17:00:23 +0200
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, Lionel Morand <lionel.morand@orange.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
Message-ID: <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com>
Date: Tue, 11 Apr 2017 17:00:23 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ifk5QKjhXIZWbISjRW_p2vDkiAY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 15:00:29 -0000

Jon, Lionel,

I believe Lionel got confused by the wording introduced in RFC 8051:
- no report, no update means stateless PCE;
- report, no update means passive stateful PCE;
- report and update means active (stateful) PCE.

More details below, [JM].

Thanks for the work,

Julien


Apr. 11, 2017 - Jonathan.Hardwick@metaswitch.com:
> =====
> 
> [LM] active/passive mode are not  advertized in PCEP. s/if active 
> stateful PCE capability was not advertised/if stateful PCE
> capability was not advertised
> 
> Jon> ACK
> 
> =====
[JM] NACK! ;-)
Actually, the passive mode is advertised using the
Stateful-capability-object TLV with the U bit unset, the active mode by
setting the U bit.

> =====
> 
> Note that even if the update capability has not been advertised, a 
> PCE can still accept LSP Status Reports from a PCC and build and 
> maintain an up to date view of the state of the PCC's LSPs.
> 
> [LM] I don't undersand. Is it not in contradiction with
> 
> "If the PCEP Speaker on the PCE supports the extensions of this
> draft but did not advertise this capability, then upon receipt of a
> PCRpt message from the PCC, it MUST generate a PCErr with error- type
> 19 (Invalid Operation), error-value 5 (Attempted LSP State Report if
>  active stateful PCE capability was not advertised) (see Section
> 8.5) and it SHOULD terminate the PCEP session."
> 
> Or does it mean that there is another way than PCRpt message for the
>  PCC to send LSP status reports to the PCE?
> 
> Jon> ACK.  I think that the statement in the draft is bogus and I 
> propose to delete this sentence from it.
> 
> =====
[JM] I do not think that the text is bogus:
- case 1: no advertised capability on update but advertised on report
(i.e. passive stateful) => no error message;
- case 2: no advertised capability on update nor report (i.e. stateless)
=> error.

> =====
> 
> [LM] Would it be useful to discover (using another TLV) whether the 
> PCE is an active/passive stateful PCE, as in IGP-based capabilities 
> discovery mechanism?
> 
> Jon> This can be inferred immediately from the U flag in the 
> STATEFUL-PCE-CAPABILITY TLV.  Passive mode is synonymous with not 
> sending / handling PCUpd messages.
> 
> =====
[JM] The mechanism is there, but section 7.1.1 may deserve an explicit
use of the "passive/active" terms, to make sure the capability
terminology is aligned with the vocabulary in the IGP section.


From nobody Tue Apr 11 08:15:51 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6356812EAB0; Tue, 11 Apr 2017 08:15:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sean Turner <sean@sn3rd.com>
To: <secdir@ietf.org>
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
Subject: Secdir last call review of draft-ietf-dnssd-mdns-dns-interop-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149192374936.15734.41201323624268863@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 08:15:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xAhWYtvhy1IBa2uvX07vWmEQGeo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 15:15:49 -0000

Reviewer: Sean Turner
Review result: Ready

The draft is short and well written.  The security considerations is
also brief, but I agree with its basic point "This memo presents some
requirements for future development, but does not specify anything." 
The persistent "visual confusability" consideration wrt
internationalized domain names is duly noted as a consideration.  In
my opinion, the security considerations as written is appropriate and
sufficient; other DNSSD WG protocol-focused drafts have more extensive
security considerations and it is better to grind the security axe
against those documents rather than here.


From nobody Tue Apr 11 08:28:18 2017
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 523ED12EAB7; Tue, 11 Apr 2017 08:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=metaswitch.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 Cp1toPE6yh5e; Tue, 11 Apr 2017 08:28:14 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0102.outbound.protection.outlook.com [104.47.37.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3521D12EAB1; Tue, 11 Apr 2017 08:28:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=R9LIjH7GIG6Jkj/tntuFPn6JwAeQFY1pZukHbxyb4mk=; b=k5nj21RcQ4IzRzSLMm/cLzi7JE32l86mBJMvzByxMDKHEbG5vnBTRpj6KN1Xsv7CLBy6KLAbxD/rCjnTL64CYFCrrBl+lU1HkVEgWfg4KRRjXfAWqFrNI10/OehN0OQMhjbzVPvb78vhKO7JV8uc5XIQttytvKjVXxLABbh9vSU=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1912.namprd02.prod.outlook.com (10.163.75.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 15:28:12 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 15:28:12 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Julien Meuric <julien.meuric@orange.com>, Lionel Morand <lionel.morand@orange.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSnjojD8qJebPVvkunBA8z9I/80aHAL9TQgAA8aICAAATfcA==
Date: Tue, 11 Apr 2017 15:28:11 +0000
Message-ID: <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.com>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com> <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com>
In-Reply-To: <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: orange.com; dkim=none (message not signed) header.d=none;orange.com; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [82.132.227.234]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1912; 7:fJ+DHo35kMwCpc/6po47bHcDUP729lBe1Po/1y4f9H8fN74HuyuFjEuv/LWCAqXlnGkwsOZwmNgON12heEcdmhX5hQ0eJuL/6jMcFmpQpNdypL+sldNuR0xEOW96qoPPaH8iDsAXo1iCPQvnvj48DfiyhHUnX5POFvMxAaX63uiYvB+ukhGA55r1tW40K8iaOKwaYyUdawogWzeq4T5dOo4noHqyrwB4DGRsCaW3bfH5jg9zMXplBWE2K1OZQvPCzsde6+ST3bvTOKENDn+XrAcvR1IE7/8X640wbM+VGUVdSuWW4/txlu3Fvo+fwWSeraT5pCS0Fs2eq42ljGIpmw==
x-ms-office365-filtering-correlation-id: c618c726-1f2f-4f95-a1a8-08d480ef5d7f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BY2PR0201MB1912; 
x-microsoft-antispam-prvs: <BY2PR0201MB191211DFF1F3C71A6A0ED30184000@BY2PR0201MB1912.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506)(18271650672692);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123555025)(20161123562025)(6072148); SRVR:BY2PR0201MB1912; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1912; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39840400002)(39410400002)(39400400002)(13464003)(51444003)(51914003)(66066001)(5660300001)(7736002)(305945005)(74316002)(2501003)(229853002)(2950100002)(189998001)(54356999)(8936002)(122556002)(53936002)(77096006)(33656002)(25786009)(6116002)(102836003)(3846002)(7696004)(50986999)(53546009)(76176999)(3660700001)(8676002)(6506006)(81166006)(6436002)(3280700002)(9686003)(4326008)(86362001)(99286003)(2900100001)(55016002)(6246003)(2906002)(38730400002)(230783001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1912; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 15:28:11.7354 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1912
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Hvv9J_PO0aj4kxA1qNPiU7PmNvY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 15:28:16 -0000

Hi Julien

You are right, but it is *really easy* for the reader to confuse "stateful =
capability" with "update capability" and "active stateful capability".  Cas=
e in point: I just confused them in my reply to Lionel.

We should fix each of the three points below to make this clearer.

Cheers
Jon

-----Original Message-----
From: Julien Meuric [mailto:julien.meuric@orange.com]=20
Sent: 11 April 2017 16:00
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>; Lionel Morand <li=
onel.morand@orange.com>; ops-dir@ietf.org
Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18

Jon, Lionel,

I believe Lionel got confused by the wording introduced in RFC 8051:
- no report, no update means stateless PCE;
- report, no update means passive stateful PCE;
- report and update means active (stateful) PCE.

More details below, [JM].

Thanks for the work,

Julien


Apr. 11, 2017 - Jonathan.Hardwick@metaswitch.com:
> =3D=3D=3D=3D=3D
>=20
> [LM] active/passive mode are not  advertized in PCEP. s/if active=20
> stateful PCE capability was not advertised/if stateful PCE capability=20
> was not advertised
>=20
> Jon> ACK
>=20
> =3D=3D=3D=3D=3D
[JM] NACK! ;-)
Actually, the passive mode is advertised using the Stateful-capability-obje=
ct TLV with the U bit unset, the active mode by setting the U bit.

> =3D=3D=3D=3D=3D
>=20
> Note that even if the update capability has not been advertised, a PCE=20
> can still accept LSP Status Reports from a PCC and build and maintain=20
> an up to date view of the state of the PCC's LSPs.
>=20
> [LM] I don't undersand. Is it not in contradiction with
>=20
> "If the PCEP Speaker on the PCE supports the extensions of this draft=20
> but did not advertise this capability, then upon receipt of a PCRpt=20
> message from the PCC, it MUST generate a PCErr with error- type
> 19 (Invalid Operation), error-value 5 (Attempted LSP State Report if =20
> active stateful PCE capability was not advertised) (see Section
> 8.5) and it SHOULD terminate the PCEP session."
>=20
> Or does it mean that there is another way than PCRpt message for the =20
> PCC to send LSP status reports to the PCE?
>=20
> Jon> ACK.  I think that the statement in the draft is bogus and I
> propose to delete this sentence from it.
>=20
> =3D=3D=3D=3D=3D
[JM] I do not think that the text is bogus:
- case 1: no advertised capability on update but advertised on report (i.e.=
 passive stateful) =3D> no error message;
- case 2: no advertised capability on update nor report (i.e. stateless) =
=3D> error.

> =3D=3D=3D=3D=3D
>=20
> [LM] Would it be useful to discover (using another TLV) whether the=20
> PCE is an active/passive stateful PCE, as in IGP-based capabilities=20
> discovery mechanism?
>=20
> Jon> This can be inferred immediately from the U flag in the
> STATEFUL-PCE-CAPABILITY TLV.  Passive mode is synonymous with not=20
> sending / handling PCUpd messages.
>=20
> =3D=3D=3D=3D=3D
[JM] The mechanism is there, but section 7.1.1 may deserve an explicit use =
of the "passive/active" terms, to make sure the capability terminology is a=
ligned with the vocabulary in the IGP section.


From nobody Tue Apr 11 08:31:36 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD9A128D6F; Mon, 10 Apr 2017 13:07:29 -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 0gqKo-76luwN; Mon, 10 Apr 2017 13:07:28 -0700 (PDT)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 4E172129AD2; Mon, 10 Apr 2017 13:07:26 -0700 (PDT)
Received: by mail-io0-x243.google.com with SMTP id x86so4410698ioe.3; Mon, 10 Apr 2017 13:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=7+Tw+0K8GiS4tTBiSsMeEoL8OfaeFc8wOwwo7jhD/Eo=; b=TES0HivxIosUVeINWMz1BxXNfkjSpUIr1R34HsFvai2EPeSgdqMYrjj1CGbLXApchS 3agCu+UL0q4MhZCjoy2OKzivXkCF9SLwmaDF0SmXuZ/S13DEIVAPpx87TUuWxmI4GEBh 4WIF+G3AwxKFGc1EdhCZSUCNC/cdyzjHy2ktGtI7YHpHFC6GWErWtChtNDVeQtHvdbEn DTMV+RkmuOrVzhYxayhf/GKkkPVB5wtf/96E71fHZmGMUBnW44Fmjyy4+G4XTBDQQQB9 dfC7A7ORMD3FzXh4JwfUMF/xGRa4T/mgrjRJBNz/UMNcATYkA8NkCLMtWc3Y4uhl4CYc ihOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=7+Tw+0K8GiS4tTBiSsMeEoL8OfaeFc8wOwwo7jhD/Eo=; b=aKnUofg6snP4LiMj0Qv0dQvdfmJzvcoCIk9PBM9NZN4QtuFJUB+dohFdiDQL0W7OYS dXtUfAg2Vf42jH7PJSUXx2qvMnAgVI5/8DgkfqO83lrgtyYC0NwDvDMibmAyarvVRLqr gk6sz/AmaEHGNpXOAVnP8bKIbY/vmfw4sNSk+qvAhN7EEpvSkdPat3BrWB+Cqw628h79 hr12PhCtF30HTNV9ZLe318TFlj5BC3Sw2gB+dQBq5WJFb4aLGgyOlJBpWygmS6f5zLG/ A8Be5WFK2YaKrjAT6cke5YS5CpndsE8Zbzikkrr3cDY7bacv/ljCIeOh1Dk7Zy7RnwlR zS8g==
X-Gm-Message-State: AFeK/H1KX9VB+xQSVI/1wmwXZrHEpbq+RsSyZwamTnfsDJoWfB62VuTz+9OSxX4rFevvfQ==
X-Received: by 10.107.21.193 with SMTP id 184mr50562690iov.116.1491854845386;  Mon, 10 Apr 2017 13:07:25 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id l33sm6858935iod.8.2017.04.10.13.07.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 13:07:24 -0700 (PDT)
Subject: Re: IAOC -- looking for committee volunteers
References: <149149603842.22056.14285846839847949929.idtracker@ietfa.amsl.com> <4D708CA7-AFE6-4023-9591-B781DE576655@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, iasa20@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b18f5087-4cc3-c514-198f-cbdd6d3d751f@gmail.com>
Date: Tue, 11 Apr 2017 08:07:23 +1200
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: <4D708CA7-AFE6-4023-9591-B781DE576655@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J0qrFbs2em6xgbkAQPMuKRHdQAE>
X-Mailman-Approved-At: Tue, 11 Apr 2017 08:31:34 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 20:07:30 -0000

Jordi,

On 11/04/2017 06:27, JORDI PALET MARTINEZ wrote:
> Once more, as I indicated in November last year. I fail to see ANY RFC =
that confirms that the IAOC itself is empowered by the community to selec=
t more committee members in a very obscure way, and as Leslie indicated b=
ased on =E2=80=9Cpersonell decisions=E2=80=9D. Clearly not transparent at=
 all.
>=20
> Why, if committees need more participants, which I understand because t=
he increase of the workload, and knowing already since several months ago=
 that this is a thread, and that the NomCom have candidates to participat=
e.
>=20
> We have got an opportunity to ask the NomCom to work on extra candidate=
s since some people was appointed already in November.
>=20
> If there is no RFC allowing it, clearly this is a decision that MUST be=
 appealed, as it is totally against the IETF spirit.

I disagree, but let me explain why, because I agree that there's a=20
problem, just not the one that you state.

And I suggest that we follow up on the appropriate list for the point I'm=

going to make (hence the way this message is addressed, with a Bcc to the=

ietf list).

Firstly, we gave the administrative job to IASA some years ago. IASA, who=
se
head is the IAD, is IMHO completely entitled to do its job how it pleases=
,
for example by negotiating resources with ISOC or by calling for communit=
y
volunteers and organising them in committees.=20

Secondly, we created the IAOC to oversee IASA and the IAD. That's what
the "O" in IAOC stands for, and it was not a casual choice.

These two separate consensus decisions have got very mixed up since 2005.=

The IAOC is evidently not just overseeing IASA - it's doing a large part =
of
the work of IASA itself. That's the problem that needs fixing - either by=

changing the rules in RFC 4071 to describe reality, or by changing realit=
y
to follow the rules.

Not everyone agrees with my analysis, but I think we have the IASA 2.0
discussion for a reason.

   Brian


From nobody Tue Apr 11 10:18:43 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC5B12955B for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:18:42 -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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 E8O7CgAOiys5 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:18:40 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D334B129A98 for <ietf@ietf.org>; Tue, 11 Apr 2017 10:18:37 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTP id 4F0D8A007634; Tue, 11 Apr 2017 10:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=6HwIemMY1bCP6U JfSBxKB26a8p8=; b=JcJpy8eX48QfeEaqT8enI+3+P/RCaEZxqIhSM6y4l6+WVQ XO7OWlzcBa1Pc1KF2UnYAYRxCI0HVy+3XAtjXzVVKnLDfggj2pwdxJeLyAV4WIdJ XyuwxgNKXc0jLR2lE7rCSYh6t4AaX6LzvMctZqrMe0U9tRTPTNVstksu/VWUc=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTPSA id 4F69BA00762E; Tue, 11 Apr 2017 10:18:36 -0700 (PDT)
Date: Tue, 11 Apr 2017 12:18:34 -0500
From: Nico Williams <nico@cryptonector.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Message-ID: <20170411171831.GA23461@localhost>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Is7VnZmfRrvwYEzGznMMRpbCsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 17:18:42 -0000

On Tue, Apr 11, 2017 at 09:51:14AM +0100, Stephen Farrell wrote:
> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
> >> I hope that the IETF never publishes
> >> draft-dolson-plus-middlebox-benefits; it makes claims about the
> >> benefits of specific solutions for different use cases with the
> >> goal of justifying those solutions.
> 
> > [Med] I'm afraid this is speculating about the intent of
> > draft-dolson. Assured this is not the purpose of that document. The
> > motivation is to document current practices without including any
> > recommendation or claiming these solutions are superior to others.
> 
> Just to note that I completely agree with Martin's interpretation
> of the thrust of this draft and I totally fail to see how your
> argument above can be justified given that draft title, abstract
> and even filename (and also the content;-). When the abstract
> says "This document summarizes benefits" then I cannot interpret
> that as other than being intended to justify the uses described.
> 
> A fairly thorough re-write to aim to describe the pros and cons
> would be a different and more useful document. Similarly a draft

Documenting the good, the bad, and the ugly, would be much better than
documenting only the good.  Documenting only one half of the story seems
to me like a bad idea on its face.

> that strives to neutrally describe existing reality could maybe
> be useful (*) but one that only describes middlebox friends with
> "benefits" is not IMO beneficial ;-)

Agreed.

I can think of a number of problems with middle boxes:

 - scalability

   Middle boxes may need to expend much more computational power in
   order to do more than forward packets, and they need to do this for
   as many extant packet flows as will fit on their pipes at full tilt.

   Middle boxes may also have to be stateful, which quickly turns into a
   morass.

 - security

   Middle boxes can get intrusive and require sharing either more
   information with the public at large, or more information with
   "trusted" middle boxes, which in turn requires more complex key
   management and more failure modes.

 - reliability

   More failure modes (see security above).  More middle boxes to
   inspect for diagnostics.  More middleboxes to fix.

 - extensibility

   Want to extend the protocol?  You can't.  You'd have to upgrade all
   the middle boxes first.  You can only get the extensibility that you
   can foresee.  If you screw up the first time, the screw up will take
   15 years to work out of the Internet in the best case, and in the
   worst case you'll never get it out.

I can probably add more later when I have more time for this thread.

One could give a lot of advice for design of protocols with "friendly"
middle boxes.  Merely saying "hey, they are good" is not enough.  We
might want to revisit end-to-end protocol design as well (e.g., maybe
ICMP isn't working so well; what can we do?).  Perhaps we can get some
of the benefits of middle-box-aware protocols without the middle boxes.
Suppose a secure middle-box quench protocol by which nodes under DDoS
can enable DDoS counter-measures in upstream routers...  Suppose a
generic, non-TCP congestion control capable but UDP-like transport with
a reusable header prefix and ICMP-ish messages for QoS and congestion
control...  I'm certain we can do more within the end-to-end model with
minimal middle-box involvement (though never zero; we need at least
packet forwarding middle boxes).

IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as it
is today.

Nico
-- 


From nobody Tue Apr 11 10:31:48 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C1F12954E for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:31: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 sTJFb9-H5RyN for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:31:46 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (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 D56D0128D69 for <ietf@ietf.org>; Tue, 11 Apr 2017 10:31:45 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id i5so1674432pfc.2 for <ietf@ietf.org>; Tue, 11 Apr 2017 10:31:45 -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; bh=ZsltdIm96pxkSCrjDSIsqF2NSJMdAEpEYKIxJIp6eKs=; b=RinbRN7gQ5SwKDcAX3ncziUCnWJ1Dp/hqYFgl12q+TpD1hRCQgsFJLTxXH8AeJKULA paBuEJAryi2/O71EtDIliwh5pOhkxDOGMzziFkfyfhtj+Ck4JhEtkEd0tcYMCSqj7lWK lNywSY16A3tOYc5RtJhoeD1VMqNtDqGMUVNGHMQMJzFiZSG0F67qGJjsBca43NbQn02h jL0JODY/e5a+TjJXgahNJGK85RczrjyV4V5mNK7IeBkE2nambsdYKQAzuV4pzewah31j lJMYEMjvtjXj6GD/eTqmpQaizLgGLuAWBaRuTPLo2PPFmwIgoDosouYzC+rge5nX9HsF jROw==
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; bh=ZsltdIm96pxkSCrjDSIsqF2NSJMdAEpEYKIxJIp6eKs=; b=ucM+sytz56RMvkfiyjxzdrr1Ye/LZqxFYMILs4wkw9gOL6nZlIMzduIP0okAjdgXOw kPi9/cyHN5awgvEPQ2RLAWKJiDP3QKNc8/QLCnmxOKhU7mLi9sEoxx1o97e14YSLSucr IjO9b4XaE0MXwsWhNelMuZAPf4zGOzDLTS1qDNoVX10pFK0mYnRyvFDKdXz4gUUjoVB+ X+7zMCTO96zped64ZCF2F/ZttvTMKzdgvqgPN2OHYoRicutH1h1Lgc3gvd6cAJtKceiy fIghKY1qexRTOVBoQDitbhi4v+xuohZ/JpKonhsOe4uPgwYc5qUx9nE6lfCmbKSNk/G/ oXvg==
X-Gm-Message-State: AFeK/H2WNq3fWRNcPKqcTDBvoJcIduqWZ+7Ai5lIFsd33i2+4AdQqhGcjPvNgU3DetCIOg==
X-Received: by 10.99.119.69 with SMTP id s66mr62664920pgc.196.1491931904832; Tue, 11 Apr 2017 10:31:44 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-81-9-radius.dynamic.acsalaska.net. [63.140.81.9]) by smtp.gmail.com with ESMTPSA id q136sm25628366pfq.80.2017.04.11.10.31.43 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 10:31:44 -0700 (PDT)
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: ietf@ietf.org
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com>
Date: Tue, 11 Apr 2017 09:31:41 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170411171831.GA23461@localhost>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0pv8IN4J4LlGcS7bPaLXbDdaigS2mtN5r"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hawzB180my0_eZ7e4W1L9vEQw-Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 17:31:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0pv8IN4J4LlGcS7bPaLXbDdaigS2mtN5r
Content-Type: multipart/mixed; boundary="FxKCthUV4DTfDmEgqpwgD2P3qO7nk0oDq";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: ietf@ietf.org
Message-ID: <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
 <20170411171831.GA23461@localhost>
In-Reply-To: <20170411171831.GA23461@localhost>

--FxKCthUV4DTfDmEgqpwgD2P3qO7nk0oDq
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 4/11/17 9:18 AM, Nico Williams wrote:
> One could give a lot of advice for design of protocols with
> "friendly" middle boxes.  Merely saying "hey, they are good" is not
> enough.  We might want to revisit end-to-end protocol design as well
> (e.g., maybe ICMP isn't working so well; what can we do?).

There have been a number of efforts to provide mechanisms for
applications to communicate explicitly with middleboxes.  None
has gotten any traction, and for the moment it looks like
anything that requires changes to middleboxes along those
lines is unlikely to be successful.  That said:

> IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as
> it is today.

No, clearly not.  I'm actually not sure I see a lot of benefit
to publishing a more balanced document, either, in the sense that
it's not likely to lead anybody to do anything differently.

Melinda


--FxKCthUV4DTfDmEgqpwgD2P3qO7nk0oDq--

--0pv8IN4J4LlGcS7bPaLXbDdaigS2mtN5r
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQIcBAEBCgAGBQJY7RL+AAoJELiGRpM6HoEu42QQALWvzdgnp1EOI9iHnpGQDVFo
uoT3aOuGOKOi4/eMeHQm8YHhU8R7JxWeY99V7JSg1RaxO/nxRjPuV+AfdkTWNIJD
1VNJ6MfnVGYF7cF5qLHLa+/VxQda1258gPb/LVPJXdcnbPm9d/RqKxm4XZpz1JPk
/fsBdftwTloPDtrmGoBb42ts22VZibOdjC5wLq62VTDuQ+xrnsQg+MY9kUYLUdM6
XclBL1Sa6JcCU5Qc+FbbX+85hylklw57XTk2tYqjG3aYhV6whGus2qYw3wUYWEf3
Ih4HmslfKg4/tN6VzYBpPG+b9uDcT54iSl+5L/ygSAJhmOe6biFVOOsfLdcHAOhW
wIDytm92xB4ZqDqVX+CfTOHdrn1Qj8o41EQG1XSPCGtF0KkRJ+ZlRnXBJvWDrdp6
D9dVCcwZJ19odxXx9HGRWhnobCoKQ9SJ1yKOIbSoGLsI/NEaJ1u0bkfNLDJQ+dJB
N52fg40ZDaRHttTJNCNRZdWK6RDq1NjfT5A3LblviUAre7O/qTh2urw7/VxykcxX
9vz+bU2Uv3njcRuwSvTqLULkNdAPcf/cR62iJNepMbTRQR+5gq6BsjXt4tFBLWSe
GGbAE3h+OO59gwgA1ltL/MDQrNql2fTYmYY9JDW3kw4Ob+ZNQauqR8ngsT8dwQAW
hMe0029SQLo3ZHxeMLPl
=ff18
-----END PGP SIGNATURE-----

--0pv8IN4J4LlGcS7bPaLXbDdaigS2mtN5r--


From nobody Tue Apr 11 10:50:31 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB0012EB59 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:50:24 -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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 geeq_WBENHUY for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 10:50:23 -0700 (PDT)
Received: from homiemail-a113.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D9F512EB44 for <ietf@ietf.org>; Tue, 11 Apr 2017 10:50:23 -0700 (PDT)
Received: from homiemail-a113.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTP id D036430002726; Tue, 11 Apr 2017 10:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=g1Ju5DVveH+VOj 9EGvbdWHqWADE=; b=l2V0qedqAxeY2faHF7TGJBVkN6a1t3Smng2GOIBx2IJIg5 ez71RqEChOb9fNzAZBA828Kp1ZJr58owklII+Fqo1wXW/zBYxdfJQk2i5qyp/O1b XNrgB+xuJTDiJaRWxXYLWacoZmam/8GckFZllE4909iXTlk+550FGj55NngFE=
Received: from localhost (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTPSA id 5D94F30002724; Tue, 11 Apr 2017 10:50:22 -0700 (PDT)
Date: Tue, 11 Apr 2017 12:50:20 -0500
From: Nico Williams <nico@cryptonector.com>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: ietf@ietf.org
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Message-ID: <20170411175019.GB23461@localhost>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost> <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0XhrhRl3WAie7cdogJWSdv7mpMs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 17:50:24 -0000

On Tue, Apr 11, 2017 at 09:31:41AM -0800, Melinda Shore wrote:
> On 4/11/17 9:18 AM, Nico Williams wrote:
> > One could give a lot of advice for design of protocols with
> > "friendly" middle boxes.  Merely saying "hey, they are good" is not
> > enough.  We might want to revisit end-to-end protocol design as well
> > (e.g., maybe ICMP isn't working so well; what can we do?).
> 
> There have been a number of efforts to provide mechanisms for
> applications to communicate explicitly with middleboxes.  None
> has gotten any traction, and for the moment it looks like
> anything that requires changes to middleboxes along those
> lines is unlikely to be successful.  That said:

Sure, but if we wanted to have an Informational RFC describing all the
goodness and badness and history of middle-box-aware protocools, that
might not be bad, and we could detail all those protocols that failed to
get traction and why.  I think such a document would end up favoring
end-to-end protocols, even if it didn't start out with that as a goal :)

> > IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as
> > it is today.
> 
> No, clearly not.  I'm actually not sure I see a lot of benefit
> to publishing a more balanced document, either, in the sense that
> it's not likely to lead anybody to do anything differently.

I'm not advocating for publishing a more balanced document.  I only
advocate not publishing draft-dolson-plus-middlebox-benefits.  If the
authors come back with a more balanced document, I might be willing to
support it, though I can say right now that I would expect the result to
favor the end-to-end model, and if it ended up advocating middle boxes
much more intelligent than routers then I'd be surprised.

Nico
-- 


From nobody Tue Apr 11 11:27:30 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E97512EB77 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=cs.tcd.ie
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 qXYwvlBqhOda for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:27:14 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D376129AB2 for <ietf@ietf.org>; Tue, 11 Apr 2017 11:26:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A1023BED5; Tue, 11 Apr 2017 19:26:23 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVmx0TFiMSXX; Tue, 11 Apr 2017 19:26:22 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9BA82BECC; Tue, 11 Apr 2017 19:26:21 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491935182; bh=VlMU+Tt1IZy4vjkj0R8u/CV1o4CRKP1Mbr1qinCHEmQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=KQDVa9ufDKu6kS80peD7WCe9+cCKsOeYGOZq0iA4cxMB+s19fpT9JA3h0P4r8GHko pVK1nw/zElvP7WNxBnFPwLp/QK1oCPNEDgyZQ1CCATxzurs0xJe+zHN/pLcOG9wMpx zLBLhos+bqpAltdb6xE4cZhK43UU7xCO8OFjrixE=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <f99d9c97-53f9-bac1-7bd1-8effa3ff9732@cs.tcd.ie>
Date: Tue, 11 Apr 2017 19:26:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="016gqDDQaMbev5jtgmCK86Pr0XceCAntl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3aaBTI-Y7b7n2ut4gF9o4CoFlnA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:27:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--016gqDDQaMbev5jtgmCK86Pr0XceCAntl
Content-Type: multipart/mixed; boundary="4AA2JLQkWvE7MdBDhvDAq7IKrqItVKFTD";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Martin Thomson <martin.thomson@gmail.com>,
 "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org"
 <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Message-ID: <f99d9c97-53f9-bac1-7bd1-8effa3ff9732@cs.tcd.ie>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>

--4AA2JLQkWvE7MdBDhvDAq7IKrqItVKFTD
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 11/04/17 12:47, mohamed.boucadair@orange.com wrote:
> Hi Stephen,
>=20
> Please see inline.
>=20
> Cheers, Med
>=20
>> -----Message d'origine----- De=C3=82 : Stephen Farrell
>> [mailto:stephen.farrell@cs.tcd.ie] Envoy=C3=83=C2=A9=C3=82 : mardi 11 =
avril 2017
>> 10:51 =C3=83=E2=82=AC=C3=82 : BOUCADAIR Mohamed IMT/OLN; Martin Thomso=
n;
>> ietf@ietf.org Cc=C3=82 :
>> draft-dolson-plus-middlebox-benefits@tools.ietf.org Objet=C3=82 : Re:
>> draft-dolson-plus-middlebox-benefits (was RE: Review of draft-=20
>> mm-wg-effect-encrypt-09)
>>=20
>>=20
>> Hi Med,
>>=20
>> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>>>> I hope that the IETF never publishes=20
>>>> draft-dolson-plus-middlebox-benefits; it makes claims about
>>>> the benefits of specific solutions for different use cases with
>>>> the goal of justifying those solutions.
>>=20
>>> [Med] I'm afraid this is speculating about the intent of=20
>>> draft-dolson. Assured this is not the purpose of that document.
>>> The motivation is to document current practices without including
>>> any recommendation or claiming these solutions are superior to
>>> others.
>>=20
>> Just to note that I completely agree with Martin's interpretation=20
>> of the thrust of this draft and I totally fail to see how your=20
>> argument above can be justified given that draft title, abstract=20
>> and even filename (and also the content;-).
>=20
> [Med] "beneficial" is derived from the initial request that motivated
> this draft (excerpt from the abstract):
>=20
> At IETF97, at a meeting regarding the Path Layer UDP Substrate
> (PLUS) protocol, a request was made for documentation about the
> benefits ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
> that might be provided by permitting middleboxes to have some=20
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
> visibility to transport-layer information.=20
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20

Well, just because someone asks for something doesn't mean
it's always a good idea to give it to them. I also not that
the quoted text is silent as to whether the downsides ought
also be documented. But regardless of whether or not there
is a desire for this document, in anything like it's current
form, I'd be one voice opposed to publication.

> When the abstract
>> says "This document summarizes benefits" then I cannot interpret=20
>> that as other than being intended to justify the uses described.
>=20
> [Med] I would prefer if we can avoid to "interpret", but raise
> questions to the authors if there is a doubt.=20

Mine was a comment not a question. I think both can be valid.

> The document does not
> provide a recommendation or claims this is the only way to achieve
> the technical goals. It does only reflect some deployment reality
> together with some motivations.

I disagree that the above fairly describes the current text.

>=20
>>=20
>> A fairly thorough re-write to aim to describe the pros and cons=20
>> would be a different and more useful document.
>=20
> [Med] There are already many RFCs that discuss the issues/cons (I can
> cite this RFC I co-authored https://tools.ietf.org/html/rfc6269 for
> the CGN case). What is needed IMHO is something else: understand the
> requirements that led to deploy some of these functions.
>=20
> Similarly a draft
>> that strives to neutrally describe existing reality could maybe be
>> useful (*)
>=20
> [Med] This is the intent of draft-dolson.

If so, I think that the current text is very very far from being
ready.

S.

>=20
> but one that only describes middlebox friends with
>> "benefits" is not IMO beneficial ;-)
>=20
> [Med] The intent is not to "sell something" but to understand the
> technical needs so that hopefully we can have a reference for future
> solution-oriented discussions. If a given function can be provided
> without involving an on-path device, this would be great for
> operators (optimize CAPEX/OPEX is our motto).
>=20
>>=20
>> Cheers, S.
>>=20
>> (*) That is the argument for draft-mm-effect-encrypt, for which I=20
>> do support publication (apparently in disagreement with Martin in=20
>> that case:-)
>>=20
>>=20
>>=20
>=20


--4AA2JLQkWvE7MdBDhvDAq7IKrqItVKFTD--

--016gqDDQaMbev5jtgmCK86Pr0XceCAntl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7R/NAAoJEC88hzaAX42iA7MIAIxB8ogKEWPSnBjybTGVUJrY
T6ca6w31Nclp6JVIrY+UPhH04hSHLJPHt1sFoJlJhGVDtT1KNo434jnivWSA8PUa
vLijUMGC1TIVfkT5eGW5d5tGe0E4XyG7cHJP3FeD7joLxMv6sApKNFrixBTVEyNb
vq0wc2ZkO5ISCVsQYVSIosDLfNk0d/bqO84ozMlZjHTth+dcOq/pG8GKp6UDB6+L
PWZCaZ6FBbr2sc4WE7+/vzQTeKCn/MweylrsMXqdTwjoh+xJ1u1KFSzERnWcVzn5
ORlSIB6G7/tzNF0ME9le0y3w4cyT/5y1c2EgyEpzeB4B8+ztb0JKc51VzNBa3cM=
=nclA
-----END PGP SIGNATURE-----

--016gqDDQaMbev5jtgmCK86Pr0XceCAntl--


From nobody Tue Apr 11 11:34:13 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF3712EBE1 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=cs.tcd.ie
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 EmLB6pu6kEf3 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:34:09 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44E2D12EBD2 for <ietf@ietf.org>; Tue, 11 Apr 2017 11:34:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 72C1ABEB5; Tue, 11 Apr 2017 19:34:07 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wM1yk5O-w7xm; Tue, 11 Apr 2017 19:34:05 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 48480BEB3; Tue, 11 Apr 2017 19:34:05 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491935645; bh=9XJrSj3pXhvkBIj6prH9Lngzym3F2k/hgA+6Av/Bqo4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=aTlqJWJEokHggYexVObasj703inA4XqNXOephkYMci7Icod6S6yAjBnBYOXGZ8Y4W 1tjJPLqt2lV64VEnjfgqE1Vb5QbnBtEWIwwF0Pn919VHFVfn/XSgVGKT/ARIo8J0IQ 0qfumcx6UyjrbGp+gXkbPn7XxLRJv9BBYWbRSyys=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: Dave Dolson <ddolson@sandvine.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie>
Date: Tue, 11 Apr 2017 19:34:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170411120303.5128273.2297.7062@sandvine.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qKGSPXNXmD1nj2Vg0WISD44ttBWeL76FP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DMJ_tUYlZidbCRgyU-ZETF_Meag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:34:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qKGSPXNXmD1nj2Vg0WISD44ttBWeL76FP
Content-Type: multipart/mixed; boundary="o5UHv6jSTiwJcnmP27LI837tnbkCbC77R";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Dave Dolson <ddolson@sandvine.com>,
 "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>,
 Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org"
 <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Message-ID: <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <20170411120303.5128273.2297.7062@sandvine.com>
In-Reply-To: <20170411120303.5128273.2297.7062@sandvine.com>

--o5UHv6jSTiwJcnmP27LI837tnbkCbC77R
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 11/04/17 13:03, Dave Dolson wrote:
> Regarding "benefits", these devices clearly have perceived benefits

I do not agree that the IETF ought described perceived benefits
as if the claimed benefits accrue as hoped for. That is far too
close to marketing. In a contentious case like this, I can see
why someone may feel that's useful as a form of balance or part
of a larger debate, but in the end I think we need to step back
and take an engineering approach.

S

> to those who deploy them. My view is that the document should explain
> that perspective for readers who lack the operator perspective. The
> intent was not to mandate or recommend deployments.
>=20
> David Dolson =C3=A2=E2=82=AC=C5=BD Original Message From: mohamed.bouca=
dair@orange.com=20
> Sent: Tuesday, April 11, 2017 7:48 AM To: Stephen Farrell; Martin
> Thomson; ietf@ietf.org Cc:
> draft-dolson-plus-middlebox-benefits@tools.ietf.org Subject: RE:
> draft-dolson-plus-middlebox-benefits (was RE: Review of
> draft-mm-wg-effect-encrypt-09)
>=20
>=20
> Hi Stephen,
>=20
> Please see inline.
>=20
> Cheers, Med
>=20
>> -----Message d'origine----- De : Stephen Farrell
>> [mailto:stephen.farrell@cs.tcd.ie] Envoy=C3=83=C2=A9 : mardi 11 avril =
2017
>> 10:51 =C3=83=E2=82=AC : BOUCADAIR Mohamed IMT/OLN; Martin Thomson;
>> ietf@ietf.org Cc :
>> draft-dolson-plus-middlebox-benefits@tools.ietf.org Objet : Re:
>> draft-dolson-plus-middlebox-benefits (was RE: Review of draft-=20
>> mm-wg-effect-encrypt-09)
>>=20
>>=20
>> Hi Med,
>>=20
>> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>>>> I hope that the IETF never publishes=20
>>>> draft-dolson-plus-middlebox-benefits; it makes claims about
>>>> the benefits of specific solutions for different use cases with
>>>> the goal of justifying those solutions.
>>=20
>>> [Med] I'm afraid this is speculating about the intent of=20
>>> draft-dolson. Assured this is not the purpose of that document.
>>> The motivation is to document current practices without including
>>> any recommendation or claiming these solutions are superior to
>>> others.
>>=20
>> Just to note that I completely agree with Martin's interpretation=20
>> of the thrust of this draft and I totally fail to see how your=20
>> argument above can be justified given that draft title, abstract=20
>> and even filename (and also the content;-).
>=20
> [Med] "beneficial" is derived from the initial request that motivated
> this draft (excerpt from the abstract):
>=20
> At IETF97, at a meeting regarding the Path Layer UDP Substrate
> (PLUS) protocol, a request was made for documentation about the
> benefits ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
> that might be provided by permitting middleboxes to have some=20
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
> visibility to transport-layer information.=20
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20
> When the abstract
>> says "This document summarizes benefits" then I cannot interpret=20
>> that as other than being intended to justify the uses described.
>=20
> [Med] I would prefer if we can avoid to "interpret", but raise
> questions to the authors if there is a doubt. The document does not
> provide a recommendation or claims this is the only way to achieve
> the technical goals. It does only reflect some deployment reality
> together with some motivations.
>=20
>>=20
>> A fairly thorough re-write to aim to describe the pros and cons=20
>> would be a different and more useful document.
>=20
> [Med] There are already many RFCs that discuss the issues/cons (I can
> cite this RFC I co-authored https://tools.ietf.org/html/rfc6269 for
> the CGN case). What is needed IMHO is something else: understand the
> requirements that led to deploy some of these functions.
>=20
> Similarly a draft
>> that strives to neutrally describe existing reality could maybe be
>> useful (*)
>=20
> [Med] This is the intent of draft-dolson.
>=20
> but one that only describes middlebox friends with
>> "benefits" is not IMO beneficial ;-)
>=20
> [Med] The intent is not to "sell something" but to understand the
> technical needs so that hopefully we can have a reference for future
> solution-oriented discussions. If a given function can be provided
> without involving an on-path device, this would be great for
> operators (optimize CAPEX/OPEX is our motto).
>=20
>>=20
>> Cheers, S.
>>=20
>> (*) That is the argument for draft-mm-effect-encrypt, for which I=20
>> do support publication (apparently in disagreement with Martin in=20
>> that case:-)
>>=20
>>=20
>>=20
>=20


--o5UHv6jSTiwJcnmP27LI837tnbkCbC77R--

--qKGSPXNXmD1nj2Vg0WISD44ttBWeL76FP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7SGcAAoJEC88hzaAX42iN7EH/A6gn3C7SyqK6t8JE2ANqDxO
d1O2a95mWUnwwSPkjYHNTbWva121UtOWRLAgz6PUAxJIcWUF424w1v9d9gf9/Sd3
Z0bOahyUbek3hnLsPIs/VU2OSYr7/vXr2VnL3lmVR6QLZ3BEjyeqnmnFIsPqOqkF
Ja6dg3NJ330U2mymgmtZliY5Eq/Yl7O13mJA+/bC+AmZCmKvffPN25qR+AI2C+No
43U3PKCsESyHOWeXSkehBOUT4V5D0ZU0g82uBiiGOdLkgL9FG24jzLdtvR+0vEy9
mCI8Y/6ppC4XWFCwGe5K11NDb07dtxeswC+KfMDYVeZJGl2a45Yvf6vgtEeBe4A=
=UARb
-----END PGP SIGNATURE-----

--qKGSPXNXmD1nj2Vg0WISD44ttBWeL76FP--


From nobody Tue Apr 11 11:54:30 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB0B012EC52 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 n_8dam6fRjhe for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 11:54:28 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DC6A12EC51 for <ietf@ietf.org>; Tue, 11 Apr 2017 11:54:27 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.local ([194.88.241.232]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v3BIsIfN097147 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Apr 2017 19:54:19 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [194.88.241.232] claimed to be cupcake.local
Message-ID: <58ED2651.8040109@foobar.org>
Date: Tue, 11 Apr 2017 20:54:09 +0200
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.12 (Macintosh/20170323)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <36f11093-8283-dbcc-68d5-0c7f4267988c@gmail.com>
In-Reply-To: <36f11093-8283-dbcc-68d5-0c7f4267988c@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DI-u-hpVZPCvUQzpnjO_npVzBQs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:54:30 -0000

Brian E Carpenter wrote:
> BTW I don't see ECMP or load balancing listed in section 3. Those
> seem to be major applications of transport layer snooping.

no, any load balancing which needs to scale needs to be stateless, so
you don't want session based mechanisms handling this.

Nick


From nobody Tue Apr 11 13:19:00 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2D4131464 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 13:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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=netapp.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 9jw6D9LX8l97 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 13:18:57 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D23F131457 for <ietf@ietf.org>; Tue, 11 Apr 2017 13:18:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.37,187,1488873600";  d="asc'?scan'208";a="195298392"
Received: from vmwexchts03-prd.hq.netapp.com ([10.122.105.31]) by mx141-out.netapp.com with ESMTP; 11 Apr 2017 13:06:07 -0700
Received: from VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) by VMWEXCHTS03-PRD.hq.netapp.com (10.122.105.31) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 11 Apr 2017 13:17:52 -0700
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Tue, 11 Apr 2017 13:17:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=DaSBduRdASSxjkZdsgxwTW6PTD8IZC2XjK6bnPOapr0=; b=iLccuNk+Kx+yarKpRSbxQN5cFLXYzg6ba6w+ZWzkTJ7Ik1JSwG6W2qmcm9/gWaBB7qJDxot+wUXDyZrUQI1rwvNuLWS2Nr5zcpgECQzkHlJJDU/AR73GIcfnM4INGJhq7YpZ1BfMWN/w92qE10td0G0Jz9doCJcdrZvrvEZYvLs=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1156.namprd06.prod.outlook.com (10.160.157.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 20:17:51 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 20:17:51 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Martin Thomson" <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AdKym8EY4i6VvDHuQjir6aepfU3ztwABQVIAAAYqoQAADesqAAAD5JcA
Date: Tue, 11 Apr 2017 20:17:51 +0000
Message-ID: <D38819F1-A43A-40B6-918C-25AFDE05A4C9@netapp.com>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <f99d9c97-53f9-bac1-7bd1-8effa3ff9732@cs.tcd.ie>
In-Reply-To: <f99d9c97-53f9-bac1-7bd1-8effa3ff9732@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
authentication-results: cs.tcd.ie; dkim=none (message not signed) header.d=none;cs.tcd.ie; dmarc=none action=none header.from=netapp.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [216.240.19.104]
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1156; 7:7ao5C3l7l/+KfT5V4/WUcmy9qbQYEVI8IGQm5xYH0LaId+2i6DxCpNelq0kOAeMI7usQ1Jq9B+p+7No/38b6vYP4oRHBj5kBgaXaz3CVDy/AyFPOvKK37s8aklcZhya+RjUgGcRRy1IrEo60cBs/qSJJyfj5jb72ZlSXI7ffErIZpocRyHKVoTrLENe54FNC3McMOreSLhdl4P+F4sMBmsX8wks4fQXDB+8E/iViraLoYqHXAIsVdv/Mzx1x9UfwQ5oktaIYklthm3EINs8v9ide54VDKyvWTybmNwQQFJfCnyIBnzWikeX/mt7Bw0WdN/qBERrqe/KbfrhXsPipmw==
x-ms-office365-filtering-correlation-id: 25b26373-e30b-45ef-b012-08d48117d474
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BN3PR0601MB1156; 
x-microsoft-antispam-prvs: <BN3PR0601MB11569FEA148AE9C8C8024020A7000@BN3PR0601MB1156.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(32856632585715);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(20161123562025)(20161123560025)(20161123564025)(6072148); SRVR:BN3PR0601MB1156; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1156; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39400400002)(39450400003)(39850400002)(39410400002)(24454002)(377424004)(76176999)(3280700002)(3660700001)(66066001)(4326008)(57306001)(2906002)(6116002)(50986999)(36756003)(99936001)(110136004)(39060400002)(38730400002)(25786009)(102836003)(53546009)(189998001)(33656002)(3846002)(229853002)(6246003)(7736002)(53936002)(54906002)(5660300001)(4001150100001)(6486002)(6506006)(122556002)(6512007)(99286003)(8676002)(81166006)(6436002)(50226002)(8936002)(2900100001)(2950100002)(6916009)(83716003)(230783001)(77096006)(82746002)(93886004)(86362001)(305945005); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1156; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_6D54460E-1679-46DA-8A52-5C6595B5A16D"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 20:17:51.2398 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1156
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PZ4w6TKnhR4sytjOAVL0GcXsdQ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 20:18:58 -0000

--Apple-Mail=_6D54460E-1679-46DA-8A52-5C6595B5A16D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-4-11, at 11:26, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> But regardless of whether or not there
> is a desire for this document, in anything like it's current
> form, I'd be one voice opposed to publication.

+1

I am surprised to see this even being proposed for publication, given =
the comments after the IETF-98 presentation.

Lars

--Apple-Mail=_6D54460E-1679-46DA-8A52-5C6595B5A16D
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-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAljtOewACgkQVLXDCb9w
wVfMkQ//eTyJA2sndo5/DwcOfRpWmPfZrmUsUZPufnLHEzh8AdYs6dNtxVXif/hT
bebwD0GIdujZomuUE6KfXbzmfqDdknFspx10QMDs1R7kzrsjJGP4emhMTK4oSnCn
2ZIhHqPpMN9/hJgr1w4MrQkPW/3zN5WPhiM6+qVwZCq5aZeQtBeYYOSNmpJemtRn
uXzsWnnwzkPIPawtOBqsEMCXLUHecLW+dJv9OF5vK1RZHQrK6J9ZX9H5T/1BntqK
kf3Kb1InW9NiYhKMO/dfKPRe2FoYGL6PgjXDvG2DYg69TBkQi+x2ONj7UEqZ+8sv
224o0SduNMn7xwU1qdpdHj72XOs/W8IU16l78xTXwrhaSiPnejf1biCvFMNAMB5M
pXLG9UBdwT+y44Gd2gJJR5AuB/cB6W2X7Uj2q8Vr/xCNYEj9Q1xWb5h1v9A/I3ds
ILfICIMSBYZccXb0DyG8yhPyQJT6DY5UAIMh+eS38cUpAvOc6+rOTiIf1rf3lWIr
GqsDG/qlQtvZgG3l4/QBhyLZV0ea7U3MtWTBZqeB4LWy9r9qPoiyQJKeDVUD52wt
p+YjLSzj4nTzRmnxoFfqkZKyddhjuGcBRtDcFj4I1QIYs4N87iLgxQyk3olOAm8b
BMzHC6ZhyiZGSPWVKWREhvtKBTUFfk8abUea6HHvlOnVtzvYd1g=
=xua/
-----END PGP SIGNATURE-----

--Apple-Mail=_6D54460E-1679-46DA-8A52-5C6595B5A16D--


From nobody Tue Apr 11 14:10:04 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4ED128C82; Tue, 11 Apr 2017 14:10:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shucheng LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-isis-auto-conf.all@ietf.org, ietf@ietf.org, isis-wg@ietf.org
Subject: Opsdir last call review of draft-ietf-isis-auto-conf-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149194500300.15796.6911396015267944322@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 14:10:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NOQrHEkbbp7KpgCfSpG3gTyPZVs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 21:10:03 -0000

Reviewer: Shucheng LIU
Review result: Ready

I have reviewed review of draft-ietf-isis-auto-conf-04 as part of the
Operational directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written with the
intent of improving the operational aspects of the IETF drafts.
Comments that are not addressed in last call may be included in AD
reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.


   "This document specifies IS-IS auto-configuration mechanisms.  The
key
   components are IS-IS System ID self-generation, duplication
detection
   and duplication resolution.  These mechanisms provide limited
IS-IS
   functions, and so are suitable for networks where plug-and-play
   configuration is expected."


My overall view of the document is Ready for publication.

I read this draft long ago in its earlier version (probably
draft-liu-isis-auto-conf-06) and happy to see that issues (e.g. the
confusing sentence such as “octets of all 0”) are already fixed.  

Some small ones below.

page 3:
> It SHOULD not be changed due to device status change (such as
interface > enable/disable, interface plug in/off, device reboot,
firmware update etc.)

The term “due to” is confusing. It might be change to “It SHOULD not
be changed until the device status change”  or “It SHOULD not be
changed as the device status change” according to the meaning.


Page 8 
> As specified in this document, there are two distinguisher need to
be > self-generated, which is System ID and Router-Fingerprint.  

s/which is/which are


Page 9
>  In a network device, normally there are resources which provide an
> extremely high probability of uniqueness thus could be used as seeds
to > derive distinguisher (e.g. hashing or generating pseudo-random
numbers), > such as:

Suggest to split the sentence to make it more readable.



From nobody Tue Apr 11 16:24:12 2017
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96AC1201F8 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 16:24:10 -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, RP_MATCHES_RCVD=-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 Fdk1VtzJPisq for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 16:24:09 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 5144E126C22 for <ietf@ietf.org>; Tue, 11 Apr 2017 16:24:09 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 26908909B0B; Tue, 11 Apr 2017 19:24:08 -0400 (EDT)
Date: Tue, 11 Apr 2017 19:24:08 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Cc: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170411232408.GE48535@verdi>
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FcwSm1Y-X7SStNlRnhrOpXDmuTM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 23:24:11 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> 
> It is fast looking as if the ability to sustain a large and very 
> well-attended network of interconnected remote hubs might become a 
> necessity rather than merely an appealing alternative...

   +1

   (and this will require some formal process for mike queuing at
the "interconnected remote hubs".)

   IMHO, what's lacking is _only_ the will to make it happen. ;^)

--
John Leslie <john@jlc.net>


From nobody Tue Apr 11 18:16:50 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 25FCF1242F5; Tue, 11 Apr 2017 18:16:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <ops-dir@ietf.org>
Cc: ipsec@ietf.org, draft-ietf-ipsecme-tcp-encaps.all@ietf.org, ietf@ietf.org
Subject: Opsdir telechat review of draft-ietf-ipsecme-tcp-encaps-00
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149195980204.15766.15879884431822692645@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 18:16:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FwIqxkf8zBD4fF8wUu8KZpD7j1w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 01:16:42 -0000

Reviewer: Mahesh Jethanandani
Review result: Ready

I have reviewed this document as part of the Operational
directorate’s ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be
included in AD reviews during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last
call comments.

Document reviewed:  draft-ietf-ipsecme-tcp-encaps-09

Summary: 

This document defines a method for encapsulating both the IKE control
messages as well as the IPSec data messages within a TCP connection.

Document Status:

Ready.

Comments:

The following comments look at the document both from an operational
perspective as well as a management perspective. 

Operational Considerations:

Operational considerations include installation and initial setup,
migration path, requirements on other protocols, impact on network
operations and verification of correct operation.

The document has adequately addressed issues related to initial setup,
migration path from using UDP over port 500, to port 4500 to using
TCP.

Management Considerations:

Management considerations include interoperability, fault management,
configuration management, accounting, performance and security.

Already acknowledged that there is performance impact in carrying IKE
and IPSec data messages over TCP. This includes limitation of message
lengths to UDP datagram ESP payload lengths, further impacting the
performance of the encapsulation method.

Document talks about reconfiguration of TCP encapsulation on both the
TCP Originator and TCP Responder. That includes configuration of ports
the Responder will listen on.

A run of idnits returns the following warnings:

   (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  == Missing Reference: 'Appendix A' is mentioned on line 305, but not
defined

  == Missing Reference: 'Section 4' is mentioned on line 363, but not
defined

  == Missing Reference: 'ChangeCipherSpec' is mentioned on line 922,
but not
     defined

  == Missing Reference: 'CERTREQ' is mentioned on line 765, but not
defined

  == Missing Reference: 'CERT' is mentioned on line 770, but not
defined

  == Missing Reference: 'CP' is mentioned on line 814, but not
defined


     Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment
(--).



From nobody Tue Apr 11 19:26:40 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE40B1242F5 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:26:38 -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 OmrVk222P_W7 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:26:37 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 B91B2126C3D for <ietf@ietf.org>; Tue, 11 Apr 2017 19:26:37 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id i5so6758965pfc.2 for <ietf@ietf.org>; Tue, 11 Apr 2017 19:26:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Qkzm7q7sbP2gba0s+FziYxeMnkllrJNzqshztJTLgpA=; b=JHntlK83XiZke6Gk78OySTOD/gIhgzXD34GcF1b/+ZcXx8bWyja2ZnLnEVfTLTaBEh kOSsl0tzahxz0lX3bm6qEzRL1kfcmwMRYNk0EdBwQ03vrOWzuyvPt/i7Q+iqGIElGvD+ 0r80DrR5jMAh+1XNAeUPwBOYt/C5eJlq+nyQPK8IsJGa1dM6OQGUcGZtDkXsZucl7Kly VrR2C4Q0mhNiMXOI2DKQisIZ7NDneY2h9WcxwsKS699XmnHigsffuu8zYqObtynn4kwh 8lDwj8OnYk50eMqLL/7Nvrjac/LzysUjBkATRU1t1HHzD+ZUeLmtDPUm07lFP4iWwPt8 gZ9Q==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Qkzm7q7sbP2gba0s+FziYxeMnkllrJNzqshztJTLgpA=; b=FB83UhpsFxPGwxxY+I0N+7ipjRnjfGDWEcBzNKqR5SVGdmnNhnbiTZ1yxQHwBI7Kri FPMnmjQnL/s283ZJc6ASj5z2xB7APzLUIGGlgS1jaaYbmPCv24IH3xyjt+/bDQZLZrB+ Uo0d0wuvpCDksEaIHhDLYAFw+y7YGiIQARyL9OH03IVWGob6pgnQLhuZ2pYqNZhq33th A7ljnoozyvnJsazlBHnyxEaf3gHdtav/36OOvkIKa59wOcGn11QGFS3VdsTMv8ixHXKR VI8Go0ffCbxVFfIewFUnoCjlUr2pojxKieDKX0KqU93BpIIkI4RRpGQdpJ+6lS3E6U3W TPNw==
X-Gm-Message-State: AFeK/H1y2hP96Bm7xKQgEDXrOlaJfG/fRGdyj4nxnCBtcFzybVm01aipmL5pnamQUXUbLA==
X-Received: by 10.98.80.209 with SMTP id g78mr63137484pfj.163.1491963997220; Tue, 11 Apr 2017 19:26:37 -0700 (PDT)
Received: from [172.26.34.236] ([104.129.192.114]) by smtp.gmail.com with ESMTPSA id w129sm32748449pfb.130.2017.04.11.19.26.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 19:26:36 -0700 (PDT)
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: Nick Hilliard <nick@foobar.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <36f11093-8283-dbcc-68d5-0c7f4267988c@gmail.com> <58ED2651.8040109@foobar.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d1a9e65b-1ab1-ab61-ae5b-243ebf6da800@gmail.com>
Date: Wed, 12 Apr 2017 14:26:35 +1200
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: <58ED2651.8040109@foobar.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KJwIJSsdYAPXOucvN73AEFnwNC4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 02:26:39 -0000

On 12/04/2017 06:54, Nick Hilliard wrote:
> Brian E Carpenter wrote:
>> BTW I don't see ECMP or load balancing listed in section 3. Those
>> seem to be major applications of transport layer snooping.
> 
> no, any load balancing which needs to scale needs to be stateless, so
> you don't want session based mechanisms handling this.

Server load balancing is often stateful, and even stateless SLB
usually includes transport info in the hash. Or so I learned while
working on RFC 7098. People who know also informed me that ECMP
sometimes (not always) uses transport info (see RFC 6438).

   Brian


From nobody Tue Apr 11 19:38:10 2017
Return-Path: <weigengyu@bupt.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A01128BB7 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level: 
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] 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 LGky8smAxeZa for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:38:01 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 9C30D126CD8 for <ietf@ietf.org>; Tue, 11 Apr 2017 19:37:58 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.255.40.36]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 9CE6A19F380; Wed, 12 Apr 2017 10:37:56 +0800 (HKT)
Message-ID: <52AFE50B189544AFB2744028519A173D@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Mark Nottingham" <mnot@mnot.net>, "Carsten Bormann" <cabo@tzi.org>
Cc: <art@ietf.org>, <draft-ietf-core-coap-tcp-tls.all@ietf.org>, <ietf@ietf.org>, <core@ietf.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net>
In-Reply-To: <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net>
Subject: Re: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Date: Wed, 12 Apr 2017 10:38:12 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j4UYmT8V-IJFL01H3M51tzuXoC8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 02:38:03 -0000

Hi Mark,

> OK. Just curious -- is there a strong motivation here?
> It seems very odd to tunnel HTTP-like semantics over a custom UDP protocol 
> (COAP) over WebSockets over HTTP again,
> rather than just using HTTP (which AIUI you already have a mapping to).

It is meaningful and interesting.
CoAP/UDP/IPv6 protocl stack can run well within CoRE environments.
But if CoAP/UDP is tried in the Internet, it will be blocked due to 
NAT/firewall etcs based on tests done here a few years ago.
CoAP/TCP or CoAP/WSS could help CoAP messages and applications available 
around Internet.

We have done some works about this topics.
The following are two abstracts of my master course students' theses, in 
which may be interested.

THE RESEARCH AND DEVELOPMENT OF CoAP over TCP
ABSTRACT
The CoAP protocol is a restricted resource application protocol. In the CoAP 
protocol research and application, the default CoAP protocol
stack use UDP as the transport layer。In the Ethernet environment, data 
transmission will be affected because of the existence of the firewall .
For the reason that CoAP can be better applied to the current Internet 
environment and cloud environment, IETF working group proposed CoAP over 
TCP,
CoAP protocol stack use TCP as the transport layer .In this context, CoAP 
over TCP is studied and CoAP over TCP is implemented based on the
open source framework Californium. The CoAP over TCP is implemented as a 
client in the real Internet environment and the function of the
implementation is evaluated. CoAP over TCP is the Internet of Things cloud 
platform services, so AWS environment is used to achieve CoAP over TLS/TCP
and the default protocol stack performance comparison.
In this paper, the significance of CoAP over TCP is expatiated, and CoAP 
over TCP is studied. After that, the overall architecture of Californium 
framework
is deeply analyzed, and the design scheme of CoAP over TCP is proposed. The 
transport layer is extended on the basis of the original frame structure.
Based on the design scheme, the modules are designed and designed in detail. 
On the core of the class through the class diagram describes the expansion
of the relationship between the various modules. The network layer, protocol 
layer and application layer implementation process are analyzed in detail.
Afterwards, we study the proxy between CoAP over TCP and default protocol 
stack, and propose the message type conversion problem and solution of 
CoAPToCoAP proxy.
The paper concludes the relevant work, and puts forward the research 
direction of the next step.
KEY WORDS: CoAP over TCP Proxy Californium Frame

THE DESIGN AND IMPLEMENTATION OF COAP OVER WEBSOCKET
ABSTRACT
The concept of Internet of Things (IoT) was originally proposed almost 
twenty years ago.  Over the past many years, IoT has gone through huge and 
rapid development,
and the field of Wireless Sensor Network (WSN) has witnessed remarkable 
advancement in particular. Compared to the progress of WSN, the practical 
service
and application of IoT still has a very long way to go. Although current 
industry standards can meet those equipments like smart phones, they are not 
quite suitable
for constrained nodes which are often battery supported and has relatively 
lower processing ability. Driven by such demands, the IETF set up CoRE 
working group
to design a RESTful application protocol which can perform better among 
constrained nodes in constrained environments.
The protocol was named Constrained Application Protocol (CoAP) and it was 
later standardized as RFC 7252.
This paper analizes the features and defect of the HTTP/CoAP proxy proposed 
in RFC 7252, and explains the CoAP over WebSocket proxy as well as its 
advantages over
the HTTP/CoAP proxy. Then a design and implementation of CoAP over WebSocket 
based on Californium open-source framework is given. Performance tests and
experiments have shown that the CoAP over WebSocket approach has some 
significant advantages over HTTP/CoAP proxy in term of response time and 
high concurrency
requests processing ability.
KEY WORDS: computer network, iot, coap, network proxy, websocket


Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Mark Nottingham
Sent: Tuesday, April 11, 2017 8:39 AM
To: Carsten Bormann
Cc: art@ietf.org ; draft-ietf-core-coap-tcp-tls.all@ietf.org ; ietf@ietf.org 
; core@ietf.org
Subject: Re: [core] Artart last call review of 
draft-ietf-core-coap-tcp-tls-07

Hi Carsten,

Couple of quic responses below.

On 10 Apr 2017, at 7:46 pm, Carsten Bormann <cabo@tzi.org> wrote:

> I agree that the introduction should focus on the Browser use case and 
> keep out of the firewall traversal jungle.

OK. Just curious -- is there a strong motivation here? It seems very odd to 
tunnel HTTP-like semantics over a custom UDP protocol (COAP) over WebSockets 
over HTTP again, rather than just using HTTP (which AIUI you already have a 
mapping to).


>> Section 7 defines a number of new URI schemes for COAP protocols.
>> Syntactically, they use "+" to separate "coap" from the underlying
>> transport(-ish) protocol that they're bound to; e.g., "coap+tcp". This
>> syntax is allowed by RFC3986, but is unprecedented, and implies a
>> sub-syntax convention similar to those used in media types, etc. Is
>> there an expectation that other URI schemes starting with "coap+" are
>> reserved?
>
> There is no such expectation.
>
> We did have the discussion about reserved URI scheme prefixes in the IETF, 
> and as I recall, the result was that there are none.  While it would be a 
> bit weird to register a URI scheme starting with coap+ or coaps+ that is 
> unrelated to CoAP, only the slightly boggled response from an expert 
> review is in the way of that happening.
>
> Would the scheme names be more palatable with a dash instead of a plus?
> Careful choice of the scheme name mostly benefits the implementer, so it 
> can be changed in the spec (at the cost of changing existing 
> implementations).

OK. I'm mostly noting this in case other folks feel that this is a bad 
precedent for URI schemes; I think the bigger concern is the one below.


>> Defining URI schemes that switch transport protocol based upon their
>> name deserves wider review as well; this has been a contentious topic
>> in the past, and it would be good to understand what tradeoffs are
>> being made by doing so. Locking identifiers into a specific transport
>> protocol sacrifices much of the power of URLs.
>
> The “siloing” of URIs along schemes is indeed a problem, which started 
> for CoAP with the separation of the coap:/coaps: name spaces.  The CoRE WG 
> did not see it as its task to address this shortcoming.  So, for now, we’ll 
> have to live with it; approaches such as 
> draft-silverajan-core-coap-protocol-negotiation are trying to address its 
> practicalities.

By defining multiple URI schemes for different transports of the same 
protocol, the WG has taken a position as to what the solution is. I'm 
finding it difficult to square this with the continuing characterisation of 
CORE as "RESTful".


>> Furthermore, creating
>> "coap+ws" to denote a specific protocol over WebSockets (which has its
>> own URI scheme) is questionable; taken to its natural conclusion,
>> we'll have a proliferation of URI schemes for things over WebSockets.
>
> I’m not sure that a proliferation will happen — WebSockets is mostly 
> used for tightly bound proprietary protocols between a JavaScript mobile 
> code client and a server that provides this mobile code client.  On the 
> other hand, deciding to never use URIs to refer to resources available 
> over a WebSockets protocol strikes me as an unnecessary restriction.
>
>> Will COAP take the same approach for HTTP?
>
> Not sure what this question is leading into.
> (We do have a defined relationship with HTTP, in RFC 7252 and RFC 8075.
> But maybe this is about something different.)

I mean to ask whether there will be a need for a "coap+http" URI scheme; it 
seems like a logical conclusion of the approach taken here.


>> I would suggest a wider discussion of these issues on art@ / uri@.
>
> Indeed, a wider discussion of these longstanding issues would be useful.
> I’m not sure that waiting for their resolution is blocking this spec.
>
>> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
>> URI, using a well-known URI in the "wss" scheme. However, "wss" is not
>> defined to use well-known URIs, so this is an invalid use.
>
> This incorrect use of RFC 5785 is indeed embarrassing.  More about that 
> later.

OK. The other obvious path is to opt wss:// (and ws://?) into RFC5785, but I 
think that would take a separate RFC that updates their scheme 
registrations. Not sure whether there would be any pushback in that 
community (but I can't see any immediate reason why there would be).


>> Section 8.1 makes it Mandatory to Implement the protocol without any
>> security ("NoSec"). This seems counter to best practice in the IETF,
>> but I'll defer to the Security Area review.
>
> Since it is the implementers who will decide whether they implement this, 
> this co-author could live with making implementing NoSec completely 
> optional.  (It will be anyway, in practice, at the level of what is 
> actually configured.)  The important point(*) from the WG perspective here 
> is that TLS is mandatory to implement, with the specifics depending on the 
> security mode needed (cf. RFC 7925).  (Note also that there are other ways 
> to provide security with CoAP.)

Ack. Again, this was mostly a note to bring it to others' attention; the use 
of the phrase "Mandatory to Implement" when applied to "no security" just 
seems odd.

Cheers,

>
> Grüße, Carsten
>
> (*) 
> https://github.com/core-wg/coap-tcp-tls/commit/fe348f543fc45e981e38e9354242012afb28dc60
>

--
Mark Nottingham   https://www.mnot.net/

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


From nobody Tue Apr 11 19:42:38 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903D5126CD8; Tue, 11 Apr 2017 19:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 XcrNX87zLUnb; Tue, 11 Apr 2017 19:42:29 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 401621242F5; Tue, 11 Apr 2017 19:42:29 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CFC6822E253; Tue, 11 Apr 2017 22:42:20 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Mark Nottingham <mnot@mnot.net>
X-Priority: 3
In-Reply-To: <52AFE50B189544AFB2744028519A173D@WeiGengyuPC>
Date: Wed, 12 Apr 2017 12:42:16 +1000
Cc: Carsten Bormann <cabo@tzi.org>, art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <52AFE50B189544AFB2744028519A173D@WeiGengyuPC>
To: weigengyu <weigengyu@bupt.edu.cn>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/29IWEhOYRD23YyO4RucKQYaC-mY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 02:42:32 -0000

So, is COAP using WebSockets for browser access, or for firewall =
traversal? The paper below seems to indicate the latter, and so the =
original question remains.

Also, the assertions about firewalls are interesting; we're hearing very =
different assertions in the discussions of QUIC (e.g,. 90%+ success =
rates for UDP protocols).

Cheers,



> On 12 Apr 2017, at 12:38 pm, weigengyu <weigengyu@bupt.edu.cn> wrote:
>=20
> Hi Mark,
>=20
>> OK. Just curious -- is there a strong motivation here?
>> It seems very odd to tunnel HTTP-like semantics over a custom UDP =
protocol (COAP) over WebSockets over HTTP again,
>> rather than just using HTTP (which AIUI you already have a mapping =
to).
>=20
> It is meaningful and interesting.
> CoAP/UDP/IPv6 protocl stack can run well within CoRE environments.
> But if CoAP/UDP is tried in the Internet, it will be blocked due to =
NAT/firewall etcs based on tests done here a few years ago.
> CoAP/TCP or CoAP/WSS could help CoAP messages and applications =
available around Internet.
>=20
> We have done some works about this topics.
> The following are two abstracts of my master course students' theses, =
in which may be interested.
>=20
> THE RESEARCH AND DEVELOPMENT OF CoAP over TCP
> ABSTRACT
> The CoAP protocol is a restricted resource application protocol. In =
the CoAP protocol research and application, the default CoAP protocol
> stack use UDP as the transport layer=E3=80=82In the Ethernet =
environment, data transmission will be affected because of the existence =
of the firewall .
> For the reason that CoAP can be better applied to the current Internet =
environment and cloud environment, IETF working group proposed CoAP over =
TCP,
> CoAP protocol stack use TCP as the transport layer .In this context, =
CoAP over TCP is studied and CoAP over TCP is implemented based on the
> open source framework Californium. The CoAP over TCP is implemented as =
a client in the real Internet environment and the function of the
> implementation is evaluated. CoAP over TCP is the Internet of Things =
cloud platform services, so AWS environment is used to achieve CoAP over =
TLS/TCP
> and the default protocol stack performance comparison.
> In this paper, the significance of CoAP over TCP is expatiated, and =
CoAP over TCP is studied. After that, the overall architecture of =
Californium framework
> is deeply analyzed, and the design scheme of CoAP over TCP is =
proposed. The transport layer is extended on the basis of the original =
frame structure.
> Based on the design scheme, the modules are designed and designed in =
detail. On the core of the class through the class diagram describes the =
expansion
> of the relationship between the various modules. The network layer, =
protocol layer and application layer implementation process are analyzed =
in detail.
> Afterwards, we study the proxy between CoAP over TCP and default =
protocol stack, and propose the message type conversion problem and =
solution of CoAPToCoAP proxy.
> The paper concludes the relevant work, and puts forward the research =
direction of the next step.
> KEY WORDS: CoAP over TCP Proxy Californium Frame
>=20
> THE DESIGN AND IMPLEMENTATION OF COAP OVER WEBSOCKET
> ABSTRACT
> The concept of Internet of Things (IoT) was originally proposed almost =
twenty years ago.  Over the past many years, IoT has gone through huge =
and rapid development,
> and the field of Wireless Sensor Network (WSN) has witnessed =
remarkable advancement in particular. Compared to the progress of WSN, =
the practical service
> and application of IoT still has a very long way to go. Although =
current industry standards can meet those equipments like smart phones, =
they are not quite suitable
> for constrained nodes which are often battery supported and has =
relatively lower processing ability. Driven by such demands, the IETF =
set up CoRE working group
> to design a RESTful application protocol which can perform better =
among constrained nodes in constrained environments.
> The protocol was named Constrained Application Protocol (CoAP) and it =
was later standardized as RFC 7252.
> This paper analizes the features and defect of the HTTP/CoAP proxy =
proposed in RFC 7252, and explains the CoAP over WebSocket proxy as well =
as its advantages over
> the HTTP/CoAP proxy. Then a design and implementation of CoAP over =
WebSocket based on Californium open-source framework is given. =
Performance tests and
> experiments have shown that the CoAP over WebSocket approach has some =
significant advantages over HTTP/CoAP proxy in term of response time and =
high concurrency
> requests processing ability.
> KEY WORDS: computer network, iot, coap, network proxy, websocket
>=20
>=20
> Regards,
>=20
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Mark Nottingham
> Sent: Tuesday, April 11, 2017 8:39 AM
> To: Carsten Bormann
> Cc: art@ietf.org ; draft-ietf-core-coap-tcp-tls.all@ietf.org ; =
ietf@ietf.org ; core@ietf.org
> Subject: Re: [core] Artart last call review of =
draft-ietf-core-coap-tcp-tls-07
>=20
> Hi Carsten,
>=20
> Couple of quic responses below.
>=20
> On 10 Apr 2017, at 7:46 pm, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>> I agree that the introduction should focus on the Browser use case =
and keep out of the firewall traversal jungle.
>=20
> OK. Just curious -- is there a strong motivation here? It seems very =
odd to tunnel HTTP-like semantics over a custom UDP protocol (COAP) over =
WebSockets over HTTP again, rather than just using HTTP (which AIUI you =
already have a mapping to).
>=20
>=20
>>> Section 7 defines a number of new URI schemes for COAP protocols.
>>> Syntactically, they use "+" to separate "coap" from the underlying
>>> transport(-ish) protocol that they're bound to; e.g., "coap+tcp". =
This
>>> syntax is allowed by RFC3986, but is unprecedented, and implies a
>>> sub-syntax convention similar to those used in media types, etc. Is
>>> there an expectation that other URI schemes starting with "coap+" =
are
>>> reserved?
>>=20
>> There is no such expectation.
>>=20
>> We did have the discussion about reserved URI scheme prefixes in the =
IETF, and as I recall, the result was that there are none.  While it =
would be a bit weird to register a URI scheme starting with coap+ or =
coaps+ that is unrelated to CoAP, only the slightly boggled response =
from an expert review is in the way of that happening.
>>=20
>> Would the scheme names be more palatable with a dash instead of a =
plus?
>> Careful choice of the scheme name mostly benefits the implementer, so =
it can be changed in the spec (at the cost of changing existing =
implementations).
>=20
> OK. I'm mostly noting this in case other folks feel that this is a bad =
precedent for URI schemes; I think the bigger concern is the one below.
>=20
>=20
>>> Defining URI schemes that switch transport protocol based upon their
>>> name deserves wider review as well; this has been a contentious =
topic
>>> in the past, and it would be good to understand what tradeoffs are
>>> being made by doing so. Locking identifiers into a specific =
transport
>>> protocol sacrifices much of the power of URLs.
>>=20
>> The =E2=80=9Csiloing=E2=80=9D of URIs along schemes is indeed a =
problem, which started for CoAP with the separation of the coap:/coaps: =
name spaces.  The CoRE WG did not see it as its task to address this =
shortcoming.  So, for now, we=E2=80=99ll have to live with it; =
approaches such as draft-silverajan-core-coap-protocol-negotiation are =
trying to address its practicalities.
>=20
> By defining multiple URI schemes for different transports of the same =
protocol, the WG has taken a position as to what the solution is. I'm =
finding it difficult to square this with the continuing characterisation =
of CORE as "RESTful".
>=20
>=20
>>> Furthermore, creating
>>> "coap+ws" to denote a specific protocol over WebSockets (which has =
its
>>> own URI scheme) is questionable; taken to its natural conclusion,
>>> we'll have a proliferation of URI schemes for things over =
WebSockets.
>>=20
>> I=E2=80=99m not sure that a proliferation will happen =E2=80=94 =
WebSockets is mostly used for tightly bound proprietary protocols =
between a JavaScript mobile code client and a server that provides this =
mobile code client.  On the other hand, deciding to never use URIs to =
refer to resources available over a WebSockets protocol strikes me as an =
unnecessary restriction.
>>=20
>>> Will COAP take the same approach for HTTP?
>>=20
>> Not sure what this question is leading into.
>> (We do have a defined relationship with HTTP, in RFC 7252 and RFC =
8075.
>> But maybe this is about something different.)
>=20
> I mean to ask whether there will be a need for a "coap+http" URI =
scheme; it seems like a logical conclusion of the approach taken here.
>=20
>=20
>>> I would suggest a wider discussion of these issues on art@ / uri@.
>>=20
>> Indeed, a wider discussion of these longstanding issues would be =
useful.
>> I=E2=80=99m not sure that waiting for their resolution is blocking =
this spec.
>>=20
>>> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
>>> URI, using a well-known URI in the "wss" scheme. However, "wss" is =
not
>>> defined to use well-known URIs, so this is an invalid use.
>>=20
>> This incorrect use of RFC 5785 is indeed embarrassing.  More about =
that later.
>=20
> OK. The other obvious path is to opt wss:// (and ws://?) into RFC5785, =
but I think that would take a separate RFC that updates their scheme =
registrations. Not sure whether there would be any pushback in that =
community (but I can't see any immediate reason why there would be).
>=20
>=20
>>> Section 8.1 makes it Mandatory to Implement the protocol without any
>>> security ("NoSec"). This seems counter to best practice in the IETF,
>>> but I'll defer to the Security Area review.
>>=20
>> Since it is the implementers who will decide whether they implement =
this, this co-author could live with making implementing NoSec =
completely optional.  (It will be anyway, in practice, at the level of =
what is actually configured.)  The important point(*) from the WG =
perspective here is that TLS is mandatory to implement, with the =
specifics depending on the security mode needed (cf. RFC 7925).  (Note =
also that there are other ways to provide security with CoAP.)
>=20
> Ack. Again, this was mostly a note to bring it to others' attention; =
the use of the phrase "Mandatory to Implement" when applied to "no =
security" just seems odd.
>=20
> Cheers,
>=20
>>=20
>> Gr=C3=BC=C3=9Fe, Carsten
>>=20
>> (*) =
https://github.com/core-wg/coap-tcp-tls/commit/fe348f543fc45e981e38e935424=
2012afb28dc60
>>=20
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Tue Apr 11 19:55:28 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F971293F4 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:55:26 -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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 Cg3mBmKPh2Rn for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 19:55:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A24E71293E0 for <ietf@ietf.org>; Tue, 11 Apr 2017 19:55:24 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id F2A45200A3 for <ietf@ietf.org>; Tue, 11 Apr 2017 23:20:04 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7E14E636E0 for <ietf@ietf.org>; Tue, 11 Apr 2017 22:55:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <20170411232408.GE48535@verdi>
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 11 Apr 2017 22:55:23 -0400
Message-ID: <15694.1491965723@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qUxTqL6DxCkpjplTCUj8IEvqIrQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 02:55:27 -0000

--=-=-=
Content-Type: text/plain


John Leslie <john@jlc.net> wrote:
    >> It is fast looking as if the ability to sustain a large and very
    >> well-attended network of interconnected remote hubs might become a
    >> necessity rather than merely an appealing alternative...

    >    +1

    >    (and this will require some formal process for mike queuing at the
    > "interconnected remote hubs".)

Agreed.

Don't cancel SFO; just renegotiate it for much a smaller group of west-coast
"locals".   Maybe we can do this with minimal impact to the contract.

So we have 99, 100, and 101 to get all the mike queue and remote hubs working.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljtlxsACgkQgItw+93Q
3WVROgf8C9+EiV65sAdhpxWb1mfF5eyIS6OkZ1oXx0pIu/a5B8Aqffg5EsZ961E+
AtTnpQkiSy6H+dYV8W9qL4vrLFz0ClijfnI8G3ToQtcIRzoZbeEy9v84R65Z5Blg
7TNTEjAxUrvcq5JLk2ESHV53euZBfhqeOdzVpuThEWXx1p//kRIy5F1ghhIMoUfW
v0tvU7Y/WV1+zVJC1r3Vcy+RevvyhySLtNkvTm6eop0xxtFJc6X6ToRfZDqaKnbo
m+E7ahoIMjp3/201g8U1WITzcrIrxR7j7B0L510VSTJcN/MweoKG/Bi00VcUJ85i
iJ8i18aFABHc6u0JPj46P+z7xpkmOA==
=ZCIU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 11 21:04:47 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8563126B71; Tue, 11 Apr 2017 21:04:45 -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 OyZA3icPqMiG; Tue, 11 Apr 2017 21:04:44 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 9CFD012009C; Tue, 11 Apr 2017 21:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3C44YFs013672; Wed, 12 Apr 2017 06:04:34 +0200 (CEST)
Received: from client-0052.vpn.uni-bremen.de (client-0052.vpn.uni-bremen.de [134.102.107.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w2r0L04mjzDHMj; Wed, 12 Apr 2017 06:04:33 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3
In-Reply-To: <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net>
Date: Wed, 12 Apr 2017 06:04:33 +0200
Cc: weigengyu <weigengyu@bupt.edu.cn>, art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
X-Mao-Original-Outgoing-Id: 513662673.384077-8d9577bc6a7635a03537385cb9593471
Content-Transfer-Encoding: quoted-printable
Message-Id: <9302A268-50CF-4688-A79D-8343E5B9B7CE@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <52AFE50B189544AFB2744028519A173D@WeiGengyuPC> <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AOhFVXHVC-EpCqk9iFPoulfeXMI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 04:04:46 -0000

On Apr 12, 2017, at 04:42, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> So, is COAP using WebSockets for browser access, or for firewall =
traversal? The paper below seems to indicate the latter, and so the =
original question remains.

Can=E2=80=99t answer that for Gengyu, but the term =E2=80=9Cfirewall=E2=80=
=9D occurs in the CoAP over TCP abstract, not in the CoAP over =
WebSockets one.

I continue to maintain that for CoAP over WebSockets the access to CoAP =
proxies from browsers is the motivating case.  (Yes, these could also be =
HTTP to CoAP cross-protocol proxies, but there are impedance mismatches =
here; e.g., for a browser application that wants to observe a CoAP =
resource.)

> Also, the assertions about firewalls are interesting; we're hearing =
very different assertions in the discussions of QUIC (e.g,. 90%+ success =
rates for UDP protocols).

Apart from the backend motivation, the main motivation for CoAP over TCP =
was easier NAT traversal (UDP bindings are timed out much faster in most =
NATs).  This may extend to other middleboxes, including firewalls that =
build (and then time out) UDP-based state.

I=E2=80=99m not sure the QUIC numbers transfer to this use case very =
well, as QUIC is mostly used for web page access from browsers, so short =
NAT binding timeouts don=E2=80=99t matter that much.  For a sensor that =
needs to be accessed every 30 minutes, these are much more of an issue.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 11 21:12:35 2017
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4451287A7 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 21:12:34 -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, RP_MATCHES_RCVD=-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 0iVXt_WN9Hhx for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 21:12:32 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 988B1127342 for <ietf@ietf.org>; Tue, 11 Apr 2017 21:12:31 -0700 (PDT)
Received: from [192.168.1.10] (unknown [112.200.233.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8D31E18014F3 for <ietf@ietf.org>; Wed, 12 Apr 2017 06:12:29 +0200 (CEST)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
From: Loa Andersson <loa@pi.nu>
Message-ID: <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
Date: Wed, 12 Apr 2017 12:12:14 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <15694.1491965723@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OFfcQdLFiGi10xv8t7IDWGw9fXo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 04:12:34 -0000

Michael,

On 2017-04-12 10:55, Michael Richardson wrote:
>
> John Leslie <john@jlc.net> wrote:
>     >> It is fast looking as if the ability to sustain a large and very
>     >> well-attended network of interconnected remote hubs might become a
>     >> necessity rather than merely an appealing alternative...
>
>     >    +1
>
>     >    (and this will require some formal process for mike queuing at the
>     > "interconnected remote hubs".)
>
> Agreed.
>
> Don't cancel SFO; just renegotiate it for much a smaller group of west-coast
> "locals".   Maybe we can do this with minimal impact to the contract.
>
> So we have 99, 100, and 101 to get all the mike queue and remote hubs working.
>
It is hard to see the logic. I've just had the experience of "attending"
an IETF meeting remotely.

Let me first say that I very much appreciate the effort made by e.g. the
meetecho people. The experience of listening to a meeting on meetecho
and sitting in the room listening is very close. All the time until
someone that sits in the middle of the room don't care to go the mike
to make a comment, but just shout it out. When this happens you just
don't lose the comment, but you also lose much of the context for the
continued discussion.

Participate in the discussion remotely, is just not there yet. This is
not (primarily) technology, but queue management and queue discipline.

I know that this is getting better, but to work smoothly I think we need
the set uo e.g. ITU-T have in Geneva where every participant has his/her
own microphone and the management of the for remote participants and
people attending in the room would be the same.

It quite often happens (it has happened to me) that someone notify the
chairs that "there is someone wanting to say something on the meetecho",
only when that happens that particular discussion is already "taken to
the list".

But an IETF meeting is so much more than the moderate number of hours
you spend in meeting rooms, if you participate remotely you miss what
is probably the most important aspect of an IETF F2F - the 10-15
corridor meetings you have each day.

I'd say cancel SFO and move to place where we all have an equal chance
to attend, even if you have made a business trip to Iran or somewhere
else in the Middle East, and where we don't have to give out passwords
to e.g. laptops that may contain business critical information.

/Loa


> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Tue Apr 11 21:56:03 2017
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547E41287A7 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 21:56:01 -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 r428G0GhLL7c for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 21:55:59 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 ECBF91292FC for <ietf@ietf.org>; Tue, 11 Apr 2017 21:55:52 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id o126so8218115pfb.3 for <ietf@ietf.org>; Tue, 11 Apr 2017 21:55:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=b7LhIq9QRGoa21OBs1U7b7/eIHxaX75V3v5n48wy5qM=; b=D6396ghc0PS//OnNFRx+/IThRjMLBT1k2s0WVGydT5l1DV4lVV3AhBnT/2iSQdlnkR E6G0pXECOUt1iNfFvMaB8TcicqyWRakyn4BV+/wKW9zqpRKwY+xiLuKPYjv0kNUgSzQJ nIBdsn52ZpWvG/rwHFojLsSkxbWemCsspUmwchfAKCo7jFuL7uTj1pn6jkgg1kXZ7FlS BuByWS26/vogcrGh2SH6zSl2mzOu4Al0iaOMVjxw+ufrACK6KFvUQvUkrwG8RHX6EWrU IWoJDFHmtp1YUcn9+L8osbOB1rMYc0wIEBpt3EHIXGPkbQ+LBFzGq9ok1lUeumh9JeYM HGAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=b7LhIq9QRGoa21OBs1U7b7/eIHxaX75V3v5n48wy5qM=; b=eB9HddMkl53mK44wruqvPJvHzYfIqnX4/5STfACCoObWni1siUy8uWaozXRP1JwQ4v 7XeJEJEickoXUEuwxLlWHlz+32uNDRKHVl8VkJbHkJulAR4K1PLHb1SVP6msPsh/wl5a XUz2Q/8q3Ek0Vs7zhlOaazXF0QYL4gDc1B2JakA2M3OKfB82Mmten3BqX4Nhe4GbxWuz oeef1z4931Q89wZGkRUPD0qJk2di+ExOsxrjgXfKoDvIOzjfwQjgv1Xj1XIWk6phGZ7a 74972hGulgoAMDEXsFOEK8sW8SoShM7Kqc2JJz6M2R5gwyJodMsusVnBwVRbwMuaRGBW DfvA==
X-Gm-Message-State: AN3rC/4ejjUFaD6eX6EtVnmZGRDL6jgg6lZY2DyDuUIJGZgG+dbNUGP6c07P5eiw6VmkEQ==
X-Received: by 10.98.8.143 with SMTP id 15mr1239163pfi.268.1491972952617; Tue, 11 Apr 2017 21:55:52 -0700 (PDT)
Received: from [192.168.1.4] ([76.126.247.72]) by smtp.gmail.com with ESMTPSA id h14sm33477063pgn.64.2017.04.11.21.55.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 21:55:51 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Tue, 11 Apr 2017 21:55:49 -0700
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Nick Hilliard <nick@foobar.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <F338C101-0929-4F5D-89BD-8E6D64836CF4@gmail.com>
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <36f11093-8283-dbcc-68d5-0c7f4267988c@gmail.com> <58ED2651.8040109@foobar.org> <d1a9e65b-1ab1-ab61-ae5b-243ebf6da800@gmail.com>
In-Reply-To: <d1a9e65b-1ab1-ab61-ae5b-243ebf6da800@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wYHFUHSW1q_xkU2_JeTmZLqLwgM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 04:56:01 -0000

Brian,

ECMP and LAG (often same code) in most cases indeed use 5 tuples to populate hashing buckets for per flow load balancing.
Cheers,
Jeff
On 4/11/17, 19:26, "ietf on behalf of Brian E Carpenter" <ietf-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:

    On 12/04/2017 06:54, Nick Hilliard wrote:
    > Brian E Carpenter wrote:
    >> BTW I don't see ECMP or load balancing listed in section 3. Those
    >> seem to be major applications of transport layer snooping.
    > 
    > no, any load balancing which needs to scale needs to be stateless, so
    > you don't want session based mechanisms handling this.
    
    Server load balancing is often stateful, and even stateless SLB
    usually includes transport info in the hash. Or so I learned while
    working on RFC 7098. People who know also informed me that ECMP
    sometimes (not always) uses transport info (see RFC 6438).
    
       Brian
    
    



From nobody Tue Apr 11 23:44:19 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1471127275 for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 23:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 STj-oYNwGfFL for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 23:44:15 -0700 (PDT)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C77C12420B for <ietf@ietf.org>; Tue, 11 Apr 2017 23:44:15 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id BD0D5100B50; Wed, 12 Apr 2017 08:44:13 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.61]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 9C65640058; Wed, 12 Apr 2017 08:44:13 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 08:44:13 +0200
From: <mohamed.boucadair@orange.com>
To: Nico Williams <nico@cryptonector.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSsuepcxG3Gt+qPke8vqYsnz4RHKHBQDOw
Date: Wed, 12 Apr 2017 06:44:12 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4C138@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost>
In-Reply-To: <20170411171831.GA23461@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
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/ietf/7uPEZVW7AX5cn0VMa3Tq064LCLU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 06:44:18 -0000

Hi Nico,=20

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Nico Williams [mailto:nico@cryptonector.com]
> Envoy=E9=A0: mardi 11 avril 2017 19:19
> =C0=A0: Stephen Farrell
> Cc=A0: BOUCADAIR Mohamed IMT/OLN; Martin Thomson; ietf@ietf.org; draft-
> dolson-plus-middlebox-benefits@tools.ietf.org
> Objet=A0: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of dra=
ft-
> mm-wg-effect-encrypt-09)
>=20
> On Tue, Apr 11, 2017 at 09:51:14AM +0100, Stephen Farrell wrote:
> > On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
> > >> I hope that the IETF never publishes
> > >> draft-dolson-plus-middlebox-benefits; it makes claims about the
> > >> benefits of specific solutions for different use cases with the
> > >> goal of justifying those solutions.
> >
> > > [Med] I'm afraid this is speculating about the intent of
> > > draft-dolson. Assured this is not the purpose of that document. The
> > > motivation is to document current practices without including any
> > > recommendation or claiming these solutions are superior to others.
> >
> > Just to note that I completely agree with Martin's interpretation
> > of the thrust of this draft and I totally fail to see how your
> > argument above can be justified given that draft title, abstract
> > and even filename (and also the content;-). When the abstract
> > says "This document summarizes benefits" then I cannot interpret
> > that as other than being intended to justify the uses described.
> >
> > A fairly thorough re-write to aim to describe the pros and cons
> > would be a different and more useful document. Similarly a draft
>=20
> Documenting the good, the bad, and the ugly, would be much better than
> documenting only the good.  Documenting only one half of the story seems
> to me like a bad idea on its face.

[Med] The point is there are RFCs that describe the issues of middleboxes. =
The initial intent of draft-dolson was to describe the expected functionali=
ty (called benefit in the draft) for enabling some of these functions. Supe=
rior solutions may exist but these solutions need to understand first what =
is the expected service; hence the need for a reference (this document) to =
understand the trade-offs.
=20
The draft can be updated with a section that identifies issues but I'm afra=
id that text won't be original compared to what was already documented in, =
e.g., RFC3234 or in specific documents such as RFC6269.

>=20
> > that strives to neutrally describe existing reality could maybe
> > be useful (*) but one that only describes middlebox friends with
> > "benefits" is not IMO beneficial ;-)
>=20
> Agreed.
>=20
> I can think of a number of problems with middle boxes:
>=20
>  - scalability
>=20
>    Middle boxes may need to expend much more computational power in
>    order to do more than forward packets, and they need to do this for
>    as many extant packet flows as will fit on their pipes at full tilt.
>=20
>    Middle boxes may also have to be stateful, which quickly turns into a
>    morass.
>=20
>  - security
>=20
>    Middle boxes can get intrusive and require sharing either more
>    information with the public at large, or more information with
>    "trusted" middle boxes, which in turn requires more complex key
>    management and more failure modes.
>=20
>  - reliability
>=20
>    More failure modes (see security above).  More middle boxes to
>    inspect for diagnostics.  More middleboxes to fix.
>=20
>  - extensibility
>=20
>    Want to extend the protocol?  You can't.  You'd have to upgrade all
>    the middle boxes first.  You can only get the extensibility that you
>    can foresee.  If you screw up the first time, the screw up will take
>    15 years to work out of the Internet in the best case, and in the
>    worst case you'll never get it out.
>=20

[Med] This is a fair list (even if some of the items are implementation-spe=
cific and/or are valid for some middleboxes not every middlebox). I can add=
 another important item for an operator:  their cost.=20

The important question then is: Why given the operational hurdles (reliabil=
ity, diagnostic, ..) and costs to deploy and operate them, these functions =
are (still) enabled in operational networks?=20

> I can probably add more later when I have more time for this thread.
>=20
> One could give a lot of advice for design of protocols with "friendly"
> middle boxes.  Merely saying "hey, they are good" is not enough.  We
> might want to revisit end-to-end protocol design as well (e.g., maybe
> ICMP isn't working so well; what can we do?).  Perhaps we can get some
> of the benefits of middle-box-aware protocols without the middle boxes.
> Suppose a secure middle-box quench protocol by which nodes under DDoS
> can enable DDoS counter-measures in upstream routers...  Suppose a
> generic, non-TCP congestion control capable but UDP-like transport with
> a reusable header prefix and ICMP-ish messages for QoS and congestion
> control...  I'm certain we can do more within the end-to-end model with
> minimal middle-box involvement (though never zero; we need at least
> packet forwarding middle boxes).
>=20
> IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as it
> is today.

[Med] This is not a frozen document. It can be updated to include comments.=
 Your inputs are more than welcome.=20

>=20
> Nico
> --


From nobody Wed Apr 12 00:09:25 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B43124BFA for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 00:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 T4LbhI0eYY7E for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 00:09:22 -0700 (PDT)
Received: from relais-inet.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 61554126B72 for <ietf@ietf.org>; Wed, 12 Apr 2017 00:09:22 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 7EE17C0621; Wed, 12 Apr 2017 09:09:20 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.61]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 527B44005B; Wed, 12 Apr 2017 09:09:20 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 09:09:20 +0200
From: <mohamed.boucadair@orange.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSsuepcxG3Gt+qPke8vqYsnz4RHKHAS5+AgAD/ByA=
Date: Wed, 12 Apr 2017 07:09:19 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4C16E@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost> <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com>
In-Reply-To: <54be4f24-352e-5248-a9fb-f040d4f07fb9@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.5]
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/ietf/rYJZ4vszsnd-tkjXAmFjZZYn8ug>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 07:09:24 -0000

Hi Melinda,=20

Please see inline.=20

Cheers,
Led

> -----Message d'origine-----
> De=A0: ietf [mailto:ietf-bounces@ietf.org] De la part de Melinda Shore
> Envoy=E9=A0: mardi 11 avril 2017 19:32
> =C0=A0: ietf@ietf.org
> Objet=A0: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of dra=
ft-
> mm-wg-effect-encrypt-09)
>=20
> On 4/11/17 9:18 AM, Nico Williams wrote:
> > One could give a lot of advice for design of protocols with
> > "friendly" middle boxes.  Merely saying "hey, they are good" is not
> > enough.  We might want to revisit end-to-end protocol design as well
> > (e.g., maybe ICMP isn't working so well; what can we do?).
>=20
> There have been a number of efforts to provide mechanisms for
> applications to communicate explicitly with middleboxes.  None
> has gotten any traction,

[Med] I'm not sure "None" and "any" reflect the deployment realty I'm aware=
 of:
* The BEHAVE recommendations for TCP(RFC5382)/UDP(RFC4787)/ICMP(RFC5508) an=
d CGNs (RFC6888) are widely followed by CGN vendors.=20
* The NAT64 (RFC6146)/DS-Lite CGN (RFC6333) specifications that is aligned =
with IETF BEHAVE recommendations are deployed in many networks with default=
 behaviors that are friendly to applications.
* Our customers are making use of PCP (RFC6887) to interact with CGNs.
* Applications that make use of UPnP-IGD interact with an CGN server by mea=
ns of a IGD/PC IWG (RFC 6970)
* Applications embedded on the CPE can interact with a local PCP client.

Sometimes the problem is not on the network side but elsewhere.      =20

 and for the moment it looks like
> anything that requires changes to middleboxes along those
> lines is unlikely to be successful.  That said:
>=20
> > IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as
> > it is today.
>=20
> No, clearly not.  I'm actually not sure I see a lot of benefit
> to publishing a more balanced document, either, in the sense that
> it's not likely to lead anybody to do anything differently.

[Med] I disagree with this position. Many times the IETF decided to not hid=
e a problem but to deal with it, interesting solutions are proposed with co=
ncrete deployments. Of course, resistance to some proposals may have conseq=
uences on some operators plans that are obliged to deploy **mature solution=
s they had at hand**.=20

>=20
> Melinda


From nobody Wed Apr 12 00:49:56 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9318128896 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 00:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 2s3fAxJrzpib for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 00:49:53 -0700 (PDT)
Received: from relais-inet.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 E82A3128854 for <ietf@ietf.org>; Wed, 12 Apr 2017 00:49:52 -0700 (PDT)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 2BF4C402EA; Wed, 12 Apr 2017 09:49:51 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id EEE2D20074; Wed, 12 Apr 2017 09:49:50 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%18]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 09:49:50 +0200
From: <mohamed.boucadair@orange.com>
To: Nico Williams <nico@cryptonector.com>, Melinda Shore <melinda.shore@gmail.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSsuepcxG3Gt+qPke8vqYsnz4RHKHAS5+AgAAFNgCAAQDqoA==
Date: Wed, 12 Apr 2017 07:49:50 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4C1A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost> <54be4f24-352e-5248-a9fb-f040d4f07fb9@gmail.com> <20170411175019.GB23461@localhost>
In-Reply-To: <20170411175019.GB23461@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
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/ietf/zUbYuMDbMxI0wrbT3M6G7HAR08Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 07:49:55 -0000

Re-,

Please see inline.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: ietf [mailto:ietf-bounces@ietf.org] De la part de Nico Williams
> Envoy=E9=A0: mardi 11 avril 2017 19:50
> =C0=A0: Melinda Shore
> Cc=A0: ietf@ietf.org
> Objet=A0: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of dra=
ft-
> mm-wg-effect-encrypt-09)
>=20
> On Tue, Apr 11, 2017 at 09:31:41AM -0800, Melinda Shore wrote:
> > On 4/11/17 9:18 AM, Nico Williams wrote:
> > > One could give a lot of advice for design of protocols with
> > > "friendly" middle boxes.  Merely saying "hey, they are good" is not
> > > enough.  We might want to revisit end-to-end protocol design as well
> > > (e.g., maybe ICMP isn't working so well; what can we do?).
> >
> > There have been a number of efforts to provide mechanisms for
> > applications to communicate explicitly with middleboxes.  None
> > has gotten any traction, and for the moment it looks like
> > anything that requires changes to middleboxes along those
> > lines is unlikely to be successful.  That said:
>=20
> Sure, but if we wanted to have an Informational RFC describing all the
> goodness and badness and history of middle-box-aware protocools, that
> might not be bad, and we could detail all those protocols that failed to
> get traction and why.  I think such a document would end up favoring
> end-to-end protocols, even if it didn't start out with that as a goal :)
>=20

[Med] This may be applicable for some cases under some conditions ... but I=
'm afraid this may not be applicable to all of them. This is why it is impo=
rtant to understand the intended usage (draft-dolson) before going further =
in the discussion (e.g., whether it makes sense to call for a generic recom=
mendation, standardize a given network-located function a la BEHAVE, etc.).=
  =20

For example, an operator will need to detect and mitigate DDoS attacks with=
out interfering with legitimate traffic issued/send to customers. "Somethin=
g" is to be done at the network side to that aim. We are investigating how =
endpoints can help to achieve that goal.=20




From nobody Wed Apr 12 01:14:06 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E98C1292D0 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 NpJ0s80CTz1S for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:14:01 -0700 (PDT)
Received: from relais-inet.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 384FC129A8F for <ietf@ietf.org>; Wed, 12 Apr 2017 01:14:01 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id A9D9A20713; Wed, 12 Apr 2017 10:13:59 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 3A8DB1C006D; Wed, 12 Apr 2017 10:13:59 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 10:13:58 +0200
From: <mohamed.boucadair@orange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Dave Dolson <ddolson@sandvine.com>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSsvIycxG3Gt+qPke8vqYsnz4RHKHBYFrg
Date: Wed, 12 Apr 2017 08:13:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie>
In-Reply-To: <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kvm5i2CTv-1S3JGjQId-fqBPjSI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 08:14:05 -0000

SGkgU3RlcGhlbiwNCg0KUGxlYXNlIHNlZSBpbmxpbmUuIA0KDQpDaGVlcnMsDQpNZWQNCg0KPiAt
LS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDogU3RlcGhlbiBGYXJyZWxsIFttYWls
dG86c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZV0NCj4gRW52b3nDqcKgOiBtYXJkaSAxMSBhdnJp
bCAyMDE3IDIwOjM0DQo+IMOAwqA6IERhdmUgRG9sc29uOyBCT1VDQURBSVIgTW9oYW1lZCBJTVQv
T0xOOyBNYXJ0aW4gVGhvbXNvbjsgaWV0ZkBpZXRmLm9yZw0KPiBDY8KgOiBkcmFmdC1kb2xzb24t
cGx1cy1taWRkbGVib3gtYmVuZWZpdHNAdG9vbHMuaWV0Zi5vcmcNCj4gT2JqZXTCoDogUmU6IGRy
YWZ0LWRvbHNvbi1wbHVzLW1pZGRsZWJveC1iZW5lZml0cyAod2FzIFJFOiBSZXZpZXcgb2YgZHJh
ZnQtDQo+IG1tLXdnLWVmZmVjdC1lbmNyeXB0LTA5KQ0KPiANCj4gDQo+IA0KPiBPbiAxMS8wNC8x
NyAxMzowMywgRGF2ZSBEb2xzb24gd3JvdGU6DQo+ID4gUmVnYXJkaW5nICJiZW5lZml0cyIsIHRo
ZXNlIGRldmljZXMgY2xlYXJseSBoYXZlIHBlcmNlaXZlZCBiZW5lZml0cw0KPiANCj4gSSBkbyBu
b3QgYWdyZWUgdGhhdCB0aGUgSUVURiBvdWdodCBkZXNjcmliZWQgcGVyY2VpdmVkIGJlbmVmaXRz
DQo+IGFzIGlmIHRoZSBjbGFpbWVkIGJlbmVmaXRzIGFjY3J1ZSBhcyBob3BlZCBmb3IuDQoNCltN
ZWRdIEknbSBhZnJhaWQgaXQgaXMgaG9wZWQgZm9yIHNvbWUgZnVuY3Rpb25zLiBGb3IgZXhhbXBs
ZSwgdGhlIElFVEYgc3BlY2lmaWVkIGluIHRoZSBwYXN0IG1hbnkgZnVuY3Rpb25zIHRvIHByb3Zp
ZGUgc3BlY2lmaWMgc2VydmljZXMgKGNhbGxlZCBiZW5lZml0IGluIGRyYWZ0LWRvbHNvbikgc3Vj
aCBhcyBOQVQ2NCAoSVB2NCBzZXJ2aWNlIGNvbnRpbnVpdHkpLg0KDQpJZiB5b3UgZG9uJ3QgcGVy
Y2VpdmUgdGhhdCBmdW5jdGlvbiBhcyBhICJiZW5lZml0IiwgY2FuIHlvdSBwbGVhc2UgYW5zd2Vy
IHRoZSBmb2xsb3dpbmc6IA0KDQoqIEJlY2F1c2UgeW91ciBvcGVyYXRvciBpcyBydW5uaW5nIG91
dCBvZiBJUHY0IGFkZHJlc3NlcywgaXQgZGVjaWRlcyB0byBnaXZlIHlvdSBhbiBJUHY2IHByZWZp
eCB3aXRob3V0IGVuYWJsaW5nIGFueSBmdW5jdGlvbiBpbiB0aGUgbmV0d29yay4gV29uJ3QgeW91
IGNhbGwgdGhlIGhvdGxpbmUgb2YgdGhhdCBvcGVyYXRvciB0byBjbGFpbSB0aGF0IHlvdSBkb24n
dCBhY2Nlc3MgdG8gbW9zdCBvZiBJbnRlcm5ldCByZXNvdXJjZXMgYW5kIHRoYXQgc29tZXRoaW5n
IGlzIHRvIGJlIGZpeGVkIG90aGVyd2lzZSB5b3Ugd2lsbCB1bnN1YnNjcmliZT8NCg0KKiBXaGVu
IHlvdSBhcmUgYXR0ZW5kaW5nIGFuIElFVEYgbWVldGluZywgSSBhc3N1bWUgeW91IGFyZSB1c2lu
ZyBJUHY2LW9ubHkgU1NJRC4gRG8geW91IHZvbHVudGVlciB0byBvcHQtb3V0IGZyb20gTkFUNjQg
aW4gdGhlIGNvbWluZyBtZWV0aW5nPw0KDQoNCiBUaGF0IGlzIGZhciB0b28NCj4gY2xvc2UgdG8g
bWFya2V0aW5nLiBJbiBhIGNvbnRlbnRpb3VzIGNhc2UgbGlrZSB0aGlzLCBJIGNhbiBzZWUNCj4g
d2h5IHNvbWVvbmUgbWF5IGZlZWwgdGhhdCdzIHVzZWZ1bCBhcyBhIGZvcm0gb2YgYmFsYW5jZSBv
ciBwYXJ0DQo+IG9mIGEgbGFyZ2VyIGRlYmF0ZSwgYnV0IGluIHRoZSBlbmQgSSB0aGluayB3ZSBu
ZWVkIHRvIHN0ZXAgYmFjaw0KPiBhbmQgdGFrZSBhbiBlbmdpbmVlcmluZyBhcHByb2FjaC4NCg0K
W01lZF0gRnVsbHkgYWdyZWUuIFRoaXMgaXMgd2h5IHdlIG5lZWQgdG8gdW5kZXJzdGFuZCB0aGUg
aW50ZW5kZWQgdXNhZ2UgdG8gaGF2ZSBhIHJlZmVyZW5jZSBmb3IgYW55IGVuZ2luZWVyaW5nIGFw
cHJvYWNoLiANCg0KPiANCj4gUw0KPiANCj4gPiB0byB0aG9zZSB3aG8gZGVwbG95IHRoZW0uIE15
IHZpZXcgaXMgdGhhdCB0aGUgZG9jdW1lbnQgc2hvdWxkIGV4cGxhaW4NCj4gPiB0aGF0IHBlcnNw
ZWN0aXZlIGZvciByZWFkZXJzIHdobyBsYWNrIHRoZSBvcGVyYXRvciBwZXJzcGVjdGl2ZS4gVGhl
DQo+ID4gaW50ZW50IHdhcyBub3QgdG8gbWFuZGF0ZSBvciByZWNvbW1lbmQgZGVwbG95bWVudHMu
DQo+ID4NCj4gPiBEYXZpZCBEb2xzb24gw6LigqzFvSBPcmlnaW5hbCBNZXNzYWdlIEZyb206IG1v
aGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20NCj4gPiBTZW50OiBUdWVzZGF5LCBBcHJpbCAxMSwg
MjAxNyA3OjQ4IEFNIFRvOiBTdGVwaGVuIEZhcnJlbGw7IE1hcnRpbg0KPiA+IFRob21zb247IGll
dGZAaWV0Zi5vcmcgQ2M6DQo+ID4gZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRz
QHRvb2xzLmlldGYub3JnIFN1YmplY3Q6IFJFOg0KPiA+IGRyYWZ0LWRvbHNvbi1wbHVzLW1pZGRs
ZWJveC1iZW5lZml0cyAod2FzIFJFOiBSZXZpZXcgb2YNCj4gPiBkcmFmdC1tbS13Zy1lZmZlY3Qt
ZW5jcnlwdC0wOSkNCj4gPg0KPiA+DQo+ID4gSGkgU3RlcGhlbiwNCj4gPg0KPiA+IFBsZWFzZSBz
ZWUgaW5saW5lLg0KPiA+DQo+ID4gQ2hlZXJzLCBNZWQNCj4gPg0KPiA+PiAtLS0tLU1lc3NhZ2Ug
ZCdvcmlnaW5lLS0tLS0gRGUgOiBTdGVwaGVuIEZhcnJlbGwNCj4gPj4gW21haWx0bzpzdGVwaGVu
LmZhcnJlbGxAY3MudGNkLmllXSBFbnZvecODwqkgOiBtYXJkaSAxMSBhdnJpbCAyMDE3DQo+ID4+
IDEwOjUxIMOD4oKsIDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjsgTWFydGluIFRob21zb247
DQo+ID4+IGlldGZAaWV0Zi5vcmcgQ2MgOg0KPiA+PiBkcmFmdC1kb2xzb24tcGx1cy1taWRkbGVi
b3gtYmVuZWZpdHNAdG9vbHMuaWV0Zi5vcmcgT2JqZXQgOiBSZToNCj4gPj4gZHJhZnQtZG9sc29u
LXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmlldyBvZiBkcmFmdC0NCj4gPj4g
bW0td2ctZWZmZWN0LWVuY3J5cHQtMDkpDQo+ID4+DQo+ID4+DQo+ID4+IEhpIE1lZCwNCj4gPj4N
Cj4gPj4gT24gMTEvMDQvMTcgMDk6MTUsIG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20gd3Jv
dGU6DQo+ID4+Pj4gSSBob3BlIHRoYXQgdGhlIElFVEYgbmV2ZXIgcHVibGlzaGVzDQo+ID4+Pj4g
ZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzOyBpdCBtYWtlcyBjbGFpbXMgYWJv
dXQNCj4gPj4+PiB0aGUgYmVuZWZpdHMgb2Ygc3BlY2lmaWMgc29sdXRpb25zIGZvciBkaWZmZXJl
bnQgdXNlIGNhc2VzIHdpdGgNCj4gPj4+PiB0aGUgZ29hbCBvZiBqdXN0aWZ5aW5nIHRob3NlIHNv
bHV0aW9ucy4NCj4gPj4NCj4gPj4+IFtNZWRdIEknbSBhZnJhaWQgdGhpcyBpcyBzcGVjdWxhdGlu
ZyBhYm91dCB0aGUgaW50ZW50IG9mDQo+ID4+PiBkcmFmdC1kb2xzb24uIEFzc3VyZWQgdGhpcyBp
cyBub3QgdGhlIHB1cnBvc2Ugb2YgdGhhdCBkb2N1bWVudC4NCj4gPj4+IFRoZSBtb3RpdmF0aW9u
IGlzIHRvIGRvY3VtZW50IGN1cnJlbnQgcHJhY3RpY2VzIHdpdGhvdXQgaW5jbHVkaW5nDQo+ID4+
PiBhbnkgcmVjb21tZW5kYXRpb24gb3IgY2xhaW1pbmcgdGhlc2Ugc29sdXRpb25zIGFyZSBzdXBl
cmlvciB0bw0KPiA+Pj4gb3RoZXJzLg0KPiA+Pg0KPiA+PiBKdXN0IHRvIG5vdGUgdGhhdCBJIGNv
bXBsZXRlbHkgYWdyZWUgd2l0aCBNYXJ0aW4ncyBpbnRlcnByZXRhdGlvbg0KPiA+PiBvZiB0aGUg
dGhydXN0IG9mIHRoaXMgZHJhZnQgYW5kIEkgdG90YWxseSBmYWlsIHRvIHNlZSBob3cgeW91cg0K
PiA+PiBhcmd1bWVudCBhYm92ZSBjYW4gYmUganVzdGlmaWVkIGdpdmVuIHRoYXQgZHJhZnQgdGl0
bGUsIGFic3RyYWN0DQo+ID4+IGFuZCBldmVuIGZpbGVuYW1lIChhbmQgYWxzbyB0aGUgY29udGVu
dDstKS4NCj4gPg0KPiA+IFtNZWRdICJiZW5lZmljaWFsIiBpcyBkZXJpdmVkIGZyb20gdGhlIGlu
aXRpYWwgcmVxdWVzdCB0aGF0IG1vdGl2YXRlZA0KPiA+IHRoaXMgZHJhZnQgKGV4Y2VycHQgZnJv
bSB0aGUgYWJzdHJhY3QpOg0KPiA+DQo+ID4gQXQgSUVURjk3LCBhdCBhIG1lZXRpbmcgcmVnYXJk
aW5nIHRoZSBQYXRoIExheWVyIFVEUCBTdWJzdHJhdGUNCj4gPiAoUExVUykgcHJvdG9jb2wsIGEg
cmVxdWVzdCB3YXMgbWFkZSBmb3IgZG9jdW1lbnRhdGlvbiBhYm91dCB0aGUNCj4gPiBiZW5lZml0
cyBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xg0KPiA+IHRoYXQgbWlnaHQgYmUgcHJvdmlkZWQgYnkgcGVybWl0dGluZyBtaWRkbGVib3hlcyB0
byBoYXZlIHNvbWUNCj4gPiBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXl5eXg0KPiA+IHZpc2liaWxpdHkgdG8gdHJhbnNwb3J0LWxheWVy
IGluZm9ybWF0aW9uLg0KPiA+IF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXg0KPiA+DQo+ID4gV2hlbiB0aGUgYWJzdHJhY3QNCj4gPj4gc2F5cyAiVGhpcyBkb2N1bWVu
dCBzdW1tYXJpemVzIGJlbmVmaXRzIiB0aGVuIEkgY2Fubm90IGludGVycHJldA0KPiA+PiB0aGF0
IGFzIG90aGVyIHRoYW4gYmVpbmcgaW50ZW5kZWQgdG8ganVzdGlmeSB0aGUgdXNlcyBkZXNjcmli
ZWQuDQo+ID4NCj4gPiBbTWVkXSBJIHdvdWxkIHByZWZlciBpZiB3ZSBjYW4gYXZvaWQgdG8gImlu
dGVycHJldCIsIGJ1dCByYWlzZQ0KPiA+IHF1ZXN0aW9ucyB0byB0aGUgYXV0aG9ycyBpZiB0aGVy
ZSBpcyBhIGRvdWJ0LiBUaGUgZG9jdW1lbnQgZG9lcyBub3QNCj4gPiBwcm92aWRlIGEgcmVjb21t
ZW5kYXRpb24gb3IgY2xhaW1zIHRoaXMgaXMgdGhlIG9ubHkgd2F5IHRvIGFjaGlldmUNCj4gPiB0
aGUgdGVjaG5pY2FsIGdvYWxzLiBJdCBkb2VzIG9ubHkgcmVmbGVjdCBzb21lIGRlcGxveW1lbnQg
cmVhbGl0eQ0KPiA+IHRvZ2V0aGVyIHdpdGggc29tZSBtb3RpdmF0aW9ucy4NCj4gPg0KPiA+Pg0K
PiA+PiBBIGZhaXJseSB0aG9yb3VnaCByZS13cml0ZSB0byBhaW0gdG8gZGVzY3JpYmUgdGhlIHBy
b3MgYW5kIGNvbnMNCj4gPj4gd291bGQgYmUgYSBkaWZmZXJlbnQgYW5kIG1vcmUgdXNlZnVsIGRv
Y3VtZW50Lg0KPiA+DQo+ID4gW01lZF0gVGhlcmUgYXJlIGFscmVhZHkgbWFueSBSRkNzIHRoYXQg
ZGlzY3VzcyB0aGUgaXNzdWVzL2NvbnMgKEkgY2FuDQo+ID4gY2l0ZSB0aGlzIFJGQyBJIGNvLWF1
dGhvcmVkIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MjY5IGZvcg0KPiA+IHRoZSBD
R04gY2FzZSkuIFdoYXQgaXMgbmVlZGVkIElNSE8gaXMgc29tZXRoaW5nIGVsc2U6IHVuZGVyc3Rh
bmQgdGhlDQo+ID4gcmVxdWlyZW1lbnRzIHRoYXQgbGVkIHRvIGRlcGxveSBzb21lIG9mIHRoZXNl
IGZ1bmN0aW9ucy4NCj4gPg0KPiA+IFNpbWlsYXJseSBhIGRyYWZ0DQo+ID4+IHRoYXQgc3RyaXZl
cyB0byBuZXV0cmFsbHkgZGVzY3JpYmUgZXhpc3RpbmcgcmVhbGl0eSBjb3VsZCBtYXliZSBiZQ0K
PiA+PiB1c2VmdWwgKCopDQo+ID4NCj4gPiBbTWVkXSBUaGlzIGlzIHRoZSBpbnRlbnQgb2YgZHJh
ZnQtZG9sc29uLg0KPiA+DQo+ID4gYnV0IG9uZSB0aGF0IG9ubHkgZGVzY3JpYmVzIG1pZGRsZWJv
eCBmcmllbmRzIHdpdGgNCj4gPj4gImJlbmVmaXRzIiBpcyBub3QgSU1PIGJlbmVmaWNpYWwgOy0p
DQo+ID4NCj4gPiBbTWVkXSBUaGUgaW50ZW50IGlzIG5vdCB0byAic2VsbCBzb21ldGhpbmciIGJ1
dCB0byB1bmRlcnN0YW5kIHRoZQ0KPiA+IHRlY2huaWNhbCBuZWVkcyBzbyB0aGF0IGhvcGVmdWxs
eSB3ZSBjYW4gaGF2ZSBhIHJlZmVyZW5jZSBmb3IgZnV0dXJlDQo+ID4gc29sdXRpb24tb3JpZW50
ZWQgZGlzY3Vzc2lvbnMuIElmIGEgZ2l2ZW4gZnVuY3Rpb24gY2FuIGJlIHByb3ZpZGVkDQo+ID4g
d2l0aG91dCBpbnZvbHZpbmcgYW4gb24tcGF0aCBkZXZpY2UsIHRoaXMgd291bGQgYmUgZ3JlYXQg
Zm9yDQo+ID4gb3BlcmF0b3JzIChvcHRpbWl6ZSBDQVBFWC9PUEVYIGlzIG91ciBtb3R0bykuDQo+
ID4NCj4gPj4NCj4gPj4gQ2hlZXJzLCBTLg0KPiA+Pg0KPiA+PiAoKikgVGhhdCBpcyB0aGUgYXJn
dW1lbnQgZm9yIGRyYWZ0LW1tLWVmZmVjdC1lbmNyeXB0LCBmb3Igd2hpY2ggSQ0KPiA+PiBkbyBz
dXBwb3J0IHB1YmxpY2F0aW9uIChhcHBhcmVudGx5IGluIGRpc2FncmVlbWVudCB3aXRoIE1hcnRp
biBpbg0KPiA+PiB0aGF0IGNhc2U6LSkNCj4gPj4NCj4gPj4NCj4gPj4NCj4gPg0KDQo=


From nobody Wed Apr 12 01:35:38 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D3712EAE1 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 cmSo3l4k1SxL for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:35:34 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABCE512EAB7 for <ietf@ietf.org>; Wed, 12 Apr 2017 01:35:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2BBC4BE5D; Wed, 12 Apr 2017 09:35:30 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qx3NwRvtzroT; Wed, 12 Apr 2017 09:35:28 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CBCA7BE53; Wed, 12 Apr 2017 09:35:27 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491986128; bh=dVyix83R7nDf7cZ7Lr+JRuQB0mFt7peotomSftwJeZg=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=xj3937jmiNIA/xJZa8UpqEFdYPspIqVYw6JNUzMCPxsdrbOJJtWmzSegoPxZQ8hdp hWrWcfD1oymBPNIKnEwjiDPGBsYvgz50xBwDxnAuY1k2ozfMc3z7XaZ/LPl+dqqObj MOzTId+bdmdY/VS0QpOVLgFvbPRal8NWHmqCRi1E=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: mohamed.boucadair@orange.com, Dave Dolson <ddolson@sandvine.com>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <6edcf3dd-373b-ee11-ccc3-c4f10f90d0f9@cs.tcd.ie>
Date: Wed, 12 Apr 2017 09:35:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="F9AkoN4aUrlDs1BjhR3KAxckUOO62gntf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tAgwER9OO9pVeIIT7aOM-RyKWLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 08:35:37 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--F9AkoN4aUrlDs1BjhR3KAxckUOO62gntf
Content-Type: multipart/mixed; boundary="GuPDJ7HVnEo66hGue3Df2emSElNc6s3Gl";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: mohamed.boucadair@orange.com, Dave Dolson <ddolson@sandvine.com>,
 Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-dolson-plus-middlebox-benefits@tools.ietf.org"
 <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Message-ID: <6edcf3dd-373b-ee11-ccc3-c4f10f90d0f9@cs.tcd.ie>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <20170411120303.5128273.2297.7062@sandvine.com>
 <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie>
 <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>

--GuPDJ7HVnEo66hGue3Df2emSElNc6s3Gl
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 12/04/17 09:13, mohamed.boucadair@orange.com wrote:
> Hi Stephen,
>=20
> Please see inline.
>=20
> Cheers, Med
>=20
>> -----Message d'origine----- De=C3=82 : Stephen Farrell
>> [mailto:stephen.farrell@cs.tcd.ie] Envoy=C3=83=C2=A9=C3=82 : mardi 11 =
avril 2017
>> 20:34 =C3=83=E2=82=AC=C3=82 : Dave Dolson; BOUCADAIR Mohamed IMT/OLN; =
Martin Thomson;
>> ietf@ietf.org Cc=C3=82 :
>> draft-dolson-plus-middlebox-benefits@tools.ietf.org Objet=C3=82 : Re:
>> draft-dolson-plus-middlebox-benefits (was RE: Review of draft-=20
>> mm-wg-effect-encrypt-09)
>>=20
>>=20
>>=20
>> On 11/04/17 13:03, Dave Dolson wrote:
>>> Regarding "benefits", these devices clearly have perceived
>>> benefits
>>=20
>> I do not agree that the IETF ought described perceived benefits as
>> if the claimed benefits accrue as hoped for.
>=20
> [Med] I'm afraid it is hoped for some functions. For example, the
> IETF specified in the past many functions to provide specific
> services (called benefit in draft-dolson) such as NAT64 (IPv4 service
> continuity).

I'm not sure that s/benefits/services/g in the document text
would work, so I don't accept that argument. If you meant
something else, I'm not sure what.

>=20
> If you don't perceive that function as a "benefit", can you please
> answer the following:
>=20
> * Because your operator is running out of IPv4 addresses, it decides
> to give you an IPv6 prefix without enabling any function in the
> network. Won't you call the hotline of that operator to claim that
> you don't access to most of Internet resources and that something is
> to be fixed otherwise you will unsubscribe?
>=20
> * When you are attending an IETF meeting, I assume you are using
> IPv6-only SSID. Do you volunteer to opt-out from NAT64 in the coming
> meeting?

I did not argue that no middlebox ever provided any benefit
to anyone so I don't know how answering the above questions
would help.

But in case it does help: yes, firewalls have provided some
benefits over the years. I suspect those are now diminishing
but could be wrong. I don't know if it's gotten to the point
that firewalls are more of a benefit or a scourge today. (Having
just had the fun of installing a stun/turn server to get two
browsers to chat with one another, I can freshly attest to the
"pointless scourge" aspect as I didn't have to ask the f/w
admins anything to get around the useless barrier they were
in this particular case;-)

It might be possible to do studies and produce data that'd help
the community decide that question (f/w utility vs. scourge) and
that could be a useful activity, if done objectively. That last
(objectivity) seems hard though, as it seems there are many folks
who find being objective in this space difficult (on all sides).
I've no idea if similar studies and data could help with
(re-)evaluating other aspects of middlebox deployment claimed
utility.

And again, I see no utility at all in a statements along the
lines that "firewalls are beneficial because they can do X."

S.

>=20
>=20
> That is far too
>> close to marketing. In a contentious case like this, I can see why
>> someone may feel that's useful as a form of balance or part of a
>> larger debate, but in the end I think we need to step back and take
>> an engineering approach.
>=20
> [Med] Fully agree. This is why we need to understand the intended
> usage to have a reference for any engineering approach.
>=20
>>=20
>> S
>>=20
>>> to those who deploy them. My view is that the document should
>>> explain that perspective for readers who lack the operator
>>> perspective. The intent was not to mandate or recommend
>>> deployments.
>>>=20
>>> David Dolson =C3=83=C2=A2=C3=A2=E2=80=9A=C2=AC=C3=85=C2=BD Original M=
essage From:
>>> mohamed.boucadair@orange.com Sent: Tuesday, April 11, 2017 7:48
>>> AM To: Stephen Farrell; Martin Thomson; ietf@ietf.org Cc:=20
>>> draft-dolson-plus-middlebox-benefits@tools.ietf.org Subject: RE:=20
>>> draft-dolson-plus-middlebox-benefits (was RE: Review of=20
>>> draft-mm-wg-effect-encrypt-09)
>>>=20
>>>=20
>>> Hi Stephen,
>>>=20
>>> Please see inline.
>>>=20
>>> Cheers, Med
>>>=20
>>>> -----Message d'origine----- De : Stephen Farrell=20
>>>> [mailto:stephen.farrell@cs.tcd.ie] Envoy=C3=83=C6=92=C3=82=C2=A9 : m=
ardi 11 avril
>>>> 2017 10:51 =C3=83=C6=92=C3=A2=E2=80=9A=C2=AC : BOUCADAIR Mohamed IMT=
/OLN; Martin Thomson;=20
>>>> ietf@ietf.org Cc :=20
>>>> draft-dolson-plus-middlebox-benefits@tools.ietf.org Objet :
>>>> Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
>>>> draft- mm-wg-effect-encrypt-09)
>>>>=20
>>>>=20
>>>> Hi Med,
>>>>=20
>>>> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>>>>>> I hope that the IETF never publishes=20
>>>>>> draft-dolson-plus-middlebox-benefits; it makes claims
>>>>>> about the benefits of specific solutions for different use
>>>>>> cases with the goal of justifying those solutions.
>>>>=20
>>>>> [Med] I'm afraid this is speculating about the intent of=20
>>>>> draft-dolson. Assured this is not the purpose of that
>>>>> document. The motivation is to document current practices
>>>>> without including any recommendation or claiming these
>>>>> solutions are superior to others.
>>>>=20
>>>> Just to note that I completely agree with Martin's
>>>> interpretation of the thrust of this draft and I totally fail
>>>> to see how your argument above can be justified given that
>>>> draft title, abstract and even filename (and also the
>>>> content;-).
>>>=20
>>> [Med] "beneficial" is derived from the initial request that
>>> motivated this draft (excerpt from the abstract):
>>>=20
>>> At IETF97, at a meeting regarding the Path Layer UDP Substrate=20
>>> (PLUS) protocol, a request was made for documentation about the=20
>>> benefits
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ that
>>> might be provided by permitting middleboxes to have some=20
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
>>> visibility to transport-layer information.=20
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>=20
>>> When the abstract
>>>> says "This document summarizes benefits" then I cannot
>>>> interpret that as other than being intended to justify the uses
>>>> described.
>>>=20
>>> [Med] I would prefer if we can avoid to "interpret", but raise=20
>>> questions to the authors if there is a doubt. The document does
>>> not provide a recommendation or claims this is the only way to
>>> achieve the technical goals. It does only reflect some deployment
>>> reality together with some motivations.
>>>=20
>>>>=20
>>>> A fairly thorough re-write to aim to describe the pros and
>>>> cons would be a different and more useful document.
>>>=20
>>> [Med] There are already many RFCs that discuss the issues/cons (I
>>> can cite this RFC I co-authored
>>> https://tools.ietf.org/html/rfc6269 for the CGN case). What is
>>> needed IMHO is something else: understand the requirements that
>>> led to deploy some of these functions.
>>>=20
>>> Similarly a draft
>>>> that strives to neutrally describe existing reality could maybe
>>>> be useful (*)
>>>=20
>>> [Med] This is the intent of draft-dolson.
>>>=20
>>> but one that only describes middlebox friends with
>>>> "benefits" is not IMO beneficial ;-)
>>>=20
>>> [Med] The intent is not to "sell something" but to understand
>>> the technical needs so that hopefully we can have a reference for
>>> future solution-oriented discussions. If a given function can be
>>> provided without involving an on-path device, this would be great
>>> for operators (optimize CAPEX/OPEX is our motto).
>>>=20
>>>>=20
>>>> Cheers, S.
>>>>=20
>>>> (*) That is the argument for draft-mm-effect-encrypt, for which
>>>> I do support publication (apparently in disagreement with
>>>> Martin in that case:-)
>>>>=20
>>>>=20
>>>>=20
>>>=20
>=20


--GuPDJ7HVnEo66hGue3Df2emSElNc6s3Gl--

--F9AkoN4aUrlDs1BjhR3KAxckUOO62gntf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7ebPAAoJEC88hzaAX42iiL8H/jW5ZELK+b+xx4N6dXcdVWAq
nSUmukLxW3D6N/7LVnOqNmOCmzewk28LWttbY9ZKdzMvUCZrsfhjQx9g1E9h1Enh
ePsGFfmCPfy2Nlanzp3B5UI8cJGtcigdKEwIj8WQLEAqkWPiwbsSMO9qVlBDzRCO
gnKcnhDVT1zURB/qdBwWVPM4I9c4+pqumvAkArMQ850CluTbX6UlWnqiwBDqPFJq
ox7L/5mIjDKbIX9coi1dJWe4vXVmU5Ze0kRgUfXl6in8DOjNAnQ5Tgxk8gU6wNxA
GlqC/9MVWGb2PF25j+oceK2AQ9MHue7DIhMgll1/o07YwR8dG9h5Mo5sMeFV900=
=mYdE
-----END PGP SIGNATURE-----

--F9AkoN4aUrlDs1BjhR3KAxckUOO62gntf--


From nobody Wed Apr 12 01:53:44 2017
Return-Path: <prvs=127550c264=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0991292CE for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:53:37 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9x7G6OQN9pIS for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 01:53:36 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6C2D13145F for <ietf@ietf.org>; Wed, 12 Apr 2017 01:53:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491987212; x=1492592012; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=aI9yMq0lCbA0LIJgYHXxwGXoB ZH7r1ZdrI32ZuIPGSo=; b=JuubM3DUV2Nf+Ai4AiFwbe4Wm6q6zKIqTS3+y1bGO uPIjh9LKXX0JMHTuLWdyInqKlvAcKzzGIE7L6hWmyc1ZIyQIsWufMzRAsf8YAGMo 7FXTaNUsxkOdRhN38A/Qefqz2NZwy5bw8H1JLYipEDQ4HBRUcDw257/ZU4qZE2bk Xc=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=g3i8QbS0+UABccoXiSbRwr0G39lrbyonc8+EqLWICKEwlMQVLPyiTg0caW2n b5fQpryBNNBC3qZ3elV1YFbb3otaPeYoRDti3flqhNyFY4JI9GZSEcmuL rnNDgh8ypdKfUBdOP09YpOXAtKZHWp3NM4Cw3t4N7PTAZfnZSlf14I=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Apr 2017 10:53:32 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Apr 2017 10:53:31 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005406859.msg for <ietf@ietf.org>; Wed, 12 Apr 2017 10:53:31 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170412:md50005406859::dpNIeQEllaraLFZa:00000SxB
X-Return-Path: prvs=127550c264=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Apr 2017 10:53:26 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>, <iaoc@ietf.org>
Message-ID: <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es>
In-Reply-To: <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eBW5NJ5grfCuH6cYitb5UH2800I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 08:53:38 -0000

Are we going to have an answer on this NOW or next year?

Do we need to ask again and again every day?

I don=E2=80=99t feel the IETF members are being respected by the IAOC which=
 the lack of response. Again, I may understand not disclosing the full deta=
ils, but a simple answer with some of the info is needed.

If the IAOC don=E2=80=99t want to provide answers, it may be better that th=
ey step down and we look for more transparent people, the community is plen=
ty of them.

Regards,
Jordi
=20

-----Mensaje original-----
De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Fecha: martes, 11 de abril de 2017, 13:11
Para: IETF Discussion <ietf@ietf.org>, <iaoc@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    Can we get an answer from the IAOC to the questions below?
   =20
    If we cancel San Francisco, how much that is going to cost to the IETF =
for each of two planned meetings?
   =20
    Can we cancel the actual hotel contract considering the new US situatio=
n? If not, has this been considered for new contracts to avoid this problem=
?
   =20
    Otherwise there is any reason that can justify the lack of transparency=
 in this?
   =20
    Regards,
    Jordi
    =20
   =20
    -----Mensaje original-----
    De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
    Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 10:26
    Para: <iaoc@ietf.org>
    Asunto: Re: IAOC requesting input on (potential) meeting cities
   =20
        One important question here, same as we had in the case of Singapor=
e.
       =20
        If we cancel San Francisco, how much that is going to cost to the I=
ETF for each of two planned meetings?
       =20
        Furthermore, can the IAOC respond to this:
       =20
        Can we cancel the actual hotel contract considering the new US situ=
ation? If not, has this been considered for new contracts to avoid this pro=
blem?
       =20
        I think the relevant information in the contract need to be disclos=
ed and have it now on the table, otherwise we will be wasting the time disc=
ussing possibilities that are actually impossible to assume for the IETF =
=E2=80=A6
       =20
        My general position is:
        1) I will prefer not cancelling already planned meetings.
        2) I will prefer not =E2=80=9Cblocking=E2=80=9D any regions or coun=
tries from future meetings, including US.
        3) However, for already contracted meetings, if this is going to co=
st IETF thousands of dollars, we can=E2=80=99t afford that.
        4) We must work with authorities to avoid people being banned for a=
ttending the meetings.
       =20
        Maybe I=E2=80=99ve missed responses to some of my answers already, =
in any case, can the IAOC provide urgently those with a complete summary of=
 the situation?
       =20
        Regards,
        Jordi
        =20
       =20
        -----Mensaje original-----
        De: Eliot Lear <lear@cisco.com>
        Responder a: <lear@cisco.com>
        Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 6:39
        Para: Nico Williams <nico@cryptonector.com>, Yoav Nir <ynir.ietf@gm=
ail.com>
        CC: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consuli=
ntel.es>, Jared Mauch <jared@puck.nether.net>
        Asunto: Re: IAOC requesting input on (potential) meeting cities
       =20
            Nico,
           =20
            On 4/5/17 12:10 AM, Nico Williams wrote:
            > I do suspect that the U.S. will be a more difficult location =
for more
            > attendees than other locations.  Certainly the news we all se=
e is not
            > encouraging as to hosting IETF meetings in the U.S.  This I d=
on't deny.
            > Though it's also possible that this is becoming a self-reinfo=
rcing meme
            > and that we're just not seeing incidents in other countries i=
n the news.
            > In any case, the U.S. certainly does not have a monopoly on t=
he border
            > harasment business.
           =20
            Certainly people have had trouble getting into other countries,=
 most
            notably Canada where an IAB member was refused entry.  But this=
 isn't
            just news.  It is a series of declarations by the U.S. governme=
nt of
            their intentions, and the IAOC has to plan ahead.  That's why J=
ared's
            request for data is simply not tenable *at this stage*.  If it =
turns out
            that things aren't so bad, the IAOC can react accordingly.  How=
ever, as
            I wrote in my original email, there is now good reason to belie=
ve that
            things will get worse, due to the European Parliament=E2=80=99s=
 decision to
            require visas from U.S. citizens.
           =20
            > Some people may wish to boycott the U.S. by refusing to host =
events
            > there.  There is some precedent for such a boycott.  For exam=
ple, some
            > time back an obscure agency of the Texas state government dec=
ided to
            > guard its surplus budget by policing public drunkenness at ho=
tel bars,
            > which led to a number of conferences pulling out of Texas, an=
d the
            > ensuing bad PR led the legislature to rein in said agency.
            >
            > However, at the scale of a state/province the politics of boy=
cotts is
            > generally not partisan, but at a national/global scale it ten=
ds to be
            > rankly partisan, and boycotts may not be productive and may b=
e divisive,
            > and should be approached with care.  Here "care" means: get s=
ome
            > evidence of negative impact on participation. =20
           =20
            We ALREADY have evidence, as some people couldn't make Chicago,=
 and said
            so on this very list (and, by the way, were shamefully attacked=
 and
            dismissed (no, it certainly wasn't you)).  What we don't have i=
s an
            understanding of the order of magnitude of the impact, and that=
 is going
            to be very hard to gather in so  fluid a situation with so long=
 a
            lookahead.  The point, by the way, as I see it, is not to punis=
h the
            U.S. but to hold a successful meeting (that is what the mtgvenu=
e draft
            states as well).
           =20
            > Reducing frequency of
            > U.S. meetings is not a boycott, and is something the IETF has=
 been doing
            > for a long time anyways.  Further reducing that frequency in =
the short
            > term would be perfectly fine, though it would also reduce opp=
ortunities
            > for gather the stats we really need to make a sound, non-part=
isan
            > decision to boycott if the stats warrant it.
            >
           =20
            Turn this around: suppose we do keep the meeting in San Francis=
co, for
            instance, and some number of people cannot get there for whatev=
er
            reason, or cannot otherwise function on an equal footing.  Woul=
d the
            IAOC then be attacked for having ignored the vast number of war=
nings
            that have been signaled?
           =20
            Eliot
           =20
           =20
       =20
       =20
       =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr 12 02:03:32 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37F1A1314A7 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 02:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 FH5OpgMcwTGo for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 02:03:27 -0700 (PDT)
Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044CE1314AE for <ietf@ietf.org>; Wed, 12 Apr 2017 02:03:25 -0700 (PDT)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 45ED3405AF; Wed, 12 Apr 2017 11:03:23 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.19]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 049FA2007D; Wed, 12 Apr 2017 11:03:23 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM44.corporate.adroot.infra.ftgroup ([fe80::b08d:5b75:e92c:a45f%18]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 11:03:22 +0200
From: <mohamed.boucadair@orange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Dave Dolson <ddolson@sandvine.com>, Martin Thomson <martin.thomson@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Subject: RE: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Topic: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
Thread-Index: AQHSs2e/szhZNP8LXEGBCxH5knLf3aHBaZRQ
Date: Wed, 12 Apr 2017 09:03:22 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E4C254@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170411120303.5128273.2297.7062@sandvine.com> <79c4d3c8-f6e6-760f-bea4-969e8d8b40a9@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4C1CE@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <6edcf3dd-373b-ee11-ccc3-c4f10f90d0f9@cs.tcd.ie>
In-Reply-To: <6edcf3dd-373b-ee11-ccc3-c4f10f90d0f9@cs.tcd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFaX2UnEwPafQw2tLpFHz2P3fr8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 09:03:30 -0000

UmUtLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4gDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0tTWVz
c2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiBEZcKgOiBTdGVwaGVuIEZhcnJlbGwgW21haWx0bzpzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllXQ0KPiBFbnZvecOpwqA6IG1lcmNyZWRpIDEyIGF2cmlsIDIw
MTcgMTA6MzUNCj4gw4DCoDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjsgRGF2ZSBEb2xzb247
IE1hcnRpbiBUaG9tc29uOyBpZXRmQGlldGYub3JnDQo+IENjwqA6IGRyYWZ0LWRvbHNvbi1wbHVz
LW1pZGRsZWJveC1iZW5lZml0c0B0b29scy5pZXRmLm9yZw0KPiBPYmpldMKgOiBSZTogZHJhZnQt
ZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmlldyBvZiBkcmFmdC0N
Cj4gbW0td2ctZWZmZWN0LWVuY3J5cHQtMDkpDQo+IA0KPiANCj4gSGl5YSwNCj4gDQo+IE9uIDEy
LzA0LzE3IDA5OjEzLCBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tIHdyb3RlOg0KPiA+IEhp
IFN0ZXBoZW4sDQo+ID4NCj4gPiBQbGVhc2Ugc2VlIGlubGluZS4NCj4gPg0KPiA+IENoZWVycywg
TWVkDQo+ID4NCj4gPj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tIERlw4IgOiBTdGVwaGVu
IEZhcnJlbGwNCj4gPj4gW21haWx0bzpzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllXSBFbnZvecOD
wqnDgiA6IG1hcmRpIDExIGF2cmlsIDIwMTcNCj4gPj4gMjA6MzQgw4PigqzDgiA6IERhdmUgRG9s
c29uOyBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xOOyBNYXJ0aW4gVGhvbXNvbjsNCj4gPj4gaWV0
ZkBpZXRmLm9yZyBDY8OCIDoNCj4gPj4gZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVm
aXRzQHRvb2xzLmlldGYub3JnIE9iamV0w4IgOiBSZToNCj4gPj4gZHJhZnQtZG9sc29uLXBsdXMt
bWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmlldyBvZiBkcmFmdC0NCj4gPj4gbW0td2ct
ZWZmZWN0LWVuY3J5cHQtMDkpDQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IE9uIDExLzA0LzE3IDEz
OjAzLCBEYXZlIERvbHNvbiB3cm90ZToNCj4gPj4+IFJlZ2FyZGluZyAiYmVuZWZpdHMiLCB0aGVz
ZSBkZXZpY2VzIGNsZWFybHkgaGF2ZSBwZXJjZWl2ZWQNCj4gPj4+IGJlbmVmaXRzDQo+ID4+DQo+
ID4+IEkgZG8gbm90IGFncmVlIHRoYXQgdGhlIElFVEYgb3VnaHQgZGVzY3JpYmVkIHBlcmNlaXZl
ZCBiZW5lZml0cyBhcw0KPiA+PiBpZiB0aGUgY2xhaW1lZCBiZW5lZml0cyBhY2NydWUgYXMgaG9w
ZWQgZm9yLg0KPiA+DQo+ID4gW01lZF0gSSdtIGFmcmFpZCBpdCBpcyBob3BlZCBmb3Igc29tZSBm
dW5jdGlvbnMuIEZvciBleGFtcGxlLCB0aGUNCj4gPiBJRVRGIHNwZWNpZmllZCBpbiB0aGUgcGFz
dCBtYW55IGZ1bmN0aW9ucyB0byBwcm92aWRlIHNwZWNpZmljDQo+ID4gc2VydmljZXMgKGNhbGxl
ZCBiZW5lZml0IGluIGRyYWZ0LWRvbHNvbikgc3VjaCBhcyBOQVQ2NCAoSVB2NCBzZXJ2aWNlDQo+
ID4gY29udGludWl0eSkuDQo+IA0KPiBJJ20gbm90IHN1cmUgdGhhdCBzL2JlbmVmaXRzL3NlcnZp
Y2VzL2cgaW4gdGhlIGRvY3VtZW50IHRleHQNCj4gd291bGQgd29yaywgc28gSSBkb24ndCBhY2Nl
cHQgdGhhdCBhcmd1bWVudC4gSWYgeW91IG1lYW50DQo+IHNvbWV0aGluZyBlbHNlLCBJJ20gbm90
IHN1cmUgd2hhdC4NCj4gDQo+ID4NCj4gPiBJZiB5b3UgZG9uJ3QgcGVyY2VpdmUgdGhhdCBmdW5j
dGlvbiBhcyBhICJiZW5lZml0IiwgY2FuIHlvdSBwbGVhc2UNCj4gPiBhbnN3ZXIgdGhlIGZvbGxv
d2luZzoNCj4gPg0KPiA+ICogQmVjYXVzZSB5b3VyIG9wZXJhdG9yIGlzIHJ1bm5pbmcgb3V0IG9m
IElQdjQgYWRkcmVzc2VzLCBpdCBkZWNpZGVzDQo+ID4gdG8gZ2l2ZSB5b3UgYW4gSVB2NiBwcmVm
aXggd2l0aG91dCBlbmFibGluZyBhbnkgZnVuY3Rpb24gaW4gdGhlDQo+ID4gbmV0d29yay4gV29u
J3QgeW91IGNhbGwgdGhlIGhvdGxpbmUgb2YgdGhhdCBvcGVyYXRvciB0byBjbGFpbSB0aGF0DQo+
ID4geW91IGRvbid0IGFjY2VzcyB0byBtb3N0IG9mIEludGVybmV0IHJlc291cmNlcyBhbmQgdGhh
dCBzb21ldGhpbmcgaXMNCj4gPiB0byBiZSBmaXhlZCBvdGhlcndpc2UgeW91IHdpbGwgdW5zdWJz
Y3JpYmU/DQo+ID4NCj4gPiAqIFdoZW4geW91IGFyZSBhdHRlbmRpbmcgYW4gSUVURiBtZWV0aW5n
LCBJIGFzc3VtZSB5b3UgYXJlIHVzaW5nDQo+ID4gSVB2Ni1vbmx5IFNTSUQuIERvIHlvdSB2b2x1
bnRlZXIgdG8gb3B0LW91dCBmcm9tIE5BVDY0IGluIHRoZSBjb21pbmcNCj4gPiBtZWV0aW5nPw0K
PiANCj4gSSBkaWQgbm90IGFyZ3VlIHRoYXQgbm8gbWlkZGxlYm94IGV2ZXIgcHJvdmlkZWQgYW55
IGJlbmVmaXQNCg0KW01lZF0gQ29vbC4gVGhpcyBpcyBub3Qgd2hhdCBJIHVuZGVyc3Rvb2QgZnJv
bSB5b3VyIGluaXRpYWwgY29tbWVudDogIi4uLmlmIHRoZSBjbGFpbWVkIGJlbmVmaXRzIGFjY3J1
ZSBhcyBob3BlZCBmb3IiDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgXl5eXl5eXl5eXg0KPiB0byBhbnlvbmUgc28gSSBkb24ndCBrbm93IGhvdyBhbnN3
ZXJpbmcgdGhlIGFib3ZlIHF1ZXN0aW9ucw0KPiB3b3VsZCBoZWxwLg0KDQpbTWVkXSBJIGhlbHBz
IHRvIHVuZGVyc3RhbmQgd2hhdCB3ZSBjYW4gY2FsbCAiYmVuZWZpY2lhbCIgb3Igbm90LiBIYXZp
bmcgY29uY3JldGUgZXhhbXBsZXMgaXMgaGVscGZ1bC4gDQoNCj4gDQo+IEJ1dCBpbiBjYXNlIGl0
IGRvZXMgaGVscDogeWVzLCBmaXJld2FsbHMgaGF2ZSBwcm92aWRlZCBzb21lDQo+IGJlbmVmaXRz
IG92ZXIgdGhlIHllYXJzLiBJIHN1c3BlY3QgdGhvc2UgYXJlIG5vdyBkaW1pbmlzaGluZw0KPiBi
dXQgY291bGQgYmUgd3JvbmcuIEkgZG9uJ3Qga25vdyBpZiBpdCdzIGdvdHRlbiB0byB0aGUgcG9p
bnQNCj4gdGhhdCBmaXJld2FsbHMgYXJlIG1vcmUgb2YgYSBiZW5lZml0IG9yIGEgc2NvdXJnZSB0
b2RheS4gKEhhdmluZw0KPiBqdXN0IGhhZCB0aGUgZnVuIG9mIGluc3RhbGxpbmcgYSBzdHVuL3R1
cm4gc2VydmVyIHRvIGdldCB0d28NCj4gYnJvd3NlcnMgdG8gY2hhdCB3aXRoIG9uZSBhbm90aGVy
LCBJIGNhbiBmcmVzaGx5IGF0dGVzdCB0byB0aGUNCj4gInBvaW50bGVzcyBzY291cmdlIiBhc3Bl
Y3QgYXMgSSBkaWRuJ3QgaGF2ZSB0byBhc2sgdGhlIGYvdw0KPiBhZG1pbnMgYW55dGhpbmcgdG8g
Z2V0IGFyb3VuZCB0aGUgdXNlbGVzcyBiYXJyaWVyIHRoZXkgd2VyZQ0KPiBpbiB0aGlzIHBhcnRp
Y3VsYXIgY2FzZTstKQ0KPiANCj4gSXQgbWlnaHQgYmUgcG9zc2libGUgdG8gZG8gc3R1ZGllcyBh
bmQgcHJvZHVjZSBkYXRhIHRoYXQnZCBoZWxwDQo+IHRoZSBjb21tdW5pdHkgZGVjaWRlIHRoYXQg
cXVlc3Rpb24gKGYvdyB1dGlsaXR5IHZzLiBzY291cmdlKSBhbmQNCj4gdGhhdCBjb3VsZCBiZSBh
IHVzZWZ1bCBhY3Rpdml0eSwgaWYgZG9uZSBvYmplY3RpdmVseS4gVGhhdCBsYXN0DQo+IChvYmpl
Y3Rpdml0eSkgc2VlbXMgaGFyZCB0aG91Z2gsIGFzIGl0IHNlZW1zIHRoZXJlIGFyZSBtYW55IGZv
bGtzDQo+IHdobyBmaW5kIGJlaW5nIG9iamVjdGl2ZSBpbiB0aGlzIHNwYWNlIGRpZmZpY3VsdCAo
b24gYWxsIHNpZGVzKS4NCg0KW01lZF0gWWVzLCB0aGF0J3MgYSBjb2xsZWN0aXZlIGVmZm9ydCB0
byBiZSBtYWRlIGJ5IGFsbC4gSW4gdGhlIG1lYW50aW1lLCB3ZSBuZWVkIHRvIHJlbWVtYmVyIHRo
YXQgSUVURiBpcyBzdXBwb3NlZCB0byBkbyBFTkdJTkVFUklORy4gDQoNCj4gSSd2ZSBubyBpZGVh
IGlmIHNpbWlsYXIgc3R1ZGllcyBhbmQgZGF0YSBjb3VsZCBoZWxwIHdpdGgNCj4gKHJlLSlldmFs
dWF0aW5nIG90aGVyIGFzcGVjdHMgb2YgbWlkZGxlYm94IGRlcGxveW1lbnQgY2xhaW1lZA0KPiB1
dGlsaXR5Lg0KPiANCj4gQW5kIGFnYWluLCBJIHNlZSBubyB1dGlsaXR5IGF0IGFsbCBpbiBhIHN0
YXRlbWVudHMgYWxvbmcgdGhlDQo+IGxpbmVzIHRoYXQgImZpcmV3YWxscyBhcmUgYmVuZWZpY2lh
bCBiZWNhdXNlIHRoZXkgY2FuIGRvIFguIg0KPiANCj4gUy4NCj4gDQo+ID4NCj4gPg0KPiA+IFRo
YXQgaXMgZmFyIHRvbw0KPiA+PiBjbG9zZSB0byBtYXJrZXRpbmcuIEluIGEgY29udGVudGlvdXMg
Y2FzZSBsaWtlIHRoaXMsIEkgY2FuIHNlZSB3aHkNCj4gPj4gc29tZW9uZSBtYXkgZmVlbCB0aGF0
J3MgdXNlZnVsIGFzIGEgZm9ybSBvZiBiYWxhbmNlIG9yIHBhcnQgb2YgYQ0KPiA+PiBsYXJnZXIg
ZGViYXRlLCBidXQgaW4gdGhlIGVuZCBJIHRoaW5rIHdlIG5lZWQgdG8gc3RlcCBiYWNrIGFuZCB0
YWtlDQo+ID4+IGFuIGVuZ2luZWVyaW5nIGFwcHJvYWNoLg0KPiA+DQo+ID4gW01lZF0gRnVsbHkg
YWdyZWUuIFRoaXMgaXMgd2h5IHdlIG5lZWQgdG8gdW5kZXJzdGFuZCB0aGUgaW50ZW5kZWQNCj4g
PiB1c2FnZSB0byBoYXZlIGEgcmVmZXJlbmNlIGZvciBhbnkgZW5naW5lZXJpbmcgYXBwcm9hY2gu
DQo+ID4NCj4gPj4NCj4gPj4gUw0KPiA+Pg0KPiA+Pj4gdG8gdGhvc2Ugd2hvIGRlcGxveSB0aGVt
LiBNeSB2aWV3IGlzIHRoYXQgdGhlIGRvY3VtZW50IHNob3VsZA0KPiA+Pj4gZXhwbGFpbiB0aGF0
IHBlcnNwZWN0aXZlIGZvciByZWFkZXJzIHdobyBsYWNrIHRoZSBvcGVyYXRvcg0KPiA+Pj4gcGVy
c3BlY3RpdmUuIFRoZSBpbnRlbnQgd2FzIG5vdCB0byBtYW5kYXRlIG9yIHJlY29tbWVuZA0KPiA+
Pj4gZGVwbG95bWVudHMuDQo+ID4+Pg0KPiA+Pj4gRGF2aWQgRG9sc29uIMODwqLDouKAmsKsw4XC
vSBPcmlnaW5hbCBNZXNzYWdlIEZyb206DQo+ID4+PiBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2Uu
Y29tIFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDExLCAyMDE3IDc6NDgNCj4gPj4+IEFNIFRvOiBTdGVw
aGVuIEZhcnJlbGw7IE1hcnRpbiBUaG9tc29uOyBpZXRmQGlldGYub3JnIENjOg0KPiA+Pj4gZHJh
ZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzQHRvb2xzLmlldGYub3JnIFN1YmplY3Q6
IFJFOg0KPiA+Pj4gZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6
IFJldmlldyBvZg0KPiA+Pj4gZHJhZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQtMDkpDQo+ID4+Pg0K
PiA+Pj4NCj4gPj4+IEhpIFN0ZXBoZW4sDQo+ID4+Pg0KPiA+Pj4gUGxlYXNlIHNlZSBpbmxpbmUu
DQo+ID4+Pg0KPiA+Pj4gQ2hlZXJzLCBNZWQNCj4gPj4+DQo+ID4+Pj4gLS0tLS1NZXNzYWdlIGQn
b3JpZ2luZS0tLS0tIERlIDogU3RlcGhlbiBGYXJyZWxsDQo+ID4+Pj4gW21haWx0bzpzdGVwaGVu
LmZhcnJlbGxAY3MudGNkLmllXSBFbnZvecODxpLDgsKpIDogbWFyZGkgMTEgYXZyaWwNCj4gPj4+
PiAyMDE3IDEwOjUxIMODxpLDouKAmsKsIDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjsgTWFy
dGluIFRob21zb247DQo+ID4+Pj4gaWV0ZkBpZXRmLm9yZyBDYyA6DQo+ID4+Pj4gZHJhZnQtZG9s
c29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzQHRvb2xzLmlldGYub3JnIE9iamV0IDoNCj4gPj4+
PiBSZTogZHJhZnQtZG9sc29uLXBsdXMtbWlkZGxlYm94LWJlbmVmaXRzICh3YXMgUkU6IFJldmll
dyBvZg0KPiA+Pj4+IGRyYWZ0LSBtbS13Zy1lZmZlY3QtZW5jcnlwdC0wOSkNCj4gPj4+Pg0KPiA+
Pj4+DQo+ID4+Pj4gSGkgTWVkLA0KPiA+Pj4+DQo+ID4+Pj4gT24gMTEvMDQvMTcgMDk6MTUsIG1v
aGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20gd3JvdGU6DQo+ID4+Pj4+PiBJIGhvcGUgdGhhdCB0
aGUgSUVURiBuZXZlciBwdWJsaXNoZXMNCj4gPj4+Pj4+IGRyYWZ0LWRvbHNvbi1wbHVzLW1pZGRs
ZWJveC1iZW5lZml0czsgaXQgbWFrZXMgY2xhaW1zDQo+ID4+Pj4+PiBhYm91dCB0aGUgYmVuZWZp
dHMgb2Ygc3BlY2lmaWMgc29sdXRpb25zIGZvciBkaWZmZXJlbnQgdXNlDQo+ID4+Pj4+PiBjYXNl
cyB3aXRoIHRoZSBnb2FsIG9mIGp1c3RpZnlpbmcgdGhvc2Ugc29sdXRpb25zLg0KPiA+Pj4+DQo+
ID4+Pj4+IFtNZWRdIEknbSBhZnJhaWQgdGhpcyBpcyBzcGVjdWxhdGluZyBhYm91dCB0aGUgaW50
ZW50IG9mDQo+ID4+Pj4+IGRyYWZ0LWRvbHNvbi4gQXNzdXJlZCB0aGlzIGlzIG5vdCB0aGUgcHVy
cG9zZSBvZiB0aGF0DQo+ID4+Pj4+IGRvY3VtZW50LiBUaGUgbW90aXZhdGlvbiBpcyB0byBkb2N1
bWVudCBjdXJyZW50IHByYWN0aWNlcw0KPiA+Pj4+PiB3aXRob3V0IGluY2x1ZGluZyBhbnkgcmVj
b21tZW5kYXRpb24gb3IgY2xhaW1pbmcgdGhlc2UNCj4gPj4+Pj4gc29sdXRpb25zIGFyZSBzdXBl
cmlvciB0byBvdGhlcnMuDQo+ID4+Pj4NCj4gPj4+PiBKdXN0IHRvIG5vdGUgdGhhdCBJIGNvbXBs
ZXRlbHkgYWdyZWUgd2l0aCBNYXJ0aW4ncw0KPiA+Pj4+IGludGVycHJldGF0aW9uIG9mIHRoZSB0
aHJ1c3Qgb2YgdGhpcyBkcmFmdCBhbmQgSSB0b3RhbGx5IGZhaWwNCj4gPj4+PiB0byBzZWUgaG93
IHlvdXIgYXJndW1lbnQgYWJvdmUgY2FuIGJlIGp1c3RpZmllZCBnaXZlbiB0aGF0DQo+ID4+Pj4g
ZHJhZnQgdGl0bGUsIGFic3RyYWN0IGFuZCBldmVuIGZpbGVuYW1lIChhbmQgYWxzbyB0aGUNCj4g
Pj4+PiBjb250ZW50Oy0pLg0KPiA+Pj4NCj4gPj4+IFtNZWRdICJiZW5lZmljaWFsIiBpcyBkZXJp
dmVkIGZyb20gdGhlIGluaXRpYWwgcmVxdWVzdCB0aGF0DQo+ID4+PiBtb3RpdmF0ZWQgdGhpcyBk
cmFmdCAoZXhjZXJwdCBmcm9tIHRoZSBhYnN0cmFjdCk6DQo+ID4+Pg0KPiA+Pj4gQXQgSUVURjk3
LCBhdCBhIG1lZXRpbmcgcmVnYXJkaW5nIHRoZSBQYXRoIExheWVyIFVEUCBTdWJzdHJhdGUNCj4g
Pj4+IChQTFVTKSBwcm90b2NvbCwgYSByZXF1ZXN0IHdhcyBtYWRlIGZvciBkb2N1bWVudGF0aW9u
IGFib3V0IHRoZQ0KPiA+Pj4gYmVuZWZpdHMNCj4gPj4+IF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eIHRoYXQNCj4gPj4+IG1pZ2h0IGJlIHBy
b3ZpZGVkIGJ5IHBlcm1pdHRpbmcgbWlkZGxlYm94ZXMgdG8gaGF2ZSBzb21lDQo+ID4+PiBeXl5e
Xl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xg0KPiA+Pj4gdmlzaWJpbGl0eSB0byB0cmFuc3BvcnQtbGF5ZXIgaW5mb3JtYXRpb24uDQo+ID4+
PiBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl4NCj4gPj4+DQo+ID4+
PiBXaGVuIHRoZSBhYnN0cmFjdA0KPiA+Pj4+IHNheXMgIlRoaXMgZG9jdW1lbnQgc3VtbWFyaXpl
cyBiZW5lZml0cyIgdGhlbiBJIGNhbm5vdA0KPiA+Pj4+IGludGVycHJldCB0aGF0IGFzIG90aGVy
IHRoYW4gYmVpbmcgaW50ZW5kZWQgdG8ganVzdGlmeSB0aGUgdXNlcw0KPiA+Pj4+IGRlc2NyaWJl
ZC4NCj4gPj4+DQo+ID4+PiBbTWVkXSBJIHdvdWxkIHByZWZlciBpZiB3ZSBjYW4gYXZvaWQgdG8g
ImludGVycHJldCIsIGJ1dCByYWlzZQ0KPiA+Pj4gcXVlc3Rpb25zIHRvIHRoZSBhdXRob3JzIGlm
IHRoZXJlIGlzIGEgZG91YnQuIFRoZSBkb2N1bWVudCBkb2VzDQo+ID4+PiBub3QgcHJvdmlkZSBh
IHJlY29tbWVuZGF0aW9uIG9yIGNsYWltcyB0aGlzIGlzIHRoZSBvbmx5IHdheSB0bw0KPiA+Pj4g
YWNoaWV2ZSB0aGUgdGVjaG5pY2FsIGdvYWxzLiBJdCBkb2VzIG9ubHkgcmVmbGVjdCBzb21lIGRl
cGxveW1lbnQNCj4gPj4+IHJlYWxpdHkgdG9nZXRoZXIgd2l0aCBzb21lIG1vdGl2YXRpb25zLg0K
PiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IEEgZmFpcmx5IHRob3JvdWdoIHJlLXdyaXRlIHRvIGFpbSB0
byBkZXNjcmliZSB0aGUgcHJvcyBhbmQNCj4gPj4+PiBjb25zIHdvdWxkIGJlIGEgZGlmZmVyZW50
IGFuZCBtb3JlIHVzZWZ1bCBkb2N1bWVudC4NCj4gPj4+DQo+ID4+PiBbTWVkXSBUaGVyZSBhcmUg
YWxyZWFkeSBtYW55IFJGQ3MgdGhhdCBkaXNjdXNzIHRoZSBpc3N1ZXMvY29ucyAoSQ0KPiA+Pj4g
Y2FuIGNpdGUgdGhpcyBSRkMgSSBjby1hdXRob3JlZA0KPiA+Pj4gaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL3JmYzYyNjkgZm9yIHRoZSBDR04gY2FzZSkuIFdoYXQgaXMNCj4gPj4+IG5lZWRl
ZCBJTUhPIGlzIHNvbWV0aGluZyBlbHNlOiB1bmRlcnN0YW5kIHRoZSByZXF1aXJlbWVudHMgdGhh
dA0KPiA+Pj4gbGVkIHRvIGRlcGxveSBzb21lIG9mIHRoZXNlIGZ1bmN0aW9ucy4NCj4gPj4+DQo+
ID4+PiBTaW1pbGFybHkgYSBkcmFmdA0KPiA+Pj4+IHRoYXQgc3RyaXZlcyB0byBuZXV0cmFsbHkg
ZGVzY3JpYmUgZXhpc3RpbmcgcmVhbGl0eSBjb3VsZCBtYXliZQ0KPiA+Pj4+IGJlIHVzZWZ1bCAo
KikNCj4gPj4+DQo+ID4+PiBbTWVkXSBUaGlzIGlzIHRoZSBpbnRlbnQgb2YgZHJhZnQtZG9sc29u
Lg0KPiA+Pj4NCj4gPj4+IGJ1dCBvbmUgdGhhdCBvbmx5IGRlc2NyaWJlcyBtaWRkbGVib3ggZnJp
ZW5kcyB3aXRoDQo+ID4+Pj4gImJlbmVmaXRzIiBpcyBub3QgSU1PIGJlbmVmaWNpYWwgOy0pDQo+
ID4+Pg0KPiA+Pj4gW01lZF0gVGhlIGludGVudCBpcyBub3QgdG8gInNlbGwgc29tZXRoaW5nIiBi
dXQgdG8gdW5kZXJzdGFuZA0KPiA+Pj4gdGhlIHRlY2huaWNhbCBuZWVkcyBzbyB0aGF0IGhvcGVm
dWxseSB3ZSBjYW4gaGF2ZSBhIHJlZmVyZW5jZSBmb3INCj4gPj4+IGZ1dHVyZSBzb2x1dGlvbi1v
cmllbnRlZCBkaXNjdXNzaW9ucy4gSWYgYSBnaXZlbiBmdW5jdGlvbiBjYW4gYmUNCj4gPj4+IHBy
b3ZpZGVkIHdpdGhvdXQgaW52b2x2aW5nIGFuIG9uLXBhdGggZGV2aWNlLCB0aGlzIHdvdWxkIGJl
IGdyZWF0DQo+ID4+PiBmb3Igb3BlcmF0b3JzIChvcHRpbWl6ZSBDQVBFWC9PUEVYIGlzIG91ciBt
b3R0bykuDQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gQ2hlZXJzLCBTLg0KPiA+Pj4+DQo+ID4+Pj4g
KCopIFRoYXQgaXMgdGhlIGFyZ3VtZW50IGZvciBkcmFmdC1tbS1lZmZlY3QtZW5jcnlwdCwgZm9y
IHdoaWNoDQo+ID4+Pj4gSSBkbyBzdXBwb3J0IHB1YmxpY2F0aW9uIChhcHBhcmVudGx5IGluIGRp
c2FncmVlbWVudCB3aXRoDQo+ID4+Pj4gTWFydGluIGluIHRoYXQgY2FzZTotKQ0KPiA+Pj4+DQo+
ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4NCj4gPg0KDQo=


From nobody Wed Apr 12 02:51:46 2017
Return-Path: <kovatsch@inf.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF77A131511; Wed, 12 Apr 2017 02:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 2AV3p0dfm7GK; Wed, 12 Apr 2017 02:51:42 -0700 (PDT)
Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C9C3131526; Wed, 12 Apr 2017 02:51:41 -0700 (PDT)
Received: from CAS12.d.ethz.ch (172.31.38.212) by edge10.ethz.ch (82.130.75.186) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 12 Apr 2017 11:51:35 +0200
Received: from MBX210.d.ethz.ch ([fe80::ed77:7d47:9467:69a9]) by CAS12.d.ethz.ch ([fe80::7861:4ecb:7c42:cad4%10]) with mapi id 14.03.0319.002;  Wed, 12 Apr 2017 11:51:39 +0200
From: "Kovatsch  Matthias" <kovatsch@inf.ethz.ch>
To: Mark Nottingham <mnot@mnot.net>, Carsten Bormann <cabo@tzi.org>
CC: "art@ietf.org" <art@ietf.org>, "draft-ietf-core-coap-tcp-tls.all@ietf.org" <draft-ietf-core-coap-tcp-tls.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>
Subject: RE: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsbAL4XGhCj4NBUOslxkUkswmRKG+Oc0AgAD5ZgCAAkm54A==
Date: Wed, 12 Apr 2017 09:51:38 +0000
Message-ID: <55877B3AFB359744BA0F2140E36F52B558B2A929@MBX210.d.ethz.ch>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net>
In-Reply-To: <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [188.195.112.97]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sjxNWTA23A8NRr0avKDnr7Bx0KY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 09:51:45 -0000

RGVhciBNYXJrDQoNCj4gT0suIEp1c3QgY3VyaW91cyAtLSBpcyB0aGVyZSBhIHN0cm9uZyBtb3Rp
dmF0aW9uIGhlcmU/IEl0IHNlZW1zIHZlcnkgb2RkIHRvIHR1bm5lbA0KPiBIVFRQLWxpa2Ugc2Vt
YW50aWNzIG92ZXIgYSBjdXN0b20gVURQIHByb3RvY29sIChDT0FQKSBvdmVyIFdlYlNvY2tldHMg
b3Zlcg0KPiBIVFRQIGFnYWluLCByYXRoZXIgdGhhbiBqdXN0IHVzaW5nIEhUVFAgKHdoaWNoIEFJ
VUkgeW91IGFscmVhZHkgaGF2ZSBhIG1hcHBpbmcNCj4gdG8pLg0KDQpUaGUgbW90aXZhdGlvbiBp
cyB0byBjb25uZWN0IHRoZSBjb25zdHJhaW5lZCBlbnZpcm9ubWVudCB0byB0aGUgV2ViIGJyb3dz
ZXIuIElkZWFsbHksIG9uZSB3b3VsZCB1c2UgSFRUUCBmcm9tIHRoZSBicm93c2VyIHRvIHRhbGsg
dG8gYSBIVFRQLUNvQVAgY3Jvc3MtcHJveHksIHdoaWNoIGluIHR1cm4gdGFsa3MgdG8gdGhlIGNv
bnN0cmFpbmVkIGRldmljZS4gVGhlIHByb2JsZW0gaGVyZSBpcyB0aGF0IEhUVFAgbmV2ZXIgcHJv
cGVybHkgYW5kIHVuaXF1ZWx5IHNvbHZlZCBzZXJ2ZXIgcHVzaCwgd2hpY2ggaXMgcXVpdGUgY3J1
Y2lhbCBmb3IgcmVzb3VyY2UtY29uc3RyYWluZWQgZGV2aWNlcyBhbmQgSW9UIHVzZSBjYXNlcy4g
VGh1cy0tLWV2ZW4gYmV5b25kIHRoZSBDb1JFIHVzZSBjYXNlLS0tcGVvcGxlIHJlc29ydCB0byBX
ZWJTb2NrZXRzLiBTaW5jZSBXZWJTb2NrZXRzIGFyZSBqdXN0IGEgYnJvd3NlciB2ZXJzaW9uIG9m
IFRDUCwgcGVvcGxlIGFsc28gaGF2ZSB0byBpbnZlbnQgdGhlaXIgb3duIHByb3RvY29sIGV2ZXJ5
IHRpbWUuLi4gVGhpcyBpcyB3aGVyZSBDb0FQLW92ZXItV2ViU29ja2V0cyBoZWxwcywgb2YgY291
cnNlIHdpdGggdGhlIHByaW1hcnkgZm9jdXMgdG8gc2VhbWxlc3NseSBjb25uZWN0IHRvIGNvbnN0
cmFpbmVkIGRldmljZXMuDQoNCkkgYW0gbm90IHN1cmUgd2hhdCBpcyB0aGUgcHJlZmVycmVkIHdh
eSB0byBzb2x2ZSB0aGUgYXN5bmMgY29tbXVuaWNhdGlvbiBpc3N1ZSBvZiBIVFRQLiBTZXJ2ZXIg
U2VudCBFdmVudHMsIGZvciBpbnN0YW5jZSwgYXJlIGFscmVhZHkgcHJldHR5IGNsb3NlIHRvIHRo
ZSBPYnNlcnZlIG1lY2hhbmlzbS4gTWF5YmUgd2UgY291bGQgcHJvcGVybHkgZml4IHRoZSBwdXNo
IHN1cHBvcnQgb2YgSFRUUCB0byBjb3VudGVyIHRoZSBlbmRsZXNzIHN0YWNraW5nIG9mIHByb3Rv
Y29scyBhIGJpdD8NCg0KQmVzdCByZWdhcmRzDQpNYXR0aGlhcw0K


From nobody Wed Apr 12 03:06:40 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB6F7131559; Wed, 12 Apr 2017 03:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 aUfiBIwyP8fX; Wed, 12 Apr 2017 03:06:25 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFBD131546; Wed, 12 Apr 2017 03:06:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1491991584; d=isode.com; s=june2016; i=@isode.com; bh=+GpEPL5/0zpcK40iiymiYtDj5GeLhe4qhSu0Wkc4aac=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ohEPv9wp6nyWJwNXZ0bjUkzYIdlpY0CaIisF+xe4aG23DPHpU1NwXByoSReA1oGYUUAwyp UxyimK903SkKTHpS4d6p7E7aclHKu8HAp8mBxg8aHupooA9IEH6M/6XxhS8AY4lCZHr8/x 2QeFD/SRfeOCviPvkZJ2jDHhYTerdfk=;
Received: from [172.20.1.215] ((unknown) [62.232.206.186])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WO38IAB2XTXN@waldorf.isode.com>; Wed, 12 Apr 2017 11:06:24 +0100
X-SMTP-Protocol-Errors: NORDNS
Subject: Re: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
To: Kovatsch Matthias <kovatsch@inf.ethz.ch>, Mark Nottingham <mnot@mnot.net>, Carsten Bormann <cabo@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <55877B3AFB359744BA0F2140E36F52B558B2A929@MBX210.d.ethz.ch>
Cc: "art@ietf.org" <art@ietf.org>, "draft-ietf-core-coap-tcp-tls.all@ietf.org" <draft-ietf-core-coap-tcp-tls.all@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <cc7b5d80-21f1-e38b-4739-f44d536cf260@isode.com>
Date: Wed, 12 Apr 2017 11:06:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
In-Reply-To: <55877B3AFB359744BA0F2140E36F52B558B2A929@MBX210.d.ethz.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RjOFrBlBlTT9W8JBTnIbQVC0-oE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 10:06:27 -0000

Hi Matthias,


On 12/04/2017 10:51, Kovatsch Matthias wrote:
> Dear Mark
>
>> OK. Just curious -- is there a strong motivation here? It seems very odd to tunnel
>> HTTP-like semantics over a custom UDP protocol (COAP) over WebSockets over
>> HTTP again, rather than just using HTTP (which AIUI you already have a mapping
>> to).
> The motivation is to connect the constrained environment to the Web browser. Ideally, one would use HTTP from the browser to talk to a HTTP-CoAP cross-proxy, which in turn talks to the constrained device. The problem here is that HTTP never properly and uniquely solved server push, which is quite crucial for resource-constrained devices and IoT use cases. Thus---even beyond the CoRE use case---people resort to WebSockets. Since WebSockets are just a browser version of TCP, people also have to invent their own protocol every time... This is where CoAP-over-WebSockets helps, of course with the primary focus to seamlessly connect to constrained devices.
>
> I am not sure what is the preferred way to solve the async communication issue of HTTP. Server Sent Events, for instance, are already pretty close to the Observe mechanism. Maybe we could properly fix the push support of HTTP to counter the endless stacking of protocols a bit?
We have a WG for this:
  https://datatracker.ietf.org/wg/webpush/about/


From nobody Wed Apr 12 03:53:21 2017
Return-Path: <bilhanan.silverajan@tut.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2EA1315FD; Wed, 12 Apr 2017 03:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tutfi.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 suNNgl9JGG52; Wed, 12 Apr 2017 03:53:17 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0106.outbound.protection.outlook.com [104.47.0.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C33131601; Wed, 12 Apr 2017 03:53:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tutfi.onmicrosoft.com;  s=selector1-tut-fi; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=r95wy0QdwwLsVIXJegmBBR+rVOAzHNUNSAeIy09VDLM=; b=fE/g04rNgjUrtN7mP+0OUgm92UmPfBUeFBYUDIrD4wQ8j5qkyl6rtk2lnK5SgUlB/o5+cvxsR6jhN7xP1bAVGppOuj9uiSjdF36KtzR+07EkbCKe7AqEfNIdRivLHyoz1niuXU+nak3x8Ue7Ie80c7Rlsf/wOLIT9konyjKdumg=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=tut.fi;
Received: from Bilhanans-MacBook-Pro.local (88.114.43.235) by AM3PR02MB1074.eurprd02.prod.outlook.com (2a01:111:e400:c405::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Wed, 12 Apr 2017 10:53:08 +0000
Subject: Re: [art] [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
To: Carsten Bormann <cabo@tzi.org>, Mark Nottingham <mnot@mnot.net>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <52AFE50B189544AFB2744028519A173D@WeiGengyuPC> <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net> <9302A268-50CF-4688-A79D-8343E5B9B7CE@tzi.org>
CC: weigengyu <weigengyu@bupt.edu.cn>, <art@ietf.org>, <draft-ietf-core-coap-tcp-tls.all@ietf.org>, <ietf@ietf.org>, <core@ietf.org>
From: Bill Silverajan <bilhanan.silverajan@tut.fi>
Message-ID: <b6ad962c-8da5-441d-8056-af0493c05398@tut.fi>
Date: Wed, 12 Apr 2017 13:53:05 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <9302A268-50CF-4688-A79D-8343E5B9B7CE@tzi.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [88.114.43.235]
X-ClientProxiedBy: VI1PR0802CA0004.eurprd08.prod.outlook.com (2603:10a6:800:aa::14) To AM3PR02MB1074.eurprd02.prod.outlook.com (2a01:111:e400:c405::16)
X-MS-Office365-Filtering-Correlation-Id: edff1787-f36b-456c-3983-08d481921b7c
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:AM3PR02MB1074; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR02MB1074; 3:8YiXnG6Au1lTLkEQLBHF2M+cZXcy9DR5jI2SPVqvhMrZ4Xp2MPT1yxTywzAZWBY1yYCz6vJdOa50AcPboFBbA6pbh4M2ofAW7vzUulttbdCKHRAMQlsliErc9HGHfza0olvTiq++AdVlcOUweY58g3/EFD5dHqm8WVbb0XxNMOlTqwiYKmE89lJ4fgmLnTRZ48EA+P5ZYpC2BaNVpkzd7iQuDYXYeQ/RpjTTT5ahDAuqZRm/eCMsnmbtquOWrBMJ73HkqI7ODc2qh+TnwEuMfnashWVUHQcQIgqy6w1RQ3npH/4YBdP1uQc2VZi4K4Y600tRMhucXBCQZgamVS5KPQ==; 25:qZUsMtca7ILoKCKS/oO1AU1LuiKfNixAJnt48bfZR3yABqg4qXDwTz3mMZBfNxdLq/qQK8/1JhBXjcIWzsNMD2lTxvlfzZoFALf6zgGLgQPukYN+3iX42tqByTDVjuSwbQv1IMsID3CXQYQL+URvS6YP2bKJVW/+nrQi0PG+I9wNYreGyakCo08as8kQKcpvY3o17nqCfHpAnj+ep6d8+Q7ojBWQ/q6+UXgT5iXP6QsTRFcjEzv1RwGuUgk/PfuyV3cI3chGYD+8U3yDW415WIvoNIE5UqLsSNL14FkV062cJkFRFnmJnTk+828AncGl+lkQaRnvp78eIz8nhobaoX2PBrAn5PkazVcorSMmu6x8+Zlmlrswm90jDZjfCGwDchOHIHx2TqyQ358ceEBXnDNEh9KEeNAhnAxPWf1hUyze+vNemTrRDzR3N+h2c+c4HvVkuGB9GRi2nJkQpBLAoA==
X-Microsoft-Exchange-Diagnostics: 1; AM3PR02MB1074; 31:iBJN8djrE6b4Sxq2D1rC52XvAe9fpeaHsQpUB/VWLmXY4Gh8hDjPHtPkMBkZ+J6svGURSdHBZ9RmHI7so9mRsOZlS01102f9KCNohSfhwpbYAtfFPyDGrDns2aeRZbV/+MaZnV1sfs41cT73fLEAL4fKa6XP276FQbJArOj+7iQplGEYR+ieSiWunWbrrtBh1UN1385EIS/P3O+fWoQlrPcC8FnjptF+FUtune5LCZuANUQqX/TwbX/k5cbj9WF7; 20:H1QAz0S7U6ARvGBK6IguwHiDOHtWzFjPVK9wQAm0lslKXQCJXCq1GGRlR6cZqj96xh4KMmcQ95XlBQVDUaV2j9beFdYI7nMfPw83bOyXoksDJCfnyKlBkeJV4AqeDr6v9ORjNje9TO4+Wt8jzH89LFT+bUOr1cx/ihaYOd2vTzmOEPI9uVXWxYTyWQEDpvCsHFXiBJCbnC09FYme22K3B6wwrRnq1rLhZ4CTERUJLt2MtkYrvQVkIJGb9jjqkt5z
X-Microsoft-Antispam-PRVS: <AM3PR02MB107484F039465B59134A4DBF9C030@AM3PR02MB1074.eurprd02.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(190756311086443)(278428928389397);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123564025)(20161123560025)(20161123555025)(20161123562025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(6072148); SRVR:AM3PR02MB1074; BCL:0; PCL:0; RULEID:; SRVR:AM3PR02MB1074; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR02MB1074; 4:P4EvM01zvSlXwAn4K2bwO33lfK4rF0+RWgaXZZerGSzrkdpt4678Qfncwdmvu7g3hIcoPtzIIUPPyXlsWv3GTbf2SQXDi7/kafgEr2wkKO73fEq5EyABGJTTsfa8xJR00+opISC84T8fjNmqanz0exai14wswUNDYsSGN30u12NgjqFSV45J4/xatIk/Js52SXSvFuw15mF4IjEgp+AUfOdDRMdUCyuiIeQEFMNbNzxGUKr8C05+Z4x5ZTX282HTpIYzVvkaASEM3jaCqJPWtnpdFdtf/b4DbO7sGPb5PTfb53+1GCehaetSaZsO27lDVQ64AMXBwPwrreEJmdW5gsaI1Ecb0IsPwQjlkIAoCzk5hLDTA5uDlcbD/WNYOg3IZQEmcbw34Q45DrCwms9LxXjG04Pl19NAPQ6NB0v2ng0QeISG6vWOOTS1b5Ct3NbNAmC0V+VpDapfSjQKb87OAJjyEm6xcDi/OibXFqcS8BQwVvBTTZYkgzjbdNPuuYWdmRkoDXeNxZ+kaDk8WINYapMB8sUJ6ELmNuCEhTms1wg3CdxbxLGGPm1ifJFY9ExrPcCjiEW86vYhh5NElxydVcUjKD5kbpgJuiAgpPK8pm1W0MhgFYK4MONOb0xL8CU5CCUd8HJ2aOTk5YKB+22nuA0zun8eBqdOzu0cS2v4JO2engROFuCJ73eWf6WXt/OFQk0LBsQA1fMq+nYclGWSKKq3nN1fZwOIcxhw6qz0qmz/bIkuac4nfrELjw/2ZzrKvyIcbY7yZgmcAIRhHfT50ntUzQQWjaIT0AokF9ErZYka2L3jQKgEKNBJxw3TT7FFw/h3AO/cE1IfEppE5nyj2g==
X-Forefront-PRVS: 027578BB13
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(39840400002)(39410400002)(39400400002)(24454002)(4326008)(230783001)(50466002)(6506006)(38730400002)(50986999)(7736002)(31696002)(81166006)(54356999)(76176999)(86362001)(8676002)(74482002)(305945005)(31686004)(6246003)(42186005)(6116002)(3846002)(5660300001)(53936002)(6486002)(6512007)(54906002)(229853002)(6666003)(2950100002)(33646002)(4001350100001)(66066001)(2906002)(53546009)(2870700001)(25786009)(189998001)(36756003)(47776003)(23676002)(83506001)(65806001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR02MB1074; H:Bilhanans-MacBook-Pro.local; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTNQUjAyTUIxMDc0OzIzOkJMYjBZeWhrU0F6dmt3WjVGM1c5bGxTUmYz?= =?utf-8?B?b1Ird0FJY1F6ZFR0VzhVYXQ0TENyM2VBeTFlNmhMOENKSnNhYmdiYUhUQU9U?= =?utf-8?B?L25YYm1aVlo4MmxTTldqU0lyS0M1aElhQkQrb0NUYkF3Y3NyVzVPUkRRNFVY?= =?utf-8?B?YmM2V2RIOVIxdXBhTEc0QUxvTjV5VzF2Yi9keUI4VmdsS2xySjlBcXp6RkhR?= =?utf-8?B?Mjk4T0FoWXpRMlBaNlNKZ2F6SEd2eFp3Wlk1VzVSZzJITFg1WTIxTHR5NEdl?= =?utf-8?B?N21Iam1kZzhGdUxJSit1NXhEWVYwa3VVTElVYUUyRWpDUmJ6bFpia2x4RXlF?= =?utf-8?B?Z1Q0LzhmQUR1UTF2ZUJ3RDkrNm9CbS9QREh4NGJuTkloU0VIQngwcEVZcVhQ?= =?utf-8?B?Z0ZyVUI3ZXd1dWRuVE1XZm56a2VrdzNmb0t6c0xwMWxpYzlYQThHZE4ydzBK?= =?utf-8?B?QlNDWTQyNVJPOTU4RFA0aHNicnlPSGpqVmJtWTJUMzY1MVF6OTkwRG5McFlF?= =?utf-8?B?SWlTRXZEYU5sck9lYTN6RmpFeDJxQTBuWG8vS2hFR3k5eTZNckYzdFNCa2xy?= =?utf-8?B?UDZwMDI1S1VjOEZMM1MwRHlDVGduVjhOY3NpUFBjQUxPaVppa3k2RC9aRE4z?= =?utf-8?B?UzNOVmdqMXBqUlBOV2FKeXRpYWxndEhPTm0yajNiN1pQVkdYaHgzYjJrM1o3?= =?utf-8?B?bUVlOGNrb3J4UnV0NTRybW5tdGNVaUkvakMzRlJxcmV5M0Q0SW04K3B1dm5R?= =?utf-8?B?d1VtcDhwaVpacHhpV0Z4MC9OaW1VVno2Nm9PeFdtaW9hUjQ3Y2tUazNaRHdx?= =?utf-8?B?bVRJV0FUaldJa0xJZWt0MVhlNTBMZko2OUxLRHgrN3M2ZXZvekNiTjJ4d3Nl?= =?utf-8?B?L3FaalVXTXJrdEUxRzJNNHpxZUZWV1BpSFhPN2h6SzdsR2YzdTdJa1lxN2tI?= =?utf-8?B?Mzhwd3FmSzZXNHhsMHAwWkZmaWxRTnRObG1SdkVhQ2VlN3pxT1pkZW5aNklT?= =?utf-8?B?VHA0NitjaWRpV1c1SUZEQ1o0MGdtWnBsTENDUUcyUU56UW82a2ZhZCtGQk1W?= =?utf-8?B?dnhBMHlRQmgwL2lYOUppNlZIQWJRWGNJM2dpTElEYmR1UkxLTnUzL0xNcUx0?= =?utf-8?B?THVOMHlMd2NvTDhqUVJCNDhnb1FsZCswTldNSDJoalBOMmo4aWRCNlFwank1?= =?utf-8?B?TnZpOUJ1akp5Z1QxZ3g2ZngrNTJzd2pwZUp0MlkvTDNscFJXZGdwUE5aeWYy?= =?utf-8?B?Ui9VVS8xdW9ETjdYcThXcXo1SjhVcFFwcEJqKzNIODMwbjBVY1ZxcG5vS3RK?= =?utf-8?B?VEFkZEtQbENtY2REcGdpNGdqVWpTSkVranhSS3h5Y1JyQURVZWE0eVdueGZV?= =?utf-8?B?YktCZGEzak5wbGtsZktmNnhIeFFyNlJkTjBZRHlqK082RlFqSm5sN1QrclJJ?= =?utf-8?B?TnUwSWRJWkNFUnBFWnVhdnpqa0NhU1l4aG85Qms5cDFWZW1FSktiQjR1Nkls?= =?utf-8?B?MjR0Y3grcGRPdTEwalp4NlEvTnpROHZlSG16RGlPUGI5NFB2M2VSRVY3eTVV?= =?utf-8?Q?zsSXRm2Ev2RQulgagqf+xGZ1rwv/r6vlVc7MBn7Fxn/M=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AM3PR02MB1074; 6:TRVc5W4Ukguue5/CDr9bG1N5RyqL2cBy4m2Xxkqm9KAmut0+FV9h3IsoH52DDf54TtQN3Tb/lIVfwWJMzg792fuZxjvmsEVAA7YWXm0a2KjgOqUwmJFElKUDcttcPNSt7tT7AIXkraKrCHRRniCysN6BeGm5Fla14AxhpVCbK1FQHfTB6IIrMQPMCGqJg9ZVYYeQbQ7CkyQuCovQMmPd8Q24ClYX3fub9JRhJrHOisK26XaNIylBmaaWyxm00AIeQnfdMJeW+1t/RX3c0iqbx5XOHlYk5UOpQzArtJtg38j1coCDS/2vVo4sTG1GTA1mLH64Nyam4vqRCqRvjRtygUjie8CWwDNPjkrgzHNbN/EhReQmZ+cUhDVaq3U19SXEZdL7j7YC8dy/PAKZSWdZQ7dE8AkBZJ7Pkj+mcTPerxmuNKhxU6oALnVtzJf4KaHsuEV+GRU6wDP0h2rNMtxWRQ==; 5:f+DyIRWpqnCA0KOOt68qNU6mhFAlc3VS/wrWObmIq3+a+tZ2+3X8N3FjYWiFJJlTN5UJic3geI/vPKttITzjoxDJ3Qf8D7XR3TbwDdn9Sb785KFAEfds5QmVsxU1qutWitpOQ/24UkI2QkwD1ywtTg==; 24:Ho1j5gdevsUmkWKEP5Z5eYOrJSizLiL+lBzsSy43FMoNi4TjkJrZqrnw0q6OWXpYwLiERnAZJpYQBpy7Xi0G2r0zZtNNyfaxq1nRDAA58H4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; AM3PR02MB1074; 7:BMWymjTfhiQi18T7YTRc8Yd0bLZFD/MF/mjEnFR8QKqZUdUkaRp1n7Y+MLJYmh+TTJRyBOh5sbJDyPlgRQnjPdYm5zCLBMerylL/q/PEPoH953B3q9bmzyeFVJfSBnoAp752gC3UbEXO5KkzPuT1VOyoAHXWO51f7eJXFy/EWr2IbwmVPz8jfudCAaSjSaT+eyttdKMCvjBXOdpVD2m1idTvD0+D75Sacy2VnzQRNN6YQaqQG14PEPKIvEjwOQwwo8VF+SNft5axw9Z2v8utUlROTzty0fjja45klACcjZtpM/lHn38ybQde9hGUzVuFn8x3plvemCouiBa1IhNG1A==
X-OriginatorOrg: tut.fi
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Apr 2017 10:53:08.5800 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR02MB1074
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iMixsHMMBbKvRbVAU9xWgi2eTFA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 10:53:19 -0000

Hello,

On 12/04/17 07:04, Carsten Bormann wrote:
> On Apr 12, 2017, at 04:42, Mark Nottingham <mnot@mnot.net> wrote:
>> So, is COAP using WebSockets for browser access, or for firewall traversal? The paper below seems to indicate the latter, and so the original question remains.
> Can’t answer that for Gengyu, but the term “firewall” occurs in the CoAP over TCP abstract, not in the CoAP over WebSockets one.
>
> I continue to maintain that for CoAP over WebSockets the access to CoAP proxies from browsers is the motivating case.  (Yes, these could also be HTTP to CoAP cross-protocol proxies, but there are impedance mismatches here; e.g., for a browser application that wants to observe a CoAP resource.)
>
Carsten's right. The primary use case which motivated us to undertake 
the work were for browser access, and for sandboxed web applications 
that want to use CoAP-based communication to a end-point, but are 
restricted from using system-level APIs such as TCP or UDP socket 
libraries. Matthias (in a forked version of this message thread) also 
mentioned where we saw benefits in allowing CoAP over Websockets to 
reach constrained devices.

While the work was progressing however, we did become aware of minor use 
cases where using CoAP over Websockets can provide an advantage: 
Reaching constrained nodes residing in domains where end users may lack 
the authority to configure middleboxes to allow new services over 
TCP/UDP. This is commonplace in particularly restrictive and firewalled 
networks that otherwise allow traditional messaging, email and web-based 
services. However, I need to emphasise this is a minor use case.

Best regards,
Bill



From nobody Wed Apr 12 04:34:04 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECC98131630 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 04:34: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, RP_MATCHES_RCVD=-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 cFjr1Fdatc4q for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 04:33:55 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2829131660 for <ietf@ietf.org>; Wed, 12 Apr 2017 04:33:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3w31ym6RtZzMlmC; Wed, 12 Apr 2017 13:33:52 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssfYgnWR2356; Wed, 12 Apr 2017 13:33:51 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC24E1.dip0.t-ipconnect.de [93.236.36.225]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Wed, 12 Apr 2017 13:33:51 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <D38819F1-A43A-40B6-918C-25AFDE05A4C9@netapp.com>
Date: Wed, 12 Apr 2017 13:33:50 +0200
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7CE81EA-9316-441F-BD4A-3416C112CAC5@tik.ee.ethz.ch>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <787AE7BB302AE849A7480A190F8B933009E4B953@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <f99d9c97-53f9-bac1-7bd1-8effa3ff9732@cs.tcd.ie> <D38819F1-A43A-40B6-918C-25AFDE05A4C9@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-SZoAXm8CGK8yyaXhU9mgsNvCkU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 11:34:02 -0000

Hi Lars, hi all,

this document is not proposed for publication at this time. This thread =
involved out of some comments on draft-mm-wg-effect-encrypt which is =
currently under IESG reveiew.

Further, this document was discussed and presented in the tsv-area =
meeting at IETF-98. My summary is that there was good discussion about =
this document and not all comments were negative. I would even say that =
there is interest on further working on this document. However, this =
document is not part of any working group and as such it solely depends =
on the authors to incorporate comments and drive this forward. Further =
note that this document is in an early state and therefore is still work =
in process. Comments, feedback, and contributions are more than welcome, =
I believe. The comment that the document should be more neutral was =
already made during the presentation and was probably well-understood by =
the authors. Please also see my next mail as reply to another comments =
that were made in this thread regarding the intention of this draft.

Mirja


> Am 11.04.2017 um 22:17 schrieb Eggert, Lars <lars@netapp.com>:
>=20
> On 2017-4-11, at 11:26, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>> But regardless of whether or not there
>> is a desire for this document, in anything like it's current
>> form, I'd be one voice opposed to publication.
>=20
> +1
>=20
> I am surprised to see this even being proposed for publication, given =
the comments after the IETF-98 presentation.
>=20
> Lars


From nobody Wed Apr 12 04:52:10 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E51129423 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 04:52:08 -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, RP_MATCHES_RCVD=-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 iLoHB5MN--iN for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 04:52:06 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B439A127078 for <ietf@ietf.org>; Wed, 12 Apr 2017 04:52:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3w32Mm3mlVzMmpm; Wed, 12 Apr 2017 13:52:04 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QS3o_9jN3HZD; Wed, 12 Apr 2017 13:52:03 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC24E1.dip0.t-ipconnect.de [93.236.36.225]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Wed, 12 Apr 2017 13:52:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <20170411171831.GA23461@localhost>
Date: Wed, 12 Apr 2017 13:52:02 +0200
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C53D353-B20C-41B2-9916-41238B520D09@tik.ee.ethz.ch>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost>
To: Nico Williams <nico@cryptonector.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lqrtFWA_dvo6qmcTVLbzdmpjldY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 11:52:09 -0000

Hi Nico, hi Stephen, hi all,

replying to this mail because that seems to be the right point to =
comment on the intent of the draft (and maybe also why it was presented =
in tsv-area).

Yes, this draft could be phrased in a more neutral way, however, this =
draft is in an early state and the author received this feedback already =
in tsv-area. I=E2=80=99m sure they will incorporate this in the next =
version.

But more important to say is that the intent is not to describe the good =
and the bad or the pros and the cons. This would be a completely =
different document. The intent of this document is actually to describe =
the benefits in the sense of why do operator deploy those middleboxes. =
Deploying and operating middleboxes costs money (and induces complexity, =
as described below in this mail) but there are still perceived benefits =
for operators otherwise the would not go through the hassle. =
Understanding these benefits is the first step to have a discussion on =
how to replace current practices as performed by middleboxes today with =
either end-to-end schemes, or at least middleboxes that are less =
intrusive or maybe find a way to provide in-network services with user =
consensus, or whatever=E2=80=A6 This document can be seen as input from =
operators to the IETF community. Again, I agree that any language that =
indicates any request to the IETF community to support any of these =
current practices should be removed. But I also believe it=E2=80=99s =
easy to misinterpret the current text if that=E2=80=99s what you already =
have in mind when you read the doc. And again, this is work in progress =
and that is not the indention.

Further, regarding the points listed below on problems with =
middbleboxes. This would be a completely different document, which could =
be valuable as well. However, here the focus would be providing =
information to the operators and I really wouldn=E2=80=99t want to mix =
this up. Also I believe especially for such a document the current =
document could be good input as a basis to refer to when discussing =
specific problems of specific functions.=20

The more constructive next step I would like to see, where this document =
from my point of view also provides the basis for the needed input, is =
to talk about mechanisms that realize the same benefits in an encrypted =
world, hopefully with less middbleboxes, and then point the operators at =
these documents, rather then just saying: what you do is bad, please =
stop.

Mirja


> Am 11.04.2017 um 19:18 schrieb Nico Williams <nico@cryptonector.com>:
>=20
> On Tue, Apr 11, 2017 at 09:51:14AM +0100, Stephen Farrell wrote:
>> On 11/04/17 09:15, mohamed.boucadair@orange.com wrote:
>>>> I hope that the IETF never publishes
>>>> draft-dolson-plus-middlebox-benefits; it makes claims about the
>>>> benefits of specific solutions for different use cases with the
>>>> goal of justifying those solutions.
>>=20
>>> [Med] I'm afraid this is speculating about the intent of
>>> draft-dolson. Assured this is not the purpose of that document. The
>>> motivation is to document current practices without including any
>>> recommendation or claiming these solutions are superior to others.
>>=20
>> Just to note that I completely agree with Martin's interpretation
>> of the thrust of this draft and I totally fail to see how your
>> argument above can be justified given that draft title, abstract
>> and even filename (and also the content;-). When the abstract
>> says "This document summarizes benefits" then I cannot interpret
>> that as other than being intended to justify the uses described.
>>=20
>> A fairly thorough re-write to aim to describe the pros and cons
>> would be a different and more useful document. Similarly a draft
>=20
> Documenting the good, the bad, and the ugly, would be much better than
> documenting only the good.  Documenting only one half of the story =
seems
> to me like a bad idea on its face.
>=20
>> that strives to neutrally describe existing reality could maybe
>> be useful (*) but one that only describes middlebox friends with
>> "benefits" is not IMO beneficial ;-)
>=20
> Agreed.
>=20
> I can think of a number of problems with middle boxes:
>=20
> - scalability
>=20
>   Middle boxes may need to expend much more computational power in
>   order to do more than forward packets, and they need to do this for
>   as many extant packet flows as will fit on their pipes at full tilt.
>=20
>   Middle boxes may also have to be stateful, which quickly turns into =
a
>   morass.
>=20
> - security
>=20
>   Middle boxes can get intrusive and require sharing either more
>   information with the public at large, or more information with
>   "trusted" middle boxes, which in turn requires more complex key
>   management and more failure modes.
>=20
> - reliability
>=20
>   More failure modes (see security above).  More middle boxes to
>   inspect for diagnostics.  More middleboxes to fix.
>=20
> - extensibility
>=20
>   Want to extend the protocol?  You can't.  You'd have to upgrade all
>   the middle boxes first.  You can only get the extensibility that you
>   can foresee.  If you screw up the first time, the screw up will take
>   15 years to work out of the Internet in the best case, and in the
>   worst case you'll never get it out.
>=20
> I can probably add more later when I have more time for this thread.
>=20
> One could give a lot of advice for design of protocols with "friendly"
> middle boxes.  Merely saying "hey, they are good" is not enough.  We
> might want to revisit end-to-end protocol design as well (e.g., maybe
> ICMP isn't working so well; what can we do?).  Perhaps we can get some
> of the benefits of middle-box-aware protocols without the middle =
boxes.
> Suppose a secure middle-box quench protocol by which nodes under DDoS
> can enable DDoS counter-measures in upstream routers...  Suppose a
> generic, non-TCP congestion control capable but UDP-like transport =
with
> a reusable header prefix and ICMP-ish messages for QoS and congestion
> control...  I'm certain we can do more within the end-to-end model =
with
> minimal middle-box involvement (though never zero; we need at least
> packet forwarding middle boxes).
>=20
> IMO the IETF must not publish draft-dolson-plus-middlebox-benefits as =
it
> is today.
>=20
> Nico
> --=20
>=20


From nobody Wed Apr 12 06:26:28 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95E1C129AFA for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:26:20 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=fugue-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 AXHUuKFMBiQj for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:26:18 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 E3ABF129B1E for <ietf@ietf.org>; Wed, 12 Apr 2017 06:26:17 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id n46so21761570qta.2 for <ietf@ietf.org>; Wed, 12 Apr 2017 06:26:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=+aJSXLepHRGtuC8Vvp1tb8sNERJWnmAtfA0FIPfFe9o=; b=G+TkwYJ00FTNUkAGSSMda/cV/tKJmPJxZgQRzxNbiF9uZ53iuFymIV+U8+mqoTZf1G GZmMI8CRsGSSrIowXxuBnYDYUOtJM8u9fDjAKOPuL6QCOG1ct0XMg7yNDeYCWv6C4nYp AuBdViXrb+IUVIlHl3W6aftCIQ3D5GS+28fQY4T9vsjzwFoWkWacRCkUdKJvcKNVHNBa IlJctrgO7D1KnS9GvTRub8Ir8FRQkVixSzH+0sDU23MZ+cO4KFK/GGye/B1teCc6N5mo pcdt5NF5P31rn7mt/e5iEaun3TEljtQY0/RsBL2EJpR3j3T9hOeicSEFupxKlkQ/uWG9 gEXA==
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=+aJSXLepHRGtuC8Vvp1tb8sNERJWnmAtfA0FIPfFe9o=; b=hoF8JWGh+/ao3qLkdyJnmTJt7cpEO6AoV8AAjLlU4Gr89t/FESPbrAe5RfTdStru92 yTXjgtjoEupgZa/MXKwg6it1MvenckGaVX2fflfzcqgL6yk/pthjjFZIgMYal7P8bdDR +Jfr6f0azWUG60rb/wc7COOqAcgaUH2vqbJ0EBnpZ+UFcK+eMnufn8zXVvPygwTlaw20 JRoZZq6DbVxvlu1fvx/dQ3hsGtUwLdd3RYzb7U+TMTU2GHcNmCfY9TcJFp66aUsLCfOt UngqQ+aXoA0flPq5QFvlaTpTN43c8+5A2H0Y4ZUp3gt81lYnEmGJMrLu3c7Wb0Fz1aXN 6I0Q==
X-Gm-Message-State: AN3rC/7Vxr9Bogy8kD060QrnlTzpMHBK52x20g3Vc8Bz2qbrB9dXrX9O9SrlWZ2JxJrL5A==
X-Received: by 10.200.56.76 with SMTP id r12mr14099343qtb.138.1492003577087; Wed, 12 Apr 2017 06:26:17 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 19sm13401873qtv.38.2017.04.12.06.26.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 06:26:16 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E49CB26A-FAF7-4DB9-87AE-E65855B2474A"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAOC requesting input on (potential) meeting cities
Date: Wed, 12 Apr 2017 09:26:14 -0400
In-Reply-To: <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es>
Cc: IETF Discussion <ietf@ietf.org>, iaoc@ietf.org
To: jordi.palet@consulintel.es
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es> <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wfwH70S3zjvzCZesUL_5V9-mFiU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 13:26:21 -0000

--Apple-Mail=_E49CB26A-FAF7-4DB9-87AE-E65855B2474A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es> wrote:
> Do we need to ask again and again every day?

Has the IAOC met since the first time you asked?


--Apple-Mail=_E49CB26A-FAF7-4DB9-87AE-E65855B2474A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<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; -webkit-line-break: after-white-space;" =
class=3D"">On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ &lt;<a =
href=3D"mailto:jordi.palet@consulintel.es" =
class=3D"">jordi.palet@consulintel.es</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; 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; float: none; display: =
inline !important;" class=3D"">Do we need to ask again and again every =
day?</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
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;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Has the IAOC met since the first time you =
asked?</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_E49CB26A-FAF7-4DB9-87AE-E65855B2474A--


From nobody Wed Apr 12 06:29:33 2017
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D927129B30 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.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 0km-mPgW627d for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:29:30 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0087.outbound.protection.outlook.com [104.47.41.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2127129B40 for <ietf@ietf.org>; Wed, 12 Apr 2017 06:29:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ig+1oq/y0Is8V2h24DcGmsOm309J2slLg1J1MORMT/Q=; b=L99ebmoLi5t0CrYFnUFJPc/sEqdlaMpFgkqNsPY2jQX9anWSPK3y35gepZyBHkjsFmIssWRA3+hPNEY0JuxiC9aXW03nqmN471bGin370kNbojcdrIxrPY7Zu+SsqS59JSy/96r7mi1bioo8p1LsqC9dtBndn2Gq4e078EYQIPg=
Authentication-Results: tik.ee.ethz.ch; dkim=none (message not signed) header.d=none;tik.ee.ethz.ch; dmarc=none action=none header.from=isoc.org;
Received: from [172.21.122.66] (152.71.207.141) by CY1PR06MB2218.namprd06.prod.outlook.com (10.166.193.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Wed, 12 Apr 2017 13:29:25 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <0C53D353-B20C-41B2-9916-41238B520D09@tik.ee.ethz.ch>
Date: Wed, 12 Apr 2017 14:29:16 +0100
CC: Nico Williams <nico@cryptonector.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <8E8F6584-768A-4C4A-B30C-902C156033B1@isoc.org>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost> <0C53D353-B20C-41B2-9916-41238B520D09@tik.ee.ethz.ch>
To: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [152.71.207.141]
X-ClientProxiedBy: AM4PR0202CA0024.eurprd02.prod.outlook.com (10.171.80.34) To CY1PR06MB2218.namprd06.prod.outlook.com (10.166.193.153)
X-MS-Office365-Filtering-Correlation-Id: c10acf4f-0228-4b6a-af51-08d481a7f099
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:CY1PR06MB2218; 
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 3:OkPNMUkirX3g9Zvu9nCOx3hOIGlYa056vjAD8wJCEbW1cO2tW4eeHrRVBzyQ4A6GD+7+GbSBXZcldUufvZOHOjmwVvAJfeypBei/PYcrQ8W1x2znwD/iVWg16fWWAn8XbWiW24gfj72kss/Sk6m5jvn8adgYlOHRcLVKPC3CXwGbQeTp5uY2L309dFxHm/iiTTD5fQAyoV3tOhaytkNkq/GZVgat91SVHlxw+XIBMJh5IrGL5iJ3QT+fv535SJZyZw4/jicxKZ5PjLo2221K4wAAtK5QZBqgY49AcfDBYAWO0Cf7oPTuNtumBqzvt+FOZeuFeqiSyIUOLOLWQCGZTQ==; 25:a5j6dULq1nZrnARiqbh6Q9BYrkZvaov+h6Zl/EOPj9Me5w91hqpz2nhwlkX/r1iPZnz25Y5nQa1EvlRSXUK7cPRWQ0sOgtwDT5QJf4ERuEp479dGOupRedNVWF/Oo+/T2HtXjrEkcJwdkl6REqyl9Cz2xNhj/hCvrLOMnROh/FZuIyDYTgt8SZhf4n7LpEaAmw50E2+Spfs5wQSyhXS7Dn5Y/dgdIa4n4/qP9GG8GhCOQoRidQJLAK+ch4wV2qJgJJl934p7/Q3gG2PjV3iBOSQDmvJhPjaMi1XBX1B2DQdWiKGZmr2JnpR6X++bv6QK0Q2ASg9zCT/AOluUtfc+fmCK22z/VzTAKBp2hcbS+99AGU3B8oZeNHNOgcxGET8Le1P3DBrvAnSzgIUVFKf4UFkAjXbQhfZ1tz5c0h2+kIsDqE4PrHSnjORVLDbLLZ6WVryEgZyjNgW9aMrKltZbhQ==
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 31:l3C8pYyA4q0+3dAV4ZJWqVbfGd3znmeJaMOxE0f6dUtdj3gnHta+NVs4zGKjQXstg7YjUxzn+w/8/oontabZsWOvnNNoKE7JjVU8JmJlY378NJ1UtcfB3GsoAKwspxmTDDLXDNnPLIcnzD8xVrTtDxkQC6nQv4ww59v59RcHoaAFEgvFuV50c6a2gFFwmaBf0Vy0lU+GdW/ZxZOBIEw8qXFGvZd/5uNbgJs2idtvN2c=; 20:fKSLEX4IjcnLKSDou07ewh0ben44D9rzopbYnPGpQs8ESWa7I9fDJQNnGV8ENM5hoPNek3eJrpQvILTKdoEVUDjEaepmmjIiMYHOgDFl9hzrwHmk500tTf862PKiJBKXt4WQzmc4rf8lpUtFocYDiJjpfNRuywfDpEaMO+kfM31CAL/AP0oo7P/VQRqX1/OvOxvIyN7XCqZ0qAkllJyejURaXR3HXiiQR34OVhm+KePW3eqIesuXBzDoCwT+vEqgosH5uDwPqHxAIhOl3EkanJlhurQmJPRP6BeDJj+zXcIxWpEUnX0ONGUU1AcnXK1x114vVInrEWzL+5xD0IkSgbyZFy4LMP09yOYEGHRt5QfBMrq9QNaySsMV8YO8O4q88B7OlmMU64gjHyJyTF97105s/1fQOGniK7YwqRwK+/OTAu9aKsx8yX3AfuHqfbdyr3POVd6miFgYw/FQvOcP54ZXh5bAyy2W7t1W3u8+VJ9sLhvTr1uzo5qlqVWRMxgk
X-Microsoft-Antispam-PRVS: <CY1PR06MB221847636275261F6526ACB8A7030@CY1PR06MB2218.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123564025)(20161123560025)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(6072148); SRVR:CY1PR06MB2218; BCL:0; PCL:0; RULEID:; SRVR:CY1PR06MB2218; 
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 4:f0ZPpbZe+5WQgvBsqTZExPTVU4HEzbMHatrk2ZNTq8ltuPOAje+FxFJmLTXP0wi3OTOh7FmcmH+6Bp63tdVQAyL/Pwdz6/g9a4wadnTuVONeseCFasfbOTX7p1pZfmD+GbHUy/CQwKFJiOrFb3Ma04ssXjBS0z+VG+H6sZWxtgr/uJMlnNuBCKUjNsak29kaOy0KiJcHUGzfRH/QBsvK8/2/GRpuLbG4/wgaXefyyGdT6tq/WBlniCJ5X7n6Rgy+4IZKXbDz0mu3ahL4latMDzVueAFGBHGDfY5A8inOvAjNWJRPwYz9rjPIqhNhsh4I/HbKB4oGGL9jxh7l1scJEhysaZz5bgVH6RpE1DYuWqp5R6aC7UphnhQ2GVuxoWAVUC4sE6AEOvSCa/FqDNk3u1aXnRe8a1vTfc0ba4XXuWi3Cv+k4M/KYehSqrHTvfwj/16cZuNoTGyBK0TXVVsl+wMoinQkaqax739tIots95teOdRcN3eWzrAMcOd4q7UlP23Tt/fHTMlIrcGWqeQsMx4mxHw6FW1ltpdEjd/cK/9cVj8hLjTXDF+kHWjGisfRT3yuejq2t8Yihp64s8Z0Ca2Z7OSSN3f0ABKgYRmzSWWixFptDzlvPR3fRbdRVXST+P9PShlO1AhVquK1KZsWHiRKjqo/HKOxqJamIGSKemR56BU11rWthDSmEgWquEd3pJesgp6r7oBG2oLJt1XVGw==
X-Forefront-PRVS: 027578BB13
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(6049001)(39400400002)(39450400003)(39830400002)(39410400002)(24454002)(50466002)(82746002)(4326008)(23676002)(305945005)(230783001)(53936002)(54906002)(38730400002)(110136004)(6246003)(6486002)(77096006)(90366009)(189998001)(7736002)(2906002)(3846002)(6116002)(47776003)(6916009)(76176999)(50986999)(81166006)(86362001)(8746002)(229853002)(36756003)(2950100002)(66066001)(6666003)(50226002)(42186005)(5660300001)(8676002)(83716003)(25786009)(53546009)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR06MB2218; H:[172.21.122.66]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTFQUjA2TUIyMjE4OzIzOnFBeXZpRUdpUGdiTWRzZW84MWRIQko2VGth?= =?utf-8?B?ZUU0K25QbEFQRU5sdWJXREY0R3ArTkNEbmdHMmVTbHRSYkowcm1obzF4Vzlm?= =?utf-8?B?Q01XazNEWVZORGF6RGVaVUo3YlY5eFNJeXdSK1c5RTRORlByMU5MTFVMR2Zy?= =?utf-8?B?NERHckR6R1lIQng2bGFocXQzT1JRMkZlbjlndWhNQ3hhU01OY1lNQk4vNlkx?= =?utf-8?B?a3pWcmVZN0dTbFhzMTRVeWNHTEVvV2RvNXQzVUIvOGd5UTRuR3RvYlZreUVy?= =?utf-8?B?Zmh0SklFQy9nRjFwM3VVRTJzN3JlMWZoZGtNVEZEMWl6QlowRHRGU0h2NDJu?= =?utf-8?B?SVNRcWIwb0dHcjkvaFNuTXplZ2VOcEdoNzVSR0NUdVV6WnAzMERHUWhqRUdS?= =?utf-8?B?UFhSTzVJakhWTURXNGNEQWVZdmRVN1VMRTN4Qk9XNzFDMXRwZmtGVW14WGw1?= =?utf-8?B?UnJ1ZmtiaWxVTnpnOFpaNnRmZDltQ0t0NnpIWXhsMnV3ZkhYbFZ3QVh2V25O?= =?utf-8?B?b1ZOSHRLZFBOQWVVdG10Y3I0aWpmeThyOWM0cUJBYTRZeWhnTEF4V2c2YU9F?= =?utf-8?B?Z21hR3VnS1dtWG9TUjB0OVN5MEFxOGlOMU5uQjc5dXNURUZTYlA3Mm5HRCtM?= =?utf-8?B?UXFuVytyQkludlVDT3JDNk9BazBqM3ZabFVHVnMwRGlCK0pYODh6U2hhMlNG?= =?utf-8?B?eEpzY0l3STFJemJLRklhdDZBckhBbWxwdklnOUpGcjF6eUpoNVNtT044MCtG?= =?utf-8?B?bU1XOG9vU3ZZYjdXQk9FRVdUM2h0SzVlcHh0a09qVGdiNUVNVHZ3RjVGMTVH?= =?utf-8?B?bHNLMy9QTG9kVDk4QjhNOU9rTXM0WDZJU0pvMUtLOFJVS3EyWFRmQmtuWStB?= =?utf-8?B?MGl1Tzc2Y25OSUdJVHFKZ3kzZmw3M01FWmhBUmRnQnBkTTlnR1cyYTdSNDlh?= =?utf-8?B?YUJFRktWKytEQ1NwSVZxejAyZkNva24vSlE0ZnJGeVhLS1NJeVVvUEcxNlpm?= =?utf-8?B?VXhnL2swVU91aERGNWR1U3Q0VHUzcjZBUXpzMUZLY25FSzBvNzdQdTBzRU9a?= =?utf-8?B?azZRYVlVVExMZ1E3WlRaYXNodytBc25BR3lxeXdTN3lpMXBtRms2UUNDT2hw?= =?utf-8?B?RFlzeGFiU1RmcitSeWVORkF5RzNRMFJFUENSOXUwUkxOQjJDUHNXa3lrWk5U?= =?utf-8?B?R1IzWXVON2VxM2J2MnVhVVpQbjd5d2JtRVlHbjlXUHJJMjJtM1dXb0EvdHUv?= =?utf-8?B?ZFVzOS9MRVVPSEpnS0hqL0xEYlhzQUpTTlN5WlNrUUpIbzlMQWNIYloyUm9M?= =?utf-8?B?WXlrSTZZWHUybVJWRDJXaHg0S2lIOURyS2laNkthdjhFTTNMK1BuMmhIUDN2?= =?utf-8?B?VWV3TXkvRi9oSVJ5NnJGS2tuNVFYL1FNTjNKaFZYcDdJQzI5bFZScDI0ejNS?= =?utf-8?B?RDJFRjhaSHFNVDRMRk1vUFJhTGpuQ1hrY2Z6RzBzaDV0bzBIWGhzNUlrNnM4?= =?utf-8?B?bGlKb29WMFBabTFCQUJPdWRTakJrR2xENXlzemozaTk5RWZxbWNQL1ZxVjR2?= =?utf-8?B?ZTJwbDJTYlN6TWd1U1IzdWpSdWNuZUE9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 6:naRpdVOPu31sPR5+313e7fBtqg960g4nLJqVnZKcmcNcS2ec8agPYhkUYbrCvkXYLNQXKXAigdxZdQHp7629f6v6S7RFHiX7ngJzg+bBD07ZW6O5Gn1KK8gL0QtSUcWgb5sYLnPuFQTCFnzt7xNbjYfCUVG9ZRwypjp+Paex0rmU+o6McYyuCa075zF008WmPvaxgmSVoI7uSiBWocNiQjQmyJjmrggHQCiu+k/SKTAuji3YbjpZRqcff8Xf+LdDoTai/HeqMDANihrW1S0V8VEY1X8Dv489hOfDyJYQ/JYGr2iP5W3HOaLka+DgCTHV0mlm9+kZ9J/O+NTzdfENqDoywLZ4CCvPVRL3G1t7A9ptKyqiNPyI/M9pjCp4upCFn23Bz2jm/F1l7S6/0t06WOx2mPCkHzjwT2q2C53PcUte/+t0Oo93Le8fhbwBt12k2Kp0puffkY00PqRyWNOWJg==; 5:3AycvK92M4b4y823ZRfniyjU/4is/oOfmoDN5ygiwAdWCBL3YBFWMy7aRwde54SV3srO45fQQyTpyn7s2ednTi4A80TqrDg7R5UJ//GBq1c8RJbLGLxOe/4Z2ItElOhAwPyAXO4bnAe/mPO78nUJbw==; 24:g1esa4i2QMHdq6ubsuNXatAHeqAGCMAbeNkxS3o1/paSoqoBvwPd9KMbaYV4muZTdj6A8dLSR0hnjtpt/okZ3BV5voHB4zvoDeM26e45ThY=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 7:800RDsLlc3fHW4nT2BQfn29yaVLmq/arXWJORwzIwns1md42oxlz3EEsshkEdesERSWc6c9sglZ+MkzJed6FjLoOhXT3xr3V/ivN54ev4fTR9ugcE8blZ1Yjyj8O39Ea0RslLnDlv9h4EZ8CQXeBaimoVtEw9jcQyYjKSzMtTbWdYBIpSAIZArFJwj/um46k3H+L/mdJY0jvHvuK3dNScwlqQ4A1Uu6pgn04AzV1ch4K6Ekl/WzYqLPaaNnt7qwOvItldQvx2JIX+iyBOZLogXlSE6Ivd/SsbMllFCyxUihygpoyEKQ9cp/kTkP7kDM2dYfNZsGiijn7glVYCW1XKA==
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Apr 2017 13:29:25.0518 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR06MB2218
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gNpjzuzwH50c0yNYKh52hWzPqYs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 13:29:32 -0000

> On 12 Apr 2017, at 12:52, Mirja K=C3=BChlewind =
<mirja.kuehlewind@tik.ee.ethz.ch> wrote:
>=20
> describe the benefits in the sense of why do operator deploy those =
middleboxes.

Then don=E2=80=99t call them =E2=80=98benefits=E2=80=99 - they aren=E2=80=99=
t universally of benefit. Call them =E2=80=98motivations=E2=80=99 or =
something, but I think a lot of people are reacting to the use of the =
word =E2=80=98benefit=E2=80=99 as that tends to imply something that is =
necessarily good. Beauty is in the eye of the beholder.

Mat=


From nobody Wed Apr 12 06:39:38 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88DC129B1E for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:39:36 -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, RP_MATCHES_RCVD=-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 2-FKZc2k8ODE for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 06:39:34 -0700 (PDT)
Received: from virgo02.ee.ethz.ch (virgo02.ee.ethz.ch [129.132.72.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B141D1294B3 for <ietf@ietf.org>; Wed, 12 Apr 2017 06:39:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo02.ee.ethz.ch (Postfix) with ESMTP id 3w34ln2HRcz15LgJ; Wed, 12 Apr 2017 15:39:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo02.ee.ethz.ch
Received: from virgo02.ee.ethz.ch ([127.0.0.1]) by localhost (virgo02.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qyDx5dXKoHu; Wed, 12 Apr 2017 15:39:32 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC24E1.dip0.t-ipconnect.de [93.236.36.225]) by virgo02.ee.ethz.ch (Postfix) with ESMTPSA; Wed, 12 Apr 2017 15:39:32 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <8E8F6584-768A-4C4A-B30C-902C156033B1@isoc.org>
Date: Wed, 12 Apr 2017 15:39:31 +0200
Cc: Nico Williams <nico@cryptonector.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <37E486C6-62BC-4D55-84E2-750443ED496E@tik.ee.ethz.ch>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <20170411171831.GA23461@localhost> <0C53D353-B20C-41B2-9916-41238B520D09@tik.ee.ethz.ch> <8E8F6584-768A-4C4A-B30C-902C156033B1@isoc.org>
To: Matthew Ford <ford@isoc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pYMQyg8eSpYjSSP-4-Vsn_Ra7AE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 13:39:37 -0000

Sure, I also figured in the mean time that using a different word could =
help. However, from the operators perspective there has to be something =
good which provides an actual positive value for them, otherwise it =
would not justify the costs.=20

However, I strongly agree that "benefits provided to the Internet=E2=80=9C=
 is completely overstated. Maybe this should be "benefits provided to =
the network=E2=80=9C or "benefits for the network operator=E2=80=9C but =
I also do believe that the operators do this because they want to =
improve =E2=80=9Ethe Internet=E2=80=9C and doing something within their =
own network is the only handle the (currently) have. Or, as you say, we =
just don=E2=80=99t use the word benefit at all if that helps!

Mirja


> Am 12.04.2017 um 15:29 schrieb Matthew Ford <ford@isoc.org>:
>=20
>=20
>> On 12 Apr 2017, at 12:52, Mirja K=C3=BChlewind =
<mirja.kuehlewind@tik.ee.ethz.ch> wrote:
>>=20
>> describe the benefits in the sense of why do operator deploy those =
middleboxes.
>=20
> Then don=E2=80=99t call them =E2=80=98benefits=E2=80=99 - they =
aren=E2=80=99t universally of benefit. Call them =E2=80=98motivations=E2=80=
=99 or something, but I think a lot of people are reacting to the use of =
the word =E2=80=98benefit=E2=80=99 as that tends to imply something that =
is necessarily good. Beauty is in the eye of the beholder.
>=20
> Mat


From nobody Wed Apr 12 07:01:37 2017
Return-Path: <prvs=127550c264=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5DBD1294B5 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnAiPgp5WHZZ for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:35 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 054AE126BF0 for <ietf@ietf.org>; Wed, 12 Apr 2017 07:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492005687; x=1492610487; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=rysYTIWVNEFO35kmXKrYHV8Pa zcM08w3bA184T0h5qE=; b=E7dmFp6+o+adomv6JwkL7ZWHtFh6tuv2qt8BeQONR DnRrRlfnoZft3T7WohfffGXulxexfBIEUiv3sLY1xRzxjrh5jlo68IK1t0NQu6ch NIsR2o5qSt/8lu90nmEbZ+gItm1RtEvWQ2gs2q7+TzwC67FiVXdrZi64o4S5TKFM zI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=KSGY/RgSr/1LnAqv/BtYDrCyiCcACTwbuaju8KAfY2EcSa1/EapsqeMjGYC3 8daHQqo0k6jaRACd+jOhlBhOb6kl1AByU6Yc/R4EDWDa7Ux63Ji92Ft83 v2zwwh0iuW7DyRP85SinAlaXFgnmBZIgAa6tTEF/6Y79OrZ1aSVpNc=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Apr 2017 16:01:26 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Apr 2017 16:01:25 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005407089.msg for <ietf@ietf.org>; Wed, 12 Apr 2017 16:01:25 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170412:md50005407089::lcXDAYyjNbm37Ut0:00001/D3
X-Return-Path: prvs=127550c264=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Apr 2017 16:01:23 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
Message-ID: <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es> <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es> <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
In-Reply-To: <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mThBjp-gBKTE1xOQVWuqczHzCnw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 14:01:37 -0000

So, you mean they don=E2=80=99t use email?

Sounds surprising to me, despite for sure they had some time in Chicago to =
decide about what can be said to the community about the SF meeting. If the=
y haven=E2=80=99t considered that, I guess we need an IAOC with more focus =
on what is the most relevant and important topic right now for the communit=
y.

By the way, it seems that they haven=E2=80=99t met anyway since August 2015=
, as they promised me to respond to one of my emails regarding some spam/em=
ail bouncing issues and the way we are managing so, and I=E2=80=99ve been w=
aiting since them. Really nice and respectful way to support the community.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Ted Lemon <mellon@fugue.com>
Responder a: <mellon@fugue.com>
Fecha: mi=C3=A9rcoles, 12 de abril de 2017, 15:26
Para: <jordi.palet@consulintel.es>
CC: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ <jordi.palet@consulin=
tel.es> wrote:
    Do we need to ask again and again every day?
   =20
   =20
   =20
   =20
   =20
    Has the IAOC met since the first time you asked?
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr 12 07:01:59 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6664D129AB3 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.574
X-Spam-Level: 
X-Spam-Status: No, score=-1.574 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, HTTP_ESCAPED_HOST=1.125, RCVD_IN_DNSWL_LOW=-0.7, 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 8PW65muSS48o for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:56 -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 A6CBA1294C5 for <ietf@ietf.org>; Wed, 12 Apr 2017 07:01:55 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id o81so88400102wmb.1 for <ietf@ietf.org>; Wed, 12 Apr 2017 07:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=z/rHEwUKeLE/lD+y2RI9tEAZ3rW6Kv6g0bWlcbwrzek=; b=HcZSEA/DdQxprVtU4QJNT1Ft3UDRRjRMspKFRUeCvSRtXNWzhL++iEx5AguWJarxI5 YgUJ2bypjnqfF9lOfQWJdhgcFMJhhSaXC7lIBvGStb+1qAeOMyJJdaTYZYbwHM4U3ZZh GTRIbbs+MYGjA5E7U7K69cKpnDCKkq96cQHCLkcvP04RgHaRyDh8ugNK/RxbKII9AQ5c GQxIZROOfGB5L1+kkJbu4CpOuPK6XyNuYIP8m4qUweqIqr1SNF95aUuq7Gj7YYhF7ztb wtv/in721JzHKA5wwwSAnPMwxvpAwD13M9Juymblm0KykuCYsj8cqxxL0TvjFHxiVLW0 L6JQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=z/rHEwUKeLE/lD+y2RI9tEAZ3rW6Kv6g0bWlcbwrzek=; b=htJkjJOos2Iw2/iozZHqacxGOtj/fV2D5RExHP7KymDOnAfeItWjRJJWr5c8EKd62T XKejf8TtyClUjjtUy+CbJqK1N6g0wwZ00ZdmDoNH8LHZPmxDjd+A8KN2s8gu6AtHYUMF 7Qe1ZfweJr3MTnRnPs/fEE4j1qOMc5XYANMkolPAnT5qCoarv/0Bl7CrtORF6pkNZyDn eQUgCo+6M4ghpcjPFUfrxai1vH4UEk6jMnFgZGIJZPSagFiQg8NFZszBOFV/orsofKLw YN+ZaA/ZoycqgAHbLPvkRyAjuRDVRYXROIPBogjg5n3yDkW2GWkfDdyVkr2OT2fJi10M UckQ==
X-Gm-Message-State: AN3rC/4H+J137MtvNDlnxfzVJXJQC9OXR51+LyAHL3wX9F/DspeqJHSq 2sKH55qAbbuUDg==
X-Received: by 10.28.157.84 with SMTP id g81mr15472830wme.120.1492005714067; Wed, 12 Apr 2017 07:01:54 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id g63sm6735432wme.11.2017.04.12.07.01.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 07:01:53 -0700 (PDT)
Subject: Fwd: Re: [RTG-DIR] extremely rapid reviews/comments on "Effects of Encryption" (draft-mm-wg-effect-encrypt)
References: <2b643b0e-9e73-f8dd-51d1-b6c8fec53a54@gmail.com>
To: IETF Discussion <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Forwarded-Message-Id: <2b643b0e-9e73-f8dd-51d1-b6c8fec53a54@gmail.com>
Message-ID: <36b217b6-7986-d4e0-e4d6-2b538372f118@gmail.com>
Date: Wed, 12 Apr 2017 15:01:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <2b643b0e-9e73-f8dd-51d1-b6c8fec53a54@gmail.com>
Content-Type: multipart/alternative; boundary="------------8B5EF3ED2CB89EADF16C1313"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ilsmH2qRCqjHldiV8vUdvpC_IPs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 14:01:57 -0000

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


Alia asked the RTG directorate for there views on 
draft-mm-wg-effect-encrypt. 
<%20https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/>

For the record, here is my reply:

I only have time to scan read this before tomorrow, but I think Alexey 
Melnikov's comment summarises what I gleaned from the document so far: 
"This document is not perfect, but I found it to be generally useful".

This is a subject that we need a more open discussion about in the IETF. 
You would think from the vocal IETF position that the situation was a 
clear cut: monitoring is bad therefore encryption is good. What this 
document is trying to demonstrate is that there are pluses and minuses 
to encryption, just as there are are pluses and minuses to traffic 
monitoring. This document therefore  attempts to moves us to a more 
balanced discussion of the problem, and as such it makes a valuable 
contribution to the design of the Internet.

If at the end of there is no IESG consensus to publish this in the IETF 
stream, I think it should be taken to the Independent stream the purpose 
of which is to provide a platform to articulate well thought out 
technical views that are contra to the mainstream position.

- Stewart



--------------8B5EF3ED2CB89EADF16C1313
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 bgcolor="#FFFFFF" text="#000000">
    <br>
    Alia asked the RTG directorate for there views on <a
      moz-do-not-send="true"
      href="%20https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/">draft-mm-wg-effect-encrypt.</a><br>
    <br>
    For the record, here is my reply:<br>
    <br>
    I only have time to scan read this before tomorrow, but I think
    Alexey Melnikov's comment summarises what I gleaned from the
    document so far: "This document is not perfect, but I found it to be
    generally useful".<br>
    <br>
    This is a subject that we need a more open discussion about in the
    IETF. You would think from the vocal IETF position that the
    situation was a clear cut: monitoring is bad therefore encryption is
    good. What this document is trying to demonstrate is that there are
    pluses and minuses to encryption, just as there are are pluses and
    minuses to traffic monitoring. This document therefore  attempts to
    moves us to a more balanced discussion of the problem, and as such
    it makes a valuable contribution to the design of the Internet.<br>
    <br>
    If at the end of there is no IESG consensus to publish this in the
    IETF stream, I think it should be taken to the Independent stream
    the purpose of which is to provide a platform to articulate well
    thought out technical views that are contra to the mainstream
    position. <br>
    <br>
    - Stewart<br>
    <br>
    <br>
  </body>
</html>

--------------8B5EF3ED2CB89EADF16C1313--


From nobody Wed Apr 12 07:31:08 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD84129BB5 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:31:06 -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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 VmTg4xap0GMl for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:31:04 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A54BC129BC8 for <ietf@ietf.org>; Wed, 12 Apr 2017 07:30:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A5EF82055F; Wed, 12 Apr 2017 10:55:38 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 85B82636E0; Wed, 12 Apr 2017 10:30:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Loa Andersson <loa@pi.nu>
cc: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 12 Apr 2017 10:30:55 -0400
Message-ID: <10890.1492007455@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/huiFPhuTP_JFEArL72mu91HwLmU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 14:31:07 -0000

--=-=-=
Content-Type: text/plain


I've done remote meetings going back to the days of when we had to
make mbone work first. (it worked once!!!)
I've probably done a dozen or so remote meetings.

Loa Andersson <loa@pi.nu> wrote:
    > Let me first say that I very much appreciate the effort made by
    > e.g. the meetecho people. The experience of listening to a meeting on
    > meetecho and sitting in the room listening is very close. All the time
    > until someone that sits in the middle of the room don't care to go the
    > mike to make a comment, but just shout it out. When this happens you
    > just don't lose the comment, but you also lose much of the context for
    > the continued discussion.

Right, so this is why it's better for everyone to be remote.

    > It quite often happens (it has happened to me) that someone notify the
    > chairs that "there is someone wanting to say something on the
    > meetecho", only when that happens that particular discussion is already
    > "taken to the list".

Yes, bad chair discipline.

    > But an IETF meeting is so much more than the moderate number of hours
    > you spend in meeting rooms, if you participate remotely you miss what
    > is probably the most important aspect of an IETF F2F - the 10-15
    > corridor meetings you have each day.

I totally agree.

    > I'd say cancel SFO and move to place where we all have an equal chance
    > to attend, even if you have made a business trip to Iran or somewhere
    > else in the Middle East, and where we don't have to give out passwords
    > to e.g. laptops that may contain business critical information.

If we can do that, I agree. Lets do that.

If we can't outright cancel, but can renegotiate significantly, my suggestion
stands.  Move the meeting and make SFO a US left-coast remote hub.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljuOh8ACgkQgItw+93Q
3WUmBAgArNBpL3iLLEDePmL5DtApAjCU2RcltbiET5koawT4IkJlwZ+qWVnQj3eA
zYv/C68meaZ+bAGmxBBALsxqoRuGrMpE5e+tjwL1qClDL765CO0phrzRRCYiJ8yk
P+U+PukzqArdB2VcXZ1GQrG4Sf+HOgfLE/jI8Rq+QPf12ghcBrK3NwcQaalpRr2t
l+LYYll43sKb7HvnY5BzTJx/MHzdQ2pgYyG/l+s3dzdeNtUEvunHOMRQ3LxSmnmI
EmB3vcZO7HfccC/V2lTzeZYc1HUZu8gzMsCGGZ10bxuZXvp/rOnqAUsTJLT7rB/Z
XKFcVGPe41tsUNSpqcf3waHeTWPzXA==
=xJxd
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 12 09:04:10 2017
Return-Path: <jayb@oz.mt.att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BB4131777; Wed, 12 Apr 2017 09:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8] 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 Sjwcv-MBwOi1; Wed, 12 Apr 2017 09:04:07 -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 A8235131774; Wed, 12 Apr 2017 09:04:07 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v3CDjBQW037672; Wed, 12 Apr 2017 09:46:46 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 29sn9mgdqs-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Apr 2017 09:46:45 -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 v3CDkiTx000328; Wed, 12 Apr 2017 09:46:45 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkcGT032579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Apr 2017 09:46:38 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi131.aldc.att.com (RSA Interceptor); Wed, 12 Apr 2017 13:46:23 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkNjx017287; Wed, 12 Apr 2017 09:46:23 -0400
Received: from oz.mt.att.com (oz.mt.att.com [135.16.165.23]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkJXW016509; Wed, 12 Apr 2017 09:46:19 -0400
Received: by oz.mt.att.com (Postfix, from userid 1000) id A2161A40E33; Wed, 12 Apr 2017 09:46:18 -0400 (EDT)
X-Mailer: emacs 24.3.1 (via feedmail 11-beta-1 I); VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22766.12199.587325.838948@oz.mt.att.com>
Date: Wed, 12 Apr 2017 09:46:15 -0400
From: Jay Borkenhagen <jayb@braeburn.org>
To: ietf@ietf.org
Cc: grow-chairs@ietf.org, grow@ietf.org, warren@kumari.net, draft-ietf-grow-large-communities-usage@ietf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [GROW] Last Call: <draft-ietf-grow-large-communities-usage-05.txt> (Use of BGP Large Communities) to Informational RFC
In-Reply-To: <149158518251.11127.8008659284325510446.idtracker@ietfa.amsl.com>
References: <149158518251.11127.8008659284325510446.idtracker@ietfa.amsl.com>
Reply-To: Jay Borkenhagen <jayb@braeburn.org>
X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3  D198 7DED 6648 2308 D3C0 
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-12_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=13 phishscore=0 bulkscore=0 spamscore=0 clxscore=1034 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704120115
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9N1I0PSze58YBZsJhdjEWOdKc2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:04:09 -0000

On 07-April-2017, The IESG writes:
 > 
 > The IESG has received a request from the Global Routing Operations WG
 > (grow) to consider the following document:
 > - 'Use of BGP Large Communities'
 >   <draft-ietf-grow-large-communities-usage-05.txt> as Informational RFC
 > 
 > The IESG plans to make a decision in the next few weeks, and solicits
 > final comments on this action. Please send substantive comments to the
 > ietf@ietf.org mailing lists by 2017-04-21. Exceptionally, comments may be
 > sent to iesg@ietf.org instead. In either case, please retain the
 > beginning of the Subject line to allow automated sorting.
 > 

The following comment may not measure up to being "substantive", but
those in authority can decide.


I have always liked the way the definition of the "BGP Communities
Attribute" spec in RFC1997 was paired with RFC1998's "An Application
of the BGP Community Attribute in Multi-home Routing": the former for
the "bits on the wire" spec, the latter for "how operators can use it."

draft-ietf-grow-large-communities-usage-05.txt's Introduction section
currently reads as follows:

   BGP Large Communities [RFC8092] provide a mechanism to signal
   opaque information between Autonomous Systems (ASs).  This document
   presents examples of how operators might utilize BGP Large
   Communities to achieve various goals.  This document draws on the
   experience of operator communities such as NANOG [1] and NLNOG [2].

I would like to suggest this minor change:

   BGP Large Communities [RFC8092] provide a mechanism to signal
   opaque information between Autonomous Systems (ASs).  In very much
   the same way that [RFC1998] provides a concrete real-world
   application for [RFC1997]'s communities, this document presents
   examples of how operators might utilize BGP Large Communities to
   achieve various goals.  This document draws on the experience of
   operator communities such as NANOG [1] and NLNOG [2].

Thanks for considering, and very belated thanks to Tony and Enke for
RFC1998. 

						Jay B.



From nobody Wed Apr 12 09:13:39 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2A3C12EAAF; Wed, 12 Apr 2017 09:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.926
X-Spam-Level: 
X-Spam-Status: No, score=-3.926 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-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=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 hFmq7DuwPkaE; Wed, 12 Apr 2017 09:13:34 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065043.outbound.protection.outlook.com [40.92.65.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC7712EACE; Wed, 12 Apr 2017 09:13:33 -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; bh=jgIazikMqqkhElG34zcd8Sxm0fozyKcWqsWFbYN78/c=; b=LQ5FnH8vZdaCTcgZas0OUQx+BIQE5Zq96Cfh/uyXU5FeX48fG0w/p4kR6OIP+0CpjB+DzLK+BhibCt4LiWyDOnlN7dYIuWyMBR4vIkKUJFrugJVh6Y4YuxCUciO88y1rk9/3E04Uwzts2regNCV1RTwz7KR//axMECSt4+inxChiO3uos5Vjt4U/p/EUTE/49r0XNO49Nkg2HsDEn4/SyXaCS0jznaVmB3e5N/T8heGK+TRdPFc+SHPvG4VTZqqdmuFCXvI7AaSv6e4ZnLCzY0hjMNK4e9YP1RKK7U3+JqaabYE/GiJsQjPEkSBmOIJ2y7gA4GAl1lb8t0rsDPL2eQ==
Received: from HE1EUR01FT019.eop-EUR01.prod.protection.outlook.com (10.152.0.52) by HE1EUR01HT201.eop-EUR01.prod.protection.outlook.com (10.152.1.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Wed, 12 Apr 2017 16:13:30 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.0.53) by HE1EUR01FT019.mail.protection.outlook.com (10.152.0.179) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Wed, 12 Apr 2017 16:13:30 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.025; Wed, 12 Apr 2017 16:13:30 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf-draft-submission@ietf.org" <ietf-draft-submission@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Khaled Routing Protocol (KRP) ID Submission.
Thread-Topic: Khaled Routing Protocol (KRP) ID Submission.
Thread-Index: AdKzp1CRFd0eQahqTpyMvf6uY+qORA==
Date: Wed, 12 Apr 2017 16:13:30 +0000
Message-ID: <AM4PR0401MB2241724888D753F586B1B949BD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:F03F171CD655D3B3BF9295BA3DF5B9B058332B69BEF050C47FC41D733BEED7A6; UpperCasedChecksum:C5C6E7EAE824AF999E7B931E988A16C2A9D5E27A31471CEE07BCB9EEAD886801; SizeAsReceived:7949; Count:40
x-tmn: [fAVBrEPfWTGEX5NCBCB9ujIFKPBFewrQ]
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT201; 5:mDbNMFp9d4Rbui1QzCxSUbV5kxiYsoIfvEtrv1yeI1NoHpAgldn2JPylSHO9U7saEEY6RONfGK2MUYlodeFv0sZ6MsLAOGYwm7NEkjhDDuIYQfdCI+qxxz9omzPUONgQDKISDmXxpVSKRNI8TiXqiQ==; 24:SkWttYVgGELNpqpWuE/oZBbWr+SF4Yh1NwdIz5a/0gtZP9T9LB/D8sfM+p/QUlcAb8hUo9eZ1lV9QNsK/ghPw290sUE0amj/XROPDIrZ628=; 7:S4cD/vSqAmVli82NqYTFVwv4Y/HbV2wUta0hSK0Fu/Gvsa/uITKKAfW4J8sPasYZyoY8qb91CGo8mLb2oRK8KkKCAlTKOeSe9Iwq0R6gAPOhTtMWT42XBE0lmJqTOl3jPl+0qTuaTh53B+vQ4VVHtD2g14uvbJDmhGbB2Vt92LxlOoYr/opmcUsRvd3FLwXgS3NSjDG9U3V4y2tB8umYN7a4H+dRaDCX0MjJ6HQXgFZLabWxKbA1c6Z6t7M2M1QwFicuB0wIYmDUr6mrwEXbwERvnSiVU15OBfPTQYGJo2E3uwDkHBu0dS8Y0lrPVdxO
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT201; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 7886c1fa-e028-44f8-7946-08d481bedc5a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:HE1EUR01HT201; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT201; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT201; 
x-forefront-prvs: 027578BB13
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_004_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2017 16:13:30.5537 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT201
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ky49M8vNuH8nQYV1wvhlv7V4cFY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:13:38 -0000

--_004_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_
Content-Type: multipart/alternative;
	boundary="_000_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_"

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

Hi Jasmine,

Please upload the 2nd ID attached.

Looking for an advanced discussion to take this ID forward.

Best Regards,

Khaled Omar

--_000_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_
Content-Type: text/html; charset="us-ascii"
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" 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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Jasmine,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please upload the 2<sup>nd</sup> ID attached.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Looking for an advanced discussion to take this ID f=
orward.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled Omar <o:p></o:p></p>
</div>
</body>
</html>

--_000_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_--

--_004_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_
Content-Type: text/plain; name="draft-omar-intarea-krp-00.txt"
Content-Description: draft-omar-intarea-krp-00.txt
Content-Disposition: attachment; filename="draft-omar-intarea-krp-00.txt";
	size=24284; creation-date="Sun, 26 Mar 2017 15:32:07 GMT";
	modification-date="Sat, 08 Apr 2017 14:47:20 GMT"
Content-Transfer-Encoding: base64

//5kAHIAYQBmAHQALQBvAG0AYQByAC0AaQBuAHQAYQByAGUAYQAtAGsAcgBwAC0AMAAwACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEsA
aABhAGwAZQBkACAATwBtAGEAcgANAAoASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAVABoAGUAIABSAG8AYQBkACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgAA0ACgBJAG4AdABlAG4AZABlAGQAIABzAHQAYQB0AHUAcwA6ACAAUwB0AGEAbgBkAGEAcgBk
ACAAVAByAGEAYwBrAA0ACgBFAHgAcABpAHIAZQBzADoAIABTAGUAcAB0AGUAbQBiAGUAcgAgADMA
MAAsACAAMgAwADEANwAJAAkAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAE0AYQByAGMAaAAg
ADMAMAAsACAAMgAwADEANwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAANAAoADQAKAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABLAEgAQQBMAEUARAAgAFIAbwB1AHQA
aQBuAGcAIABQAHIAbwB0AG8AYwBvAGwAIAAoAEsAUgBQACkADQAKACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABTAHAAZQBjAGkAZgBpAGMA
YQB0AGkAbwBuAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAZAByAGEAZgB0AC0AbwBtAGEAcgAtAGkAbgB0AGEAcgBlAGEALQBrAHIAcAAtADAAMAANAAoA
DQAKAFMAdABhAHQAdQBzACAAbwBmACAAdABoAGkAcwAgAE0AZQBtAG8ADQAKAA0ACgAgACAAIABU
AGgAaQBzACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAaQBzACAAcwB1AGIAbQBpAHQA
dABlAGQAIABpAG4AIABmAHUAbABsACAAYwBvAG4AZgBvAHIAbQBhAG4AYwBlACAAdwBpAHQAaAAg
AHQAaABlACAAcAByAG8AdgBpAHMAaQBvAG4AcwANAAoAIAAgACAAbwBmACAAQgBDAFAAIAA3ADgA
IABhAG4AZAAgAEIAQwBQACAANwA5AC4ADQAKAA0ACgAgACAAIABJAG4AdABlAHIAbgBlAHQALQBE
AHIAYQBmAHQAcwAgAGEAcgBlACAAdwBvAHIAawBpAG4AZwAgAGQAbwBjAHUAbQBlAG4AdABzACAA
bwBmACAAdABoAGUAIABJAG4AdABlAHIAbgBlAHQAIABFAG4AZwBpAG4AZQBlAHIAaQBuAGcAIABU
AGEAcwBrAA0ACgAgACAAIABGAG8AcgBjAGUAIAAoAEkARQBUAEYAKQAuACAATgBvAHQAZQAgAHQA
aABhAHQAIABvAHQAaABlAHIAIABnAHIAbwB1AHAAcwAgAG0AYQB5ACAAYQBsAHMAbwAgAGQAaQBz
AHQAcgBpAGIAdQB0AGUAIAB3AG8AcgBrAGkAbgBnACAAZABvAGMAdQBtAGUAbgB0AHMADQAKACAA
IAAgAGEAcwAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzAC4AIABUAGgAZQAgAGwAaQBz
AHQAIABvAGYAIABjAHUAcgByAGUAbgB0ACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0AHMA
IABpAHMAIABhAHQADQAKACAAIAAgAGgAdAB0AHAAOgAvAC8AZABhAHQAYQB0AHIAYQBjAGsAZQBy
AC4AaQBlAHQAZgAuAG8AcgBnAC8AZAByAGEAZgB0AHMALwBjAHUAcgByAGUAbgB0AC8ALgANAAoA
DQAKACAAIAAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzACAAYQByAGUAIABkAHIAYQBm
AHQAIABkAG8AYwB1AG0AZQBuAHQAcwAgAHYAYQBsAGkAZAAgAGYAbwByACAAYQAgAG0AYQB4AGkA
bQB1AG0AIABvAGYAIABzAGkAeAAgAG0AbwBuAHQAaABzACAAYQBuAGQADQAKACAAIAAgAG0AYQB5
ACAAYgBlACAAdQBwAGQAYQB0AGUAZAAsACAAcgBlAHAAbABhAGMAZQBkACwAIABvAHIAIABvAGIA
cwBvAGwAZQB0AGUAZAAgAGIAeQAgAG8AdABoAGUAcgAgAGQAbwBjAHUAbQBlAG4AdABzACAAYQB0
ACAAYQBuAHkAIAB0AGkAbQBlAC4ADQAKACAAIAAgAEkAdAAgAGkAcwAgAGkAbgBhAHAAcAByAG8A
cAByAGkAYQB0AGUAIAB0AG8AIAB1AHMAZQAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABz
ACAAYQBzACAAcgBlAGYAZQByAGUAbgBjAGUAIABtAGEAdABlAHIAaQBhAGwAIABvAHIAIAB0AG8A
IABjAGkAdABlAA0ACgAgACAAIAB0AGgAZQBtACAAbwB0AGgAZQByACAAdABoAGEAbgAgAGEAcwAg
ACIAdwBvAHIAawAgAGkAbgAgAHAAcgBvAGcAcgBlAHMAcwAuACIADQAKAA0ACgAgACAAIABUAGgA
aQBzACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAdwBpAGwAbAAgAGUAeABwAGkAcgBl
ACAAbwBuACAAUwBlAHAAdABlAG0AYgBlAHIAIAAzADAALAAgADIAMAAxADcALgANAAoADQAKAA0A
CgANAAoAQwBvAHAAeQByAGkAZwBoAHQAIABOAG8AdABpAGMAZQANAAoADQAKACAAIAAgAEMAbwBw
AHkAcgBpAGcAaAB0ACAAKABjACkAIAAyADAAMQA2ACAASQBFAFQARgAgAFQAcgB1AHMAdAAgAGEA
bgBkACAAdABoAGUAIABwAGUAcgBzAG8AbgBzACAAaQBkAGUAbgB0AGkAZgBpAGUAZAAgAGEAcwAg
AHQAaABlACAAZABvAGMAdQBtAGUAbgB0AA0ACgAgACAAIABhAHUAdABoAG8AcgBzAC4AIABBAGwA
bAAgAHIAaQBnAGgAdABzACAAcgBlAHMAZQByAHYAZQBkAC4AIAANAAoADQAKACAAIAAgAFQAaABp
AHMAIABkAG8AYwB1AG0AZQBuAHQAIABpAHMAIABzAHUAYgBqAGUAYwB0ACAAdABvACAAQgBDAFAA
IAA3ADgAIABhAG4AZAAgAHQAaABlACAASQBFAFQARgAgAFQAcgB1AHMAdAAnAHMAIABMAGUAZwBh
AGwAIABQAHIAbwB2AGkAcwBpAG8AbgBzAA0ACgAgACAAIABSAGUAbABhAHQAaQBuAGcAIAB0AG8A
IABJAEUAVABGACAARABvAGMAdQBtAGUAbgB0AHMAIAAoAGgAdAB0AHAAOgAvAC8AdAByAHUAcwB0
AGUAZQAuAGkAZQB0AGYALgBvAHIAZwAvAGwAaQBjAGUAbgBzAGUALQBpAG4AZgBvACkAIABpAG4A
IABlAGYAZgBlAGMAdAANAAoAIAAgACAAbwBuACAAdABoAGUAIABkAGEAdABlACAAbwBmACAAcAB1
AGIAbABpAGMAYQB0AGkAbwBuACAAbwBmACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAuACAA
UABsAGUAYQBzAGUAIAByAGUAdgBpAGUAdwAgAHQAaABlAHMAZQAgAGQAbwBjAHUAbQBlAG4AdABz
AA0ACgAgACAAIABjAGEAcgBlAGYAdQBsAGwAeQAsACAAYQBzACAAdABoAGUAeQAgAGQAZQBzAGMA
cgBpAGIAZQAgAHkAbwB1AHIAIAByAGkAZwBoAHQAcwAgAGEAbgBkACAAcgBlAHMAdAByAGkAYwB0
AGkAbwBuAHMAIAB3AGkAdABoACAAcgBlAHMAcABlAGMAdAAgAHQAbwAgAHQAaABpAHMADQAKACAA
IAAgAGQAbwBjAHUAbQBlAG4AdAAuACAAQwBvAGQAZQAgAEMAbwBtAHAAbwBuAGUAbgB0AHMAIABl
AHgAdAByAGEAYwB0AGUAZAAgAGYAcgBvAG0AIAB0AGgAaQBzACAAZABvAGMAdQBtAGUAbgB0ACAA
bQB1AHMAdAAgAGkAbgBjAGwAdQBkAGUADQAKACAAIAAgAFMAaQBtAHAAbABpAGYAaQBlAGQAIABC
AFMARAAgAEwAaQBjAGUAbgBzAGUAIAB0AGUAeAB0ACAAYQBzACAAZABlAHMAYwByAGkAYgBlAGQA
IABpAG4AIABTAGUAYwB0AGkAbwBuACAANAAuAGUAIABvAGYAIAB0AGgAZQAgAFQAcgB1AHMAdAAg
AEwAZQBnAGEAbAANAAoAIAAgACAAUAByAG8AdgBpAHMAaQBvAG4AcwAgAGEAbgBkACAAYQByAGUA
IABwAHIAbwB2AGkAZABlAGQAIAB3AGkAdABoAG8AdQB0ACAAdwBhAHIAcgBhAG4AdAB5ACAAYQBz
ACAAZABlAHMAYwByAGkAYgBlAGQAIABpAG4AIAB0AGgAZQAgAFMAaQBtAHAAbABpAGYAaQBlAGQA
DQAKACAAIAAgAEIAUwBEACAATABpAGMAZQBuAHMAZQAuAA0ACgANAAoADQAKAEEAYgBzAHQAcgBh
AGMAdAANAAoADQAKACAAIAAgAFQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQAIABzAHAAZQBjAGkA
ZgBpAGUAcwAgAEsASABBAEwARQBEACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAg
ACgASwBSAFAAKQAuAA0ACgANAAoADQAKAA0ACgANAAoAVABhAGIAbABlACAAbwBmACAAQwBvAG4A
dABlAG4AdABzAA0ACgANAAoAIAAgACAAMQAuACAASQBuAHQAcgBvAGQAdQBjAHQAaQBvAG4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADEADQAKACAAIAAgADIALgAg
AEsASABBAEwARQBEACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgASwBSAFAA
KQAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAxAA0ACgAgACAAIAAzAC4AIABLAFIAUAAgAEYAbwByAHcAYQByAGQAaQBuAGcA
IABNAGUAYwBoAGEAbgBpAHMAbQAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4AMgANAAoAIAAgACAAMwAuACAA
UwBlAGMAdQByAGkAdAB5ACAAQwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBzAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuADMADQAKACAAIAAgADQALgAgAEEAYwBrAG4AbwB3AGwAZQBkAGcAbQBlAG4AdABz
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAzAA0ACgAgACAAIAA1AC4AIABB
AHUAdABoAG8AcgAgAEEAZABkAHIAZQBzAHMALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4AMwANAAoAIAAgACAANgAuACAAUgBlAGYAZQByAGUAbgBjAGUAcwAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADMADQAKACAAIAAgADcALgAgAEYA
dQBsAGwAIABDAG8AcAB5AHIAaQBnAGgAdAAgAFMAdABhAHQAZQBtAGUAbgB0AC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAzAA0ACgANAAoADQAKAA0ACgANAAoASwBoAGEAbABlAGQAIABPAG0AYQByACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEAZwBlACAAMQBdAA0ACgANAAoAUgBG
AEMAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEsASABBAEwARQBEACAAUgBvAHUAdABpAG4A
ZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgASwBSAFAAKQAgACAAIAAgACAAIAAgACAATQBhAHIAYwBo
ACAAMwAwACwAIAAyADAAMQA3AA0ACgANAAoADQAKADEALgAgACAASQBuAHQAcgBvAGQAdQBjAHQA
aQBvAG4ADQAKAA0ACgANAAoAIAAgACAAIAAtACAASwBIAEEATABFAEQAIABSAG8AdQB0AGkAbgBn
ACAAUAByAG8AdABvAGMAbwBsACAAKABLAFIAUAApACAAaQBzACAAYQBuACAARQB4AHQAZQByAGkA
bwByACAARwBhAHQAZQB3AGEAeQAgAFAAcgBvAHQAbwBjAG8AbAAgACgARQBHAFAAKQAgAHQAaABh
AHQADQAKACAAIAAgACAAIAAgAGkAbgB0AHIAbwBkAHUAYwBlAHMAIABhACAAbgBlAHcAIAB3AGEA
eQAgAG8AZgAgAHIAbwB1AHQAaQBuAGcAIABJAFAAIABwAGEAYwBrAGUAdABzACAAZgByAG8AbQAg
AHQAaABlACAAcwBvAHUAcgBjAGUAIAB0AG8AIAB0AGgAZQAgAGQAZQBzAHQAaQBuAGEAdABpAG8A
bgANAAoAIAAgACAAIAAgACAAdABoAHIAbwB1AGcAaAAgAGQAaQBmAGYAZQByAGUAbgB0ACAAQQB1
AHQAbwBuAG8AbQBvAHUAcwAgAFMAeQBzAHQAZQBtAHMAIAAoAEEAUwBzACkALgANAAoAIAAgACAA
IAAtACAAVABoAGUAIABJAG4AdABlAHIAbgBlAHQAIAB3AGkAbABsACAAYgBlACAAcwB1AGIAZABp
AHYAaQBkAGUAZAAgAGkAbgB0AG8AIABsAG8AZwBpAGMAYQBsACAAcgBlAGcAaQBvAG4AcwAgAG8A
cgAgAGIAeQAgAHQAaABlACAAcABoAHkAcwBpAGMAYQBsAA0ACgAgACAAIAAgACAAIABsAG8AYwBh
AHQAaQBvAG4AIABvAGYAIABjAG8AbgB0AGkAbgBlAG4AdABzAC4ADQAKACAAIAAgACAALQAgAFQA
aABlACAAcgBvAHUAdABpAG4AZwAgAHAAcgBvAGMAZQBzAHMAIAB0AGgAYQB0ACAASwBIAEEATABF
AEQAIABSAG8AdQB0AGkAbgBnACAAUAByAG8AdABvAGMAbwBsACAAKABLAFIAUAApACAAdQBzAGUA
cwAgAGkAcwAgAGIAYQBzAGUAZAAgAG8AbgAgAHQAaABlAA0ACgAgACAAIAAgACAAIABLAFIAUAAg
AFIAZQBnAGkAbwBuACAATgB1AG0AYgBlAHIAIAAoAFIATgApACwAIAB0AGgAZQAgAEsAUgBQACAA
QQB1AHQAbwBuAG8AbQBvAHUAcwAgAFMAeQBzAHQAZQBtACAATgB1AG0AYgBlAHIAIAAoAEEAUwBO
ACkALAAgAEIAZQBzAHQAIABQAGEAdABoACAAQQBsAGcAbwByAGkAdABoAG0ADQAKACAAIAAgACAA
IAAgACgAQQBTACAAUABhAHQAaAApACAAYQBuAGQAIAB0AGgAZQAgAGUAZgBmAG8AcgB0AHMAIABt
AGEAZABlACAAYgB5ACAAdABoAGUAIABJAEcAUAAgAHcAaQB0AGgAaQBuACAAZQBhAGMAaAAgAEEA
UwAuAA0ACgAgACAAIAAgAC0AIABUAGgAZQAgAG0AYQBqAG8AcgAgAGQAaQBmAGYAZQByAGUAbgBj
AGUAIABiAGUAdAB3AGUAZQBuACAASwBSAFAAIABhAG4AZAAgAEIARwBQACAAaQBzACAAdABoAGEA
dAAgAEsAUgBQACAAZABvAGUAcwAgAG4AbwB0ACAAdQBzAGUAcwAgAGEAIABsAGEAcgBnAGUAIAB0
AGEAYgBsAGUADQAKACAAIAAgACAAIAAgAHcAaQB0AGgAIABoAHUAbgBkAHIAZQBkAHMAIABvAGYA
IAB0AGgAbwB1AHMAYQBuAGQAcwAgAG8AZgAgAGUAbgB0AHIAaQBlAHMAIAAoAEIARwBQACAAVABh
AGIAbABlACkAIABzAHQAbwByAGUAZAAgAHcAaQB0AGgAaQBuACAAZQBhAGMAaAAgAEkAbgB0AGUA
cgBuAGUAdAAgAHIAbwB1AHQAZQByACwADQAKACAAIAAgACAAIAAgAGkAbgBzAHQAZQBhAGQAIABv
AGYAIAB0AGgAYQB0ACwAIABpAHQAIAB1AHMAZQBzACAAYQAgAHMAbQBhAHIAdABlAHIAIAB3AGEA
eQAgAG8AZgAgAHIAbwB1AHQAaQBuAGcAIABiAGEAcwBlAGQAIABvAG4AIAB0AGgAZQAgAEsAUgBQ
ACAAUgBOACwAIAAgAEsAUgBQACAAQQBTAE4ADQAKACAAIAAgACAAIAAgAHMAdABvAHIAZQBkACAA
dwBpAHQAaABpAG4AIABlAGEAYwBoACAASQBQACAAYQBkAGQAcgBlAHMAcwAsACAAQgBlAHMAdAAg
AFAAYQB0AGgAIABBAGwAZwBvAHIAaQB0AGgAbQAgACgAQQBTACAAUABhAHQAaAApACAAYQBuAGQA
IAB0AGgAZQAgAGUAZgBmAG8AcgB0AHMAIABhAGwAcgBlAGEAZAB5AA0ACgAgACAAIAAgACAAIABi
AGUAaQBuAGcAIABkAG8AbgBlACAAYgB5ACAAZQBhAGMAaAAgAEkARwBQACAAdwBpAHQAaABpAG4A
IABhAG4AIABBAFMALgANAAoADQAKAA0ACgANAAoADQAKADIALgAgAEsASABBAEwARQBEACAAUgBv
AHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgASwBSAFAAKQANAAoADQAKAA0ACgAgACAA
IAAgAC0AIABLAFIAUAAgAHUAcwBlAHMAIABuAGUAdwAgAHQAZQByAG0AcwAgAHQAaABhAHQAIABj
AGEAbgAgAGIAZQAgAGQAZQBmAGkAbgBlAGQAIABhAHMAIABmAG8AbABsAG8AdwBzADoADQAKAA0A
CgANAAoAIAAgACAAIAAqACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUAcgAgACgAUgBOACkAOgAN
AAoADQAKACAAIAAgAC0AIAAzAC0AYgBpAHQAcwAgAHIAZQBwAHIAZQBzAGUAbgB0AGUAZAAgAGkA
bgAgAG8AbgBlACAAZABlAGMAaQBtAGEAbAAgAGQAaQBnAGkAdAAuAA0ACgAgACAAIAAtACAAOAAg
AFIATgBzACAAYwBhAG4AIABiAGUAIAB1AHMAZQBkACAAdABvACAAcgBlAHAAcgBlAHMAZQBuAHQA
IAA4ACAAZABpAGYAZgBlAHIAZQBuAHQAIABSAGUAZwBpAG8AbgBzACAAKABmAHIAbwBtACAAMAAg
AHQAbwAgADcAKQAuAA0ACgAgACAAIAAtACAAVABoAGUAIAAxAHMAdAAgAGgAZQB4ACAAZABpAGcA
aQB0ACAAbwBmACAAdABoAGUAIAAxAHMAdAAgAGcAcgBvAHUAcAAgAG8AZgAgAGEAbgAgAEkAUAB2
ADYAIABhAGQAZAByAGUAcwBzACAAZABlAHQAZQByAG0AaQBuAGUAcwAgAG8AbgAgAHcAaABpAGMA
aAAgAFIATgAgAHQAaABpAHMAIABJAFAAdgA2AA0ACgAgACAAIAAgACAAYQBkAGQAcgBlAHMAcwAg
AGkAcwAgAGwAbwBjAGEAdABlAGQALgAuAA0ACgAgACAAIAAtACAAVABoAGUAIAAxAHMAdAAgAG8A
YwB0AGUAdAAgAG8AZgAgAGEAbgAgAEkAUAB2ADQAIABhAGQAZAByAGUAcwBzACAAZABlAHQAZQBy
AG0AaQBuAGUAcwAgAG8AbgAgAHcAaABpAGMAaAAgAFIATgAgAHQAaABpAHMAIABJAFAAdgA0ACAA
YQBkAGQAcgBlAHMAcwAgAGkAcwAgAGwAbwBjAGEAdABlAGQALgANAAoAIAAgACAALQAgAFQAaABl
ACAAdABhAGIAbABlACAAdABoAGEAdAAgAHcAaQBsAGwAIABiAGUAIAB1AHMAZQBkACAAbABpAHMA
dABpAG4AZwAgAHQAaABlACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUAcgAgACgAUgBOACkALAAg
AHQAaABlACAAYwBvAHIAcgBlAHMAcABvAG4AZABpAG4AZwAgAEkAUAB2ADYADQAKACAAIAAgACAA
IAAxAHMAdAAgAGgAZQB4ACAAZABpAGcAaQB0AHMAIABhAG4AZAAgAHQAaABlACAASQBQAHYANAAg
ADEAcwB0ACAAbwBjAHQAZQB0ACAAcABvAG8AbAAgAG8AZgAgAG4AdQBtAGIAZQByAHMAIABpAHMA
IABjAGEAbABsAGUAZAAgAHQAaABlACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUAcgAgAFQAYQBi
AGwAZQANAAoAIAAgACAAIAAgACgAUgBOAFQAKQAgAGEAbgBkACAAaQBzACAAcwB0AG8AcgBlAGQA
IABvAG4AIABlAHYAZQByAHkAIABLAFIAUAAgAHIAbwB1AHQAZQByACAAYQBuAGQAIABpAHMAIABh
AHMAIABmAG8AbABsAG8AdwBzADoADQAKAA0ACgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgAFIAZQBnAGkAbwBuACAATgB1
AG0AYgBlAHIAIAAgACoAIAAgADEAcwB0ACAASQBQAHYANgAgAGgAZQB4ACAAZABpAGcAaQB0AHMA
IAAgACoAIAAgADEAcwB0ACAASQBQAHYANAAgAE8AYwB0AGUAdABzACAAKgAgAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACAAIAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACoA
IAAgACAAIAAgACAAIAAgADEAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAxACAALQAg
ADYAIAAtACAAQgAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgAEEAUgBJAE4AIABQAG8AbwBsACAA
IAAgACAAKgAgACAAIAAgACAAIAAgACAADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAIAAgAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAMgAgACAA
IAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgADIAIAAtACAANwAgAC0AIABDACAAIAAgACAAIAAg
ACAAKgAgACAAIABSAEkAUABFACAATgBDAEMAIABQAG8AbwBsACAAIAAqACAAIAAgACAAIAAgACAA
IAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAgACAADQAKACAAIAAgACAAIAAg
ACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAzACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAA
IAAgACAAMwAgAC0AIAA4ACAALQAgAEQAIAAgACAAIAAgACAAIAAqACAAIAAgAEEARgBSAEkATgBJ
AEMAIABQAG8AbwBsACAAIAAgACoAIAAgACAAIAAgACAAIAAgAA0ACgAgACAAIAAgACAAIAAgACAA
IAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACAAIAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAg
ACAAIAAgADQAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAA0ACAALQAgADkAIAAtACAA
RQAgACAAIAAgACAAIAAgACoAIAAgACAAIABBAFAATgBJAEMAIABQAG8AbwBsACAAIAAgACAAKgAg
ACAAIAAgACAAIAAgACAADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAIAAgAA0A
CgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAANQAgACAAIAAgACAAIAAg
ACAAKgAgACAAIAAgACAAIAAgADUAIAAtACAAQQAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAA
IABMAEEAQwBOAEkAQwAgAFAAbwBvAGwAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAANAAoAIAAg
ACAAIAAgACAAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoADQAKAA0ACgANAAoAIAAgACAAIAAqACAA
UgBlAGcAaQBvAG4AYQBsACAAQgBvAGEAcgBkAGUAcgAgAFIAbwB1AHQAZQByACAAKABSAEIAUgAp
ACAAPQA9AD4AIABBACAAcgBvAHUAdABlAHIAIABpAG4AIABhACAAcgBlAGcAaQBvAG4AIAB0AGgA
YQB0ACAAaABhAHMADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAYQB0ACAAbABlAGEAcwB0ACAA
bwBuAGUAIABpAG4AdABlAHIAZgBhAGMAZQAgAGMAbwBuAG4AZQBjAHQAZQBkAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAHQAbwAgAGEAIAByAG8AdQB0AGUAcgAnAHMAIABpAG4AdABlAHIAZgBh
AGMAZQAgAGkAbgAgAGEAbgBvAHQAaABlAHIADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAcgBl
AGcAaQBvAG4ALgANAAoADQAKAA0ACgAgACAAIAAgACoAIABSAGUAZwBpAG8AbgBhAGwAIABSAG8A
dQB0AGUAcgAgACgAUgBSACkAIAA9AD0APgAgAEEAIAByAG8AdQB0AGUAcgAgAGkAbgAgAGEAIABy
AGUAZwBpAG8AbgAgAGEAbgBkACAAaABhAHMAIABhAGwAbAAgAGkAbgB0AGUAcgBmAGEAYwBlAHMA
DQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAYwBvAG4AbgBlAGMAdABlAGQAIAB0AG8AIABvAHQAaABlAHIAIAByAG8AdQB0AGUA
cgBzACAAaQBuACAAdABoAGUAIABzAGEAbQBlAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAHIAZQBnAGkAbwBuAC4ADQAKAA0A
CgANAAoAIAAgACAALQAgAEUAYQBjAGgAIABSAEIAUgAgAGEAbgBkACAAUgBSACAAaQBzACAAYwBv
AG4AZgBpAGcAdQByAGUAZAAgAHcAaQB0AGgAIABhACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUA
cgAgACgAUgBOACkAIAB0AGgAYQB0ACAAaQBkAGUAbgB0AGkAZgBpAGUAcwANAAoAIAAgACAAIAAg
AGkAbgAgAHcAaABpAGMAaAAgAHIAZQBnAGkAbwBuACAAdABoAGEAdAAgAHIAbwB1AHQAZQByACAA
aQBzACAAbABvAGMAYQB0AGUAZAAuACAADQAKACAAIAAgAC0AIABBAGwAbAAgAFIAQgBSAHMAIABh
AG4AZAAgAFIAUgBzACAAaQBuAHQAZQByAGYAYQBjAGUAcwAgAHcAaQBsAGwAIABiAGUAIABhAHMA
cwBpAGcAbgBlAGQAIABiAHkAIABkAGUAZgBhAHUAbAB0ACAAdABvACAAdABoAGUAIABjAG8AbgBm
AGkAZwB1AHIAZQBkAA0ACgAgACAAIAAgACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUAcgAgACgA
UgBOACkALgANAAoAIAAgACAALQAgAFQAaABlACAAdAB3AG8AIABjAG8AbgBuAGUAYwB0AGUAZAAg
AEsAUgBQACAAcgBvAHUAdABlAHIAcwAgAGUAeABjAGgAYQBuAGcAZQAgAHQAaABlAGkAcgAgAFIA
TgBzADoAIAANAAoADQAKACAAIAAgACAAIAAgACAAMQApACAASQBmACAAdABoAGUAeQAgAGEAcgBl
ACAAdABoAGUAIABzAGEAbQBlACwAIAB0AGgAZQAgAHQAdwBvACAASwBSAFAAIAByAG8AdQB0AGUA
cgBzACAAYQByAGUAIABSAFIAcwAuAA0ACgAgACAAIAAgACAAIAAgADIAKQAgAEkAZgAgAHQAaABl
AHkAIABhAHIAZQAgAGQAaQBmAGYAZQByAGUAbgB0ACwAIAB0AGgAZQAgAHQAdwBvACAASwBSAFAA
IAByAG8AdQB0AGUAcgBzACAAYQByAGUAIABSAEIAUgBzAC4ADQAKAA0ACgAgACAAIAANAAoADQAK
AA0ACgANAAoADQAKAA0ACgBLAGgAYQBsAGUAZAAgAE8AbQBhAHIAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIABJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIABbAFAAYQBnAGUAIAAyAF0ADQAKAA0ACgBSAEYAQwAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIABLAEgAQQBMAEUARAAgAFIAbwB1AHQAaQBuAGcAIABQAHIAbwB0
AG8AYwBvAGwAIAAoAEsAUgBQACkAIAAgACAAIAAgACAAIAAgAE0AYQByAGMAaAAgADMAMAAsACAA
MgAwADEANwANAAoADQAKAA0ACgANAAoADQAKADMALgAgAEsAUgBQACAARgBvAHIAdwBhAHIAZABp
AG4AZwAgAE0AZQBjAGgAYQBuAGkAcwBtAA0ACgANAAoADQAKAA0ACgAgACAAIAAtACAASwBSAFAA
IAByAGUAcQB1AGkAcgBlAHMAIAB0AGgAZQAgAEkAUAB2ADYAIABhAG4AZAAgAEkAUAB2ADQAIABh
AHMAcwBpAGcAbgBtAGUAbgB0ACAAbQB1AHMAdAAgAGYAbwBsAGwAbwB3ACAAdABoAGUAcwBlACAA
cgBlAHEAdQBpAHIAZQBtAGUAbgB0AHMAOgANAAoADQAKACAAIAAgACAAIABhACkAIABUAGgAZQAg
ADEAcwB0ACAAdAB3AG8AIABnAHIAbwB1AHAAcwAgAG8AZgAgAGEAbgAgAEkAUAB2ADYAIABhAGQA
ZAByAGUAcwBzACAAaQBzACAAcgBlAHAAcgBlAHMAZQBuAHQAZQBkACAAYQBzACAAZgBvAGwAbABv
AHcAcwA6AA0ACgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB5AHkA
eQB5AHwAeQB5AHkAeQB8AHkAeQB5AHkAfAB5AHkAeQB5ADoAeQB5AHkAeQB8AHkAeQB5AHkAfAB5
AHkAeQB5AHwAeQB5AHkAeQANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABZAFkAWQBZADoA
WQBZAFkAWQANAAoADQAKACAAIAAgACAAIAAgACAAdwBoAGUAcgBlACAAWQBZAFkAWQA6AFkAWQBZ
AFkAIABoAGUAeAAgAGQAaQBnAGkAdABzACAAcgBlAHAAcgBlAHMAZQBuAHQAcwAgAHQAaABlACAA
SwBSAFAAIABBAHUAdABvAG4AbwBtAG8AdQBzACAAUwB5AHMAdABlAG0AIABOAHUAbQBiAGUAcgAg
ACgAQQBTAE4AKQAuAA0ACgANAAoADQAKAA0ACgAgACAAIAAgACAAYgApACAAVABoAGUAIAAxAHMA
dAAgAHQAdwBvACAAbwBjAHQAZQB0AHMAIABvAGYAIABhAG4AIABJAFAAdgA0ACAAYQBkAGQAcgBl
AHMAcwAgAGkAcwAgAHIAZQBwAHIAZQBzAGUAbgB0AGUAZAAgAGEAcwAgAGYAbwBsAGwAbwB3AHMA
OgANAAoADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAB5AHkAeQB5AHkAeQB5AHkALgB5AHkAeQB5AHkAeQB5AHkADQAKAA0ACgAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAWQBZAC4AWQBZAA0ACgANAAoAIAAgACAAIAAgACAAdwBoAGUAcgBlACAAWQBZAC4A
WQBZACAAaABlAHgAIABkAGkAZwBpAHQAcwAgAHIAZQBwAHIAZQBzAGUAbgB0AHMAIAB0AGgAZQAg
AEsAUgBQACAAQQB1AHQAbwBuAG8AbQBvAHUAcwAgAFMAeQBzAHQAZQBtACAATgB1AG0AYgBlAHIA
IAAoAEEAUwBOACkALgANAAoADQAKACAAIAAgACAAIABOAG8AdABlADoALQAgAC0AIABUAGgAZQAg
AEsAUgBQACAAQQBTAE4AIABtAHUAcwB0ACAAYgBlACAAdQBuAGkAcQB1AGUAIABmAG8AcgAgAGUA
dgBlAHIAeQAgAEEAUwAuAA0ACgANAAoADQAKAA0ACgAgACAAIAAgAC0AIABUAGgAZQByAGUAIABh
AHIAZQAgADMAIAB0AHkAcABlAHMAIABvAGYAIAB0AGEAYgBsAGUAcwAgAGEAbgBkACAAMQAgAFIA
QgBSACAAbQBlAHMAcwBhAGcAZQAgAHQAaABhAHQAIAB0AGgAZQAgAEsAUgBQACAAdQBzAGUAcwAg
AGYAbwByACAAZgBvAHIAdwBhAHIAZABpAG4AZwAgAGEAIABwAGEAYwBrAGUAdAA6AA0ACgANAAoA
DQAKACAAIAAgACAAIABhACkAIABLAFIAUAAgAHIAbwB1AHQAZQByACAAUgBlAGcAaQBvAG4AYQBs
ACAAVABhAGIAbABlACAAKABSAFQAKQA6AA0ACgANAAoADQAKACAAIAAgACAAIAAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqAA0ACgAgACAAIAAgACAAKgAgAEwAbwBjAGEAbAAgAFIATgAgACoAIABS
AGUAbQBvAHQAZQAgAFIATgAgACoAIABUAHIAYQBmAGYAaQBjACAAQwBsAGEAcwBzACAAKgAgAEwA
bwBjAGEAbAAgAEsAUgBQACAAQQBTAE4AIAAqACAAUgBCAFIAIABLAFIAUAAgAEEAUwBOACAAKgAg
AA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAgACAADQAKACAAIAAgACAA
IAAqACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACoA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqAA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgANAAoADQAKAA0ACgAgACAAIAAgAC0AIABFAGEAYwBoACAAUgBCAFIAIABhAG4A
ZAAgAFIAUgAgAGMAcgBlAGEAdABlAHMAIABpAHQAcwAgAG8AdwBuACAAUgBlAGcAaQBvAG4AYQBs
ACAAVABhAGIAbABlACAAKABSAFQAKQAuAA0ACgAgACAAIAAgAC0AIABUAGgAZQAgAFIAZQBnAGkA
bwBuAGEAbAAgAFQAYQBiAGwAZQAgACgAUgBUACkAIABpAHMAIABhAHMAIABmAG8AbABsAG8AdwBz
ADoADQAKAA0ACgANAAoAIAAgACAAIAAgACAATgBvAHQAZQA6AC0AIAAtACAARQBhAGMAaAAgAFIA
QgBSACAAYgByAG8AYQBkAGMAYQBzAHQAcwAgAHQAaABlACAAZgB1AGwAbAAgAGwAZQBhAHIAbgBl
AGQAIABSAFQAIABmAGkAcgBzAHQALAAgAHQAaABlAG4AIAB0AGgAZQAgAG4AZQB3ACAAbABlAGEA
cgBuAGUAZAAgAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABSAGUAbQBvAHQAZQAg
AFIATgAuAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAC0AIABFAGEAYwBoACAAUgBCAFIA
IABiAHIAbwBhAGQAYwBhAHMAdABzACAAdABoAGUAIABSAFQAIABvAHUAdAAgAG8AZgAgAGEAbABs
ACAAaQB0AHMAIABpAG4AdABlAHIAZgBhAGMAZQBzACAAZQB4AGMAZQBwAHQAIAB0AGgAZQAgAGkA
bgB0AGUAcgBmAGEAYwBlAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB3AGgAZQBy
AGUAIABpAHQAIABsAGUAYQByAG4AZQBkACAAYQBiAG8AdQB0ACAAdABoAGUAIAByAGUAbQBvAHQA
ZQAgAFIATgAuAA0ACgANAAoADQAKAA0ACgAgACAAIAAgAGIAKQAgAEsAUgBQACAAcgBvAHUAdABl
AHIAIABGAG8AcgB3AGEAcgBkAGkAbgBnACAAVABhAGIAbABlACAAKABGAFQAKQA6AA0ACgANAAoA
DQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoAIAAg
ACAAIAAgACoAIAAgACAATABvAGMAYQBsACAAIAAqACAAIAAgAFIAZQBtAG8AdABlACAAIAAqACAA
IAAgACAAUgBCAFIAIAAgACAAIAAqACAAIAAgACAAQgBlAHMAdAAgACAAIAAqACAAIAAgAE8AdQB0
AHAAdQB0ACAAIAAgACoAIAAgACAATgBlAHgAdAAtAGgAbwBwACAAIAAqAA0ACgAgACAAIAAgACAA
KgAgACAASwBSAFAAIABBAFMATgAgACoAIAAgAEsAUgBQACAAQQBTAE4AIAAgACoAIAAgAEsAUgBQ
ACAAQQBTAE4AIAAgACoAIAAgAEEAUwAgAFAAYQB0AGgAIAAgACoAIAAgAEkAbgB0AGUAcgBmAGEA
YwBlACAAKgAgACAASQBQACAAQQBkAGQAcgBlAHMAcwAgACoADQAKACAAIAAgACAAIAAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAgACAADQAKACAAIAAgACAAIAAqACAAIAAgACAA
IAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAg
ACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAKgANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqAA0ACgANAAoADQAKAA0ACgAgACAAIAAgAGMAKQAgAEsAUgBQACAA
cgBvAHUAdABlAHIAIABJAEcAUAAgAFIAbwB1AHQAaQBuAGcAIABUAGEAYgBsAGUAIAAoAEkAUgBU
ACkAOgANAAoADQAKAA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoAIAAgACAAIAAgACoAIABQAHIA
ZQBmAGkAeAAgACgAUwB1AGIAbgBlAHQAKQAgACoAIABNAGUAdAByAGkAYwAgACoAIABPAHUAdABw
AHUAdAAgAEkAbgB0AGUAcgBmAGEAYwBlACAAKgAgAE4AZQB4AHQALQBoAG8AcAAgAEkAUAAgACoA
IAANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAIAANAAoAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAg
ACAADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqAA0ACgAgACAAIAANAAoADQAKAA0ACgAgACAAIAAtACAA
UgBCAFIAIABBAGQAdgBlAHIAdABpAHMAZQBkACAATQBlAHMAcwBhAGcAZQAgAEkAbgBmAG8AcgBt
AGEAdABpAG8AbgAgAGYAbwByACAAdABoAGUAIABsAG8AYwBhAGwAIAByAGUAZwBpAG8AbgAgAGkA
cwAgAGEAcwAgAGYAbwBsAGwAbwB3AHMAOgANAAoADQAKAA0ACgAgACAAIAAgACAAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoAIAAgACAAIAAg
ACoAIABSAGUAbQBvAHQAZQAgAFIATgAgACoAIABNAGUAdAByAGkAYwAgACoAIABPAHUAdABwAHUA
dAAgAEkAbgB0AGUAcgBmAGEAYwBlACAAKgAgAE4AZQB4AHQALQBoAG8AcAAgAEkAUAAgACoAIAAN
AAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAIAANAAoAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAA
IAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAADQAKACAAIAAgACAAIAAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqAA0ACgANAAoADQAKAA0A
CgAgACAAIAAtACAAUgBCAFIAIABBAGQAdgBlAHIAdABpAHMAZQBkACAATQBlAHMAcwBhAGcAZQAg
AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAgAGYAbwByACAAdABoAGUAIAByAGUAbQBvAHQAZQAgAHIA
ZQBnAGkAbwBuACAAaQBzACAAYQBzACAAZgBvAGwAbABvAHcAcwA6AA0ACgANAAoADQAKACAAIAAg
ACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoADQAKACAAIAAgACAAIAAqACAATABvAGMAYQBsACAAKgAgAFIAZQBtAG8AdABlACAA
KgAgAFQAcgBhAGYAZgBpAGMAIAAqACAATgB1AG0AYgBlAHIAIAAgACoAIABUAGkAbQBlAC0AbwB1
AHQAIAAqACAAIAAgAFIAQgBSACAAIAAgACoADQAKACAAIAAgACAAIAAqACAAIABSAE4AIAAgACAA
KgAgACAAIABSAE4AIAAgACAAKgAgACAAQwBsAGEAcwBzACAAIAAqACAAbwBmACAASABvAHAAcwAg
ACoAIAAgAFYAYQBsAHUAZQAgACAAIAAqACAASwBSAFAAIABBAFMATgAgACoADQAKACAAIAAgACAA
IAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAIAANAAoAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAg
ACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAANAAoAIAAgACAAIAAgACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAN
AAoADQAKAA0ACgANAAoAIAAgACAAIABkACkAIABSAEIAUgAgAFIAZQBnAGkAbwBuAGEAbAAgAFQA
YQBiAGwAZQAgACgAUgBSAFQAKQA6AA0ACgANAAoADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoAIAAgACAAIAAgACoAIABM
AG8AYwBhAGwAIABSAE4AIAAqACAAUgBlAG0AbwB0AGUAIABSAE4AIAAqACAAVAByAGEAZgBmAGkA
YwAgAEMAbABhAHMAcwAgACoAIABSAEIAUgAgAEsAUgBQACAAQQBTAE4AIAAqACAADQAKACAAIAAg
ACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAg
ACAADQAKACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAA
IAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAKgANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqAA0ACgANAAoADQAKAA0ACgANAAoADQAKAEsAaABhAGwAZQBkACAA
TwBtAGEAcgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBh
AGYAdAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFsAUABhAGcAZQAgADMA
XQANAAoADQAKAFIARgBDACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABLAEgAQQBMAEUARAAg
AFIAbwB1AHQAaQBuAGcAIABQAHIAbwB0AG8AYwBvAGwAIAAoAEsAUgBQACkAIAAgACAAIAAgACAA
IAAgAE0AYQByAGMAaAAgADMAMAAsACAAMgAwADEANwANAAoARQB4AHAAaQByAGUAcwA6ACAAMwAw
AC0AOQAtADIAMAAxADcADQAKAA0ACgANAAoADQAKAFMAZQBjAHUAcgBpAHQAeQAgAEMAbwBuAHMA
aQBkAGUAcgBhAHQAaQBvAG4AcwANAAoADQAKAA0ACgANAAoAQQBjAGsAbgBvAHcAbABlAGQAZwBt
AGUAbgB0AHMADQAKAA0ACgANAAoADQAKAEEAdQB0AGgAbwByACAAQQBkAGQAcgBlAHMAcwANAAoA
DQAKACAAIAAgAEsAaABhAGwAZQBkACAATwBtAGEAcgAgAEkAYgByAGEAaABpAG0AIABPAG0AYQBy
AA0ACgAgACAAIABUAGgAZQAgAFIAbwBhAGQADQAKACAAIAAgADYAdABoACAAbwBmACAATwBjAHQA
bwBiAGUAcgAgAEMAaQB0AHkALAAgAEcAaQB6AGEADQAKACAAIAAgAEUAZwB5AHAAdAANAAoADQAK
ACAAIAAgAFAAaABvAG4AZQA6ACAAKwAyACAAMAAxADAAMAAzADYAMgAwADIAOAA0AA0ACgAgACAA
IABFAC0AbQBhAGkAbAA6ACAAZQBuAGcALgBrAGgAYQBsAGUAZAAuAG8AbQBhAHIAQABoAG8AdABt
AGEAaQBsAC4AYwBvAG0ADQAKACAAIAAgAE4AYQB0AGkAbwBuAGEAbAAgAEkARAAgAE4AbwAuADoA
IAAyADgANgAxADEAMgA2ADIAMQAwADIAOQA5ADIADQAKAA0ACgANAAoAUgBlAGYAZQByAGUAbgBj
AGUAcwANAAoADQAKAA0ACgANAAoADQAKAEYAdQBsAGwAIABDAG8AcAB5AHIAaQBnAGgAdAAgAFMA
dABhAHQAZQBtAGUAbgB0AA0ACgANAAoAIAAgACAAQwBvAHAAeQByAGkAZwBoAHQAIAAoAEMAKQAg
AEkARQBUAEYAIAAoADIAMAAxADYAKQAuACAAIABBAGwAbAAgAFIAaQBnAGgAdABzACAAUgBlAHMA
ZQByAHYAZQBkAC4ADQAKAA0ACgAgACAAIABUAGgAaQBzACAAZABvAGMAdQBtAGUAbgB0ACAAYQBu
AGQAIAB0AHIAYQBuAHMAbABhAHQAaQBvAG4AcwAgAG8AZgAgAGkAdAAgAG0AYQB5ACAAYgBlACAA
YwBvAHAAaQBlAGQAIABhAG4AZAAgAGYAdQByAG4AaQBzAGgAZQBkACAAdABvAA0ACgAgACAAIABv
AHQAaABlAHIAcwAsACAAYQBuAGQAIABkAGUAcgBpAHYAYQB0AGkAdgBlACAAdwBvAHIAawBzACAA
dABoAGEAdAAgAGMAbwBtAG0AZQBuAHQAIABvAG4AIABvAHIAIABvAHQAaABlAHIAdwBpAHMAZQAg
AGUAeABwAGwAYQBpAG4AIABpAHQADQAKACAAIAAgAG8AcgAgAGEAcwBzAGkAcwB0ACAAaQBuACAA
aQB0AHMAIABpAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AIABtAGEAeQAgAGIAZQAgAHAAcgBl
AHAAYQByAGUAZAAsACAAYwBvAHAAaQBlAGQALAAgAHAAdQBiAGwAaQBzAGgAZQBkAA0ACgAgACAA
IABhAG4AZAAgAGQAaQBzAHQAcgBpAGIAdQB0AGUAZAAsACAAaQBuACAAdwBoAG8AbABlACAAbwBy
ACAAaQBuACAAcABhAHIAdAAsACAAdwBpAHQAaABvAHUAdAAgAHIAZQBzAHQAcgBpAGMAdABpAG8A
bgAgAG8AZgAgAGEAbgB5AA0ACgAgACAAIABrAGkAbgBkACwAIABwAHIAbwB2AGkAZABlAGQAIAB0
AGgAYQB0ACAAdABoAGUAIABhAGIAbwB2AGUAIABjAG8AcAB5AHIAaQBnAGgAdAAgAG4AbwB0AGkA
YwBlACAAYQBuAGQAIAB0AGgAaQBzACAAcABhAHIAYQBnAHIAYQBwAGgAIABhAHIAZQANAAoAIAAg
ACAAaQBuAGMAbAB1AGQAZQBkACAAbwBuACAAYQBsAGwAIABzAHUAYwBoACAAYwBvAHAAaQBlAHMA
IABhAG4AZAAgAGQAZQByAGkAdgBhAHQAaQB2AGUAIAB3AG8AcgBrAHMALgAgACAASABvAHcAZQB2
AGUAcgAsACAAdABoAGkAcwANAAoAIAAgACAAZABvAGMAdQBtAGUAbgB0ACAAaQB0AHMAZQBsAGYA
IABtAGEAeQAgAG4AbwB0ACAAYgBlACAAbQBvAGQAaQBmAGkAZQBkACAAaQBuACAAYQBuAHkAIAB3
AGEAeQAsACAAcwB1AGMAaAAgAGEAcwAgAGIAeQAgAHIAZQBtAG8AdgBpAG4AZwANAAoAIAAgACAA
dABoAGUAIABjAG8AcAB5AHIAaQBnAGgAdAAgAG4AbwB0AGkAYwBlACAAbwByACAAcgBlAGYAZQBy
AGUAbgBjAGUAcwAsACAAZQB4AGMAZQBwAHQAIABhAHMAIABuAGUAZQBkAGUAZAAgAGYAbwByACAA
dABoAGUAIABwAHUAcgBwAG8AcwBlACAAbwBmAA0ACgAgACAAIABkAGUAdgBlAGwAbwBwAGkAbgBn
ACAASQBuAHQAZQByAG4AZQB0ACAAcwB0AGEAbgBkAGEAcgBkAHMAIABpAG4AIAB3AGgAaQBjAGgA
IABjAGEAcwBlACAAdABoAGUAIABwAHIAbwBjAGUAZAB1AHIAZQBzACAAZgBvAHIADQAKACAAIAAg
AGMAbwBwAHkAcgBpAGcAaAB0AHMAIABkAGUAZgBpAG4AZQBkACAAaQBuACAAdABoAGUAIABJAG4A
dABlAHIAbgBlAHQAIABTAHQAYQBuAGQAYQByAGQAcwAgAHAAcgBvAGMAZQBzAHMAIABtAHUAcwB0
ACAAYgBlAA0ACgAgACAAIABmAG8AbABsAG8AdwBlAGQALAAgAG8AcgAgAGEAcwAgAHIAZQBxAHUA
aQByAGUAZAAgAHQAbwAgAHQAcgBhAG4AcwBsAGEAdABlACAAaQB0ACAAaQBuAHQAbwAgAGwAYQBu
AGcAdQBhAGcAZQBzACAAbwB0AGgAZQByACAAdABoAGEAbgANAAoAIAAgACAARQBuAGcAbABpAHMA
aAAuAA0ACgANAAoAIAAgACAAVABoAGUAIABsAGkAbQBpAHQAZQBkACAAcABlAHIAbQBpAHMAcwBp
AG8AbgBzACAAZwByAGEAbgB0AGUAZAAgAGEAYgBvAHYAZQAgAGEAcgBlACAAcABlAHIAcABlAHQA
dQBhAGwAIABhAG4AZAAgAHcAaQBsAGwAIABuAG8AdAAgAGIAZQANAAoAIAAgACAAcgBlAHYAbwBr
AGUAZAAuAA0ACgANAAoAIAAgACAAVABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAGEAbgBkACAA
dABoAGUAIABpAG4AZgBvAHIAbQBhAHQAaQBvAG4AIABjAG8AbgB0AGEAaQBuAGUAZAAgAGgAZQBy
AGUAaQBuACAAaQBzACAAcAByAG8AdgBpAGQAZQBkACAAbwBuAA0ACgAgACAAIABUAEgARQAgAEkA
TgBUAEUAUgBOAEUAVAAgAEUATgBHAEkATgBFAEUAUgBJAE4ARwAgAFQAQQBTAEsAIABGAE8AUgBD
AEUAIABEAEkAUwBDAEwAQQBJAE0AUwAgAEEATABMACAAVwBBAFIAUgBBAE4AVABJAEUAUwAsAA0A
CgAgACAAIABFAFgAUABSAEUAUwBTACAATwBSACAASQBNAFAATABJAEUARAAsACAASQBOAEMATABV
AEQASQBOAEcAIABCAFUAVAAgAE4ATwBUACAATABJAE0ASQBUAEUARAAgAFQATwAgAEEATgBZACAA
VwBBAFIAUgBBAE4AVABZACAAVABIAEEAVAANAAoAIAAgACAAVABIAEUAIABVAFMARQAgAE8ARgAg
AFQASABFACAASQBOAEYATwBSAE0AQQBUAEkATwBOACAASABFAFIARQBJAE4AIABXAEkATABMACAA
TgBPAFQAIABJAE4ARgBSAEkATgBHAEUAIABBAE4AWQAgAFIASQBHAEgAVABTACAATwBSAA0ACgAg
ACAAIABBAE4AWQAgAEkATQBQAEwASQBFAEQAIABXAEEAUgBSAEEATgBUAEkARQBTACAATwBGACAA
TQBFAFIAQwBIAEEATgBUAEEAQgBJAEwASQBUAFkAIABPAFIAIABGAEkAVABOAEUAUwBTACAARgBP
AFIAIABBACAAUABBAFIAVABJAEMAVQBMAEEAUgANAAoAIAAgACAAUABVAFIAUABPAFMARQAuAA0A
CgA=

--_004_AM4PR0401MB2241724888D753F586B1B949BD030AM4PR0401MB2241_--


From nobody Wed Apr 12 09:15:11 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E4912EA81; Wed, 12 Apr 2017 09:15:01 -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, RP_MATCHES_RCVD=-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 fS2CDi3bpzm2; Wed, 12 Apr 2017 09:14:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 698B9129506; Wed, 12 Apr 2017 09:14:55 -0700 (PDT)
Received: from mbp-4.local ([IPv6:2620:11a:c081:20:b029:cf01:225c:cf4b]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v3CGEKvw010934 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 12 Apr 2017 16:14:21 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:b029:cf01:225c:cf4b] claimed to be mbp-4.local
Subject: Re: IAOC requesting input on (potential) meeting cities
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, iaoc@ietf.org, IETF Discussion <ietf@ietf.org>
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es> <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es> <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com> <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <7c61933d-1cbd-75d6-cdbc-dbf2fa60792b@bogus.com>
Date: Wed, 12 Apr 2017 09:14:15 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6rDk12mG5druORR2jdJeHx6AjdATadAJP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UQhQnG_m1f2_jsjYimz6HGOvy1U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:15:02 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6rDk12mG5druORR2jdJeHx6AjdATadAJP
Content-Type: multipart/mixed; boundary="FSwl2jlukdr6moCDvfixh86tKio2TIOUa";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, iaoc@ietf.org,
 IETF Discussion <ietf@ietf.org>
Message-ID: <7c61933d-1cbd-75d6-cdbc-dbf2fa60792b@bogus.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca>
 <20170403152624.GA11714@gsp.org>
 <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com>
 <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es>
 <20170404181505.GA4004@localhost>
 <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com>
 <20170404202446.GB4004@localhost>
 <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie>
 <20170404204617.GC16732@puck.nether.net>
 <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com>
 <20170404221042.GC4004@localhost>
 <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es>
 <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es>
 <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es>
 <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
 <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>
In-Reply-To: <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>

--FSwl2jlukdr6moCDvfixh86tKio2TIOUa
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/12/17 07:01, JORDI PALET MARTINEZ wrote:
> So, you mean they don=E2=80=99t use email?
>
> Sounds surprising to me, despite for sure they had some time in Chicago=
 to decide about what can be said to the community about the SF meeting. =
If they haven=E2=80=99t considered that, I guess we need an IAOC with mor=
e focus on what is the most relevant and important topic right now for th=
e community.
>
> By the way, it seems that they haven=E2=80=99t met anyway since August =
2015, as they promised me to respond to one of my emails regarding some s=
pam/email bouncing issues and the way we are managing so, and I=E2=80=99v=
e been waiting since them. Really nice and respectful way to support the =
community.
As a mailing list moderator who sees a fair amount of bounces, It is
notable that you mta routinly bounces messages to various lists for
reasons that from from the header appear to be disliking the sender. How
you run your MTAm since it is yours, is obviously up to you.

joel
> Regards,
> Jordi
> =20
>
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Ted Lemon <mellon@fugue.c=
om>
> Responder a: <mellon@fugue.com>
> Fecha: mi=C3=A9rcoles, 12 de abril de 2017, 15:26
> Para: <jordi.palet@consulintel.es>
> CC: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
> Asunto: Re: IAOC requesting input on (potential) meeting cities
>
>     On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ <jordi.palet@cons=
ulintel.es> wrote:
>     Do we need to ask again and again every day?
>    =20
>    =20
>    =20
>    =20
>    =20
>     Has the IAOC met since the first time you asked?
>    =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=
 confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that=
 any disclosure, copying, distribution or use of the contents of this inf=
ormation, including attached files, is prohibited.
>
>
>
>



--FSwl2jlukdr6moCDvfixh86tKio2TIOUa--

--6rDk12mG5druORR2jdJeHx6AjdATadAJP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAljuUlgACgkQ8AA1q7Z/VrJwdgCfVMHjPjVfpO7VIGXrLuNF25vX
Ir0An1ZOoL9nv2Als8hWXTfJJedGnPv+
=2i9L
-----END PGP SIGNATURE-----

--6rDk12mG5druORR2jdJeHx6AjdATadAJP--


From nobody Wed Apr 12 09:29:10 2017
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21789131786; Wed, 12 Apr 2017 09:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 dD_RJ7Ol2KMy; Wed, 12 Apr 2017 09:28:59 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E1C713178B; Wed, 12 Apr 2017 09:28:57 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 5AC706045B; Wed, 12 Apr 2017 18:28:55 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.2]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 25351180066; Wed, 12 Apr 2017 18:28:55 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 18:28:52 +0200
From: <lionel.morand@orange.com>
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "MEURIC Julien IMT/OLN" <julien.meuric@orange.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSssnNDQvmKPrPVk6JDOdpTPcg8qHAIZWAgAAHxYCAAbQL8A==
Date: Wed, 12 Apr 2017 16:28:51 +0000
Message-ID: <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com> <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com> <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.com>
In-Reply-To: <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.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.3]
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/ietf/9VLRblD_JVPNjHQYWpihujLExyk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:29:01 -0000

Hi Julien, Jon,

Thank you for your feedback.
Please see below my answer/feedback (indicated with [LM2])

Regards,

Lionel
=20
> Hi Julien
>=20
> You are right, but it is *really easy* for the reader to confuse "stateful
> capability" with "update capability" and "active stateful capability".  C=
ase in
> point: I just confused them in my reply to Lionel.
>=20
> We should fix each of the three points below to make this clearer.

[LM2] I agree :)

> Jon, Lionel,
>=20
> I believe Lionel got confused by the wording introduced in RFC 8051:
> - no report, no update means stateless PCE;
> - report, no update means passive stateful PCE;
> - report and update means active (stateful) PCE.

[LM2] understood!
>=20
> > =3D=3D=3D=3D=3D
> >
> > [LM] active/passive mode are not  advertized in PCEP. s/if active
> > stateful PCE capability was not advertised/if stateful PCE capability
> > was not advertised
> >
> > Jon> ACK
> >
> > =3D=3D=3D=3D=3D
> [JM] NACK! ;-)
> Actually, the passive mode is advertised using the Stateful-capability-ob=
ject TLV
> with the U bit unset, the active mode by setting the U bit.
>=20
[LM2] "il faut =EAtre sorti de Saint-Cyr pour comprendre" as we say in fren=
ch :)
Could be good to add something like "(as indicated by the U-bit clear in St=
ateful-capability-object)"

> > =3D=3D=3D=3D=3D
> >
> > Note that even if the update capability has not been advertised, a PCE
> > can still accept LSP Status Reports from a PCC and build and maintain
> > an up to date view of the state of the PCC's LSPs.
> >
> > [LM] I don't undersand. Is it not in contradiction with
> >
> > "If the PCEP Speaker on the PCE supports the extensions of this draft
> > but did not advertise this capability, then upon receipt of a PCRpt
> > message from the PCC, it MUST generate a PCErr with error- type
> > 19 (Invalid Operation), error-value 5 (Attempted LSP State Report if
> > active stateful PCE capability was not advertised) (see Section
> > 8.5) and it SHOULD terminate the PCEP session."
> >
> > Or does it mean that there is another way than PCRpt message for the
> > PCC to send LSP status reports to the PCE?
> >
> > Jon> ACK.  I think that the statement in the draft is bogus and I
> > propose to delete this sentence from it.
> >
> > =3D=3D=3D=3D=3D
> [JM] I do not think that the text is bogus:
> - case 1: no advertised capability on update but advertised on report (i.=
e. passive
> stateful) =3D> no error message;
> - case 2: no advertised capability on update nor report (i.e. stateless) =
=3D> error.

[LM2] After multiple readings and thanks to your explanation, I think I hav=
e understood. Am I correct saying that the PCE will accept LSP Status Repor=
ts from a PCC ONLY if the stateful PCE capability has been advertised (i.e.=
 Stateful Capability TLV with the 'LSP Update' Flag cleared)? If it is the =
case, is it really required to keep this text, as in the previous paragraph=
 we find the conditions to accept/reject reports from the PCC?
>=20
> > =3D=3D=3D=3D=3D
> >
> > [LM] Would it be useful to discover (using another TLV) whether the
> > PCE is an active/passive stateful PCE, as in IGP-based capabilities
> > discovery mechanism?
> >
> > Jon> This can be inferred immediately from the U flag in the
> > STATEFUL-PCE-CAPABILITY TLV.  Passive mode is synonymous with not
> > sending / handling PCUpd messages.
> >
> > =3D=3D=3D=3D=3D
> [JM] The mechanism is there, but section 7.1.1 may deserve an explicit us=
e of
> the "passive/active" terms, to make sure the capability terminology is al=
igned
> with the vocabulary in the IGP section.

[LM2] I can only be agree with you :)


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed Apr 12 09:32:46 2017
Return-Path: <prvs=127550c264=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52CDC129543 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 09:32: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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHvVk8t8vqW6 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 09:32:36 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D675112EAEA for <ietf@ietf.org>; Wed, 12 Apr 2017 09:32:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492014751; x=1492619551; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=OyMj4F7QvibIx/1YW6rlKEVjV k/UnsVspWzgHZ8U5yM=; b=h5fkpHAAGfEKeuwpVylPTaurpLEoaxR8UYdxh86pZ e3+cKXXD0NxUSwChNta0XUD3mWZfPvJ2e+9VXOPuADV12wJ+mlgYdIH/g6ya0AiG 8lmbV9ofnBmsle5gO1cF7wIdsPeJDGYMvFTWR0A/pgg9EKhWfbQ8tLTSe1n0cLMx gA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=SX7BF5Vv34mjsOucJfNpbUJFZk2e4Zg+67nG3fQCc1I4GAxyBRyITL7VkOck h6qUCGi0ayDa5ydXBFfHQkFWNNQfKtK5faX4W0KnKAfUYrx7lBYsVYUMH ZhfZdnF0vmMe7lKcBApfuGLWgCPafa4pNfQwAv774iIil23qTkN51Q=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Apr 2017 18:32:31 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Apr 2017 18:32:30 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005407288.msg for <ietf@ietf.org>; Wed, 12 Apr 2017 18:32:29 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170412:md50005407288::NmBD/UAA8nNwxCnt:000022lX
X-Return-Path: prvs=127550c264=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Apr 2017 18:32:26 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
Message-ID: <A8777DA9-D116-449F-ABAA-9AFFEB87CD0F@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es> <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es> <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com> <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es> <7c61933d-1cbd-75d6-cdbc-dbf2fa60792b@bogus.com>
In-Reply-To: <7c61933d-1cbd-75d6-cdbc-dbf2fa60792b@bogus.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sP7oWT10khxldy1TXNDaIpk7aZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:32:40 -0000

Hi Joel,

I=E2=80=99ve checked right now the stats of my MTA about *ietf.org and *irt=
f.org, and I don=E2=80=99t see any bounces. Actually, those are in a specia=
l white list since many years ago. So, if you have contradictory informatio=
n it will be helpful to get that in private.

Yes, I use DNS-BL and spamassassin to score and eventually reject emails wh=
ich score extremely high (not just bounce them), but this is not related to=
 the way IETF mail servers were accepting and/or bouncing emails in 2015, a=
nd NOT RELATED AT ALL to the lack of response from the IAOC, especially if =
they promised to come back about that.

The point here is the lack of response, not the specific matter.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de joel jaeggli <joelja@bogus.co=
m>
Responder a: <joelja@bogus.com>
Fecha: mi=C3=A9rcoles, 12 de abril de 2017, 18:14
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, <iaoc@ietf.org>, I=
ETF Discussion <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    On 4/12/17 07:01, JORDI PALET MARTINEZ wrote:
    > So, you mean they don=E2=80=99t use email?
    >
    > Sounds surprising to me, despite for sure they had some time in Chica=
go to decide about what can be said to the community about the SF meeting. =
If they haven=E2=80=99t considered that, I guess we need an IAOC with more =
focus on what is the most relevant and important topic right now for the co=
mmunity.
    >
    > By the way, it seems that they haven=E2=80=99t met anyway since Augus=
t 2015, as they promised me to respond to one of my emails regarding some s=
pam/email bouncing issues and the way we are managing so, and I=E2=80=99ve =
been waiting since them. Really nice and respectful way to support the comm=
unity.
    As a mailing list moderator who sees a fair amount of bounces, It is
    notable that you mta routinly bounces messages to various lists for
    reasons that from from the header appear to be disliking the sender. Ho=
w
    you run your MTAm since it is yours, is obviously up to you.
   =20
    joel
    > Regards,
    > Jordi
    > =20
    >
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Ted Lemon <mellon@fugue=
.com>
    > Responder a: <mellon@fugue.com>
    > Fecha: mi=C3=A9rcoles, 12 de abril de 2017, 15:26
    > Para: <jordi.palet@consulintel.es>
    > CC: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
    > Asunto: Re: IAOC requesting input on (potential) meeting cities
    >
    >     On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ <jordi.palet@co=
nsulintel.es> wrote:
    >     Do we need to ask again and again every day?
    >    =20
    >    =20
    >    =20
    >    =20
    >    =20
    >     Has the IAOC met since the first time you asked?
    >    =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 confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that a=
ny disclosure, copying, distribution or use of the contents of this informa=
tion, including attached files, is prohibited.
    >
    >
    >
    >
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr 12 09:47:14 2017
Return-Path: <prvs=127550c264=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9D5129559 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 09:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQq-Wm-pnJt7 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 09:47:11 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29BF01270A7 for <ietf@ietf.org>; Wed, 12 Apr 2017 09:47:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492015628; x=1492620428; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=xZlt7kLRt6+/9aen4W0oOZW/M Qo/iEvP3Ii2pmuAlkY=; b=TrUWlhTSBpTLmsj4DEW+gd39YIQXuHBLX+S3K9ave nn+HoWIYcyArB0rcaLvnGGX2vsSr4P+M687FrEUE/ZIEW2ul9Z9HJdl6igYxXwv+ 56VGqFvfQDB2hwJ8jJnxvvdJLpiuDboN3P+0oVhJ5hIU3ZUz/kmF4vk5Gl3u7+Dk yU=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=No+T4hx492TaASM1A4ID3Y+MvtGgxuvaElSbF96gtXOlY3SpucvKvaYZ0dwN QaOEYxDASdRie8r2moGOko1XK9AmO9gqKJCO56aFZcah5YUQP55EhtOdc EQoL1EodI2uySD4SCK1MFfBW1SzF2QW1i9zrTVvPiKQOx04ZN9MqHI=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Apr 2017 18:47:08 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Apr 2017 18:47:07 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005407318.msg for <ietf@ietf.org>; Wed, 12 Apr 2017 18:47:06 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170412:md50005407318::+ZY7X2gRDEKwofj+:00000nAW
X-Return-Path: prvs=127550c264=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Apr 2017 18:47:04 +0200
Subject: Re: Khaled Routing Protocol (KRP) ID Submission.
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <eng.khaled.omar@hotmail.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <D7707E4B-CD37-478A-B640-47148DE3276A@consulintel.es>
Thread-Topic: Khaled Routing Protocol (KRP) ID Submission.
References: <AM4PR0401MB2241724888D753F586B1B949BD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB2241724888D753F586B1B949BD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ld_9341eott5uYtKA5roCiKXHdU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:47:13 -0000

Hi Khaled,

Speaking as sergeant-at-arms.

Several folks, including myself, have explained you, several times, that it=
 is inappropriate to send documents to this list, even less when they have =
a specific venue for their discussion.

If you want to participate and contribute, you should read the chapter of t=
his list:

https://tools.ietf.org/html/rfc3005

As you=E2=80=99re submitting a document to the int-area (according to the d=
ocument naming), this probably is the right list for that document discussi=
on, but in any case the document should not be forwarded to any list, just =
the links once published by the RFC editor.

If you keep insisting, I will have no other option than restricting your po=
sting rights in this list, hopefully we can avoid that.

Hat off.

I think if you=E2=80=99re working in a routing document, the right place is=
 the routing-area or a more specific WG, not int-area.

By the way, if that=E2=80=99s useful for you, the submission of the documen=
ts is done automatically here:

https://datatracker.ietf.org/submit/

You can check your XML file here:

https://xml2rfc.tools.ietf.org/

Last, but not least, you should read with care https://www.ietf.org/tao.htm=
l, and more generic link at https://www.ietf.org/newcomers.html.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Khaled Omar <eng.khaled.omar@=
hotmail.com>
Responder a: <eng.khaled.omar@hotmail.com>
Fecha: mi=C3=A9rcoles, 12 de abril de 2017, 18:13
Para: "ietf-draft-submission@ietf.org" <ietf-draft-submission@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: Khaled Routing Protocol (KRP) ID Submission.

    Hi Jasmine,
    =20
    Please upload the 2nd ID attached.
    =20
    Looking for an advanced discussion to take this ID forward.
    =20
    Best Regards,
    =20
    Khaled Omar=20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr 12 11:28:39 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCEB12EB3F for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:28:37 -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, RP_MATCHES_RCVD=-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 OHEN5bOxhLYN for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:28:35 -0700 (PDT)
Received: from virgo02.ee.ethz.ch (virgo02.ee.ethz.ch [129.132.72.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2897812EB28 for <ietf@ietf.org>; Wed, 12 Apr 2017 11:28:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo02.ee.ethz.ch (Postfix) with ESMTP id 3w3C9F4D1cz15LhY; Wed, 12 Apr 2017 20:28:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo02.ee.ethz.ch
Received: from virgo02.ee.ethz.ch ([127.0.0.1]) by localhost (virgo02.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tNPezt5t814f; Wed, 12 Apr 2017 20:28:32 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC24E1.dip0.t-ipconnect.de [93.236.36.225]) by virgo02.ee.ethz.ch (Postfix) with ESMTPSA; Wed, 12 Apr 2017 20:28:32 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
Date: Wed, 12 Apr 2017 20:28:31 +0200
Cc: Martin Thomson <martin.thomson@gmail.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A74855AD-0C8B-4A4D-86C7-940F56873F9E@tik.ee.ethz.ch>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X0Y3SyeWQIjlBeqkB5_nz7_tDc0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 18:28:37 -0000

Hi Martin, hi Kathleen,

I would like to comment (for now) just on this one section, as my name =
was called out.

> Am 11.04.2017 um 05:54 schrieb Kathleen Moriarty =
<kathleen.moriarty.ietf@gmail.com>:
>=20
>>> Section 2.1
>>>=20
>>> This is one of the few sections that talk about what it means to =
operate a
>>> service as opposed to operate a network.
>>>=20
>>> Overall, this section doesn't work particularly well.  The =
distinction
>>> between
>>> integrated and standalone load balancing is an interesting division, =
but
>>> it
>>> doesn't leverage this distinction well.  What causes a standalone
>>> load-balancer
>>> to be necessary? =20

My understanding is that the stand-alone load balancer was only brought =
up to better explain what an integrated load balancer is, assuming that =
the integrated (more complex) case is the common one.=20

However, to answer your question, for a stand-alone laod balancer it is =
assumed that you only have a small number of servers at one single =
location and you only need one box that does the load-balancing on these =
different servers. So all this box needs to know is the IP address of =
these servers.

>>> Is this something a network operator uses?  I see text
>>> on NFV
>>> later, but it's far removed from the original text and it seems
>>> aspirational
>>> rather than concrete.  On the other hand, many of the concerns in =
this
>>> document
>>> simply don't apply to an integrated load balancer.

To my understanding all the concerns apply to integrated load balancers. =
Integrated only means that the load balancer shares some information =
with the server and based on this knowledge the load balancer can =
identify based on some information in the packets which server this =
packet should be forwarded to.

>>>=20
>>> The amount of text on QUIC here is surprising.  Given how much of =
QUIC is
>>> changing right now, we shouldn't publish a document that attempts to =
make
>>> claims
>>> about what QUIC is or how it is operated.  This attempts to dive =
into the
>>> details of QUIC connection migration in a way that presumes much =
about the
>>> outcome of issues that the QUIC working group is still struggling =
with.
>>>=20
>>> I would strongly recommend removing QUIC-specific language from this
>>> section and
>>> the document as a whole.  We have an operational document in the =
QUIC
>>> working
>>> group that would be a good venue to discuss some of these concerns.
>=20
> While we read this as  more of a substantive remark, the text on
> load balancers and QUIC were added per Mirja's IESG review.  We would
> need to check with her about making any changes here.  They were
> specific additions that were requested.
>=20
> Further, it is only IETF QUIC that is in active development.
> Google QUIC (referred to as GQUIC in IETF discussions) is a more
> stable experiment now.


I fully agree to remove the quic specific language. It=E2=80=99s =
definitely too early to say something in this document (and GQUIC is =
probably not documented well enough to rely on this). This text wasn=E2=80=
=99t provided by me but I recommended a contributor for this text who is =
also active in the quic wg and missed this when he send the text.

I recommend to simply remove the following sentences:

"QUIC is an example of such
   protocol in development by IETF QUIC WG right now.=E2=80=9C

"New connection-migration-tolerant protocols, such as QUIC, are
   deliberately designed to allow such extra information available in
   plain text (QUIC's server-generated flow IDs).=E2=80=9C


>=20
>>>=20
>>> Is this an oblique reference to (the much-loved) RFC 7974?

No, not at all. There are other ways middleboxes can add information. =
But in this case actually the server would add information because the =
load balancers and the server share some knowledge.

>>>=20
>>>   Current protocols, such as TCP, allow the development of stateless
>>> integrated
>>>   load balancers by availing such load balancers of additional plain =
text
>>>   information in client-to-server packets.
>>>=20
>>> Otherwise, I don't know what it means.

A server could select a certain sequence number (range), or TCP =
timestamp, I guess...

>>>=20
>>> BTW, I like this parenthetical:
>>>=20
>>>   (That said, care must be exercised to make sure that the =
information
>>> encoded
>>>   by the endpoints is not sufficient to identify unique flows and
>>> facilitate
>>>   Persistent Surveillance attack vector.)
>>>=20
>>> I'm going to take this to the QUIC working group, because QUIC =
certainly
>>> doesn't
>>> meet that bar right now.  It fully facilitates Persistent =
Surveillance in
>>> its
>>> current form (proper noun?  I haven't really seen that term before, =
even
>>> though
>>> it draws a neat parallel with Pervasive Surveillance).
>>>=20
>=20
> OK, let us know what you hear back.  These changes were in response to
> the sponsoring AD's request of that work.

I think this sentence should be removed in this document and a reference =
to RFC 7258 should be added, instead of coming up with new terminology =
here that sets the bar higher that what was agreed in RFC 7258.

>=20
>>> Editorial:
>>> * "pop" is a term of art that needs explanation.
>>> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - =
the
>>>  possessive form for the inanimate.
>>> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>=20
> Thanks for the nit corrections.

Thanks!

I will further comment later!

Mirja



From nobody Wed Apr 12 11:31:21 2017
Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8D712EB38 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 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_LOW=-0.7, T_HTML_ATTACH=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.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 6wUEaiQUOufE for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:31:16 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 473D1129A97 for <ietf@ietf.org>; Wed, 12 Apr 2017 11:31:16 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id u2so30505439wmu.0 for <ietf@ietf.org>; Wed, 12 Apr 2017 11:31:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=3zqZGsfxxS/yG0cgsPsf31sXc+Qy1MRyJN5drqUuPGg=; b=PyoZLpjV8nzd5WZfP75yHvSLwMQ99RaIjA+Hj+K5gLX8SElEZABYexE04rbIBYxBBs 5T20CKzh/rlBRvIV4JjSTd99oLCid2ekqAf2kLLJRThs4z7pWnOBENRhCnUfid9fWmco bRFX3JvLakzLPwwYRYY08DIf1gGK/c/CrhhtOwheOIpDHIe74M1HU1AXg7o/DxHeJIDS 5eH8pj+xHFng5ezPkf5gG1Bk7l86F9Xh+9LPNVLev+U0wSh5GBdfdqqMQ0J27QTCepzl prcCZT/qge3ceg3R2liV59Y9usoaZL8smU8BtT3lhpJHl5qDlvT1u+SJhryr8QiuEhSU pbqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3zqZGsfxxS/yG0cgsPsf31sXc+Qy1MRyJN5drqUuPGg=; b=F/nehKT6BnWjs0JE3q+kFXtWgOe/Dj1pWdEcovLfUyDYvhs9zDSBmvWMO3RK5Nnmrn YC6L1Idk4cstxRpSJJrN4AMHlpxrrYYIa+ixj4hfApjOZHTbjao0pqxtygSXyJ8vQRs9 ssVb6h7RI3fOEgjTi7sm7Xb22y+TyjNt8k2GZwo6Qi1WA8Ujtji0tlGCIBhQghoXndw+ miUlBlgTd2eBPWwlulypp+S/jFc1LGXDpUc6HCyCBKpksr+z91Q19utxEkOM/zBh23FP meVC97YOQ3eEdQehl+x6LXwgI/mNzkQtF7eh6fhYsjeyUstAqNclfyCBrY6Whz8lNVyd oBFg==
X-Gm-Message-State: AN3rC/5ufZk8DGeoDy8owdlkDzKCR5u9lDYsdD59sYVzhknwqeh1rNWkatzahJ4j2CTiQA==
X-Received: by 10.28.198.10 with SMTP id w10mr4008989wmf.1.1492021874623; Wed, 12 Apr 2017 11:31:14 -0700 (PDT)
Received: from localhost ([185.78.129.1]) by smtp.gmail.com with ESMTPSA id l186sm7512110wmd.17.2017.04.12.11.31.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 11:31:12 -0700 (PDT)
Date: Wed, 12 Apr 2017 20:31:10 +0200
From: Job Snijders <job@instituut.net>
To: Jay Borkenhagen <jayb@braeburn.org>
Cc: ietf@ietf.org, grow-chairs@ietf.org, grow@ietf.org, warren@kumari.net, draft-ietf-grow-large-communities-usage@ietf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [GROW] Last Call: <draft-ietf-grow-large-communities-usage-05.txt> (Use of BGP Large Communities) to Informational RFC
Message-ID: <20170412183110.qx23vkx6oi5u3xb2@Vurt.local>
References: <149158518251.11127.8008659284325510446.idtracker@ietfa.amsl.com> <22766.12199.587325.838948@oz.mt.att.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="stpihhpuit6yxyxp"
Content-Disposition: inline
In-Reply-To: <22766.12199.587325.838948@oz.mt.att.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hZrf214G6b54qFoAJkptgUr_LIQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 18:31:20 -0000

--stpihhpuit6yxyxp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Apr 12, 2017 at 09:46:15AM -0400, Jay Borkenhagen wrote:
> On 07-April-2017, The IESG writes:
>  > 
>  > The IESG has received a request from the Global Routing Operations WG
>  > (grow) to consider the following document:
>  > - 'Use of BGP Large Communities'
>  >   <draft-ietf-grow-large-communities-usage-05.txt> as Informational RFC
>  > 
>  > The IESG plans to make a decision in the next few weeks, and solicits
>  > final comments on this action. Please send substantive comments to the
>  > ietf@ietf.org mailing lists by 2017-04-21. Exceptionally, comments may be
>  > sent to iesg@ietf.org instead. In either case, please retain the
>  > beginning of the Subject line to allow automated sorting.
>  > 
> 
> The following comment may not measure up to being "substantive", but
> those in authority can decide.
> 
> I have always liked the way the definition of the "BGP Communities
> Attribute" spec in RFC1997 was paired with RFC1998's "An Application
> of the BGP Community Attribute in Multi-home Routing": the former for
> the "bits on the wire" spec, the latter for "how operators can use it."
> 
> draft-ietf-grow-large-communities-usage-05.txt's Introduction section
> currently reads as follows:
> 
>    BGP Large Communities [RFC8092] provide a mechanism to signal
>    opaque information between Autonomous Systems (ASs).  This document
>    presents examples of how operators might utilize BGP Large
>    Communities to achieve various goals.  This document draws on the
>    experience of operator communities such as NANOG [1] and NLNOG [2].
> 
> I would like to suggest this minor change:
> 
>    BGP Large Communities [RFC8092] provide a mechanism to signal
>    opaque information between Autonomous Systems (ASs).  In very much
>    the same way that [RFC1998] provides a concrete real-world
>    application for [RFC1997]'s communities, this document presents
>    examples of how operators might utilize BGP Large Communities to
>    achieve various goals.  This document draws on the experience of
>    operator communities such as NANOG [1] and NLNOG [2].
> 
> Thanks for considering, and very belated thanks to Tony and Enke for
> RFC1998. 

I would not object to this change. After all, the whole idea for
draft-ietf-grow-large-communities-usage originated from the fact that
RFC 1998 exists, so we might as well mention & acknowledge that. :-)

Attached is a HTML diff of what the -06 version would look like. Barring
no objections, I'll post -06 somewhere in the next few days.

Kind regards,

Job

--stpihhpuit6yxyxp
Content-Type: text/html; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-grow-large-communities-usage-06-from-5.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Darwin Vurt.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:45:33 PST 2017; root:xnu-3789.51.2~1/RELEASE_X86_64 x86_64 --> 
<!-- Using awk: /usr/local/bin/gawk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 3.1.5, GNU MP 6.1.2) --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (GNU wdiff) 1.2.2 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-grow-large-communities-usage-05.txt - draft-ietf-grow-large-communities-usage-06.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-grow-large-communities-usage-05.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-grow-large-communities-usage-06.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Global Routing Operations                                    J. Snijders</td><td> </td><td class="right">Global Routing Operations                                    J. Snijders</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                J. Heasley</td><td> </td><td class="right">Internet-Draft                                                J. Heasley</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Informational                                       NTT</td><td> </td><td class="right">Intended status: Informational                                       NTT</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">September 24, 2017</span>                                   M. Schmidt</td><td> </td><td class="rblock">Expires: <span class="insert">October 14, 2017  </span>                                   M. Schmidt</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                                 i3D.net</td><td> </td><td class="right">                                                                 i3D.net</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                          <span class="delete">March 23</span>, 2017</td><td> </td><td class="rblock">                                                          <span class="insert">April 12</span>, 2017</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                      Use of BGP Large Communities</td><td> </td><td class="right">                      Use of BGP Large Communities</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">               draft-ietf-grow-large-communities-usage-0<span class="delete">5</span></td><td> </td><td class="rblock">               draft-ietf-grow-large-communities-usage-0<span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Examples and inspiration for operators to use BGP Large Communities.</td><td> </td><td class="right">   Examples and inspiration for operators to use BGP Large Communities.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right">   This Internet-Draft is submitted in full conformance with the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   provisions of BCP 78 and BCP 79.</td><td> </td><td class="right">   provisions of BCP 78 and BCP 79.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">September 2</span>4, 2017.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">October 1</span>4, 2017.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 2, line 36</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 2, line 36</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       4.3.2.  Region Based Manipulation of LOCAL_PREF . . . . . . .  10</td><td> </td><td class="right">       4.3.2.  Region Based Manipulation of LOCAL_PREF . . . . . . .  10</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       4.3.3.  Note of Caution for LOCAL_PREF Functions  . . . . . .  11</td><td> </td><td class="right">       4.3.3.  Note of Caution for LOCAL_PREF Functions  . . . . . .  11</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     4.4.  Route Server Prefix Distribution Control  . . . . . . . .  11</td><td> </td><td class="right">     4.4.  Route Server Prefix Distribution Control  . . . . . . . .  11</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12</td><td> </td><td class="right">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12</td><td> </td><td class="right">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12</td><td> </td><td class="right">   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13</td><td> </td><td class="right">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  13</td><td> </td><td class="right">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  13</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13</td><td> </td><td class="right">     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  13</td><td> </td><td class="right">     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  13</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  1<span class="delete">3</span></td><td> </td><td class="rblock">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP Large Communities [RFC8092] provide a mechanism to signal opaque</td><td> </td><td class="right">   BGP Large Communities [RFC8092] provide a mechanism to signal opaque</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   information between Autonomous Systems (ASs).  <span class="delete">This</span> document presents</td><td> </td><td class="rblock">   information between Autonomous Systems (ASs).  <span class="insert">In very much the same</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   examples of how operators might utilize BGP Large Communities to</td><td> </td><td class="rblock"><span class="insert">   way that [RFC1998] provides a concrete real-world application for</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   achieve various goals.  This document draws on the experience of</td><td> </td><td class="rblock"><span class="insert">   [RFC1997] communities, this</span> document presents examples of how</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   operator communities such as NANOG [1] and NLNOG [2].</td><td> </td><td class="rblock">   operators might utilize BGP Large Communities to achieve various</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   goals.  This document draws on the experience of operator communities</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   such as NANOG [1] and NLNOG [2].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">2.  The Design Overview</td><td> </td><td class="right">2.  The Design Overview</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP Large Communities are composed of three 4-octet fields.  The</td><td> </td><td class="right">   BGP Large Communities are composed of three 4-octet fields.  The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   first is the Global Administrator (GA) field, whose value is the</td><td> </td><td class="right">   first is the Global Administrator (GA) field, whose value is the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Autonomous System Number (ASN) of the AS that has defined the meaning</td><td> </td><td class="right">   Autonomous System Number (ASN) of the AS that has defined the meaning</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the remaining two 4-octet fields, known as "Local Data Part 1" and</td><td> </td><td class="right">   of the remaining two 4-octet fields, known as "Local Data Part 1" and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   "Local Data Part 2".  This document describes an approach where the</td><td> </td><td class="right">   "Local Data Part 2".  This document describes an approach where the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   "Local Data Part 1" field contains a function identifier and the</td><td> </td><td class="right">   "Local Data Part 1" field contains a function identifier and the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   "Local Data Part 2" contains a parameter value.  Using the canonical</td><td> </td><td class="right">   "Local Data Part 2" contains a parameter value.  Using the canonical</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 13, line 24</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 13, line 24</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454,</td><td> </td><td class="right">              and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              February 2015, &lt;http://www.rfc-editor.org/info/rfc7454&gt;.</td><td> </td><td class="right">              February 2015, &lt;http://www.rfc-editor.org/info/rfc7454&gt;.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC8092]  Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas,</td><td> </td><td class="right">   [RFC8092]  Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              I., and N. Hilliard, "BGP Large Communities Attribute",</td><td> </td><td class="right">              I., and N. Hilliard, "BGP Large Communities Attribute",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              RFC 8092, DOI 10.17487/RFC8092, February 2017,</td><td> </td><td class="right">              RFC 8092, DOI 10.17487/RFC8092, February 2017,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              &lt;http://www.rfc-editor.org/info/rfc8092&gt;.</td><td> </td><td class="right">              &lt;http://www.rfc-editor.org/info/rfc8092&gt;.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">8.2.  Informative References</td><td> </td><td class="right">8.2.  Informative References</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">[RFC1998]  Chen, E. and T. Bates, "An Application of the BGP</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">              Community Attribute in Multi-home Routing", RFC 1998,</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">              DOI 10.17487/RFC1998, August 1996,</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">              &lt;http://www.rfc-editor.org/info/rfc1998&gt;.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC4264]  Griffin, T. and G. Huston, "BGP Wedgies", RFC 4264,</td><td> </td><td class="right">   [RFC4264]  Griffin, T. and G. Huston, "BGP Wedgies", RFC 4264,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              DOI 10.17487/RFC4264, November 2005,</td><td> </td><td class="right">              DOI 10.17487/RFC4264, November 2005,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              &lt;http://www.rfc-editor.org/info/rfc4264&gt;.</td><td> </td><td class="right">              &lt;http://www.rfc-editor.org/info/rfc4264&gt;.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7947]  Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker,</td><td> </td><td class="right">   [RFC7947]  Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              "Internet Exchange BGP Route Server", RFC 7947,</td><td> </td><td class="right">              "Internet Exchange BGP Route Server", RFC 7947,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              DOI 10.17487/RFC7947, September 2016,</td><td> </td><td class="right">              DOI 10.17487/RFC7947, September 2016,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              &lt;http://www.rfc-editor.org/info/rfc7947&gt;.</td><td> </td><td class="right">              &lt;http://www.rfc-editor.org/info/rfc7947&gt;.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7948]  Hilliard, N., Jasinska, E., Raszuk, R., and N. Bakker,</td><td> </td><td class="right">   [RFC7948]  Hilliard, N., Jasinska, E., Raszuk, R., and N. Bakker,</td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 7 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>9 lines changed or deleted</i></th><th><i> </i></th><th><i>16 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--stpihhpuit6yxyxp--


From nobody Wed Apr 12 11:43:41 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1561296C6 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:43:39 -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 DaG9jG7KG-rZ for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 11:43:37 -0700 (PDT)
Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::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 98F0A12955B for <ietf@ietf.org>; Wed, 12 Apr 2017 11:43:37 -0700 (PDT)
Received: by mail-pg0-x22b.google.com with SMTP id 72so10379473pge.2 for <ietf@ietf.org>; Wed, 12 Apr 2017 11:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=D8jZ7KgdtWHRuFOmrybIhr1R6PO0moxnCewZj4WeN3s=; b=sfTRcaat0upCeRBo52OXqn90xPv/012yzcL4g/1KqdbwxfMBosVNQHNoick3o+BlCk +fVAknZPQgPnCJJ90HMnEY63thYQr5ggWa5or2PXi+m/vHlsfVfO6MXiCsM7D6s9nBFA NdNcAGAGPXafM1+N954odkTtOAf2Uzs8phbHeXxACBOFByG/7IPyPSL1uY3AvS73es45 lozxqCVGAjPINP11Q+wogBc80E9649ZShpqIkcW50MIibVncTdTKavdHr8z/53SPJ2LQ a5RtKtIdo17v5Al8zwl9b7zF182pS4y2yyTTnqktMnl0J34MReMjJ0Xwz5pev7vl83vz DEcw==
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:content-transfer-encoding; bh=D8jZ7KgdtWHRuFOmrybIhr1R6PO0moxnCewZj4WeN3s=; b=QJYsCeCXeyKdTmvk+CN2rYzFZYsMWHRT/gKj0X4IJrzXJMk1QQkvo3KAnSLB9Dv/6P bJ4Tt/Hb/AucBgnXWMNtx9mXeWRR0eWXFyiwAMFtzbDgPRFR15nVjs8WjdaIfSEBzXOi TZSdkLij0T0ngUDdaY/Uy+63T4NFKp04KbNvwSwBTBJ6hlGc0otbaVmSUGZjc2tbsa4Y Q14vMpuZ892lTChZ/X8dz0qm5Q2XIYaE3y9pTGtJOw9el23JzvEIrhrLHeNLGUGfQ4Nn EGfHBkvCgkoNysNuWtmeYGvyQzixeYeRRlfCuJ5dg2xFhT3GXF8uGkUxjQ/NYGb4+4DI 6diA==
X-Gm-Message-State: AN3rC/7D+12YxUHtn77T5++gnzh+YJXhTxEZfy9/6Dp0JNn/gIbDlmZ+q16IDqggLQmAfFr4p0Rnf2SfZDdvjg==
X-Received: by 10.98.29.86 with SMTP id d83mr15338312pfd.68.1492022617157; Wed, 12 Apr 2017 11:43:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.162.41 with HTTP; Wed, 12 Apr 2017 11:42:56 -0700 (PDT)
In-Reply-To: <A74855AD-0C8B-4A4D-86C7-940F56873F9E@tik.ee.ethz.ch>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com> <A74855AD-0C8B-4A4D-86C7-940F56873F9E@tik.ee.ethz.ch>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 12 Apr 2017 14:42:56 -0400
Message-ID: <CAHbuEH4gDB==ngGvqpN7747uFV_FnrYtKi_azk7hyoV8YHH6Jw@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Cc: Martin Thomson <martin.thomson@gmail.com>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HyXCzWEvx-V4PGajszm_qrcofRg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 18:43:40 -0000

Mirja,

Sorry for the top post.

Thank you for responding on the outstanding items that were more
technical in nature (QUIC and load balancing).  We'll integrate your
suggested edits in the next revision.

Kathleen

On Wed, Apr 12, 2017 at 2:28 PM, Mirja K=C3=BChlewind
<mirja.kuehlewind@tik.ee.ethz.ch> wrote:
> Hi Martin, hi Kathleen,
>
> I would like to comment (for now) just on this one section, as my name wa=
s called out.
>
>> Am 11.04.2017 um 05:54 schrieb Kathleen Moriarty <kathleen.moriarty.ietf=
@gmail.com>:
>>
>>>> Section 2.1
>>>>
>>>> This is one of the few sections that talk about what it means to opera=
te a
>>>> service as opposed to operate a network.
>>>>
>>>> Overall, this section doesn't work particularly well.  The distinction
>>>> between
>>>> integrated and standalone load balancing is an interesting division, b=
ut
>>>> it
>>>> doesn't leverage this distinction well.  What causes a standalone
>>>> load-balancer
>>>> to be necessary?
>
> My understanding is that the stand-alone load balancer was only brought u=
p to better explain what an integrated load balancer is, assuming that the =
integrated (more complex) case is the common one.
>
> However, to answer your question, for a stand-alone laod balancer it is a=
ssumed that you only have a small number of servers at one single location =
and you only need one box that does the load-balancing on these different s=
ervers. So all this box needs to know is the IP address of these servers.
>
>>>> Is this something a network operator uses?  I see text
>>>> on NFV
>>>> later, but it's far removed from the original text and it seems
>>>> aspirational
>>>> rather than concrete.  On the other hand, many of the concerns in this
>>>> document
>>>> simply don't apply to an integrated load balancer.
>
> To my understanding all the concerns apply to integrated load balancers. =
Integrated only means that the load balancer shares some information with t=
he server and based on this knowledge the load balancer can identify based =
on some information in the packets which server this packet should be forwa=
rded to.
>
>>>>
>>>> The amount of text on QUIC here is surprising.  Given how much of QUIC=
 is
>>>> changing right now, we shouldn't publish a document that attempts to m=
ake
>>>> claims
>>>> about what QUIC is or how it is operated.  This attempts to dive into =
the
>>>> details of QUIC connection migration in a way that presumes much about=
 the
>>>> outcome of issues that the QUIC working group is still struggling with=
.
>>>>
>>>> I would strongly recommend removing QUIC-specific language from this
>>>> section and
>>>> the document as a whole.  We have an operational document in the QUIC
>>>> working
>>>> group that would be a good venue to discuss some of these concerns.
>>
>> While we read this as  more of a substantive remark, the text on
>> load balancers and QUIC were added per Mirja's IESG review.  We would
>> need to check with her about making any changes here.  They were
>> specific additions that were requested.
>>
>> Further, it is only IETF QUIC that is in active development.
>> Google QUIC (referred to as GQUIC in IETF discussions) is a more
>> stable experiment now.
>
>
> I fully agree to remove the quic specific language. It=E2=80=99s definite=
ly too early to say something in this document (and GQUIC is probably not d=
ocumented well enough to rely on this). This text wasn=E2=80=99t provided b=
y me but I recommended a contributor for this text who is also active in th=
e quic wg and missed this when he send the text.
>
> I recommend to simply remove the following sentences:
>
> "QUIC is an example of such
>    protocol in development by IETF QUIC WG right now.=E2=80=9C
>
> "New connection-migration-tolerant protocols, such as QUIC, are
>    deliberately designed to allow such extra information available in
>    plain text (QUIC's server-generated flow IDs).=E2=80=9C
>
>
>>
>>>>
>>>> Is this an oblique reference to (the much-loved) RFC 7974?
>
> No, not at all. There are other ways middleboxes can add information. But=
 in this case actually the server would add information because the load ba=
lancers and the server share some knowledge.
>
>>>>
>>>>   Current protocols, such as TCP, allow the development of stateless
>>>> integrated
>>>>   load balancers by availing such load balancers of additional plain t=
ext
>>>>   information in client-to-server packets.
>>>>
>>>> Otherwise, I don't know what it means.
>
> A server could select a certain sequence number (range), or TCP timestamp=
, I guess...
>
>>>>
>>>> BTW, I like this parenthetical:
>>>>
>>>>   (That said, care must be exercised to make sure that the information
>>>> encoded
>>>>   by the endpoints is not sufficient to identify unique flows and
>>>> facilitate
>>>>   Persistent Surveillance attack vector.)
>>>>
>>>> I'm going to take this to the QUIC working group, because QUIC certain=
ly
>>>> doesn't
>>>> meet that bar right now.  It fully facilitates Persistent Surveillance=
 in
>>>> its
>>>> current form (proper noun?  I haven't really seen that term before, ev=
en
>>>> though
>>>> it draws a neat parallel with Pervasive Surveillance).
>>>>
>>
>> OK, let us know what you hear back.  These changes were in response to
>> the sponsoring AD's request of that work.
>
> I think this sentence should be removed in this document and a reference =
to RFC 7258 should be added, instead of coming up with new terminology here=
 that sets the bar higher that what was agreed in RFC 7258.
>
>>
>>>> Editorial:
>>>> * "pop" is a term of art that needs explanation.
>>>> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - t=
he
>>>>  possessive form for the inanimate.
>>>> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>>
>> Thanks for the nit corrections.
>
> Thanks!
>
> I will further comment later!
>
> Mirja
>
>



--=20

Best regards,
Kathleen


From nobody Wed Apr 12 13:17:12 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59628129666 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 13:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 Du4Os0gDjFfF for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 13:17:08 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-oln040092068101.outbound.protection.outlook.com [40.92.68.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DA3112778E for <ietf@ietf.org>; Wed, 12 Apr 2017 13:17: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; bh=jjb2IiBxzhtVUj4XMJxODFAQztKzDCJywR/HVMPVT7Q=; b=GY9hDlq39EFexUbwC/vkI/pUkibP2pM0/tPBsmAzL2ngY1arM2Oia9dk4bDLnGB+Lu71UKooM9LlxGOsfuMJ813QbQUW7q1RUdpoStjtcsed2YQfZfcbrawScKOVClXH/rOZrbn5gYed/fUSDAS3EHIejtOEnD4WmjBi2KX55U2ag4sM78VEl/D4Y7TykT0L0Qma9bjKJ4sDcfFq6DVLGhGuvhoP1n6tSOlEVyYESxlNvYG8fEYso8aiOFUa1ullfP3vVvr1UfdhBYszGRPpvwpoBc11fpVsxmS/Nhlp83ORwsSVNgGmbDQOfH0H9Ms6ozFswsdg1VnRj5f1t1m1Sw==
Received: from HE1EUR02FT008.eop-EUR02.prod.protection.outlook.com (10.152.10.54) by HE1EUR02HT047.eop-EUR02.prod.protection.outlook.com (10.152.10.179) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Wed, 12 Apr 2017 20:17:05 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.10.53) by HE1EUR02FT008.mail.protection.outlook.com (10.152.10.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Wed, 12 Apr 2017 20:17:05 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Wed, 12 Apr 2017 20:17:05 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: ietf <ietf@ietf.org>, "routing-area@ietf.com" <routing-area@ietf.com>
Subject: Re: Khaled Routing Protocol (KRP) ID Submission.
Thread-Topic: Khaled Routing Protocol (KRP) ID Submission.
Thread-Index: AdKzp1CRFd0eQahqTpyMvf6uY+qORA==
Date: Wed, 12 Apr 2017 20:17:05 +0000
Message-ID: <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <D7707E4B-CD37-478A-B640-47148DE3276A@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: consulintel.es; dkim=none (message not signed) header.d=none; consulintel.es; dmarc=none action=none header.from=hotmail.com; 
x-incomingtopheadermarker: OriginalChecksum:0D9546E2791921EF3B044133DA2FAF505F750598C74E973B197DA8B408E0F29F; UpperCasedChecksum:012DD63C8B90556899630999057AF484E074E1789AF14D0A78E50EA481451A43; SizeAsReceived:7927; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT047; 5:YLLvQKGQbhXD+asaxCnH2gGuoLD4IzaDaKXyY+KumX/9vd7Q4LYW0N2YAJ856QMCsB+8kIRvIVybLvyBlK/4Zqt4WeEZ56oV31jrxYcKf6aEGoxXVBEMMXZChvtEi2+fFVD8pVoxWypr5Som3Hhwyw==; 24:3U+d+OOr62Wu5NW1vSSjHEWuoVF38HOVtmRQBJAdIZWC1poFoz+nm8pqZhasUKfTsamtDFK5Hv7+eUObd4Z9bI6mSOHi3I8UojgTzNxyoOk=; 7:RWbTomzxk2qxX4DSbSMiiLesVWoLVTyP5ebNnfUjvH9AJapX6v4XeixXqxqntAAGoCvtR9dxOP3jztoGg31P9q+zeSNS7zY2o3q85/T/dvP5maYduN3DOaM5av8qPgM7WbXOTQnyAUSNy1JaRJeEeKvLqaOEBcCpVEhTy4w3eXdUJCt+HYNzzaTDooZ6JOhL/YXUB5BIpGZoukgkAJti4d53acyIooJT1d6LcZaRzF12wd56bVVRYiwr/1SUqHPIB9YnJ8BRQIq1fEaA9z6dJdsY4L45UbBe/Of/HeHjwC+Od67Upa5NmFZ2YqR/a3Jz
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT047; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 5adbb6e9-9cae-4905-44c5-08d481e0e220
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR02HT047; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR02HT047; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT047; 
x-forefront-prvs: 027578BB13
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241689CED212EF6C7F2E66ABD030AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2017 20:17:05.0260 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT047
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T9PAT845i8WT-Ptv3e6_t3uIgzM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 20:17:10 -0000

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

SGksDQoNCkkgc2VudCBteSAybmQgSUQgdG8gYWxsIHRoZSBpZXRmIGxpc3QgYXMgd2VsbCBzbyBJ
IGNhbiBmaW5kIGEgc3VnZ2VzdGlvbiB3aGVyZSB0aGlzIElEIHNob3VsZCBiZSBkaXNjdXNzZWQg
YW5kIHRob3NlIG9uIHRoZSBsaXN0IGNhbiBrbm93IGFib3V0IEtIQUxFRCBSb3V0aW5nIFByb3Rv
Y29sIChLUlApIHNvIG1heWJlIHNvbWVvbmUgaXMgaW50ZXJlc3RlZCBpbiBteSBuZXcgZHJhZnQg
YXMgdGhlcmUgYXJlIHRoaW5ncyBleHBlY3RlZCB0byBiZSBhZGRlZCB0byBtYWtlIHRoaXMgSUQg
aW4gdGhlIGJlc3QgZm9ybS4NCg0KQmVzdCByZWdhcmRzLA0KDQpLaGFsZWQgT21hcg0KDQoNCi0t
LS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLaGFsZWQgUm91
dGluZyBQcm90b2NvbCAoS1JQKSBJRCBTdWJtaXNzaW9uLg0KRnJvbTogSk9SREkgUEFMRVQgTUFS
VElORVoNClRvOiBlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20NCkNDOiBpZXRmQGlldGYub3Jn
DQoNCg0KSGkgS2hhbGVkLA0KDQpTcGVha2luZyBhcyBzZXJnZWFudC1hdC1hcm1zLg0KDQpTZXZl
cmFsIGZvbGtzLCBpbmNsdWRpbmcgbXlzZWxmLCBoYXZlIGV4cGxhaW5lZCB5b3UsIHNldmVyYWwg
dGltZXMsIHRoYXQgaXQgaXMgaW5hcHByb3ByaWF0ZSB0byBzZW5kIGRvY3VtZW50cyB0byB0aGlz
IGxpc3QsIGV2ZW4gbGVzcyB3aGVuIHRoZXkgaGF2ZSBhIHNwZWNpZmljIHZlbnVlIGZvciB0aGVp
ciBkaXNjdXNzaW9uLg0KDQpJZiB5b3Ugd2FudCB0byBwYXJ0aWNpcGF0ZSBhbmQgY29udHJpYnV0
ZSwgeW91IHNob3VsZCByZWFkIHRoZSBjaGFwdGVyIG9mIHRoaXMgbGlzdDoNCg0KaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL3JmYzMwMDUNCg0KQXMgeW914oCZcmUgc3VibWl0dGluZyBhIGRv
Y3VtZW50IHRvIHRoZSBpbnQtYXJlYSAoYWNjb3JkaW5nIHRvIHRoZSBkb2N1bWVudCBuYW1pbmcp
LCB0aGlzIHByb2JhYmx5IGlzIHRoZSByaWdodCBsaXN0IGZvciB0aGF0IGRvY3VtZW50IGRpc2N1
c3Npb24sIGJ1dCBpbiBhbnkgY2FzZSB0aGUgZG9jdW1lbnQgc2hvdWxkIG5vdCBiZSBmb3J3YXJk
ZWQgdG8gYW55IGxpc3QsIGp1c3QgdGhlIGxpbmtzIG9uY2UgcHVibGlzaGVkIGJ5IHRoZSBSRkMg
ZWRpdG9yLg0KDQpJZiB5b3Uga2VlcCBpbnNpc3RpbmcsIEkgd2lsbCBoYXZlIG5vIG90aGVyIG9w
dGlvbiB0aGFuIHJlc3RyaWN0aW5nIHlvdXIgcG9zdGluZyByaWdodHMgaW4gdGhpcyBsaXN0LCBo
b3BlZnVsbHkgd2UgY2FuIGF2b2lkIHRoYXQuDQoNCkhhdCBvZmYuDQoNCkkgdGhpbmsgaWYgeW91
4oCZcmUgd29ya2luZyBpbiBhIHJvdXRpbmcgZG9jdW1lbnQsIHRoZSByaWdodCBwbGFjZSBpcyB0
aGUgcm91dGluZy1hcmVhIG9yIGEgbW9yZSBzcGVjaWZpYyBXRywgbm90IGludC1hcmVhLg0KDQpC
eSB0aGUgd2F5LCBpZiB0aGF04oCZcyB1c2VmdWwgZm9yIHlvdSwgdGhlIHN1Ym1pc3Npb24gb2Yg
dGhlIGRvY3VtZW50cyBpcyBkb25lIGF1dG9tYXRpY2FsbHkgaGVyZToNCg0KaHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9zdWJtaXQvDQoNCllvdSBjYW4gY2hlY2sgeW91ciBYTUwgZmlsZSBo
ZXJlOg0KDQpodHRwczovL3htbDJyZmMudG9vbHMuaWV0Zi5vcmcvDQoNCkxhc3QsIGJ1dCBub3Qg
bGVhc3QsIHlvdSBzaG91bGQgcmVhZCB3aXRoIGNhcmUgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvdGFv
Lmh0bWwsIGFuZCBtb3JlIGdlbmVyaWMgbGluayBhdCBodHRwczovL3d3dy5pZXRmLm9yZy9uZXdj
b21lcnMuaHRtbC4NCg0KUmVnYXJkcywNCkpvcmRpDQoNCg0KLS0tLS1NZW5zYWplIG9yaWdpbmFs
LS0tLS0NCkRlOiBpZXRmIGVuIG5vbWJyZSBkZSBLaGFsZWQgT21hcg0KUmVzcG9uZGVyIGE6DQpG
ZWNoYTogbWnDqXJjb2xlcywgMTIgZGUgYWJyaWwgZGUgMjAxNywgMTg6MTMNClBhcmE6ICJpZXRm
LWRyYWZ0LXN1Ym1pc3Npb25AaWV0Zi5vcmciDQpDQzogImlldGZAaWV0Zi5vcmciDQpBc3VudG86
IEtoYWxlZCBSb3V0aW5nIFByb3RvY29sIChLUlApIElEIFN1Ym1pc3Npb24uDQoNCkhpIEphc21p
bmUsDQoNClBsZWFzZSB1cGxvYWQgdGhlIDJuZCBJRCBhdHRhY2hlZC4NCg0KTG9va2luZyBmb3Ig
YW4gYWR2YW5jZWQgZGlzY3Vzc2lvbiB0byB0YWtlIHRoaXMgSUQgZm9yd2FyZC4NCg0KQmVzdCBS
ZWdhcmRzLA0KDQpLaGFsZWQgT21hcg0KDQoNCg0KDQoNCioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioNCklQdjQgaXMgb3Zlcg0KQXJlIHlvdSByZWFkeSBmb3Ig
dGhlIG5ldyBJbnRlcm5ldCA/DQpodHRwOi8vd3d3LmNvbnN1bGludGVsLmVzDQpUaGUgSVB2NiBD
b21wYW55DQoNClRoaXMgZWxlY3Ryb25pYyBtZXNzYWdlIGNvbnRhaW5zIGluZm9ybWF0aW9uIHdo
aWNoIG1heSBiZSBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbC4gVGhlIGluZm9ybWF0aW9uIGlz
IGludGVuZGVkIHRvIGJlIGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsKHMpIG5hbWVkIGFi
b3ZlLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGJlIGF3YXJlIHRoYXQg
YW55IGRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiBvciB1c2Ugb2YgdGhlIGNvbnRl
bnRzIG9mIHRoaXMgaW5mb3JtYXRpb24sIGluY2x1ZGluZyBhdHRhY2hlZCBmaWxlcywgaXMgcHJv
aGliaXRlZC4NCg0KDQoNCg==

--_000_AM4PR0401MB2241689CED212EF6C7F2E66ABD030AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <6FE159E035976348AD840997B659CCDE@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSGksPGJyPg0KPGJy
Pg0KSSBzZW50IG15IDJuZCBJRCB0byBhbGwgdGhlIGlldGYgbGlzdCBhcyB3ZWxsIHNvIEkgY2Fu
IGZpbmQgYSBzdWdnZXN0aW9uIHdoZXJlIHRoaXMgSUQgc2hvdWxkIGJlIGRpc2N1c3NlZCBhbmQg
dGhvc2Ugb24gdGhlIGxpc3QgY2FuIGtub3cgYWJvdXQgS0hBTEVEIFJvdXRpbmcgUHJvdG9jb2wg
KEtSUCkgc28gbWF5YmUgc29tZW9uZSBpcyBpbnRlcmVzdGVkIGluIG15IG5ldyBkcmFmdCBhcyB0
aGVyZSBhcmUgdGhpbmdzIGV4cGVjdGVkIHRvIGJlIGFkZGVkDQogdG8gbWFrZSB0aGlzIElEIGlu
IHRoZSBiZXN0IGZvcm0uPGJyPg0KPGJyPg0KQmVzdCByZWdhcmRzLDxicj4NCjxicj4NCktoYWxl
ZCBPbWFyDQo8ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4N
Cjxicj4NCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBS
ZTogS2hhbGVkIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCkgSUQgU3VibWlzc2lvbi48YnI+DQpGcm9t
OiBKT1JESSBQQUxFVCBNQVJUSU5FWiA8am9yZGkucGFsZXRAY29uc3VsaW50ZWwuZXM+PGJyPg0K
VG86IGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTxicj4NCkNDOiBpZXRmQGlldGYub3JnPGJy
Pg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90
ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3Bh
ZGRpbmctbGVmdDoxZXgiPg0KSGkgS2hhbGVkLDxicj4NCjxicj4NClNwZWFraW5nIGFzIHNlcmdl
YW50LWF0LWFybXMuPGJyPg0KPGJyPg0KU2V2ZXJhbCBmb2xrcywgaW5jbHVkaW5nIG15c2VsZiwg
aGF2ZSBleHBsYWluZWQgeW91LCBzZXZlcmFsIHRpbWVzLCB0aGF0IGl0IGlzIGluYXBwcm9wcmlh
dGUgdG8gc2VuZCBkb2N1bWVudHMgdG8gdGhpcyBsaXN0LCBldmVuIGxlc3Mgd2hlbiB0aGV5IGhh
dmUgYSBzcGVjaWZpYyB2ZW51ZSBmb3IgdGhlaXIgZGlzY3Vzc2lvbi48YnI+DQo8YnI+DQpJZiB5
b3Ugd2FudCB0byBwYXJ0aWNpcGF0ZSBhbmQgY29udHJpYnV0ZSwgeW91IHNob3VsZCByZWFkIHRo
ZSBjaGFwdGVyIG9mIHRoaXMgbGlzdDo8YnI+DQo8YnI+DQpodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvcmZjMzAwNTxicj4NCjxicj4NCkFzIHlvdeKAmXJlIHN1Ym1pdHRpbmcgYSBkb2N1bWVu
dCB0byB0aGUgaW50LWFyZWEgKGFjY29yZGluZyB0byB0aGUgZG9jdW1lbnQgbmFtaW5nKSwgdGhp
cyBwcm9iYWJseSBpcyB0aGUgcmlnaHQgbGlzdCBmb3IgdGhhdCBkb2N1bWVudCBkaXNjdXNzaW9u
LCBidXQgaW4gYW55IGNhc2UgdGhlIGRvY3VtZW50IHNob3VsZCBub3QgYmUgZm9yd2FyZGVkIHRv
IGFueSBsaXN0LCBqdXN0IHRoZSBsaW5rcyBvbmNlIHB1Ymxpc2hlZCBieSB0aGUgUkZDIGVkaXRv
ci48YnI+DQo8YnI+DQpJZiB5b3Uga2VlcCBpbnNpc3RpbmcsIEkgd2lsbCBoYXZlIG5vIG90aGVy
IG9wdGlvbiB0aGFuIHJlc3RyaWN0aW5nIHlvdXIgcG9zdGluZyByaWdodHMgaW4gdGhpcyBsaXN0
LCBob3BlZnVsbHkgd2UgY2FuIGF2b2lkIHRoYXQuPGJyPg0KPGJyPg0KSGF0IG9mZi48YnI+DQo8
YnI+DQpJIHRoaW5rIGlmIHlvdeKAmXJlIHdvcmtpbmcgaW4gYSByb3V0aW5nIGRvY3VtZW50LCB0
aGUgcmlnaHQgcGxhY2UgaXMgdGhlIHJvdXRpbmctYXJlYSBvciBhIG1vcmUgc3BlY2lmaWMgV0cs
IG5vdCBpbnQtYXJlYS48YnI+DQo8YnI+DQpCeSB0aGUgd2F5LCBpZiB0aGF04oCZcyB1c2VmdWwg
Zm9yIHlvdSwgdGhlIHN1Ym1pc3Npb24gb2YgdGhlIGRvY3VtZW50cyBpcyBkb25lIGF1dG9tYXRp
Y2FsbHkgaGVyZTo8YnI+DQo8YnI+DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL3N1Ym1p
dC88YnI+DQo8YnI+DQpZb3UgY2FuIGNoZWNrIHlvdXIgWE1MIGZpbGUgaGVyZTo8YnI+DQo8YnI+
DQpodHRwczovL3htbDJyZmMudG9vbHMuaWV0Zi5vcmcvPGJyPg0KPGJyPg0KTGFzdCwgYnV0IG5v
dCBsZWFzdCwgeW91IHNob3VsZCByZWFkIHdpdGggY2FyZSBodHRwczovL3d3dy5pZXRmLm9yZy90
YW8uaHRtbCwgYW5kIG1vcmUgZ2VuZXJpYyBsaW5rIGF0IGh0dHBzOi8vd3d3LmlldGYub3JnL25l
d2NvbWVycy5odG1sLjxicj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KSm9yZGk8YnI+DQo8YnI+DQo8
YnI+DQotLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLTxicj4NCkRlOiBpZXRmIDxpZXRmLWJvdW5j
ZXNAaWV0Zi5vcmc+ZW4gbm9tYnJlIGRlIEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90
bWFpbC5jb20+DQo8YnI+DQpSZXNwb25kZXIgYTogPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNv
bT48YnI+DQpGZWNoYTogbWnDqXJjb2xlcywgMTIgZGUgYWJyaWwgZGUgMjAxNywgMTg6MTM8YnI+
DQpQYXJhOiAmcXVvdDtpZXRmLWRyYWZ0LXN1Ym1pc3Npb25AaWV0Zi5vcmcmcXVvdDsgPGlldGYt
ZHJhZnQtc3VibWlzc2lvbkBpZXRmLm9yZz48YnI+DQpDQzogJnF1b3Q7aWV0ZkBpZXRmLm9yZyZx
dW90OyA8aWV0ZkBpZXRmLm9yZz48YnI+DQpBc3VudG86IEtoYWxlZCBSb3V0aW5nIFByb3RvY29s
IChLUlApIElEIFN1Ym1pc3Npb24uPGJyPg0KPGJyPg0KSGkgSmFzbWluZSw8YnI+DQo8YnI+DQpQ
bGVhc2UgdXBsb2FkIHRoZSAybmQgSUQgYXR0YWNoZWQuPGJyPg0KPGJyPg0KTG9va2luZyBmb3Ig
YW4gYWR2YW5jZWQgZGlzY3Vzc2lvbiB0byB0YWtlIHRoaXMgSUQgZm9yd2FyZC48YnI+DQo8YnI+
DQpCZXN0IFJlZ2FyZHMsPGJyPg0KPGJyPg0KS2hhbGVkIE9tYXIgPGJyPg0KPGJyPg0KPGJyPg0K
PGJyPg0KPGJyPg0KPGJyPg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKjxicj4NCklQdjQgaXMgb3Zlcjxicj4NCkFyZSB5b3UgcmVhZHkgZm9yIHRoZSBuZXcg
SW50ZXJuZXQgPzxicj4NCmh0dHA6Ly93d3cuY29uc3VsaW50ZWwuZXM8YnI+DQpUaGUgSVB2NiBD
b21wYW55PGJyPg0KPGJyPg0KVGhpcyBlbGVjdHJvbmljIG1lc3NhZ2UgY29udGFpbnMgaW5mb3Jt
YXRpb24gd2hpY2ggbWF5IGJlIHByaXZpbGVnZWQgb3IgY29uZmlkZW50aWFsLiBUaGUgaW5mb3Jt
YXRpb24gaXMgaW50ZW5kZWQgdG8gYmUgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwocykg
bmFtZWQgYWJvdmUuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgYmUgYXdh
cmUgdGhhdCBhbnkgZGlzY2xvc3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uIG9yDQogdXNlIG9m
IHRoZSBjb250ZW50cyBvZiB0aGlzIGluZm9ybWF0aW9uLCBpbmNsdWRpbmcgYXR0YWNoZWQgZmls
ZXMsIGlzIHByb2hpYml0ZWQuPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM4PR0401MB2241689CED212EF6C7F2E66ABD030AM4PR0401MB2241_--


From nobody Wed Apr 12 13:58:25 2017
Return-Path: <aretana@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12DB91273B1 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 13:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 U_SQLrwfGyLt for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 13:58:22 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E905127369 for <ietf@ietf.org>; Wed, 12 Apr 2017 13:58:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10180; q=dns/txt; s=iport; t=1492030702; x=1493240302; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lLffsZxEzVNaOBdqYBSWTguNlv6RFK0F8wjD9nTA7mY=; b=J24891/lrcDJPQD8EydQajgOnvDYiDsAGZ+uo1kmNd0Yd0LtcLnpxmwl ZcfONNN2UjQUxDT6Vur9Ra/fihVxTmvU+vbola2UMoz3406K6G2J9bRPr odyCOgHRPoCHZsXb1vKUW4FI5XPA6TdJQcPRpbkNEbbl27TcaRiLXUu3U A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DDAwBClO5Y/49dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm46K2GBCweDX4oTkTWCWYVgiAqFNYIPKIV8AhqDZz8YAQIBAQE?= =?us-ascii?q?BAQEBayiFFgYjVhACAQgOMQMCAgIwFBEBAQQBDQWJfgMVqVeCJiuKZgEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBARgFhlGBXSsJgmOBPAGBFIULLoIxBZYnhig7AY4ehEK?= =?us-ascii?q?Bf4UuiheLAoh/AR84gQVbFUERAYRVgXN1AYgUgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,191,1488844800";  d="scan'208,217";a="410740246"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Apr 2017 20:58:21 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3CKwLqY031864 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Apr 2017 20:58:21 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Apr 2017 15:58:20 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Wed, 12 Apr 2017 15:58:20 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: "routing-area@ietf.com" <routing-area@ietf.com>, ietf <ietf@ietf.org>
Subject: Re: Khaled Routing Protocol (KRP) ID Submission.
Thread-Topic: Khaled Routing Protocol (KRP) ID Submission.
Thread-Index: AdKzp1CRFd0eQahqTpyMvf6uY+qORAAMJSGA
Date: Wed, 12 Apr 2017 20:58:20 +0000
Message-ID: <CDD5DCA6-4722-4C7A-92E3-501AA25C547A@cisco.com>
References: <D7707E4B-CD37-478A-B640-47148DE3276A@consulintel.es> <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: multipart/alternative; boundary="_000_CDD5DCA647224C7A92E3501AA25C547Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KCGg1rTYXt0TIfJ2rTyZyu1bKvs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 20:58:24 -0000

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

S2hhbGVkOg0KDQpIaSENCg0KSSB0b29rIGEgcXVpY2sgbG9vayBhdCB5b3VyIGRyYWZ0LiAgSXQg
c2VlbXMgdG8gYmUgcHJvcG9zaW5nIGEgd2F5IHRvIGFzc2lnbiBJUCBhZGRyZXNzZXMgc28gdGhh
dCB0aGV5IGNvbnRhaW4gaW5mb3JtYXRpb24gYWJvdXQgcmVnaW9ucyBhbmQgYXV0b25vbW91cyBz
eXN0ZW1zIOKAkyBhbmQgdGhlbiBzdWdnZXN0aW5nIHRoYXQgZm9yd2FyZGluZyBjYW4gYmUgZG9u
ZSBiYXNlZCBvbiB0aGF0LiAgQnV0IHlvdSBhcmUgbm90IHByb3Bvc2luZyBhIHJvdXRpbmcgcHJv
dG9jb2wgKHBhY2tldCBmb3JtYXRzLCBwcm90b2NvbCBkZXRhaWxzLCBldGMuKS4uLg0KDQpOb3Rl
IHRoYXQgdGhlIElFVEYgaGFzIGJlZW4gcmVzcG9uc2libGUgZm9yIGRlZmluaW5nIElQdjQvSVB2
NiwgYnV0IGl0IGlzIG5vdCByZXNwb25zaWJsZSBmb3IgdGhlIGFzc2lnbm1lbnQgb2YgSVAgYWRk
cmVzc2VzLCB3aGljaCBzZWVtcyB0byBiZSB0aGUgY2VudHJhbCBwb2ludCBvZiB5b3VyIHByb3Bv
c2FsLiAgSUFOQSBpcyByZXNwb25zaWJsZSBmb3IgYWxsb2NhdGluZyBhZGRyZXNzIGJsb2NrcyB0
byB0aGUgcmVnaW9uYWwgcmVnaXN0cmllcyBbMV0sIGJ1dCB0aGUgYWxsb2NhdGlvbiBoYXMgYWxy
ZWFkeSBiZWVuIHN1Y2ggdGhhdCBpdCBpcyB0b28gbGF0ZSB0byBjaGFuZ2UgdGhlIHBvbGljaWVz
ICh3aGljaCBhcmUgbm90IHNldCBieSB0aGUgSUVURiBlaXRoZXIpIHRvIG1hdGNoIHdoYXQgeW91
IHByb3Bvc2UuDQoNCkkgcmVjb21tZW5kIHRoYXQgeW91IHJldmlldyB0aGUgZXhpc3RpbmcgcG9s
aWNpZXMgYW5kIHdoYXQgZWFjaCBvcmdhbml6YXRpb24gaXMgaW4gY2hhcmdlIG9mIGRvaW5nIGJl
Zm9yZSB3cml0aW5nIGFub3RoZXIgcHJvcG9zYWwuDQoNCklmIHlvdSB3YW50IHRvIGhhdmUgZnVy
dGhlciBkaXNjdXNzaW9ucyBvbiB0aGlzIHRvcGljLCBwbGVhc2UgZmVlbCBmcmVlIHRvIGNvbnRh
Y3QgbWUgZGlyZWN0bHkuDQoNClJlZ2FyZHMsDQoNCkFsdmFyby4NCg0KDQpbMV0gaHR0cHM6Ly93
d3cuaWFuYS5vcmcvbnVtYmVycw0KDQpPbiA0LzEyLzE3LCA0OjE3IFBNLCAiaWV0ZiBvbiBiZWhh
bGYgb2YgS2hhbGVkIE9tYXIiIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOmlldGYtYm91
bmNlc0BpZXRmLm9yZz4gb24gYmVoYWxmIG9mIGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTxt
YWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPj4gd3JvdGU6DQoNCkkgc2VudCBteSAy
bmQgSUQgdG8gYWxsIHRoZSBpZXRmIGxpc3QgYXMgd2VsbCBzbyBJIGNhbiBmaW5kIGEgc3VnZ2Vz
dGlvbiB3aGVyZSB0aGlzIElEIHNob3VsZCBiZSBkaXNjdXNzZWQgYW5kIHRob3NlIG9uIHRoZSBs
aXN0IGNhbiBrbm93IGFib3V0IEtIQUxFRCBSb3V0aW5nIFByb3RvY29sIChLUlApIHNvIG1heWJl
IHNvbWVvbmUgaXMgaW50ZXJlc3RlZCBpbiBteSBuZXcgZHJhZnQgYXMgdGhlcmUgYXJlIHRoaW5n
cyBleHBlY3RlZCB0byBiZSBhZGRlZCB0byBtYWtlIHRoaXMgSUQgaW4gdGhlIGJlc3QgZm9ybS4N
Cg0K

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTotd2Via2l0LXN0YW5kYXJkOw0KCXBhbm9zZS0xOjAgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KLyog
U3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29O
b3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXpl
OjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQphOmxpbmssIHNwYW4u
TXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRl
eHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0Zv
bGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseTpDYWxpYnJpOw0KCWNvbG9yOndpbmRvd3Rl
eHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsO30NCnNwYW4ubXNv
SW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCW1zby1zdHlsZS1uYW1lOiIiOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJY29sb3I6dGVhbDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w
aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVT
IiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTpDYWxpYnJpIj5LaGFsZWQ6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2Fs
aWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SGkhPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SSB0b29rIGEgcXVpY2sgbG9vayBhdCB5b3VyIGRyYWZ0
LiZuYnNwOyBJdCBzZWVtcyB0byBiZSBwcm9wb3NpbmcgYSB3YXkgdG8gYXNzaWduIElQIGFkZHJl
c3NlcyBzbyB0aGF0IHRoZXkgY29udGFpbiBpbmZvcm1hdGlvbiBhYm91dCByZWdpb25zIGFuZCBh
dXRvbm9tb3VzIHN5c3RlbXMg4oCTIGFuZCB0aGVuIHN1Z2dlc3RpbmcgdGhhdA0KIGZvcndhcmRp
bmcgY2FuIGJlIGRvbmUgYmFzZWQgb24gdGhhdC4mbmJzcDsgQnV0IHlvdSBhcmUgbm90IHByb3Bv
c2luZyBhIHJvdXRpbmcgcHJvdG9jb2wgKHBhY2tldCBmb3JtYXRzLCBwcm90b2NvbCBkZXRhaWxz
LCBldGMuKS4uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPk5vdGUgdGhhdCB0aGUgSUVURiBo
YXMgYmVlbiByZXNwb25zaWJsZSBmb3IgZGVmaW5pbmcgSVB2NC9JUHY2LCBidXQgaXQgaXMgbm90
IHJlc3BvbnNpYmxlIGZvciB0aGUgYXNzaWdubWVudCBvZiBJUCBhZGRyZXNzZXMsIHdoaWNoIHNl
ZW1zIHRvIGJlIHRoZSBjZW50cmFsIHBvaW50IG9mIHlvdXIgcHJvcG9zYWwuJm5ic3A7IElBTkEN
CiBpcyByZXNwb25zaWJsZSBmb3IgYWxsb2NhdGluZyBhZGRyZXNzIGJsb2NrcyB0byB0aGUgcmVn
aW9uYWwgcmVnaXN0cmllcyBbMV0sIGJ1dCB0aGUgYWxsb2NhdGlvbiBoYXMgYWxyZWFkeSBiZWVu
IHN1Y2ggdGhhdCBpdCBpcyB0b28gbGF0ZSB0byBjaGFuZ2UgdGhlIHBvbGljaWVzICh3aGljaCBh
cmUgbm90IHNldCBieSB0aGUgSUVURiBlaXRoZXIpIHRvIG1hdGNoIHdoYXQgeW91IHByb3Bvc2Uu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SSByZWNvbW1lbmQgdGhhdCB5b3UgcmV2aWV3IHRo
ZSBleGlzdGluZyBwb2xpY2llcyBhbmQgd2hhdCBlYWNoIG9yZ2FuaXphdGlvbiBpcyBpbiBjaGFy
Z2Ugb2YgZG9pbmcgYmVmb3JlIHdyaXRpbmcgYW5vdGhlciBwcm9wb3NhbC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTpDYWxpYnJpIj5JZiB5b3Ugd2FudCB0byBoYXZlIGZ1cnRoZXIgZGlzY3Vzc2lvbnMgb24g
dGhpcyB0b3BpYywgcGxlYXNlIGZlZWwgZnJlZSB0byBjb250YWN0IG1lIGRpcmVjdGx5LjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNhbGlicmkiPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+
QWx2YXJvLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNhbGlicmkiPlsxXSA8YSBocmVmPSJodHRwczovL3d3dy5pYW5hLm9yZy9u
dW1iZXJzIj4NCmh0dHBzOi8vd3d3LmlhbmEub3JnL251bWJlcnM8L2E+IDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gNC8xMi8xNywgNDoxNyBQTSwgJnF1
b3Q7aWV0ZiBvbiBiZWhhbGYgb2YgS2hhbGVkIE9tYXImcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0
bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmciPmlldGYtYm91bmNlc0BpZXRmLm9yZzwvYT4gb24gYmVo
YWxmIG9mDQo8YSBocmVmPSJtYWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tIj5lbmcu
a2hhbGVkLm9tYXJAaG90bWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90Oy13ZWJraXQtc3RhbmRhcmQmcXVvdDssJnF1b3Q7
c2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPkkgc2VudCBteSAybmQgSUQgdG8gYWxsIHRoZSBpZXRm
IGxpc3QgYXMgd2VsbCBzbyBJIGNhbiBmaW5kIGEgc3VnZ2VzdGlvbiB3aGVyZSB0aGlzIElEIHNo
b3VsZCBiZSBkaXNjdXNzZWQgYW5kIHRob3NlIG9uIHRoZSBsaXN0IGNhbiBrbm93IGFib3V0IEtI
QUxFRCBSb3V0aW5nDQogUHJvdG9jb2wgKEtSUCkgc28gbWF5YmUgc29tZW9uZSBpcyBpbnRlcmVz
dGVkIGluIG15IG5ldyBkcmFmdCBhcyB0aGVyZSBhcmUgdGhpbmdzIGV4cGVjdGVkIHRvIGJlIGFk
ZGVkIHRvIG1ha2UgdGhpcyBJRCBpbiB0aGUgYmVzdCBmb3JtLjwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7LXdlYmtpdC1zdGFuZGFyZCZxdW90OywmcXVvdDtzZXJpZiZxdW90
Oztjb2xvcjpibGFjayI+PGJyIHN0eWxlPSJmb250LXZhcmlhbnQtY2Fwczogbm9ybWFsO29ycGhh
bnM6IGF1dG87dGV4dC1hbGlnbjpzdGFydDt3aWRvd3M6IGF1dG87LXdlYmtpdC10ZXh0LXN0cm9r
ZS13aWR0aDogMHB4O3dvcmQtc3BhY2luZzowcHgiPg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CDD5DCA647224C7A92E3501AA25C547Aciscocom_--


From nobody Wed Apr 12 14:14:31 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7CB12EB53 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 14:14:29 -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, RP_MATCHES_RCVD=-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 kqoY8wjbbidI for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 14:14:28 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6949B129ACD for <ietf@ietf.org>; Wed, 12 Apr 2017 14:14:28 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cyPas-000ETB-10; Wed, 12 Apr 2017 17:14:26 -0400
Date: Wed, 12 Apr 2017 17:14:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
cc: ietf <ietf@ietf.org>
Subject: Re: Khaled Routing Protocol (KRP) ID Submission.
Message-ID: <D6B9456162B8E9F798A4C3DA@PSB>
In-Reply-To: <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <D7707E4B-CD37-478A-B640-47148DE3276A@consulintel.es> <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5_W5b_Q1_IIGXV_nNHPRzX_a4HE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 21:14:30 -0000

Khaled,

You have been asked repeatedly, on and off list, to not try to
post I-Ds to this mailing list.  If you want comments on a
draft, get that draft posted, then ask for  comments and input
(something Jordi's note mentioned but that has also been said
before).

If you are unwilling or unable to do that, you should reasonably
expect that people will become annoyed at you, something that
does not encourage them to study and review the draft, and that
people will reach the conclusion that you are being
intentionally disruptive and request that your posting rights be
suspended sooner rather than later.

As before, if you need help getting drafts posted or otherwise
navigating the IETF system, there are several of us who are
willing to try to help if you write us off list.    But, at
least for me and perhaps others, a condition for that help is
that you try to understand the IETF's way of working and conform
to it.

regards,
   john



--On Wednesday, April 12, 2017 20:17 +0000 Khaled Omar
<eng.khaled.omar@hotmail.com> wrote:

> Hi,
> 
> I sent my 2nd ID to all the ietf list as well so I can find a
> suggestion where this ID should be discussed and those on the
> list can know about KHALED Routing Protocol (KRP) so maybe
> someone is interested in my new draft as there are things
> expected to be added to make this ID in the best form.





From nobody Wed Apr 12 16:40:31 2017
Return-Path: <ldaigle@thinkingcat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D0E129AD5; Wed, 12 Apr 2017 16:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.589
X-Spam-Level: 
X-Spam-Status: No, score=-4.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=thinkingcat.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 sohvSJGBJSvy; Wed, 12 Apr 2017 16:40:19 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28BDE12947E; Wed, 12 Apr 2017 16:40:19 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id B2483D000083D; Wed, 12 Apr 2017 16:40:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:references:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=t82zclG/SkjSJS t+nt8Ps0CKCeg=; b=inZ9tp/IOybI/dn+nIOXX0d5grjpXwj+HY131cJ+OgQ4bk mU9oDNv5YRWsQntlDEqVYGATCX9ikz9fcJHaFj80d3wivbsnXjc2A2jJyoXHGjO7 e2GdPdEUZlmpxssdlNqnTM0dLBYS/ZQ6TM48Hjy8FL8ab79KGxk4N5HhiqjSk=
Received: from [192.168.1.5] (pool-173-72-147-193.clppva.fios.verizon.net [173.72.147.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPSA id 3EF33D000083C; Wed, 12 Apr 2017 16:40:18 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Cc: IAOC@ietf.org
Subject: Fwd: Update on feedback on US-based meetings, and IETF 102
Date: Wed, 12 Apr 2017 19:40:17 -0400
Message-ID: <F21BFB22-BA7D-411B-BF13-141CD6886621@thinkingcat.com>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_96A31A1A-19EE-4A76-9C48-081116344796_="
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ui4XJ7F-ZHjxDUa8HPl9XsTFBB8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 23:40:23 -0000

--=_MailMate_96A31A1A-19EE-4A76-9C48-081116344796_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable


FYI =E2=80=94 this is the information as we have it.

Leslie.

--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------

Forwarded message:

> From: IAOC Chair <iaoc-chair@ietf.org>
> To: IETF Announcement List <ietf-announce@ietf.org>
> Subject: Update on feedback on US-based meetings, and IETF 102
> Date: Wed, 12 Apr 2017 16:39:18 -0700
>
> On March 31, 2017, we put out a request for input on experiences with=20
> travel to the recent IETF meeting in the US, and solicited information=20
> pertinent to plans to attend IETF meetings within or outside the US in=20
> the coming years.  We have had over 350 responses to the=20
> questionnaire, and we appreciate each and every one of them!   We did=20
> not gather the data in such a way for it to reflect a representative=20
> sample of the IETF community, or of potential meeting attendees. But=20
> we did gain insights from those who responded that we did not have=20
> before.
>
> Over 40% of the respondents said they had attended 20 or more IETF=20
> meetings, and over 50% of them said they were authors of active=20
> working group documents.  Slightly more than 40% stated US residency,=20
> and just less than 60% said they were not US-resident.
>
> There was a noted impact of the recent changes to US travel policies=20
> and procedures.  Of the respondents living outside of the US who did=20
> NOT attend the IETF meeting in Chicago, a few were denied visas or=20
> entry into the US, and more than 30 said they did not come because of=20
> concerns about US travel restrictions.  On the other hand 45 people=20
> said they were not troubled by the US situation (and presumably chose=20
> not to come for other reasons).
>
> For those who did travel to IETF 98 in Chicago, the written comments=20
> were illuminating:  most people had no issues (for some, even a=20
> smoother border crossing than usual); some people experienced the=20
> expected flutter over visa approvals as things were in flux as the US=20
> Executive Order and court stays played out, but were eventually able=20
> to come.
>
> The general comments on meeting in the US played along the same lines=20
> as has been shared on the IETF discussion list:  people are variously=20
> for moving all meetings out of the US, or adamantly against, or=20
> somewhere in between, each position supported by good reasons.
>
> The IAOC is continuing to gather data on travel to the US, concerns=20
> about traveling outside of it, and what alternatives are possible for=20
> IETF 102.  Our focus is currently on whether holding IETF 102 in San=20
> Francisco is the best option to meet the needs of IETF work,=20
> recognizing that we cannot predict the future.  While it may take=20
> several weeks to allow for review and negotiation of any alternatives=20
> (if applicable), we are moving as quickly as possible because we=20
> realize that people will need time to plan their travel.
>
>
> Leslie, for the IAOC.

--=_MailMate_96A31A1A-19EE-4A76-9C48-081116344796_=
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 http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">FYI =E2=80=94 this is the information as we have it.</p>

<p dir=3D"auto">Leslie.</p>

<p dir=3D"auto">-- </p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">Leslie Daigle<br>
Principal, ThinkingCat Enterprises LLC</p>

<h2 style=3D"font-size:1.2em"><a href=3D"mailto:ldaigle@thinkingcat.com" =
style=3D"color:#3983C4">ldaigle@thinkingcat.com</a></h2>

<p dir=3D"auto">Forwarded message:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">From: IAOC Chair <a href=3D"mailto:iaoc-chair@ietf.org" s=
tyle=3D"color:#777">iaoc-chair@ietf.org</a><br>
To: IETF Announcement List <a href=3D"mailto:ietf-announce@ietf.org" styl=
e=3D"color:#777">ietf-announce@ietf.org</a><br>
Subject: Update on feedback on US-based meetings, and IETF 102<br>
Date: Wed, 12 Apr 2017 16:39:18 -0700</p>

<p dir=3D"auto">On March 31, 2017, we put out a request for input on expe=
riences with travel to the recent IETF meeting in the US, and solicited i=
nformation pertinent to plans to attend IETF meetings within or outside t=
he US in the coming years.  We have had over 350 responses to the questio=
nnaire, and we appreciate each and every one of them!   We did not gather=
 the data in such a way for it to reflect a representative sample of the =
IETF community, or of potential meeting attendees. But we did gain insigh=
ts from those who responded that we did not have before.</p>

<p dir=3D"auto">Over 40% of the respondents said they had attended 20 or =
more IETF meetings, and over 50% of them said they were authors of active=
 working group documents.  Slightly more than 40% stated US residency, an=
d just less than 60% said they were not US-resident.</p>

<p dir=3D"auto">There was a noted impact of the recent changes to US trav=
el policies and procedures.  Of the respondents living outside of the US =
who did NOT attend the IETF meeting in Chicago, a few were denied visas o=
r entry into the US, and more than 30 said they did not come because of c=
oncerns about US travel restrictions.  On the other hand 45 people said t=
hey were not troubled by the US situation (and presumably chose not to co=
me for other reasons).</p>

<p dir=3D"auto">For those who did travel to IETF 98 in Chicago, the writt=
en comments were illuminating:  most people had no issues (for some, even=
 a smoother border crossing than usual); some people experienced the expe=
cted flutter over visa approvals as things were in flux as the US Executi=
ve Order and court stays played out, but were eventually able to come.</p=
>

<p dir=3D"auto">The general comments on meeting in the US played along th=
e same lines as has been shared on the IETF discussion list:  people are =
variously for moving all meetings out of the US, or adamantly against, or=
 somewhere in between, each position supported by good reasons.</p>

<p dir=3D"auto">The IAOC is continuing to gather data on travel to the US=
, concerns about traveling outside of it, and what alternatives are possi=
ble for IETF 102.  Our focus is currently on whether holding IETF 102 in =
San Francisco is the best option to meet the needs of IETF work, recogniz=
ing that we cannot predict the future.  While it may take several weeks t=
o allow for review and negotiation of any alternatives (if applicable), w=
e are moving as quickly as possible because we realize that people will n=
eed time to plan their travel.</p>

<p dir=3D"auto">Leslie, for the IAOC.</p>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_96A31A1A-19EE-4A76-9C48-081116344796_=--


From nobody Wed Apr 12 17:01:09 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38BB9128C84; Wed, 12 Apr 2017 17:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 BIoxUeQGrT8T; Wed, 12 Apr 2017 17:00:58 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43F8F12871F; Wed, 12 Apr 2017 17:00:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D5985BEE3; Thu, 13 Apr 2017 01:00:54 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pvVEepV95u3; Thu, 13 Apr 2017 01:00:53 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 57109BED4; Thu, 13 Apr 2017 01:00:53 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492041653; bh=v6Qm63emn2SsZnhRBEaWLlLJT2opskGKdFptWC92Cio=; h=Subject:To:References:From:Date:In-Reply-To:From; b=IkdvwE0ZZg6wJzWTJjp1Mi2QL9vw+bOvNkR57cgfdnCe+11/YLOBS3d7VgUmQyUIW QYewwe4e3h3/JSnZoviknkFvIBcNELBTVWbwwgtu5wtvNldqQMAZ6JY7V01Rzx6qpx evjdzho0Q54v7nknf/KzMLz4ppdj0BBMAT5nts3U=
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: ietf@ietf.org, iaoc@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
Date: Thu, 13 Apr 2017 01:00:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AJfRf5fb9MbC5mPCln3mGkTiMJHwUOQlE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v9rUCxXHaMqnEuIvjGcyeMyI5Ko>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 00:01:00 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AJfRf5fb9MbC5mPCln3mGkTiMJHwUOQlE
Content-Type: multipart/mixed; boundary="qdRgR5Wqv5Qttjr4JvOrCXjBHEvDCo49A";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: ietf@ietf.org, iaoc@ietf.org,
 IETF Announcement List <ietf-announce@ietf.org>
Message-ID: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
In-Reply-To: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>

--qdRgR5Wqv5Qttjr4JvOrCXjBHEvDCo49A
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Leslie,

Thanks for the update. One query...

On 13/04/17 00:39, IAOC Chair wrote:
> The general comments on meeting in the US played along the same lines
> as has been shared on the IETF discussion list:  people are variously
> for moving all meetings out of the US, or adamantly against, or
> somewhere in between, each position supported by good reasons.

I have seen mail to the list that argued for not meeting in the US
within our current planing horizon. Some of that was adamant. (For
clarity: I'd agree with the position that we ought not risk meeting
in the US for a few years, incl. that we ought, if possible, move
ietf-102 on the basis that the we don't have a predictable situation
with the US at the moment and that we ought not plan to meet in any
place that's currently that unpredictable.)

I do not recall the opposite on the list, i.e. someone adamantly
arguing that we ought continue to meet in the US. There were some
mails that I'd say maybe weakly argued for continued US meetings
in the relevant timeframe. But nothing approaching adamant.

Is that my bias in reading the list traffic or did I miss some mail,
or is it possible that the (public) list traffic and (relatively
private) survey responses are less similar that your mail implies?

That last wouldn't be surprising, but I'd hope that in that case
some of the people who filled in the survey who adamantly said we
ought continue to meet in the US would be willing to justify that
on the list. If none were, then I think the IAOC ought consider
that as a relevant input in their decision making. (Not as a
winning argument, but as a relevant thing.)

Thanks,
S.


--qdRgR5Wqv5Qttjr4JvOrCXjBHEvDCo49A--

--AJfRf5fb9MbC5mPCln3mGkTiMJHwUOQlE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7r+0AAoJEC88hzaAX42ij8QH/2Ofsr4yAb/Q9aFy8pj0T384
IN0jWHF4uDyI3oXVVrhcqbpxpfJzI4WBvvx5vJKLtj6NDaImnXAt39Rx8P/1VegK
EwhLIVerdp6V6x+N6y/g2aHvO/Jr7F34tubZ3uozRosWlIxSNJYvoW4pbwU4iDfl
+CgoDVzl5dd3SD+WfCh8BxDNA4rmxByZ1cc1YTiAzU1RJgeUA/pKupaYPhNnOVmW
55OVxlUJUGAFeNk56kL22bLtDIRz2m/S/NUULknluvSuMhg42NP/roK2cmRFvMh6
NH/l8NDGHJDEcfg2zr9yNYqeYTiCwcNfgPjMAMGXscXLMXHzZ5gNzREd00tfRKQ=
=0CYh
-----END PGP SIGNATURE-----

--AJfRf5fb9MbC5mPCln3mGkTiMJHwUOQlE--


From nobody Wed Apr 12 17:04:52 2017
Return-Path: <jrmitche@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB8F612786A; Wed, 12 Apr 2017 17:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 Gm2EKuLcl-OM; Wed, 12 Apr 2017 17:04:32 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id A1A2B127599; Wed, 12 Apr 2017 17:04:32 -0700 (PDT)
Received: from [192.168.1.8] (pool-70-106-204-94.clppva.fios.verizon.net [70.106.204.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 072D1540570; Wed, 12 Apr 2017 20:04:30 -0400 (EDT)
Date: Wed, 12 Apr 2017 20:04:28 -0400
Subject: Re: Review of draft-ietf-ippm-twamp-time-format-05
Message-ID: <ad199549-d4b3-4187-81b2-207834d1c8a0@email.android.com>
X-Android-Message-ID: <ad199549-d4b3-4187-81b2-207834d1c8a0@email.android.com>
In-Reply-To: <CA+RyBmWdwf55No_BELKz4TKHiMC-KzGKbmdJNS3zOBRNtiMmag@mail.gmail.com>
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: "	ietf@ietf.org" <ietf@ietf.org>, draft-ietf-ippm-twamp-time-format.all@ietf.org, ops-dir@ietf.org, ippm@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KZ0HDRzYoUMgIBFlFNV1qN1Dzuo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 00:04:34 -0000

PGRpdiBkaXI9J2F1dG8nPjxkaXYgZGlyPSJhdXRvIj48YnI+PC9kaXY+PGRpdiBkaXI9ImF1dG8i
PlNHVE08L2Rpdj48L2Rpdj48ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPjxkaXYgY2xhc3M9
ImdtYWlsX3F1b3RlIj5PbiBBcHIgMTAsIDIwMTcgMTI6MzEsIEdyZWcgTWlyc2t5ICZsdDtncmVn
aW1pcnNreUBnbWFpbC5jb20mZ3Q7IHdyb3RlOjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+PGJsb2Nr
cXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6
MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+PGRpdiBkaXI9Imx0ciI+SGkgSm9uLDxk
aXY+YXBvbG9naWVzIGZvciB0aGUgZXh0ZW5kZWQgZGVsYXkgdG8gYWRkcmVzcyB5b3VyIGNvbW1l
bnQuIEkmIzM5O2QgbGlrZSB0byBhZGQgdGhlIGZvbGxvd2luZyBqdXN0IGJlZm9yZSB0aGUgU2Vj
dGlvbiAyLjE6PC9kaXY+PGRpdj48cHJlIHN0eWxlPSJjb2xvcjpyZ2IoIDAgLCAwICwgMCApO3dv
cmQtd3JhcDpicmVhay13b3JkO3doaXRlLXNwYWNlOnByZS13cmFwIj4gICBJbXBsZW1lbnRhdGlv
bnMgb2YgT1dBTVAgYW5kL29yIFRXQU1QIE1BWSBwcm92aWRlIGEgY29uZmlndXJhdGlvbg0KICAg
a25vYiB0byBieXBhc3MgdGhlIHRpbWVzdGFtcCBmb3JtYXQgbmVnb3RpYXRpb24gcHJvY2VzcyBh
bmQgdG8gdXNlDQogICB0aGUgbG9jYWxseSBjb25maWd1cmVkIHZhbHVlcyBpbnN0ZWFkLg0KPC9w
cmU+PC9kaXY+PGRpdj5Ib3BlIGl0IGNhcHR1cmVzIHRoZSBpZGVhIG9mIGFuZCBhZGRyZXNzZXMg
eW91ciBjb21tZW50LjwvZGl2PjxkaXY+PGJyIC8+PC9kaXY+PGRpdj5SZWdhcmRzLDwvZGl2Pjxk
aXY+R3JlZzwvZGl2PjxkaXY+PGJyIC8+PC9kaXY+PC9kaXY+PGRpdj48YnIgLz48ZGl2IGNsYXNz
PSJlbGlkZWQtdGV4dCI+T24gTW9uLCBNYXIgMjAsIDIwMTcgYXQgMTA6MzQgQU0sIEdyZWcgTWly
c2t5IDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmdyZWdpbWlyc2t5JiM2NDtn
bWFpbC5jb20iPmdyZWdpbWlyc2t5JiM2NDtnbWFpbC5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6
PGJyIC8+PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbjowIDAgMCAwLjhleDtib3JkZXItbGVmdDox
cHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48ZGl2IGRpcj0ibHRyIj5IaSBKb24sPGRp
dj50aGFuayB5b3UgZm9yIGtpbmQgY29uc2lkZXJhdGlvbiBvZiB0aGUgZHJhZnQgYW5kIHRob3Vn
aHRmdWwgY29tbWVudC4gSW5kZWVkLCBUV0FNUCBUZXN0LCBhbmQgdGhlIHRpbWUgc3RhbXAgZm9y
bWF0IHRvIGJlIHVzZWQsIG1heSBiZSBjb250cm9sbGVkIGJ5IG1lYW5zIG90aGVyIHRoYW4gVFdB
TVAgQ29udHJvbCwgZS5nLiwgbG9jYWwgY29uZmlndXJhYmxlIGtub2IgZXhwb3NlZCB2aWEgZGF0
YSBtb2RlbCBvciBDTEkuIEkmIzM5O2xsIHdvcmsgb24gdGV4dCB1cGRhdGVzIGZvciB0aGUgbmV4
dCB2ZXJzaW9uLjwvZGl2PjxkaXY+PGJyIC8+PC9kaXY+PGRpdj5SZWdhcmRzLDwvZGl2PjxkaXY+
R3JlZzwvZGl2PjwvZGl2PjxkaXY+PGRpdj48ZGl2PjxiciAvPjxkaXYgY2xhc3M9ImVsaWRlZC10
ZXh0Ij5PbiBGcmksIE1hciAxNywgMjAxNyBhdCAyOjAxIFBNLCBKb24gTWl0Y2hlbGwgPHNwYW4g
ZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86anJtaXRjaGUmIzY0O3B1Y2submV0aGVyLm5l
dCI+anJtaXRjaGUmIzY0O3B1Y2submV0aGVyLm5ldDwvYT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnIg
Lz48YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luOjAgMCAwIDAuOGV4O2JvcmRlci1sZWZ0OjFweCAj
Y2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPlJldmlld2VyOiBKb24gTWl0Y2hlbGw8YnIgLz4N
ClJldmlldyByZXN1bHQ6IEhhcyBOaXRzPGJyIC8+DQo8YnIgLz4NCkkgaGF2ZSByZXZpZXdlZCB0
aGlzIGRvY3VtZW50IGFzIHBhcnQgb2YgdGhlIE9wZXJhdGlvbmFsIGRpcmVjdG9yYXRlJiMzOTtz
PGJyIC8+DQo8YnIgLz4NCm9uZ29pbmcgZWZmb3J0IHRvIHJldmlldyBhbGwgSUVURiBkb2N1bWVu
dHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZTxiciAvPg0KSUVTRy7CoCBUaGVzZTxiciAvPg0KY29t
bWVudHMgd2VyZSB3cml0dGVuIHdpdGggdGhlIGludGVudCBvZiBpbXByb3ZpbmcgdGhlIG9wZXJh
dGlvbmFsPGJyIC8+DQphc3BlY3RzIG9mIHRoZTxiciAvPg0KSUVURiBkcmFmdHMuIENvbW1lbnRz
IHRoYXQgYXJlIG5vdCBhZGRyZXNzZWQgaW4gbGFzdCBjYWxsIG1heSBiZTxiciAvPg0KaW5jbHVk
ZWQgaW4gQUQgcmV2aWV3czxiciAvPg0KZHVyaW5nIHRoZSBJRVNHIHJldmlldy7CoCBEb2N1bWVu
dCBlZGl0b3JzIGFuZCBXRyBjaGFpcnMgc2hvdWxkIHRyZWF0PGJyIC8+DQp0aGVzZSBjb21tZW50
czxiciAvPg0KanVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuPGJyIC8+DQo8
YnIgLz4NClJlYWR5IHdpdGggTml0cyAtIHRoaXMgZHJhZnQgYWRkcyB0aGUgYWJpbGl0eSB0byB1
c2UgUFRQIHRpbWVzdGFtcHMgYXM8YnIgLz4NCmFuIGFsdGVybmF0aXZlIHRvIE5UUCB0aW1lc3Rh
bXBzIGZvciBhY3RpdmUgcGVyZm9ybWFuY2UgbWVhc3VyZW1lbnQ8YnIgLz4NCnByb3RvY29scyBP
V0FNUCBhbmQgVFdBTVAuwqAgQWx0aG91Z2ggdGhpcyBkcmFmdCBkb2VzIGEgZ29vZCBqb2Igb2Y8
YnIgLz4NCmRpc2N1c3NpbmcgaW50ZXJvcGVyYWJpbGl0eSBmb3IgYm90aCBzaWRlcyBvZiB0aGUg
c2Vzc2lvbiBoYXZpbmcgb3I8YnIgLz4NCm5vdCBoYXZpbmcgc3VwcG9ydCBmb3IgdGhpcyBvcGVy
YXRpb25hbCBjYXBhYmlsaXR5LCBpbiBzZXZlcmFsIHBsYWNlczxiciAvPg0KaXQgc3RhdGVzIHRo
YXQgaWYgYSBzZW5kL3JlY2VpdmVyIHN1cHBvcnQgdGhpcyBjYXBhYmlsaXR5IGl0IG11c3QgYmU8
YnIgLz4NCnNldCB0byAxIGluIHRoZSBmbGFncy7CoCBIb3dldmVyLCBvbmx5IGZvciBUV0FNUCBM
aWdodCBtb2RlLCB0aGlzIHNlZW1zPGJyIC8+DQpjb25maWd1cmFibGUuwqAgVGhpcyBtYXkganVz
dCBiZSBteSBpbnRlcnByZXRhdGlvbiwgYnV0IGl0IHByb2JhYmx5PGJyIC8+DQpzaG91bGQgc3Rh
dGUgdGhhdCBsb2NhbCBpbXBsZW1lbnRhdGlvbnMgTUFZIHByb3ZpZGUgYSBjb25maWd1cmFibGU8
YnIgLz4NCmtub2IgdG8gbm90IG5lZ290aWF0ZSBQVFB2MiB0aW1lc3RhbXBzIGluIHNlY3Rpb24g
Mi4xIGFuZCAyLjIgZXZlbiBpZjxiciAvPg0KdGhlIGNhcGFiaWxpdHkgaXMgc3VwcG9ydGVkIGJ5
IHRoZSBpbXBsZW1lbnRhdGlvbi48YnIgLz4NCjxiciAvPg0KPGJyIC8+DQo8L2Jsb2NrcXVvdGU+
PC9kaXY+PGJyIC8+PC9kaXY+DQo8L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+PGJyIC8+
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2Pg==


From nobody Wed Apr 12 17:27:31 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B949126C83; Wed, 12 Apr 2017 17:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 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_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 ctv7WOiKDUf2; Wed, 12 Apr 2017 17:27:21 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 1205812786A; Wed, 12 Apr 2017 17:27:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id ECF59780088; Wed, 12 Apr 2017 17:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1492043238; bh=oIWwAUeBUJPDqJUcelLq+OQ6EvT7+Qh1GL7Q05mNmtw=; h=Subject:To:References:From:Date:In-Reply-To:From; b=RqhD8Fb9+p2D2xzWEp9Ap/8wwVEj0l7By1QP+LlsCv5d9Plyv9V7MlmmpzM2AZr67 vvj1o1tHwTlKR6G4+tgSf8k9XQb5erN4dYkKkZsaUXOkcKdDC3CYz8PNw6WNr0zdnC wSAnPp/BKI5GAkUNdxXY3dCHmIkWTejlifB8NKOI=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id D37B2780080; Wed, 12 Apr 2017 17:27:17 -0700 (PDT)
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org, iaoc@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>
Date: Wed, 12 Apr 2017 20:27:16 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-12pFoksWkEh_GCXqe08Bh1W87c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 00:27:23 -0000

Stephen, there may be another factor.
I think that many of us take it as given taht it is desirable to meet in 
the US.  It may not be possible.  It may not, on balance, be what we 
choose.  But choosing to not meet in the US at all creates its own 
hardships.  (Not, I grant, comparable with what some folks get put 
through right now.)

In contrast, I am quite sure that folks who felt strongly that we should 
not meet in the US understood that for that to happen, they needed to 
make their voices heard.

Yours,
Joel

On 4/12/17 8:00 PM, Stephen Farrell wrote:
>
> Hi Leslie,
>
> Thanks for the update. One query...
>
> On 13/04/17 00:39, IAOC Chair wrote:
>> The general comments on meeting in the US played along the same lines
>> as has been shared on the IETF discussion list:  people are variously
>> for moving all meetings out of the US, or adamantly against, or
>> somewhere in between, each position supported by good reasons.
>
> I have seen mail to the list that argued for not meeting in the US
> within our current planing horizon. Some of that was adamant. (For
> clarity: I'd agree with the position that we ought not risk meeting
> in the US for a few years, incl. that we ought, if possible, move
> ietf-102 on the basis that the we don't have a predictable situation
> with the US at the moment and that we ought not plan to meet in any
> place that's currently that unpredictable.)
>
> I do not recall the opposite on the list, i.e. someone adamantly
> arguing that we ought continue to meet in the US. There were some
> mails that I'd say maybe weakly argued for continued US meetings
> in the relevant timeframe. But nothing approaching adamant.
>
> Is that my bias in reading the list traffic or did I miss some mail,
> or is it possible that the (public) list traffic and (relatively
> private) survey responses are less similar that your mail implies?
>
> That last wouldn't be surprising, but I'd hope that in that case
> some of the people who filled in the survey who adamantly said we
> ought continue to meet in the US would be willing to justify that
> on the list. If none were, then I think the IAOC ought consider
> that as a relevant input in their decision making. (Not as a
> winning argument, but as a relevant thing.)
>
> Thanks,
> S.
>


From nobody Wed Apr 12 17:44:32 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8C11201F8; Wed, 12 Apr 2017 17:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 HDiuVVVkKHut; Wed, 12 Apr 2017 17:44:21 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4E95126C83; Wed, 12 Apr 2017 17:44:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7D8B2BE6F; Thu, 13 Apr 2017 01:44:18 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bCaPHB2rOHJ; Thu, 13 Apr 2017 01:44:17 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E6000BE49; Thu, 13 Apr 2017 01:44:16 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492044257; bh=hc82diEvWWzZGHFO/6XHaCvZJNU34LrIcTDhRqlQyVQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=q7RyzCo6aMe8osgEkjaTcoHTlbcSEoxb5hW0K2HUqdm5zV6GtdTqc747xHLb28UAg K9edLe5KFuxfeHKdhpRdM1Q6OsUfo9J5eOgM+HElkBzHJYkMRS65gmlnEdG4aEjQPL ut+ZPdJCbcnIDGmBNozmJRt8lY6r/EVlLS5sQSqc=
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: "Joel M. Halpern" <jmh@joelhalpern.com>, ietf@ietf.org, iaoc@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
Date: Thu, 13 Apr 2017 01:44:16 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iUAR83bPjPN5oe80Kd0C11K7tQn4IEIa6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MAEZnp9UDFFWNFs2vh9Og_aLwe8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 00:44:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--iUAR83bPjPN5oe80Kd0C11K7tQn4IEIa6
Content-Type: multipart/mixed; boundary="kWd8m9tHfpFDiigg1NTBC8QHMRnQwvqBL";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, ietf@ietf.org, iaoc@ietf.org,
 IETF Announcement List <ietf-announce@ietf.org>
Message-ID: <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
 <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
 <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>
In-Reply-To: <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>

--kWd8m9tHfpFDiigg1NTBC8QHMRnQwvqBL
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 13/04/17 01:27, Joel M. Halpern wrote:
>=20
> I think that many of us take it as given taht it is desirable to meet i=
n
> the US.

I do not doubt that many IETFers likely think that. And I almost
agree with it.

My only problem is that I'm sadly no longer sure that the present
tense is correct in your statement, which is just a shame.

I fully agree with your statement cast into the past tense.

I really hope that the future tense variant will be something with
which I can agree. At the moment I do not for the reasons stated
(to do with unpredictability).

> In contrast, I am quite sure that folks who felt strongly that we
> should not meet in the US understood that for that to happen, they
> needed to make their voices heard.

That's a fair point. I think though that it also puts on onus on
any folks who adamantly think we ought continue to meet in the US,
to also publicly justify that, given the opposite arguments already
voiced on the list. (I do realise there's a danger there of folks
going OTT, so I hope we all impose a bit of self-restraint if making
arguments either way.)

Note though that my query was with Leslie's assertion that the survey
result and list traffic reflected similar levels of adamant assertion.
(I wasn't doubting that some of us are likely adamant about any random
or non-random topic:-)

Cheers,
S.


--kWd8m9tHfpFDiigg1NTBC8QHMRnQwvqBL--

--iUAR83bPjPN5oe80Kd0C11K7tQn4IEIa6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7sngAAoJEC88hzaAX42iTwEH/iOKiaXCDxyysvNzi80iKQoL
tzNoRwjNbwfEJXVrmA1KOhRoTEy5CTFmhPdqHuCsKXyqQxZ8Ha4ifOxrkcWH6lXm
Oi69O3w4TFaO4L2XxqrdTepTjG8Y72FUeuMGTRSm7X367mEqstPmjcRdfo+i5fsu
MnsTIC2QhP9Ly/30rux1nFc81SO1brulbw4Z/AH/TGBjqQWmMjDycG4pu8UzbWHY
RAmZvabIfGarE3U01xyz4pcsUrlj/3Ih45/ZI406NSqs4gRJ2IpQqN6UcM3CR1ys
4JC32zUmIQvswhnUwnFIPMGiugRzS4UImyN29KbN4CkUH6u83Cdv+UUI2u9TERc=
=92+X
-----END PGP SIGNATURE-----

--iUAR83bPjPN5oe80Kd0C11K7tQn4IEIa6--


From nobody Wed Apr 12 18:22:28 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADEEB126C7B for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 18:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 2gSoLcjKMDRN for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 18:22:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C596B127909 for <ietf@ietf.org>; Wed, 12 Apr 2017 18:22:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cyTSp-0007Np-DB; Thu, 13 Apr 2017 01:22:23 +0000
Date: Thu, 13 Apr 2017 10:22:21 +0900
Message-ID: <m2mvblyucy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Cc: Khaled Omar <eng.khaled.omar@hotmail.com>, ietf <ietf@ietf.org>
Subject: Re: Khaled Routing Protocol (KRP) ID Submission.
In-Reply-To: <CDD5DCA6-4722-4C7A-92E3-501AA25C547A@cisco.com>
References: <D7707E4B-CD37-478A-B640-47148DE3276A@consulintel.es> <AM4PR0401MB2241689CED212EF6C7F2E66ABD030@AM4PR0401MB2241.eurprd04.prod.outlook.com> <CDD5DCA6-4722-4C7A-92E3-501AA25C547A@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=BIG5
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uLV1htX7mNSIXKqTEsKFWduFTpI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 01:22:28 -0000

PiBJIHRvb2sgYSBxdWljayBsb29rIGF0IHlvdXIgZHJhZnQuICBJdCBzZWVtcyB0byBiZSBwcm9w
b3NpbmcgYSB3YXkgdG8NCj4gYXNzaWduIElQIGFkZHJlc3NlcyBzbyB0aGF0IHRoZXkgY29udGFp
biBpbmZvcm1hdGlvbiBhYm91dCByZWdpb25zIGFuZA0KPiBhdXRvbm9tb3VzIHN5c3RlbXMgoVYg
YW5kIHRoZW4gc3VnZ2VzdGluZyB0aGF0IGZvcndhcmRpbmcgY2FuIGJlIGRvbmUNCj4gYmFzZWQg
b24gdGhhdC4gIEJ1dCB5b3UgYXJlIG5vdCBwcm9wb3NpbmcgYSByb3V0aW5nIHByb3RvY29sIChw
YWNrZXQNCj4gZm9ybWF0cywgcHJvdG9jb2wgZGV0YWlscywgZXRjLikuLi4NCg0KbGFuZG1hcmsg
cm91dGluZywgdGxhL25sYSwgLi4uICB3ZSBoYXZlIHNlZW4gaWRlYXMgaW4gdGhpcyBhcmVhIG5v
bmUgb2YNCndoaWNoIGZsZXcuICBpIGFncmVlIHRoYXQgdGhpcyBuZWVkcyBtb3JlIHNwZWNpZmlj
cyBiZWZvcmUgd2UgY2FuIHJlYWxseQ0KanVkZ2UuDQoNCmtoYWxlZCwgaWYgeW91IG5lZWQgaGVs
cCBkZWFsaW5nIHdpdGggdGhlIGlldGYncyBvYnNjdXJlIG1ldGhvZHMgZm9yDQpuYW1pbmcsIHBv
c3RpbmcsIC4uLiBkcmFmdHMsIGZlZWwgZnJlZSB0byB3cml0ZSB0byBtZS4NCg0KcmFuZHkNCg0K


From nobody Wed Apr 12 18:34:10 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 780AE1287A5; Wed, 12 Apr 2017 18:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 A27ozQwVn28A; Wed, 12 Apr 2017 18:34:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 652B5128768; Wed, 12 Apr 2017 18:34:00 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cyTe2-0007RU-Pj; Thu, 13 Apr 2017 01:33:59 +0000
Date: Thu, 13 Apr 2017 10:33:56 +0900
Message-ID: <m2lgr5yttn.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: ietf@ietf.org, iaoc@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
In-Reply-To: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wloJmcVaWliXr49kPHUK95WJKBE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 01:34:02 -0000

> I'd agree with the position that we ought not risk meeting in the US
> for a few years, incl. that we ought, if possible, move ietf-102 on
> the basis that the we don't have a predictable situation with the US
> at the moment and that we ought not plan to meet in any place that's
> currently that unpredictable.)

to me, the lack of predictibility on the draconian index is the main
issue.  and for the uk as well as the states,  both seem to have a well
developed and practiced ability to do very damaging things on very, or
no, notice.

randy


From nobody Wed Apr 12 19:28:35 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45A87126C26 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 19:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=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 7g3Y7G1vx633 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 19:28:31 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069068.outbound.protection.outlook.com [40.92.69.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88495124C27 for <ietf@ietf.org>; Wed, 12 Apr 2017 19:28:30 -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; bh=eych1wXbVpLovu2xR6IyUgCPp1jPdOxlH8wxebMJKEs=; b=QzQxwfrOcewXjjmrhpJBKffT6ZouJfVl4GicrZvNM1Cj6v10Vpaw0YnWv/9/Ah6vIrDGwW7oZGmL16Z4Z2Dw4QkojwMVB8tiKewJmaCWg8hcbTPjhIXg81gokLACPoDMPy67PLClVj+FXVTadlDNyE/b5c6qTmda/Iz46UQGuECYHPrbJYJ+rxwf8o/Jf2QQeE8w+oI48QvNnc4FtywdIrlr2izmarCV+G9YgbSNM3IAEKw3GtNmr0jBOEI8tLU3g5GELe7jXnrm+ZzROvOnXMLqUPTHStlKs30oLAx0oyBek8ohOqtfumhK2Fqx3T4nCR1JzDAiQUEi0JckIaTSUg==
Received: from AM5EUR02FT010.eop-EUR02.prod.protection.outlook.com (10.152.8.58) by AM5EUR02HT159.eop-EUR02.prod.protection.outlook.com (10.152.9.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 02:28:28 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.8.56) by AM5EUR02FT010.mail.protection.outlook.com (10.152.8.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 02:28:28 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 02:28:28 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Leslie Daigle <ldaigle@thinkingcat.com>
CC: ietf <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+Y54XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 02:28:28 +0000
Message-ID: <AM4PR0401MB2241AB792647E5766373588ABD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <F21BFB22-BA7D-411B-BF13-141CD6886621@thinkingcat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: thinkingcat.com; dkim=none (message not signed) header.d=none;thinkingcat.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:7EBC202A18AAEB9756D17FE550FE4814A78886A11E7F5BC969AA84F9E6203582; UpperCasedChecksum:35DAA510FBEA097679A834F7C62B9B0F89B1200EB1896325CD35CDFD57FA717A; SizeAsReceived:7867; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR02HT159; 5:lZxdOHkzpcjgp4m8aMNythO01+/HrpjVaOE6Z4MANw0zJE7tyKxeCjNsBMb40+UwUPA8gdqkPCf2StFo711v7M2R8CA3fLjgvi2ivo85EOEE8LbrZQZe1EKbY04BRTghrzk3u5aSQ8wfZv0vqZvH0w==; 24:OxwXurNZ6O0/lNQcP3j+iFVeOrFL5nn39GYhD8ZCxcKv0xHewA6KTtO+/UwJBmIDEtKS3aj3PLcN3PDwwCDdQhKPs64igxRFFbHVsqOOLm8=; 7:PN5zyukp5/BRrsHQzNsEqBuCOeQid6DLb2l0E4sqX8r0FA0eLGKrUM+HlfJ7Z94U7CmnRHNtGDxOtw9GxCDozyLJja+vL+AF4LHLR3QvW2ZbY4tFuCr1/E1tQ/CPuU9JMyACPa9gEr8rZYkXasuSxlymjgqAFpyvh5zHnv7se4xV6h5kB+MS9ptM8i3vePm1XduhVvauUEdhm/ivTYxiH5u+wsRhVYkwZN4W1gMmhSb+6KXfzhxZ0RwU3VIHlDIVQdiAa6PUwdJAkkKMtdKhZigVSA4/sJXwqKW3D4hIvDIjDhyHh9OE91Yk678NpBxL
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR02HT159; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 4c260085-94cd-4fc4-d877-08d48214c468
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR02HT159; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR02HT159; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR02HT159; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241AB792647E5766373588ABD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 02:28:28.3153 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT159
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1BPfcRBZ-bpMeBhWHnS374jCZaA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 02:28:33 -0000

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

SGkgTGVzbGllLA0KDQpVbmZvcnR1bmF0ZWx5IEkgZGlkIG5vdCBrbm93IGFib3V0IHRoaXMgcXVl
c3Rpb25haXIsIHNvIGlmIEkgY2FuIG1ha2UgYSBzdWdnZXN0aW9uIHJlZ2FyZGluZyB0aGUgbmV4
dCBJRVRGIG1lZXRpbmdzJyBsb2NhdGlvbiwgSSB3b3VsZCBzdWdnZXN0IENhaXJvLCBFZ3lwdCBh
cyBvbmUgb2YgdGhlIGxvY2F0aW9ucyB0byBiZSBjb25zaWRlcmVkIGZvciBhbiBJRVRGIG1lZXRp
bmcsIHBvc2l0aXZlIElFVEYgcGFydGljaXBhbnRzIHdpbGwgYmUgd2VsY29tZWQgaGVyZSBhbmQg
d2lsbCBlbmpveSB0aGUgc3Vubnkgd2VhdGhlciBhbGwgdGhlIHllYXIuDQoNCkZvciBtZSBpdCB3
YXMgZGlmZmljdWx0IHRvIGF0dGVuZCB0aGUgbWVldGluZyBoZWxkIGluIFUuUy4gaW4gcGVyc29u
IGFuZCBpdCB3YXMgYWxzbyBkaWZmaWN1bHQgdG8gYXR0ZW5kIHJlbW90ZWx5LCBzbyBpZiBFZ3lw
dCB3aWxsIGJlIGNvbnNpZGVyZWQgZm9yIGEgbWVldGluZywgaSdtIHN1cmUgcGFydGljaXBhbnRz
IHdpbGwgZW5qb3kgdGltZSBoZXJlIGR1cmluZyB0aGUgbWVldGluZy4NCg0KQmVzdCBSZWdhcmRz
LA0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IEZ3ZDog
VXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCkZy
b206IExlc2xpZSBEYWlnbGUNClRvOiAiSWV0ZkBJZXRmLiBPcmciDQpDQzogSUFPQ0BpZXRmLm9y
Zw0KDQoNCg0KRllJIOKAlCB0aGlzIGlzIHRoZSBpbmZvcm1hdGlvbiBhcyB3ZSBoYXZlIGl0Lg0K
DQpMZXNsaWUuDQoNCi0tDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkxl
c2xpZSBEYWlnbGUNClByaW5jaXBhbCwgVGhpbmtpbmdDYXQgRW50ZXJwcmlzZXMgTExDDQoNCmxk
YWlnbGVAdGhpbmtpbmdjYXQuY29tPG1haWx0bzpsZGFpZ2xlQHRoaW5raW5nY2F0LmNvbT4NCg0K
Rm9yd2FyZGVkIG1lc3NhZ2U6DQoNCkZyb206IElBT0MgQ2hhaXIgaWFvYy1jaGFpckBpZXRmLm9y
ZzxtYWlsdG86aWFvYy1jaGFpckBpZXRmLm9yZz4NClRvOiBJRVRGIEFubm91bmNlbWVudCBMaXN0
IGlldGYtYW5ub3VuY2VAaWV0Zi5vcmc8bWFpbHRvOmlldGYtYW5ub3VuY2VAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRG
IDEwMg0KRGF0ZTogV2VkLCAxMiBBcHIgMjAxNyAxNjozOToxOCAtMDcwMA0KDQpPbiBNYXJjaCAz
MSwgMjAxNywgd2UgcHV0IG91dCBhIHJlcXVlc3QgZm9yIGlucHV0IG9uIGV4cGVyaWVuY2VzIHdp
dGggdHJhdmVsIHRvIHRoZSByZWNlbnQgSUVURiBtZWV0aW5nIGluIHRoZSBVUywgYW5kIHNvbGlj
aXRlZCBpbmZvcm1hdGlvbiBwZXJ0aW5lbnQgdG8gcGxhbnMgdG8gYXR0ZW5kIElFVEYgbWVldGlu
Z3Mgd2l0aGluIG9yIG91dHNpZGUgdGhlIFVTIGluIHRoZSBjb21pbmcgeWVhcnMuIFdlIGhhdmUg
aGFkIG92ZXIgMzUwIHJlc3BvbnNlcyB0byB0aGUgcXVlc3Rpb25uYWlyZSwgYW5kIHdlIGFwcHJl
Y2lhdGUgZWFjaCBhbmQgZXZlcnkgb25lIG9mIHRoZW0hIFdlIGRpZCBub3QgZ2F0aGVyIHRoZSBk
YXRhIGluIHN1Y2ggYSB3YXkgZm9yIGl0IHRvIHJlZmxlY3QgYSByZXByZXNlbnRhdGl2ZSBzYW1w
bGUgb2YgdGhlIElFVEYgY29tbXVuaXR5LCBvciBvZiBwb3RlbnRpYWwgbWVldGluZyBhdHRlbmRl
ZXMuIEJ1dCB3ZSBkaWQgZ2FpbiBpbnNpZ2h0cyBmcm9tIHRob3NlIHdobyByZXNwb25kZWQgdGhh
dCB3ZSBkaWQgbm90IGhhdmUgYmVmb3JlLg0KDQpPdmVyIDQwJSBvZiB0aGUgcmVzcG9uZGVudHMg
c2FpZCB0aGV5IGhhZCBhdHRlbmRlZCAyMCBvciBtb3JlIElFVEYgbWVldGluZ3MsIGFuZCBvdmVy
IDUwJSBvZiB0aGVtIHNhaWQgdGhleSB3ZXJlIGF1dGhvcnMgb2YgYWN0aXZlIHdvcmtpbmcgZ3Jv
dXAgZG9jdW1lbnRzLiBTbGlnaHRseSBtb3JlIHRoYW4gNDAlIHN0YXRlZCBVUyByZXNpZGVuY3ks
IGFuZCBqdXN0IGxlc3MgdGhhbiA2MCUgc2FpZCB0aGV5IHdlcmUgbm90IFVTLXJlc2lkZW50Lg0K
DQpUaGVyZSB3YXMgYSBub3RlZCBpbXBhY3Qgb2YgdGhlIHJlY2VudCBjaGFuZ2VzIHRvIFVTIHRy
YXZlbCBwb2xpY2llcyBhbmQgcHJvY2VkdXJlcy4gT2YgdGhlIHJlc3BvbmRlbnRzIGxpdmluZyBv
dXRzaWRlIG9mIHRoZSBVUyB3aG8gZGlkIE5PVCBhdHRlbmQgdGhlIElFVEYgbWVldGluZyBpbiBD
aGljYWdvLCBhIGZldyB3ZXJlIGRlbmllZCB2aXNhcyBvciBlbnRyeSBpbnRvIHRoZSBVUywgYW5k
IG1vcmUgdGhhbiAzMCBzYWlkIHRoZXkgZGlkIG5vdCBjb21lIGJlY2F1c2Ugb2YgY29uY2VybnMg
YWJvdXQgVVMgdHJhdmVsIHJlc3RyaWN0aW9ucy4gT24gdGhlIG90aGVyIGhhbmQgNDUgcGVvcGxl
IHNhaWQgdGhleSB3ZXJlIG5vdCB0cm91YmxlZCBieSB0aGUgVVMgc2l0dWF0aW9uIChhbmQgcHJl
c3VtYWJseSBjaG9zZSBub3QgdG8gY29tZSBmb3Igb3RoZXIgcmVhc29ucykuDQoNCkZvciB0aG9z
ZSB3aG8gZGlkIHRyYXZlbCB0byBJRVRGIDk4IGluIENoaWNhZ28sIHRoZSB3cml0dGVuIGNvbW1l
bnRzIHdlcmUgaWxsdW1pbmF0aW5nOiBtb3N0IHBlb3BsZSBoYWQgbm8gaXNzdWVzIChmb3Igc29t
ZSwgZXZlbiBhIHNtb290aGVyIGJvcmRlciBjcm9zc2luZyB0aGFuIHVzdWFsKTsgc29tZSBwZW9w
bGUgZXhwZXJpZW5jZWQgdGhlIGV4cGVjdGVkIGZsdXR0ZXIgb3ZlciB2aXNhIGFwcHJvdmFscyBh
cyB0aGluZ3Mgd2VyZSBpbiBmbHV4IGFzIHRoZSBVUyBFeGVjdXRpdmUgT3JkZXIgYW5kIGNvdXJ0
IHN0YXlzIHBsYXllZCBvdXQsIGJ1dCB3ZXJlIGV2ZW50dWFsbHkgYWJsZSB0byBjb21lLg0KDQpU
aGUgZ2VuZXJhbCBjb21tZW50cyBvbiBtZWV0aW5nIGluIHRoZSBVUyBwbGF5ZWQgYWxvbmcgdGhl
IHNhbWUgbGluZXMgYXMgaGFzIGJlZW4gc2hhcmVkIG9uIHRoZSBJRVRGIGRpc2N1c3Npb24gbGlz
dDogcGVvcGxlIGFyZSB2YXJpb3VzbHkgZm9yIG1vdmluZyBhbGwgbWVldGluZ3Mgb3V0IG9mIHRo
ZSBVUywgb3IgYWRhbWFudGx5IGFnYWluc3QsIG9yIHNvbWV3aGVyZSBpbiBiZXR3ZWVuLCBlYWNo
IHBvc2l0aW9uIHN1cHBvcnRlZCBieSBnb29kIHJlYXNvbnMuDQoNClRoZSBJQU9DIGlzIGNvbnRp
bnVpbmcgdG8gZ2F0aGVyIGRhdGEgb24gdHJhdmVsIHRvIHRoZSBVUywgY29uY2VybnMgYWJvdXQg
dHJhdmVsaW5nIG91dHNpZGUgb2YgaXQsIGFuZCB3aGF0IGFsdGVybmF0aXZlcyBhcmUgcG9zc2li
bGUgZm9yIElFVEYgMTAyLiBPdXIgZm9jdXMgaXMgY3VycmVudGx5IG9uIHdoZXRoZXIgaG9sZGlu
ZyBJRVRGIDEwMiBpbiBTYW4gRnJhbmNpc2NvIGlzIHRoZSBiZXN0IG9wdGlvbiB0byBtZWV0IHRo
ZSBuZWVkcyBvZiBJRVRGIHdvcmssIHJlY29nbml6aW5nIHRoYXQgd2UgY2Fubm90IHByZWRpY3Qg
dGhlIGZ1dHVyZS4gV2hpbGUgaXQgbWF5IHRha2Ugc2V2ZXJhbCB3ZWVrcyB0byBhbGxvdyBmb3Ig
cmV2aWV3IGFuZCBuZWdvdGlhdGlvbiBvZiBhbnkgYWx0ZXJuYXRpdmVzIChpZiBhcHBsaWNhYmxl
KSwgd2UgYXJlIG1vdmluZyBhcyBxdWlja2x5IGFzIHBvc3NpYmxlIGJlY2F1c2Ugd2UgcmVhbGl6
ZSB0aGF0IHBlb3BsZSB3aWxsIG5lZWQgdGltZSB0byBwbGFuIHRoZWlyIHRyYXZlbC4NCg0KTGVz
bGllLCBmb3IgdGhlIElBT0MuDQo=

--_000_AM4PR0401MB2241AB792647E5766373588ABD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <533FD533B9F05A4493ED4B31E2A6EC86@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSGkgTGVzbGllLCA8
YnI+DQo8YnI+DQpVbmZvcnR1bmF0ZWx5IEkgZGlkIG5vdCBrbm93IGFib3V0IHRoaXMgcXVlc3Rp
b25haXIsIHNvIGlmIEkgY2FuIG1ha2UgYSBzdWdnZXN0aW9uIHJlZ2FyZGluZyB0aGUgbmV4dCBJ
RVRGIG1lZXRpbmdzJyBsb2NhdGlvbiwgSSB3b3VsZCBzdWdnZXN0IENhaXJvLCBFZ3lwdCBhcyBv
bmUgb2YgdGhlIGxvY2F0aW9ucyB0byBiZSBjb25zaWRlcmVkIGZvciBhbiBJRVRGIG1lZXRpbmcs
IHBvc2l0aXZlIElFVEYgcGFydGljaXBhbnRzIHdpbGwgYmUgd2VsY29tZWQNCiBoZXJlIGFuZCB3
aWxsIGVuam95IHRoZSBzdW5ueSB3ZWF0aGVyIGFsbCB0aGUgeWVhci48YnI+DQo8YnI+DQpGb3Ig
bWUgaXQgd2FzIGRpZmZpY3VsdCB0byBhdHRlbmQgdGhlIG1lZXRpbmcgaGVsZCBpbiBVLlMuIGlu
IHBlcnNvbiBhbmQgaXQgd2FzIGFsc28gZGlmZmljdWx0IHRvIGF0dGVuZCByZW1vdGVseSwgc28g
aWYgRWd5cHQgd2lsbCBiZSBjb25zaWRlcmVkIGZvciBhIG1lZXRpbmcsIGknbSBzdXJlIHBhcnRp
Y2lwYW50cyB3aWxsIGVuam95IHRpbWUgaGVyZSBkdXJpbmcgdGhlIG1lZXRpbmcuPGJyPg0KPGJy
Pg0KQmVzdCBSZWdhcmRzLA0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDog
MS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0K
U3ViamVjdDogRndkOiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFu
ZCBJRVRGIDEwMjxicj4NCkZyb206IExlc2xpZSBEYWlnbGUgPGxkYWlnbGVAdGhpbmtpbmdjYXQu
Y29tPjxicj4NClRvOiAmcXVvdDtJZXRmQElldGYuIE9yZyZxdW90OyA8aWV0ZkBpZXRmLm9yZz48
YnI+DQpDQzogSUFPQ0BpZXRmLm9yZzxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+
DQo8YmxvY2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3Jk
ZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjwhRE9DVFlQRSBIVE1M
IFBVQkxJQyAiLS8vVzNDLy9EVEQgSFRNTCA0LjAxIFRyYW5zaXRpb25hbC8vRU4iPg0KPGRpdiBz
dHlsZT0iZm9udC1mYW1pbHk6c2Fucy1zZXJpZiI+DQo8ZGl2IHN0eWxlPSJ3aGl0ZS1zcGFjZTpu
b3JtYWwiPg0KPHAgZGlyPSJhdXRvIj5GWUkg4oCUIHRoaXMgaXMgdGhlIGluZm9ybWF0aW9uIGFz
IHdlIGhhdmUgaXQuPC9wPg0KPHAgZGlyPSJhdXRvIj5MZXNsaWUuPC9wPg0KPHAgZGlyPSJhdXRv
Ij4tLSA8L3A+DQo8aHIgc3R5bGU9ImJhY2tncm91bmQ6IzMzMzsgYmFja2dyb3VuZC1pbWFnZTps
aW5lYXItZ3JhZGllbnQodG8gcmlnaHQsICNjY2MsICMzMzMsICNjY2MpOyBib3JkZXI6MDsgaGVp
Z2h0OjFweCIgaGVpZ2h0PSIxIj4NCjxwIGRpcj0iYXV0byI+TGVzbGllIERhaWdsZTxicj4NClBy
aW5jaXBhbCwgVGhpbmtpbmdDYXQgRW50ZXJwcmlzZXMgTExDPC9wPg0KPGgyIHN0eWxlPSJmb250
LXNpemU6MS4yZW0iPjxhIGhyZWY9Im1haWx0bzpsZGFpZ2xlQHRoaW5raW5nY2F0LmNvbSIgc3R5
bGU9ImNvbG9yOiMzOTgzQzQiPmxkYWlnbGVAdGhpbmtpbmdjYXQuY29tPC9hPjwvaDI+DQo8cCBk
aXI9ImF1dG8iPkZvcndhcmRlZCBtZXNzYWdlOjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3Jk
ZXItbGVmdDoycHggc29saWQgIzc3NzsgY29sb3I6Izc3NzsgbWFyZ2luOjAgMCA1cHg7IHBhZGRp
bmctbGVmdDo1cHgiPg0KPHAgZGlyPSJhdXRvIj5Gcm9tOiBJQU9DIENoYWlyIDxhIGhyZWY9Im1h
aWx0bzppYW9jLWNoYWlyQGlldGYub3JnIiBzdHlsZT0iY29sb3I6Izc3NyI+DQppYW9jLWNoYWly
QGlldGYub3JnPC9hPjxicj4NClRvOiBJRVRGIEFubm91bmNlbWVudCBMaXN0IDxhIGhyZWY9Im1h
aWx0bzppZXRmLWFubm91bmNlQGlldGYub3JnIiBzdHlsZT0iY29sb3I6Izc3NyI+DQppZXRmLWFu
bm91bmNlQGlldGYub3JnPC9hPjxicj4NClN1YmplY3Q6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBV
Uy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyPGJyPg0KRGF0ZTogV2VkLCAxMiBBcHIgMjAx
NyAxNjozOToxOCAtMDcwMDwvcD4NCjxwIGRpcj0iYXV0byI+T24gTWFyY2ggMzEsIDIwMTcsIHdl
IHB1dCBvdXQgYSByZXF1ZXN0IGZvciBpbnB1dCBvbiBleHBlcmllbmNlcyB3aXRoIHRyYXZlbCB0
byB0aGUgcmVjZW50IElFVEYgbWVldGluZyBpbiB0aGUgVVMsIGFuZCBzb2xpY2l0ZWQgaW5mb3Jt
YXRpb24gcGVydGluZW50IHRvIHBsYW5zIHRvIGF0dGVuZCBJRVRGIG1lZXRpbmdzIHdpdGhpbiBv
ciBvdXRzaWRlIHRoZSBVUyBpbiB0aGUgY29taW5nIHllYXJzLiBXZSBoYXZlIGhhZCBvdmVyDQog
MzUwIHJlc3BvbnNlcyB0byB0aGUgcXVlc3Rpb25uYWlyZSwgYW5kIHdlIGFwcHJlY2lhdGUgZWFj
aCBhbmQgZXZlcnkgb25lIG9mIHRoZW0hIFdlIGRpZCBub3QgZ2F0aGVyIHRoZSBkYXRhIGluIHN1
Y2ggYSB3YXkgZm9yIGl0IHRvIHJlZmxlY3QgYSByZXByZXNlbnRhdGl2ZSBzYW1wbGUgb2YgdGhl
IElFVEYgY29tbXVuaXR5LCBvciBvZiBwb3RlbnRpYWwgbWVldGluZyBhdHRlbmRlZXMuIEJ1dCB3
ZSBkaWQgZ2FpbiBpbnNpZ2h0cyBmcm9tIHRob3NlDQogd2hvIHJlc3BvbmRlZCB0aGF0IHdlIGRp
ZCBub3QgaGF2ZSBiZWZvcmUuPC9wPg0KPHAgZGlyPSJhdXRvIj5PdmVyIDQwJSBvZiB0aGUgcmVz
cG9uZGVudHMgc2FpZCB0aGV5IGhhZCBhdHRlbmRlZCAyMCBvciBtb3JlIElFVEYgbWVldGluZ3Ms
IGFuZCBvdmVyIDUwJSBvZiB0aGVtIHNhaWQgdGhleSB3ZXJlIGF1dGhvcnMgb2YgYWN0aXZlIHdv
cmtpbmcgZ3JvdXAgZG9jdW1lbnRzLiBTbGlnaHRseSBtb3JlIHRoYW4gNDAlIHN0YXRlZCBVUyBy
ZXNpZGVuY3ksIGFuZCBqdXN0IGxlc3MgdGhhbiA2MCUgc2FpZCB0aGV5IHdlcmUgbm90IFVTLXJl
c2lkZW50LjwvcD4NCjxwIGRpcj0iYXV0byI+VGhlcmUgd2FzIGEgbm90ZWQgaW1wYWN0IG9mIHRo
ZSByZWNlbnQgY2hhbmdlcyB0byBVUyB0cmF2ZWwgcG9saWNpZXMgYW5kIHByb2NlZHVyZXMuIE9m
IHRoZSByZXNwb25kZW50cyBsaXZpbmcgb3V0c2lkZSBvZiB0aGUgVVMgd2hvIGRpZCBOT1QgYXR0
ZW5kIHRoZSBJRVRGIG1lZXRpbmcgaW4gQ2hpY2FnbywgYSBmZXcgd2VyZSBkZW5pZWQgdmlzYXMg
b3IgZW50cnkgaW50byB0aGUgVVMsIGFuZCBtb3JlIHRoYW4gMzAgc2FpZA0KIHRoZXkgZGlkIG5v
dCBjb21lIGJlY2F1c2Ugb2YgY29uY2VybnMgYWJvdXQgVVMgdHJhdmVsIHJlc3RyaWN0aW9ucy4g
T24gdGhlIG90aGVyIGhhbmQgNDUgcGVvcGxlIHNhaWQgdGhleSB3ZXJlIG5vdCB0cm91YmxlZCBi
eSB0aGUgVVMgc2l0dWF0aW9uIChhbmQgcHJlc3VtYWJseSBjaG9zZSBub3QgdG8gY29tZSBmb3Ig
b3RoZXIgcmVhc29ucykuPC9wPg0KPHAgZGlyPSJhdXRvIj5Gb3IgdGhvc2Ugd2hvIGRpZCB0cmF2
ZWwgdG8gSUVURiA5OCBpbiBDaGljYWdvLCB0aGUgd3JpdHRlbiBjb21tZW50cyB3ZXJlIGlsbHVt
aW5hdGluZzogbW9zdCBwZW9wbGUgaGFkIG5vIGlzc3VlcyAoZm9yIHNvbWUsIGV2ZW4gYSBzbW9v
dGhlciBib3JkZXIgY3Jvc3NpbmcgdGhhbiB1c3VhbCk7IHNvbWUgcGVvcGxlIGV4cGVyaWVuY2Vk
IHRoZSBleHBlY3RlZCBmbHV0dGVyIG92ZXIgdmlzYSBhcHByb3ZhbHMgYXMgdGhpbmdzDQogd2Vy
ZSBpbiBmbHV4IGFzIHRoZSBVUyBFeGVjdXRpdmUgT3JkZXIgYW5kIGNvdXJ0IHN0YXlzIHBsYXll
ZCBvdXQsIGJ1dCB3ZXJlIGV2ZW50dWFsbHkgYWJsZSB0byBjb21lLjwvcD4NCjxwIGRpcj0iYXV0
byI+VGhlIGdlbmVyYWwgY29tbWVudHMgb24gbWVldGluZyBpbiB0aGUgVVMgcGxheWVkIGFsb25n
IHRoZSBzYW1lIGxpbmVzIGFzIGhhcyBiZWVuIHNoYXJlZCBvbiB0aGUgSUVURiBkaXNjdXNzaW9u
IGxpc3Q6IHBlb3BsZSBhcmUgdmFyaW91c2x5IGZvciBtb3ZpbmcgYWxsIG1lZXRpbmdzIG91dCBv
ZiB0aGUgVVMsIG9yIGFkYW1hbnRseSBhZ2FpbnN0LCBvciBzb21ld2hlcmUgaW4gYmV0d2Vlbiwg
ZWFjaCBwb3NpdGlvbiBzdXBwb3J0ZWQNCiBieSBnb29kIHJlYXNvbnMuPC9wPg0KPHAgZGlyPSJh
dXRvIj5UaGUgSUFPQyBpcyBjb250aW51aW5nIHRvIGdhdGhlciBkYXRhIG9uIHRyYXZlbCB0byB0
aGUgVVMsIGNvbmNlcm5zIGFib3V0IHRyYXZlbGluZyBvdXRzaWRlIG9mIGl0LCBhbmQgd2hhdCBh
bHRlcm5hdGl2ZXMgYXJlIHBvc3NpYmxlIGZvciBJRVRGIDEwMi4gT3VyIGZvY3VzIGlzIGN1cnJl
bnRseSBvbiB3aGV0aGVyIGhvbGRpbmcgSUVURiAxMDIgaW4gU2FuIEZyYW5jaXNjbyBpcyB0aGUg
YmVzdCBvcHRpb24gdG8gbWVldA0KIHRoZSBuZWVkcyBvZiBJRVRGIHdvcmssIHJlY29nbml6aW5n
IHRoYXQgd2UgY2Fubm90IHByZWRpY3QgdGhlIGZ1dHVyZS4gV2hpbGUgaXQgbWF5IHRha2Ugc2V2
ZXJhbCB3ZWVrcyB0byBhbGxvdyBmb3IgcmV2aWV3IGFuZCBuZWdvdGlhdGlvbiBvZiBhbnkgYWx0
ZXJuYXRpdmVzIChpZiBhcHBsaWNhYmxlKSwgd2UgYXJlIG1vdmluZyBhcyBxdWlja2x5IGFzIHBv
c3NpYmxlIGJlY2F1c2Ugd2UgcmVhbGl6ZSB0aGF0IHBlb3BsZSB3aWxsIG5lZWQgdGltZQ0KIHRv
IHBsYW4gdGhlaXIgdHJhdmVsLjwvcD4NCjxwIGRpcj0iYXV0byI+TGVzbGllLCBmb3IgdGhlIElB
T0MuPC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM4PR0401MB2241AB792647E5766373588ABD020AM4PR0401MB2241_--


From nobody Wed Apr 12 20:02:27 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59DED126C26 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:02: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, 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 E8yXRMzxUGit for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:02:24 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 BDD8412751F for <ietf@ietf.org>; Wed, 12 Apr 2017 20:02:22 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id s16so22286178pfs.0 for <ietf@ietf.org>; Wed, 12 Apr 2017 20:02:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=OvSIAHEL+AV4f/b5zG8kOUUhpXyu/fxZGPB5qMbX3I4=; b=SbMeYylXqtFM35VlADGKp2uz3feQibZO+GX74+McQodMO4nVrhTnkcwxUD1VBU7Tzf 4e22IYdWlYaqAXOA9FmpAOJztQT+4ZgxjfkdSMs+MCfS3A+bJ7kuiCAYSdvKqaGVH12f YZVQ/VD+ZvEuBxJsFD1T86IOqbF7RfLlqISobD5SDZ6E/1yMYvKoOiAYOJam1NAvKHvO L3zb30Zf7P3gcPM0Rf9qxC/zNIdgoNmcT5KMYUm0OO8u1vnMs/aE9ORjboPObdKBpAb5 ZEwhbl0qAXlNw8FljNHhTlhnDRMWStmVZBHCGpjv4qCw0GIg+tMv2zZPL4Zv15ylY5Gw 0HEg==
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:content-transfer-encoding; bh=OvSIAHEL+AV4f/b5zG8kOUUhpXyu/fxZGPB5qMbX3I4=; b=WpdRsxFH2C3HErZEF1jsL+NrFK6fK7S1ykFh89ldvc8sOwwnLtmNvnXxVgzKXIcu9q /S2gYRLNfp28LDZxe+atyNqQ9HBzPYIuUwou1OyU5iUrolgGOp9mIRRDO1/AJfMakuFj k+YCjpmWVWVGUFrVbKm5fSThZJ+w8vcODfE2GEJxVHzBDudFw3pYF2c/mlg92BZj8XB2 JdJgL9zDgbhzJ23CjjHvmUPVG1Sz5yk1h6ZqAqUSzZ0f7ikFyo1Nv0FiWvRMlDECI6JA QqwqILHinIjkmbtbvs6lGrUIvVkFL96sN2L7TG5p+H135Az2BXMgaEq12shsjNEcAEOb 12ng==
X-Gm-Message-State: AN3rC/5BiecKH6m4Hd10jp2xb1nAWGQ9toI/JCeuDUcLcPEl75A20Udj p72aQWE36OY2Qh/ltl+DyOxpwHRJsxc3
X-Received: by 10.99.62.68 with SMTP id l65mr942952pga.172.1492052542241; Wed, 12 Apr 2017 20:02:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.162.41 with HTTP; Wed, 12 Apr 2017 20:01:41 -0700 (PDT)
In-Reply-To: <CAHbuEH4gDB==ngGvqpN7747uFV_FnrYtKi_azk7hyoV8YHH6Jw@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com> <A74855AD-0C8B-4A4D-86C7-940F56873F9E@tik.ee.ethz.ch> <CAHbuEH4gDB==ngGvqpN7747uFV_FnrYtKi_azk7hyoV8YHH6Jw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 12 Apr 2017 23:01:41 -0400
Message-ID: <CAHbuEH47ozoQ+6UHDgdM0VFGsx-T-ccj-c_Az_pkhb3PXXipcA@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Cc: Martin Thomson <martin.thomson@gmail.com>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-RQxHEqP0D_HdR-nJSjKtXlSZfg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 03:02:26 -0000

Hi Mirja and Martin,

Responding inline with adjustments that were made to address the
technical comments and responses in this section of the review.  This
will show up in version 11.

On Wed, Apr 12, 2017 at 2:42 PM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:
> Mirja,
>
> Sorry for the top post.
>
> Thank you for responding on the outstanding items that were more
> technical in nature (QUIC and load balancing).  We'll integrate your
> suggested edits in the next revision.
>
> Kathleen
>
> On Wed, Apr 12, 2017 at 2:28 PM, Mirja K=C3=BChlewind
> <mirja.kuehlewind@tik.ee.ethz.ch> wrote:
>> Hi Martin, hi Kathleen,
>>
>> I would like to comment (for now) just on this one section, as my name w=
as called out.
>>
>>> Am 11.04.2017 um 05:54 schrieb Kathleen Moriarty <kathleen.moriarty.iet=
f@gmail.com>:
>>>
>>>>> Section 2.1
>>>>>
>>>>> This is one of the few sections that talk about what it means to oper=
ate a
>>>>> service as opposed to operate a network.
>>>>>
>>>>> Overall, this section doesn't work particularly well.  The distinctio=
n
>>>>> between
>>>>> integrated and standalone load balancing is an interesting division, =
but
>>>>> it
>>>>> doesn't leverage this distinction well.  What causes a standalone
>>>>> load-balancer
>>>>> to be necessary?
>>
>> My understanding is that the stand-alone load balancer was only brought =
up to better explain what an integrated load balancer is, assuming that the=
 integrated (more complex) case is the common one.
>>
>> However, to answer your question, for a stand-alone laod balancer it is =
assumed that you only have a small number of servers at one single location=
 and you only need one box that does the load-balancing on these different =
servers. So all this box needs to know is the IP address of these servers.
>>
>>>>> Is this something a network operator uses?  I see text
>>>>> on NFV
>>>>> later, but it's far removed from the original text and it seems
>>>>> aspirational
>>>>> rather than concrete.  On the other hand, many of the concerns in thi=
s
>>>>> document
>>>>> simply don't apply to an integrated load balancer.
>>
>> To my understanding all the concerns apply to integrated load balancers.=
 Integrated only means that the load balancer shares some information with =
the server and based on this knowledge the load balancer can identify based=
 on some information in the packets which server this packet should be forw=
arded to.
>>
>>>>>
>>>>> The amount of text on QUIC here is surprising.  Given how much of QUI=
C is
>>>>> changing right now, we shouldn't publish a document that attempts to =
make
>>>>> claims
>>>>> about what QUIC is or how it is operated.  This attempts to dive into=
 the
>>>>> details of QUIC connection migration in a way that presumes much abou=
t the
>>>>> outcome of issues that the QUIC working group is still struggling wit=
h.
>>>>>
>>>>> I would strongly recommend removing QUIC-specific language from this
>>>>> section and
>>>>> the document as a whole.  We have an operational document in the QUIC
>>>>> working
>>>>> group that would be a good venue to discuss some of these concerns.
>>>
>>> While we read this as  more of a substantive remark, the text on
>>> load balancers and QUIC were added per Mirja's IESG review.  We would
>>> need to check with her about making any changes here.  They were
>>> specific additions that were requested.
>>>
>>> Further, it is only IETF QUIC that is in active development.
>>> Google QUIC (referred to as GQUIC in IETF discussions) is a more
>>> stable experiment now.
>>
>>
>> I fully agree to remove the quic specific language. It=E2=80=99s definit=
ely too early to say something in this document (and GQUIC is probably not =
documented well enough to rely on this). This text wasn=E2=80=99t provided =
by me but I recommended a contributor for this text who is also active in t=
he quic wg and missed this when he send the text.
>>
>> I recommend to simply remove the following sentences:
>>
>> "QUIC is an example of such
>>    protocol in development by IETF QUIC WG right now.=E2=80=9C
>>
>> "New connection-migration-tolerant protocols, such as QUIC, are
>>    deliberately designed to allow such extra information available in
>>    plain text (QUIC's server-generated flow IDs).=E2=80=9C
>>

These sentences have been removed.  Thanks for your guidance on these quest=
ions.

>>
>>>
>>>>>
>>>>> Is this an oblique reference to (the much-loved) RFC 7974?
>>
>> No, not at all. There are other ways middleboxes can add information. Bu=
t in this case actually the server would add information because the load b=
alancers and the server share some knowledge.
>>
>>>>>
>>>>>   Current protocols, such as TCP, allow the development of stateless
>>>>> integrated
>>>>>   load balancers by availing such load balancers of additional plain =
text
>>>>>   information in client-to-server packets.
>>>>>
>>>>> Otherwise, I don't know what it means.
>>
>> A server could select a certain sequence number (range), or TCP timestam=
p, I guess...
>>
>>>>>
>>>>> BTW, I like this parenthetical:
>>>>>
>>>>>   (That said, care must be exercised to make sure that the informatio=
n
>>>>> encoded
>>>>>   by the endpoints is not sufficient to identify unique flows and
>>>>> facilitate
>>>>>   Persistent Surveillance attack vector.)
>>>>>
>>>>> I'm going to take this to the QUIC working group, because QUIC certai=
nly
>>>>> doesn't
>>>>> meet that bar right now.  It fully facilitates Persistent Surveillanc=
e in
>>>>> its
>>>>> current form (proper noun?  I haven't really seen that term before, e=
ven
>>>>> though
>>>>> it draws a neat parallel with Pervasive Surveillance).
>>>>>
>>>
>>> OK, let us know what you hear back.  These changes were in response to
>>> the sponsoring AD's request of that work.
>>
>> I think this sentence should be removed in this document and a reference=
 to RFC 7258 should be added, instead of coming up with new terminology her=
e that sets the bar higher that what was agreed in RFC 7258.

Thanks, Mirja.  Deborah suggested some new text for the abstract and
introduction that hits on this same point as well.  It should assist
with some of Martin's tone comments.  As for this specific suggestion,
we deleted the text as advised and added the following per your
suggestion:

       As noted in Section 2 of RFC7258, careful consideration
        in protocol design to mitigate PM is important, while ensuring
        manageability of the network.
>>
>>>
>>>>> Editorial:
>>>>> * "pop" is a term of art that needs explanation.
>>>>> * "QUIC?s", "network?s" - avoid smart quotes, and - more generally - =
the
>>>>>  possessive form for the inanimate.
>>>>> * "QUIC's server-generated flow IDs" -> "QUIC's connection IDs".
>>>
>>> Thanks for the nit corrections.
>>
>> Thanks!
>>
>> I will further comment later!
>>
>> Mirja
>>
>>
>
>
>
> --
>
> Best regards,
> Kathleen

Your assistance is much appreciated.

--=20

Best regards,
Kathleen


From nobody Wed Apr 12 20:10:35 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4651286B1 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:10: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 3cuWob_FJJGa for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:10:32 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::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 AA026127B73 for <ietf@ietf.org>; Wed, 12 Apr 2017 20:10:32 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id i5so22292408pfc.2 for <ietf@ietf.org>; Wed, 12 Apr 2017 20:10:32 -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; bh=mh/21OzOvJRveM43IE/S8931NCogtg1j912jicVi46s=; b=qBUBZofojd28XYxXdZcXpSd9G4M6aNUKbogyGCHJSYXZH957L+zH+KKHL8RH3JVLG3 d0Kr2OPIJS8l2wm68rHNHlZzgxf+86ZSJozCr0aHUajKZgrbkcxN1kHjpmVYFGKE4ru2 sYM1PdsCRqKdb9Qsq9dVHW9PgqEP+zbW+lpzskxg9F7sUZ/qGplVZ26DzVa7Zf6cXSxs 4VDT5LyYPwi6YB01+ofaDRv4T6x/njDLIAkfKRlYJ6Pyh10khS1DNXQGBX6AZFvSMf/B xWukBidZEUX6PiLltUZ041SbO8ZweKt/ly43PU6I4arWgmGEpUozaQlR8EA+7+8RplLh VnhA==
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; bh=mh/21OzOvJRveM43IE/S8931NCogtg1j912jicVi46s=; b=AOm4Qw1ENyKC3YhfXN5ijIeK97xTdk5XwQdHdYdDxokmqMugWXXls+CJcxAfmFYjrT BMuSWIOVEq18KMEObNaEx5sdmW4X2zclPwq1OnTWmdqQe7myz0FoeSmcS4tikio+foJp 0uMsIWBLQHfSWIzJny5bBxJx1zYbF2UoVWK908f8TD6JUB34TeU/OyMJj7LTukcpwUER Y0VqYbx7OeBsfuN/w/Ev35yyW9R/0kzHwTVrA9Ygmkzxw0R9lDf5IF6OV/YTYBMxnJ5S UGLFrq0aI4m2noMavWjnleVvVnNQrbaFOyao4U2zWLrMqWegxcxCOojwcXCi373RFnYs yv9w==
X-Gm-Message-State: AN3rC/6QWVW35kGG+2P3QqSJELVXKuJYAuHlt2pnXLk1hFh6MQHlbiEi mjUAetJFcbwluyOELJ8=
X-Received: by 10.84.143.1 with SMTP id 1mr1285963ply.70.1492053031779; Wed, 12 Apr 2017 20:10:31 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-121-9-radius.dynamic.acsalaska.net. [216.67.121.9]) by smtp.gmail.com with ESMTPSA id m3sm2401938pgn.30.2017.04.12.20.10.30 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 20:10:31 -0700 (PDT)
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: ietf@ietf.org
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <m2lgr5yttn.wl-randy@psg.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <b5846131-d912-b288-670b-2f74c901b2d5@gmail.com>
Date: Wed, 12 Apr 2017 19:10:28 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m2lgr5yttn.wl-randy@psg.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qtSRRfIWee90R71rlpV75RtdVr9iHV6PR"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YlTWFVN2i9bbKWtxBzpwgZBDHTA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 03:10:33 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qtSRRfIWee90R71rlpV75RtdVr9iHV6PR
Content-Type: multipart/mixed; boundary="s7ETstc1wA8CQeLAlbpm4HoxQXqwkXSct";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: ietf@ietf.org
Message-ID: <b5846131-d912-b288-670b-2f74c901b2d5@gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
 <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
 <m2lgr5yttn.wl-randy@psg.com>
In-Reply-To: <m2lgr5yttn.wl-randy@psg.com>

--s7ETstc1wA8CQeLAlbpm4HoxQXqwkXSct
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 4/12/17 5:33 PM, Randy Bush wrote:
> to me, the lack of predictibility on the draconian index is the main
> issue.  and for the uk as well as the states,  both seem to have a well=

> developed and practiced ability to do very damaging things on very, or
> no, notice.

+1

Melinda




--s7ETstc1wA8CQeLAlbpm4HoxQXqwkXSct--

--qtSRRfIWee90R71rlpV75RtdVr9iHV6PR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQIcBAEBCgAGBQJY7uwlAAoJELiGRpM6HoEumwIP/2drRhP3iYFPbz45yNcSerMs
u6BYMMT3lXZ9gF5//hRBiRPlQIEqcEpNTwgy4gmoJ5FgoEfRkdLuGUCwDno8T/CR
cdN6gZ4XqbPtviRG9pimJX07FlxHxW9rhp6V+ENaDDgIzmmNSNN/gL9xGroBWqw8
cgLOZwMQXKTBTCgpksBcHwi37tUnQMkxpmQa9zSpgHPZKOdd3SUgn1BVVsL8I2CB
mauwyEph2bpr8gmMmpDV3MUxw018UnxV81W3222KyfJrfnXOjO2ukCEcLInEaDuT
jFyveHRQ9ew7tMMshMp+w0MaVfar/+oQJJu+Kb0rZygwKYXTwtwGzXfE6Hrit8rA
MUtJUF969j2MANjgBuSkcO/jAG0lsaUGQ7mmufcshlpoYjS92Y1kRTHatrSyzWIc
vNWsWvdiz87+qi1OBrf6hwt6UVYN+OBWbpmO8+tZbJP5LEUt50KXQ9/QB/96jhEb
7SVpLkPViMqDMAsaUiMbKgjqwJhO2SG5fApeJgJdkC/ZSGxkRkrirZ9LsF07wMZb
1jv20rylpLFiXff8Hr4aShWW7ttC3Y4GA5SqPO8jwznSWbwWOQcXWZwHUvELXdJW
HRgViw3MSP3+o0V52jMZ73hZ4qQfHtI0rfbzPwbi7uUhL81mWoNLLtr3WYcm96eQ
5eNyVCzNh9nAOxEgmhsq
=HHTP
-----END PGP SIGNATURE-----

--qtSRRfIWee90R71rlpV75RtdVr9iHV6PR--


From nobody Wed Apr 12 20:38:24 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD3CD127867 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 gW1q2RM1c_Sr for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 20:38:15 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066051.outbound.protection.outlook.com [40.92.66.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398DD124D37 for <ietf@ietf.org>; Wed, 12 Apr 2017 20:38:15 -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; bh=cwkKSwvb7S4U4hMeOq9gDSOithZqkDt3oGPlQsvLvA8=; b=Wo/OU/UKcjr+4z7IDwhW42p3K3AYrAKpmo62ExQV+xY8cnrVzzq1Dnju6bWillYXU7MX2p94NErFwyiVCsZbC7HC63l1uYf53znPnYOYDGRDIsRnmcOhBkcPhUSGo4abs4h8QDmIgn13iQiaUilUsf+cL9ekwVvR/jh4vh7WCAFcIp2Y/7Wt5k5c1z6L9pNAcINQBlsZwTEwVx/4uugRElf/ZLu1tvQF6FAsPAUD7F9e8DeRkVqSFwQUJme3ggF32KbQZwSKkOLal9+L4eqF4Up7Wmx5hfF1/hHpcKwolZ4wkMstzEA89ANgJEOwcdOMu5PxFERdZ22O6pJqxxUxxA==
Received: from VE1EUR01FT022.eop-EUR01.prod.protection.outlook.com (10.152.2.51) by VE1EUR01HT078.eop-EUR01.prod.protection.outlook.com (10.152.3.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 03:38:13 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.2.53) by VE1EUR01FT022.mail.protection.outlook.com (10.152.2.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 03:38:13 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 03:38:13 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+Y54XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 03:38:12 +0000
Message-ID: <AM4PR0401MB22417EED46F47428FAB30353BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <m2efwxyqi5.wl-randy@psg.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:DA22C48C3D9099635B93B0C664338428AD28288C21253A4BA1B4E5540C2716CA; UpperCasedChecksum:B3767C7C4310B924578AEAD22E1602F3680E109EE4CD31922BF56E5DC065ED7F; SizeAsReceived:7801; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT078; 5:+gq5MEK6QK+key+4ihoXlk4t7XT0jpUicCLpX87A2iB5HaOzR6so3/LeYWChij8OyOcn2/jqlTHWAczn9/Ixa0A7dvl53Y5p4OlFZfhIcLxvcCs84OgmhhAwxQRbEYX8r0lZ1is60+W5xAfnj3YYr1WVYIWZyGRQXoknVppCrdc=; 24:/Qcb4lkiS/6DqwLSNPULlPkXz0hkLIxF1kBvNXGs5LLsvh2DI2OK4MI6jep7ZMQAXE06n3u/LSIh+erhW+z/G/lz+4ovkJPv71/vK67CjzE=; 7:Vdc/PiEu4TctRgwJha5+n2s7PCQf/K7P91X79WMnJGsMZ9yqmirljY3ski8BA1rWdn2ljOV/W77jJxHZ7miBh/BDxMVT/aWCVpl2uXvjL+lFvUdL8PFwA4TrpVRMmaxHpvV3BKGLwUsT2szvRBPdFAmL96oG7liT5D+Q22WWScZMeaPdvmURVRUa2dma6fPkc8L7IZstDmalLLJu7jwyTePgSxcz3T6hz2xeEX9CMqKY28jxOxrPsdkJNoSNT8YKLOBrfow50+muuoMARCAlIqrGjTOGB0zlz2ukjMRXbutUPN7n61JblW/ztP/wh4LR
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT078; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 695d4b31-4706-4e64-a55c-08d4821e82b3
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR01HT078; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT078; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT078; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB22417EED46F47428FAB30353BD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 03:38:12.9191 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT078
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I0bHVgOlhEtECCaMkCzng9EpWpQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 03:38:23 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBVcGRh
dGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMg0KRnJvbTog
S2hhbGVkIE9tYXINClRvOiBSYW5keSBCdXNoDQpDQzoNCg0KDQpZZXMsIEVneXB0IGlzIGEgc2Vy
aW91cyBjb250ZW5kZXIuDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0K
U3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5k
IElFVEYgMTAyDQpGcm9tOiBSYW5keSBCdXNoDQpUbzogS2hhbGVkIE9tYXINCkNDOiBMZXNsaWUg
RGFpZ2xlDQoNCg0KWyBvZmYgbGlzdCBdDQoNCj4gdGhlIG5leHQgSUVURiBtZWV0aW5ncycgbG9j
YXRpb24sIEkgd291bGQgc3VnZ2VzdCBDYWlybywgRWd5cHQNCg0KYSBzZXJpb3VzIGNvbnRlbmRl
ciBmb3IgaGlnaCB2YXJpYW5jZSBvbiB0aGUgZHJhY29uaWFuIHdpdGggbGl0dGxlDQp3YXJuaW5n
IGluZGV4Lg0KDQpyYW5keQ0K

--_000_AM4PR0401MB22417EED46F47428FAB30353BD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <AE0AEFFC39C22D40813EED4DBCA7E60E@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFj
ayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyPGJyPg0KRnJvbTogS2hhbGVkIE9t
YXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpUbzogUmFuZHkgQnVzaCA8cmFu
ZHlAcHNnLmNvbT48YnI+DQpDQzogPGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4N
CjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRl
ci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KWWVzLCBFZ3lwdCBpcyBh
IHNlcmlvdXMgY29udGVuZGVyLg0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdo
dDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJy
Pg0KU3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywg
YW5kIElFVEYgMTAyPGJyPg0KRnJvbTogUmFuZHkgQnVzaCA8cmFuZHlAcHNnLmNvbT48YnI+DQpU
bzogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpDQzogTGVz
bGllIERhaWdsZSA8bGRhaWdsZUB0aGlua2luZ2NhdC5jb20+PGJyPg0KPGJyPg0KPGJyIHR5cGU9
ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjow
IDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0K
WyBvZmYgbGlzdCBdPGJyPg0KPGJyPg0KJmd0OyB0aGUgbmV4dCBJRVRGIG1lZXRpbmdzJyBsb2Nh
dGlvbiwgSSB3b3VsZCBzdWdnZXN0IENhaXJvLCBFZ3lwdDxicj4NCjxicj4NCmEgc2VyaW91cyBj
b250ZW5kZXIgZm9yIGhpZ2ggdmFyaWFuY2Ugb24gdGhlIGRyYWNvbmlhbiB3aXRoIGxpdHRsZTxi
cj4NCndhcm5pbmcgaW5kZXguPGJyPg0KPGJyPg0KcmFuZHk8YnI+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM4PR0401MB22417EED46F47428FAB30353BD020AM4PR0401MB2241_--


From nobody Wed Apr 12 21:09:23 2017
Return-Path: <phluid61@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD0A128CDB for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 21:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wyBjv12ZYYD2 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 21:09:19 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001: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 844BA128B51 for <ietf@ietf.org>; Wed, 12 Apr 2017 21:09:19 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id r16so64071648ioi.2 for <ietf@ietf.org>; Wed, 12 Apr 2017 21:09:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=DnGsTw6M85CBL2KinO1NjQc1bXFWWvc+Dlx3nt+Nntg=; b=teFPoYYIVKs9ZXXubG6jNIz2wJJuSKbUPT7qTgIkCu5aA4K4vHimopQqtHoIUwAa5R RnayhecQaaDU5Tp9lB5wKJeMErX40f0IVmgeNX47UyhWe+Vqeu1kSr95wMidUzJ41qMC VTquDUk3j9kXAyCx8vgxoKZWUg+1WF7clvkZP5NiusCiJQYeIPactDJOsObeUViprL9l wP3Tz59cU2E4C4fNpKylF44IP3wtlOoew0gsYNf/bRuoCiBbD9IYed41udmUZpbt3MD4 Y/vka70f5rxbh1pQs/NTfRAR/mZJqY+KwgODxNsJfmEElvyWN3IqQHVAmmAqiVXKZ1QI I9OQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=DnGsTw6M85CBL2KinO1NjQc1bXFWWvc+Dlx3nt+Nntg=; b=iQiVqGD+UPa70xheVZyqp1L5NuHGc26IIM8yWjkc5QrWuheA17MOoeR9RYb27zDdIj B9gEOssCDj3fPQGmH+KE5JKLIi2VNK0NPpAhqDgckdwIV/AM9SzLla6Sm9WUC/py9XR0 YgbN91MMkqok6dfK6BfrdagyvpfgOeKd1hZn23ntM0+K4G9AzKfFG8wYJnfgQOTyUO4h 4vHmeC5ksUJV4nxhv1n4gjBf4lA+xmPtO7YY7jVD60q9vi6Ek1/ipzzhcfxN6wQ6KLtg nD+nTGnCtxSHe0QtL+2c+AA6eRelXlVyNm3a3Ii6csAdDoGc5m/gtF8sgEfY8AuKqHT9 W8aA==
X-Gm-Message-State: AN3rC/44O3GqOcjEMsva/5EnRBLjwZRtHSM4coAF6tqyWdfbdZmFCypM gKAkNUKN6GJhes1SjsTBx8Q69wD7SA==
X-Received: by 10.107.28.73 with SMTP id c70mr1696431ioc.198.1492056558941; Wed, 12 Apr 2017 21:09:18 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.169.67 with HTTP; Wed, 12 Apr 2017 21:09:18 -0700 (PDT)
In-Reply-To: <AM4PR0401MB22417EED46F47428FAB30353BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <m2efwxyqi5.wl-randy@psg.com> <AM4PR0401MB22417EED46F47428FAB30353BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Thu, 13 Apr 2017 14:09:18 +1000
X-Google-Sender-Auth: _0Z8BeRPFdNSQqp8wShFxAM13rk
Message-ID: <CACweHNA7owJ9RuLUZS7ZDtrUF-pqnGE6q0Q7oes+EMYJKsO_VQ@mail.gmail.com>
Subject: Re: Fw: Update on feedback on US-based meetings, and IETF 102
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113fe80e2e3c31054d047df2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UQqY4st2tZU-RaSUVADvnzmAl0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 04:09:21 -0000

--001a113fe80e2e3c31054d047df2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 13 April 2017 at 13:38, Khaled Omar <eng.khaled.omar@hotmail.com> wrote:

>
> -------- Original Message --------
> From: Randy Bush
> To: Khaled Omar
> CC: Leslie Daigle
>
> [ off list ]
>
> > the next IETF meetings' location, I would suggest Cairo, Egypt
>
> a serious contender for high variance on the draconian with little
> warning index.
>
> randy
>
>
=E2=80=8BWell, there's always Australi...uh, nevermind.

Cheers
--=20
  Matthew Kerwin
  http://matthew.kerwin.net.au/

--001a113fe80e2e3c31054d047df2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif;color:#073763"><span style=3D"font-family:arial,sans-serif;color:rgb(=
34,34,34)">On 13 April 2017 at 13:38, Khaled Omar </span><span dir=3D"ltr" =
style=3D"font-family:arial,sans-serif;color:rgb(34,34,34)">&lt;<a href=3D"m=
ailto:eng.khaled.omar@hotmail.com" target=3D"_blank">eng.khaled.omar@hotmai=
l.com</a>&gt;</span><span style=3D"font-family:arial,sans-serif;color:rgb(3=
4,34,34)"> wrote:</span><br></div><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">



<div>
<div class=3D"m_35263145388776624quote" style=3D"line-height:1.5"><br><bloc=
kquote class=3D"m_35263145388776624quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><div class=3D"m_35263145388776624quo=
te" style=3D"line-height:1.5">-------- Original Message --------<br>From: R=
andy Bush <u></u><br>
To: Khaled Omar <u></u><br>
CC: Leslie Daigle <u></u><br><br type=3D"attribution">
<blockquote class=3D"m_35263145388776624quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
[ off list ]<span class=3D""><br>
<br>
&gt; the next IETF meetings&#39; location, I would suggest Cairo, Egypt<br>
<br></span>
a serious contender for high variance on the draconian with little<br>
warning index.<br>
<br>
randy<br>
</blockquote>
</div>
</blockquote>
</div>
</div>

</blockquote></div><br><div class=3D"gmail_default" style=3D"font-family:ge=
orgia,serif;color:rgb(7,55,99)">=E2=80=8BWell, there&#39;s always Australi.=
..uh, nevermind.</div><div class=3D"gmail_default" style=3D"font-family:geo=
rgia,serif;color:rgb(7,55,99)"><br></div><div class=3D"gmail_default" style=
=3D"font-family:georgia,serif;color:rgb(7,55,99)">Cheers</div>-- <br><div c=
lass=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr=
">=C2=A0 Matthew Kerwin<br>=C2=A0 <a href=3D"http://matthew.kerwin.net.au/"=
 target=3D"_blank">http://matthew.kerwin.net.au/</a></div></div>
</div></div>

--001a113fe80e2e3c31054d047df2--


From nobody Wed Apr 12 22:23:03 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90DEE1293E4; Wed, 12 Apr 2017 22:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiHWAgaE0e2C; Wed, 12 Apr 2017 22:23:00 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 87B2B1270A0; Wed, 12 Apr 2017 22:22:59 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id u2so38277877wmu.0; Wed, 12 Apr 2017 22:22:59 -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=vm/9tGt8qR42e4bV5R5tAXmX0KfP3B2Fy5a8/6VVNcY=; b=PcSNVazJtacEZ7fsAsnrOPQbCpS9T0KYtAi2EWJabxn3v85Mdllj+/Uhcu6DsRTqwU 7paxQYgCHRznA9lV0shM7O3Xx9B08o1CGLGvjVz2m4Ks6ElmXcFWq1xP7n5Aiu8D9Dm3 fCMi3IhxYLycRp99jC9xwicAAzBOU+3Ao2aqZo7p6gn7RGte5xsA3xkrz3uqVLcpM9rw N//PV4478vjphfug5tKuJY411l/V031TnCKWdVgvdxbwRI4byrbCIHPH+c9tB62sZf7H 4LEckxI8mciel5R9Zl86f+70UrizAJdMZQI9l8ljxllwZDRT03UFOykBWKUpZyii0rEu jxYw==
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=vm/9tGt8qR42e4bV5R5tAXmX0KfP3B2Fy5a8/6VVNcY=; b=DJ4HgRl4/NqXB/vhHuvpgYac2of4Ws+UdPGXz52nLncQoeO6PUZYGAU0/e7joidThR QNhhT54hf+yO9vUnIxgvD/4MUEJzOpMY4v/u6dslh+Dc3CPGaUndQrhBtlSJWnBOZ+2i pJ5lTAo7Hb8Lc/jW1wQ+0JrRPNAUqmZfby9hTd1mZu2WSChi8Uovcnfj5INwQ6d1d+aj znW0SARUM+XDE1R6/rV5HM1odfkno8bLiZGOnPFk4CBn+/otrBrhFuUoQ+BSEr2ErgN1 nhNnI8bdrTx1wJgBZ2bh7tTFE6Jqld9DTiifjalx+Rl7hQgSgegoh5MmfEvWjoX2TnvG i+rw==
X-Gm-Message-State: AN3rC/4tUe2Sp1zxQUkea/QM3x/wh9nh/OW5k8jGkeS5wDz2wDRml68S yJ9Qcu+c/eIakyWZC6Q=
X-Received: by 10.28.138.209 with SMTP id m200mr1317305wmd.109.1492060978081;  Wed, 12 Apr 2017 22:22:58 -0700 (PDT)
Received: from [192.168.137.62] ([109.253.214.44]) by smtp.gmail.com with ESMTPSA id g53sm3798288wrg.22.2017.04.12.22.22.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 22:22:57 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <D8982F24-0151-4762-BFE9-AD80DB674C0A@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6702BC96-9B14-4E7E-A48B-0C3611E02209"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Date: Thu, 13 Apr 2017 08:22:52 +0300
In-Reply-To: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
Cc: IETF <ietf@ietf.org>, IAOC List <iaoc@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4LGcGH-Kn4E7c4_-dJ442o92C-U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:23:01 -0000

--Apple-Mail=_6702BC96-9B14-4E7E-A48B-0C3611E02209
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 13 Apr 2017, at 3:00, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:


> I do not recall the opposite on the list, i.e. someone adamantly
> arguing that we ought continue to meet in the US. There were some
> mails that I'd say maybe weakly argued for continued US meetings
> in the relevant timeframe. But nothing approaching adamant.

Well at this point arguing for more US meetings because I had no trouble =
obtaining a visa and entering the US is the equivalent of stating that =
I=E2=80=99m a white guy and I=E2=80=99m not feeling any racism or =
sexism.

More to the point, pretty much all US venues work out better than pretty =
much any European let alone Asian venues, weirdly shaped rooms =
notwithstanding. London and Paris come close. Berlin and Prague don=E2=80=99=
t. This is in terms of nearby availability of food (notice the lack of a =
=E2=80=9COMG where can I get a grab-and-go sandwich=E2=80=9D thread in =
98attendees) and in terms of the availability of nearby low-cost hotels. =
And yes, the fact that everybody speaks English also helps. And despite =
what people think about crime, no IETF-er ever got shot in the US during =
IETF week, but every time we meet in Europe some of us will get their =
pockets picked.

For me, US meetings (Canada=E2=80=99s OK too) are more convenient =
despite the long, tortuous flight. People have been grumbling about US =
entry procedure for years and with good reason. But overall US meetings =
are simply more convenient. YMMV

Yoav


--Apple-Mail=_6702BC96-9B14-4E7E-A48B-0C3611E02209
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-----

iQEcBAEBCgAGBQJY7wstAAoJELhJCxUKWMyZirwH/jkZr4lUXZKikQmodZe+Bxvq
BG2/rW9SaJwPalq4D+fYKqkN8KfZJ2UmGmA91sE8FV0huFmbqwHYWAuui/bUehVg
A1uR1iLfVP+rYWsstJzirF/EJe5UtHRTYlBNKJNT3Q5tJXAbkK85V9AcKXa+/pzQ
CBgzStVnvNd4KECkNgr2PdJB+zga3M9NpfkznSooIL8yZuX6KIulImVGxG/Rp+Bn
++SRzufOjFNeIR760hIVb2I+qQcza3NEEc8QcLIoS1rM7YsCUCbQkeUIqIc0CbAN
4HHMLXWw7MbNV/yJ6N7pVQBSVrYgUtO/soRfrl7AH6R0iC5R4+lDOwQ3FOnFYPs=
=3cR2
-----END PGP SIGNATURE-----

--Apple-Mail=_6702BC96-9B14-4E7E-A48B-0C3611E02209--


From nobody Wed Apr 12 22:37:05 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2DAF1250B8 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=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 GOZ6OmmeenWH for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:37:01 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071105.outbound.protection.outlook.com [40.92.71.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 33FD512009C for <ietf@ietf.org>; Wed, 12 Apr 2017 22:37:01 -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; bh=hEgontU5fdxEYhlw8pnC5lpe3HsA5153Bp9yM5TlUKk=; b=jU6DWoKbj45VicLmfdGhj8fypL6vTrGFnRYvEuD6aOMh+jo49HLI6Wu7tvxyY7uxgPnGbtCxee+W9ZKYIfxCJ6eDalZoQJ/bD9HMA0yrl+tSWI0A0Frc3K9DJpqyyA/rzfflbFhsw5kEFKNR0NlHAYl87EINcBYV/JDZI/a0QHkVSN/cAR6RVyqt/JoDNIWOeo6Lqf72FHcvgsA8y2ophMfaTRTteUGaYel2l3oLgwnJuwb5BeTwoSCYeFAAa1rTukts4jXXrVpqgWUbQtR6bRYgvEgEjGE3NiwOUZlIau2DTb/e7R/EH48n35RSwj1yLVn1ImbBPziKihyNvlpvcg==
Received: from DB5EUR03FT064.eop-EUR03.prod.protection.outlook.com (10.152.20.53) by DB5EUR03HT018.eop-EUR03.prod.protection.outlook.com (10.152.20.251) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 05:36:58 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.20.52) by DB5EUR03FT064.mail.protection.outlook.com (10.152.21.199) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 05:36:58 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 05:36:57 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Matthew Kerwin <matthew@kerwin.net.au>
CC: ietf <ietf@ietf.org>
Subject: Re: Fw: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Fw: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+Y54XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 05:36:57 +0000
Message-ID: <AM4PR0401MB22414AE3B248E376C2747642BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CACweHNA7owJ9RuLUZS7ZDtrUF-pqnGE6q0Q7oes+EMYJKsO_VQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: kerwin.net.au; dkim=none (message not signed) header.d=none;kerwin.net.au; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:6F6FACB812D19D48FD3AA3BF99394FC20C9ABD4F39A6ACFD031E68FF81022DF1; UpperCasedChecksum:D67D5F1CEEB11F16B2F5FEEC90C87B3FD069DE2B79901C05ABF20E703850BD1B; SizeAsReceived:7887; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; DB5EUR03HT018; 5:6B9dUGz0fEBJa91e6YORMAfTi5AT7e0m/z1KAmrf/LYhmMvNW7w7dzPYOHaDU1bXA2HBGywC9+VZSUcNl1dNbUUj3YFv/xETw3b2doR/ZDQKvx2M9H+q8iEFn1ZlL7BN5JRUzmF/JIsBKBF/FNudaA==; 24:Miw506R2nUKaFx41f2TDYNIoFvbczDOHYWG1fQ8Wsbhlrahy2zdKXGYkkrz9cP30jKfVURPParIWKRYI9DARk5gFMWbSS091wIb8Ep/l0pY=; 7:IxFieffa5IM6OywU8rA+Vp6lQf7n+HxzYy4VKw/oRpstwm8fOS/iAk+giSfQF9nIVviWIdQgGTU+scQTJMg3Y7vEfJlMLsEYEpNu82PPLJKhkM5qLY1iiZ4U6bS3h8RHFlYTfDopCQ5C8584FiJEBalyi4X6c/2s7/kqDylUTV7Sk4DMUive91miV96fj0Yv/9kqA/beZzi47h1Hr+V81/k995XlMt1wAp4WsMDxdJrPIAUx9dfTr4bJSyb7G9lmb7BxJuaBCKSavByLdjBirPgaO7OEGPQRXgEhwvF9YOx8kJoKFxQke+3z2uTXXJyd
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR03HT018; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 090bda67-40bf-457b-ddc4-08d4822f1920
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:DB5EUR03HT018; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:DB5EUR03HT018; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR03HT018; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB22414AE3B248E376C2747642BD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 05:36:57.7633 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT018
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4aEbQRqjt_k8ZgjzHxZJHxJ-D0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:37:03 -0000

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

U28gZmFyLCBidXQgbmljZSBjb3VudHJ5Lg0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2Ug
LS0tLS0tLS0NClN1YmplY3Q6IFJlOiBGdzogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2Vk
IG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206IE1hdHRoZXcgS2Vyd2luDQpUbzogS2hhbGVk
IE9tYXINCkNDOiBpZXRmDQoNCg0KT24gMTMgQXByaWwgMjAxNyBhdCAxMzozOCwgS2hhbGVkIE9t
YXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTxtYWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhv
dG1haWwuY29tPj4gd3JvdGU6DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0N
CkZyb206IFJhbmR5IEJ1c2gNClRvOiBLaGFsZWQgT21hcg0KQ0M6IExlc2xpZSBEYWlnbGUNCg0K
WyBvZmYgbGlzdCBdDQoNCj4gdGhlIG5leHQgSUVURiBtZWV0aW5ncycgbG9jYXRpb24sIEkgd291
bGQgc3VnZ2VzdCBDYWlybywgRWd5cHQNCg0KYSBzZXJpb3VzIGNvbnRlbmRlciBmb3IgaGlnaCB2
YXJpYW5jZSBvbiB0aGUgZHJhY29uaWFuIHdpdGggbGl0dGxlDQp3YXJuaW5nIGluZGV4Lg0KDQpy
YW5keQ0KDQrigItXZWxsLCB0aGVyZSdzIGFsd2F5cyBBdXN0cmFsaS4uLnVoLCBuZXZlcm1pbmQu
DQoNCkNoZWVycw0KLS0NCiAgTWF0dGhldyBLZXJ3aW4NCiAgaHR0cDovL21hdHRoZXcua2Vyd2lu
Lm5ldC5hdS8NCg==

--_000_AM4PR0401MB22414AE3B248E376C2747642BD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <1B711719EF6D4C469768BFE5ECCB87A6@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KU28gZmFyLCBidXQg
bmljZSBjb3VudHJ5Lg0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41
Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3Vi
amVjdDogUmU6IEZ3OiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFu
ZCBJRVRGIDEwMjxicj4NCkZyb206IE1hdHRoZXcgS2Vyd2luIDxtYXR0aGV3QGtlcndpbi5uZXQu
YXU+PGJyPg0KVG86IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PGJy
Pg0KQ0M6IGlldGYgPGlldGZAaWV0Zi5vcmc+PGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0
aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4
O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdiBkaXI9
Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6Z2Vv
cmdpYSxzZXJpZjtjb2xvcjojMDczNzYzIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWws
c2Fucy1zZXJpZjtjb2xvcjpyZ2IoMzQsMzQsMzQpIj5PbiAxMyBBcHJpbCAyMDE3IGF0IDEzOjM4
LCBLaGFsZWQgT21hcg0KPC9zcGFuPjxzcGFuIGRpcj0ibHRyIiBzdHlsZT0iZm9udC1mYW1pbHk6
YXJpYWwsc2Fucy1zZXJpZjtjb2xvcjpyZ2IoMzQsMzQsMzQpIj4mbHQ7PGEgaHJlZj0ibWFpbHRv
OmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmVuZy5raGFsZWQu
b21hckBob3RtYWlsLmNvbTwvYT4mZ3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTph
cmlhbCxzYW5zLXNlcmlmO2NvbG9yOnJnYigzNCwzNCwzNCkiPiB3cm90ZTo8L3NwYW4+PGJyPg0K
PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9xdW90
ZSI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAg
LjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXY+
DQo8ZGl2IGNsYXNzPSJtXzM1MjYzMTQ1Mzg4Nzc2NjI0cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdo
dDoxLjUiPjxicj4NCjxibG9ja3F1b3RlIGNsYXNzPSJtXzM1MjYzMTQ1Mzg4Nzc2NjI0cXVvdGUi
IHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRk
aW5nLWxlZnQ6MWV4Ij4NCjxkaXYgY2xhc3M9Im1fMzUyNjMxNDUzODg3NzY2MjRxdW90ZSIgc3R5
bGU9ImxpbmUtaGVpZ2h0OjEuNSI+LS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLTxi
cj4NCkZyb206IFJhbmR5IEJ1c2ggPHU+PC91Pjxicj4NClRvOiBLaGFsZWQgT21hciA8dT48L3U+
PGJyPg0KQ0M6IExlc2xpZSBEYWlnbGUgPHU+PC91Pjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlv
biI+DQo8YmxvY2txdW90ZSBjbGFzcz0ibV8zNTI2MzE0NTM4ODc3NjYyNHF1b3RlIiBzdHlsZT0i
bWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0
OjFleCI+DQpbIG9mZiBsaXN0IF08c3BhbiBjbGFzcz0iIj48YnI+DQo8YnI+DQomZ3Q7IHRoZSBu
ZXh0IElFVEYgbWVldGluZ3MnIGxvY2F0aW9uLCBJIHdvdWxkIHN1Z2dlc3QgQ2Fpcm8sIEVneXB0
PGJyPg0KPGJyPg0KPC9zcGFuPmEgc2VyaW91cyBjb250ZW5kZXIgZm9yIGhpZ2ggdmFyaWFuY2Ug
b24gdGhlIGRyYWNvbmlhbiB3aXRoIGxpdHRsZTxicj4NCndhcm5pbmcgaW5kZXguPGJyPg0KPGJy
Pg0KcmFuZHk8YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjxkaXYgY2xhc3M9ImdtYWls
X2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTpnZW9yZ2lhLHNlcmlmO2NvbG9yOnJnYig3LDU1
LDk5KSI+4oCLV2VsbCwgdGhlcmUncyBhbHdheXMgQXVzdHJhbGkuLi51aCwgbmV2ZXJtaW5kLjwv
ZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5Omdlb3Jn
aWEsc2VyaWY7Y29sb3I6cmdiKDcsNTUsOTkpIj48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9Imdt
YWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTpnZW9yZ2lhLHNlcmlmO2NvbG9yOnJnYig3
LDU1LDk5KSI+Q2hlZXJzPC9kaXY+DQotLSA8YnI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9zaWduYXR1
cmUiIGRhdGEtc21hcnRtYWlsPSJnbWFpbF9zaWduYXR1cmUiPg0KPGRpdiBkaXI9Imx0ciI+Jm5i
c3A7IE1hdHRoZXcgS2Vyd2luPGJyPg0KJm5ic3A7IDxhIGhyZWY9Imh0dHA6Ly9tYXR0aGV3Lmtl
cndpbi5uZXQuYXUvIiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL21hdHRoZXcua2Vyd2luLm5ldC5h
dS88L2E+PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB22414AE3B248E376C2747642BD020AM4PR0401MB2241_--


From nobody Wed Apr 12 22:53:13 2017
Return-Path: <cheshire@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8B81293E0 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=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 pHDhPEC1QBne for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:53:09 -0700 (PDT)
Received: from mail-in21.apple.com (mail-out21.apple.com [17.171.2.31]) (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 97C0C127201 for <ietf@ietf.org>; Wed, 12 Apr 2017 22:53:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1492062788; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ynhZtJ+zD8DkXmpIZacyrL01VH5Ia97z0k1h8lV6j7k=; b=E935uCSKFKRNgv3BV6HaVBNS6uLgTb5B74rr94a5hLFetenyh53hm7d5EJkZFrJo 5ykoAAL+u/dYnuBSKmHwlmBbAe5hDT5bwAgE2WfsKA4uS+FMFtCKyyZie3NDdr// J5SO7BFxzKcLLW4LYLbSCsqmP5DmBRAiJr2vsijq4yixjVu0adbtq+7YYSSImWt3 dBGPVQduf5zOq4bofTBaovwdTOHuGIpdQz/vKAl6z21DHDmZAc5fAwygB65/0L7n 09nJ7DB2pqg5EOQplioOtqCctGsR8YIvp+C9SmwcF/dv1VMg+6CCfvIZ58dH8sX4 G7+Qna5MXH4OnV7vM0Zv9Q==;
Received: from relay7.apple.com (relay7.apple.com [17.128.113.101]) by mail-in21.apple.com (Apple Secure Mail Relay) with SMTP id CC.2C.13165.3421FE85; Wed, 12 Apr 2017 22:53:08 -0700 (PDT)
X-AuditID: 11ab0215-dc5879a00000336d-9f-58ef12435967
Received: from kencur (kencur.apple.com [17.151.62.38]) by relay7.apple.com (Apple SCV relay) with SMTP id 34.87.26825.3421FE85; Wed, 12 Apr 2017 22:53:07 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Received: from [10.0.1.35] (50-197-138-101-static.hfc.comcastbusiness.net [50.197.138.101]) by kencur.apple.com (Oracle Communications Messaging Server 8.0.1.2.20170210 64bit (built Feb 10 2017)) with ESMTPSA id <0OOC00MTF30HRX60@kencur.apple.com>; Wed, 12 Apr 2017 22:53:07 -0700 (PDT)
Sender: cheshire@apple.com
Subject: Re: [dnssd] Last Call: <draft-ietf-dnssd-mdns-dns-interop-04.txt> (On Interoperation of Labels Among Conventional DNS and Other Resolution Systems) to Informational RFC
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <149090820270.9007.2835487042847566330.idtracker@ietfa.amsl.com>
Date: Wed, 12 Apr 2017 22:53:07 -0700
Cc: IETF-Announce <ietf-announce@ietf.org>, draft-ietf-dnssd-mdns-dns-interop@ietf.org, dnssd@ietf.org, dnssd-chairs@ietf.org, Suzanne Woolf <suzworldwide@gmail.com>, terry.manderson@icann.org
Content-transfer-encoding: quoted-printable
Message-id: <099780BE-C3BC-4EF7-8C0F-93522195E6AE@apple.com>
References: <149090820270.9007.2835487042847566330.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3124)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUi2FCYqusi9D7CoOOOicWVd33MFu+XzmK0 +Pb7HZvFvTPT2SyebZzPYtE0ZRqrRevRm6wO7B47Z91l9zh84T6Lx5IlP5kCmKO4bFJSczLL Uov07RK4MpZ9+cxasNCy4uaNe+wNjEv1uhg5OSQETCRuT7/F0sXIxSEksJ9R4sLVWUwwictv jrBCJFYwSrx+v4INJMErICjxY/I9oA4ODmYBdYkpU3Khapgkutd2g9UIC0hJvFr5mRkkISyw lVFi8fnFLCAJNgEtiRefr4AVcQr4Skzp2QW2jUVAVWLroYlg25gFjjFKPH12F6yIWUBb4sm7 C6wg23gFbCQ2vaoECQsJ+EhMn32BCSQsAnTQwceWEEfLSjw5uQjsGwmBHWwSj+beZ53AKDwL yd2zEO6ehWTBAkbmVYzCuYmZObqZeUaGeokFBTmpesn5uZsYQZGxmkl0B+P8V4aHGAU4GJV4 eDsE30cIsSaWFVfmHmKU5mBREuedPvVdhJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG6owp 1i7RFXqb7Or7pixhP3e67vV0NaVlQj8+TP8n8VE1KLosImiOw1Efhq85DoJNjltyNPhbF7sr zWNh+5PaYH3OZx6jpn2jl5/pmndcD1wkt6d9+Sz9ZgrHy4VyX7ImL86eknzl65SrYk3q92bu fqFS76Cc7K+1Q+5/7N51/qkCxY0KKTuUWIozEg21mIuKEwHhXzGvbQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUiON1OTddZ6H2Ewf13OhZX3vUxW7xfOovR 4tvvd2wW985MZ7N4tnE+i0XTlGmsFq1Hb7I6sHvsnHWX3ePwhfssHkuW/GQKYI7isklJzcks Sy3St0vgylj25TNrwULLips37rE3MC7V62Lk5JAQMJG4/OYIaxcjF4eQwApGidfvV7CBJHgF BCV+TL7H0sXIwcEsoC4xZUouVA2TRPfabrAaYQEpiVcrPzODJIQFtjJKLD6/mAUkwSagJfHi 8xWwIk4BX4kpPbuYQGwWAVWJrYcmgm1jFjjGKPH02V2wImYBbYkn7y6wgmzjFbCR2PSqEiQs JOAjMX32BSaQsAjQQQcfW0IcLSvx5OQilgmMArOQnDoL4dRZSGYuYGRexShQlJqTWGmul1hQ kJOql5yfu4kRFMYNhak7GBuXWx1iFOBgVOLhPSH7LkKINbGsuDL3EKMEB7OSCO/sn0Ah3pTE yqrUovz4otKc1OJDjNIcLErivJdF3kQICaQnlqRmp6YWpBbBZJk4OKUaGO2nuCo0fErgl9vA r7mnScfs3pyJFz/uTdptv+zSgaRZO8+ZTdE7dfjwJu0jm899K1y87vabXjGp0GPczUckt/3d 7KMdeE0mcPukF10RDmslU527lZakK8T6ml4QUF+8Z1H9vGR3q51ST48yTn6exZ0au+SuKYep /axeuW0J8ifv3S6sOBx+20+JpTgj0VCLuag4EQB1gAN3XwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xk-70enoepfg3g2pCqlxVIdICVQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:53:12 -0000

On 30 Mar 2017, at 14:10, The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has received a request from the Extensions for Scalable DNS
> Service Discovery  WG (dnssd) to consider the following document:
> - 'On Interoperation of Labels Among Conventional DNS and Other
>   Resolution Systems'
>  <draft-ietf-dnssd-mdns-dns-interop-04.txt> as Informational RFC

Overall I think this document is very good.

Re-reading draft-04 today, I have a few minor comments.

Page 3:

> Users and developers of applications are, of course, frequently
> unconcerned with (not to say oblivious to) the name-resolution
> system(s) in service at any given moment

Does =E2=80=9Cnot to say=E2=80=9D mean =E2=80=9Cnot oblivious=E2=80=9D =
or =E2=80=9Coblivious=E2=80=9D?

It would be clearer to say:

> Users ... are, of course, frequently unconcerned with (but not =
oblivious to) ...

or

> Users ... are, of course, frequently unconcerned with (or even =
oblivious to) ...

Page 3:

> As a result, the same domain name might be tried using different name =
resolution technologies.

Any given name may only be looked up using the single name resolution =
technology appropriate for that name.

It might be clearer to say:

> As a result, names entered into the same domain name slot might be =
resolved using different name resolution technologies.

Page 3:

> the global DNS is eventually likely to be implicated

The global DNS is already used for service discovery. Every time someone =
prints at an IETF meeting using AirPrint to the Terminal Room printer, =
the global DNS is being used. This is now, not the future.

How about just removing the word =E2=80=9Ceventually=E2=80=9D?

Page 5:

> In any case, if a given portion is implicated, the
> profile will need to apply to all labels in that portion.

This is overly strict. It=E2=80=99s not necessarily all-or-nothing. The =
<Domain> portion of the Service Instance Name may require mixed =
handling. Consider the Service Instance Name:

Public Printer._ipp._tcp.3rd Floor.caf=C3=A9.com.

The <Instance> portion, =E2=80=9CPublic Printer=E2=80=9D, is UTF-8.

The <Service> portion, =E2=80=9C_ipp._tcp=E2=80=9D, is plain ASCII, and =
uncomplicated.

The <Domain> portion is mixed.
=E2=80=9C3rd Floor=E2=80=9D has a space, and has to be UTF-8.
But =E2=80=9Ccaf=C3=A9.com=E2=80=9D is actually registered as =
=E2=80=9Cxn--caf-dma.com=E2=80=9D and has to be converted as such.

Fortunately the iterative algorithm described in RFC 6763, and =
implemented and shipping in Apple products and the Open Source =
mDNSResponder code, handles this. So, while this may appear to be a =
problem, it is in fact a solved problem.

Page 6:

> some recommendations from [RFC6763] will not really be possible to =
implement

Can you elaborate on what recommendations are not possible to implement?

> many labels in the <Domain> part of a Service Instance Name are
> unlikely to be found in the UTF-8 form in the public DNS tree

Saying =E2=80=9Cunlikely=E2=80=9D is too strong. An administrator who =
wants spaces or similar exotic Unicode characters in a service discovery =
domain name will have to use UTF-8 for that name, even if host names in =
the same zone use Punycode. And this is not hard to do. You simply edit =
the zone file using a UTF-8-capable text editor, and type in the desired =
UTF-8 text. Name servers such as =E2=80=98named=E2=80=99 will happily =
serve that zone. The name server itself doesn=E2=80=99t need to be =
UTF-8-capable in any way. It just acts on the bytes in the zone file, =
without attempting to interpret how humans will perceive those bytes.

Page 6:

> mDNS normally uses UTF-8.

should say:

> mDNS exclusively uses UTF-8.

Page 7:

> As a practical matter, this
> likely means special-purpose name resolution software for DNS-SD.

This reads as if it=E2=80=99s talking about some hypothetical future. =
This special-purpose name resolution software is already used for =
service discovery, and has been since Mac OS X 10.2 in 2002. This =
special-purpose name resolution software, and its APIs, is on Apple =
products, Microsoft Windows, Linux, and Android. So, again, this text is =
describing a non-problem. It=E2=80=99s like text warning against using =
JPEG as an image format in 2017, because JPEG images require =
=E2=80=9Cspecial-purpose JPEG image decoding software=E2=80=9D, at a =
time when all major platforms have had JPEG image decoding software for =
many years.

Page 8:

> DNS-SD implementations ought somehow to identify the <Domain> portion =
of
> the Service Instance Name and treat it subject to IDNA2008 in case the
> domain is to be queried from the global DNS.  In the event that the
> <Domain> portion of the Service Instance Name fails to resolve, it is
> acceptable to substitute labels with plain UTF-8, starting at the
> lowest label in the DNS tree and working toward the root.  This
> approach differs from the rule for resolution published in [RFC6763],
> because it privileges IDNA2008-compatible labels over UTF-8 labels.

If we want to recommend this change in behavior, I think this document =
is the wrong place to do it.

RFC 6763 is a published Standards-Track specification. For good or bad, =
it went though thorough lengthy review, and is a result of the IETF =
consensus process. I think it=E2=80=99s confusing to have an =
Informational RFC that appears to update a Standards-Track RFC. Should =
an implementer follow RFC 6763 because it=E2=80=99s a Standards-Track =
specification and this document is merely Informational, and doesn=E2=80=99=
t say, =E2=80=9CUpdates: RFC 6763=E2=80=9D? Or should an implementer =
follow this document because it=E2=80=99s newer and therefore is assumed =
to supersede any text found in older Standards-Track RFCs?

RFC 6763 specifies an iterative algorithm that is implemented, and in =
use, and appears to work. Overturning that specification should require =
careful scrutiny and Standards-Track action. In 2017, does the IETF want =
to be encouraging movement towards UTF-8 as the universal encoding for =
everything, or encouraging continued diversification into =E2=80=9Cevery =
protocol invents its own different incompatible encoding for =
international text=E2=80=9D?

Page 8:

> The first of these is rejected because it represents a potentially
> significant increase in DNS lookup traffic for no value.

I request removing the value judgement =E2=80=9Cfor no value=E2=80=9D.

The value of using UTF-8 is that it is both more compact and more =
expressive than Punycode.

How about:

> An issue with the first of these is that it represents a potentially
> significant increase in DNS lookup traffic.

Page 8:

> it is unlikely that the UTF-8 version of the zone will be delegated =
from anywhere

This is circular logic. An administrator using a UTF-8 zone *will* make =
sure that UTF-8 zone is accessible, or there=E2=80=99s no point having =
it. This could be done by delegation, but need not be. Subdomains =
don=E2=80=99t have to be delegated -- subdomains can exist in a single =
zone. Not all subdomain boundaries need to be zone cuts, and many are =
not.

Stuart Cheshire


From nobody Wed Apr 12 22:55:29 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8308F128B8F for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 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, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 qnD3v2m4iPUF for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:55:26 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065058.outbound.protection.outlook.com [40.92.65.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97798127201 for <ietf@ietf.org>; Wed, 12 Apr 2017 22:55:25 -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; bh=Y6Rmj3uu6yVRpPKJLdLDo4J2CgLLG3RrWOrknzYLKtg=; b=mClANdO+uWqZ64VYBYuDBYZHdZWmVvMQyhIpVNL7SQ71ySnSqDaGMzskYrWTGz9FY8fPlZ2PCbV0VluA6gHeNG9H65ynDHwQhBi3JBCQcVxOedlSZtlfG7NuFAairjZpP+f6fyON7DDnIHWdRkUKoTfjYs2IDS0geNG5ecDt1VFfXV0cVU1SPLfr5AubPU0NLT2MZnMeN0gCMxvY3v+/cO90QxtHlmN0U0HoKeCCnsnYIRfbltQQE26iciBm1qHrOQDHsT7FokQ6y8y7SE9+cY7x6YWC1AYDZdQC37GcZUDxxVbY/Re66YiRBle57cImgu6XqE/ovjQ6AIou2mPKFw==
Received: from VE1EUR01FT040.eop-EUR01.prod.protection.outlook.com (10.152.2.60) by VE1EUR01HT080.eop-EUR01.prod.protection.outlook.com (10.152.3.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 05:55:23 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.2.54) by VE1EUR01FT040.mail.protection.outlook.com (10.152.3.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 05:55:23 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 05:55:22 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
CC: ietf <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+kD4XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 05:55:22 +0000
Message-ID: <AM4PR0401MB2241D2424F3027B4DB2496A7BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <D8982F24-0151-4762-BFE9-AD80DB674C0A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:C8B4CEB42ECEFC643E36732264BC3A2F331D6E4CB4B85FB4BE329C95B49FFEDC; UpperCasedChecksum:B1AACC14D6249D6FDBD0A55C3355A13264C84EE7C72DD022782A69830A5DCB9E; SizeAsReceived:7852; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT080; 5:CCX/7mwZkECAtXUHVP3UPpIhNUi1oihuYtX4O0JhUcdgCC8XLDPWOgIrccu5D9DfTZgs29+dJuTz7hcjvZDfthDG1iGsQ8Ybq7+gEr+rlhbby+tJhxGhS5IS1el8AzJpJqh9yOHc7qSt2tRWkwyEUA==; 24:2Xqs+1JGW6HxM9V6+1lYFwH8nOIx7EX2lt4GrPbPJd2DakcpqSo1XEZUO04wHGS/mLhNsgFJChnysOzW21hxMC0wnwEls5p1bm5FEHMVZpY=; 7:fBYHe61l7vrlUC0n24FDtsfXRnllH9Z+ercK8akFCJqCNfV1PkuKJx81245vtMzR78Xswr+b60F5Gy5CpcLXz4lVqtXCYA5bvNIkKW5pv3BzdrZteuwvmyMji5BsRmaJO1Ttimksscx3PS04wPIQFy5/sV5a52idhZDdtacJxBlQjP0rnAEYTAXK1GQ6dgz8nUcMeE4vUhOkPzgKxJSB6N3FTIMLPlBT8Tj9N/KTJwlTwHiG8bL8fXhnlVDjUby6YMoTifZFVhKJA+61mQFxyAPtwLxCV3Tc/i2bQW+9tLDWl9vK1efMtzgDs33CAxYD
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT080; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 6e2222f7-7d7b-4242-b573-08d48231abff
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:VE1EUR01HT080; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT080; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT080; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241D2424F3027B4DB2496A7BD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 05:55:22.7101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT080
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n8xLmhRgZH5-lJ2LaO_VyZhPT3M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:55:27 -0000

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

SSByZWNvbW1lbmQgRWd5cHQgYmVjYXVzZSBpdCBpcyBhdCB0aGUgY2VudGVyLCB3aWxsIG5vdCBi
ZSBzbyBsb25nIGZvciBhbnlvbmUsIGFsc28sIHdlYXRoZXIgaXMgYW4gaW1wb3J0YW50IGZhY3Rv
ciwgYW5kIGZvciB0aG9zZSB3aG8gd291bGQgbGlrZSB0byB2aXNpdCBoaXN0b3JpY2FsIHBsYWNl
cyBzaG91bGQgZm9jdXMgbW9yZSBhYm91dCBob3cgdG8gZ28gYW5kIHdoYXQgdG8gd2VhciwgdGhl
cmUgYXJlIG1vZGVybiBjaXRpZXMgYW5kIG9sZCBjaXRpZXMsIHRoZXJlIGlzIGEgYmlnIGRpZmZl
cmVuY2UsIG1hbnkgdG91cmlzdHMgaGVyZSB3aXRoIGFsbCBkaWZmZXJlbnQgc3R5bGVzLCBhbmQg
b2YgY291cnNlIG5vIG9uZSB3aWxsIGRpc3Jlc3BlY3QgcG9lcGxlIGhlcmUgc28gaGUvc2hlIHdp
bGwgZ2V0IGluIHRyb3VibGUuDQoNCkJ1dCByZWdhcmRpbmcgQ2FuYWRhLCBmdWxsIHJlc3BlY3Qg
dG8gdGhvc2UgcGVvcGxlIGFuZCB0aGV5IHdpbGwgYmUgbW9yZSB0aGFuIHdlbGNvbWVkIGhlcmUu
DQoNClJlZ2FyZHMsDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0KU3Vi
amVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElF
VEYgMTAyDQpGcm9tOiBZb2F2IE5pcg0KVG86IFN0ZXBoZW4gRmFycmVsbA0KQ0M6IElBT0MgTGlz
dCAsSUVURg0KDQoNCk9uIDEzIEFwciAyMDE3LCBhdCAzOjAwLCBTdGVwaGVuIEZhcnJlbGwgd3Jv
dGU6DQoNCg0KPiBJIGRvIG5vdCByZWNhbGwgdGhlIG9wcG9zaXRlIG9uIHRoZSBsaXN0LCBpLmUu
IHNvbWVvbmUgYWRhbWFudGx5DQo+IGFyZ3VpbmcgdGhhdCB3ZSBvdWdodCBjb250aW51ZSB0byBt
ZWV0IGluIHRoZSBVUy4gVGhlcmUgd2VyZSBzb21lDQo+IG1haWxzIHRoYXQgSSdkIHNheSBtYXli
ZSB3ZWFrbHkgYXJndWVkIGZvciBjb250aW51ZWQgVVMgbWVldGluZ3MNCj4gaW4gdGhlIHJlbGV2
YW50IHRpbWVmcmFtZS4gQnV0IG5vdGhpbmcgYXBwcm9hY2hpbmcgYWRhbWFudC4NCg0KV2VsbCBh
dCB0aGlzIHBvaW50IGFyZ3VpbmcgZm9yIG1vcmUgVVMgbWVldGluZ3MgYmVjYXVzZSBJIGhhZCBu
byB0cm91YmxlIG9idGFpbmluZyBhIHZpc2EgYW5kIGVudGVyaW5nIHRoZSBVUyBpcyB0aGUgZXF1
aXZhbGVudCBvZiBzdGF0aW5nIHRoYXQgSeKAmW0gYSB3aGl0ZSBndXkgYW5kIEnigJltIG5vdCBm
ZWVsaW5nIGFueSByYWNpc20gb3Igc2V4aXNtLg0KDQpNb3JlIHRvIHRoZSBwb2ludCwgcHJldHR5
IG11Y2ggYWxsIFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0ZXIgdGhhbiBwcmV0dHkgbXVjaCBhbnkg
RXVyb3BlYW4gbGV0IGFsb25lIEFzaWFuIHZlbnVlcywgd2VpcmRseSBzaGFwZWQgcm9vbXMgbm90
d2l0aHN0YW5kaW5nLiBMb25kb24gYW5kIFBhcmlzIGNvbWUgY2xvc2UuIEJlcmxpbiBhbmQgUHJh
Z3VlIGRvbuKAmXQuIFRoaXMgaXMgaW4gdGVybXMgb2YgbmVhcmJ5IGF2YWlsYWJpbGl0eSBvZiBm
b29kIChub3RpY2UgdGhlIGxhY2sgb2YgYSDigJxPTUcgd2hlcmUgY2FuIEkgZ2V0IGEgZ3JhYi1h
bmQtZ28gc2FuZHdpY2jigJ0gdGhyZWFkIGluIDk4YXR0ZW5kZWVzKSBhbmQgaW4gdGVybXMgb2Yg
dGhlIGF2YWlsYWJpbGl0eSBvZiBuZWFyYnkgbG93LWNvc3QgaG90ZWxzLiBBbmQgeWVzLCB0aGUg
ZmFjdCB0aGF0IGV2ZXJ5Ym9keSBzcGVha3MgRW5nbGlzaCBhbHNvIGhlbHBzLiBBbmQgZGVzcGl0
ZSB3aGF0IHBlb3BsZSB0aGluayBhYm91dCBjcmltZSwgbm8gSUVURi1lciBldmVyIGdvdCBzaG90
IGluIHRoZSBVUyBkdXJpbmcgSUVURiB3ZWVrLCBidXQgZXZlcnkgdGltZSB3ZSBtZWV0IGluIEV1
cm9wZSBzb21lIG9mIHVzIHdpbGwgZ2V0IHRoZWlyIHBvY2tldHMgcGlja2VkLg0KDQpGb3IgbWUs
IFVTIG1lZXRpbmdzIChDYW5hZGHigJlzIE9LIHRvbykgYXJlIG1vcmUgY29udmVuaWVudCBkZXNw
aXRlIHRoZSBsb25nLCB0b3J0dW91cyBmbGlnaHQuIFBlb3BsZSBoYXZlIGJlZW4gZ3J1bWJsaW5n
IGFib3V0IFVTIGVudHJ5IHByb2NlZHVyZSBmb3IgeWVhcnMgYW5kIHdpdGggZ29vZCByZWFzb24u
IEJ1dCBvdmVyYWxsIFVTIG1lZXRpbmdzIGFyZSBzaW1wbHkgbW9yZSBjb252ZW5pZW50LiBZTU1W
DQoNCllvYXYNCg0K

--_000_AM4PR0401MB2241D2424F3027B4DB2496A7BD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <8A253F0D37E85D458D649FAB6AEF259C@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSSByZWNvbW1lbmQg
RWd5cHQgYmVjYXVzZSBpdCBpcyBhdCB0aGUgY2VudGVyLCB3aWxsIG5vdCBiZSBzbyBsb25nIGZv
ciBhbnlvbmUsIGFsc28sIHdlYXRoZXIgaXMgYW4gaW1wb3J0YW50IGZhY3RvciwgYW5kIGZvciB0
aG9zZSB3aG8gd291bGQgbGlrZSB0byB2aXNpdCBoaXN0b3JpY2FsIHBsYWNlcyBzaG91bGQgZm9j
dXMgbW9yZSBhYm91dCBob3cgdG8gZ28gYW5kIHdoYXQgdG8gd2VhciwgdGhlcmUgYXJlIG1vZGVy
biBjaXRpZXMgYW5kIG9sZA0KIGNpdGllcywgdGhlcmUgaXMgYSBiaWcgZGlmZmVyZW5jZSwgbWFu
eSB0b3VyaXN0cyBoZXJlIHdpdGggYWxsIGRpZmZlcmVudCBzdHlsZXMsIGFuZCBvZiBjb3Vyc2Ug
bm8gb25lIHdpbGwgZGlzcmVzcGVjdCBwb2VwbGUgaGVyZSBzbyBoZS9zaGUgd2lsbCBnZXQgaW4g
dHJvdWJsZS48YnI+DQo8YnI+DQpCdXQgcmVnYXJkaW5nIENhbmFkYSwgZnVsbCByZXNwZWN0IHRv
IHRob3NlIHBlb3BsZSBhbmQgdGhleSB3aWxsIGJlIG1vcmUgdGhhbiB3ZWxjb21lZCBoZXJlLjxi
cj4NCjxicj4NClJlZ2FyZHMsDQo8ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0
OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+
DQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBh
bmQgSUVURiAxMDI8YnI+DQpGcm9tOiBZb2F2IE5pciA8eW5pci5pZXRmQGdtYWlsLmNvbT48YnI+
DQpUbzogU3RlcGhlbiBGYXJyZWxsIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPjxicj4NCkND
OiBJQU9DIExpc3QgPGlhb2NAaWV0Zi5vcmc+LElFVEYgPGlldGZAaWV0Zi5vcmc+PGJyPg0KPGJy
Pg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5
bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmct
bGVmdDoxZXgiPg0KT24gMTMgQXByIDIwMTcsIGF0IDM6MDAsIFN0ZXBoZW4gRmFycmVsbCA8c3Rl
cGhlbi5mYXJyZWxsQGNzLnRjZC5pZT53cm90ZTo8YnI+DQo8YnI+DQo8YnI+DQomZ3Q7IEkgZG8g
bm90IHJlY2FsbCB0aGUgb3Bwb3NpdGUgb24gdGhlIGxpc3QsIGkuZS4gc29tZW9uZSBhZGFtYW50
bHk8YnI+DQomZ3Q7IGFyZ3VpbmcgdGhhdCB3ZSBvdWdodCBjb250aW51ZSB0byBtZWV0IGluIHRo
ZSBVUy4gVGhlcmUgd2VyZSBzb21lPGJyPg0KJmd0OyBtYWlscyB0aGF0IEknZCBzYXkgbWF5YmUg
d2Vha2x5IGFyZ3VlZCBmb3IgY29udGludWVkIFVTIG1lZXRpbmdzPGJyPg0KJmd0OyBpbiB0aGUg
cmVsZXZhbnQgdGltZWZyYW1lLiBCdXQgbm90aGluZyBhcHByb2FjaGluZyBhZGFtYW50Ljxicj4N
Cjxicj4NCldlbGwgYXQgdGhpcyBwb2ludCBhcmd1aW5nIGZvciBtb3JlIFVTIG1lZXRpbmdzIGJl
Y2F1c2UgSSBoYWQgbm8gdHJvdWJsZSBvYnRhaW5pbmcgYSB2aXNhIGFuZCBlbnRlcmluZyB0aGUg
VVMgaXMgdGhlIGVxdWl2YWxlbnQgb2Ygc3RhdGluZyB0aGF0IEnigJltIGEgd2hpdGUgZ3V5IGFu
ZCBJ4oCZbSBub3QgZmVlbGluZyBhbnkgcmFjaXNtIG9yIHNleGlzbS48YnI+DQo8YnI+DQpNb3Jl
IHRvIHRoZSBwb2ludCwgcHJldHR5IG11Y2ggYWxsIFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0ZXIg
dGhhbiBwcmV0dHkgbXVjaCBhbnkgRXVyb3BlYW4gbGV0IGFsb25lIEFzaWFuIHZlbnVlcywgd2Vp
cmRseSBzaGFwZWQgcm9vbXMgbm90d2l0aHN0YW5kaW5nLiBMb25kb24gYW5kIFBhcmlzIGNvbWUg
Y2xvc2UuIEJlcmxpbiBhbmQgUHJhZ3VlIGRvbuKAmXQuIFRoaXMgaXMgaW4gdGVybXMgb2YgbmVh
cmJ5IGF2YWlsYWJpbGl0eSBvZiBmb29kIChub3RpY2UNCiB0aGUgbGFjayBvZiBhIOKAnE9NRyB3
aGVyZSBjYW4gSSBnZXQgYSBncmFiLWFuZC1nbyBzYW5kd2ljaOKAnSB0aHJlYWQgaW4gOThhdHRl
bmRlZXMpIGFuZCBpbiB0ZXJtcyBvZiB0aGUgYXZhaWxhYmlsaXR5IG9mIG5lYXJieSBsb3ctY29z
dCBob3RlbHMuIEFuZCB5ZXMsIHRoZSBmYWN0IHRoYXQgZXZlcnlib2R5IHNwZWFrcyBFbmdsaXNo
IGFsc28gaGVscHMuIEFuZCBkZXNwaXRlIHdoYXQgcGVvcGxlIHRoaW5rIGFib3V0IGNyaW1lLCBu
byBJRVRGLWVyDQogZXZlciBnb3Qgc2hvdCBpbiB0aGUgVVMgZHVyaW5nIElFVEYgd2VlaywgYnV0
IGV2ZXJ5IHRpbWUgd2UgbWVldCBpbiBFdXJvcGUgc29tZSBvZiB1cyB3aWxsIGdldCB0aGVpciBw
b2NrZXRzIHBpY2tlZC48YnI+DQo8YnI+DQpGb3IgbWUsIFVTIG1lZXRpbmdzIChDYW5hZGHigJlz
IE9LIHRvbykgYXJlIG1vcmUgY29udmVuaWVudCBkZXNwaXRlIHRoZSBsb25nLCB0b3J0dW91cyBm
bGlnaHQuIFBlb3BsZSBoYXZlIGJlZW4gZ3J1bWJsaW5nIGFib3V0IFVTIGVudHJ5IHByb2NlZHVy
ZSBmb3IgeWVhcnMgYW5kIHdpdGggZ29vZCByZWFzb24uIEJ1dCBvdmVyYWxsIFVTIG1lZXRpbmdz
IGFyZSBzaW1wbHkgbW9yZSBjb252ZW5pZW50LiBZTU1WPGJyPg0KPGJyPg0KWW9hdjxicj4NCjxi
cj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM4PR0401MB2241D2424F3027B4DB2496A7BD020AM4PR0401MB2241_--


From nobody Wed Apr 12 22:58:57 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2331128B8F for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:58: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, 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 zRlc_FyHrx3x for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 22:58:49 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 1C93B127201 for <ietf@ietf.org>; Wed, 12 Apr 2017 22:58:49 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id c198so23964732pfc.1 for <ietf@ietf.org>; Wed, 12 Apr 2017 22:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/7JfEB/8LJpxuvPsnsjsvSGlvQc2VwYZ+rh0S2oL+iQ=; b=WKunuCM/Sryf8ax42gdZ054p5mKmwInYcGaMOnxOOaDt24gnp4pWYIKB15uk3B/vZh 85sc7XII9mYnhTFo6UcZ7sp9QO2Kjta9hbJ54Ze9VUuiSiI774L23LG/4oYDAv3qGScg 5n8RE4PH+p5zroKvx4PfrTBq3UoMMA2O0orZlfCdPdvtVnkKDIBK0klEe1WJHK0rOHvR OkJ8NkKgRdlTjDZP7ANM+6v9g4hJmneMzGffkNQAUFYAK87SBxbREF55xX84CF55K6bY N3Zl01b2svajnQbO/5wmPhQXdbdilPB3Cdj0V3awtFQq+ZXP4IpbgVMZEmO2hVaVsRK+ B+kg==
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=/7JfEB/8LJpxuvPsnsjsvSGlvQc2VwYZ+rh0S2oL+iQ=; b=cY3NhxVrn37XAg9vvhdSgDfbIYMCGAxx6kXrLC0TE/qVxeQk1c3iQZCIavCksrP+7V nKG6Nxf32Lis4SlXW1RvkHoGO8ePgdmP0FLXyfFWrQuVK7EOHPwyrRZV1tqxhKjeeRXI o9vHUXRQhRJudtQEbBo2DtsHntUh+qSC1jd7BLY814OiEjT3gXrjFtn1O6ZYyDqX9F/Y 05H+0apSaT/CqF+uDcCPKd4UkUxUUh96+6yr4M0wlone7rQ7kh/OJhKW9oxjmOpyQSD7 UyWrKvc2FwNCeZEhIK0SeeG70efLk5EMM9MKwAXPli1Ws+Ut4/3mXbPiYs/TO8nM611d AXzw==
X-Gm-Message-State: AN3rC/5rAT5bT7S8+yMK4j5C7CIdSyD/fbJ/DyiLJrSvypbPoeq7/ZdG 0d59orywkvPs9yOx268CQUGhyLIw1Q==
X-Received: by 10.98.105.134 with SMTP id e128mr1421779pfc.19.1492061644171; Wed, 12 Apr 2017 22:34:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.162.41 with HTTP; Wed, 12 Apr 2017 22:33:23 -0700 (PDT)
In-Reply-To: <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 13 Apr 2017 01:33:23 -0400
Message-ID: <CAHbuEH7br-buD57BKe-rciaf16m9sfv-BuveZo09pJPytx9CCg@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Martin Thomson <martin.thomson@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1hSVlcNsCBcs1XHmXOC7Ei2VodI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:58:55 -0000

Hello,

On Mon, Apr 10, 2017 at 11:54 PM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:
> Hi Martin,
>
> We went through your comments one more time to make sure any
> technical/substantive comments are addressed.  Please see the
> discussion inline.
>
>
> On Mon, Apr 10, 2017 at 5:05 PM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
>> I most certainly reviewed 09. I haven't reviewed the diff. I doubt that it
>> would change my opinion on the macro - level problems.
>
> My mistake, I thought the acronym you corrected was in version 9.
>
>>
>> On 8 Apr. 2017 3:34 am, "Kathleen Moriarty"
>> <kathleen.moriarty.ietf@gmail.com> wrote:
>>
>> Hello Martin,
>>
>> Thanks for your review.  It seems that you have read version 8 or
>> earlier and not the current version, 9, from some of your suggestions
>> that have been corrected already.  Your review also reads to me that
>> additional context setting may help, but please note that some context
>> setting was improved in version 9.  We re-arranged some of the
>> sections per IESG review recommendations in the latest version as
>> well.
>>
>> Perhaps you have additional language suggestions for context setting?

We have updated version 11 with new context setting text that
hopefully addresses your major concerns in tone setting for the rest
of the document.

>>
>> The abstract states:
>>
>>    Increased use of encryption impacts operations for security and
>>    network management causing a shift in how these functions are
>>    performed.  In some cases, new methods to both monitor and protect
>>    data will evolve.  In other cases, the ability to monitor and
>>    troubleshoot could be eliminated.  This draft includes a collection
>>    of current security and network management functions that may be
>>    impacted by the shift to increased use of encryption.  This draft
>>    does not attempt to solve these problems, but rather document the
>>    current state to assist in the development of alternate options to
>>    achieve the intended purpose of the documented practices.
>>
>> which is repeated again in the introduction, but slightly reworded.
>> The introduction also includes statements on the existing publications
>> related to encryption and I read them as not having any bias, but
>> rather supporting the existing documents that also had consensus.
>>
>> A couple of comments and one question inline.
>>
>> On Thu, Apr 6, 2017 at 11:24 PM, Martin Thomson
>> <martin.thomson@gmail.com> wrote:
>>> Draft: draft-mm-wg-effect-encrypt-09
>>> Date: 2017-04-07
>>>
>>> Overall
>>>
>>> This document is unfocused and unclear in its intent.  It is filled with
>>> unsubstantiated claims, misleading statements, bias, and implied
>>> recommendations
>>> for bad practices.  I would oppose its publication in the current form.
>>> Furthermore, I don't believe that small scale or editorial changes would
>>> be
>>> sufficient to correct these problems.
>>>
>>>
>>> Aside from weakening its utility and/or arguments, the lack of focus will
>>> allow
>>> this document to be abused in various ways.  For instance, it might imply
>>> IETF
>>> endorsement of the practices described in the document.  Given that the
>>> IETF has
>>> published positions that in some cases reject these practices, this
>>> document
>>> needs to be very precise with its claims.  In its current form, it is not
>>> nearly
>>> careful enough.
>
> This paragraph is all speculation about an unfortunate future.
> We could speculate that the operator, security and app communities
> come together to work out solutions after reading this doc,
> which is part of our intent.
>
>>>
>>> If this document is going to be published as an RFC, then it needs to be
>>> very
>>> clear about its intent and its position - or lack thereof - toward these
>>> practices.  It might be possible to say that these practices were employed
>>> in
>>> networks in the past and that encryption is reducing the viability of
>>> those
>>> practices.  A value-neutral statement like that might be acceptable as
>>> long as
>>> it were framed carefully.
>
> The document conveys that message everywhere. The words contributed were
> changed in many places to remove any implication that the current practices
> are "requirements" or even "needs".
>
> The abstract and introduction contain value neutral statements like
> what you are suggesting already.  We actually say the practices may be
> eliminated, going further than your request as that may be the case.
>
> The only change I could see in the abstract would be the following:

The abstract has been updated further to ensure the context is set and
shows how the document further supports the goals of RFC7258.
Hopefully this is a helpful update for you.

>
>    Increased use of encryption impacts operations for security and
>    network management causing a shift in how these functions are
>    performed.  In some cases, new methods to both monitor and protect
>    data will evolve.  In other cases, the ability to monitor and
>    troubleshoot could be eliminated.  This draft includes a collection
>    of current security and network management functions that may be
>    impacted by the shift to increased use of encryption and encryption
> that is designed prevent interception.  This draft
>    does not attempt to solve these problems, but rather document the
>    current state to assist in the development of alternate options to
>    achieve the intended purpose of the documented practices when possible.
>
> Do you have additional suggestions?  Or is the phrasing read
> differently than we intended by stating functions may be eliminated?
> We thought that was very clear to your points.
>
>>>
>>> What is problematic is the implicit argument that is presented.  This
>>> document
>>> could easily be construed as the IETF legitimizing these practices.  This
>>> includes things on which the IETF has published statements (see for
>>> example RFC
>>> 2804).
>>
>> See the abstract and introduction and summary.
>>
>>>
>>> This steps firmly into to sticky mess that is the politics of encryption
>>> policy.
>>> If the IETF is going to make a political statement with this document,
>>> then that
>>> statement needs to be a lot better than this.
>
> The intent of this document is to help operators as these changes
> continue.  It is to make sure we are not ignoring the impact of the
> changes the IETF has with our decision (which are supported in this
> document).  This document is intended to assist operators.  By
> explaining the functions being performed, some have already been
> provided alternate methods to achieve their goals.  We have also
> received quite a bit of positive feedback from operators - that this
> document helped them come back to the discussion and to approach a
> world with more encryption or sessions that can't be intercepted (TLS
> 1.3, TCPinc, QUIC, etc.).
>
>>>
>>> Furthermore, any statement needs to be consistent with previous
>>> statements,
>>> where in this case that primarily means RFC 7258.  Right now it reads as
>>> an
>>> attempt to dilute RFC 7258.
>>
>> Not at all.
>
> It does not read that way to many people who strongly support RFC
> 7258, including Stephen who was our sponsoring AD (and was for 7258).
> Can you give specific sections where it sounds like we are weakening
> RFC 7258 so we can change that specific wording?
>
>>
>>>
>>> If this document were more clearly formulated as an even-handed treatment
>>> of
>>> what happens today - without judgment - then it could be useful.  Here the
>>> model
>>> of RFC 7754 is a good one.  It describes the different facets of a use
>>> case,
>>> then the different practices that might be employed to achieve that goal.
>>> For
>>> each practice the pros, cons, and technical limitations are covered with
>>> an eye
>>> to all involved parties.
>>>
>
> Version 8 to 9 had some edits to remove statements with used terms
> like 'need'.  We may have missed a couple, we'll check the ones you
> pointed out.  There are also numerous statements that are explicitly
> in support of RFC7258.  These are in the abstract, introduction,
> summary and sprinkled throughout the document.
>
> Apparently, RFC 7754 goes further than our scope. We are not describing:
> "... the different practices that might be employed to achieve that goal."
>
>>>
>>> The Real Purpose of this Document
>>>
>>> I think that this is the real question that this document wants to ask is:
>>>
>>>    In a world where we are forced to defend against pervasive monitoring
>>> by
>>>    motivated and malicious actors, can we find a role for less pervasive
>>>    monitoring by well-intentioned entities?
>
> The document aims to help operators by giving them a chance to discuss
> the impact.  It opens the
> door to conversation so they can find new ways to achieve the same
> goals (better performance for customers for instance or monitoring
> services that have been requested - web content, DLP), which may mean
> endpoint solutions are needed or filtering limited to hostnames for
> now until other mechanisms are developed (likely at the application
> layer).
>
> For enterprises, application and host level solutions are
> fine as many organizations have employees sign away their rights to
> privacy.  I would never check FaceBook from work for instance or
> access any site of a personal nature.  This is why we broke out the
> sections by the type of network or SP, their options are different
> with and without encryption.
>
> QUESTION: Would it help to add some text like the first paragraph into
> the introduction?  - This document aims to...
>
>>>
>>> There is an interesting discussion to be had here, but I'm convinced after
>>> my
>>> review that this document is the wrong vehicle for that discussion.
>
> RFCs are the vehicles the IETF has found most useful in talking to the world.
>
>>>  I'm
>>> also
>>> inclined to suggest that this is the wrong question to ask in the first
>>> place.
>
> We can't ignore the problems resulting from the changes, we the IETF
> make, to improve privacy and security.  While we agree it is a positive
> thing to improve these functions, we (the IETF) should also help with
> the wake we
> leave in our path.  Otherwise, we can't expect people to play along
> with the protocol specifications the IETF publishes.
>
> It's much more than an "interesting discussion" to many operators.
> Some are required by law to use these practices to protect privacy.
>
> There are many questions to ask, some of which have already been
> answered. For example, RFC 7258 asked 'How can we deal with
> pervasive monitoring' and answered it through the same IETF
> consensus process this document has already gone through.
>
>>>
>>> To the extent that we have the tools necessary to protect against
>>> pervasive
>>> monitoring, we have to accept that more-legitimate uses of monitoring are
>>> collateral.  Mostly, that's just a function of the limitations of the
>>> imperfect
>>> tools we have.
>>>
>>> The value in this document is in the rather comprehensive collection of
>>> use
>>> cases.  Sure, some we might not attribute much weight to, like
>>> wiretapping.
>>> Others are frankly frightening and not just in the Orwellian sense.
>>>
>>> The problems that are implied by the current practices of network
>>> operators is a
>>> large vein of unexplored work for the community.  Spending effort on
>>> finding
>>> better solutions to legitimate problems is worthwhile.
>
> Right, so we started by documenting them *before* the collateral damage appears.

We've added some additional statements in line with the goals of
RFC7258 balancing network management and PM mitigations.

>
>>>
>>> In other words, the right question might be:
>>>
>>>    For each of these practices that we see today, are the use cases that
>>>    motivate them legitimate and how might be implement alternative
>>> techniques
>>>    that properly respect privacy and security?
>>>
>
> Yes, this is the point of the document and it's stated in several places.
>
>>>
>>> Two- and Three- Party Interactions
>>>
>>> A great many sections of the document are unclear about the relationships
>>> between different actors.  It seems like many of the activities describe,
>>> which
>>> are presented here as being beneficial, are performed by a third party
>>> without
>>> the consent or involvement of the two communicating peers.  After all,
>>> those are
>>> the cases where encryption most often interferes.
>>>
>
> As the draft says, some of the methods will be eliminated.

This wording has been updated to avoid unintended interpretations of that text.

>
>>> The assertion that some benefit is accrued to communicating peers as a
>>> result of
>>> these actions is the constant subject of the text.  I observe that in most
>>> of
>>> the cases listed in this document, the benefit is accrued primarily to the
>>> third
>>> party.
>
> Operators by their nature have different privacy concerns than their end
> users. Operators by their nature want to accrue benefits. This document
> doesn't change the balance; instead, it tells them how to deal with privacy
> that has already been applied.  While we agree with your statement and think
> it's important to build privacy and privacy options into IETF protocols,
> operators often don't care, despite the many RFCs we have published
> telling them that they should care. We still need to engage them so we can
> have this discussion.
>
> The "third party" is likely the only one receiving a trouble call,
> and there is benefit for all parties when the trouble is cleared.
>
>>>
>>> Clarity around the arguments that the document makes with respect to
>>> benefits to
>>> each of the involved parties is sorely lacking.
>>>
>>> In addition to this, where benefits truly do accrue to communicating
>>> peers,
>>> technical options that don't rely on privacy-invasive techniques are
>>> routinely
>>> dismissed in an offhand fashion.  In this way, any moral imprimatur
>>> attributed
>>> to the use case is used to justify the privacy-invasive method.
>>>
>
> Without specific comments, the above are all subjective statements and
> we have responded to them.

We have also made an effort to update text to clear up tone questions
where specific text has been called into question.

>
>>>
>>> Document Structure
>>>
>>> This document is very hard to read (and review).  Probably my biggest
>>> complaint
>>> is that the sections are haphazardly organized.  They contain a mixture of
>>> use
>>> cases (what does SP X want to do) and techniques (how do they do these
>>> things).
>>> Material is duplicated between sections.  Sections cover 10 different use
>>> cases
>>> while talking about techniques, then other sections talk about different
>>> techniques whiles talking about a scenario.  This leads to a lot of
>>> repetition.
>>>
>>> There are three axes that this document contemplates:
>>>
>>>  - the techniques that are currently used in networks
>>>  - the use cases that motivate these techniques
>>>  - the deployment scenarios in which these use cases manifest
>>>
>>> It would appear that the document attemps to start from the deployment
>>> scenarios.  However, this causes use cases and techniques to be mixed.
>>> Judicious use of cross-referencing might have made this arrangement
>>> tractable,
>>> but there are virtually no cross references.
>>>
>
> The above is stylistic in nature.  We've already made changes to the
> format to address specific comments in IESG review. A complete
> re-write is not appropriate at this point in the draft lifecycle.
> That's not the point of IESG review.
>
>>>
>>> Section 1
>>>
>>> I find the introduction of this document difficult to parse.  I think that
>>> what
>>> it wants to say is pretty straightforward, but it manages this in quite an
>>> obtuse way.  Here's what I think that it is trying to say:
>>>
>>> 1. The IETF (and the larger community) has reacted to revelations of
>>> pervasive
>>>    monitoring by increasing the use of encryption.
>>> 2. That has been somewhat successful.
>>> 3. More encryption has an impact on some practices that network operators
>>> have
>>>    become accustomed to employing.
>>>
>>> Expressed in this way, you can see how you could make a value-neutral
>>> statement.
>>>
>>> On the first, you can definitely make an argument based on the documents
>>> that
>>> the IETF have published.  However, it is a mistake here in assuming that
>>> the
>>> IETF - or the revelations of global-scale surveillance - is directly
>>> responsible
>>> for the uptick in adoption of cryptographic protection for Internet
>>> traffic.
>
> The abstract is value neutral right now.

The abstract has been updated, please see version 11.

>
> The increase or changes are not just about PM.  We are making
> TLS 1.3 so that it cannot be intercepted (I agree with this move of
> course as we should make our protocols strong and adhere to
> established IETF principles)?  Or the efforts of TCPInc and
> QUIC?  We do directly affect the use of encryption and the types of
> encryption that are deployed.  We work with the vendor communities in
> publishing deprecation drafts as well.  All of these efforts got
> additional energy from the PM work and that's a good thing.  Events
> trigger increases in security and it's fine to acknowledge that.  The
> introduction states:
>
>    In response to pervasive monitoring revelations and the IETF
>    consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
>    are underway to increase encryption of Internet traffic.  Session
>    encryption helps to prevent both passive and active attacks on
>    transport protocols;
>
> We could change it to say:
>
>    In response to pervasive monitoring revelations and the IETF
>    consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
>    are underway to improve and increase encryption of Internet traffic.  Session
>    encryption helps to prevent both passive and active attacks on
>    transport protocols;
>
> The second sentence mentions passive and active attacks here as that
> hits on the prevention of active attacks - improving session
> encryption protocols helps with this.

update made.
>
>>> This is something that the community as a whole has been working towards
>>> for
>>> many years; these trends predate the actions this draft focuses on.  This
>>> is
>>> particularly true for the hosted provider cases in Section 3, where
>>> business
>>> motivations for protection are far stronger than any concerns over
>>> government
>>> surveillance.  Yeah, that's a subjective view, but I'm just reviewing, I
>>> don't
>>> have to write a statement that will be labelled as having IETF consensus.
>
> Section 3 already makes this point very clear (full text for the intro
> to that section):
>
> 3.  Encryption in Hosting SP Environments
>
>    Hosted environments have had varied requirements in the past for
>    encryption, with many businesses choosing to use these services
>    primarily for data and applications that are not business or privacy
>    sensitive.  A shift prior to the revelations on surveillance/passive
>    monitoring began where businesses were asking for hosted environments
>    to provide higher levels of security so that additional applications
>    and service could be hosted externally.  Businesses understanding the
>    threats of monitoring in hosted environments only increased that
>    pressure to provide more secure access and session encryption to
>    protect the management of hosted environments as well as for the data
>    and applications.
>
>>>
>>> The immediate focus on opportunistic security is highly misleading,
>>> especially
>>> in the web case.  The amount of opportunistically secured web traffic is
>>> miniscule by global standards.  Since Firefox is the only browser to
>>> support OS
>>> for the web, so adjust the following by market share:
>>> <https://mzl.la/2oc46ch>.
>
> You'll need to cite text that is leading you to this conclusion as I
> don't read it as being specific to OS, rather that OS is explained so
> operators understand it in the mix of encryption options.
>
>>>
>>> I understand that mail is more often opportunistically secured, and you
>>> will
>>> hear the virtues of OS sung from the rooftops, but all evidence suggests
>>> that
>>> this is just a transitory state.  Instant messaging is closer to the web
>>> case,
>>> with the trend toward strong protections that include authentication.  Of
>>> course, I don't believe that mail or instant messaging represent any
>>> significant
>>> traffic volume, so you need to be very careful about the nature of the
>>> claims
>>> that are being made.  It has to be that the volume of mail has to be a
>>> rounding
>>> error when it comes to capacity planning for networks.
>>>
>>> On the second point, when making claims about prevalence of encryption, I
>>> would
>>> advise caution when citing statistics.  Here's the graph for the Mozilla
>>> figures
>>> that I think are being cited <https://mzl.la/2obZjrb>. Here's a different
>>> graph
>>> with a different number <https://mzl.la/2oc263J>.  This highlights the
>>> point
>>> that statistics need to be carefully cited, because bare claims are
>>> difficult to
>>> assess.  Methodology matters when it comes to these sorts of claims - are
>>> we
>>> talking proportions of packets, requests, flows, or something else?
>>> Furthermore, the citations in the document are made more difficult to
>>> assess by
>>> being measured at very different times (where the two I cite here were
>>> made at
>>> roughly the same point in time).
>>
>> For the Mozilla statistics, Richard Barnes had reviewed the text after
>> providing the statistic as he wanted to make sure it was stated
>> clearly raising the same concerns you do about statistics.  Do you
>> have further text suggestions to clarify this statistic?
>>
>
>>
>>>
>>> The statistics do support the notion that there is a significant amount of
>>> encryption in use, but it would appear that the claim is that the amount
>>> of
>>> encryption is *increasing*.  This is not an extraordinary claim, but no
>>> evidence
>>> is offered in support of the claim.  It isn't a certain thing either.
>>> From the
>>> statistics that I have access to, there was a definite uptick in October
>>> of
>>> 2015, but the rate appears to be stable since then.
>>>
>>> It appears that the remainder of the document is intended to address the
>>> third
>>> of my points in some detail.  That's a good structure in theory, but see
>>> above.
>>>
>>> I don't think that the "service provider" taxonomy works for this
>>> document.
>>> Based solely on the structure of the document, the only service provider
>>> that
>>> this document concerns itself with is the one who forwards the packets.
>>> That
>>> application service providers are involved as one of the endpoints is
>>> relevant
>>> in some cases, but not all.  For that reason, I prefer "network operator"
>>> and to
>>> use specific terms like "mail host" or "web server" as appropriate to the
>>> context.
>>>
>
> Those are subjective comments, so we'll put those aside.
>
>>>
>>> Section 2 (top section)
>>>
>>> I like that the attacks on SMTP by network operators is highlighted here.
>
> We tried to have balance and had other attacks by operators in
> previous versions, but only articles that are not stable references
> for them and were asked to remove them in AD review.
>
>>>
>>> There's an implicit argument here that runs counter to established IETF
>>> consensus.
>>>
>>>    Some methods used by service providers are impacted by the use of
>>> encryption
>>>    where middle boxes were in use to perform functions that range from
>>> load
>>>    balancing techniques to monitoring for attacks or enabling "lawful
>>>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>>>
>>> This fails to remain neutral.
>
> The functions are impacted, so how would you suggest we word this
> text?  It doesn't endorse the functions, just says they are impacted.
> We are open to suggested text.  Similar to how we describe 'attacks'
> by operators to break encryption or use RSA private keys.  We do have
> text in both directions on this and your review is complimentary of
> the ones that fit your dialog, but are also not value neutral.  Mind
> you, I am constantly reviewing RFCs and making sure TLS best practices
> are considered and questioning the use of deprecated crypto or not-yet
> but should be deprecated crypto.

I read the text in the draft again and changed it as follows:

      Some methods, used by service providers are impacted by the
      use of encryption where middle boxes were in use to perform functions
      that range from load balancing techniques to monitoring for attacks or
      enabling "lawful intercept", such that described in ETSI101331
in the US. Only methods keeping with the goal of
      balancing network management and PM mitigation in
      RFC7258 should be considered in solution work resulting
      from this document.
>
>>> This implicitly makes a value-judgment
>>> about
>>> relative morality/acceptability/value of certain practices.
>
> We have statements in both directions in the document as you point out
> above with one of them.
>
>>>  What is
>>> particularly insidious about this particular form is that it invites
>>> interpretation that is subjectively coloured.  For instance, as a non-EU
>>> and
>>> non-US citizen, I might consider the use of the particular lawful
>>> intercept
>>> techniques offensive; thus I might interpret this as a spectrum between
>>> inoffensive to offensive.  An employee of the US government might view
>>> this
>>> somewhat differently and interpret this as a scale between low-value to
>>> high-value.  I'm guessing here, but this is really just to highlight my
>>> point
>>> about care.
>>>
>>> A more serious concern is this statement:
>>>
>>>    The loss of access to these fields may prompt undesirable security
>>> practices
>>>    in order to gain access to the fields in unencrypted data flows.
>>>
>
> But this is true and we've seen operators do things like prevent
> STARTTLS.  This isn't a good thing and we need to ack that this has
> happened.  We need to help operators figure out how they help users in
> new ways and understand that some of the functions they perform
> currently (TLS 1.2) won't work in the future.
>
> This text got re-worded during AD review, I believe.  The intent is to
> say that this is not good - the practices are called out as
> undesirable.  How would you suggest it be re-phrased and we can check
> back with Stephen to see if he agrees.
>

We changed the text slightly in a way that should help with your concern:

      The loss of access to these fields, has in some cases,
      prompted undesirable security practices in order to gain access to the
      fields in unencrypted data flows.

>>> I've read this argument before (see
>>> https://queue.acm.org/detail.cfm?id=2508864
>>> for the long form), and it might even have an element of truth to it.
>>> However,
>>> it's not a statement that I personally attribute any real credibility to,
>>> and
>>> nor do I think that it needs to be credited with any amount of
>>> seriousness.  I
>>> certainly disagree with the IETF making any such statement.  It says that
>>> we are
>>> collectively willing to bow in response to (anticipated) threats of
>>> violence.
>
> Prior to AD review, there was a reference in the text to the practices
> being bad and stating that regulators and the media helped to correct
> this behavior.  The problem here may be the evolution of the
> text and lack of reference now since we couldn't find a stable
> reference.  Do you have a wording suggestion?
>

<snip> questions and text addressed with Mirja's assistance.

>
>>> Editorial:
>>> * "pop" is a term of art that needs explanation.

> Thanks for the nit corrections.
>
>>>
>>> Section 2.2
>>>
>>> I think that this sums the situation up reasonably well.  It fails the
>>> value-neutral test in a few ways though.  As I understand the situation,
>>> surveying operates at many levels.  For accurate planning, models of
>>> endpoint
>>> behaviour are used to determine things like whether loss or congestion is
>>> affecting throughput.  Really good models require knowledge of what users
>>> are
>>> attempting to do and the applications they are using (as mentioned, things
>>> like
>>> browser version matter in these models).  For instance, it isn't enough to
>>> understand that the user is trying to receive 720p video, you also have to
>>> know
>>> that a 4k stream for the same content is available.
>
> Sure, that's why we broke the draft down by operator type.  Some
> functions are shifting and the responsibilities for operators will
> shift with these changes.
>
>>>
>>> The degree to which these models are privacy-invasive is not even
>>> acknowledged.
>
> Suggest text please.  The abstract and intro were meant to set the
> context for the document.  Some of the functions will be eliminated -
> and that's fine, it is what it is, but operators need to adapt and
> deal with the change.  We should help them so we all get to a better
> place with improved privacy for users and increased security.  By not
> helping them, we do not get closer to solving these problems.
>
> Try to consider the operators perspective here. They are used to knowing
> what SI has been exposed by knowing video format
> or browser type that has been in the clear for years.  Understanding
> the practices
> helps make it possible for apps/ops/security/transport to come together to
> reach better solutions.
>
>>>
>>> Nit: Did you realize that "well-intentioned" is a euphemism?  I'd expect
>>> that
>>> subtlety to be lost on many readers though.

removed.

>>>
>>> Section 2.3.1
>>>
>>> I find this sad, even if I can recognize the truth of it:
>>>
>>>    A monitoring system could easily identify a specific browser,
>>>    and by correlating other information, identify a specific user.
>>>
>>> As a browser vendor, we don't consider this to be a feature, it's a bug.
>>>
>>> Section 2.3.2.1
>>>
>>> This is a strange section under which to put caching.  Caching is a use
>>> case
>>> akin to compression.  I don't see it as belonging to the class of things
>>> that
>>> rely on DPI.  You just intermediate the cleartext HTTP in the way that RFC
>>> 7230
>>> recognizes.  Note that RFC 7230 explicitly does not endorse the practice
>>> of
>>> transparent proxying for a range of reasons, not the least of which is the
>>> complete lack of transparency (yep).
>
>
> This was organized per IESG review.
>
>>>
>>> Section 2.3.2.2
>>>
>>> Again, it's strange to see differential treatment under DPI.  I was fairly
>>> sure
>>> that fingerprinting was used here as well.
>>>
>>> Section 2.4
>>>
>>> This section doesn't even attempt to recognize that applications are much
>>> better
>>> now at scaling content to suit the device on which that content is
>>> intended to
>>> be consumed.  It should.
>
> The reason for that is that there has been a useful dialog between application
> designers and network providers over time, beginning with app designers
> saying "what do you mean the network has errors and delay? this works
> fine in my lab...".  The contributors viewed that as well understood
> and far back
> in time, so not necessary to mention.
>
> If you think there should be text to this point, please suggest some.
>
>>>
>>> This section should not represent compression as an unmitigated good.  I'm
>>> told
>>> that significant damage can be done to video streams by "well-intentioned"
>>> compression middleboxes.
>
> Please suggest text.
>
>>>
>>> Yet again I see a call back to the implicit threat of violence in "they
>>> will
>>> adopt undesirable security practices".  Statements in that form have no
>>> place in
>>> IETF RFCs.
>
> This was edited text per review and agreed upon (I think in the AD
> review).  Suggest alternate
> text and we'll go back to the other person.
>
>>>
>>> Section 2.5
>>>
>>> This mentions RFC 7754 then blithely ignores its primary conclusion.
>>> Generally,
>>> The treatment in RFC 7754 of this subject is more even-handed.
>>>
>>> The use of particular examples (betting, gambling, dating) shows cultural
>>> bias.
>
> subjective review again, but 7754 cites examples too.
>
>>>
>>> Jargon warning: "core network", "the mobile network" ("the"?)
>>>
>>> Section 2.5.2
>>>
>>>    This type of granular filtering could occur at the endpoint, however
>>> the
>>>    ability to efficiently provide this as a service without new efficient
>>>    management solutions for end point solutions impacts providers.
>>>
>>> The initial premise here (up to the first comma) is the conclusion of RFC
>>> 7754.
>>> I disagree with the conclusion, and I suspect so does RFC 7754.  In
>>> scenarios
>>> where this matters, endpoints are routinely managed centrally.  The range
>>> of
>>> options for this sort of management are plentiful and diverse.
>
> Sure, but there is an impact and it's okay to ack that and assist with
> these alternate options.  If you have text to suggest, please do so.
>
>>>
>>> Section 2.5.3
>>>
>>> This describes a captive portal, which in the case where the service
>>> provider
>>> has a relationship with their customers, seems like a poor solution.  See
>>> the
>>> CAPPORT working group for ways in which people are actually working on a
>>> solution to this problem.
>>>
>>> Section 2.6
>>>
>>> The capitalization of section headings is inconsistent here (and
>>> throughout).
>>>
>>> Section 2.6.1
>>>
>>> Isn't this a duplicate of Section 2.1?
>>>
>>> Section 2.6.2
>>>
>>> I can't parse this statement:
>>>
>>>    Approved access to a network is a prerequisite to requests for Internet
>>>    traffic - hence network access, including any authentication and
>>>    authorization, is not impacted by encryption.
>>>
>>> And then we get into zero rating, which is a hot-button topic.  No
>>> acknowledgment given to the sensitivities on the subject, or even a
>>> superficial
>>> exploration of the technical options that are available.
>
> Please suggest text.  This was updated in IESG review.
>
>>>
>>> This text references a non-existent Appendix.
>
>
> Fixed. It's section 7 now.
>
>>>
>>> Section 2.6.5
>>>
>>> This paragraph is strange.  It starts by describing what appears to be use
>>> cases
>>> (are those scare quotes?).  It finishes by implying that these are attacks
>>> on
>>> privacy (which they are).
>>>
>>> What is "Non-Customer Proprietary Network Information"?  I hope that this
>>> isn't
>>> an attempt to somehow privilege the information so that it seems less than
>>> privacy-invasive.
>>>
>>> Section 2.7
>>>
>>> This is one of the areas that is most legitimately affected by increased
>>> adoption of encryption.  I have no doubt that having detailed information
>>> about
>>> the application and its use makes the process of troubleshooting easier.
>>>
>>> This is the first mention in the document of network-based optimization.
>>> Was
>>> the section describing that cut from an earlier draft?
>>>
>>> The use of websockets as a primary example is an odd one.  It's just not
>>> that
>>> common.  For reference, we see >20% failure rates on encrypted websockets
>>> and
>>>>50% failures in the clear; no one in their right mind would rely on
>>>> websockets.
>>> If the point is that HTTP is carrying more traffic (see
>>> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
>>> just that
>>> would be more effective.
>
> "in their right mind" . That isn't helpful.  Operators submitted text
> to explain what they are doing and how it's impacted.  How about
> proposing text to help in that vein.
>
>>>
>>> Section 3
>>>
>>> It would help if "hosted environments" was defined before diving in.
>>>
>>> Section 3.1
>>>
>>> The paragraph on DLP is ironically amusing.  Encryption exists to prevent
>>> private information leakage, but the assertion here is that encryption is
>>> hampering DLP attempts.
>>>
>>> It's true that protection of intellectual property is an important
>>> business
>>> goal, but this handling suggests an architecture that I'm fairly sure is
>>> counter
>>> to established wisdom (see "SSL added and removed here :-)":
>>>
>>> https://www.washingtonpost.com/rf/image_404h/2010-2019/WashingtonPost/2013/10/30/Local/Images/GOOGLE-CLOUD-EXPLOITATION1383148810.jpg).
>>> Worse, this casually dismisses a model that is actually more likely to
>>> work.
>>> Malware encrypts too (https://arxiv.org/abs/1607.01639).
>
> The section talks about the end points being the better place for this already.
>
>>>
>>> Section 3.1.1
>>>
>>> Who is the customer here?
>>>
>>> Why does the hosting provider need to monitor access?  They have the
>>> ability to
>>> limit accesses, but this is suggesting that what happens within the
>>> envelope of
>>> what they permit is important for them to know.  I'd be surprised if you
>>> could
>>> show that this is true.  Hosting providers - in my experience - value
>>> their
>>> ongoing business and would not jeapardize it by snooping on their
>>> customers.
>>> It's different if the customer opts in to a security service, but that
>>> demonstrates a cooperative situation, where the rest of this document is
>>> largely
>>> concerned with adversarial uses of encryption.
>
> This is describing the cooperative scenario.  The service is hosted,
> so maybe the definition of hosted would have helped you.
>
>>>
>>> Section 3.1.2
>>>
>>> This is another example where the organization of the document could
>>> be improved.
>>>
>>> Again with the "SSL added and removed here :-)" recommendation.  PCI don't
>>> permit that for good reason.
>
> I don't read the following text in this section as a recommendation or
> endorsement.  Is there a tweak you think that should be made as I'm
> not seeing the problem your describing. This is just describing what
> they do and stating that it will be impacted and then the truth that
> the functions may no longer be possible - not stating that it is good
> or bad, just the fact that it won't be possible.
>
>    The use of tools that
>    perform SSL/TLS decryption are impacted by the increased use of
>    encryption that prevents interception.  Alternate methods to acheive
>    the goals of these functions may be necessary and in some cases, the
>    functions may no longer persist in a pervasively encrypted Internet.
>
>>>
>>> Section 3.2.1
>>>
>>> I don't believe that monitoring of these types of application require
>>> cleartext
>>> access.  There are two parties involved: the provider of the application
>>> and the
>>> user of it.  The provider has most of the power here and can theoretically
>>> design the system to allow whatever level of access they require.  To the
>>> extent
>>> that the user needs protection from the application provider, that is a
>>> matter
>>> of negotiation between them.
>>>
>>> I don't see how the adversarial three-party situation presented in the
>>> rest of
>>> the document applies in this situation.
>
> Sure, there is a shift in how many functions will be performed
> happening and this is documenting that shift.  Much moves to the
> application.  We are helping to document the changes.
>
>>>
>>> Section 3.2.2
>>>
>>> No real mention of the effect of encryption here, or is this just saying
>>> that
>>> there is no issue here?
>>>
>>> I don't see the point of the PGP/Dark Mail paragraph.  I'd be leery of the
>>> IETF
>>> saying things like "PGP may be a front runner" though.
>>>
>
> This was added per EKR in IESG review.
>
>>> Section 3.3
>>>
>>> There's certainly a lot of detail here, but I had a really hard time
>>> extracting
>>> value from this section.  I can't see how data storage is fundamentally
>>> different to the general case of an application provider.
>
> They figured out how to increase encryption and manage their hosted
> environments.  There were adjustments made and they've been
> successful.
>
>>>
>>> Section 4.1.1
>>>
>>> I appreciate the recognition that endpoint-based techniques work.  The
>>> implication that this isn't the obvious solution, much less so.
>
> This isn't a technical comment, but we'll revisit the text to see if a
> wording change can help.
>
>>>
>>> Section 4.1.2
>>>
>>> I'm confused about the purpose of this section.  This seems to be talking
>>> about
>>> the sort of network-based methodologies an application provider might
>>> employ to
>>> ensure that their application is working as intended.  Why would the
>>> application
>>> provider not have access to detailed logging and usage metrics?
>
> The problem cited to us is that logging is sorely lacking.  This needs
> to be pointed out and fixed as it is too much for the operator to deal
> with given the large number of applications running in their
> environments.
>
>>>
>>> As an aside, I skimmed through ietf-ippm-6man-pdm-option, since it is
>>> cited no
>>> fewer than three times in the same paragraph.  It makes some fairly bold
>>> claims
>>> about its effect on privacy that I don't believe will hold up to analysis.
>>>
>>> Section 4.1.3.1
>>>
>>> This section correctly identifies the issue as one of shortcomings in
>>> logging,
>>> not increased use of encryption.
>
> Right, a key point in this document - other methods will have to be
> used and an obvious one is logging.  However, logging needs to improve
> for that to be possible.
>
>>>
>>> I would have stopped there, but the section persists and ultimately
>>> references
>>> RFC 7974, which is widely recognized as a monstrously bad idea (the IESG
>>> note is
>>> fairly clear on this point).
>
> Thanks for catching that.  We can drop this text.
dropped.
>
>>>
>>> Section 4.1.3.2
>>>
>>> "HTTP/2", not "HTTP2".
>
> Fixed.
>
>>>
>>> I don't see how this section belongs in this document.  The 1:1
>>> correlation
>>> between actions and flows in HTTP was a mistake of the 1980s that we've
>>> spent a
>>> lot of time on correcting (sometimes unsuccessfully, see pipelining).
>>>
>>> Section 4.1.3.3
>>>
>>> It's not a "service call" it's just a request.
>>>
>>> Section 4.2
>>>
>>> If the inclusion of a reference to RFC 7457 is to support a claim that TLS
>>> is
>>> attacked, that's sailing far too close to an endorsement of attacks than I
>>> am
>>> comfortable with.  However, I don't believe that any of the listed attacks
>>> remain viable in modern applications.  What is most often the case is that
>>> a
>>> trust anchor is installed on enterprise users' machines and new
>>> certificates are
>>> minted as needed.  In other words, the host that is accessing the HTTPS
>>> site is
>>> owned by the enterprise and modified so that it can comply with its
>>> policies.
>>>
>>> When you recommend attack like this (to be clear, I would oppose
>>> publication of
>>> text that does this), you need to acknowledge the downsides.

By use of the word, attack, this is not a recommended method.  It's
also not in line with the goals of RFC7258, so it's just a practice
that's documented.  Not one that is endorsed (none are).

  For example,
>>> MitM
>>> devices routinely break connections, they hide the true security status of
>>> communications from endpoints and users, they frequently implement weaker
>>> versions of protocols, they often don't include the same degree of rigor
>>> in
>>> things like certificate validation, and probably many more things that I
>>> can't
>>> casually list off the cuff.
>
> Please suggest text.
>
>>>
>>> The discussion of caching here warrants a new section.
>>>
>>> Section 5.1
>>>
>>> s/effect/affect
>>>
>
> Thanks, we'll fix this.
>
>>> No complaint here, just an advertisement for technical solutions that
>>> aren't
>>> affected by increases in encryption.  Good, though I'm not sure if the
>>> section
>>> meets the document's criteria for inclusion.
>>>
>>> Section 5.3
>>>
>>> No cititation for APWG.  Not an IETF working group from what I can see.
>
> We'll add that, thanks.

Added reference.
>
>>>
>>> There's a presumption here that administrators need to perform these
>>> tasks.  Why
>>> can't endpoints do this?  It would certainly be a whole lot less invasive
>>> that
>>> way.  Take a look at how browsers implement checks for "bad" sites (which
>>> include phishing sites).  These methods have some fairly significant
>>> privacy
>>> safeguards without compromising on performance.
>
> A lot will move to the endpoints, but things like logging need to
> improve and we need to get application developers to do a better job
> so that there is no reason for someone to want to try to intercept
> traffic for troubleshooting.  Operators see this as an insurmountable
> problem.  We need to help.
>
>>>
>>> Section 5.5
>>>
>>> See my comment about about endpoint-based methods.
>
> Already agree with this point.
>
>>>
>>> Section 5.6
>>>
>>> I believe that the spoofed source address problem is not relevant to this
>>> document.  It's a fairly well understood problem.  That said, if we could
>>> wave a
>>> magic wand and get BCP 38 deployed, that might be nice.
>>>
>>> Section 6.1
>>>
>>> As this says, it's fairly well understood that - for HTTP - SNI is used.
>>> The
>>> point that it is optional is interesting, but doesn't deserve the amount
>>> of
>>> attention this section devotes to it.  The clients that don't include SNI
>>> are in
>>> a diminishing minority.
>
> Text was aded per EKR's review.
>
>>>
>>> That said, this doesn't pay any attention to another feature in HTTP/2:
>>> connection coalescing.
>
> Please suggest text if this should be included.
>
>>>
>>> Section 6.2
>>>
>>> ALPN will be encrypted in TLS 1.3.
>
> Noted.  Thanks.
>
>>>
>>> Section 6.3
>>>
>>> This reads as a invitation to perform traffic analysis (a statement that I
>>> oppose).  Note that we have added padding to most recent protocols (HTTP/2
>>> and
>>> TLS 1.3 in particular) to give endpoints the ability to resist this sort
>>> of
>>> attack.
>>>
>>> Note that block ciphers can add ~240 octets of discretionary padding per
>>> record.
>>> That can be pretty effective if you are careful.
>
> I believe this text was added through the IESG review.  I don't see
> the problem with the text you are citing, so could you suggest
> alternate text?
>
>>>
>>> Section 7
>>>
>>> This section is duplicative of much of the rest of the document.  I
>>> realize that
>>> editing is hard, but see my earlier comments about structure.
>
> This text was the appendix, but moved to section 7 per IESG review and
> discuss.  It was the mobile operator view.
>
>>>
>>> It's obvious that this section is about QUIC.  That shows in several ways.
>>> It's
>>> nice how it doesn't say so out loud, but it leaks through in several
>>> confusing
>>> ways.  See below.
>>>
>>> Section 7.1
>>>
>>> This section is purportedly about encrypted ACKs, which won't happen until
>>> we
>>> get to QUIC.  But the points regarding proxies (b, c, d) are not prevented
>>> by
>>> encrypted ACKs, they are prevented by encryption more generally.  Point e
>>> is
>>> defeated by integrity protection of ACKs, not confidentiality protection.
>>>
>>> I hope that the IETF never publishes draft-dolson-plus-middlebox-benefits;
>>> it
>>> makes claims about the benefits of specific solutions for different use
>>> cases
>>> with the goal of justifying those solutions.  At the same time, it fails
>>> to
>>> recognize the existence of alternative, often superior, solutions for
>>> those use
>>> cases.  In other words, it has many of the same issues as this document.
>
> I think this is an early document and expect it will get some
> revision.  This was added into our document per Mirja's IESG review.
> They are documenting middle boxes that use 5-tuples.  That point isn't
> clear until the summary.  I provided some light feedback, but could
> provide more to help them improve the document.  I think it's fine to
> document these things and then figure out how we can do better with
> IETF agreed upon protocol design intentions (end-to-end and assisting
> to improve user's privacy as well as the security of sessions.
>
>>>
>>> FWIW, also be OK if draft-thomson-http-bc never went anywhere as well; I
>>> don't
>>> know how to close the gap between the privacy assurances I wish it had and
>>> the
>>> privacy weaknesses it has.
>>>
>>> The phrase "trusted proxies" is a dangerously misleading phrase.  The
>>> concept of
>>> trust is - particularly in this context - frequently abused.
>
> That's why the quotes were there, but this has been re-phrased in 10 -
> see the SecDir review.
>
>>>
>>> Sections 7.2 and 7.3
>>>
>>> I'd be interested in learning about the justification for these features
>>> (again,
>>> go back to my comment about to whom the benefit accrues, and I'd advise
>>> caution
>>> not to make the trickle-down economics mistake of using second-order
>>> effects).
>>> Personally, I'm not that sad that they are going to be negatively
>>> affected.
>>>
>>> Section 7.2, Point d seems to be saying something about a multiplexed
>>> protocol,
>>> not one that has an encrypted transport header (see above regarding QUIC).
>>>
>>> All these points equally apply to HTTPS, which suggest that encrypted
>>> transport
>>> headers is not the issue (unless by transport we mean HTTP).
>
> Again, section 7 was changed in IESG review and added into the body of
> the document per Mirja's discuss since the mobile operator is
> important to include.
>
>>>
>>> Section 7.4
>>>
>>> s/GPSR/GPRS/ ?
>
> Fixed.  I thought this was fixed in 9, hence me thinking you read the
> wrong version.
>
>>>
>>> Section 8
>>>
>>> I generally agree with the first statement here, but after having read the
>>> document, I could take away some very different views on what the
>>> "problems at
>>> hand" actually are.  I suspect that different people will have very
>>> different
>>> takeaways.
>>>
>>> The conclusion section of a document is not the right place to start
>>> introducing
>>> new information, particularly information relevant to RFC 2804.
>
> Should we move this to the introduction perhaps to help with context setting?
>
>>>
>>> Not sure where this is going:
>>>
>>>    Terrorists and criminals have been using encryption for many years.
>>>
>>> Because it's disconnected from the remainder of the paragraph.  If you are
>>> going
>>> to invoke the T-word, you had better have a strong argument to make.  On
>>> the
>>> final sentence of that paragraph, the subject ("This") is unclear.
>>>
>
> Sure, the point was that their use of encryption is not a
> justification argue any of the improvements to crypto for the general
> population.  Incident handlers know full well that encryption has been
> in place for a long time by these users.  Essentially, it's not an argument that
> hold muster.

The following sentence was added:
      Changes to improve encryption or to deploy OS methods have little
      impact on the detection of such activities as they already have access to
      strong encryption.
>
>>
>>
>>
>> --
>>
>> Best regards,
>> Kathleen
>>
>>
>
>
>
> --
>
> Best regards,
> Kathleen & Al



-- 

Best regards,
Kathleen


From nobody Wed Apr 12 23:09:26 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C461267BB for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 23:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 r0EjHX2mVrsl for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 23:09:23 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-oln040092070068.outbound.protection.outlook.com [40.92.70.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67E88124234 for <ietf@ietf.org>; Wed, 12 Apr 2017 23:09:23 -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; bh=AhNLU1c0ijUmQpZBnqYSZecuNRsuqWe6ebSMe5LHpRk=; b=UEykFGDkBYlNwXIdxpof14M+wsWRyuyp8NkruCKStMh2jHqQcfz48odkqm9zqV7QacidKKpj8gu/LqWodWtX4O/w+4QSnrtZ2BJgmUszUIVB0XgLM+k2qFMh7gO7f1rdHE/GP55uOEn6mioL0qyhgd82zcgBz1UuPJabZQhOKte00nt/YXit5o9RRPHESYmliLHaV9+i1y5XdxH02h1ahbl+Miz+HWajmtoDdjYx+7H22fc6z/XbBx0KrlvhxyPW9PY9DY1M83sC5Z/UM8VByMdnmrCKyfmnOrMxlRK7f5ou46JWvMIp6D7mcnpNwj8JzYTNMteDJLSKMHROV7u+TA==
Received: from AM5EUR03FT056.eop-EUR03.prod.protection.outlook.com (10.152.16.57) by AM5EUR03HT058.eop-EUR03.prod.protection.outlook.com (10.152.17.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 06:09:21 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.59) by AM5EUR03FT056.mail.protection.outlook.com (10.152.17.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 06:09:21 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 06:09:21 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
CC: ietf <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+kD4XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 06:09:21 +0000
Message-ID: <AM4PR0401MB2241B3E945CE1163AFD22BBABD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241D2424F3027B4DB2496A7BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:4D7E9F7DE71D9C866382F7D5CEBBCB2F849412894983DA58CF0447E32D403938; UpperCasedChecksum:BE69E4034AAED842C8E36B66CC99B13F252EB79642A2F8209E46CBDB8BD1EB4C; SizeAsReceived:7884; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT058; 5:OBSFA0AA6OPHN7ImODdwSi0gZF3t9X2e3141XCMlk8d/0nzTV5kNatHH8TDni3jLHipUnRub+eiihTmf5vqs0KPM0kknIw4N7ofrXeXNDq+0cCAOsJKgU+zlkc5ZNLjZ9jJyTsHbfctoRAO7YegRdw==; 24:tfOm3Dev8Acxt1g60yFuz+rmcXrpCC06lIEyLMgIIBU2Z9Ys0AxSgKSrMCiXa/59TK/GO18EjkYYc+IEYFSfFJz6kQdliDvHghOwmZodyzk=; 7:9RMYD6YvRBe3wqoLkDeIr5MwpIDjrVGg6zENmkzSB8iPHVk1uCLXQln3ZFBHgQ4xpJDLzcYPVYCkUFBA7evI641m+PEzqoCSUJE7i5L6GrlkBXrHRQmo6GAVSAdCWf29i/mDVbQW1mNkxA7jZ4ZzIGn2IqpDJjhbd6Pa326O8GOXvQBEVN+Ee4g/UZD0kAseHkgi4GiFgdsxRO4aOyO1y4rKKr8IC2pECsNOo2AVnmUM+TkitZmdZDDUDiM+pjhh+O/sPN6D38XZwd/I0a06lz0jw4lo7CWKsfne2VQb+jSg20hDxiwFoT8EDof8C+bo
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT058; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 538a65c5-07ba-4a5e-0718-08d482339feb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:AM5EUR03HT058; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT058; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT058; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241B3E945CE1163AFD22BBABD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 06:09:21.3423 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT058
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2vvsnCFbNhfza0Eg61ruFoWStdA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 06:09:25 -0000

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

U29tZXRoaW5nIGVsc2UgdG8gYWRkLCBDYWlybyBhbmQgR2l6YSBhcmUgc28gYmlnIGdvdmVybm9y
YXRlcywgYW5kIG5lYXIgZWFjaCBvdGhlcnMsIGNvbnRhaW5pbmcgZG96ZW5zIG9mIGNpdGllcywg
SSByZW1lbWJlciBJIGF0dGVuZGVkIGFuIGV2ZW50IG1hZGUgYnkgQWZyaW5pYyBhbmQgcmVhbGx5
IHRoZXkgbWFkZSBhIGdvb2QgY2hvaWNlIGluIHNlbGVjdGluZyB0aGUgaG90ZWwgYW5kIGNpdHks
IHF1aXRlIGFyZWEgYW5kIG5vdCBmYXIgZnJvbSBvdGhlciBoaXN0b3JpY2FsIG9yIG1vZGVybiBj
aXRpZXMsIGl0IHdhcyAyMCBtaW51dGVzIHRvIGdvIHRvIHRoZSBweXJhbWlkcyBmb3IgZXhhbXBs
ZSAoYW5kIG9mIGNvdXJzZSB3aXRoIGlnbm9yaW5nIHRyYWZmaWMgYmVjYXVzZSBpdCBkZXBlbmRz
IG9uIHdoZW4gYW5kIHdoZXJlIHRvIGdvKS4NCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1l
ZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206IEtoYWxlZCBPbWFyDQpUbzogWW9hdiBOaXINCkND
OiBpZXRmDQoNCg0KSSByZWNvbW1lbmQgRWd5cHQgYmVjYXVzZSBpdCBpcyBhdCB0aGUgY2VudGVy
LCB3aWxsIG5vdCBiZSBzbyBsb25nIGZvciBhbnlvbmUsIGFsc28sIHdlYXRoZXIgaXMgYW4gaW1w
b3J0YW50IGZhY3RvciwgYW5kIGZvciB0aG9zZSB3aG8gd291bGQgbGlrZSB0byB2aXNpdCBoaXN0
b3JpY2FsIHBsYWNlcyBzaG91bGQgZm9jdXMgbW9yZSBhYm91dCBob3cgdG8gZ28gYW5kIHdoYXQg
dG8gd2VhciwgdGhlcmUgYXJlIG1vZGVybiBjaXRpZXMgYW5kIG9sZCBjaXRpZXMsIHRoZXJlIGlz
IGEgYmlnIGRpZmZlcmVuY2UsIG1hbnkgdG91cmlzdHMgaGVyZSB3aXRoIGFsbCBkaWZmZXJlbnQg
c3R5bGVzLCBhbmQgb2YgY291cnNlIG5vIG9uZSB3aWxsIGRpc3Jlc3BlY3QgcG9lcGxlIGhlcmUg
c28gaGUvc2hlIHdpbGwgZ2V0IGluIHRyb3VibGUuDQoNCkJ1dCByZWdhcmRpbmcgQ2FuYWRhLCBm
dWxsIHJlc3BlY3QgdG8gdGhvc2UgcGVvcGxlIGFuZCB0aGV5IHdpbGwgYmUgbW9yZSB0aGFuIHdl
bGNvbWVkIGhlcmUuDQoNClJlZ2FyZHMsDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAt
LS0tLS0tLQ0KU3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0
aW5ncywgYW5kIElFVEYgMTAyDQpGcm9tOiBZb2F2IE5pcg0KVG86IFN0ZXBoZW4gRmFycmVsbA0K
Q0M6IElBT0MgTGlzdCAsSUVURg0KDQoNCk9uIDEzIEFwciAyMDE3LCBhdCAzOjAwLCBTdGVwaGVu
IEZhcnJlbGwgd3JvdGU6DQoNCg0KPiBJIGRvIG5vdCByZWNhbGwgdGhlIG9wcG9zaXRlIG9uIHRo
ZSBsaXN0LCBpLmUuIHNvbWVvbmUgYWRhbWFudGx5DQo+IGFyZ3VpbmcgdGhhdCB3ZSBvdWdodCBj
b250aW51ZSB0byBtZWV0IGluIHRoZSBVUy4gVGhlcmUgd2VyZSBzb21lDQo+IG1haWxzIHRoYXQg
SSdkIHNheSBtYXliZSB3ZWFrbHkgYXJndWVkIGZvciBjb250aW51ZWQgVVMgbWVldGluZ3MNCj4g
aW4gdGhlIHJlbGV2YW50IHRpbWVmcmFtZS4gQnV0IG5vdGhpbmcgYXBwcm9hY2hpbmcgYWRhbWFu
dC4NCg0KV2VsbCBhdCB0aGlzIHBvaW50IGFyZ3VpbmcgZm9yIG1vcmUgVVMgbWVldGluZ3MgYmVj
YXVzZSBJIGhhZCBubyB0cm91YmxlIG9idGFpbmluZyBhIHZpc2EgYW5kIGVudGVyaW5nIHRoZSBV
UyBpcyB0aGUgZXF1aXZhbGVudCBvZiBzdGF0aW5nIHRoYXQgSeKAmW0gYSB3aGl0ZSBndXkgYW5k
IEnigJltIG5vdCBmZWVsaW5nIGFueSByYWNpc20gb3Igc2V4aXNtLg0KDQpNb3JlIHRvIHRoZSBw
b2ludCwgcHJldHR5IG11Y2ggYWxsIFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0ZXIgdGhhbiBwcmV0
dHkgbXVjaCBhbnkgRXVyb3BlYW4gbGV0IGFsb25lIEFzaWFuIHZlbnVlcywgd2VpcmRseSBzaGFw
ZWQgcm9vbXMgbm90d2l0aHN0YW5kaW5nLiBMb25kb24gYW5kIFBhcmlzIGNvbWUgY2xvc2UuIEJl
cmxpbiBhbmQgUHJhZ3VlIGRvbuKAmXQuIFRoaXMgaXMgaW4gdGVybXMgb2YgbmVhcmJ5IGF2YWls
YWJpbGl0eSBvZiBmb29kIChub3RpY2UgdGhlIGxhY2sgb2YgYSDigJxPTUcgd2hlcmUgY2FuIEkg
Z2V0IGEgZ3JhYi1hbmQtZ28gc2FuZHdpY2jigJ0gdGhyZWFkIGluIDk4YXR0ZW5kZWVzKSBhbmQg
aW4gdGVybXMgb2YgdGhlIGF2YWlsYWJpbGl0eSBvZiBuZWFyYnkgbG93LWNvc3QgaG90ZWxzLiBB
bmQgeWVzLCB0aGUgZmFjdCB0aGF0IGV2ZXJ5Ym9keSBzcGVha3MgRW5nbGlzaCBhbHNvIGhlbHBz
LiBBbmQgZGVzcGl0ZSB3aGF0IHBlb3BsZSB0aGluayBhYm91dCBjcmltZSwgbm8gSUVURi1lciBl
dmVyIGdvdCBzaG90IGluIHRoZSBVUyBkdXJpbmcgSUVURiB3ZWVrLCBidXQgZXZlcnkgdGltZSB3
ZSBtZWV0IGluIEV1cm9wZSBzb21lIG9mIHVzIHdpbGwgZ2V0IHRoZWlyIHBvY2tldHMgcGlja2Vk
Lg0KDQpGb3IgbWUsIFVTIG1lZXRpbmdzIChDYW5hZGHigJlzIE9LIHRvbykgYXJlIG1vcmUgY29u
dmVuaWVudCBkZXNwaXRlIHRoZSBsb25nLCB0b3J0dW91cyBmbGlnaHQuIFBlb3BsZSBoYXZlIGJl
ZW4gZ3J1bWJsaW5nIGFib3V0IFVTIGVudHJ5IHByb2NlZHVyZSBmb3IgeWVhcnMgYW5kIHdpdGgg
Z29vZCByZWFzb24uIEJ1dCBvdmVyYWxsIFVTIG1lZXRpbmdzIGFyZSBzaW1wbHkgbW9yZSBjb252
ZW5pZW50LiBZTU1WDQoNCllvYXYNCg0K

--_000_AM4PR0401MB2241B3E945CE1163AFD22BBABD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <E4486AB3F0DF444B8427A9E68CEBB1EE@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KU29tZXRoaW5nIGVs
c2UgdG8gYWRkLCBDYWlybyBhbmQgR2l6YSBhcmUgc28gYmlnIGdvdmVybm9yYXRlcywgYW5kIG5l
YXIgZWFjaCBvdGhlcnMsIGNvbnRhaW5pbmcgZG96ZW5zIG9mIGNpdGllcywgSSByZW1lbWJlciBJ
IGF0dGVuZGVkIGFuIGV2ZW50IG1hZGUgYnkgQWZyaW5pYyBhbmQgcmVhbGx5IHRoZXkgbWFkZSBh
IGdvb2QgY2hvaWNlIGluIHNlbGVjdGluZyB0aGUgaG90ZWwgYW5kIGNpdHksIHF1aXRlIGFyZWEg
YW5kIG5vdCBmYXIgZnJvbQ0KIG90aGVyIGhpc3RvcmljYWwgb3IgbW9kZXJuIGNpdGllcywgaXQg
d2FzIDIwIG1pbnV0ZXMgdG8gZ28gdG8gdGhlIHB5cmFtaWRzIGZvciBleGFtcGxlIChhbmQgb2Yg
Y291cnNlIHdpdGggaWdub3JpbmcgdHJhZmZpYyBiZWNhdXNlIGl0IGRlcGVuZHMgb24gd2hlbiBh
bmQgd2hlcmUgdG8gZ28pLg0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDog
MS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0K
U3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5k
IElFVEYgMTAyPGJyPg0KRnJvbTogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWls
LmNvbT48YnI+DQpUbzogWW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFpbC5jb20+PGJyPg0KQ0M6IGll
dGYgPGlldGZAaWV0Zi5vcmc+PGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxi
bG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1s
ZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KSSByZWNvbW1lbmQgRWd5cHQg
YmVjYXVzZSBpdCBpcyBhdCB0aGUgY2VudGVyLCB3aWxsIG5vdCBiZSBzbyBsb25nIGZvciBhbnlv
bmUsIGFsc28sIHdlYXRoZXIgaXMgYW4gaW1wb3J0YW50IGZhY3RvciwgYW5kIGZvciB0aG9zZSB3
aG8gd291bGQgbGlrZSB0byB2aXNpdCBoaXN0b3JpY2FsIHBsYWNlcyBzaG91bGQgZm9jdXMgbW9y
ZSBhYm91dCBob3cgdG8gZ28gYW5kIHdoYXQgdG8gd2VhciwgdGhlcmUgYXJlIG1vZGVybiBjaXRp
ZXMgYW5kIG9sZA0KIGNpdGllcywgdGhlcmUgaXMgYSBiaWcgZGlmZmVyZW5jZSwgbWFueSB0b3Vy
aXN0cyBoZXJlIHdpdGggYWxsIGRpZmZlcmVudCBzdHlsZXMsIGFuZCBvZiBjb3Vyc2Ugbm8gb25l
IHdpbGwgZGlzcmVzcGVjdCBwb2VwbGUgaGVyZSBzbyBoZS9zaGUgd2lsbCBnZXQgaW4gdHJvdWJs
ZS48YnI+DQo8YnI+DQpCdXQgcmVnYXJkaW5nIENhbmFkYSwgZnVsbCByZXNwZWN0IHRvIHRob3Nl
IHBlb3BsZSBhbmQgdGhleSB3aWxsIGJlIG1vcmUgdGhhbiB3ZWxjb21lZCBoZXJlLjxicj4NCjxi
cj4NClJlZ2FyZHMsDQo8ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUi
Pjxicj4NCjxicj4NCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJq
ZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVU
RiAxMDI8YnI+DQpGcm9tOiBZb2F2IE5pciA8eW5pci5pZXRmQGdtYWlsLmNvbT48YnI+DQpUbzog
U3RlcGhlbiBGYXJyZWxsIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPjxicj4NCkNDOiBJQU9D
IExpc3QgPGlhb2NAaWV0Zi5vcmc+LElFVEYgPGlldGZAaWV0Zi5vcmc+PGJyPg0KPGJyPg0KPGJy
IHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1h
cmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDox
ZXgiPg0KT24gMTMgQXByIDIwMTcsIGF0IDM6MDAsIFN0ZXBoZW4gRmFycmVsbCA8c3RlcGhlbi5m
YXJyZWxsQGNzLnRjZC5pZT53cm90ZTo8YnI+DQo8YnI+DQo8YnI+DQomZ3Q7IEkgZG8gbm90IHJl
Y2FsbCB0aGUgb3Bwb3NpdGUgb24gdGhlIGxpc3QsIGkuZS4gc29tZW9uZSBhZGFtYW50bHk8YnI+
DQomZ3Q7IGFyZ3VpbmcgdGhhdCB3ZSBvdWdodCBjb250aW51ZSB0byBtZWV0IGluIHRoZSBVUy4g
VGhlcmUgd2VyZSBzb21lPGJyPg0KJmd0OyBtYWlscyB0aGF0IEknZCBzYXkgbWF5YmUgd2Vha2x5
IGFyZ3VlZCBmb3IgY29udGludWVkIFVTIG1lZXRpbmdzPGJyPg0KJmd0OyBpbiB0aGUgcmVsZXZh
bnQgdGltZWZyYW1lLiBCdXQgbm90aGluZyBhcHByb2FjaGluZyBhZGFtYW50Ljxicj4NCjxicj4N
CldlbGwgYXQgdGhpcyBwb2ludCBhcmd1aW5nIGZvciBtb3JlIFVTIG1lZXRpbmdzIGJlY2F1c2Ug
SSBoYWQgbm8gdHJvdWJsZSBvYnRhaW5pbmcgYSB2aXNhIGFuZCBlbnRlcmluZyB0aGUgVVMgaXMg
dGhlIGVxdWl2YWxlbnQgb2Ygc3RhdGluZyB0aGF0IEnigJltIGEgd2hpdGUgZ3V5IGFuZCBJ4oCZ
bSBub3QgZmVlbGluZyBhbnkgcmFjaXNtIG9yIHNleGlzbS48YnI+DQo8YnI+DQpNb3JlIHRvIHRo
ZSBwb2ludCwgcHJldHR5IG11Y2ggYWxsIFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0ZXIgdGhhbiBw
cmV0dHkgbXVjaCBhbnkgRXVyb3BlYW4gbGV0IGFsb25lIEFzaWFuIHZlbnVlcywgd2VpcmRseSBz
aGFwZWQgcm9vbXMgbm90d2l0aHN0YW5kaW5nLiBMb25kb24gYW5kIFBhcmlzIGNvbWUgY2xvc2Uu
IEJlcmxpbiBhbmQgUHJhZ3VlIGRvbuKAmXQuIFRoaXMgaXMgaW4gdGVybXMgb2YgbmVhcmJ5IGF2
YWlsYWJpbGl0eSBvZiBmb29kIChub3RpY2UNCiB0aGUgbGFjayBvZiBhIOKAnE9NRyB3aGVyZSBj
YW4gSSBnZXQgYSBncmFiLWFuZC1nbyBzYW5kd2ljaOKAnSB0aHJlYWQgaW4gOThhdHRlbmRlZXMp
IGFuZCBpbiB0ZXJtcyBvZiB0aGUgYXZhaWxhYmlsaXR5IG9mIG5lYXJieSBsb3ctY29zdCBob3Rl
bHMuIEFuZCB5ZXMsIHRoZSBmYWN0IHRoYXQgZXZlcnlib2R5IHNwZWFrcyBFbmdsaXNoIGFsc28g
aGVscHMuIEFuZCBkZXNwaXRlIHdoYXQgcGVvcGxlIHRoaW5rIGFib3V0IGNyaW1lLCBubyBJRVRG
LWVyDQogZXZlciBnb3Qgc2hvdCBpbiB0aGUgVVMgZHVyaW5nIElFVEYgd2VlaywgYnV0IGV2ZXJ5
IHRpbWUgd2UgbWVldCBpbiBFdXJvcGUgc29tZSBvZiB1cyB3aWxsIGdldCB0aGVpciBwb2NrZXRz
IHBpY2tlZC48YnI+DQo8YnI+DQpGb3IgbWUsIFVTIG1lZXRpbmdzIChDYW5hZGHigJlzIE9LIHRv
bykgYXJlIG1vcmUgY29udmVuaWVudCBkZXNwaXRlIHRoZSBsb25nLCB0b3J0dW91cyBmbGlnaHQu
IFBlb3BsZSBoYXZlIGJlZW4gZ3J1bWJsaW5nIGFib3V0IFVTIGVudHJ5IHByb2NlZHVyZSBmb3Ig
eWVhcnMgYW5kIHdpdGggZ29vZCByZWFzb24uIEJ1dCBvdmVyYWxsIFVTIG1lZXRpbmdzIGFyZSBz
aW1wbHkgbW9yZSBjb252ZW5pZW50LiBZTU1WPGJyPg0KPGJyPg0KWW9hdjxicj4NCjxicj4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0
bWw+DQo=

--_000_AM4PR0401MB2241B3E945CE1163AFD22BBABD020AM4PR0401MB2241_--


From nobody Wed Apr 12 23:33:14 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5C0128B92 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 23:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 bvXw0oZjIhdV for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 23:33:10 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069102.outbound.protection.outlook.com [40.92.69.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31AD4127867 for <ietf@ietf.org>; Wed, 12 Apr 2017 23:33:10 -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; bh=6Aa/rmL8oU5nbHqeg27KGCYhBNb3w+uT09z3oGtKorE=; b=VFhPjilBsgQhmMGGFwVaRPIgWbbMCeuKxOt09BZC7Za3OH5da/s6wUWsqMeM4qPjntE4k9zSbuwughuIEyh4mYxgcNSCvvDwDhxGMpaNtgaSkEHtv9yrtybQqnxEX0Kwu11WNMQPcaJyCdYTgWPqFmkse91sWZjsNoHNLhA0ytIgt2nuMhoqHPNnX1JpnRaRV3FfdxA7PAxuYtUlcFQ5OGGqNrhi8LfO7X1mZ9cnF205qqLQ2RF/+lY8aLPz9Gj9u3zQMKROjPUUP0NTlQw1y/Ozmsvvyxc7oLijLe51F7pF6sWa3K/cOE/RTPf4BvF3KFIgUzfFc8flQCJ3FuFEog==
Received: from HE1EUR02FT008.eop-EUR02.prod.protection.outlook.com (10.152.10.60) by HE1EUR02HT033.eop-EUR02.prod.protection.outlook.com (10.152.11.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 06:33:08 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.10.54) by HE1EUR02FT008.mail.protection.outlook.com (10.152.10.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 06:33:08 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 06:33:07 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+kD4XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 06:33:07 +0000
Message-ID: <AM4PR0401MB2241DCA8589E952E278705A6BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241B3E945CE1163AFD22BBABD020@AM4PR0401MB2241.eurprd04.prod.outlook.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:6DBF4B759C5367410EB92A7D868A9A0B0B0A437AC65EDD231BA61D329ED1C323; UpperCasedChecksum:7843FBCFA38F06F079C91EDE292B23CDA13B0810F6C1B8C4B388881DEF7676B4; SizeAsReceived:7859; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT033; 5:FNn/QKyypciTMN3VSz1yYc4LUupCWVz/oT+a7qCxH9NGMVfgcIyge4HuB1weqyDaTaNMj57ZUJoxvOs+D0isrYIJo8g2nU8hn68zxt1GieGwcZFySLT6kCBmZlguLTWXDCgKRHspv/gQc3SWhZd6dgBV7g999QmkrmgnZhbC8aY=; 24:uHj13REdYNXrHIcafuM+9gHPWUlgcUCaCwNkqYQW5hI7zw9ALL5+4Ik//oBqoTOTVT8rOR0YKViTHWeocAl1YqLBUTt9f2vIOVgv0ewUNlI=; 7:fIScjYXTs1s1E0280owZ1hKIynNISvRgeSvRzdRV0J8DuhMvUwGGVT9KFHYKJ1Bvdn05RPzJL4V3Y5pJxLEcWY4Zzv+Hsh9uMOi5kgOi+7Fkqx7TJ+bbIBAj6tjXQVXeFTv0/nkqwJf3FfHPGR6lPGwqrOxMIZHiw89EnNCVwS4F8F0yYrF6hdl+WB14xgfsdRsCBRgpMDx0NAFf9+NKE/jodEyZDFH1OWmz2QWOXoMC7mqEUoQvQgp0R+9JOaTAHE24Af+twtjcFiOy60SImXSPeW0YLAji8q2JwrP1QhXjyg0Xg9KOBriH8+nypA4D
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT033; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 3d55f199-c513-4f3d-dfa6-08d48236f209
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR02HT033; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR02HT033; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT033; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241DCA8589E952E278705A6BD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 06:33:07.5267 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT033
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rdeFaUmK0u5frLw0qZ4M--vNMmE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 06:33:12 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBVcGRh
dGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMg0KRnJvbTog
S2hhbGVkIE9tYXINClRvOiBZb2F2IE5pcg0KQ0M6DQoNCg0KUmVnYXJkaW5nIHZpc2EgYW5kIGVu
dHJ5LCB0aGVyZSB3aWxsIGJlIG5vIGNvbXBsaWNhdGlvbnMgZXNwZWNpYWxseSBmb3IgcGVvcGxl
IGxpa2UgeW91LCBJIG1lYW4gc2NpZW50aXN0cyB3aG8gYXJlIGNvbWluZyB0byBoZWxkIGEgdGVj
aG5pY2FsIG1lZXRpbmcsIGknbSBzdXJlIHRoZXJlIHdpbGwgYmUgbm8gcHJvYmxlbSBmb3IgYWxs
IHNvIHRoaXMgaXNzdWUgY2FuIGJlIGlnbm9yZWQgKG5vIHJhY2lzbSBoZXJlKSwgYnV0IG91dHNp
ZGUgdGhlIG1lZXRpbmcgc2VjdXJpdHkgaXMgeW91ciBvd24gcmVzcG9uc2liaWx0eS4NCg0KDQot
LS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogVXBkYXRlIG9u
IGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206IEtoYWxl
ZCBPbWFyDQpUbzogWW9hdiBOaXINCkNDOiBpZXRmDQoNCg0KU29tZXRoaW5nIGVsc2UgdG8gYWRk
LCBDYWlybyBhbmQgR2l6YSBhcmUgc28gYmlnIGdvdmVybm9yYXRlcywgYW5kIG5lYXIgZWFjaCBv
dGhlcnMsIGNvbnRhaW5pbmcgZG96ZW5zIG9mIGNpdGllcywgSSByZW1lbWJlciBJIGF0dGVuZGVk
IGFuIGV2ZW50IG1hZGUgYnkgQWZyaW5pYyBhbmQgcmVhbGx5IHRoZXkgbWFkZSBhIGdvb2QgY2hv
aWNlIGluIHNlbGVjdGluZyB0aGUgaG90ZWwgYW5kIGNpdHksIHF1aXRlIGFyZWEgYW5kIG5vdCBm
YXIgZnJvbSBvdGhlciBoaXN0b3JpY2FsIG9yIG1vZGVybiBjaXRpZXMsIGl0IHdhcyAyMCBtaW51
dGVzIHRvIGdvIHRvIHRoZSBweXJhbWlkcyBmb3IgZXhhbXBsZSAoYW5kIG9mIGNvdXJzZSB3aXRo
IGlnbm9yaW5nIHRyYWZmaWMgYmVjYXVzZSBpdCBkZXBlbmRzIG9uIHdoZW4gYW5kIHdoZXJlIHRv
IGdvKS4NCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBS
ZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDIN
CkZyb206IEtoYWxlZCBPbWFyDQpUbzogWW9hdiBOaXINCkNDOiBpZXRmDQoNCg0KSSByZWNvbW1l
bmQgRWd5cHQgYmVjYXVzZSBpdCBpcyBhdCB0aGUgY2VudGVyLCB3aWxsIG5vdCBiZSBzbyBsb25n
IGZvciBhbnlvbmUsIGFsc28sIHdlYXRoZXIgaXMgYW4gaW1wb3J0YW50IGZhY3RvciwgYW5kIGZv
ciB0aG9zZSB3aG8gd291bGQgbGlrZSB0byB2aXNpdCBoaXN0b3JpY2FsIHBsYWNlcyBzaG91bGQg
Zm9jdXMgbW9yZSBhYm91dCBob3cgdG8gZ28gYW5kIHdoYXQgdG8gd2VhciwgdGhlcmUgYXJlIG1v
ZGVybiBjaXRpZXMgYW5kIG9sZCBjaXRpZXMsIHRoZXJlIGlzIGEgYmlnIGRpZmZlcmVuY2UsIG1h
bnkgdG91cmlzdHMgaGVyZSB3aXRoIGFsbCBkaWZmZXJlbnQgc3R5bGVzLCBhbmQgb2YgY291cnNl
IG5vIG9uZSB3aWxsIGRpc3Jlc3BlY3QgcG9lcGxlIGhlcmUgc28gaGUvc2hlIHdpbGwgZ2V0IGlu
IHRyb3VibGUuDQoNCkJ1dCByZWdhcmRpbmcgQ2FuYWRhLCBmdWxsIHJlc3BlY3QgdG8gdGhvc2Ug
cGVvcGxlIGFuZCB0aGV5IHdpbGwgYmUgbW9yZSB0aGFuIHdlbGNvbWVkIGhlcmUuDQoNClJlZ2Fy
ZHMsDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0KU3ViamVjdDogUmU6
IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyDQpG
cm9tOiBZb2F2IE5pcg0KVG86IFN0ZXBoZW4gRmFycmVsbA0KQ0M6IElBT0MgTGlzdCAsSUVURg0K
DQoNCk9uIDEzIEFwciAyMDE3LCBhdCAzOjAwLCBTdGVwaGVuIEZhcnJlbGwgd3JvdGU6DQoNCg0K
PiBJIGRvIG5vdCByZWNhbGwgdGhlIG9wcG9zaXRlIG9uIHRoZSBsaXN0LCBpLmUuIHNvbWVvbmUg
YWRhbWFudGx5DQo+IGFyZ3VpbmcgdGhhdCB3ZSBvdWdodCBjb250aW51ZSB0byBtZWV0IGluIHRo
ZSBVUy4gVGhlcmUgd2VyZSBzb21lDQo+IG1haWxzIHRoYXQgSSdkIHNheSBtYXliZSB3ZWFrbHkg
YXJndWVkIGZvciBjb250aW51ZWQgVVMgbWVldGluZ3MNCj4gaW4gdGhlIHJlbGV2YW50IHRpbWVm
cmFtZS4gQnV0IG5vdGhpbmcgYXBwcm9hY2hpbmcgYWRhbWFudC4NCg0KV2VsbCBhdCB0aGlzIHBv
aW50IGFyZ3VpbmcgZm9yIG1vcmUgVVMgbWVldGluZ3MgYmVjYXVzZSBJIGhhZCBubyB0cm91Ymxl
IG9idGFpbmluZyBhIHZpc2EgYW5kIGVudGVyaW5nIHRoZSBVUyBpcyB0aGUgZXF1aXZhbGVudCBv
ZiBzdGF0aW5nIHRoYXQgSeKAmW0gYSB3aGl0ZSBndXkgYW5kIEnigJltIG5vdCBmZWVsaW5nIGFu
eSByYWNpc20gb3Igc2V4aXNtLg0KDQpNb3JlIHRvIHRoZSBwb2ludCwgcHJldHR5IG11Y2ggYWxs
IFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0ZXIgdGhhbiBwcmV0dHkgbXVjaCBhbnkgRXVyb3BlYW4g
bGV0IGFsb25lIEFzaWFuIHZlbnVlcywgd2VpcmRseSBzaGFwZWQgcm9vbXMgbm90d2l0aHN0YW5k
aW5nLiBMb25kb24gYW5kIFBhcmlzIGNvbWUgY2xvc2UuIEJlcmxpbiBhbmQgUHJhZ3VlIGRvbuKA
mXQuIFRoaXMgaXMgaW4gdGVybXMgb2YgbmVhcmJ5IGF2YWlsYWJpbGl0eSBvZiBmb29kIChub3Rp
Y2UgdGhlIGxhY2sgb2YgYSDigJxPTUcgd2hlcmUgY2FuIEkgZ2V0IGEgZ3JhYi1hbmQtZ28gc2Fu
ZHdpY2jigJ0gdGhyZWFkIGluIDk4YXR0ZW5kZWVzKSBhbmQgaW4gdGVybXMgb2YgdGhlIGF2YWls
YWJpbGl0eSBvZiBuZWFyYnkgbG93LWNvc3QgaG90ZWxzLiBBbmQgeWVzLCB0aGUgZmFjdCB0aGF0
IGV2ZXJ5Ym9keSBzcGVha3MgRW5nbGlzaCBhbHNvIGhlbHBzLiBBbmQgZGVzcGl0ZSB3aGF0IHBl
b3BsZSB0aGluayBhYm91dCBjcmltZSwgbm8gSUVURi1lciBldmVyIGdvdCBzaG90IGluIHRoZSBV
UyBkdXJpbmcgSUVURiB3ZWVrLCBidXQgZXZlcnkgdGltZSB3ZSBtZWV0IGluIEV1cm9wZSBzb21l
IG9mIHVzIHdpbGwgZ2V0IHRoZWlyIHBvY2tldHMgcGlja2VkLg0KDQpGb3IgbWUsIFVTIG1lZXRp
bmdzIChDYW5hZGHigJlzIE9LIHRvbykgYXJlIG1vcmUgY29udmVuaWVudCBkZXNwaXRlIHRoZSBs
b25nLCB0b3J0dW91cyBmbGlnaHQuIFBlb3BsZSBoYXZlIGJlZW4gZ3J1bWJsaW5nIGFib3V0IFVT
IGVudHJ5IHByb2NlZHVyZSBmb3IgeWVhcnMgYW5kIHdpdGggZ29vZCByZWFzb24uIEJ1dCBvdmVy
YWxsIFVTIG1lZXRpbmdzIGFyZSBzaW1wbHkgbW9yZSBjb252ZW5pZW50LiBZTU1WDQoNCllvYXYN
Cg0K

--_000_AM4PR0401MB2241DCA8589E952E278705A6BD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <EB8148E73A94BC4DA53B7977E0544455@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFj
ayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyPGJyPg0KRnJvbTogS2hhbGVkIE9t
YXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpUbzogWW9hdiBOaXIgPHluaXIu
aWV0ZkBnbWFpbC5jb20+PGJyPg0KQ0M6IDxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlv
biI+DQo8YmxvY2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDti
b3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NClJlZ2FyZGluZyB2
aXNhIGFuZCBlbnRyeSwgdGhlcmUgd2lsbCBiZSBubyBjb21wbGljYXRpb25zIGVzcGVjaWFsbHkg
Zm9yIHBlb3BsZSBsaWtlIHlvdSwgSSBtZWFuIHNjaWVudGlzdHMgd2hvIGFyZSBjb21pbmcgdG8g
aGVsZCBhIHRlY2huaWNhbCBtZWV0aW5nLCBpJ20gc3VyZSB0aGVyZSB3aWxsIGJlIG5vIHByb2Js
ZW0gZm9yIGFsbCBzbyB0aGlzIGlzc3VlIGNhbiBiZSBpZ25vcmVkIChubyByYWNpc20gaGVyZSks
IGJ1dCBvdXRzaWRlIHRoZSBtZWV0aW5nDQogc2VjdXJpdHkgaXMgeW91ciBvd24gcmVzcG9uc2li
aWx0eS4NCjxkaXYgY2xhc3M9InF1b3RlIiBzdHlsZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0K
PGJyPg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJl
OiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMjxi
cj4NCkZyb206IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PGJyPg0K
VG86IFlvYXYgTmlyIDx5bmlyLmlldGZAZ21haWwuY29tPjxicj4NCkNDOiBpZXRmIDxpZXRmQGll
dGYub3JnPjxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8YmxvY2txdW90ZSBj
bGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2Nj
YyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NClNvbWV0aGluZyBlbHNlIHRvIGFkZCwgQ2Fpcm8g
YW5kIEdpemEgYXJlIHNvIGJpZyBnb3Zlcm5vcmF0ZXMsIGFuZCBuZWFyIGVhY2ggb3RoZXJzLCBj
b250YWluaW5nIGRvemVucyBvZiBjaXRpZXMsIEkgcmVtZW1iZXIgSSBhdHRlbmRlZCBhbiBldmVu
dCBtYWRlIGJ5IEFmcmluaWMgYW5kIHJlYWxseSB0aGV5IG1hZGUgYSBnb29kIGNob2ljZSBpbiBz
ZWxlY3RpbmcgdGhlIGhvdGVsIGFuZCBjaXR5LCBxdWl0ZSBhcmVhIGFuZCBub3QgZmFyIGZyb20N
CiBvdGhlciBoaXN0b3JpY2FsIG9yIG1vZGVybiBjaXRpZXMsIGl0IHdhcyAyMCBtaW51dGVzIHRv
IGdvIHRvIHRoZSBweXJhbWlkcyBmb3IgZXhhbXBsZSAoYW5kIG9mIGNvdXJzZSB3aXRoIGlnbm9y
aW5nIHRyYWZmaWMgYmVjYXVzZSBpdCBkZXBlbmRzIG9uIHdoZW4gYW5kIHdoZXJlIHRvIGdvKS4N
CjxkaXYgY2xhc3M9InF1b3RlIiBzdHlsZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0K
LS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBVcGRh
dGUgb24gZmVlZGJhY2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMjxicj4NCkZy
b206IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PGJyPg0KVG86IFlv
YXYgTmlyIDx5bmlyLmlldGZAZ21haWwuY29tPjxicj4NCkNDOiBpZXRmIDxpZXRmQGlldGYub3Jn
Pjxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8YmxvY2txdW90ZSBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xp
ZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCkkgcmVjb21tZW5kIEVneXB0IGJlY2F1c2UgaXQgaXMgYXQg
dGhlIGNlbnRlciwgd2lsbCBub3QgYmUgc28gbG9uZyBmb3IgYW55b25lLCBhbHNvLCB3ZWF0aGVy
IGlzIGFuIGltcG9ydGFudCBmYWN0b3IsIGFuZCBmb3IgdGhvc2Ugd2hvIHdvdWxkIGxpa2UgdG8g
dmlzaXQgaGlzdG9yaWNhbCBwbGFjZXMgc2hvdWxkIGZvY3VzIG1vcmUgYWJvdXQgaG93IHRvIGdv
IGFuZCB3aGF0IHRvIHdlYXIsIHRoZXJlIGFyZSBtb2Rlcm4gY2l0aWVzIGFuZCBvbGQNCiBjaXRp
ZXMsIHRoZXJlIGlzIGEgYmlnIGRpZmZlcmVuY2UsIG1hbnkgdG91cmlzdHMgaGVyZSB3aXRoIGFs
bCBkaWZmZXJlbnQgc3R5bGVzLCBhbmQgb2YgY291cnNlIG5vIG9uZSB3aWxsIGRpc3Jlc3BlY3Qg
cG9lcGxlIGhlcmUgc28gaGUvc2hlIHdpbGwgZ2V0IGluIHRyb3VibGUuPGJyPg0KPGJyPg0KQnV0
IHJlZ2FyZGluZyBDYW5hZGEsIGZ1bGwgcmVzcGVjdCB0byB0aG9zZSBwZW9wbGUgYW5kIHRoZXkg
d2lsbCBiZSBtb3JlIHRoYW4gd2VsY29tZWQgaGVyZS48YnI+DQo8YnI+DQpSZWdhcmRzLA0KPGRp
diBjbGFzcz0icXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0t
LS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IFVwZGF0ZSBv
biBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyPGJyPg0KRnJvbTog
WW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFpbC5jb20+PGJyPg0KVG86IFN0ZXBoZW4gRmFycmVsbCA8
c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZT48YnI+DQpDQzogSUFPQyBMaXN0IDxpYW9jQGlldGYu
b3JnPixJRVRGIDxpZXRmQGlldGYub3JnPjxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlv
biI+DQo8YmxvY2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDti
b3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCk9uIDEzIEFwciAy
MDE3LCBhdCAzOjAwLCBTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW4uZmFycmVsbEBjcy50Y2QuaWU+
d3JvdGU6PGJyPg0KPGJyPg0KPGJyPg0KJmd0OyBJIGRvIG5vdCByZWNhbGwgdGhlIG9wcG9zaXRl
IG9uIHRoZSBsaXN0LCBpLmUuIHNvbWVvbmUgYWRhbWFudGx5PGJyPg0KJmd0OyBhcmd1aW5nIHRo
YXQgd2Ugb3VnaHQgY29udGludWUgdG8gbWVldCBpbiB0aGUgVVMuIFRoZXJlIHdlcmUgc29tZTxi
cj4NCiZndDsgbWFpbHMgdGhhdCBJJ2Qgc2F5IG1heWJlIHdlYWtseSBhcmd1ZWQgZm9yIGNvbnRp
bnVlZCBVUyBtZWV0aW5nczxicj4NCiZndDsgaW4gdGhlIHJlbGV2YW50IHRpbWVmcmFtZS4gQnV0
IG5vdGhpbmcgYXBwcm9hY2hpbmcgYWRhbWFudC48YnI+DQo8YnI+DQpXZWxsIGF0IHRoaXMgcG9p
bnQgYXJndWluZyBmb3IgbW9yZSBVUyBtZWV0aW5ncyBiZWNhdXNlIEkgaGFkIG5vIHRyb3VibGUg
b2J0YWluaW5nIGEgdmlzYSBhbmQgZW50ZXJpbmcgdGhlIFVTIGlzIHRoZSBlcXVpdmFsZW50IG9m
IHN0YXRpbmcgdGhhdCBJ4oCZbSBhIHdoaXRlIGd1eSBhbmQgSeKAmW0gbm90IGZlZWxpbmcgYW55
IHJhY2lzbSBvciBzZXhpc20uPGJyPg0KPGJyPg0KTW9yZSB0byB0aGUgcG9pbnQsIHByZXR0eSBt
dWNoIGFsbCBVUyB2ZW51ZXMgd29yayBvdXQgYmV0dGVyIHRoYW4gcHJldHR5IG11Y2ggYW55IEV1
cm9wZWFuIGxldCBhbG9uZSBBc2lhbiB2ZW51ZXMsIHdlaXJkbHkgc2hhcGVkIHJvb21zIG5vdHdp
dGhzdGFuZGluZy4gTG9uZG9uIGFuZCBQYXJpcyBjb21lIGNsb3NlLiBCZXJsaW4gYW5kIFByYWd1
ZSBkb27igJl0LiBUaGlzIGlzIGluIHRlcm1zIG9mIG5lYXJieSBhdmFpbGFiaWxpdHkgb2YgZm9v
ZCAobm90aWNlDQogdGhlIGxhY2sgb2YgYSDigJxPTUcgd2hlcmUgY2FuIEkgZ2V0IGEgZ3JhYi1h
bmQtZ28gc2FuZHdpY2jigJ0gdGhyZWFkIGluIDk4YXR0ZW5kZWVzKSBhbmQgaW4gdGVybXMgb2Yg
dGhlIGF2YWlsYWJpbGl0eSBvZiBuZWFyYnkgbG93LWNvc3QgaG90ZWxzLiBBbmQgeWVzLCB0aGUg
ZmFjdCB0aGF0IGV2ZXJ5Ym9keSBzcGVha3MgRW5nbGlzaCBhbHNvIGhlbHBzLiBBbmQgZGVzcGl0
ZSB3aGF0IHBlb3BsZSB0aGluayBhYm91dCBjcmltZSwgbm8gSUVURi1lcg0KIGV2ZXIgZ290IHNo
b3QgaW4gdGhlIFVTIGR1cmluZyBJRVRGIHdlZWssIGJ1dCBldmVyeSB0aW1lIHdlIG1lZXQgaW4g
RXVyb3BlIHNvbWUgb2YgdXMgd2lsbCBnZXQgdGhlaXIgcG9ja2V0cyBwaWNrZWQuPGJyPg0KPGJy
Pg0KRm9yIG1lLCBVUyBtZWV0aW5ncyAoQ2FuYWRh4oCZcyBPSyB0b28pIGFyZSBtb3JlIGNvbnZl
bmllbnQgZGVzcGl0ZSB0aGUgbG9uZywgdG9ydHVvdXMgZmxpZ2h0LiBQZW9wbGUgaGF2ZSBiZWVu
IGdydW1ibGluZyBhYm91dCBVUyBlbnRyeSBwcm9jZWR1cmUgZm9yIHllYXJzIGFuZCB3aXRoIGdv
b2QgcmVhc29uLiBCdXQgb3ZlcmFsbCBVUyBtZWV0aW5ncyBhcmUgc2ltcGx5IG1vcmUgY29udmVu
aWVudC4gWU1NVjxicj4NCjxicj4NCllvYXY8YnI+DQo8YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB2241DCA8589E952E278705A6BD020AM4PR0401MB2241_--


From nobody Thu Apr 13 00:05:33 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC8112EAC3 for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 00:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 VjrtD_gPUWDz for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 00:05:30 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-oln040092072073.outbound.protection.outlook.com [40.92.72.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4329A12EB53 for <ietf@ietf.org>; Thu, 13 Apr 2017 00:05:30 -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; bh=+ISH3vxPXloHiO7fwVp8OaKJ34SzvGUmrGFj7XXxuSQ=; b=JZYkR/wR4JS4nbYfpbqZgf8ZBqLdPq2BeCvek5J4PFMADvGElj7HSHb9G/SLa5YvGTtJP/nFbnuvHGssmVglvTCovvYlMI8mf0e1M0mIXiJTRaWJ17lxBUzoQgJNRWEBcMGsCYMQsLa0+u40iI2Kc0rOmAsHPX7IUUtMvHIUSqkvjK0wDVIpmESJSaHZTW5AWr5dSa7Midvd+2Dfu+Lp0w0j9ccMgp6KEa1/HgiG9UzqDXG6L9SJu2+rim6GJOcbBFuurPGZIwgwbO6bYICO43psZz4UD3PnlJrl5/EDH/JvDzSNZABLdlTh5nOl+43llee6PkUajPLuylJ5dB1GtA==
Received: from AM5EUR03FT008.eop-EUR03.prod.protection.outlook.com (10.152.16.55) by AM5EUR03HT170.eop-EUR03.prod.protection.outlook.com (10.152.17.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Thu, 13 Apr 2017 07:05:28 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.59) by AM5EUR03FT008.mail.protection.outlook.com (10.152.16.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Thu, 13 Apr 2017 07:05:28 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1019.026; Thu, 13 Apr 2017 07:05:28 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+kD4XIpMDBpUUKi5tFZaQ2HSw==
Date: Thu, 13 Apr 2017 07:05:27 +0000
Message-ID: <AM4PR0401MB224136E039EC816F717B0065BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241DCA8589E952E278705A6BD020@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:1A03C9BBCF884C0FA05723F8842D093E61F32911E18AC4B4C6CF98816C158F15; UpperCasedChecksum:6F3C237FCB2D67417B90B673A60711E909E355096FEC2DCEB4F1512C296B15D5; SizeAsReceived:7852; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT170; 5:GcQRTHRnUL6vghsxdCxvYRdXE94g0aTy7hgchYML4VBZ7Y/3kKmsFEjJfU5W4+qsceFDzgymIYLuEZZa+MnBHSkRNyJBGcbwLYKEIcygNBDDTy77+geO+2AIFY4sppK8N8uybiD2aUrVnFGWFzz3LWG88N6kiV4VE6y1ldkNCXI=; 24:NOAiSz11qxJNXOUcPWOBRD8KQHjjMjXMXsbz281zRZD3L8+Yzwh/4zQzWSv2SQbIvmyyhDwC0Cu6QGlBb4jGs5omG9nLtx2mxgEqrdAgJlM=; 7:Uri+mayVzGfteh17gz2uHJNiKt63l48J4waBhljZ5nhcdaQuFK/ksMD2/WqO3fK+TQnyWnjpuO1OSLDlHBB3X18zBGUmNpwmW9u5izdY2EXYE9OLGFev08XOv1K5aoGZTVsAkJQXEKSyJKDrTVPlSBVbzV4tLmCLgDm4dxEBBpa3pcRr3Qhl3hrbdKWAr0l90Y/1pqzDm70X878IQ1FrXswvfhWnD8Jn+YBTtaGAIuKqjngZPsmWDESZR0yERiCQz+2MxKcAXuliBJncZrLvXAlR5nVcabqlYVdRo4TL4Os8SKnt5YIiQPAm0bjcfu9K
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT170; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 48fbe6c9-a4fa-4dd3-8b4a-08d4823b769c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:AM5EUR03HT170; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT170; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT170; 
x-forefront-prvs: 02760F0D1C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB224136E039EC816F717B0065BD020AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 07:05:27.9902 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT170
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mE1k1QlqNcZC8H3TveroIIUwHEU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 07:05:32 -0000

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

SWYgeW91IGRlY2lkZWQgdG8gY2hvb3NlIEVneXB0IGZvciBhbiBJRVRGIG1lZXRpbmcsIHBsZWFz
ZSBpbmZvcm0gbWUgc28gSSBjYW4gcHJlcGFyZSB0byBwYXJ0aWNpcGF0ZSByZW1vdGVseSA6LSkN
Cg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBGdzogVXBk
YXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206
IEtoYWxlZCBPbWFyDQpUbzogaWV0Zg0KQ0M6DQoNCg0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1l
c3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMtYmFz
ZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMg0KRnJvbTogS2hhbGVkIE9tYXINClRvOiBZb2F2IE5p
cg0KQ0M6DQoNCg0KUmVnYXJkaW5nIHZpc2EgYW5kIGVudHJ5LCB0aGVyZSB3aWxsIGJlIG5vIGNv
bXBsaWNhdGlvbnMgZXNwZWNpYWxseSBmb3IgcGVvcGxlIGxpa2UgeW91LCBJIG1lYW4gc2NpZW50
aXN0cyB3aG8gYXJlIGNvbWluZyB0byBoZWxkIGEgdGVjaG5pY2FsIG1lZXRpbmcsIGknbSBzdXJl
IHRoZXJlIHdpbGwgYmUgbm8gcHJvYmxlbSBmb3IgYWxsIHNvIHRoaXMgaXNzdWUgY2FuIGJlIGln
bm9yZWQgKG5vIHJhY2lzbSBoZXJlKSwgYnV0IG91dHNpZGUgdGhlIG1lZXRpbmcgc2VjdXJpdHkg
aXMgeW91ciBvd24gcmVzcG9uc2liaWx0eS4NCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1l
ZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206IEtoYWxlZCBPbWFyDQpUbzogWW9hdiBOaXINCkND
OiBpZXRmDQoNCg0KU29tZXRoaW5nIGVsc2UgdG8gYWRkLCBDYWlybyBhbmQgR2l6YSBhcmUgc28g
YmlnIGdvdmVybm9yYXRlcywgYW5kIG5lYXIgZWFjaCBvdGhlcnMsIGNvbnRhaW5pbmcgZG96ZW5z
IG9mIGNpdGllcywgSSByZW1lbWJlciBJIGF0dGVuZGVkIGFuIGV2ZW50IG1hZGUgYnkgQWZyaW5p
YyBhbmQgcmVhbGx5IHRoZXkgbWFkZSBhIGdvb2QgY2hvaWNlIGluIHNlbGVjdGluZyB0aGUgaG90
ZWwgYW5kIGNpdHksIHF1aXRlIGFyZWEgYW5kIG5vdCBmYXIgZnJvbSBvdGhlciBoaXN0b3JpY2Fs
IG9yIG1vZGVybiBjaXRpZXMsIGl0IHdhcyAyMCBtaW51dGVzIHRvIGdvIHRvIHRoZSBweXJhbWlk
cyBmb3IgZXhhbXBsZSAoYW5kIG9mIGNvdXJzZSB3aXRoIGlnbm9yaW5nIHRyYWZmaWMgYmVjYXVz
ZSBpdCBkZXBlbmRzIG9uIHdoZW4gYW5kIHdoZXJlIHRvIGdvKS4NCg0KDQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9u
IFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCkZyb206IEtoYWxlZCBPbWFyDQpUbzog
WW9hdiBOaXINCkNDOiBpZXRmDQoNCg0KSSByZWNvbW1lbmQgRWd5cHQgYmVjYXVzZSBpdCBpcyBh
dCB0aGUgY2VudGVyLCB3aWxsIG5vdCBiZSBzbyBsb25nIGZvciBhbnlvbmUsIGFsc28sIHdlYXRo
ZXIgaXMgYW4gaW1wb3J0YW50IGZhY3RvciwgYW5kIGZvciB0aG9zZSB3aG8gd291bGQgbGlrZSB0
byB2aXNpdCBoaXN0b3JpY2FsIHBsYWNlcyBzaG91bGQgZm9jdXMgbW9yZSBhYm91dCBob3cgdG8g
Z28gYW5kIHdoYXQgdG8gd2VhciwgdGhlcmUgYXJlIG1vZGVybiBjaXRpZXMgYW5kIG9sZCBjaXRp
ZXMsIHRoZXJlIGlzIGEgYmlnIGRpZmZlcmVuY2UsIG1hbnkgdG91cmlzdHMgaGVyZSB3aXRoIGFs
bCBkaWZmZXJlbnQgc3R5bGVzLCBhbmQgb2YgY291cnNlIG5vIG9uZSB3aWxsIGRpc3Jlc3BlY3Qg
cG9lcGxlIGhlcmUgc28gaGUvc2hlIHdpbGwgZ2V0IGluIHRyb3VibGUuDQoNCkJ1dCByZWdhcmRp
bmcgQ2FuYWRhLCBmdWxsIHJlc3BlY3QgdG8gdGhvc2UgcGVvcGxlIGFuZCB0aGV5IHdpbGwgYmUg
bW9yZSB0aGFuIHdlbGNvbWVkIGhlcmUuDQoNClJlZ2FyZHMsDQoNCg0KLS0tLS0tLS0gT3JpZ2lu
YWwgTWVzc2FnZSAtLS0tLS0tLQ0KU3ViamVjdDogUmU6IFVwZGF0ZSBvbiBmZWVkYmFjayBvbiBV
Uy1iYXNlZCBtZWV0aW5ncywgYW5kIElFVEYgMTAyDQpGcm9tOiBZb2F2IE5pcg0KVG86IFN0ZXBo
ZW4gRmFycmVsbA0KQ0M6IElBT0MgTGlzdCAsSUVURg0KDQoNCk9uIDEzIEFwciAyMDE3LCBhdCAz
OjAwLCBTdGVwaGVuIEZhcnJlbGwgd3JvdGU6DQoNCg0KPiBJIGRvIG5vdCByZWNhbGwgdGhlIG9w
cG9zaXRlIG9uIHRoZSBsaXN0LCBpLmUuIHNvbWVvbmUgYWRhbWFudGx5DQo+IGFyZ3VpbmcgdGhh
dCB3ZSBvdWdodCBjb250aW51ZSB0byBtZWV0IGluIHRoZSBVUy4gVGhlcmUgd2VyZSBzb21lDQo+
IG1haWxzIHRoYXQgSSdkIHNheSBtYXliZSB3ZWFrbHkgYXJndWVkIGZvciBjb250aW51ZWQgVVMg
bWVldGluZ3MNCj4gaW4gdGhlIHJlbGV2YW50IHRpbWVmcmFtZS4gQnV0IG5vdGhpbmcgYXBwcm9h
Y2hpbmcgYWRhbWFudC4NCg0KV2VsbCBhdCB0aGlzIHBvaW50IGFyZ3VpbmcgZm9yIG1vcmUgVVMg
bWVldGluZ3MgYmVjYXVzZSBJIGhhZCBubyB0cm91YmxlIG9idGFpbmluZyBhIHZpc2EgYW5kIGVu
dGVyaW5nIHRoZSBVUyBpcyB0aGUgZXF1aXZhbGVudCBvZiBzdGF0aW5nIHRoYXQgSeKAmW0gYSB3
aGl0ZSBndXkgYW5kIEnigJltIG5vdCBmZWVsaW5nIGFueSByYWNpc20gb3Igc2V4aXNtLg0KDQpN
b3JlIHRvIHRoZSBwb2ludCwgcHJldHR5IG11Y2ggYWxsIFVTIHZlbnVlcyB3b3JrIG91dCBiZXR0
ZXIgdGhhbiBwcmV0dHkgbXVjaCBhbnkgRXVyb3BlYW4gbGV0IGFsb25lIEFzaWFuIHZlbnVlcywg
d2VpcmRseSBzaGFwZWQgcm9vbXMgbm90d2l0aHN0YW5kaW5nLiBMb25kb24gYW5kIFBhcmlzIGNv
bWUgY2xvc2UuIEJlcmxpbiBhbmQgUHJhZ3VlIGRvbuKAmXQuIFRoaXMgaXMgaW4gdGVybXMgb2Yg
bmVhcmJ5IGF2YWlsYWJpbGl0eSBvZiBmb29kIChub3RpY2UgdGhlIGxhY2sgb2YgYSDigJxPTUcg
d2hlcmUgY2FuIEkgZ2V0IGEgZ3JhYi1hbmQtZ28gc2FuZHdpY2jigJ0gdGhyZWFkIGluIDk4YXR0
ZW5kZWVzKSBhbmQgaW4gdGVybXMgb2YgdGhlIGF2YWlsYWJpbGl0eSBvZiBuZWFyYnkgbG93LWNv
c3QgaG90ZWxzLiBBbmQgeWVzLCB0aGUgZmFjdCB0aGF0IGV2ZXJ5Ym9keSBzcGVha3MgRW5nbGlz
aCBhbHNvIGhlbHBzLiBBbmQgZGVzcGl0ZSB3aGF0IHBlb3BsZSB0aGluayBhYm91dCBjcmltZSwg
bm8gSUVURi1lciBldmVyIGdvdCBzaG90IGluIHRoZSBVUyBkdXJpbmcgSUVURiB3ZWVrLCBidXQg
ZXZlcnkgdGltZSB3ZSBtZWV0IGluIEV1cm9wZSBzb21lIG9mIHVzIHdpbGwgZ2V0IHRoZWlyIHBv
Y2tldHMgcGlja2VkLg0KDQpGb3IgbWUsIFVTIG1lZXRpbmdzIChDYW5hZGHigJlzIE9LIHRvbykg
YXJlIG1vcmUgY29udmVuaWVudCBkZXNwaXRlIHRoZSBsb25nLCB0b3J0dW91cyBmbGlnaHQuIFBl
b3BsZSBoYXZlIGJlZW4gZ3J1bWJsaW5nIGFib3V0IFVTIGVudHJ5IHByb2NlZHVyZSBmb3IgeWVh
cnMgYW5kIHdpdGggZ29vZCByZWFzb24uIEJ1dCBvdmVyYWxsIFVTIG1lZXRpbmdzIGFyZSBzaW1w
bHkgbW9yZSBjb252ZW5pZW50LiBZTU1WDQoNCllvYXYNCg0K

--_000_AM4PR0401MB224136E039EC816F717B0065BD020AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <13CA418F8913E6459EC7C9A4295C9074@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSWYgeW91IGRlY2lk
ZWQgdG8gY2hvb3NlIEVneXB0IGZvciBhbiBJRVRGIG1lZXRpbmcsIHBsZWFzZSBpbmZvcm0gbWUg
c28gSSBjYW4gcHJlcGFyZSB0byBwYXJ0aWNpcGF0ZSByZW1vdGVseSA6LSkNCjxkaXYgY2xhc3M9
InF1b3RlIiBzdHlsZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IEZ3OiBVcGRhdGUgb24gZmVlZGJh
Y2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMjxicj4NCkZyb206IEtoYWxlZCBP
bWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PGJyPg0KVG86IGlldGYgPGlldGZAaWV0
Zi5vcmc+PGJyPg0KQ0M6IDxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8Ymxv
Y2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVm
dDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgY2xhc3M9InF1b3RlIiBz
dHlsZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVz
c2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBVcGRhdGUgb24gZmVlZGJhY2sgb24gVVMt
YmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMjxicj4NCkZyb206IEtoYWxlZCBPbWFyIDxlbmcu
a2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PGJyPg0KVG86IFlvYXYgTmlyIDx5bmlyLmlldGZAZ21h
aWwuY29tPjxicj4NCkNDOiA8YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJs
b2NrcXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxl
ZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpSZWdhcmRpbmcgdmlzYSBhbmQg
ZW50cnksIHRoZXJlIHdpbGwgYmUgbm8gY29tcGxpY2F0aW9ucyBlc3BlY2lhbGx5IGZvciBwZW9w
bGUgbGlrZSB5b3UsIEkgbWVhbiBzY2llbnRpc3RzIHdobyBhcmUgY29taW5nIHRvIGhlbGQgYSB0
ZWNobmljYWwgbWVldGluZywgaSdtIHN1cmUgdGhlcmUgd2lsbCBiZSBubyBwcm9ibGVtIGZvciBh
bGwgc28gdGhpcyBpc3N1ZSBjYW4gYmUgaWdub3JlZCAobm8gcmFjaXNtIGhlcmUpLCBidXQgb3V0
c2lkZSB0aGUgbWVldGluZw0KIHNlY3VyaXR5IGlzIHlvdXIgb3duIHJlc3BvbnNpYmlsdHkuDQo8
ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4NCjxicj4NCi0t
LS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogVXBkYXRl
IG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDI8YnI+DQpGcm9t
OiBLaGFsZWQgT21hciA8ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPjxicj4NClRvOiBZb2F2
IE5pciA8eW5pci5pZXRmQGdtYWlsLmNvbT48YnI+DQpDQzogaWV0ZiA8aWV0ZkBpZXRmLm9yZz48
YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1
b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7
cGFkZGluZy1sZWZ0OjFleCI+DQpTb21ldGhpbmcgZWxzZSB0byBhZGQsIENhaXJvIGFuZCBHaXph
IGFyZSBzbyBiaWcgZ292ZXJub3JhdGVzLCBhbmQgbmVhciBlYWNoIG90aGVycywgY29udGFpbmlu
ZyBkb3plbnMgb2YgY2l0aWVzLCBJIHJlbWVtYmVyIEkgYXR0ZW5kZWQgYW4gZXZlbnQgbWFkZSBi
eSBBZnJpbmljIGFuZCByZWFsbHkgdGhleSBtYWRlIGEgZ29vZCBjaG9pY2UgaW4gc2VsZWN0aW5n
IHRoZSBob3RlbCBhbmQgY2l0eSwgcXVpdGUgYXJlYSBhbmQgbm90IGZhciBmcm9tDQogb3RoZXIg
aGlzdG9yaWNhbCBvciBtb2Rlcm4gY2l0aWVzLCBpdCB3YXMgMjAgbWludXRlcyB0byBnbyB0byB0
aGUgcHlyYW1pZHMgZm9yIGV4YW1wbGUgKGFuZCBvZiBjb3Vyc2Ugd2l0aCBpZ25vcmluZyB0cmFm
ZmljIGJlY2F1c2UgaXQgZGVwZW5kcyBvbiB3aGVuIGFuZCB3aGVyZSB0byBnbykuDQo8ZGl2IGNs
YXNzPSJxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0t
IE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZl
ZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDI8YnI+DQpGcm9tOiBLaGFs
ZWQgT21hciA8ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPjxicj4NClRvOiBZb2F2IE5pciA8
eW5pci5pZXRmQGdtYWlsLmNvbT48YnI+DQpDQzogaWV0ZiA8aWV0ZkBpZXRmLm9yZz48YnI+DQo8
YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1b3RlIiBz
dHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGlu
Zy1sZWZ0OjFleCI+DQpJIHJlY29tbWVuZCBFZ3lwdCBiZWNhdXNlIGl0IGlzIGF0IHRoZSBjZW50
ZXIsIHdpbGwgbm90IGJlIHNvIGxvbmcgZm9yIGFueW9uZSwgYWxzbywgd2VhdGhlciBpcyBhbiBp
bXBvcnRhbnQgZmFjdG9yLCBhbmQgZm9yIHRob3NlIHdobyB3b3VsZCBsaWtlIHRvIHZpc2l0IGhp
c3RvcmljYWwgcGxhY2VzIHNob3VsZCBmb2N1cyBtb3JlIGFib3V0IGhvdyB0byBnbyBhbmQgd2hh
dCB0byB3ZWFyLCB0aGVyZSBhcmUgbW9kZXJuIGNpdGllcyBhbmQgb2xkDQogY2l0aWVzLCB0aGVy
ZSBpcyBhIGJpZyBkaWZmZXJlbmNlLCBtYW55IHRvdXJpc3RzIGhlcmUgd2l0aCBhbGwgZGlmZmVy
ZW50IHN0eWxlcywgYW5kIG9mIGNvdXJzZSBubyBvbmUgd2lsbCBkaXNyZXNwZWN0IHBvZXBsZSBo
ZXJlIHNvIGhlL3NoZSB3aWxsIGdldCBpbiB0cm91YmxlLjxicj4NCjxicj4NCkJ1dCByZWdhcmRp
bmcgQ2FuYWRhLCBmdWxsIHJlc3BlY3QgdG8gdGhvc2UgcGVvcGxlIGFuZCB0aGV5IHdpbGwgYmUg
bW9yZSB0aGFuIHdlbGNvbWVkIGhlcmUuPGJyPg0KPGJyPg0KUmVnYXJkcywNCjxkaXYgY2xhc3M9
InF1b3RlIiBzdHlsZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBVcGRhdGUgb24gZmVlZGJh
Y2sgb24gVVMtYmFzZWQgbWVldGluZ3MsIGFuZCBJRVRGIDEwMjxicj4NCkZyb206IFlvYXYgTmly
IDx5bmlyLmlldGZAZ21haWwuY29tPjxicj4NClRvOiBTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW4u
ZmFycmVsbEBjcy50Y2QuaWU+PGJyPg0KQ0M6IElBT0MgTGlzdCA8aWFvY0BpZXRmLm9yZz4sSUVU
RiA8aWV0ZkBpZXRmLm9yZz48YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJs
b2NrcXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxl
ZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpPbiAxMyBBcHIgMjAxNywgYXQg
MzowMCwgU3RlcGhlbiBGYXJyZWxsIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPndyb3RlOjxi
cj4NCjxicj4NCjxicj4NCiZndDsgSSBkbyBub3QgcmVjYWxsIHRoZSBvcHBvc2l0ZSBvbiB0aGUg
bGlzdCwgaS5lLiBzb21lb25lIGFkYW1hbnRseTxicj4NCiZndDsgYXJndWluZyB0aGF0IHdlIG91
Z2h0IGNvbnRpbnVlIHRvIG1lZXQgaW4gdGhlIFVTLiBUaGVyZSB3ZXJlIHNvbWU8YnI+DQomZ3Q7
IG1haWxzIHRoYXQgSSdkIHNheSBtYXliZSB3ZWFrbHkgYXJndWVkIGZvciBjb250aW51ZWQgVVMg
bWVldGluZ3M8YnI+DQomZ3Q7IGluIHRoZSByZWxldmFudCB0aW1lZnJhbWUuIEJ1dCBub3RoaW5n
IGFwcHJvYWNoaW5nIGFkYW1hbnQuPGJyPg0KPGJyPg0KV2VsbCBhdCB0aGlzIHBvaW50IGFyZ3Vp
bmcgZm9yIG1vcmUgVVMgbWVldGluZ3MgYmVjYXVzZSBJIGhhZCBubyB0cm91YmxlIG9idGFpbmlu
ZyBhIHZpc2EgYW5kIGVudGVyaW5nIHRoZSBVUyBpcyB0aGUgZXF1aXZhbGVudCBvZiBzdGF0aW5n
IHRoYXQgSeKAmW0gYSB3aGl0ZSBndXkgYW5kIEnigJltIG5vdCBmZWVsaW5nIGFueSByYWNpc20g
b3Igc2V4aXNtLjxicj4NCjxicj4NCk1vcmUgdG8gdGhlIHBvaW50LCBwcmV0dHkgbXVjaCBhbGwg
VVMgdmVudWVzIHdvcmsgb3V0IGJldHRlciB0aGFuIHByZXR0eSBtdWNoIGFueSBFdXJvcGVhbiBs
ZXQgYWxvbmUgQXNpYW4gdmVudWVzLCB3ZWlyZGx5IHNoYXBlZCByb29tcyBub3R3aXRoc3RhbmRp
bmcuIExvbmRvbiBhbmQgUGFyaXMgY29tZSBjbG9zZS4gQmVybGluIGFuZCBQcmFndWUgZG9u4oCZ
dC4gVGhpcyBpcyBpbiB0ZXJtcyBvZiBuZWFyYnkgYXZhaWxhYmlsaXR5IG9mIGZvb2QgKG5vdGlj
ZQ0KIHRoZSBsYWNrIG9mIGEg4oCcT01HIHdoZXJlIGNhbiBJIGdldCBhIGdyYWItYW5kLWdvIHNh
bmR3aWNo4oCdIHRocmVhZCBpbiA5OGF0dGVuZGVlcykgYW5kIGluIHRlcm1zIG9mIHRoZSBhdmFp
bGFiaWxpdHkgb2YgbmVhcmJ5IGxvdy1jb3N0IGhvdGVscy4gQW5kIHllcywgdGhlIGZhY3QgdGhh
dCBldmVyeWJvZHkgc3BlYWtzIEVuZ2xpc2ggYWxzbyBoZWxwcy4gQW5kIGRlc3BpdGUgd2hhdCBw
ZW9wbGUgdGhpbmsgYWJvdXQgY3JpbWUsIG5vIElFVEYtZXINCiBldmVyIGdvdCBzaG90IGluIHRo
ZSBVUyBkdXJpbmcgSUVURiB3ZWVrLCBidXQgZXZlcnkgdGltZSB3ZSBtZWV0IGluIEV1cm9wZSBz
b21lIG9mIHVzIHdpbGwgZ2V0IHRoZWlyIHBvY2tldHMgcGlja2VkLjxicj4NCjxicj4NCkZvciBt
ZSwgVVMgbWVldGluZ3MgKENhbmFkYeKAmXMgT0sgdG9vKSBhcmUgbW9yZSBjb252ZW5pZW50IGRl
c3BpdGUgdGhlIGxvbmcsIHRvcnR1b3VzIGZsaWdodC4gUGVvcGxlIGhhdmUgYmVlbiBncnVtYmxp
bmcgYWJvdXQgVVMgZW50cnkgcHJvY2VkdXJlIGZvciB5ZWFycyBhbmQgd2l0aCBnb29kIHJlYXNv
bi4gQnV0IG92ZXJhbGwgVVMgbWVldGluZ3MgYXJlIHNpbXBseSBtb3JlIGNvbnZlbmllbnQuIFlN
TVY8YnI+DQo8YnI+DQpZb2F2PGJyPg0KPGJyPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB224136E039EC816F717B0065BD020AM4PR0401MB2241_--


From nobody Thu Apr 13 01:31:00 2017
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A30001317C1; Thu, 13 Apr 2017 01:30:57 -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, 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 lDmXs6wDxIzG; Thu, 13 Apr 2017 01:30:55 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 A055D1317E6; Thu, 13 Apr 2017 01:30:49 -0700 (PDT)
X-AuditID: c6180641-417ff700000058cf-81-58eef0db02e3
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id 92.D4.22735.BD0FEE85; Thu, 13 Apr 2017 05:30:39 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0339.000; Thu, 13 Apr 2017 04:30:44 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Subject: RE: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+YQECjTpLL78USByfjfVB8KHqHCrUkAgAAHYACAAATAAIAAPrVA
Date: Thu, 13 Apr 2017 08:30:44 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
In-Reply-To: <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyuXRPrO79D+8iDLY85bT4dPEOq8W9M9PZ LJ5tnM9i8fHUGyaL6XuvsTuweqztvsrmsWTJTyaPc1O+MwYwR3HZpKTmZJalFunbJXBlzLv1 laWgS6Ti5TTuBsYTwl2MHBwSAiYSD+7IdjFycQgJbGCU+PNyAjuEs5xRYuaJncxdjJwcbAIa EsfurGUESYgInGeUWN48nR0kISzgJLFyey+YLSLgLLGteQcThO0msWnBTBYQm0VAVWLz58ds IDavgK/EgifPWSA2vGGU+DjzGFgRp4CtxIKmG2BFjAJiEt9PrQEbxCwgLnHryXwwW0JAQGLJ nvPMELaoxMvH/1ghbCWJSUvPsYK8wyygKbF+lz5Eq6LElO6H7BB7BSVOznzCMoFRZBaSqbMQ OmYh6ZiFpGMBI8sqRo7S4oKc3HQjw02MwNg4JsHmuINxb6/nIUYBDkYlHt4Fv95GCLEmlhVX 5h5ilOBgVhLhddB9HyHEm5JYWZValB9fVJqTWnyIUZqDRUmc9135hQghgfTEktTs1NSC1CKY LBMHp1QDY9UqvVfN3IlnG9nz7bivCO5S/f1d+1+Y/YUl3hbbbjuc8Avb9fP7pWexN7dVMGtd twpSNJo8q6fCVseS3fe+aNvKx8lL3HiPBEi8vHHzq+xmddmTkncMzHxCO5zX8WY9L1K1P1fb 75q5JZct3UDVxPDs1BvxXNEfXk07JRkbFuj4Kfz9xUuZSizFGYmGWsxFxYkAiD2SWYkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QU2hlGi4_fbFcQIvYa0l7KU5GbU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 08:30:58 -0000

U3RlcGhlbiwNCg0KWW91ciBhcmd1bWVudCBzZWVtcyB0byBhc3N1bWUgdGhhdCBwZW9wbGUgc2hv
dWxkIGZlZWwgYSBuZWVkIHRvIHB1YmxpY2x5IGp1c3RpZnkgdGhlaXIgZmVlbGluZ3Mgb24gYW55
IHRvcGljLg0KDQpUaGF0IGlzIHNpbXBseSBub3QgdGhlIGNhc2UuDQoNCi0tDQpFcmljDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmIFttYWlsdG86aWV0Zi1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgU3RlcGhlbiBGYXJyZWxsDQpTZW50OiBkZW4gMTMgYXBy
aWwgMjAxNyAwMjo0NA0KVG86IEpvZWwgTS4gSGFscGVybiA8am1oQGpvZWxoYWxwZXJuLmNvbT47
IGlldGZAaWV0Zi5vcmc7IGlhb2NAaWV0Zi5vcmc7IElFVEYgQW5ub3VuY2VtZW50IExpc3QgPGll
dGYtYW5ub3VuY2VAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9u
IFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQgSUVURiAxMDINCg0KDQpIaXlhLA0KDQpPbiAxMy8wNC8x
NyAwMToyNywgSm9lbCBNLiBIYWxwZXJuIHdyb3RlOg0KPiANCj4gSSB0aGluayB0aGF0IG1hbnkg
b2YgdXMgdGFrZSBpdCBhcyBnaXZlbiB0YWh0IGl0IGlzIGRlc2lyYWJsZSB0byBtZWV0IA0KPiBp
biB0aGUgVVMuDQoNCkkgZG8gbm90IGRvdWJ0IHRoYXQgbWFueSBJRVRGZXJzIGxpa2VseSB0aGlu
ayB0aGF0LiBBbmQgSSBhbG1vc3QgYWdyZWUgd2l0aCBpdC4NCg0KTXkgb25seSBwcm9ibGVtIGlz
IHRoYXQgSSdtIHNhZGx5IG5vIGxvbmdlciBzdXJlIHRoYXQgdGhlIHByZXNlbnQgdGVuc2UgaXMg
Y29ycmVjdCBpbiB5b3VyIHN0YXRlbWVudCwgd2hpY2ggaXMganVzdCBhIHNoYW1lLg0KDQpJIGZ1
bGx5IGFncmVlIHdpdGggeW91ciBzdGF0ZW1lbnQgY2FzdCBpbnRvIHRoZSBwYXN0IHRlbnNlLg0K
DQpJIHJlYWxseSBob3BlIHRoYXQgdGhlIGZ1dHVyZSB0ZW5zZSB2YXJpYW50IHdpbGwgYmUgc29t
ZXRoaW5nIHdpdGggd2hpY2ggSSBjYW4gYWdyZWUuIEF0IHRoZSBtb21lbnQgSSBkbyBub3QgZm9y
IHRoZSByZWFzb25zIHN0YXRlZCAodG8gZG8gd2l0aCB1bnByZWRpY3RhYmlsaXR5KS4NCg0KPiBJ
biBjb250cmFzdCwgSSBhbSBxdWl0ZSBzdXJlIHRoYXQgZm9sa3Mgd2hvIGZlbHQgc3Ryb25nbHkg
dGhhdCB3ZSANCj4gc2hvdWxkIG5vdCBtZWV0IGluIHRoZSBVUyB1bmRlcnN0b29kIHRoYXQgZm9y
IHRoYXQgdG8gaGFwcGVuLCB0aGV5IA0KPiBuZWVkZWQgdG8gbWFrZSB0aGVpciB2b2ljZXMgaGVh
cmQuDQoNClRoYXQncyBhIGZhaXIgcG9pbnQuIEkgdGhpbmsgdGhvdWdoIHRoYXQgaXQgYWxzbyBw
dXRzIG9uIG9udXMgb24gYW55IGZvbGtzIHdobyBhZGFtYW50bHkgdGhpbmsgd2Ugb3VnaHQgY29u
dGludWUgdG8gbWVldCBpbiB0aGUgVVMsIHRvIGFsc28gcHVibGljbHkganVzdGlmeSB0aGF0LCBn
aXZlbiB0aGUgb3Bwb3NpdGUgYXJndW1lbnRzIGFscmVhZHkgdm9pY2VkIG9uIHRoZSBsaXN0LiAo
SSBkbyByZWFsaXNlIHRoZXJlJ3MgYSBkYW5nZXIgdGhlcmUgb2YgZm9sa3MgZ29pbmcgT1RULCBz
byBJIGhvcGUgd2UgYWxsIGltcG9zZSBhIGJpdCBvZiBzZWxmLXJlc3RyYWludCBpZiBtYWtpbmcg
YXJndW1lbnRzIGVpdGhlciB3YXkuKQ0KDQpOb3RlIHRob3VnaCB0aGF0IG15IHF1ZXJ5IHdhcyB3
aXRoIExlc2xpZSdzIGFzc2VydGlvbiB0aGF0IHRoZSBzdXJ2ZXkgcmVzdWx0IGFuZCBsaXN0IHRy
YWZmaWMgcmVmbGVjdGVkIHNpbWlsYXIgbGV2ZWxzIG9mIGFkYW1hbnQgYXNzZXJ0aW9uLg0KKEkg
d2Fzbid0IGRvdWJ0aW5nIHRoYXQgc29tZSBvZiB1cyBhcmUgbGlrZWx5IGFkYW1hbnQgYWJvdXQg
YW55IHJhbmRvbSBvciBub24tcmFuZG9tIHRvcGljOi0pDQoNCkNoZWVycywNClMuDQoNCg==


From nobody Thu Apr 13 01:45:39 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6214A131814; Thu, 13 Apr 2017 01:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=cs.tcd.ie
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 9W4T5YlPZxIJ; Thu, 13 Apr 2017 01:45:29 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBCC5131815; Thu, 13 Apr 2017 01:45:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6A4FCBE8E; Thu, 13 Apr 2017 09:45:26 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSf2YmXMH5Ik; Thu, 13 Apr 2017 09:45:21 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B04AABED5; Thu, 13 Apr 2017 09:45:20 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492073121; bh=g7LoG6Rrh4BtIKZFU2bCA5WB6i3n4f4XBZjv4bc7PPk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=JOTwKX9kf+PWTTlM5y2o7fdW1twsTQWsB+tpx6FBZ2CSfBnO4xO02CIV6cbxtP5aO 5uokES+93Pn25lh4osdivbWWBFnAfW2xAklug2a7ioFRdwOG2HVOdyWkzsVAzu8cQ4 LM8ShYCmdQHSS45gNfC3Gz7Gn+sxDaJ9MgB3cTRg=
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: Eric Gray <eric.gray@ericsson.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie> <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
Date: Thu, 13 Apr 2017 09:45:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GtlTdpAG3odrBB8XSfvCs74tSUPTCI6w2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7ywVvZV48FQq6Bn9U3Qt0QWmQBg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 08:45:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GtlTdpAG3odrBB8XSfvCs74tSUPTCI6w2
Content-Type: multipart/mixed; boundary="I2hqn0pwJN89f9RoErH8BHpMDtSEXIKEq";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Eric Gray <eric.gray@ericsson.com>, "Joel M. Halpern"
 <jmh@joelhalpern.com>, "ietf@ietf.org" <ietf@ietf.org>,
 "iaoc@ietf.org" <iaoc@ietf.org>,
 IETF Announcement List <ietf-announce@ietf.org>
Message-ID: <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
 <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
 <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com>
 <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
 <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se>

--I2hqn0pwJN89f9RoErH8BHpMDtSEXIKEq
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 13/04/17 09:30, Eric Gray wrote:
> Stephen,
>=20
> Your argument seems to assume that people should feel a need to
> publicly justify their feelings on any topic.

No I did not argue that at all.

>=20
> That is simply not the case.

I agree.

OTOH, if nobody were in fact to adamantly argue in pubic to
continue near term meetings in the US, then I do think that
(as I already said) that is something the IAOC ought factor
into their considerations.

S.


>=20
> -- Eric
>=20
> -----Original Message----- From: ietf [mailto:ietf-bounces@ietf.org]
> On Behalf Of Stephen Farrell Sent: den 13 april 2017 02:44 To: Joel
> M. Halpern <jmh@joelhalpern.com>; ietf@ietf.org; iaoc@ietf.org; IETF
> Announcement List <ietf-announce@ietf.org> Subject: Re: Update on
> feedback on US-based meetings, and IETF 102
>=20
>=20
> Hiya,
>=20
> On 13/04/17 01:27, Joel M. Halpern wrote:
>>=20
>> I think that many of us take it as given taht it is desirable to
>> meet in the US.
>=20
> I do not doubt that many IETFers likely think that. And I almost
> agree with it.
>=20
> My only problem is that I'm sadly no longer sure that the present
> tense is correct in your statement, which is just a shame.
>=20
> I fully agree with your statement cast into the past tense.
>=20
> I really hope that the future tense variant will be something with
> which I can agree. At the moment I do not for the reasons stated (to
> do with unpredictability).
>=20
>> In contrast, I am quite sure that folks who felt strongly that we=20
>> should not meet in the US understood that for that to happen, they
>>  needed to make their voices heard.
>=20
> That's a fair point. I think though that it also puts on onus on any
> folks who adamantly think we ought continue to meet in the US, to
> also publicly justify that, given the opposite arguments already
> voiced on the list. (I do realise there's a danger there of folks
> going OTT, so I hope we all impose a bit of self-restraint if making
> arguments either way.)
>=20
> Note though that my query was with Leslie's assertion that the survey
> result and list traffic reflected similar levels of adamant
> assertion. (I wasn't doubting that some of us are likely adamant
> about any random or non-random topic:-)
>=20
> Cheers, S.
>=20


--I2hqn0pwJN89f9RoErH8BHpMDtSEXIKEq--

--GtlTdpAG3odrBB8XSfvCs74tSUPTCI6w2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY7zqgAAoJEC88hzaAX42iIOkH/3s9Zf87Vt4wpXWn4Y4AHHPo
U2yOWyv4vYhLz9zdpuSKdtsB14O1MitorsJP6EhyFUbYuJWgtUTXiOi32FqgutPn
lZyOdsZZr2dl3U3qls7erepADv693jsHTq/2qHJ7vZpy+WWoP31kfiVttvm+vT32
i6UoTx4Gq/PZUlM8A7m/2Q41I2MiEAMUl2Ke9wkjzn5YDH25w2eWtydndquWahC6
tq2tmulq8q1ithNGhubTOhWnn5xgVUqV5PBTHCoquSQEi1J4yPNZBSPT0rthkOVz
JdGp91UkqFnsMVFTUmCimPbPQT3kk6sABDD+kYh+PQ9ffwEdhXZp7y+/whMBIB0=
=UTAX
-----END PGP SIGNATURE-----

--GtlTdpAG3odrBB8XSfvCs74tSUPTCI6w2--


From nobody Thu Apr 13 02:14:55 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCD6131868 for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 02:14:53 -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, RP_MATCHES_RCVD=-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 ARUM1dFUjQDs for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 02:14:50 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB3913186B for <ietf@ietf.org>; Thu, 13 Apr 2017 02:14:50 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 7F2D11B0159F; Thu, 13 Apr 2017 12:10:09 +0100 (BST)
Message-ID: <58EF416D.70605@erg.abdn.ac.uk>
Date: Thu, 13 Apr 2017 10:14:21 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Feedback on draft-mm-wg-effect-encrypt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DCt6TR2mrsX5xUTlsMLg3egMGlc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 09:14:54 -0000

Al and Kathleen,
I read the above draft as part of my preparation to think through the 
implications of encrypting transport-layer information, and this is 
therefore a very late post (sorry).

I have a few very top level comments, which I hope may help:

* I think this sort of Informational document from a slightly different 
perspective is really important to publish for the  community. It 
raises-up a myriad of topics and starts to expose areas that require 
thought in the design of protocols, operational procedures, etc. The 
greatest strength is that the scope is wide-ranging. This does not 
replace the need for more focussed infromation at each protocol layer.

* It is important to think about current operational support when we 
discuss monitoring, otherwise I fear the discussion will tend to focus 
on what is perceived as malicous monitoring. It could be easy to simply 
lump all monitoring, middleboxes, etc as bad for all, and all encryption 
as helpful to all. We need to understand the implications on design, and 
how now to best operate networks.

There are actually still quite a lot of NiTs, and I'm assuming these 
will be fixed to make this more readable):

* A few places "?" has been substituted for an apostrophe:-)
* "a reasonable
        assumption is that the DSCP markings would be withheld from the
        outer IP header to further obscure which packets belong to each
        application flow."
- Is this true. I know I worked on HAIPE (IPsec) and they allowed DSCP 
through, after a struggle, because it was such a powerful tool for 
running their networks and piroritising flows? So I question whether 
this is a given, or just a consideration that needs to be weighed? 
Actually in a mobile context we haven't observed a lot of DSCP support 
in networks... but maybe some operators do this well? (I think they 
should start!)
* Some of the mobile stuff seemed that it was jargon-rich, and more 
general wording would help where this happens. (That also may make it 
accessible to people working on Enterprise wireless, anb other network 
technologies with varying managed capacity).
* /QAM/ - I think this should be modulation/coding scheme, to be less 
technology-specific?
* /PGP/ /SMTP/ /TLS/ /DTLS/ /iSCSI/ /KPIs/ /KQI/ /QOE/ /DRM/  etc, define?
* /TCP transmitter/ /TCP sender/
* /TCP Pipelining/Session Multiplexing/ - does using a VPN also have the 
same effect?

Some sarcastic or colloqual sentences will I think make this hard to 
follow for someone who doesn't agree or does not have English as a first 
language. The key value of a survey is that it is accessible to others.

My last comment is probably the one that I think most concerns me: The 
abstract doesn't say that this is from an operational perspective - or - 
based on experience of service providers - or - something that sets the 
context, I think it is important to call-out this sort of detail for any 
informational document, to really differentiate it from publishing IETF 
consensus (e.g., BCP).

Thanks for writing this,

Best wishes,

Gorry


From nobody Thu Apr 13 03:00:06 2017
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC120131493; Thu, 13 Apr 2017 03:00:05 -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, 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 QK15UcTUEEGT; Thu, 13 Apr 2017 03:00:04 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.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 D761C131464; Thu, 13 Apr 2017 03:00:03 -0700 (PDT)
X-AuditID: c618062d-77bff700000029b8-8d-58ef5e4e3872
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by  (Symantec Mail Security) with SMTP id 1E.46.10680.F4E5FE85; Thu, 13 Apr 2017 13:17:38 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0339.000; Thu, 13 Apr 2017 05:59:59 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Subject: RE: Update on feedback on US-based meetings, and IETF 102
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Thread-Index: AQHSs+YQECjTpLL78USByfjfVB8KHqHCrUkAgAAHYACAAATAAIAAPrVAgABHtAD//8vq8A==
Date: Thu, 13 Apr 2017 09:59:58 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF64B608D74@eusaamb107.ericsson.se>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie> <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se> <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
In-Reply-To: <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyuXRPlG5Q3PsIg2vfuCw+XbzDanHvzHQ2 i2cb57NYfDz1hsli+t5r7A6sHmu7r7J5LFnyk8nj3JTvjAHMUVw2Kak5mWWpRfp2CVwZN1ee Yi9YpVFx5O9ExgbGJepdjJwcEgImEhdmHGfvYuTiEBLYwCixYdtBZghnOaPEnGkrmEGq2AQ0 JI7dWcsIkhAROM8osbx5OjtIQljASWLl9l4wW0TAWWJb8w4mCDtM4vjLDWwgNouAqsTv22tZ QWxeAV+JhVN+skFseMwkMfvyPrAGTgFbictdJ8GKGAXEJL6fWgMWZxYQl7j1ZD4TxK0CEkv2 nGeGsEUlXj7+xwphK0lMWnoOyOYAqteUWL9LH6JVUWJK90N2iL2CEidnPmGZwCgyC8nUWQgd s5B0zELSsYCRZRUjR2lxQU5uupHBJkZgfByTYNPdwXh/uuchRgEORiUe3gdG7yKEWBPLiitz DzFKcDArifCednkfIcSbklhZlVqUH19UmpNafIhRmoNFSZx3wvkLEUIC6YklqdmpqQWpRTBZ Jg5OqQZGxuglJvPWilbYu+t/nhUfGrzzkNSkaaYbH2lf+HP9Sv3Pjy9uBPNKv7qbIb5zicnM 1L8bpisK8ybenXJm6f7Pc2/23P/D+OFhmv6SN10soUnB/fs2836983WnqXbhxZMb9ParbCna 7vsqRa90Mqv2zJQbCxP1/VV2Zrheux3mo77cZ8/B32d5opRYijMSDbWYi4oTAYJBXqGLAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q1WEVDf-CTSqGWN_xmoPCZRQgaM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 10:00:06 -0000

U3RlcGhlbiwNCg0KWW91IHVzZWQgdGhlIHdvcmQgIm9udXMiIC0gd2hpY2ggY2FuIGJlIGludGVy
cHJldGVkIHRvIG1lYW4gImR1dHkiIG9yICJyZXNwb25zaWJpbGl0eS4iDQoNCkZvciBtZSwgYXQg
bGVhc3QsIHRoZSBkaXN0aW5jdGlvbiBiZXR3ZWVuIGR1dHksIHJlc3BvbnNpYmlsaXR5IGFuZCAi
bmVlZCIgaXMgcHJhY3RpY2FsbHkgbm9uLWV4aXN0ZW50LiAgVGhpcyB0aGUgYmFzaXMgb2YgbXkg
b2JqZWN0aW9uIHRvIHdoYXQgeW91IHNhaWQuDQoNCkV2ZW4gaWYgeW91IGRpc2FncmVlIHdpdGgg
dGhpcyBpbnRlcnByZXRhdGlvbiwgaG93ZXZlciwgSSB2ZXJ5IG11Y2ggZG91YnQgdGhhdCBhbnlv
bmUgc2hvdWxkIGZlZWwgYW4gIm9udXMiIHRvIHB1YmxpY2x5IGRlZmVuZCB0aGVpciBvcGluaW9u
IG9uIGFueSB0b3BpYywgbXVjaCBsZXNzIG9uIGEgdG9waWMgdGhhdCBpcyBhcyBsaWtlbHkgdG8g
YmUgdW5wb3B1bGFyIHdpdGggb25lIGdyb3VwIG9yIGFub3RoZXIgYXMgdGhpcyB0b3BpYyBpcy4N
Cg0KSSBhbHNvIGRvdWJ0IHRoYXQgdGhpcyBhcHBsaWVzIHRvIGFueSAib251cyIgdG8gc3RhdGUg
dGhlIGRlZ3JlZSBvciBzdHJlbmd0aCBvZiBjb252aWN0aW9uIHJlZ2FyZGluZyBhbiBvcGluaW9u
LCBldmVuIGlmIG9uZSBpcyB3aWxsaW5nIHRvIHN0YXRlIGl0Lg0KDQpJZiB5b3VyIHBvaW50IGlz
IHRoYXQgcGVyaGFwcyB0aGUgZGVncmVlIHRvIHdoaWNoIGFueSByZXNwb25zZSB3YXMgImFkYW1h
bnQiIHNob3VsZCBwcm9iYWJseSBoYXZlIGJlZW4gb21pdHRlZCwgdGhlbiBJIGFncmVlLiAgQnV0
LCBpZiB5b3VyIHBvaW50IGlzIHRoYXQgdGhlIHdpbGxpbmduZXNzIG9mIG9uZSBncm91cCBvZiBy
ZXNwb25kZW50cyB0byBzdGF0ZSB0aGVpciBkZWdyZWUgb2YgY29udmljdGlvbiBwbGFjZXMgYW55
IGR1dHkgb3IgcmVzcG9uc2liaWxpdHkgb24gYW55b25lIHBvc2l0aW5nIGEgZGlmZmVyZW50IG9w
aW5pb24gdG8gc2ltaWxhcmx5IHN0YXRlIGEgZGVncmVlIG9mIGNvbnZpY3Rpb24sIHRoZW4gSSBm
ZWVsIGEgbmVlZCB0byBkaXNhZ3JlZS4gIFBlcmhhcHMgYWRhbWFudGx5LiAgOi0pDQoNCi0tDQpF
cmljIA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU3RlcGhlbiBGYXJyZWxs
IFttYWlsdG86c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZV0gDQpTZW50OiBkZW4gMTMgYXByaWwg
MjAxNyAxMDo0NQ0KVG86IEVyaWMgR3JheSA8ZXJpYy5ncmF5QGVyaWNzc29uLmNvbT47IEpvZWwg
TS4gSGFscGVybiA8am1oQGpvZWxoYWxwZXJuLmNvbT47IGlldGZAaWV0Zi5vcmc7IGlhb2NAaWV0
Zi5vcmc7IElFVEYgQW5ub3VuY2VtZW50IExpc3QgPGlldGYtYW5ub3VuY2VAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBSZTogVXBkYXRlIG9uIGZlZWRiYWNrIG9uIFVTLWJhc2VkIG1lZXRpbmdzLCBhbmQg
SUVURiAxMDINCkltcG9ydGFuY2U6IEhpZ2gNCg0KDQoNCk9uIDEzLzA0LzE3IDA5OjMwLCBFcmlj
IEdyYXkgd3JvdGU6DQo+IFN0ZXBoZW4sDQo+IA0KPiBZb3VyIGFyZ3VtZW50IHNlZW1zIHRvIGFz
c3VtZSB0aGF0IHBlb3BsZSBzaG91bGQgZmVlbCBhIG5lZWQgdG8gDQo+IHB1YmxpY2x5IGp1c3Rp
ZnkgdGhlaXIgZmVlbGluZ3Mgb24gYW55IHRvcGljLg0KDQpObyBJIGRpZCBub3QgYXJndWUgdGhh
dCBhdCBhbGwuDQoNCj4gDQo+IFRoYXQgaXMgc2ltcGx5IG5vdCB0aGUgY2FzZS4NCg0KSSBhZ3Jl
ZS4NCg0KT1RPSCwgaWYgbm9ib2R5IHdlcmUgaW4gZmFjdCB0byBhZGFtYW50bHkgYXJndWUgaW4g
cHViaWMgdG8gY29udGludWUgbmVhciB0ZXJtIG1lZXRpbmdzIGluIHRoZSBVUywgdGhlbiBJIGRv
IHRoaW5rIHRoYXQgKGFzIEkgYWxyZWFkeSBzYWlkKSB0aGF0IGlzIHNvbWV0aGluZyB0aGUgSUFP
QyBvdWdodCBmYWN0b3IgaW50byB0aGVpciBjb25zaWRlcmF0aW9ucy4NCg0KUy4NCg0KDQo+IA0K
PiAtLSBFcmljDQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSBGcm9tOiBpZXRmIFtt
YWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSANCj4gT24gQmVoYWxmIE9mIFN0ZXBoZW4gRmFy
cmVsbCBTZW50OiBkZW4gMTMgYXByaWwgMjAxNyAwMjo0NCBUbzogSm9lbCBNLiANCj4gSGFscGVy
biA8am1oQGpvZWxoYWxwZXJuLmNvbT47IGlldGZAaWV0Zi5vcmc7IGlhb2NAaWV0Zi5vcmc7IElF
VEYgDQo+IEFubm91bmNlbWVudCBMaXN0IDxpZXRmLWFubm91bmNlQGlldGYub3JnPiBTdWJqZWN0
OiBSZTogVXBkYXRlIG9uIA0KPiBmZWVkYmFjayBvbiBVUy1iYXNlZCBtZWV0aW5ncywgYW5kIElF
VEYgMTAyDQo+IA0KPiANCj4gSGl5YSwNCj4gDQo+IE9uIDEzLzA0LzE3IDAxOjI3LCBKb2VsIE0u
IEhhbHBlcm4gd3JvdGU6DQo+PiANCj4+IEkgdGhpbmsgdGhhdCBtYW55IG9mIHVzIHRha2UgaXQg
YXMgZ2l2ZW4gdGFodCBpdCBpcyBkZXNpcmFibGUgdG8gbWVldCANCj4+IGluIHRoZSBVUy4NCj4g
DQo+IEkgZG8gbm90IGRvdWJ0IHRoYXQgbWFueSBJRVRGZXJzIGxpa2VseSB0aGluayB0aGF0LiBB
bmQgSSBhbG1vc3QgYWdyZWUgDQo+IHdpdGggaXQuDQo+IA0KPiBNeSBvbmx5IHByb2JsZW0gaXMg
dGhhdCBJJ20gc2FkbHkgbm8gbG9uZ2VyIHN1cmUgdGhhdCB0aGUgcHJlc2VudCANCj4gdGVuc2Ug
aXMgY29ycmVjdCBpbiB5b3VyIHN0YXRlbWVudCwgd2hpY2ggaXMganVzdCBhIHNoYW1lLg0KPiAN
Cj4gSSBmdWxseSBhZ3JlZSB3aXRoIHlvdXIgc3RhdGVtZW50IGNhc3QgaW50byB0aGUgcGFzdCB0
ZW5zZS4NCj4gDQo+IEkgcmVhbGx5IGhvcGUgdGhhdCB0aGUgZnV0dXJlIHRlbnNlIHZhcmlhbnQg
d2lsbCBiZSBzb21ldGhpbmcgd2l0aCANCj4gd2hpY2ggSSBjYW4gYWdyZWUuIEF0IHRoZSBtb21l
bnQgSSBkbyBub3QgZm9yIHRoZSByZWFzb25zIHN0YXRlZCAodG8gDQo+IGRvIHdpdGggdW5wcmVk
aWN0YWJpbGl0eSkuDQo+IA0KPj4gSW4gY29udHJhc3QsIEkgYW0gcXVpdGUgc3VyZSB0aGF0IGZv
bGtzIHdobyBmZWx0IHN0cm9uZ2x5IHRoYXQgd2UgDQo+PiBzaG91bGQgbm90IG1lZXQgaW4gdGhl
IFVTIHVuZGVyc3Rvb2QgdGhhdCBmb3IgdGhhdCB0byBoYXBwZW4sIHRoZXkgIA0KPj4gbmVlZGVk
IHRvIG1ha2UgdGhlaXIgdm9pY2VzIGhlYXJkLg0KPiANCj4gVGhhdCdzIGEgZmFpciBwb2ludC4g
SSB0aGluayB0aG91Z2ggdGhhdCBpdCBhbHNvIHB1dHMgb24gb251cyBvbiBhbnkgDQo+IGZvbGtz
IHdobyBhZGFtYW50bHkgdGhpbmsgd2Ugb3VnaHQgY29udGludWUgdG8gbWVldCBpbiB0aGUgVVMs
IHRvIGFsc28gDQo+IHB1YmxpY2x5IGp1c3RpZnkgdGhhdCwgZ2l2ZW4gdGhlIG9wcG9zaXRlIGFy
Z3VtZW50cyBhbHJlYWR5IHZvaWNlZCBvbiANCj4gdGhlIGxpc3QuIChJIGRvIHJlYWxpc2UgdGhl
cmUncyBhIGRhbmdlciB0aGVyZSBvZiBmb2xrcyBnb2luZyBPVFQsIHNvIA0KPiBJIGhvcGUgd2Ug
YWxsIGltcG9zZSBhIGJpdCBvZiBzZWxmLXJlc3RyYWludCBpZiBtYWtpbmcgYXJndW1lbnRzIA0K
PiBlaXRoZXIgd2F5LikNCj4gDQo+IE5vdGUgdGhvdWdoIHRoYXQgbXkgcXVlcnkgd2FzIHdpdGgg
TGVzbGllJ3MgYXNzZXJ0aW9uIHRoYXQgdGhlIHN1cnZleSANCj4gcmVzdWx0IGFuZCBsaXN0IHRy
YWZmaWMgcmVmbGVjdGVkIHNpbWlsYXIgbGV2ZWxzIG9mIGFkYW1hbnQgYXNzZXJ0aW9uLiANCj4g
KEkgd2Fzbid0IGRvdWJ0aW5nIHRoYXQgc29tZSBvZiB1cyBhcmUgbGlrZWx5IGFkYW1hbnQgYWJv
dXQgYW55IHJhbmRvbSANCj4gb3Igbm9uLXJhbmRvbSB0b3BpYzotKQ0KPiANCj4gQ2hlZXJzLCBT
Lg0KPiANCg0K


From nobody Thu Apr 13 05:14:34 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE98129439 for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 05:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.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 anZhiA71f-5D for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 05:14:30 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0104.outbound.protection.outlook.com [104.47.0.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 173BA1252BA for <ietf@ietf.org>; Thu, 13 Apr 2017 05:14:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=UGtZr+tT+bF6b/PqNrLC75OCSvA7O1Zsi39HB6LftFw=; b=flAUxcy8MJepARh5QFCuXn9z26nmXyl0f9glKn467Tnu0Jud9YMjzm7Atqi7gLWgKXuBUkdqWZ+tW+VAadroTP8maeTtrw++k8JfUvsWB4Psyl/ne2+hPCtakfPGEPWlED6nxstykg4r3UAOZjcwipuO7YWtO4hR20r0tpTDhzM=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.169.157.161) by VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.6; Thu, 13 Apr 2017 12:14:27 +0000
Message-ID: <06e001d2b44f$340c40c0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <m2lgr5yttn.wl-randy@psg.com> <b5846131-d912-b288-670b-2f74c901b2d5@gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Date: Thu, 13 Apr 2017 12:00:54 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.169.157.161]
X-ClientProxiedBy: AM4PR05CA0022.eurprd05.prod.outlook.com (10.171.184.163) To VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13)
X-MS-Office365-Filtering-Correlation-Id: 2a46cd79-46d2-4f8f-6d80-08d48266a16b
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 3:vsPTNwMAeDbJNd4wFwqG5JNkwx33DJevhX2orVMQllMx8FRb/StOmDNhnMO2nZFyQ1E+6bLe+vUNhTCsEeZRAA6FMjSgTiRxBuA6QMPJWFx7a8g+vT5dzw+Fg5/7MdOchmv1lRIaojKsvgkUiuvMahtJLfRJMapaCnoE5D+qVyZ2aNgcCJvpvNli+yHuC2FtBcxVMA9DrVDeajAZPZt7rQop5DEpNSwM7d3fxBtd3S7M737uUtvh9CV2wi59zVzX6yqEX4qKX6tUt/a9byLwsAEDpZm0f3vujeVoJwm3AyqN9eYNP0TySk2i733rL2BU8aERaT/fIdjUBuYVZSNmBQ==; 25:5zrlUrjPQNZO8yFBwCroPrkWhyo41Xx8Q0mu3teAWYYKiMkgNo5MHm3MYMO0cbAeZP4amts06GY50gotV+e3aM+/7paUTn/Kdf1/hfTMN/CrhYPSWmxiaGP0Sfx9FHu1PRaADqf/+tWvnJB9CNIlYjqPGaGL7KnZsXxeQxkQC2GQLQwhInzwezjptvGXzfu2t+FzzFLS9272ViNf/Chrb1uA8s1m6P7Rc2r5DVGEmVWxa2Fgqo7JifmsAF46n6DRJ6vlClWBQ39f+mrAfr8HGqDU5eDvseTD424Bd2nTPOYCzmPMdD0dQWBn1fux2wQoeRuwMTP8w/hs9f90KWbW+0j434PYqrbfzcKGHOclgXEpvJA8pHCkdrGXRv3j2ddlfl94dINf/Mf7z2YCyoL/+1YbsyswmcC8WjU9guBDFHSrBS5S/w/7EXQNxqIZRbsAKc/eU7Jr/9/rc77ckpZe3I6/5eOhxI0hyP45gq3DsM8=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 31:LJ0OGGkTJhGwDu0aFGLrMzKkegftuJn4DbNclOr1OlCX3Ln6QhGCRjE0CZuD2FSZrlWg26GCbMU7MzDvk2t9gadiZm7mMsWOO48n+41ITesBwCntm/Mm3veuLMrD+KZ537FVrturil3sHrWQjuawkzBG0oTH1bKFDyLiiQkA3iyZ32UT+ppPbIX8fJZEVN8fG9ZD8PTnlxInJtQ4ueNzz+iW09+j80rALWmqhmbng31cqNY9U24viaZh3gBryZQ7AwqJ2PwYg4Dt4Lf7r9P9IA==
X-Microsoft-Antispam-PRVS: <VI1PR07MB156772BB741CE8F44D1BAC1FC6020@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(6072148); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 4:c267FRGuzYuCKgFEuDj8B3b8dJYAZmDk+0UuiGJaZRnNDDzEvmLPMGoQuQ8T7nsulMSee4ZJr3BieWv4JmYblLx/n+J/k30Lfbu2/sVH8imb89NVfoznYGudX3lLvmnlpXX1sUfjZUB6n94gY8b3RvuYMXwwEmCJs/o8WjFUeZBxeQ+x0kFMqOhUlMFFTLMl17XsuvSKikz1SZgmcRqk9h/s1G+62aGTpDnORk1SkDmTUJqa+MzWND+4st0UyJnJYmQKG2ugZ7+XVckk1Q26k64JuRI3sIRL2HZu4vwaAL6Qxazfk85v6LcxMb03TzYjHzhnDbtM7VTBoKPeL0jQxl7YmlGhfxsmpS5TrRo/e0VT0PMLAkJ97AEVZpufuIvVTKY0uaUT6LBJlC2cGbQOzNLdiISnRsozYHq+cWqKwckcshhpklraIaJ4llN7tUmFXkI6kIRXSq+nrJInyMnAfSTcCOVFizhIxQyNJJVKbExmE8GXTjkFNtwOKuCE2O0qtBbKq7Tk34PLJDynUEBl4J/SpMzXCbS+Nij5tq1sSsfXWOvYJuO3KNX2jSehnjBQw8B75gZKW5D64s57VVDY9cOqAJYTjxgQ63ry8XI4zAv3jxyLO6SF7ztxGDXG5YF6qvUin/yfPOM35wtIDVwA38K0WTLGaLMrEWfbLc/4hlAh3skQc+SsTrIM4kSx0C48/GGZ+cEdKgAnAHBlszZlRw==
X-Forefront-PRVS: 02760F0D1C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(39840400002)(39860400002)(39850400002)(39400400002)(39410400002)(13464003)(24454002)(377454003)(6116002)(25786009)(6246003)(3846002)(81166006)(8676002)(6486002)(38730400002)(33646002)(116806002)(23746002)(66066001)(230700001)(44716002)(7736002)(44736005)(5660300001)(53546009)(305945005)(93886004)(47776003)(6916009)(229853002)(189998001)(6496005)(2351001)(61296003)(50466002)(42186005)(50226002)(81686999)(50986999)(76176999)(9686003)(4720700003)(15650500001)(110136004)(86362001)(53936002)(81816999)(6666003)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; VI1PR07MB1567; 23:rTJEQv+ZlocO0A44GqEVdUmJNr4Vj5yqWOC8S?= =?Windows-1252?Q?vZfzdwZfF9pQ9gvl7m9k0K+P7bVfDy8XRlkj2envXJbBW4M4WvwiwBac?= =?Windows-1252?Q?fPfD6eXW7YZRCm6hJcQEXsBUPA7fLIHw6Vpon6JoEjafcg1T/oCuagCJ?= =?Windows-1252?Q?P62qikfi+CfouBGbfMMaU4QvY2Mo6aaZXFCPHorwx7Ykh0QHFk6iMWhO?= =?Windows-1252?Q?GBiKVwEgfzo8WZe1rMJRtELJpOn8DTaGJrL/S8b21G8eA7eCHUGVTkS5?= =?Windows-1252?Q?Dm1g98d2nZP4n3a1nyiNG7+N2dM6t+RfQsiZ3czdCTOjTZtRes0wvOZa?= =?Windows-1252?Q?po56V1paLFyEos/vm9Ml+L0EvNqsiYSgrumX16d+clfh73NoZmv3J1zZ?= =?Windows-1252?Q?smR3NpDpK8hA0+oVpg96VO3AI7kp2xK56FVQg78VM4qVDlog8HtyMcIH?= =?Windows-1252?Q?HIvGOM9FjJbNrhXS8QTai7z8AZZDAmSPXJ77/06olW9WuHODqoBoPlWP?= =?Windows-1252?Q?+yAkI25JstBsIJPwZ1qixxGRyfwbT4mOxoIOAGwuwGnQ1Mf6HWQ6eHJA?= =?Windows-1252?Q?QSSiWZYQ7Eir9CiJbVwd268+ZfURjA+AMPNRAz29mbuSgbffMK/cAuO4?= =?Windows-1252?Q?oE4cw9qviRQJRqfWif4oxJeYRnSNHPeAdrdMQLKR1Z0E92f4494jLiiR?= =?Windows-1252?Q?8zTA+MXcs6BhZS+dmTR8pZvexJvcPDZ9xC6LeMk4x95UXup++PvYG2Iu?= =?Windows-1252?Q?4qhld/dSTh+TfzUG/vTzVHrC891ivoh6jeqAh4Yci+kkL6LUygFx/4Yo?= =?Windows-1252?Q?mHkL7zrE848zCOkrsS6iqDFBqX4EF9LEP2ScdyVkAvIjTWX68forgCFr?= =?Windows-1252?Q?sReurjruWf7jpfV1XbR9OWzWHAxuteuiXs1UHY5iQytZhXI9FxLcdJUp?= =?Windows-1252?Q?z6vNQpmUfJVqL9XMT99Bd6eT/uc/WgiyUAAQ2dXFAmQ2qVdVSm41uAnV?= =?Windows-1252?Q?otKPpNbNN0wc3dWjSy8qqFDEFNmTztbZ/j+QvK+KdkIht/Dmf4HBVW3U?= =?Windows-1252?Q?GwcykCJLMcZmROOpLl265n2SWKT7Uh56R+Mm+Db5kcT0jQ2V07Crt2ga?= =?Windows-1252?Q?Lesj9kbub4zmTIO6ZtRYolnOpQ84i9mhH3yAsnS3Lae1Vfhtt1G1MVzQ?= =?Windows-1252?Q?wCwAc0dlG9g/USGewXr7ZXlNnJgZZoT75aSBrV8KRCGTLYSwa1tW6CMy?= =?Windows-1252?Q?sFab2hvVMAUeUeu0/gEnPoWPTFZfbbHexDL4Zc5Vz/b/AtUupA7Wxfvv?= =?Windows-1252?Q?U04b9sVMcNKZJZE5pB0He9JnAyTVERC+bmG9tGaRjkcTKxGfhATShqyp?= =?Windows-1252?Q?uF2RbKVr1GJleZZjHsm275ju9hxle5trBSYBFaodc6Us3W9dqBFdDo?= =?Windows-1252?Q?=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 6:F8Z+yVl24CxOefSIh4LJ/d0HlE2NMPpyHcs5kCxrpY+SdVicTeVSb53qq9+aQBsB1hhyx/sPV4AbnbpEkbUK7he3WfBuozomS+Obrnq/0BryAg8Tu9tGCWurTNVeEMiHwc8+kbD3YVqDImJKQdrNjtyQP/0g4/YcuR13+l7Kaa3SsxR0GJDi/WX1YQnd/V3d7+gAIQbUbUOIxT7+jpedK8Jl4eWvfuLZcpAi2JQ/xP8WM9q+fuYmFZEMydMZRjMAGbaJU4Zvj5GSRRVUdYWcezdxoajwv7AWTGIYY4fD1dyhTlhCbs1CydeqMSKOqjk2DEj39JbQtVjMG0fv83a7Nk70rJPEd3OrXaykkHT8HIB/j0kj7PdFbITf/Blw2LxqgHp8wzr6xyx7pZTYaBuRPdnbgOH2im9w3kN7JP18yeVU8mJtgWzh3eLxPdoi6w/6mQ3YIA3w5Y0b0sY+fCbhFw==; 5:pUQp3vEZ4V/ADKKT4/zShJpI+1JmSWv1FhygHs99VKLtQ04ngcXyxiT1A0Bu+VdBH/1upVKds06TwrW8rUa9kHigJkyRwN8aY0UdKwa2RfK7kISl8CkaSfMiXJr1qk9mU3oMd/JX02h8vkziE77EDA==; 24:Fz726wmiHtjYstlhoFo8h73EofRt/FUXl4bVPQHc7KKGTOb2fM7E9CgjExaTJUquZJ+MdvwJZ/a6/XFK4ORtWxTnTtVyV3jaNo9pq7lJqtA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 7:7TfQ1c+kJYuDElP6s80XZwBR1yTvd4q+Zw4ibhg3XkPNadFb3GkrSK61vopS2g4zBdY26FDP4nEY1KIDE8gsxeNeAugRoXdVyl0fTLHqgC32ntgTAhCv15iV/HTgMYv92+yds+PtwNzoUYEYuGReLzL1XGL2MGdO+7iFOBvrX/HFE2ITTmQ06w8ES9UM22nsugaLPQQCJQH4o1vRAJIAr68xponGGFfiLSWVGnkboOBcnM/jDaEDcmZKJAcPV45YnnJ0PehY9TrSenjiD1D+ZbS2LJGTEzDVOZf+nidHjDKUxPjtbvPd7u/62DPKD7AjlvzSrz6KyygYW5SS19WAtQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Apr 2017 12:14:27.0185 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XuIrLxJKydcloiSsha9YpZKGfgw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 12:14:33 -0000

----- Original Message -----
Sent: Thursday, April 13, 2017 4:10 AM

On 4/12/17 5:33 PM, Randy Bush wrote:
> to me, the lack of predictibility on the draconian index is the main
> issue.  and for the uk as well as the states,  both seem to have a
well
> developed and practiced ability to do very damaging things on very, or
> no, notice.

I am in favour of the UK doing very damaging things on very, or no,
notice; in fact, I prefer no notice.

I don't know how widely bad news spreads these days, but suspected
terrorists continue to kill people in the UK, and Europe, every few
months and while some of the attacks have resulted in significant loss
of life, we have not, in the recent past, had the hundreds of deaths
from a plane being brought down; and the worst case scenario, of a crash
over a major city, would make that thousands.

The shoe bomber was not forestalled but did not cause a crash.  The
printer cartridge bomb was not forestalled but did not cause a crash.
The use of three household liquids to create a bomb on board was
forestalled; preventing it caused massive disruption and resentment but
when the facts emerged, then the action seemed reasonable and
proportionate; and I was relieved that no notice was given.

Now there is a ban on electronic devices in hand luggage when travelling
to the UK from six countries; I saw that that was going to be extended
for travel to all Europe and perhaps to the USA.  I see no explanation
for this action but the history, as above, makes me see this, on
balance, as a prudent precaution.

So suspected terrorists switch to low tech means - lorries, knives and
such like - and people continue to be killed but when, without warning,
my travel plans are disrupted, then I give the disrupters the benefit of
the doubt.

Probabality low, impact high.  YMMV.

Tom Petch

+1

Melinda





From nobody Thu Apr 13 07:47:14 2017
Return-Path: <jaime.jimenez@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6CD129481; Thu, 13 Apr 2017 07:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ucrBtVSv0t8N; Thu, 13 Apr 2017 07:47:05 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.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 56624129409; Thu, 13 Apr 2017 07:47:04 -0700 (PDT)
X-AuditID: c1b4fb30-abffb70000006667-8c-58ef8f65d397
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id 66.C0.26215.56F8FE85; Thu, 13 Apr 2017 16:47:02 +0200 (CEST)
Received: from ESESSMB107.ericsson.se ([169.254.7.253]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0339.000; Thu, 13 Apr 2017 16:47:00 +0200
From: =?utf-8?B?SmFpbWUgSmltw6luZXo=?= <jaime.jimenez@ericsson.com>
To: Mark Nottingham <mnot@mnot.net>
CC: weigengyu <weigengyu@bupt.edu.cn>, Carsten Bormann <cabo@tzi.org>, "art@ietf.org" <art@ietf.org>, "draft-ietf-core-coap-tcp-tls.all@ietf.org" <draft-ietf-core-coap-tcp-tls.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "core@ietf.org" <core@ietf.org>
Subject: Re: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsa/qwMrkOzw42UWHLUrHT1G7O6G+Oc0AgAD5ZwCAAbONAIAAASMAgAJc0QA=
Date: Thu, 13 Apr 2017 14:47:00 +0000
Message-ID: <180A6A3D-2242-4D71-AAC7-4180284398E4@ericsson.com>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <52AFE50B189544AFB2744028519A173D@WeiGengyuPC> <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net>
In-Reply-To: <7D33923C-AB67-43F1-9417-08574DCC62A3@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_180A6A3D22424D71AAC74180284398E4ericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrIIsWRmVeSWpSXmKPExsUyM2K7rm5a//sIgxWL5SxW3PWwODLlLqvF vrfrmS32vXnHYvFs43wWi/WfHjNaTJn5id2B3aPx1F42jyVLfjJ5bFz8ndVj2qLMAJYoLpuU 1JzMstQifbsErowNq46wFbyWqFjxOL6BsUmii5GTQ0LARGLj2U+sXYxcHEIC6xklfl79ygbh LGGU6Gn9xQRSxSbgLPHpWSM7iC0ioCzxff4SFpAiZoFWJomWrdPBEsICARJL224ANXAAFQVK bDmkD1HvJ7Hk6TRmEJtFQFVi0Zw2sHJeAXuJyc/mQ21uZ5KY+X4P2DJOARuJWy+eMILYjAJi Et9PrQGLMwuIS9x6Mp8J4mwBiSV7zjND2KISLx//Y4WwlSQalzxhhahPlvh+9TUjxDJBiZMz n7BMYBSZhWTULCRls5CUzQJ6gVlAU2L9Ln2IEkWJKd0P2SFsDYnWOXOhbGuJpkWnWJDVLGDk WMUoWpxanJSbbmSkl1qUmVxcnJ+nl5dasokRGLEHt/w22MH48rnjIUYBDkYlHt6ElvcRQqyJ ZcWVuYcYJTiYlUR4p7UBhXhTEiurUovy44tKc1KLDzFKc7AoifM67rsQISSQnliSmp2aWpBa BJNl4uCUamDUMZ5vWszzU/z/sdVyZfF3FpboXLkjE+A982v6Mv8NO0smbN+z59RC3z///z7d l1Y2e2f2kvPtfzt6chZIbaxT1awLK2V7IPdm0fKnh2wmZk5+k1H/+X30lfLyiOP1RywtDtyd +1DveJbAOvOqSymnNxy871L/WzpNu+zvN3HJ7x2R3krOSka/lFiKMxINtZiLihMBtD8nhNQC AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xEthu49YSeJqOtfkcRX7_p_VCbI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 14:47:06 -0000

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

SGksDQoNCmNvdWxkIHlvdSBzaGFyZSBkYXRhIHNvdXJjZSBvbiB0aGF0IHBscz8gSXTigJlkIGNv
bWUgaW4gaGFuZHkuDQoNCkNpYW8hDQotIC0gSmFpbWUgSmltw6luZXoNCg0KT24gMTIgQXByIDIw
MTcsIGF0IDUuNDIsIE1hcmsgTm90dGluZ2hhbSA8bW5vdEBtbm90Lm5ldDxtYWlsdG86bW5vdEBt
bm90Lm5ldD4+IHdyb3RlOg0KDQooZS5nLC4gOTAlKyBzdWNjZXNzIHJhdGVzIGZvciBVRFAgcHJv
dG9jb2xzKS4NCg0K

--_000_180A6A3D22424D71AAC74180284398E4ericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <4FBEA9501C975747B32AB3369FEF09FA@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGksDQo8ZGl2IGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5jb3VsZCB5b3Ugc2hhcmUgZGF0YSBz
b3VyY2Ugb24gdGhhdCBwbHM/IEl04oCZZCBjb21lIGluIGhhbmR5LjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Q2lhbyE8YnIgY2xhc3M9
IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgbGV0
dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjogc3RhcnQ7IHRl
eHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFjZTogbm9ybWFs
OyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdp
ZHRoOiAwcHg7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNl
OyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyIgY2xhc3M9IiI+DQo8ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBsZXR0ZXItc3BhY2luZzogbm9ybWFsOyBvcnBo
YW5zOiBhdXRvOyB0ZXh0LWFsaWduOiBzdGFydDsgdGV4dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFu
c2Zvcm06IG5vbmU7IHdoaXRlLXNwYWNlOiBub3JtYWw7IHdpZG93czogYXV0bzsgd29yZC1zcGFj
aW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsgd29yZC13cmFwOiBicmVh
ay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCi0gLSBKYWltZSBKaW3DqW5lejwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gMTIgQXByIDIwMTcsIGF0IDUuNDIsIE1hcmsg
Tm90dGluZ2hhbSAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1ub3RAbW5vdC5uZXQiIGNsYXNzPSIiPm1u
b3RAbW5vdC5uZXQ8L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJj
aGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTog
SGVsdmV0aWNhOyBmb250LXNpemU6IDEycHg7IGZvbnQtc3R5bGU6IG5vcm1hbDsgZm9udC12YXJp
YW50LWNhcHM6IG5vcm1hbDsgZm9udC13ZWlnaHQ6IG5vcm1hbDsgbGV0dGVyLXNwYWNpbmc6IG5v
cm1hbDsgdGV4dC1hbGlnbjogc3RhcnQ7IHRleHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3Jt
OiBub25lOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10
ZXh0LXN0cm9rZS13aWR0aDogMHB4OyBmbG9hdDogbm9uZTsgZGlzcGxheTogaW5saW5lICFpbXBv
cnRhbnQ7IiBjbGFzcz0iIj4oZS5nLC4NCiA5MCUmIzQzOyBzdWNjZXNzIHJhdGVzIGZvciBVRFAg
cHJvdG9jb2xzKS48L3NwYW4+PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_180A6A3D22424D71AAC74180284398E4ericssoncom_--


From nobody Thu Apr 13 08:21:38 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 550B11292F5 for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 08:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 eU33Y7G5Hjcg for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 08:21:34 -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 EF05A128B44 for <ietf@ietf.org>; Thu, 13 Apr 2017 08:21:33 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id b187so68931433oif.0 for <ietf@ietf.org>; Thu, 13 Apr 2017 08:21:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=WUT8ZbfjYglkIYvM99pR2yNLypbMNX9rXOZvYy5Uu5A=; b=IFBU/niDMDD0ZR/V23m1glJwIZpBkXBoHnY1mOBOaqqH++Hf79G7WqrnCPIVov7Vdx dn2fn+ayZBLbMfOauFCOBRoG5dMz6StMc8DMbaV+8euIxFbhWvNV3g7WgE/0ZQwl4QuF qysyE3ekhXrf2WXLfJLrASxZsjddMncJjhzPiOt9vvfBvsSizWi0vgon+ERTj7GWHQS/ ArmkgkCjyyAYAgnZys00OmJC/htASw/JNgfrmaPFaeUyH0RQPN8nz3/akEP3H3CoLbDu SOVZf8fK+zVHH5478OeLbNJq2iQFPeSc7SVrtHBwEkX5jjteP+kVAVZE2/VjMdM0Ralr nR1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=WUT8ZbfjYglkIYvM99pR2yNLypbMNX9rXOZvYy5Uu5A=; b=ZXC6p8eJUmAj3XuIuvnOf8hc6nWf1XRKUXzZ/9m5DmngbnRaaKDsm2XB3hZax3maYZ SVf2q560xpJjM/k8YuJoDHY0HjTpzThK76EFeK2AwnbLP3/X+H/g4WvVJu2+Y0MIFvJF P2jwBSUY/HzUxTKv4H+wOuewk9Qufe6ZuDZF59HCQdlBJRBd7sbm5rcCHsSKUOFVd94Y lRe4+/XCUDh0r3d26nb62KQHWwGtIfIjnqNcP4FxbtmsltqZB8vURa6tenngvDhqrgxm TfVeNeRNCAQS8vxFB1NDE+cmaLey1WAANCYDzV58Zj9skOdN7Q2UxAfYVYkj+4CTV+zf FajA==
X-Gm-Message-State: AN3rC/7HxbWbpzEZEBDZMu+o+Kp4rWSRmVOZ7CeGw+tvlQtyFWzIOAk4 jTXsZD43mhLba9Zeac16wAMRaDyCSw==
X-Received: by 10.202.226.81 with SMTP id z78mr1557591oig.96.1492096893355; Thu, 13 Apr 2017 08:21:33 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Thu, 13 Apr 2017 08:21:32 -0700 (PDT)
In-Reply-To: <06e001d2b44f$340c40c0$4001a8c0@gateway.2wire.net>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <m2lgr5yttn.wl-randy@psg.com> <b5846131-d912-b288-670b-2f74c901b2d5@gmail.com> <06e001d2b44f$340c40c0$4001a8c0@gateway.2wire.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 13 Apr 2017 11:21:32 -0400
X-Google-Sender-Auth: kck7td_Ya-Hm7ZfD7ltw1BzsCYU
Message-ID: <CAMm+LwhTHo3oD7x1Hr6nSw7ZYUR7cxHo9+1S6Zv2ddB9DJ5hjA@mail.gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: "tom p." <daedulus@btconnect.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1141b3124c8aca054d0de1ae
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gr-ptU0gJHps9_TFkudjt5_LnC4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 15:21:36 -0000

--001a1141b3124c8aca054d0de1ae
Content-Type: text/plain; charset=UTF-8

The problem with the current state of unpredictability is that the trust
and good faith which previously underpinned the actions of the authorities
has been stripped away.

When you have a politician ranting to a mob that Muslims and Mexicans won't
be allowed in and they get elected, that has consequences. All the actions
that have in the past been dismissed as unrepresentative are being held up
as representative examples.

The idea of a security concern that only happens to affect specific
airlines flying specific routes is rather difficult for me to accept. When
it turns out that the only two governments to impose the restrictions just
so happen to have a commercial interest in establishing a non tariff
barrier to protect their own hub airports against competition, one does ask
if security is merely being used as a pretext for a measure designed to
protect trade interests, not people.

The system of international relationships and connections depends on trust.
I for one do not see any reason to give any politician the benefit of the
doubt when I am taking them at their word.

What is said, cannot be unsaid. There are very good reasons why politicians
with long experience in the system do not attempt to gain office using the
methods that characterized 2016. It is one thing to gain office, quite
another to gain power.

--001a1141b3124c8aca054d0de1ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
 problem with the current state of unpredictability is that the trust and g=
ood faith which previously underpinned the actions of the authorities has b=
een stripped away.</div><div class=3D"gmail_default" style=3D"font-size:sma=
ll"><br></div><div class=3D"gmail_default" style=3D"font-size:small">When y=
ou have a politician ranting to a mob that Muslims and Mexicans won&#39;t b=
e allowed in and they get elected, that has consequences. All the actions t=
hat have in the past been dismissed as unrepresentative are being held up a=
s representative examples.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
">The idea of a security concern that only happens to affect specific airli=
nes flying specific routes is rather difficult for me to accept. When it tu=
rns out that the only two governments to impose the restrictions just so ha=
ppen to have a commercial interest in establishing a non tariff barrier to =
protect their own hub airports against competition, one does ask if securit=
y is merely being used as a pretext for a measure designed to protect trade=
 interests, not people.</div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">T=
he system of international relationships and connections depends on trust. =
I for one do not see any reason to give any politician the benefit of the d=
oubt when I am taking them at their word.</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">What is said, cannot be unsaid. There are very good reason=
s why politicians with long experience in the system do not attempt to gain=
 office using the methods that characterized 2016. It is one thing to gain =
office, quite another to gain power.</div></div>

--001a1141b3124c8aca054d0de1ae--


From nobody Thu Apr 13 08:30:44 2017
Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A061294A2; Thu, 13 Apr 2017 08:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_HELO_PASS=-0.001, 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=joelhalpern.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 CnfCqFH7epPv; Thu, 13 Apr 2017 08:30:35 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 3527F12949F; Thu, 13 Apr 2017 08:30:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4C9F41C01FD; Thu, 13 Apr 2017 08:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1492097434; bh=mlvT0E/dBV2Kd0ccxNA2LOqLrloIIpFwg40zniZBJno=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=CWyso0z/Ek7qWWdXqyapxtB2qA/OEVl5cbxV2xnvUFBr4eEg/nIx5gHlpTwvHAvBp AgI0vGQPOxyil18ieIXANZhqEdRXn7RUjOqdI1NFUhNT9Tbq3uzxlsAhjEoTwNbd5Q 2XLd03BUEjVapbvGOp//ZC4iOyTnaROHSDGWw+kU=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 3B9BB1C017B; Thu, 13 Apr 2017 08:30:33 -0700 (PDT)
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie> <48E1A67CB9CA044EADFEAB87D814BFF64B608B76@eusaamb107.ericsson.se> <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <e9b4a11b-13d1-046b-b4b5-adaf47b44c6a@joelhalpern.com>
Date: Thu, 13 Apr 2017 11:30:32 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <684f067b-6ad2-ac8d-5470-5312aa5979f7@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dA3XGwRDzvqksROWCaPw7gBsuWc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 15:30:37 -0000

In addition to Eric's well-said point, adamance is probably not the most 
important factor.

To make up numbers, if 3/4 of the community thinks we should continue to 
meet in the US, 23 or so percent think we shouldn't, and a small number 
of people are adamant that we shouldn't meet in the US, the much larger 
number of quiet people on both sides of the issue is FAR more important 
than a small number of adamant voices.

In fact, we have a version of this problem with almost all of our 
process discussions, wherein we weigh the strident voices on both sides 
much higher than the interested, reasoned, but quiet participants.

Yours,
Joel

On 4/13/17 4:45 AM, Stephen Farrell wrote:
>
>
> On 13/04/17 09:30, Eric Gray wrote:
>> Stephen,
>>
>> Your argument seems to assume that people should feel a need to
>> publicly justify their feelings on any topic.
>
> No I did not argue that at all.
>
>>
>> That is simply not the case.
>
> I agree.
>
> OTOH, if nobody were in fact to adamantly argue in pubic to
> continue near term meetings in the US, then I do think that
> (as I already said) that is something the IAOC ought factor
> into their considerations.
>
> S.
>
>
>>
>> -- Eric
>>
>> -----Original Message----- From: ietf [mailto:ietf-bounces@ietf.org]
>> On Behalf Of Stephen Farrell Sent: den 13 april 2017 02:44 To: Joel
>> M. Halpern <jmh@joelhalpern.com>; ietf@ietf.org; iaoc@ietf.org; IETF
>> Announcement List <ietf-announce@ietf.org> Subject: Re: Update on
>> feedback on US-based meetings, and IETF 102
>>
>>
>> Hiya,
>>
>> On 13/04/17 01:27, Joel M. Halpern wrote:
>>>
>>> I think that many of us take it as given taht it is desirable to
>>> meet in the US.
>>
>> I do not doubt that many IETFers likely think that. And I almost
>> agree with it.
>>
>> My only problem is that I'm sadly no longer sure that the present
>> tense is correct in your statement, which is just a shame.
>>
>> I fully agree with your statement cast into the past tense.
>>
>> I really hope that the future tense variant will be something with
>> which I can agree. At the moment I do not for the reasons stated (to
>> do with unpredictability).
>>
>>> In contrast, I am quite sure that folks who felt strongly that we
>>> should not meet in the US understood that for that to happen, they
>>>  needed to make their voices heard.
>>
>> That's a fair point. I think though that it also puts on onus on any
>> folks who adamantly think we ought continue to meet in the US, to
>> also publicly justify that, given the opposite arguments already
>> voiced on the list. (I do realise there's a danger there of folks
>> going OTT, so I hope we all impose a bit of self-restraint if making
>> arguments either way.)
>>
>> Note though that my query was with Leslie's assertion that the survey
>> result and list traffic reflected similar levels of adamant
>> assertion. (I wasn't doubting that some of us are likely adamant
>> about any random or non-random topic:-)
>>
>> Cheers, S.
>>
>


From nobody Thu Apr 13 08:50:13 2017
Return-Path: <julien.meuric@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 990FA1294B3; Thu, 13 Apr 2017 08:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 TU4-frcTDRmu; Thu, 13 Apr 2017 08:50:10 -0700 (PDT)
Received: from r-mail1.rd.orange.com (r-mail1.rd.orange.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id B67E3129455; Thu, 13 Apr 2017 08:50:09 -0700 (PDT)
Received: from r-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id CCDF6A4414A; Thu, 13 Apr 2017 17:50:08 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail1.rd.orange.com (Postfix) with ESMTP id AB51CA44115; Thu, 13 Apr 2017 17:50:08 +0200 (CEST)
Received: from [10.193.71.173] (10.193.71.173) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.319.2; Thu, 13 Apr 2017 17:50:08 +0200
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: <lionel.morand@orange.com>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com> <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com> <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.com> <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>
CC: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
Message-ID: <a9e752e5-64df-3dc1-c1b9-74908b477c10@orange.com>
Date: Thu, 13 Apr 2017 17:50:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rw169rjw5neoNRNfDVArCw564-s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 15:50:12 -0000

Hi Lionel,

Thank you for following up. I think we're almost done. My answers below
as [JM2].

Julien


Apr. 12, 2017 - <lionel.morand@orange.com:

[snip]

>>> =====
>> [JM] NACK! ;-) Actually, the passive mode is advertised using the 
>> Stateful-capability-object TLV with the U bit unset, the active 
>> mode by setting the U bit.
>> 
> [LM2] "il faut être sorti de Saint-Cyr pour comprendre" as we say in
>  french :)

[JM2] Let me check with my colleague next door... ;-)

> Could be good to add something like "(as indicated by the U-bit clear
> in Stateful-capability-object)"

[JM2] ACK!

> 
>>> =====
>>> 
>>> Note that even if the update capability has not been advertised,
>>>  a PCE can still accept LSP Status Reports from a PCC and build 
>>> and maintain an up to date view of the state of the PCC's LSPs.
>>> 
>>> [LM] I don't undersand. Is it not in contradiction with
>>> 
>>> "If the PCEP Speaker on the PCE supports the extensions of this 
>>> draft but did not advertise this capability, then upon receipt of
>>> a PCRpt message from the PCC, it MUST generate a PCErr with 
>>> error- type 19 (Invalid Operation), error-value 5 (Attempted LSP
>>>  State Report if active stateful PCE capability was not 
>>> advertised) (see Section 8.5) and it SHOULD terminate the PCEP 
>>> session."
>>> 
>>> Or does it mean that there is another way than PCRpt message for
>>>  the PCC to send LSP status reports to the PCE?
>>> 
>>> Jon> ACK.  I think that the statement in the draft is bogus and
>>> I propose to delete this sentence from it.
>>> 
>>> =====
>> [JM] I do not think that the text is bogus: - case 1: no advertised
>> capability on update but advertised on report (i.e. passive
>> stateful) => no error message; - case 2: no advertised capability
>> on update nor report (i.e. stateless) => error.
> [LM2] After multiple readings and thanks to your explanation, I think
> I have understood. Am I correct saying that the PCE will accept LSP
> Status Reports from a PCC ONLY if the stateful PCE capability has
> been advertised (i.e. Stateful Capability TLV with the 'LSP Update'
> Flag cleared)? 

[JM2] Almost... but not fully! Your main sentence is true, your
parenthesis is not. The latter should be rephrased as "i.e. inclusion of
the Stateful Capability TLV". Indeed, passive (report, no update) and
active (report + update) are two possible modes within stateful, i.e. we
do not care about the 'LSP Update' flag when talking about
Report/"stateful at large".

If it is the case, is it really required to keep this
> text, as in the previous paragraph we find the conditions to
> accept/reject reports from the PCC?

[JM2] AFAIU, the sentence clarifies the fact that an error on an update
attempt does not lead to an error on the report feature.

[JM2] Side note to the (RFC?) editor, on page 11: s/this draft/this
document/


From nobody Thu Apr 13 09:12:11 2017
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B3C129455; Thu, 13 Apr 2017 09:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Level: 
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 zlsFUK_nx2ym; Thu, 13 Apr 2017 09:12:07 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36DFB12922E; Thu, 13 Apr 2017 09:12:07 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 2EBCE1C0410; Thu, 13 Apr 2017 18:12:05 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.24]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 0C58B80158; Thu, 13 Apr 2017 18:12:05 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0319.002; Thu, 13 Apr 2017 18:12:03 +0200
From: <lionel.morand@orange.com>
To: MEURIC Julien IMT/OLN <julien.meuric@orange.com>
CC: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: =?iso-8859-1?Q?RE=A0:_Re:_[Pce]_Review_of_draft-ietf-pce-stateful-pce-18?=
Thread-Topic: =?iso-8859-1?Q?RE=A0:_Re:_[Pce]_Review_of_draft-ietf-pce-stateful-pce-18?=
Thread-Index: AQHStHCvrFjPsc1mcUWSYeXwRZ/bqw==
Date: Thu, 13 Apr 2017 16:12:02 +0000
Message-ID: <29620_1492099925_58EFA355_29620_12579_1_ffca0df1-733d-49f7-a832-f483750b8ecd@OPEXCLILM7D.corporate.adroot.infra.ftgroup>
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com> <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com> <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.com> <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>, <a9e752e5-64df-3dc1-c1b9-74908b477c10@orange.com>
In-Reply-To: <a9e752e5-64df-3dc1-c1b9-74908b477c10@orange.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_ffca0df1733d49f7a832f483750b8ecdOPEXCLILM7Dcorporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rag4B0wEcJjv3LyAnvsjhCc-OyQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 16:12:10 -0000

--_000_ffca0df1733d49f7a832f483750b8ecdOPEXCLILM7Dcorporateadr_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Everything is fine for me.
Thank you.

Regards,

Lionel

Le 13 avr. 2017 17:50, Julien Meuric <julien.meuric@orange.com> a =E9crit :
Hi Lionel,

Thank you for following up. I think we're almost done. My answers below
as [JM2].

Julien


Apr. 12, 2017 - <lionel.morand@orange.com:

[snip]

>>> =3D=3D=3D=3D=3D
>> [JM] NACK! ;-) Actually, the passive mode is advertised using the
>> Stateful-capability-object TLV with the U bit unset, the active
>> mode by setting the U bit.
>>
> [LM2] "il faut =EAtre sorti de Saint-Cyr pour comprendre" as we say in
>  french :)

[JM2] Let me check with my colleague next door... ;-)

> Could be good to add something like "(as indicated by the U-bit clear
> in Stateful-capability-object)"

[JM2] ACK!

>
>>> =3D=3D=3D=3D=3D
>>>
>>> Note that even if the update capability has not been advertised,
>>>  a PCE can still accept LSP Status Reports from a PCC and build
>>> and maintain an up to date view of the state of the PCC's LSPs.
>>>
>>> [LM] I don't undersand. Is it not in contradiction with
>>>
>>> "If the PCEP Speaker on the PCE supports the extensions of this
>>> draft but did not advertise this capability, then upon receipt of
>>> a PCRpt message from the PCC, it MUST generate a PCErr with
>>> error- type 19 (Invalid Operation), error-value 5 (Attempted LSP
>>>  State Report if active stateful PCE capability was not
>>> advertised) (see Section 8.5) and it SHOULD terminate the PCEP
>>> session."
>>>
>>> Or does it mean that there is another way than PCRpt message for
>>>  the PCC to send LSP status reports to the PCE?
>>>
>>> Jon> ACK.  I think that the statement in the draft is bogus and
>>> I propose to delete this sentence from it.
>>>
>>> =3D=3D=3D=3D=3D
>> [JM] I do not think that the text is bogus: - case 1: no advertised
>> capability on update but advertised on report (i.e. passive
>> stateful) =3D> no error message; - case 2: no advertised capability
>> on update nor report (i.e. stateless) =3D> error.
> [LM2] After multiple readings and thanks to your explanation, I think
> I have understood. Am I correct saying that the PCE will accept LSP
> Status Reports from a PCC ONLY if the stateful PCE capability has
> been advertised (i.e. Stateful Capability TLV with the 'LSP Update'
> Flag cleared)?

[JM2] Almost... but not fully! Your main sentence is true, your
parenthesis is not. The latter should be rephrased as "i.e. inclusion of
the Stateful Capability TLV". Indeed, passive (report, no update) and
active (report + update) are two possible modes within stateful, i.e. we
do not care about the 'LSP Update' flag when talking about
Report/"stateful at large".

If it is the case, is it really required to keep this
> text, as in the previous paragraph we find the conditions to
> accept/reject reports from the PCC?

[JM2] AFAIU, the sentence clarifies the fact that an error on an update
attempt does not lead to an error on the report feature.

[JM2] Side note to the (RFC?) editor, on page 11: s/this draft/this
document/


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


--_000_ffca0df1733d49f7a832f483750b8ecdOPEXCLILM7Dcorporateadr_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<p dir=3D"ltr">Everything is fine for me. <br>
Thank you. <br>
<br>
Regards, <br>
<br>
Lionel</p>
<div class=3D"x_quote">Le 13 avr. 2017 17:50, Julien Meuric &lt;julien.meur=
ic@orange.com&gt; a =E9crit :<br type=3D"attribution">
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Hi Lionel,<br>
<br>
Thank you for following up. I think we're almost done. My answers below<br>
as [JM2].<br>
<br>
Julien<br>
<br>
<br>
Apr. 12, 2017 - &lt;lionel.morand@orange.com:<br>
<br>
[snip]<br>
<br>
&gt;&gt;&gt; =3D=3D=3D=3D=3D<br>
&gt;&gt; [JM] NACK! ;-) Actually, the passive mode is advertised using the =
<br>
&gt;&gt; Stateful-capability-object TLV with the U bit unset, the active <b=
r>
&gt;&gt; mode by setting the U bit.<br>
&gt;&gt; <br>
&gt; [LM2] &quot;il faut =EAtre sorti de Saint-Cyr pour comprendre&quot; as=
 we say in<br>
&gt;&nbsp; french :)<br>
<br>
[JM2] Let me check with my colleague next door... ;-)<br>
<br>
&gt; Could be good to add something like &quot;(as indicated by the U-bit c=
lear<br>
&gt; in Stateful-capability-object)&quot;<br>
<br>
[JM2] ACK!<br>
<br>
&gt; <br>
&gt;&gt;&gt; =3D=3D=3D=3D=3D<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Note that even if the update capability has not been advertise=
d,<br>
&gt;&gt;&gt;&nbsp; a PCE can still accept LSP Status Reports from a PCC and=
 build <br>
&gt;&gt;&gt; and maintain an up to date view of the state of the PCC's LSPs=
.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; [LM] I don't undersand. Is it not in contradiction with<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; &quot;If the PCEP Speaker on the PCE supports the extensions o=
f this <br>
&gt;&gt;&gt; draft but did not advertise this capability, then upon receipt=
 of<br>
&gt;&gt;&gt; a PCRpt message from the PCC, it MUST generate a PCErr with <b=
r>
&gt;&gt;&gt; error- type 19 (Invalid Operation), error-value 5 (Attempted L=
SP<br>
&gt;&gt;&gt;&nbsp; State Report if active stateful PCE capability was not <=
br>
&gt;&gt;&gt; advertised) (see Section 8.5) and it SHOULD terminate the PCEP=
 <br>
&gt;&gt;&gt; session.&quot;<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Or does it mean that there is another way than PCRpt message f=
or<br>
&gt;&gt;&gt;&nbsp; the PCC to send LSP status reports to the PCE?<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Jon&gt; ACK.&nbsp; I think that the statement in the draft is =
bogus and<br>
&gt;&gt;&gt; I propose to delete this sentence from it.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; =3D=3D=3D=3D=3D<br>
&gt;&gt; [JM] I do not think that the text is bogus: - case 1: no advertise=
d<br>
&gt;&gt; capability on update but advertised on report (i.e. passive<br>
&gt;&gt; stateful) =3D&gt; no error message; - case 2: no advertised capabi=
lity<br>
&gt;&gt; on update nor report (i.e. stateless) =3D&gt; error.<br>
&gt; [LM2] After multiple readings and thanks to your explanation, I think<=
br>
&gt; I have understood. Am I correct saying that the PCE will accept LSP<br>
&gt; Status Reports from a PCC ONLY if the stateful PCE capability has<br>
&gt; been advertised (i.e. Stateful Capability TLV with the 'LSP Update'<br>
&gt; Flag cleared)? <br>
<br>
[JM2] Almost... but not fully! Your main sentence is true, your<br>
parenthesis is not. The latter should be rephrased as &quot;i.e. inclusion =
of<br>
the Stateful Capability TLV&quot;. Indeed, passive (report, no update) and<=
br>
active (report &#43; update) are two possible modes within stateful, i.e. w=
e<br>
do not care about the 'LSP Update' flag when talking about<br>
Report/&quot;stateful at large&quot;.<br>
<br>
If it is the case, is it really required to keep this<br>
&gt; text, as in the previous paragraph we find the conditions to<br>
&gt; accept/reject reports from the PCC?<br>
<br>
[JM2] AFAIU, the sentence clarifies the fact that an error on an update<br>
attempt does not lead to an error on the report feature.<br>
<br>
[JM2] Side note to the (RFC?) editor, on page 11: s/this draft/this<br>
document/<br>
<br>
</div>
</span></font>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_ffca0df1733d49f7a832f483750b8ecdOPEXCLILM7Dcorporateadr_--


From nobody Thu Apr 13 11:36:12 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7F8C1315D4; Thu, 13 Apr 2017 11:36:03 -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, RP_MATCHES_RCVD=-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 dWwf9AX85z2B; Thu, 13 Apr 2017 11:36:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA4C1315D7; Thu, 13 Apr 2017 11:35:39 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cyjaj-000HaZ-Iy; Thu, 13 Apr 2017 14:35:37 -0400
Date: Thu, 13 Apr 2017 14:35:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: ietf@ietf.org, iaoc@ietf.org
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Message-ID: <3DF53F6ACE338CACF247F910@PSB>
In-Reply-To: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OcSBoz9KErZPTnKyOULqaiF7fUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 18:36:04 -0000

--On Thursday, April 13, 2017 01:00 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> Is that my bias in reading the list traffic or did I miss some
> mail, or is it possible that the (public) list traffic and
> (relatively private) survey responses are less similar that
> your mail implies?
> 
> That last wouldn't be surprising, but I'd hope that in that
> case some of the people who filled in the survey who adamantly
> said we ought continue to meet in the US would be willing to
> justify that on the list. If none were, then I think the IAOC
> ought consider that as a relevant input in their decision
> making. (Not as a winning argument, but as a relevant thing.)

Stephen (and others, with a specific nod to Randy's and Tom's
comments):

As least a few of us interpreted the IAOC as requesting comments
to their special list, found the "cities" and "US meetings"
inquiries inseparable, and decided to adhere to that request.
Dismissing our comments because we did so seems inappropriate.
In addition, some relevant comments were made during the
Mtgvenue session in Chicago and presumably recorded in its
minutes; especially if the request was for advice to the IAOC
rather than a general discussion, it hardly seemed necessary to
repeat those comments here.

However, to reprise while trying to remain brief:

(1) We are living in very unstable times in which reliable
predictions of the long-term future, or even the future for the
3 to 5 years out that the IAOC thinks the community has told it
to plan meetings, is even more difficult than usual. There are
strong reasons, connected to our traditional criteria such as
locations near where concentrations of the participants live and
appropriate facilities, for meeting in the US, and we should
avoid meeting in the US only if the circumstances and logic make
sense.

(2) I don't believe in canceling, or refusing to hold, meetings
in a particular location to make a political point or to punish
a government that we see as behaving badly, if only for the
purely pragmatic reason that few governments are likely to pay
any attention at all to where we do or do not hold meetings.
Certainly the US is not one of the exceptions.   However, if we
do make decisions on that basis --and some of the on-list
comments have sounded very much like that-- then we'd better be
ready to schedule meetings for those countries, on
shorter-than-usual notice if necessary, to reward them if the
policies are changed.

(3) Circumstances change.  Not just political circumstances (who
would have predicted a year ago that the US would be in its
present state now?), but there is always a risk of hotel or
neighborhood remodeling or construction and natural and
human-made disasters that could severely impede a meeting or
attendance at it.  It seems to me to be very important that we
think through the circumstances under which we would pull the
plug on a venue on short notice -- whether to try to find a
different location or to go largely or entirely remote -- and,
as others suggested during the mtgvenue session, that we keep
that set of discussions rather separate from how we do
longer-term meeting planning.

(4) I have no idea how to predict likely US policies toward
visitors (or residents traveling outside the country and trying
to return) six months out, much less three to five years in the
future.  The government's sudden policy reversals in several
other areas in the last two weeks should add to everyone's
uncertainty, as should the possibility that the courts will
continue to block obnoxious policies and punish those who
profile and harass selected visitors.   The threats to require
passwords, inspection of phones, and similar nonsense of people
who are now covered by visa waivers may turn out to be a real
issues or as hollow as promises to brand China a currency
manipulator turned into during the last 48 hours or so.

Equally important, it is impossible to predict British policies
as Brexit evolves nor what other countries might do in
retaliation or response to those policies, US actions, etc.
Given other forces in the world, I think it would be unwise to
place large bets on the Schengen agreements being unchanged
three or five years from now, especially where holders of non-EU
passports are concerned.  Similar issues apply in Asia: for
example, I hope that we won't see sufficient destabilization on
the Korean Peninsula to make a meeting in Seoul or even Busan
inadvisable, but, if the macho chest-pounding, posturing, and
implicit threats by assorted crazy-spectrum people continues,
one never knows.   I think it is pretty safe to suggest that it
would be unwise to plan a meeting for Damascus or Aleppo three
years from now, but no one has seriously proposed either city.  

However, within sensible limits (with the two Syrian examples
mentioned as examples of non-sensible cases), I'm opposed to
making _any_ changes in our long-term meeting plans based on
rapidly changing political considerations, including but not
limited to events in the US or UK in the last year.  Again, I
think it is important to monitor things as meetings get close
and to have some community consensus about the circumstances
under which we would make significant changes in meeting plans,
but deciding to hold (or not hold) a meeting in the US based on
fears or fantasies about what has happened in the last six
months (or overconfidence about how those things will play 9ut)
and where those things might lead makes no sense to me.

best,
    john








From nobody Thu Apr 13 11:38:28 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409D51315BE for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 11:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.802
X-Spam-Level: 
X-Spam-Status: No, score=-0.802 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 6C2wl-J3Cbtt for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 11:38:26 -0700 (PDT)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (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 7E9661315C0 for <ietf@ietf.org>; Thu, 13 Apr 2017 11:38:25 -0700 (PDT)
Received: from resomta-po-02v.sys.comcast.net ([96.114.154.226]) by resqmta-po-06v.sys.comcast.net with SMTP id yjcAckbzwbempyjdQcSVSW; Thu, 13 Apr 2017 18:38:24 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1492108704; bh=QBnpMvwBRRsScWIkldAe1J2/6N6vAxcLDF4jekq4RFU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=hVidVourwM+s9Z2+nwemfjk1SDjbPFOHCF1tKUSBflcEdxN8W0rULQEa2UV9TrTxz or9JKBTV2nk/LD1x2L2HJgH/pz3TyQShJxSaAicjGZ3Bbi65figRGtFjFc8H9dmo0m N9Bs5PVtdmOxg0L6enLmGGNu6MbxUMP15euWBC3pl1mET/XTmjuZ8i+Xr9ZUseMRSp 0qmgBQJCixDjPi5+ykmetL9+9jifejouee06Dq6zMB9ycCpKyWkSO59/Tc7h00N0Wu LXgqjpCWZf66+1RVjmDixQX7NX/kLo9hIlphZ52yiFjz4a8UAYoe8G4f0kWwBA42kG gk/3/6TTO6dcw==
Received: from [10.230.64.36] ([74.121.22.10]) by resomta-po-02v.sys.comcast.net with SMTP id yjdHczxkOlZOxyjdKcMXk1; Thu, 13 Apr 2017 18:38:22 +0000
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: ietf@ietf.org
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <43378975-daf3-0170-35c7-b57e03b834b2@comcast.net>
Date: Thu, 13 Apr 2017 14:37:36 -0400
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: <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfNVREFHXgxMA0QpdbiJf3zMoueA6iWH+p6NM1Q+jDpDN83L9kNCuvjM2ULAaprXVkD98SBCWaEk+LTkNYiIMwL2fYCfdiVS8eQTqLnPz2AGB2+68dE+Z q9nrKQ7AdH3dwW/41MbBqXT7p6ITAhs+KWKQVCQa0TVmwhLB0vm/ZuO9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jglsB5c1-7lGZEuadi2jrJgCwlQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 18:38:27 -0000

On 4/12/2017 8:44 PM, Stephen Farrell wrote:
> That's a fair point. I think though that it also puts on onus on
> any folks who adamantly think we ought continue to meet in the US,
> to also publicly justify that, given the opposite arguments already
> voiced on the list.


Does it also put the onus on say the UK and the rest of the EU to gaze 
into the future and promise that the breakup will be amicable and that 
there will be no changes in the current passage rules between the two or 
even between EU members?

As much as you might like to require someone to prove a negative - it's 
generally understood that proposing that someone do so tends to be more 
of a political debate trick than anything else.

Looking back in history, immediately after 9/11 - arguably the biggest 
provocation the US has received during the Internet era - 4 out of the 5 
IETF meetings immediately after 9/11 were held in the US under the 
increased travel scrutiny that we take for granted now and we adapted.  
The current questions are or need to be:  What are the changes and can 
we adapt.

We have a US President that has made big claims and broad pronouncements 
- but here's the thing.  He's not a dictator and he's bound by strong 
laws and constitutional requirements that limit his reach.   Basing a 
decision on whether or not to hold meetings in the US based on only what 
Trump says and does vs what he might say and do vs looking at what 
actually happens (e.g. travel restrictions held in abeyance due to 
perceived constitutional violations) seems to be taking counsel of fears 
rather than counsel of facts.

I would suggest that we not cancel SF and use it to gain FACTS. I would 
suggest that by the time SF comes around the bulk of changes (if any) 
will have occurred and we will be able to quantify their impact on the 
IETF participants in the scope of that meeting and whether future 
meetings will need to be held elsewhere for a period of time or whether 
we're able to adapt.  I would further suggest that the impact of having 
one "bad" meeting would be minimal in the broader scheme of things vs 
not having a consensus and agreement on both the actual problem and the 
solution to said problem.


Mike





From nobody Thu Apr 13 11:42:55 2017
Return-Path: <dave.taht@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79D0712EAAE; Thu, 13 Apr 2017 11:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 fbYBcjGXuQNn; Thu, 13 Apr 2017 11:42:51 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::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 6B0511315A5; Thu, 13 Apr 2017 11:42:49 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id h67so55171800qke.0; Thu, 13 Apr 2017 11:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hI20XLqyoyecwEWs3pP0SCwcqGP6WH0lrQEyILRJACQ=; b=Z/Lw/Gkd7aOVhEGJTJez+kPHh2MmUeCXFJ90VlJB+QoJye7Po/X/Cl2fUsFYgeDN6s OQI5BnqVNXc4ZkRAMVelBKyNkPHO3jTWXyaDiOLPsTmqv+FrBhr5deIQDbwqo570sP1S /iBA5ouCtc2U1tLB9z5yQ0QLQAF2u8TBt8OFE9EvVjDhGD9rlWEcRfYWRBTaEE8AowSY Ynmq5eCt+4Gsj194AgRipfstzq+hf640OkCJXEWOsIInd9GSgag00mgBy8uv+Q+GSd7+ 6fKdmFSjt5994dtDyYkSsbfDuBSwuaJ9qK4EDHnluFtsVryatBtesr9OkfTuA1rIBxvY KcZw==
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=hI20XLqyoyecwEWs3pP0SCwcqGP6WH0lrQEyILRJACQ=; b=MOCU0zXLujIlJIAxTBaZFJgSmLU1B1Fd4F9mok3XUjggMv3u8bU2JqJ6UyHPEsRH4v il6j6g3SQoBqUpLv8b7oH6fprpUGnieTVxAkdwRVNFHL7XJOyoI+y668YqcXQA2ND9eA guBPn2AfNfIWKM+Yr0o9deLwxz/VNmZNlIr5tNeCslJYknyun5Gi9EnSgrRAb5Nalyoi hxznJxwTE1TVFLN4w0H6zn6jikvejeX6RTknUzdUZsvvohXyFUdKRIYMV8tURC2dULDw p5hKAfu0anSy+t3NmyaWalL9oc+R+mw/i89hQ02IXbqO4cx2l2dpZdcZWoxrgukSnEEn zDJQ==
X-Gm-Message-State: AN3rC/6iI3s1+WIL0dfZhhw2kaAf0FdGZ30dix3nnzVI9utgvmCNof9i B2l7KBGZSKy0hm8/hLydWUTVwv2HCA==
X-Received: by 10.233.222.3 with SMTP id s3mr3683281qkf.17.1492108968682; Thu, 13 Apr 2017 11:42:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.140.8 with HTTP; Thu, 13 Apr 2017 11:42:48 -0700 (PDT)
In-Reply-To: <3DF53F6ACE338CACF247F910@PSB>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <3DF53F6ACE338CACF247F910@PSB>
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, 13 Apr 2017 11:42:48 -0700
Message-ID: <CAA93jw7ScrfQQc2FsN1mHupniC_CCyP=uO87A_imLpCFufH3mA@mail.gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: John C Klensin <john-ietf@jck.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, iaoc@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ECJisAqhj15do1h9ZSp4Aci9zSw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 18:42:53 -0000

I find meetecho to have evolved to being an effective tool, and no
longer intend to attend ietf meetings in person. I'll miss the beer,
company and cookies; won't miss the travel and hotel hassles.


From nobody Thu Apr 13 13:36:56 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C13D5126D74; Thu, 13 Apr 2017 13:36: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 ESqaoXIaxV4g; Thu, 13 Apr 2017 13:36:46 -0700 (PDT)
Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (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 4DDBE12957F; Thu, 13 Apr 2017 13:36:46 -0700 (PDT)
Received: by mail-qt0-x243.google.com with SMTP id o36so9413816qtb.2; Thu, 13 Apr 2017 13:36:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=wZ0xjRLmeHfcEjov0hd27CKgsfd72wX2xok98aT6NKU=; b=m4hdwwHlf3W9fQRZ5afS+8vo4VaDU+bf5CDMnjlF3zDwCJ8+nrEmbKPq0PD49U2lkc gjHXSqg8zMJjUQ/PUGsJhGaUZtxWgslT8642dXNDrfHISWi8uIB39tjREssJtWRlZgNj oTnREh4jVCcdu72sJZWUNJg3XcC1ti9sTHcaFmJXCSwiKzNNegvOr+UydQygkeZ55qru M0/bNcE/Ome5ZdFH0X/VuFhGXgWNZmIWr8o6wt3YHyRbAEpeRaGAs9GQBKWXCqVYSgnP Y/dbOZYGfd0tNl7U+FKKqIRJFvHFMJUzZrxDMxYtU+cEcxkW4Oy56sJ7NMa/be4k8U74 QPlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=wZ0xjRLmeHfcEjov0hd27CKgsfd72wX2xok98aT6NKU=; b=QnFFRWr3x+JNNukgGkQrC8p5k/s2oADg0Ejk9YOOpJcXjctG4jBEyChS0rX3CgOntV BpEIyI9ZKvSFM7EgK6yT56/QMSmhHYv5fQqKqv3Wn84Qz/vPRiZfgbznzzz9UHJ6EgUk j6GXoFLQkNVR1bLyXnfPqaCaoTAQ4nVGfUjZJmFDe+tebvifYDlsbOAkn7hlkOj0xWz/ nFPYbE698wfsDf/o4/4xKOimV79TatQ9i2muVpbxuXjGrgh613EC44wDdOJyiPfoyCAk siEV00sqSNEV+s53xcbguPO82FGDdWWH24yZqq2mz5v0SvTFh6AqiiIiNaey37CxS84r CBDw==
X-Gm-Message-State: AN3rC/5Oq1fqWnbvbQ5kd50Q6CwKmP1m/IgqgYIg59eK/1PZpuSuGzH3 aDaiKn+iYLWUyQ==
X-Received: by 10.237.34.125 with SMTP id o58mr4179352qtc.108.1492115805392; Thu, 13 Apr 2017 13:36:45 -0700 (PDT)
Received: from [172.19.37.144] ([2001:4878:8000:60:6123:c904:e972:b002]) by smtp.gmail.com with ESMTPSA id p77sm722599qka.39.2017.04.13.13.36.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Apr 2017 13:36:44 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: ietf@ietf.org, iaoc@ietf.org
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Date: Thu, 13 Apr 2017 16:36:43 -0400
Message-ID: <3233BEC0-DE8F-4538-AF6C-2D2B2D60DD9C@gmail.com>
In-Reply-To: <3DF53F6ACE338CACF247F910@PSB>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <3DF53F6ACE338CACF247F910@PSB>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4bNENfzjcJwuYikuzGSJMMT1HA4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 20:36:49 -0000

+1

On 13 Apr 2017, at 14:35, John C Klensin wrote:

> I'm opposed to
> making _any_ changes in our long-term meeting plans based on
> rapidly changing political considerations, including but not
> limited to events in the US or UK in the last year.  Again, I
> think it is important to monitor things as meetings get close
> and to have some community consensus about the circumstances
> under which we would make significant changes in meeting plans,
> but deciding to hold (or not hold) a meeting in the US based on
> fears or fantasies about what has happened in the last six
> months (or overconfidence about how those things will play 9ut)
> and where those things might lead makes no sense to me.


From nobody Thu Apr 13 16:02:25 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3135812EAD1; Thu, 13 Apr 2017 16:02:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: v6ops@ietf.org, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  ietf@ietf.org
Subject: Genart last call review of draft-ietf-v6ops-unique-ipv6-prefix-per-host-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149212453015.27548.13210718340210615403@ietfa.amsl.com>
Date: Thu, 13 Apr 2017 16:02:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HCtbj2Nz8pmXB3kA3XBcJ5iXce0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 23:02:10 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-v6ops-unique-ipv6-prefix-per-host-??
Reviewer: Joel Halpern
Review Date: 2017-04-13
IETF LC End Date: None
IESG Telechat date: Not scheduled for a telechat

Summary: This document is almsot ready for publication as an RFC.

Major issues: N/A

Minor issues:
    The proposed status seems questionable.  We as a community are not
recommending that operators assign unique prefixes to hosts.  This
document is saying "if you want to do that, here is a way, using
existing tools, to make that work."  The document also recommends
specific setting of other flags (the O flag in the RA, for example)
that are not closely coupled to the particular topic.  This looks like
an ordinary Informational RFC.  I would have no concern with this
being published with that label.

Nits/editorial comments: 
    As per the nits checker, the document uses RFC 2119 terminology. 
The usage seems quite appropriate.  The document should therefore cite
RFC 2119.
    Also, as per the nits checker, the document references RFC 6106. 
It should reference RFC 8106.



From nobody Thu Apr 13 16:59:14 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E0D1276AF; Thu, 13 Apr 2017 16:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level: 
X-Spam-Status: No, score=-4.801 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=microsoft.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 h2Eb-AFn5fGu; Thu, 13 Apr 2017 16:59:02 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0102.outbound.protection.outlook.com [104.47.42.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC029126579; Thu, 13 Apr 2017 16:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=G2ZsdUrm33rZMSK2i+iYZQhZAnVsP7ePcPIBhV34mCw=; b=UVA3dY/vICtzuhNp7qC1dmvi+l2+6ktrSMorrnCHXETEqLuN+ddlTuudjDjF4yTMkaOWgyRkLjxPOrpjouiVdAhCkD/nWpzADS6eeICZVHQpFRRaNzr+z62g1r/o2o40nNonLSfW7wNZnS0Uiqa9J2Dvj7CHklBetdGcJUz2Zf4=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2121.namprd03.prod.outlook.com (10.164.2.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.10; Thu, 13 Apr 2017 23:59:01 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1034.011; Thu, 13 Apr 2017 23:59:00 +0000
From: Orit Levin <oritl@microsoft.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kA=
Date: Thu, 13 Apr 2017 23:59:00 +0000
Message-ID: <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
In-Reply-To: <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [124.74.42.142]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2121; 7:Acny2Gpm73Rjtjh4y1fdgJKq6HqKCx25oVZrc/WT49AAwRi8CO+aZCkv6/d+5MfEtLPIlXll6VedD303PBxRkZhh/3sJJ3uUfKFc42GkWbULUKgSHirXMx20R2YUEsiRa0uG8fWkbcN6A9YgnB5gZfa6R98xqriOdUFFDA8vsUpahvIK1XNeLb4rCOKiA9bkAA8PZmY2nAFzUSVrxVj6Gv4w/zGlMmDRy+ZxRZPEi7kQbMprxqrozf74K9QlQiKkQ4T+y0e5ojE+b7wv/p0I6Fmv6BPR25fN9TXXM7XaLnc8GTTQoG2yBWvdtGzO0ZfH+Sv9uvkfpV3WKIzN/4P2NFMMfts+5dY38VI2FlczZiE=
x-ms-office365-filtering-correlation-id: b06ab864-2084-4960-c2eb-08d482c90e7e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:CY1PR0301MB2121; 
x-microsoft-antispam-prvs: <CY1PR0301MB21215A4F16D7A6959936887AAD020@CY1PR0301MB2121.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(131327999870524)(788757137089)(95692535739014); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(20161123555025)(6072148); SRVR:CY1PR0301MB2121; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2121; 
x-forefront-prvs: 02760F0D1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39850400002)(39860400002)(39840400002)(39450400003)(377454003)(13464003)(129404003)(85664002)(377424004)(8676002)(9686003)(10090500001)(81166006)(6246003)(5005710100001)(8936002)(53546009)(25786009)(122556002)(99286003)(74316002)(5660300001)(55016002)(305945005)(7736002)(86362001)(229853002)(4326008)(7696004)(2900100001)(8990500004)(6306002)(54906002)(86612001)(3846002)(3660700001)(50986999)(38730400002)(53936002)(77096006)(102836003)(33656002)(10290500002)(3280700002)(54356999)(76176999)(6506006)(66066001)(6436002)(189998001)(230783001)(2906002)(2950100002)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2121; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2017 23:59:00.7589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2121
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/urBScRsNp5y-9IraULpn2EpPB_M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 23:59:05 -0000

Hi Les,
Sorry for the delay in response.
Your feedback was very helpful. Below is a refresh of my comments. I tried =
to make them more pointed and some are new.

Summary: This draft is "ready with issues" for publication.

General:
1) For implementers who are familiar with the history and the intent of thi=
s extension, the information in the draft is probably sufficient to serve a=
s a check list for implementing a multi-instance IS-IS router. For all othe=
r readers, the document doesn't contain an overview of the new mode of oper=
ation, i.e. where the instances are not a configuration and an internal imp=
lementation choice only, but are exposed through the protocol to achieve th=
e stated objective. Lacking such an overview, the reader needs to reverse-e=
ngineer the logic behind the documented guidance.
2) The draft talks about "extensions" in plural. Based on a single extensio=
n on the wire and the overall goal of the new mechanism, I would say that i=
t is a single extension only.  How many protocol extensions does this docum=
ent define? If they can be clearly separated, then it needs to be clarified=
 throughout the document. Otherwise, the language throughout the document n=
eeds to be changed from "extensions" to "the extention".
3) Editorial: Please, compare (Diff) the current draft with the published R=
FC 6822. You will find that various RFC Editor corrections got lost in this=
 bis document. Some repeating examples of the lost corrections are "instanc=
e-specific", " topology (or topologies)" and "Type-Length-Value".

My comments below are a result of a reverse-engineering exercise. Please, c=
onsider incorporating the suggested clarifications to improve the document =
readability. I might have misunderstood some of the parts; in such cases, p=
lease, provide an alternative text.

Abstract
1) Add clarification: "This document is not backwards compatible with RFC 6=
822."
2) Par. 2, replace the first two sentences with: "Configuration of multiple=
 protocol instances within a router allow the isolation of resources associ=
ated with each instance. This document introduces a new mode of operation w=
here the protocol instances are not a matter of configuration only, but are=
 exposed through the new protocol extension to achieve the objective stated=
 above."
3) Par. 3 uses both present and future time. Does it mean before and after =
the extension? Please, clarify by spelling out the intent and/or changing t=
he grammar.

1. Introduction
1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the Introd=
uction to improve its logical flow (also related to the next comment).
2) Par 4, sentence #2 says "This document defines an extension to IS-IS to =
allow non-zero instances...". My assumption is that the intent of this draf=
t is to define a single extension, which will improve the routing operation=
s in a number of ways. If this is the case, the quote needs to be replaced =
with "The MI-IS-IS extension, defined in this document, also allows so-call=
ed "non-zero instances"..." .
3) Par 4, sentences #4 and #5 are not sufficient to describe the new mode o=
f operation introduced by this extension. Below is my attempt to describe i=
t. Please, correct, if I got it wrong.
"IS-IS router instances that support this extension are preconfigured with =
unique non-zero Instance Identifiers (IIDs) giving them the name "non-zero =
instances". In addition, MI RTRs MAY (or SHOULD ?) implement the legacy (or=
 so-called "standard") instance of the IS-IS router for backwards compatibi=
lity with legacy IS-IS routers. IID #0 is only used by MI-RTRs to convey in=
formation associated with such standard interface if implemented. See secti=
on 2.6 Interoperability Considerations for more details."
4) Par 4, replace the two "may" with "can" to clarify the intent.
5) Par 5, change "defined" to "described" since the examples are not normat=
ive.
5) Par 5, add references to the (sub)sections containing the description of=
 the two methods.
6) Par 7, move the last paragraph before listing the two examples and adjus=
t the text accordingly, to improve the logical flow.
7) In the end of the Introduction add a reference: "This RFC is not backwar=
ds compatible with RFC 6822. Differences between this document and RFC 6822=
 are described in Annex A." ... so that others don't skip it by mistake as =
I did earlier...

2. Elements of Procedure
1) It seems that this section (informational) and its subsections (normativ=
e) use present and future times and, at times,  the normative language inco=
nsistently both within the sections and among the sub-sections. Please, exp=
lain the reasons and improve consistency accordingly.=20
2) Par 1, clarify the scope by adding "within a routing domain" at the end =
of the first sentence.
3) Par 1, after the first sentence add a new sentence alone the following l=
ines "Routers form adjacencies and exchange routing updates only if their I=
IDs correspond." This explains the basic premise of the whole mechanism.
4) Par 2, change "may" to "can" or "might" for consistency.

Section 2.1
1) Par 2, change "may" to "MAY".
2) Par 3, remove "supported by legacy systems" from the first sentence to a=
void confusion. My understanding is that IID #0 is reserved  for use by MI-=
RTRs that also implement the standard instance and advertise it in IIH usin=
g IID-TLV.
3) Par 3, change "except where noted" to "except as noted in section 2.6.2 =
(?)".  This is an excellent place to explain the logic behind this MUST NOT=
 statement or, at least, state the general circumstances where IID #0 is in=
cluded in IID-TLV.
4) Par 9 (4th after the picture), change "as described later" to " as descr=
ibed in section 2.6.2 (?)". =20
5) Par 13, change "recommended" to "RECOMMENDED".
6) Editorial: Par 13, change "particularf" to "particular".

Section 2.2
1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as well =
and which packets are used to advertise it.
2) Rephrase "marks ... by including" to "MUST include" to use requirements =
language.

Section 2.3
Editorial: Replace "normal" with "usual".

Section 2.4.1=20
1) Par 1. Replace "IID #0" with "standard instance".
2) Par 1. Replace "instances other than IID #0" with "non-zero instances".
3) Par 2 second sentence. What does it mean "normal expectations"? Is this =
a network configuration requirement? Please, clarify in the text.

Section 2.4.2 Improve language consistency=20
1) Verbs are used inconsistently: some are used in present time, others in =
future time.=20

Section 2.5, replace "exists" with "MUST be performed".
Section 2.5.1, replace "only operates" with "MUST only be performed".
Section 2.5.2, replace "This requires" with "It is REQUIRED".
Section 2.5.2 third sentence, after "inconsistent" insert "due to their con=
figuration". (Please, correct me if I am wrong.)

Section 2.6.1=20
1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid".
2) Par 2, remove "(IID #0)".
3) Par 2, replace "non-zero IID" with "non-zero instance".
4) Par 5 NOTE, replace "IID #0" with "standard instance".

Section 2.6.2=20
Replace all four appearances of "IID #0" with "standard instance".=20

Section 3.1
Replace the two "MAY" to "can".=20

7 Security Considerations
Discuss possible additional security considerations (or the lack of them) r=
elated to the exposure of "instances" on the wire.
Reason: Beyond the normal IETF procedure, this is especially important beca=
use "multiple instances allow isolation of resources..." Can this isolation=
, if observed or interfered on the wire, be damaging beyond the previous "s=
tandard instance" situation.

Thanks,
Orit.
-----Original Message-----
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]=20
Sent: Saturday, April 8, 2017 4:23 PM
To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02

Orit -

Thanx for the review.
Responses inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 06, 2017 8:27 PM
> To: gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area=20
> Review Team (Gen-ART) reviews all IETF documents being processed by=20
> the IESG for the IETF Chair.  Please treat these comments just like=20
> any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-isis-mi-bis-02
> Reviewer: Orit Levin
> Review Date: 2017-04-06
> IETF LC End Date: 2017-04-07
> IESG Telechat date: 2017-04-13
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> 1. Add text explaining the reason (or reasons) for replacing the=20
> original RFC
> 6822 from 2012.
> Reason: It is a "bis" draft and there is no mention about it in the text.

[Les:] Note that the latest revision of the draft correctly identifies the =
draft as obsoleting RFC 6822. Previous versions had incorrectly identified =
this as an update to RFC 6822.
This is then the new Standard for the IS-IS MI support.

There are two classes of future readers of this document:

a)Readers who are unfamiliar with RFC 6822. For them what changed between R=
FC 6822 and this document is irrelevant.=20

b)Readers who are familiar with RFC 6822. For them it is useful to know wha=
t changed - which is described in Appendix A.

In order not to distract readers of type "a" - as well as to provide an "un=
interrupted" description of the normative behavior I believe placement of t=
he change description in an Appendix improves the readability of the docume=
nt.

Does this make sense to you?

> 2. In Abstract, state clearly that this standard introduces the=20
> support for instances vs. other already existing concepts also listed=20
> in the Abstract (i.e., circuits, adjacencies,  topologies, etc.).

[Les:] The Abstract currently says:

"This draft describes a mechanism that allows a single router to share
   one or more circuits among multiple Intermediate System To
   Intermediate System (IS-IS) routing protocol instances."

Previous to this extension, a router could have multiple instances of the I=
S-IS protocol, but multiple instance could not be run over the same interfa=
ce.=20
So we are not introducing "instances", but we are introducing the ability t=
o enable multiple instances on the same interface.

> Reason: The wording is not clear about what is the new feature vs.=20
> what are the new benefits vs. what was the original baseline

>3. Throughout the
> document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are=20
>used  interchangeably throughout the document. It seems that they all=20
>refer to the  same thing - the implementation of the original protocol=20
>without the concept  of instances. Please, correct me if I am wrong.

[Les:]  I don't think this is possible without seriously compromising the d=
ocument. For example:

Section 2.1

" IID #0 is reserved for the standard instance supported by legacy
   systems. "

Changing this to  " Standard instance is reserved for the standard instance=
 ..."

Is clearly nonsensical.

Later in Section 2.1

"When the IID =3D 0, the list of supported ITIDs MUST NOT be present."

What is being discussed here is what is the correct behavior when an MI-cap=
able router sends a PDU associated IID #0 and includes the new IID TLV.=20
Replacing this with "When the standard instance..." loses the important poi=
nt that the value of the IID in the IID TLV in this case is "0".

Hope this helps clarify things.

> 4. In section 2 par 3, change "support" and "operates" to "MUST=20
> support" to use requirements language.

[Les:] I am on the fence as regards this change. Section 2 is an introducti=
on to the following sub-sections - which define the normative behavior. But=
 the introduction itself is not defining normative behavior - it is providi=
ng a context in which the protocol extensions defined in the following sub-=
sections can be understood.=20

I am more inclined to change the "MAY" used later in the same paragraph you=
 mention to "may" so it is consistent with the rest of this section.

???


> 5. In section 2 par 2, change "may" to either "can" or "MAY" to=20
> clarify the intent.

[Les:] Did you mean Section 2.1 para 2?
If so I agree to the change.

> 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the=
 wire.

[Les:] There are numerous places in the document where the legal use of IID=
  #0 is discussed. I do not understand how a reader would conclude that IID=
 #0 is never sent on the wire.

> Explain the concept of the "standard interface" (see previous comment)

[Les:] There is no mention of "standard interface" - did you mean "standard=
 instance"?

If so, Section 1 paragraph 4 states:

"Legacy routers support the standard
   or zero instance of the protocol."

   Les


From nobody Thu Apr 13 20:05:42 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82362129463; Thu, 13 Apr 2017 20:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 KlZFEpQE6ZIT; Thu, 13 Apr 2017 20:05:37 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB00C12947D; Thu, 13 Apr 2017 20:05:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17076; q=dns/txt; s=iport; t=1492139136; x=1493348736; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=1lU4EDQ6UQmwqTjczhBtUvLhEoV34v5gBd5YdsnzV8w=; b=XnU7xhQLQ9G4A9gQ69wfuFGjHqTAtqzC2izwZltyvPDXVriHzvxB4exE TtKqM9lCgKvV2gkYMSQOfSDmX/dE8U/EtpOwANC3bXttgL5obVXITK0gx Lg5gW4ZT5Dz/YZ44filB03EurCH5OQHxKkBoXpq/2GX8ywlVLRwFEbAkP E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AWAQDrO/BY/4gNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrYYELB410kVqVWIIPLIV4AoN4PxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBOj8FBwQCAQgRAwEBAR8JBzIUCQgBAQQBDQUIigYIDqtYixEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdhlGBXYMXhB2GHgEEiS6GRYY7hmQBhwGDK4gsgghVhFm?= =?us-ascii?q?KF4hnix0BHziBBVsVQYRbHIFjdQGILYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,195,1488844800"; d="scan'208";a="411575674"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Apr 2017 03:05:35 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v3E35ZFP028735 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Apr 2017 03:05:35 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 13 Apr 2017 22:05:34 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Thu, 13 Apr 2017 22:05:34 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Orit Levin <oritl@microsoft.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kAAbW6QgA==
Date: Fri, 14 Apr 2017 03:05:34 +0000
Message-ID: <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com> <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com>
In-Reply-To: <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.152.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e2EB9FFpNrOxjs4-npVvfT76Gj4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 03:05:41 -0000

Orit -

It is obvious you spent a lot of time on this review - and I do want to be =
respectful of that.
However, there is a larger context here which I think has a significant bea=
ring on handling of many of your comments.

RFC 6822 was published over 4 years ago. Multiple interoperable implementat=
ions exist. The bis version makes some modest - but significant changes. Ho=
wever, we deliberately strived to keep the bis version as consistent as pos=
sible with RFC 6822 in order to minimize the possibility that aspects of th=
e specification which had NOT been changed would be reinterpreted simply be=
cause the wording had changed. So, in cases where you suggest (below) that =
a different wording is desirable I am very reluctant to make such changes b=
ecause of the above concern.
If I do not indicate any response to a particular comment you can interpret=
 as meaning:

"Unnecessary changes relative to RFC 6822 are not desirable."

Inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 13, 2017 4:59 PM
> To: Les Ginsberg (ginsberg); gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Hi Les,
> Sorry for the delay in response.
> Your feedback was very helpful. Below is a refresh of my comments. I trie=
d
> to make them more pointed and some are new.
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> General:
> 1) For implementers who are familiar with the history and the intent of t=
his
> extension, the information in the draft is probably sufficient to serve a=
s a
> check list for implementing a multi-instance IS-IS router. For all other =
readers,
> the document doesn't contain an overview of the new mode of operation,
> i.e. where the instances are not a configuration and an internal
> implementation choice only, but are exposed through the protocol to
> achieve the stated objective. Lacking such an overview, the reader needs =
to
> reverse-engineer the logic behind the documented guidance.

[Les:] I am not sure I understand your concern. You seem to be suggesting t=
hat readers won't know when to use MI and when to simply create multiple no=
n-MI instances of the protocol.
The short answer to that is that it is not the purpose of this document to =
make that decision. We have provided some new functionality - it is up to t=
he user to decide when it is appropriate to use the new functionality and w=
hen it is not. We have provided some guidance in Sections 3 and 4 - but thi=
s is non-normative - as it should be.
But your use of "reverse-engineer" confuses me, so likely I do not understa=
nd your point.

As regards new vs old readers, the new version of the document provides as =
much (or as little) guidance as RFC 6822 - so I do not see why new readers =
would have any more issues than new readers of RFC 6822 had 4 years ago.


> 2) The draft talks about "extensions" in plural. Based on a single extens=
ion on
> the wire and the overall goal of the new mechanism, I would say that it i=
s a
> single extension only.  How many protocol extensions does this document
> define? If they can be clearly separated, then it needs to be clarified
> throughout the document. Otherwise, the language throughout the
> document needs to be changed from "extensions" to "the extention".

[Les:] There are multiple changes in protocol behavior described - hence th=
e term extensions is correct.

> 3) Editorial: Please, compare (Diff) the current draft with the published=
 RFC
> 6822. You will find that various RFC Editor corrections got lost in this =
bis
> document. Some repeating examples of the lost corrections are "instance-
> specific", " topology (or topologies)" and "Type-Length-Value".

[Les:] Noted - thanx.

> My comments below are a result of a reverse-engineering exercise. Please,
> consider incorporating the suggested clarifications to improve the docume=
nt
> readability. I might have misunderstood some of the parts; in such cases,
> please, provide an alternative text.
>=20
> Abstract
> 1) Add clarification: "This document is not backwards compatible with RFC
> 6822."

[Les:] This statement is made explicitly in the Appendix - and I believe th=
at is where it belongs for reasons I have previously stated.

> 2) Par. 2, replace the first two sentences with: "Configuration of multip=
le
> protocol instances within a router allow the isolation of resources assoc=
iated
> with each instance. This document introduces a new mode of operation
> where the protocol instances are not a matter of configuration only, but =
are
> exposed through the new protocol extension to achieve the objective state=
d
> above."
> 3) Par. 3 uses both present and future time. Does it mean before and afte=
r
> the extension? Please, clarify by spelling out the intent and/or changing=
 the
> grammar.
>=20
[Les:] The sentence will in any case be changed when the document becomes a=
n RFC - not worth discussing.

> 1. Introduction
> 1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the
> Introduction to improve its logical flow (also related to the next commen=
t).
> 2) Par 4, sentence #2 says "This document defines an extension to IS-IS t=
o
> allow non-zero instances...". My assumption is that the intent of this dr=
aft is
> to define a single extension, which will improve the routing operations i=
n a
> number of ways. If this is the case, the quote needs to be replaced with =
"The
> MI-IS-IS extension, defined in this document, also allows so-called "non-=
zero
> instances"..." .
> 3) Par 4, sentences #4 and #5 are not sufficient to describe the new mode=
 of
> operation introduced by this extension. Below is my attempt to describe i=
t.
> Please, correct, if I got it wrong.
> "IS-IS router instances that support this extension are preconfigured wit=
h
> unique non-zero Instance Identifiers (IIDs) giving them the name "non-zer=
o
> instances". In addition, MI RTRs MAY (or SHOULD ?) implement the legacy (=
or
> so-called "standard") instance of the IS-IS router for backwards compatib=
ility
> with legacy IS-IS routers. IID #0 is only used by MI-RTRs to convey
> information associated with such standard interface if implemented. See
> section 2.6 Interoperability Considerations for more details."
> 4) Par 4, replace the two "may" with "can" to clarify the intent.
> 5) Par 5, change "defined" to "described" since the examples are not
> normative.
> 5) Par 5, add references to the (sub)sections containing the description =
of
> the two methods.
> 6) Par 7, move the last paragraph before listing the two examples and adj=
ust
> the text accordingly, to improve the logical flow.
> 7) In the end of the Introduction add a reference: "This RFC is not backw=
ards
> compatible with RFC 6822. Differences between this document and RFC 6822
> are described in Annex A." ... so that others don't skip it by mistake as=
 I did
> earlier...
>=20
 [Les:] Reading of the Appendix is optional - the new version is usable wit=
hout any need to refer to RFC 6822 - and that is its primary purpose.

> 2. Elements of Procedure
> 1) It seems that this section (informational) and its subsections (normat=
ive)
> use present and future times and, at times,  the normative language
> inconsistently both within the sections and among the sub-sections. Pleas=
e,
> explain the reasons and improve consistency accordingly.
> 2) Par 1, clarify the scope by adding "within a routing domain" at the en=
d of
> the first sentence.
> 3) Par 1, after the first sentence add a new sentence alone the following=
 lines
> "Routers form adjacencies and exchange routing updates only if their IIDs
> correspond." This explains the basic premise of the whole mechanism.
> 4) Par 2, change "may" to "can" or "might" for consistency.
>=20
> Section 2.1
> 1) Par 2, change "may" to "MAY".
> 2) Par 3, remove "supported by legacy systems" from the first sentence to
> avoid confusion. My understanding is that IID #0 is reserved  for use by =
MI-
> RTRs that also implement the standard instance and advertise it in IIH us=
ing
> IID-TLV.
> 3) Par 3, change "except where noted" to "except as noted in section 2.6.=
2
> (?)".  This is an excellent place to explain the logic behind this MUST N=
OT
> statement or, at least, state the general circumstances where IID #0 is
> included in IID-TLV.
> 4) Par 9 (4th after the picture), change "as described later" to " as des=
cribed
> in section 2.6.2 (?)".
> 5) Par 13, change "recommended" to "RECOMMENDED".
> 6) Editorial: Par 13, change "particularf" to "particular".
>=20
[Les:] #6 - Agreed.

> Section 2.2
> 1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as
> well and which packets are used to advertise it.
> 2) Rephrase "marks ... by including" to "MUST include" to use requirement=
s
> language.
>=20
> Section 2.3
> Editorial: Replace "normal" with "usual".
>=20
> Section 2.4.1
> 1) Par 1. Replace "IID #0" with "standard instance".
> 2) Par 1. Replace "instances other than IID #0" with "non-zero instances"=
.
> 3) Par 2 second sentence. What does it mean "normal expectations"? Is thi=
s a
> network configuration requirement? Please, clarify in the text.
>=20
> Section 2.4.2 Improve language consistency
> 1) Verbs are used inconsistently: some are used in present time, others i=
n
> future time.
>=20
> Section 2.5, replace "exists" with "MUST be performed".
> Section 2.5.1, replace "only operates" with "MUST only be performed".
> Section 2.5.2, replace "This requires" with "It is REQUIRED".
> Section 2.5.2 third sentence, after "inconsistent" insert "due to their
> configuration". (Please, correct me if I am wrong.)
>=20
> Section 2.6.1
> 1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid"=
.
> 2) Par 2, remove "(IID #0)".
> 3) Par 2, replace "non-zero IID" with "non-zero instance".
> 4) Par 5 NOTE, replace "IID #0" with "standard instance".
>=20
> Section 2.6.2
> Replace all four appearances of "IID #0" with "standard instance".
>=20
> Section 3.1
> Replace the two "MAY" to "can".
>=20
> 7 Security Considerations
> Discuss possible additional security considerations (or the lack of them)
> related to the exposure of "instances" on the wire.
> Reason: Beyond the normal IETF procedure, this is especially important
> because "multiple instances allow isolation of resources..." Can this iso=
lation,
> if observed or interfered on the wire, be damaging beyond the previous
> "standard instance" situation.
>=20

[Les:] There are no security concerns associated with the use of multiple i=
nstances.
Security reviews of the document have been satisfied w the current contents=
.

   Les

> Thanks,
> Orit.
> -----Original Message-----
> From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> Sent: Saturday, April 8, 2017 4:23 PM
> To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Orit -
>=20
> Thanx for the review.
> Responses inline.
>=20
> > -----Original Message-----
> > From: Orit Levin [mailto:oritl@microsoft.com]
> > Sent: Thursday, April 06, 2017 8:27 PM
> > To: gen-art@ietf.org
> > Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> > Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area
> > Review Team (Gen-ART) reviews all IETF documents being processed by
> > the IESG for the IETF Chair.  Please treat these comments just like
> > any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-isis-mi-bis-02
> > Reviewer: Orit Levin
> > Review Date: 2017-04-06
> > IETF LC End Date: 2017-04-07
> > IESG Telechat date: 2017-04-13
> >
> > Summary: This draft is "ready with issues" for publication.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > 1. Add text explaining the reason (or reasons) for replacing the
> > original RFC
> > 6822 from 2012.
> > Reason: It is a "bis" draft and there is no mention about it in the tex=
t.
>=20
> [Les:] Note that the latest revision of the draft correctly identifies th=
e draft as
> obsoleting RFC 6822. Previous versions had incorrectly identified this as=
 an
> update to RFC 6822.
> This is then the new Standard for the IS-IS MI support.
>=20
> There are two classes of future readers of this document:
>=20
> a)Readers who are unfamiliar with RFC 6822. For them what changed
> between RFC 6822 and this document is irrelevant.
>=20
> b)Readers who are familiar with RFC 6822. For them it is useful to know w=
hat
> changed - which is described in Appendix A.
>=20
> In order not to distract readers of type "a" - as well as to provide an
> "uninterrupted" description of the normative behavior I believe placement
> of the change description in an Appendix improves the readability of the
> document.
>=20
> Does this make sense to you?
>=20
> > 2. In Abstract, state clearly that this standard introduces the
> > support for instances vs. other already existing concepts also listed
> > in the Abstract (i.e., circuits, adjacencies,  topologies, etc.).
>=20
> [Les:] The Abstract currently says:
>=20
> "This draft describes a mechanism that allows a single router to share
>    one or more circuits among multiple Intermediate System To
>    Intermediate System (IS-IS) routing protocol instances."
>=20
> Previous to this extension, a router could have multiple instances of the=
 IS-IS
> protocol, but multiple instance could not be run over the same interface.
> So we are not introducing "instances", but we are introducing the ability=
 to
> enable multiple instances on the same interface.
>=20
> > Reason: The wording is not clear about what is the new feature vs.
> > what are the new benefits vs. what was the original baseline
>=20
> >3. Throughout the
> > document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> > Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are
> >used  interchangeably throughout the document. It seems that they all
> >refer to the  same thing - the implementation of the original protocol
> >without the concept  of instances. Please, correct me if I am wrong.
>=20
> [Les:]  I don't think this is possible without seriously compromising the
> document. For example:
>=20
> Section 2.1
>=20
> " IID #0 is reserved for the standard instance supported by legacy
>    systems. "
>=20
> Changing this to  " Standard instance is reserved for the standard instan=
ce ..."
>=20
> Is clearly nonsensical.
>=20
> Later in Section 2.1
>=20
> "When the IID =3D 0, the list of supported ITIDs MUST NOT be present."
>=20
> What is being discussed here is what is the correct behavior when an MI-
> capable router sends a PDU associated IID #0 and includes the new IID TLV=
.
> Replacing this with "When the standard instance..." loses the important p=
oint
> that the value of the IID in the IID TLV in this case is "0".
>=20
> Hope this helps clarify things.
>=20
> > 4. In section 2 par 3, change "support" and "operates" to "MUST
> > support" to use requirements language.
>=20
> [Les:] I am on the fence as regards this change. Section 2 is an introduc=
tion to
> the following sub-sections - which define the normative behavior. But the
> introduction itself is not defining normative behavior - it is providing =
a
> context in which the protocol extensions defined in the following sub-
> sections can be understood.
>=20
> I am more inclined to change the "MAY" used later in the same paragraph
> you mention to "may" so it is consistent with the rest of this section.
>=20
> ???
>=20
>=20
> > 5. In section 2 par 2, change "may" to either "can" or "MAY" to
> > clarify the intent.
>=20
> [Les:] Did you mean Section 2.1 para 2?
> If so I agree to the change.
>=20
> > 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on t=
he wire.
>=20
> [Les:] There are numerous places in the document where the legal use of I=
ID
> #0 is discussed. I do not understand how a reader would conclude that IID=
 #0
> is never sent on the wire.
>=20
> > Explain the concept of the "standard interface" (see previous comment)
>=20
> [Les:] There is no mention of "standard interface" - did you mean "standa=
rd
> instance"?
>=20
> If so, Section 1 paragraph 4 states:
>=20
> "Legacy routers support the standard
>    or zero instance of the protocol."
>=20
>    Les


From nobody Thu Apr 13 21:53:22 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E19126C3D for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 21:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 UEgGLpzjvlgc for <ietf@ietfa.amsl.com>; Thu, 13 Apr 2017 21:53:17 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (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 9069E128B91 for <ietf@ietf.org>; Thu, 13 Apr 2017 21:53:17 -0700 (PDT)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v3E4mmj0072529 for <ietf@ietf.org>; Fri, 14 Apr 2017 00:53:13 -0400
Received: from e17.ny.us.ibm.com (e17.ny.us.ibm.com [129.33.205.207]) by mx0a-001b2d01.pphosted.com with ESMTP id 29tns9kjpb-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 14 Apr 2017 00:53:13 -0400
Received: from localhost by e17.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 14 Apr 2017 00:53:11 -0400
Received: from b01cxnp23033.gho.pok.ibm.com (9.57.198.28) by e17.ny.us.ibm.com (146.89.104.204) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 14 Apr 2017 00:53:09 -0400
Received: from b01ledav03.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp23033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v3E4rCiI44368064 for <ietf@ietf.org>; Fri, 14 Apr 2017 04:53:12 GMT
Received: from b01ledav03.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3AADFB2056 for <ietf@ietf.org>; Fri, 14 Apr 2017 00:53:04 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav03.gho.pok.ibm.com (Postfix) with ESMTPS id 1C472B204D for <ietf@ietf.org>; Fri, 14 Apr 2017 00:53:04 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v3E4r7T5007137 for <ietf@ietf.org>; Fri, 14 Apr 2017 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v3E4r6g1007120 for ietf@ietf.org; Fri, 14 Apr 2017 00:53:06 -0400
From: narten@us.ibm.com
Date: Fri, 14 Apr 2017 00:53:06 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17041404-0040-0000-0000-00000315F1F3
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006932; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000208; SDB=6.00847215; UDB=6.00418030; IPR=6.00625741;  BA=6.00005288; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015041; XFM=3.00000013; UTC=2017-04-14 04:53:10
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17041404-0041-0000-0000-00000709FEB2
Message-Id: <201704140453.v3E4r6g1007120@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-14_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=89 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704140040
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b3Cesl-T0oQOWB5uXyUec-ortAE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 04:53:20 -0000

Total of 148 messages in the last 7 days.
 
script run at: Fri Apr 14 00:53:06 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.11% |   12 | 11.35% |   232574 | eng.khaled.omar@hotmail.com
  4.05% |    6 | 11.99% |   245674 | kathleen.moriarty.ietf@gmail.com
  4.73% |    7 |  4.20% |    85948 | stephen.farrell@cs.tcd.ie
  4.73% |    7 |  3.93% |    80507 | jordi.palet@consulintel.es
  4.73% |    7 |  3.88% |    79398 | mohamed.boucadair@orange.com
  4.05% |    6 |  4.19% |    85785 | ginsberg@cisco.com
  2.70% |    4 |  4.16% |    85274 | jonathan.hardwick@metaswitch.com
  3.38% |    5 |  2.16% |    44272 | cabo@tzi.org
  2.70% |    4 |  2.44% |    49932 | aretana@cisco.com
  2.70% |    4 |  2.06% |    42230 | mnot@mnot.net
  2.70% |    4 |  2.00% |    41068 | mirja.kuehlewind@tik.ee.ethz.ch
  0.68% |    1 |  3.93% |    80607 | martin.thomson@gmail.com
  2.70% |    4 |  1.42% |    29056 | rjsparks@nostrum.com
  2.03% |    3 |  1.56% |    31863 | brian.e.carpenter@gmail.com
  2.03% |    3 |  1.47% |    30083 | jmh@joelhalpern.com
  2.03% |    3 |  0.94% |    19346 | randy@psg.com
  1.35% |    2 |  1.40% |    28675 | lionel.morand@orange.com
  0.68% |    1 |  2.02% |    41475 | job@ntt.net
  0.68% |    1 |  1.87% |    38304 | job@instituut.net
  1.35% |    2 |  1.05% |    21498 | leo.liubing@huawei.com
  0.68% |    1 |  1.70% |    34871 | shares@ndzh.com
  1.35% |    2 |  1.01% |    20665 | nishida@sfc.wide.ad.jp
  1.35% |    2 |  1.00% |    20495 | eric.gray@ericsson.com
  1.35% |    2 |  0.99% |    20355 | melinda.shore@gmail.com
  1.35% |    2 |  0.97% |    19911 | linuxwolf+ietf@outer-planes.net
  1.35% |    2 |  0.94% |    19178 | nico@cryptonector.com
  1.35% |    2 |  0.92% |    18872 | john-ietf@jck.com
  1.35% |    2 |  0.90% |    18464 | julien.meuric@orange.com
  1.35% |    2 |  0.83% |    17022 | mcr+ietf@sandelman.ca
  1.35% |    2 |  0.76% |    15667 | aaron.falk@gmail.com
  0.68% |    1 |  1.12% |    22842 | oritl@microsoft.com
  0.68% |    1 |  0.79% |    16219 | weigengyu@bupt.edu.cn
  0.68% |    1 |  0.79% |    16169 | bilhanan.silverajan@tut.fi
  0.68% |    1 |  0.78% |    16062 | cheshire@apple.com
  0.68% |    1 |  0.76% |    15604 | daedulus@btconnect.com
  0.68% |    1 |  0.74% |    15087 | ford@isoc.org
  0.68% |    1 |  0.68% |    13948 | ldaigle@thinkingcat.com
  0.68% |    1 |  0.67% |    13624 | lloyd.wood@yahoo.co.uk
  0.68% |    1 |  0.64% |    13048 | gregimirsky@gmail.com
  0.68% |    1 |  0.60% |    12211 | lars@netapp.com
  0.68% |    1 |  0.58% |    11953 | huitema@huitema.net
  0.68% |    1 |  0.56% |    11398 | narten@us.ibm.com
  0.68% |    1 |  0.55% |    11226 | phill@hallambaker.com
  0.68% |    1 |  0.53% |    10948 | joelja@bogus.com
  0.68% |    1 |  0.53% |    10912 | stewart.bryant@gmail.com
  0.68% |    1 |  0.53% |    10805 | jaime.jimenez@ericsson.com
  0.68% |    1 |  0.53% |    10796 | acee@cisco.com
  0.68% |    1 |  0.52% |    10624 | jrmitche@puck.nether.net
  0.68% |    1 |  0.52% |    10619 | ddolson@sandvine.com
  0.68% |    1 |  0.51% |    10475 | matthew@kerwin.net.au
  0.68% |    1 |  0.49% |    10046 | mellon@fugue.com
  0.68% |    1 |  0.49% |    10016 | jmh.direct@joelhalpern.com
  0.68% |    1 |  0.49% |     9996 | ynir.ietf@gmail.com
  0.68% |    1 |  0.48% |     9903 | jayb@braeburn.org
  0.68% |    1 |  0.47% |     9531 | lear@cisco.com
  0.68% |    1 |  0.45% |     9308 | mstjohns@comcast.net
  0.68% |    1 |  0.44% |     9095 | jefftant.ietf@gmail.com
  0.68% |    1 |  0.44% |     9037 | loa@pi.nu
  0.68% |    1 |  0.42% |     8686 | gorry@erg.abdn.ac.uk
  0.68% |    1 |  0.41% |     8402 | nalini.elkins@insidethestack.com
  0.68% |    1 |  0.40% |     8138 | alexey.melnikov@isode.com
  0.68% |    1 |  0.40% |     8118 | dhc@dcrocker.net
  0.68% |    1 |  0.38% |     7818 | kovatsch@inf.ethz.ch
  0.68% |    1 |  0.37% |     7639 | worley@ariadne.com
  0.68% |    1 |  0.37% |     7523 | dave.taht@gmail.com
  0.68% |    1 |  0.36% |     7308 | mjethanandani@gmail.com
  0.68% |    1 |  0.35% |     7144 | rsk@gsp.org
  0.68% |    1 |  0.33% |     6685 | liushucheng@huawei.com
  0.68% |    1 |  0.32% |     6633 | wes@mti-systems.com
  0.68% |    1 |  0.32% |     6632 | nick@foobar.org
  0.68% |    1 |  0.31% |     6411 | john@jlc.net
  0.68% |    1 |  0.27% |     5457 | ron.even.tlv@gmail.com
  0.68% |    1 |  0.26% |     5376 | sean@sn3rd.com
--------+------+--------+----------+------------------------
100.00% |  148 |100.00% |  2048541 | Total


From nobody Fri Apr 14 01:24:01 2017
Return-Path: <prvs=12776aa295=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A90128B92 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 01:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9L5oBR_Fpqml for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 01:23:58 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EBA9128DF3 for <ietf@ietf.org>; Fri, 14 Apr 2017 01:23:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492158234; x=1492763034; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=Pfrps1/hfdQxFO8n7+ZOhTA2E qnbq22U1ivq8cKRNPA=; b=Z/y+FsDMjEP/35aHT637FO5XRhQVH+/pSRHUTyMK0 14pfYA+aLhAbwKQeqkFx6ApJdMoWk1mjIdOgi0sx0GNlXSIu2JrW1L3Q4WBek55S fefolObWmb5RihWlftDGqf/ORADldZeJODxal4L4DGJE1XmJj0M8wNIohPaYF0Zv 08=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=oagsxpgjba7WMK2dR+lHF/7FnV/M1Rz3hFdz4aQ6ImSHqeMD+VjU2SI+LPum E9JzeekzcEURtnVP08eirVkBrR1SkG2lnpo0zp8ut+CQUtXGywrpXNyhz df/54ctCj5K7houhqFqnt0tb9O858r6sNfn7aYHPwzd1egDc/ObM6o=;
X-MDAV-Processed: mail.consulintel.es, Fri, 14 Apr 2017 10:23:54 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 14 Apr 2017 10:23:54 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005408361.msg for <ietf@ietf.org>; Fri, 14 Apr 2017 10:23:52 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170414:md50005408361::T9vNBXPrXdUVWrQs:00000dbK
X-Return-Path: prvs=12776aa295=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Fri, 14 Apr 2017 10:23:50 +0200
Subject: Re: Update on feedback on US-based meetings, and IETF 102
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <D846BB0A-D2B2-424A-9166-F8D591C56EBF@consulintel.es>
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie> <43378975-daf3-0170-35c7-b57e03b834b2@comcast.net>
In-Reply-To: <43378975-daf3-0170-35c7-b57e03b834b2@comcast.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3BhGnAllG_fFT8lonP08Ek0N8gk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 08:24:00 -0000

Well, for some countries what Trump said, has already been a fact, for exam=
ple the prohibition to have computers on board. Is not that the case?

Whatever we want to decide, cancel SF or not, it may highly depend on budge=
t, we like it or not. And that means that we need answers:

    If we cancel San Francisco, how much that is going to cost to the IETF =
for each of two planned meetings?
   =20
    Can we cancel the actual hotel contract considering the new US situatio=
n? If not, has this been considered for new contracts to avoid this problem=
?
   =20
    Otherwise there is any reason that can justify the lack of transparency=
 in this?

The problem is so big for this community that I don=E2=80=99t even agree th=
at the IAOC should take the decision. It must be a collective one, especial=
ly when the IAOC is demonstrating thru facts that they don=E2=80=99t care t=
hat we are discussing and wasting our time without the minimum relevant dat=
a, this is disrespectful and even more, not responding to emails since even=
 since years ago, shows lack of education=20

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Michael StJohns <mstjohns@com=
cast.net>
Responder a: <mstjohns@comcast.net>
Fecha: jueves, 13 de abril de 2017, 20:37
Para: <ietf@ietf.org>
Asunto: Re: Update on feedback on US-based meetings, and IETF 102

    On 4/12/2017 8:44 PM, Stephen Farrell wrote:
    > That's a fair point. I think though that it also puts on onus on
    > any folks who adamantly think we ought continue to meet in the US,
    > to also publicly justify that, given the opposite arguments already
    > voiced on the list.
   =20
   =20
    Does it also put the onus on say the UK and the rest of the EU to gaze=
=20
    into the future and promise that the breakup will be amicable and that=
=20
    there will be no changes in the current passage rules between the two o=
r=20
    even between EU members?
   =20
    As much as you might like to require someone to prove a negative - it's=
=20
    generally understood that proposing that someone do so tends to be more=
=20
    of a political debate trick than anything else.
   =20
    Looking back in history, immediately after 9/11 - arguably the biggest=
=20
    provocation the US has received during the Internet era - 4 out of the =
5=20
    IETF meetings immediately after 9/11 were held in the US under the=20
    increased travel scrutiny that we take for granted now and we adapted. =
=20
    The current questions are or need to be:  What are the changes and can=
=20
    we adapt.
   =20
    We have a US President that has made big claims and broad pronouncement=
s=20
    - but here's the thing.  He's not a dictator and he's bound by strong=
=20
    laws and constitutional requirements that limit his reach.   Basing a=
=20
    decision on whether or not to hold meetings in the US based on only wha=
t=20
    Trump says and does vs what he might say and do vs looking at what=20
    actually happens (e.g. travel restrictions held in abeyance due to=20
    perceived constitutional violations) seems to be taking counsel of fear=
s=20
    rather than counsel of facts.
   =20
    I would suggest that we not cancel SF and use it to gain FACTS. I would=
=20
    suggest that by the time SF comes around the bulk of changes (if any)=
=20
    will have occurred and we will be able to quantify their impact on the=
=20
    IETF participants in the scope of that meeting and whether future=20
    meetings will need to be held elsewhere for a period of time or whether=
=20
    we're able to adapt.  I would further suggest that the impact of having=
=20
    one "bad" meeting would be minimal in the broader scheme of things vs=
=20
    not having a consensus and agreement on both the actual problem and the=
=20
    solution to said problem.
   =20
   =20
    Mike
   =20
   =20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Fri Apr 14 02:06:44 2017
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A5F126B6E; Fri, 14 Apr 2017 02:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVQ5UkVmF-NL; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 AA8931201F8; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id p68so64949785qke.1; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=316zf3Ma9DNlsGA740pZl5rsIFuOYE/b0gG+4n4g6cY=; b=SpnDhQ6Z84ZVdqCTXrhPSqhjoRCJ1ue7wn3Q2SYomaQ3Hx2HF+OKzXRR3A2VThvPbO RavBVwVoWauljdWCkgBQl68UD2Ci6mpqiEZR14K4b7Bt3yrylsI1AL5h10wbHXVisk1F ohU/0EZKVdcqLFyPTQZ2tGdQKGq/LsQiHrzn6tCo9drhKsteDL8xzWPge8vIWzFj0L8l lRAX50sDcpGuyE/Fgs43KexNu9GNpEVjIm9YGEcmn/ZOXy7+iLObvk9WX5VDQZL+Cfnu RUajzt71aCDmSId4yZVOpY2wGEYeQgITaazeAS4Td35X3rUCxWmhxvVIEtngap8sqkDd GZEQ==
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:content-transfer-encoding; bh=316zf3Ma9DNlsGA740pZl5rsIFuOYE/b0gG+4n4g6cY=; b=fEtdL2/Db7xtPZ6T2UAPnGAuDUMUnixeqp8JyYuPp661GtAJ5IqzaTKZpMSopJ8vda PgNPtiHqHXpXWPREW+nDqq2oxVkPzGmbZXexBtnLsaQVrVzy34WVz00zGiT3v3N2FvQq dJA27TWgGDuNZqOkKjU6DkO/bUMXTpvv+vrDAHG/5WuwxWl7DY1lgSeF8xXtOVwN9jGw PiGy4EXaPORX2KsT1DLXYLDgxenH+2uepoiB/xism8bz6m6cc0fr3lQ0a3X67HcCSbq/ ccfVAX6kAu+Hi26A6eWAdPbloPb/bumu2C87hQKgnKvF1r7LjrLMV+LTlzWXgIt1qT4u 9c0A==
X-Gm-Message-State: AN3rC/5W165tq8lLgmnVBjnTi+B51m1ViJ6/7qDgjdENoC7dLxbTWtwG xO0PSZYA+/YqxSzn6LESHf3EfdtPYxoD
X-Received: by 10.55.99.69 with SMTP id x66mr5928586qkb.129.1492160800721; Fri, 14 Apr 2017 02:06:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.34.104 with HTTP; Fri, 14 Apr 2017 02:06:40 -0700 (PDT)
In-Reply-To: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
From: Vinayak Hegde <vinayakh@gmail.com>
Date: Fri, 14 Apr 2017 14:36:40 +0530
Message-ID: <CAKe6YvN08wvC9N_GQQc2nNYa61EcqKmtZ=ajQUnfBUJvtEC6pw@mail.gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: IETF Discussion Mailing List <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DPW_IdeSiWL4iM-oFZWXzd3YAd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 09:06:43 -0000

On Thu, Apr 13, 2017 at 5:09 AM, IAOC Chair <iaoc-chair@ietf.org> wrote:
> On March 31, 2017, we put out a request for input on experiences with tra=
vel to the recent IETF meeting in the US, and solicited information pertine=
nt to plans to attend IETF meetings within or outside the US in the coming =
years.  We have had over 350 responses to the questionnaire, and we appreci=
ate each and every one of them!   We did not gather the data in such a way =
for it to reflect a representative sample of the IETF community, or of pote=
ntial meeting attendees. But we did gain insights from those who responded =
that we did not have before.

Can the data be put out in an anonymized fashion without revealing PII
(such as name or email) ? The data has been interpreted for the
community but it might be useful for the community to look at the data
gathered as well. It might help change opinions or people on the fence
or people to rethink their positions.

> Over 40% of the respondents said they had attended 20 or more IETF meetin=
gs, and over 50% of them said they were authors of active working group doc=
uments.  Slightly more than 40% stated US residency, and just less than 60%=
 said they were not US-resident.

Since the US-meeting disproportionately affects those traveling to the
US, I think that might be an axis against which data needs to be
interpreted. The burden on many US citizens would be (possibly) extra
travel in case the meeting is not located nearby (such as in Canada or
Mexico).

Also many nationalities might not need to apply for US visa or face
lesser stringent barriers to entry. So knowing the country of
citizenship might be useful in the data.

> The general comments on meeting in the US played along the same lines as =
has been shared on the IETF discussion list:  people are variously for movi=
ng all meetings out of the US, or adamantly against, or somewhere in betwee=
n, each position supported by good reasons.

Again might be useful to see the data.

> The IAOC is continuing to gather data on travel to the US, concerns about=
 traveling outside of it, and what alternatives are possible for IETF 102. =
 Our focus is currently on whether holding IETF 102 in San Francisco is the=
 best option to meet the needs of IETF work, recognizing that we cannot pre=
dict the future.  While it may take several weeks to allow for review and n=
egotiation of any alternatives (if applicable), we are moving as quickly as=
 possible because we realize that people will need time to plan their trave=
l.

Is there a rough timeline for this ?

-- Vinayak


From nobody Fri Apr 14 09:04:23 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6E412ECA8 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:04:21 -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 NNXYia2SJvZa for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:04:19 -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 A2ED01296D2 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:04:19 -0700 (PDT)
Received: from [192.168.0.228] (176-35-156-161.xdsl.murphx.net [176.35.156.161]) (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 519EF8304B; Fri, 14 Apr 2017 18:04:17 +0200 (CEST)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: dcrocker@bbiw.net, IETF <ietf@ietf.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com>
Date: Fri, 14 Apr 2017 17:04:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z9ZYG5hQsIJfnwBFHzYFuAyKEww>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:04:22 -0000

On 04/10/2017 11:01 PM, Dave Crocker wrote:
> 
> It is fast looking as if the ability to sustain a large and very
> well-attended network of interconnected remote hubs might become a
> necessity rather than merely an appealing alternative...

FWIW, for the developing world, remote participation has possibly always
been a necessity.

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





From nobody Fri Apr 14 09:12:00 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9FB12949D for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level: 
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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=dcrocker.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 tez6ES6oK6Kr for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:11:57 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 F2BE3126CF9 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:11:56 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3EGEAaF005524 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 14 Apr 2017 09:14:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492186450; bh=Hw6dCkuJjKLKzG42VDB+CFFsXCsXeQalRgij7/Tq+F0=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=AqddReRCWDaGadoKa2VLt+EjUUGTLB4MjGqiK4afFRPVPkMVEhAzYgbbidEnrAJHN cDQz9BXm/qCUBvhndUNGAJdxWYHUhtEy4Rwjx2o83gjjkmL6qytXKWGZyRpeu8y2GS eP+GHiQYrAL6h4wfO/Si9z27e9D1laPn+gMqiZYk=
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Fernando Gont <fgont@si6networks.com>, IETF <ietf@ietf.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
Date: Fri, 14 Apr 2017 09:11:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PdE25WiuBMuX62BwjlEQZhwB8Tc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:11:59 -0000

On 4/14/2017 9:04 AM, Fernando Gont wrote:
> FWIW, for the developing world, remote participation has possibly always
> been a necessity.


Indeed.  I hadn't understood how extensive this had become until seeing:

    https://tools.ietf.org/html/draft-elkins-ietf-remote-hubs-00#section-3

However, there is a significant difference between their current mode of 
integration with the 'main' venue site, versus what we will need to have 
remote sites able to have nearly seamless participation in sessions.

Some of this is functional, such as a single queue for everyone wanting 
to speak, no matter where they are.  Some of this is much more robust 
performance and reliability (within obvious networking limitations.)

I suspect the easiest bit will be improved usability design, since the 
Meetecho folk tend to start with reasonable design and make improvements 
quickly, as experience is gained.  But yes, from some comments over the 
last two meetings, there's probably room for that improvement.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr 14 09:22:40 2017
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7B4D1294A6 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:22:38 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=krsek-cz.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 CI5j6I1zCQxv for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:22:37 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 ED935126BF0 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:22:36 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id o21so53219740wrb.2 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krsek-cz.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=msS6IuxGHjnnlTCIh113VRJ8sL5H+M8nSD1uWn6iYLk=; b=hnHzwmtXdIBdLN98I77PqmC7+OS9mOiMih9M6/jnjsl4jxr5JdTenU6N5sJZyFAaxM tXzrCiHVXxf2UIz9uVf4h7yQIR1b9bFR3HQMf7mpWQdWXECkAnlbaT7GB1h8g9QHkAHS D52+NcuTvv2VXRldG4CVelX8DeOQ2oAu8+W0aiNpbQiCe2r3FJ4WbrLue9oTxBPmW8q3 0NwhNXsTGJo8sTQB/VDdoU1q+OTci7o3Nfmcf1ihgAksxrIbfyFAFbRS3fhB8pmc7ock eBGAOGKOpLZ2ORnpDw6tnIkJIuNuWlY84lYDTtNoVdDledAzWyjD05bg/fXz7ic7xDJo j6wg==
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-transfer-encoding; bh=msS6IuxGHjnnlTCIh113VRJ8sL5H+M8nSD1uWn6iYLk=; b=MnZyxqzzASdr3b3qgktEYQa/Nfe1NxGIh06uVgX3wQVU+/dyvOIE5zaghoM0EPitrv AWlHq0c8qQZfz7GnoPnKcLvL9tNwhlpcr/eyhzBSWHvRtHI9/lZPdvdfDbufUt1u5BJr /06VBDKs9qPacUp04RezMGdieL37uwj0uLsa2jsx5PZNmy6XS4RsmAoe7GrxU7fZCcZM 6kWFYhzWk4LAJFxo4fBLLhVOltLn7QzSsRsvoexDIa8mRMTTXkjoCSCkauW4HI8T4Y3p JFDoW8jrdRIYIR5gBcuqtXsXDgu3k0U9mY8L96M0o1bTaUGzlW+LHxxawsN0xWqaS1et 6GLQ==
X-Gm-Message-State: AN3rC/6sDQQ7ii5qfH0l3Pwb2Qne8vKyGAXj/+vr5XjMh+pxVlkPzFKX wIJJVfPOEFLhwxp0qb8=
X-Received: by 10.223.168.23 with SMTP id l23mr7955328wrc.185.1492186955190; Fri, 14 Apr 2017 09:22:35 -0700 (PDT)
Received: from Michals-MacBook-Air.local (ip-37-188-238-204.eurotel.cz. [37.188.238.204]) by smtp.gmail.com with ESMTPSA id 92sm2919755wra.18.2017.04.14.09.22.33 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Apr 2017 09:22:34 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com> <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
From: Michal Krsek <michal@krsek.cz>
Message-ID: <fad6ad6f-15ef-6bb1-b4e1-0c494c845799@krsek.cz>
Date: Fri, 14 Apr 2017 18:22:29 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K-O4q6ezouRbRftI_8lbClWH7d8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:22:39 -0000

Hi,
> Some of this is functional, such as a single queue for everyone 
> wanting to speak, no matter where they are.  Some of this is much more 
> robust performance and reliability (within obvious networking 
> limitations.)
>
> I suspect the easiest bit will be improved usability design, since the 
> Meetecho folk tend to start with reasonable design and make 
> improvements quickly, as experience is gained.  But yes, from some 
> comments over the last two meetings, there's probably room for that 
> improvement.

there are more universities across the globe who do remote lectures 
using "lecture hall to lecture hall" concept. I can ask CESNET "remote 
collaboration" team during Prague meeting to discuss stuff and avoid 
dead ends already found.

                     Michal


From nobody Fri Apr 14 09:32:55 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C091294C0 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:32:53 -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 iQuJqZoQBXhD for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:32:51 -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 425F9126C23 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:32:51 -0700 (PDT)
Received: from [192.168.0.228] (176-35-156-161.xdsl.murphx.net [176.35.156.161]) (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 F3B668085F; Fri, 14 Apr 2017 18:32:48 +0200 (CEST)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: dcrocker@bbiw.net, IETF <ietf@ietf.org>
References: <9fee9874-1306-07a2-a84a-4e09381a5336@cisco.com> <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <a7b74cca-be56-2e3f-6276-a459f28fa445@si6networks.com> <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <fd39aaf7-4674-73e4-712d-83feab48303b@si6networks.com>
Date: Fri, 14 Apr 2017 17:32:16 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <e5b456ff-0234-1003-8d26-b3cdfee03c4e@dcrocker.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UaygckfUGoB6nG4hyjJHtFVZlxk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:32:53 -0000

On 04/14/2017 05:11 PM, Dave Crocker wrote:
> On 4/14/2017 9:04 AM, Fernando Gont wrote:
>> FWIW, for the developing world, remote participation has possibly always
>> been a necessity.
> 
> 
> Indeed.  I hadn't understood how extensive this had become until seeing:
> 
>    https://tools.ietf.org/html/draft-elkins-ietf-remote-hubs-00#section-3

I haven't checked the I-D. However, no matter what it says, there's
remote participation with meet echo, without hubs. For instance, I
participated (and presented) remotely in two wgs during the Chicago
IETF, without "attending" any hub.



> However, there is a significant difference between their current mode of
> integration with the 'main' venue site, versus what we will need to have
> remote sites able to have nearly seamless participation in sessions.

What I tried to note is that the situation for part of the participants
is such that remote participation is already necessary.

>From the pov of participants of North America or Europe, this *might* be
different and the current situation might be a game changer. But for us
in latin maerica, remote participation has always been a need, even if
we managed to attend one or more meetings (that's kind of like "the
exception to the rule").


> Some of this is functional, such as a single queue for everyone wanting
> to speak, no matter where they are.

Agreed.


>  Some of this is much more robust
> performance and reliability (within obvious networking limitations.)
> 
> I suspect the easiest bit will be improved usability design, since the
> Meetecho folk tend to start with reasonable design and make improvements
> quickly, as experience is gained.  But yes, from some comments over the
> last two meetings, there's probably room for that improvement.

I must say that modulo issues with the network (which were probably
local on my side), the experience was great, and I must say that the
meetecho folks provided "online" help in a very timely manner (thanks!).


There's room for improvements.. but in some cases they seem to be more
about integration of local and remote participants, than with "bugs" in
the tools themselves. e.g., as you've correctly noted, it would be great
if there was a means for managing the mic queue, such that there's a
single queue, that includes remote participants.

Thanks!

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





From nobody Fri Apr 14 09:38:13 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ADAD129421 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 Iw898j8qrrwb for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:38:11 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 EFF171294B5 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:38:10 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id u2so67833621wmu.0 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:38:10 -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-transfer-encoding; bh=G8dPXeK2vH55hWQbtJQPnZOzZu7HyHa4fKt5C1ZRp+4=; b=lq/XFJJgYziOsbxYQInwhmZ0EyO9a4yaK1rds42p++cU480tvUls7SqYxZyhWnIH1J sCZJSE5Oa6DyFolvN4m0Acustt66RyY1ii2afhuAi1SGaQxkk6kqPKi2qh5aYYLh9tSj dulqhMop+0DPEI5uxwaDznbWnbSj250ALfFXMR7WNmXqWZR4kzbvZigMY8/JXMmYZlgk tTPDQnQFe+MFrorEzyW9TRN5fJtSr/iAVhMUh1YtSB1L3uGvWkVL3EoZUJLQYkf3ROhl lDV5KxUHS7S+mmBYmBSCiPX4v1chClhJ6vLFvAsF0KvacbgUah/SD9frjlE9Cb8C9yMR lQnQ==
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-transfer-encoding; bh=G8dPXeK2vH55hWQbtJQPnZOzZu7HyHa4fKt5C1ZRp+4=; b=h4c14kztxu71X4d1/+gCpdohVzg4uUSY3O9h1dQDtHHquVJoNhZ65nAqlSb4cs4uQF VDqWVfyAdzKHNmxx9o+ytFQkdLk1rvY6hfmEq+vFhoSvTqxFS1sU9e8zy/H8XTIr/wWe d6LFUPHxJXn6pK0E0/PzR1UWsMMB7pU8m7/81dTNvrtbW+de7H8qTggHufBm4VyuzVBx l3h6au8SeLsamY6aQn78tR32ANOKjQjFr3xau109joZMsEmaR2pSp12Sbk4DN+LJm8r8 XjM1xEus4iDaSpL3pmKrWq1ZJKsOZ7w1t8NPBIjPFC94c0FuujqljSx5wJlO9bjfg697 +q7Q==
X-Gm-Message-State: AN3rC/4kqTdJUeCung2dJd8fIlmFkYcq+FA44wLrWgR2/U071i+4QBZk gVIv9SjhohHZRV+cCBs=
X-Received: by 10.28.74.70 with SMTP id x67mr8070326wma.137.1492187889364; Fri, 14 Apr 2017 09:38:09 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id k199sm3256123wmd.20.2017.04.14.09.38.08 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Apr 2017 09:38:08 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
Date: Fri, 14 Apr 2017 17:38:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <10890.1492007455@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1TKNviWyHY5HHZ2ATReBIBPWj_o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:38:12 -0000

On 12/04/2017 15:30, Michael Richardson wrote:
> Right, so this is why it's better for everyone to be remote.

Except that the IETF funding model requires attendees to pay their 
meeting fee.

- Stewart


From nobody Fri Apr 14 09:42:28 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40E7D129421 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 Gqwiks6kO_xA for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:42:24 -0700 (PDT)
Received: from nm8-vm1.bullet.mail.gq1.yahoo.com (nm8-vm1.bullet.mail.gq1.yahoo.com [98.136.218.224]) (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 782D0128B8E for <ietf@ietf.org>; Fri, 14 Apr 2017 09:42:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1492188144; bh=Ys1KtFsH6/zMz5m8AmS+Ne1DYq9BE9mho4WwEcD0yy8=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=ku153Wxo9ulYekeOdsq9a/ydEDTZ+rHqGYdtIj6cqYyOZWN5j8UpMpG+CnHwE/4K4x6+4k+4TYgnBBFu+AhtRvGnGkC2MwOacbTDD1aj3Mplx6ZntN4t7T7f6z1i50UVkfbVbZkWWoMMQ9NwigBcYX0XWEMH7/L2qoEFr341XC7g3gC6t//AGyPEdYgfL2PFcV/EzYm83VQz9MF0qoI8A1y4vEBHLWQOGt2j4FlKAspz8l82/FDpI5OMsX+RutT/Olk4UdLqaRnUnbMP/cq2IznM+3kPnfbxwP1rRNzDDvTIXelplyDCU34vWbVnufS6ZW2TR+Y9/lT3ves604TolQ==
Received: from [98.137.12.63] by nm8.bullet.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
Received: from [98.137.12.203] by tm8.bullet.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
Received: from [127.0.0.1] by omp1011.mail.gq1.yahoo.com with NNFMP; 14 Apr 2017 16:42:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 42264.74270.bm@omp1011.mail.gq1.yahoo.com
X-YMail-OSG: eqc9XvQVM1mrgkDhRPwV0G2cHMo_vKPzbDQlSeMSd3pqn1EOyriWcHJER_wtOou nFDeehv7AHJqd.YrXze9Hk3sAE_nrK1iBCz17V8CHS8p.XGqN0Gns52KNPg57CvP6PBLzNtj5.7y JtCDva7iAX91PVsWQMNmAtlCLp8lcBTuA6e2lFEjJauho9MAkYPaFLTVYYIaDJb6mJ0XVIZ0Zpf9 7fw5em.w51FLz2p5ysOzcEnHBlS3Obi4yfGhdQZ6LdW5BxzMymjZChV_Ie9fKT3RUr0.jSQVgkz_ YaBU3Cg8t4bwfaeaS8HH.BVmQ7TKf8AAeZOs0gbE_wRmnwFjzkxaEQKWSj2e6ZvAaJz9_r8DyI.J PZozBa5ZVh8dJjmga8ocg0EfVlEJ7wB7P9EjMc0SUNYm.RpHKSbWLi9uUaG2GYDwq.1ZNY6ubJUb w1M1VXTtC.vjDImFDAtOsWJeGcVD_ENdkx6Ju1_NaOhuET1u2I2vPRYWvjCcHjHxzHERzTA7zZPK TiITobvYN0CvdtSVWYaAMzSznIRu6aOv4d1sSeX33b08VqnuQlEU-
Received: from jws300014.mail.gq1.yahoo.com by sendmailws147.mail.gq1.yahoo.com; Fri, 14 Apr 2017 16:42:23 +0000; 1492188143.673
Date: Fri, 14 Apr 2017 16:42:23 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
Reply-To: <nalini.elkins@insidethestack.com>
To: <dcrocker@bbiw.net>, IETF <ietf@ietf.org>,  Fernando Gont <fgont@si6networks.com>
Message-ID: <2078246913.570269.1492188143169@mail.yahoo.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <2078246913.570269.1492188143169.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9408 YahooMailBasic Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFTGd-bYmPbfEo7FfvqxA2gIij4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:42:26 -0000

Guys,

Sorry for the top post.  (Running out the door!)  =20

There were a number of volunteers in the Chicago IETF to help revise / recr=
eate from scratch a remote hubs draft.   I was busy with other tasks but wi=
ll get this going next week.

If anyone else would like to volunteer to help, pls let me know.     I have=
 a feeling that we will end up doing virtual group work meetings every two =
weeks to get / review input.

Thanks,

Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

--------------------------------------------
On Fri, 4/14/17, Fernando Gont <fgont@si6networks.com> wrote:

 Subject: Re: IAOC requesting input on (potential) meeting cities
 To: dcrocker@bbiw.net, "IETF" <ietf@ietf.org>
 Date: Friday, April 14, 2017, 9:32 AM
=20
 On 04/14/2017 05:11 PM, Dave
 Crocker wrote:
 > On 4/14/2017 9:04 AM,
 Fernando Gont wrote:
 >> FWIW, for the
 developing world, remote participation has possibly
 always
 >> been a necessity.
 >=20
 >=20
 > Indeed.=C2=A0 I hadn't understood how
 extensive this had become until seeing:
 >
=20
 >=C2=A0 =C2=A0 https://tools.ietf.org/html/draft-elkins-ietf-remote-hubs-0=
0#section-3
=20
 I haven't checked the I-D.
 However, no matter what it says, there's
 remote participation with meet echo, without
 hubs. For instance, I
 participated (and
 presented) remotely in two wgs during the Chicago
 IETF, without "attending" any hub.
=20
=20
=20
 > However, there is a significant difference
 between their current mode of
 >
 integration with the 'main' venue site, versus what
 we will need to have
 > remote sites able
 to have nearly seamless participation in sessions.
=20
 What I tried to note is that
 the situation for part of the participants
 is such that remote participation is already
 necessary.
=20
 >From the pov
 of participants of North America or Europe, this *might*
 be
 different and the current situation might
 be a game changer. But for us
 in latin
 maerica, remote participation has always been a need, even
 if
 we managed to attend one or more meetings
 (that's kind of like "the
 exception
 to the rule").
=20
=20
 > Some of this is functional, such as a
 single queue for everyone wanting
 > to
 speak, no matter where they are.
=20
 Agreed.
=20
=20
 >=C2=A0 Some of this is much more robust
 > performance and reliability (within
 obvious networking limitations.)
 >=20
 > I suspect the easiest bit will be improved
 usability design, since the
 > Meetecho
 folk tend to start with reasonable design and make
 improvements
 > quickly, as experience is
 gained.=C2=A0 But yes, from some comments over the
 > last two meetings, there's probably
 room for that improvement.
=20
 I must say that modulo issues with the network
 (which were probably
 local on my side), the
 experience was great, and I must say that the
 meetecho folks provided "online" help
 in a very timely manner (thanks!).
=20
=20
 There's room for
 improvements.. but in some cases they seem to be more
 about integration of local and remote
 participants, than with "bugs" in
 the tools themselves. e.g., as you've
 correctly noted, it would be great
 if there
 was a means for managing the mic queue, such that
 there's a
 single queue, that includes
 remote participants.
=20
 Thanks!
=20
 Cheers,
 --=20
 Fernando Gont
 SI6
 Networks
 e-mail: fgont@si6networks.com
 PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4
 AE25 0D55 1D4E 7492
=20
=20
=20
=20
=20


From nobody Fri Apr 14 09:45:00 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB3BB129421 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.803
X-Spam-Level: 
X-Spam-Status: No, score=-0.803 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 YWQdgnysBbbh for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:44:57 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 322DD128B8E for <ietf@ietf.org>; Fri, 14 Apr 2017 09:44:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 1944788013F; Fri, 14 Apr 2017 09:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1492188297; bh=n/AdIzfuaLBpN3JoMPrsPpW9opk0UOuPgylTZIGapU0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=pjiKb5M/U9CxY+pDN2Di2Y0Z9ho79AEQ20MpdNjIVi3fSgklZylxt3JcpI30Uua39 9q/Ky4iXBGx1meelfPPY7JRafykTcBXRofQlXxY1AxJXWKmAghPcqLgQulpYMeEi2x i6xiihmwtvsRabEE+D2WN+DhvszWMzeeKMN52dWU=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 87D111C0274; Fri, 14 Apr 2017 09:44:55 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Stewart Bryant <stewart.bryant@gmail.com>, ietf@ietf.org
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
Date: Fri, 14 Apr 2017 12:44:52 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZwyhWlJAfCSjlLOoum_UA49of9o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:44:59 -0000

There is a lot of value in face-to-face interaction.
While we can not always get the interactions we want, virtual 
interaction is no replacement for face-to-face.  Being able to chat with 
people between meetings.  Having folks in the same place to set up 
high-interaction discussions.  And multiple additional benefits.

Yes, funding matters.  But in my view that is secondary to the actual 
benefit of the meetings.  Which is why I attend.

Yours,
Joel

On 4/14/17 12:38 PM, Stewart Bryant wrote:
>
>
> On 12/04/2017 15:30, Michael Richardson wrote:
>> Right, so this is why it's better for everyone to be remote.
>
> Except that the IETF funding model requires attendees to pay their
> meeting fee.
>
> - Stewart
>
>


From nobody Fri Apr 14 09:46:30 2017
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D34C128B8E for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:46:29 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=krsek-cz.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 IaUK-A2GA2eA for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 09:46:28 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 56D5E131461 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:46:13 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id c55so53443854wrc.3 for <ietf@ietf.org>; Fri, 14 Apr 2017 09:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krsek-cz.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=6RA1Zn7wpJzxhomwII2HPNwfn3hv6mkGdkCMQHdKg9s=; b=FVdanLgmx+7ECB3TpS/U2lx0ZCYbv6bwh/7cKehtrFLF/f4FJggOXz5dZfa5nTVvCV vfIx+lVn6Jps/cEhpId7X1ABoWsbjJiQPlLgHh9IaeMIw0XjvypSo+ggbmbo4p/XZ1k7 q9KpHspQe2MEjXdfZFsAOq3zxHq8Y8/z/wxbpfBQMNiAo1MC4DwJ0yMmUSVAbQMM/D2R Byq7KnBL1JY1yMr0x/r8wzFUrZfWhZa4fxuozVLH/PyKJeKO4U3mifaz11RJpVvTqglz eiIWXsAUQgf3EaIgQrdyV1vzs22t9tcliiOTa4nW4IfjGeUF87SRiAOcS67uBRwQ5sm2 KUQQ==
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-transfer-encoding; bh=6RA1Zn7wpJzxhomwII2HPNwfn3hv6mkGdkCMQHdKg9s=; b=m1CKwdUvpZ99PLYwNU7E3jkXbwIXpxN6YuVobt2rnlz5CXvUX6jpnRemBm4I6QfteQ KPxOEsarBHayvwSZdlAifCyAdP182EVrvYH/89hF3uWoULGjD8uV9F2dXu5KZym0Xs8Q 8L4hLRwKCraR5t/Vs8BsKYCUEUdexHbnoJYoWfF73RJGcgAOPV3heWHSZ411XxjN/5kb O7JwjoEGgXgBZZmJso4xmmNnCji8COJMT4yMCdtjgB43HqH9c6yYYcYz7wduJzjUBHKt Ar6z5U1PHPLl54kWdWa+cEQYebvOkP/Pu3AfarBmGpJDvztBWC/XZ05gryKjAnKGkSnq 8f2w==
X-Gm-Message-State: AN3rC/4qZpg+7ZvjfckUm0Q1hi0jwQx9MM5lf5kqAyNTUxfhRt1EI0qD SqCUXVidAQoQ0l987Yw=
X-Received: by 10.223.171.234 with SMTP id s97mr9149384wrc.167.1492188371670;  Fri, 14 Apr 2017 09:46:11 -0700 (PDT)
Received: from Michals-MacBook-Air.local (ip-37-188-238-204.eurotel.cz. [37.188.238.204]) by smtp.gmail.com with ESMTPSA id l186sm3360129wmd.17.2017.04.14.09.46.10 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Apr 2017 09:46:11 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: ietf@ietf.org
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
From: Michal Krsek <michal@krsek.cz>
Message-ID: <2a925214-5235-c629-d19c-a01ef1a89dfc@krsek.cz>
Date: Fri, 14 Apr 2017 18:46:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ny77ETqV8Gr7-liR8SryFma0LgU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 16:46:29 -0000

Hi Stewart,

>> Right, so this is why it's better for everyone to be remote.
>
> Except that the IETF funding model requires attendees to pay their 
> meeting fee.

I believe that the model can be changed, for example remote 
participation may require some small fee too. We need to make remote 
participation as productive as the local one and prepare financial models.

I believe if IETF has meeting to Sydney, at least some local communities 
in Europe or South America prepare their side meetings interconnected 
with the main meeting - and those side meeting organizers may need to 
pay a participation fee - this is just an idea.

             Michal


From nobody Fri Apr 14 10:11:54 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA77124281 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 10:11:52 -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, RP_MATCHES_RCVD=-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 8LrZcosvChFA for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 10:11:51 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90C9B120046 for <ietf@ietf.org>; Fri, 14 Apr 2017 10:11:51 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2B041203B8 for <ietf@ietf.org>; Fri, 14 Apr 2017 13:36:41 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AF027636BB for <ietf@ietf.org>; Fri, 14 Apr 2017 13:11:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Update on feedback on US-based meetings, and IETF 102
In-Reply-To: <D846BB0A-D2B2-424A-9166-F8D591C56EBF@consulintel.es>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <a52be35f-df24-6581-90e6-bc2a262736ea@joelhalpern.com> <56c58cdd-1cc9-2e55-556a-2b799eb6e1cc@cs.tcd.ie> <43378975-daf3-0170-35c7-b57e03b834b2@comcast.net> <D846BB0A-D2B2-424A-9166-F8D591C56EBF@consulintel.es>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 14 Apr 2017 13:11:50 -0400
Message-ID: <16097.1492189910@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3_yWEtMmz2O7nSF7w-J4kGFamkw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 17:11:53 -0000

--=-=-=
Content-Type: text/plain


JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    >     If we cancel San Francisco, how much that is going to cost to the
    > IETF for each of two planned meetings?

And, what is the "break-even" point for attendance?
If people vote with their wallets, what is the impact?

(remember that the revenue that pays to operate the rfc-editor function is
generated as a result of having meetings)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljxAtYACgkQgItw+93Q
3WV3YAf+J6Iw76ttCoqRhaYplqs6i9BKQDU6uqRRZQBwIMwnwleH7gIy+OQweAKX
1eO3tOp4jMm5khsyh6Ud6MfFV26gsrfAZkkXPKj7iJzzkBPtI29ntPFrzNb2D4HK
/9Zw7hcEkezFzqkYqcb2QGE7oCM2QUtHGwEOHLFRfeqR5Qz1FpSK7EyUnwFCXE0Y
91RKHUBND4ertMkb/OGc2AFVpfahvT52ekIPU801OFQRUerHo7PmXBMzPrY1J5TU
R2wUh2zCqpyBAzDUFfYE5ae7MeBKRFbm4bMtVxN5XROJBHT1ghNGYyxKa91NxVmw
JcKaTnBA7jP7n7ORLw8qZ2lbXOQ7UA==
=HAAd
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr 14 10:31:57 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50C511292AE; Fri, 14 Apr 2017 10:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 AowJfTG5QejC; Fri, 14 Apr 2017 10:31:46 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6BDC127977; Fri, 14 Apr 2017 10:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7807; q=dns/txt; s=iport; t=1492191106; x=1493400706; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=9NEbkVvw/IkjC1VU3PW1tH4xRvviYd5eETLFfJfZI1s=; b=dn2VcASAJjlUjJIJ5/pRO0+LaQV/G1uFekBjTXkhdkcBqgXpmYDYvp/Q T9eIaJBwVRN688MFfGDTHGVnkRq79sxTVFT4xhWAdFF786aFX3ZfHaA5n XGW+YqIMNKbactLXMzmARmbP+7FHLtUilJtAes+YUgIWXZr/xJog/5Lu3 Q=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeBAAqB/FY/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBiSWLCKZHgg8Hhh0ChEAWAQIBAQEBAQEBayiFFgYjQw8EEAtCAgJ?= =?us-ascii?q?XBgEMCAEBEIoDqRyCJoFHiU4BAQEBAQEBAQEBAQEBAQEBAQEBEA+ILiuBYgGBC?= =?us-ascii?q?YE8gnaDKoJfAQQ0hkKEFZIMg36CEINZg3CFDoF/GYhRhl2IaYshJgsmgQUmHQg?= =?us-ascii?q?YFUGEboF1PoczBII5AQEB?=
X-IronPort-AV: E=Sophos;i="5.37,199,1488844800";  d="asc'?scan'208";a="652158914"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Apr 2017 17:31:39 +0000
Received: from [10.61.201.40] ([10.61.201.40]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v3EHVdp8002457; Fri, 14 Apr 2017 17:31:39 GMT
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: John C Klensin <john-ietf@jck.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <3DF53F6ACE338CACF247F910@PSB>
Cc: iaoc@ietf.org, ietf@ietf.org
From: Eliot Lear <lear@cisco.com>
Message-ID: <4df26dec-b244-b09b-5c29-195c25d95565@cisco.com>
Date: Fri, 14 Apr 2017 19:31:38 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <3DF53F6ACE338CACF247F910@PSB>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ViL0AqPXBQeRMiWKQ0pqg2MeTTcMK5fw2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GYmYAArhkKUbyscE_6r7cP7nTPQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 17:31:48 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ViL0AqPXBQeRMiWKQ0pqg2MeTTcMK5fw2
Content-Type: multipart/mixed; boundary="COG1rV9EtGeSVnhSd5Xpc7b75HDoSXB9C";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: John C Klensin <john-ietf@jck.com>,
 Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: iaoc@ietf.org, ietf@ietf.org
Message-ID: <4df26dec-b244-b09b-5c29-195c25d95565@cisco.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
 <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
 <3DF53F6ACE338CACF247F910@PSB>
In-Reply-To: <3DF53F6ACE338CACF247F910@PSB>

--COG1rV9EtGeSVnhSd5Xpc7b75HDoSXB9C
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi John,


On 4/13/17 8:35 PM, John C Klensin wrote:

> (1) We are living in very unstable times in which reliable
> predictions of the long-term future, or even the future for the
> 3 to 5 years out that the IAOC thinks the community has told it
> to plan meetings, is even more difficult than usual. There are
> strong reasons, connected to our traditional criteria such as
> locations near where concentrations of the participants live and
> appropriate facilities, for meeting in the US, and we should
> avoid meeting in the US only if the circumstances and logic make
> sense.

The same holds true for other regions.

>
> (2) I don't believe in canceling, or refusing to hold, meetings
> in a particular location to make a political point or to punish
> a government that we see as behaving badly, if only for the
> purely pragmatic reason that few governments are likely to pay
> any attention at all to where we do or do not hold meetings.
> Certainly the US is not one of the exceptions.   However, if we
> do make decisions on that basis --and some of the on-list
> comments have sounded very much like that-- then we'd better be
> ready to schedule meetings for those countries, on
> shorter-than-usual notice if necessary, to reward them if the
> policies are changed.

I largely agree with you on this point.  The basis of whether to hold a
meeting is whether the organizers believe that the objectives of the
IETF can be achieved.  If as individuals a great many of us make known
that we would refuse to attend a meeting because of the locale, then the
likelihood of holding a successful meeting is diminished.  Thus, we
don't really require additional rules in this regard.

>
> (3) Circumstances change.  Not just political circumstances (who
> would have predicted a year ago that the US would be in its
> present state now?), but there is always a risk of hotel or
> neighborhood remodeling or construction and natural and
> human-made disasters that could severely impede a meeting or
> attendance at it.  It seems to me to be very important that we
> think through the circumstances under which we would pull the
> plug on a venue on short notice -- whether to try to find a
> different location or to go largely or entirely remote -- and,
> as others suggested during the mtgvenue session, that we keep
> that set of discussions rather separate from how we do
> longer-term meeting planning.

I think that's a worthy discussion, but as editor of that doc, my plea
is that we not get bogged down in it just yet.

>
> (4) I have no idea how to predict likely US policies toward
> visitors (or residents traveling outside the country and trying
> to return) six months out, much less three to five years in the
> future.  The government's sudden policy reversals in several
> other areas in the last two weeks should add to everyone's
> uncertainty, as should the possibility that the courts will
> continue to block obnoxious policies and punish those who
> profile and harass selected visitors.   The threats to require
> passwords, inspection of phones, and similar nonsense of people
> who are now covered by visa waivers may turn out to be a real
> issues or as hollow as promises to brand China a currency
> manipulator turned into during the last 48 hours or so.

These aren't mere threats.  The CPB *already* does require *some* people
to unlock their devices.  As inconvenient as that might be (a) it is not
new, and (b) it is by no means unique to the United States.
>
> Equally important, it is impossible to predict British policies
> as Brexit evolves nor what other countries might do in
> retaliation or response to those policies, US actions, etc.
> Given other forces in the world, I think it would be unwise to
> place large bets on the Schengen agreements being unchanged
> three or five years from now, especially where holders of non-EU
> passports are concerned.  Similar issues apply in Asia: for
> example, I hope that we won't see sufficient destabilization on
> the Korean Peninsula to make a meeting in Seoul or even Busan
> inadvisable, but, if the macho chest-pounding, posturing, and
> implicit threats by assorted crazy-spectrum people continues,
> one never knows.   I think it is pretty safe to suggest that it
> would be unwise to plan a meeting for Damascus or Aleppo three
> years from now, but no one has seriously proposed either city. =20
>
> However, within sensible limits (with the two Syrian examples
> mentioned as examples of non-sensible cases), I'm opposed to
> making _any_ changes in our long-term meeting plans based on
> rapidly changing political considerations, including but not
> limited to events in the US or UK in the last year.  Again, I
> think it is important to monitor things as meetings get close
> and to have some community consensus about the circumstances
> under which we would make significant changes in meeting plans,
> but deciding to hold (or not hold) a meeting in the US based on
> fears or fantasies about what has happened in the last six
> months (or overconfidence about how those things will play 9ut)
> and where those things might lead makes no sense to me.

Stability is an important aspect, when considering all of this.  It also
seems to be diminishing commodity.

The IAOC can only work on the information they have at the time that
they make decisions.  At THIS time, people are being refused visas and
being turned away at the border in a nearly indiscriminate fashion.=20
Maybe not a lot, but perhaps enough (where "enough" is going to be in
the eye of the beholder).  While it is true that the situation could
calm down in the next few months or years, that is NOT the information
we have at THIS time.  At the end of the day, the IAOC must make an
assessment as to whether or not they are likely to hold a successful
meeting in the U.S. in several years' time.  If they judge that the
meeting would exclude a good number of people, where in, say, Canada the
refusals would be lower, why wouldn't we hold the meeting in Canada
instead (not that Canada is perfect)?

Eliot



--COG1rV9EtGeSVnhSd5Xpc7b75HDoSXB9C--

--ViL0AqPXBQeRMiWKQ0pqg2MeTTcMK5fw2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY8Qd6AAoJEIe2a0bZ0nozvwkH/RFc3KfDwHyBodfmnPLo7GR7
qdW1W/IpqY+MTURG+wpeqJWNRUnyl/Row3sBKJKM/IfwO1K/1qRs28zM6D8gX1/j
wtjfJrCz3/mkBFNRZJ18jh61+HL6xMWNWMo+DpfRtNnJ/kc3UTKjdmDoPpEExioy
CYOxGGMu5+ZXQ1CzkPDtBT5SySXnN1FvB74CccCEY9YI+lQT3SHxfnwESBgl5ABT
lp3fLRkU7qdtA+YRtH5WtDwhy6+70UgPEPa2+ClCvBSnL5+gAYTODs5MnGELwzVE
QMsA38oAyQ3I+gBi2m9xLwQU50ECPk0P7DcK5Wm5TQmrLg6ymsuDhMiXY1V0GaI=
=k0mP
-----END PGP SIGNATURE-----

--ViL0AqPXBQeRMiWKQ0pqg2MeTTcMK5fw2--


From nobody Fri Apr 14 10:49:21 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456A8120725; Fri, 14 Apr 2017 10:49:20 -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, RP_MATCHES_RCVD=-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 BNiZyC-3fyzl; Fri, 14 Apr 2017 10:49:18 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B75E81294CF; Fri, 14 Apr 2017 10:49:18 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cz5LP-000LHR-E3; Fri, 14 Apr 2017 13:49:15 -0400
Date: Fri, 14 Apr 2017 13:49:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Taht <dave.taht@gmail.com>
cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, iaoc@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Message-ID: <8AC41042FC6544B50B0D40F2@PSB>
In-Reply-To: <CAA93jw7ScrfQQc2FsN1mHupniC_CCyP=uO87A_imLpCFufH3mA@mail.gmail.com>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <3DF53F6ACE338CACF247F910@PSB> <CAA93jw7ScrfQQc2FsN1mHupniC_CCyP=uO87A_imLpCFufH3mA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qPVhIUE48XYEb6ku9RriQcj6ei0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 17:49:20 -0000

--On Thursday, April 13, 2017 11:42 -0700 Dave Taht
<dave.taht@gmail.com> wrote:

> I find meetecho to have evolved to being an effective tool,
> and no longer intend to attend ietf meetings in person. I'll
> miss the beer, company and cookies; won't miss the travel and
> hotel hassles.

I'm not quite at the point of "never", although Chicago was my
first f2f meeting in a few years.

However, even weighting the beer, company, and cookies in, I
think you identify another factor that the IAOC should consider
and that may affect the present discussion and especially the
short-term changes in policies, practices, or facilities:  I
think it is likely that, over time, more people will follow your
lead in not finding f2f attendance at particular meetings
critical and, in particular, in not attending meeting that
appear to them, perhaps not long before the registration
deadline, to be more trouble then they are worth.   Could that
result in reduced attendance in July 2018?  Sure, although
probably not as much reduced as Michael's "local west coast
attendees" prediction.  But suppose that, by then, US border
policies have stabilized back to around the 2015 status quo
(plus or minus some ongoing ranting that people might have
learned to ignore by then), UK policies are in a state of some
disarray a year into the Brexit transition, and a non-trivial
number of people find Singapore inappropriate because of issues
discussed at great length on this list and/or a bit expensive
for their tastes or budgets.  That combination of scenarios --
none of them especially far-fetched -- with those of us who like
to get to a meeting occasionally even if we expect to be remote
most of the time  plus locals looking in to see what IETF is
about (IIR, we've had a large number of those in previous
meetings in the Bay Area and down the peninsula) could easily
lead to a larger-than-expected attendance in San Francisco (even
if the IAOC has already estimated the last factor and included
it in their estimates).    

That is a really bad game to play, especially if one remembers
how restive the community gets when meeting rooms are too small
for WG attendees to get into them.

While I think it is less likely than that US policies 15 months
hence will be a lot closer to where they were a year ago than to
what Trump tried to put into effect in January, were changes to
occur in Singapore that would result in visa requirements for
everyone and requirements to indicate religion and sexual
preferences on applications, previous discussions on this list
would imply that meeting would be, IMO, in a _lot_ more trouble
than we can anticipate for San Francisco.

And that, again without underestimating the difficulties or
costs of meeting cancellations, moves, etc., brings me rather
quickly back to "can't predict what will happen nearly well
enough to make finely-tuned plans wrt either countries or cities
within those countries on the basis of immigration/ travel/ or
border policies" so the most useful strategy is the general
policies we've been following, with as much flexibility for
unpredictable fluctuations in attendance vis-a-vis projections
as we can get.  Either that or, in the hope that we can predict
that far in advance (which might not be true), we just stop
trying to set meeting locations more than a year in advance with
whatever that implies about choices, costs, conflicts and
disruption (including probably needing to cancel some meetings,
or at least move dates around, because we can't otherwise find a
place to meet).  Probably can't have it both ways.

    john




From nobody Fri Apr 14 11:20:05 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1088912951D for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 11:20:04 -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, RP_MATCHES_RCVD=-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 Wg0M-dcpuFHW for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 11:20:02 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89E3129511 for <ietf@ietf.org>; Fri, 14 Apr 2017 11:20:02 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0CDA5E1E5; Fri, 14 Apr 2017 14:44:52 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5E3F1636BB; Fri, 14 Apr 2017 14:20:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Stewart Bryant <stewart.bryant@gmail.com>
cc: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 14 Apr 2017 14:20:01 -0400
Message-ID: <386.1492194001@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v581zZoSlHCU1EqpDtTbWGVsSLY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 18:20:04 -0000

--=-=-=
Content-Type: text/plain


Stewart Bryant <stewart.bryant@gmail.com> wrote:
    > On 12/04/2017 15:30, Michael Richardson wrote:
    >> Right, so this is why it's better for everyone to be remote.

    > Except that the IETF funding model requires attendees to pay their
    > meeting fee.

That's orthogonal, but a very good point.

And it's why turning SFO into a large "remote hub" (with a fee, and cookies) might make sense.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljxEtEACgkQgItw+93Q
3WUd1Qf+PqP+9qf7NeHHefOuc7A3LUzxPaBJQWasbX7c8cO9OLCp3Hnz14l728Fc
+YiFCOCPF325yNhNFU1eGhWglRfJjhmnU4q4xv5ZbCdjsM7hIdGc84Y9Dj97eEa9
bpGZLqU71LgmxGuJljI4huONHqXYnhuMc4zJJtgPA8s/gkPubqtYnrJKxtwQFjNn
OG6/OqMc9RVxVyhx0gjKzSq7yiY8cqaiKDoNmYzP7Jca6lQ94fq5+hlq9NrmOl2/
65yX1MAw/D21T0JUlBM66gSWX6RFciBIwcixQU/ScQHsTMEqKs1qmgQW0NW6/g+P
FwpB4lTrCqh6sL6rS22A6vc988KRFA==
=ObNW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr 14 13:29:41 2017
Return-Path: <ldaigle@thinkingcat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8097129A97; Fri, 14 Apr 2017 13:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.589
X-Spam-Level: 
X-Spam-Status: No, score=-4.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=thinkingcat.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 E_Eklj5aTZF6; Fri, 14 Apr 2017 13:29:38 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60C79129649; Fri, 14 Apr 2017 13:29:38 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTP id C37C830002B26; Fri, 14 Apr 2017 13:29:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=c OruOykq847tkvSTL2Fpb41PgTY=; b=ZaMOBW0twC/D/qUk13EE2qLggMUdudosW AxgVOU4vlj/s+Dnfvvpz/dkMPe6w48xpStf/Yn6a/bOXB3dQP9rox5xAS+iIB96b dR8V6qSiVnK6awLBPojBxQDES1PwvFBbBpBN40iIrFyCiW/BNhXEFS7FSbLlxBz0 tzgAKpIm9U=
Received: from [192.168.1.5] (pool-173-72-147-193.clppva.fios.verizon.net [173.72.147.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTPSA id 5D66030002B21; Fri, 14 Apr 2017 13:29:37 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc: ietf@ietf.org, iaoc@ietf.org
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Date: Fri, 14 Apr 2017 16:29:36 -0400
Message-ID: <BA8E6E50-20D9-4015-87EB-B2CFF69DE67A@thinkingcat.com>
In-Reply-To: <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uuT8d4DArEXfWl54Xq35kL7YmkU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 20:29:41 -0000

Stephen,

Apologies for taking so long to respond =E2=80=94 quiet minutes in front =
of a=20
computer keyboard have been distressingly scarce this week.

In-line:

On 12 Apr 2017, at 20:00, Stephen Farrell wrote:

> Hi Leslie,
>
> Thanks for the update. One query...
>
> On 13/04/17 00:39, IAOC Chair wrote:
>> The general comments on meeting in the US played along the same lines
>> as has been shared on the IETF discussion list:  people are variously
>> for moving all meetings out of the US, or adamantly against, or
>> somewhere in between, each position supported by good reasons.
>
> I have seen mail to the list that argued for not meeting in the US
> within our current planing horizon. Some of that was adamant. (For
> clarity: I'd agree with the position that we ought not risk meeting
> in the US for a few years, incl. that we ought, if possible, move
> ietf-102 on the basis that the we don't have a predictable situation
> with the US at the moment and that we ought not plan to meet in any
> place that's currently that unpredictable.)
>
> I do not recall the opposite on the list, i.e. someone adamantly
> arguing that we ought continue to meet in the US. There were some
> mails that I'd say maybe weakly argued for continued US meetings
> in the relevant timeframe. But nothing approaching adamant.
>
> Is that my bias in reading the list traffic or did I miss some mail,
> or is it possible that the (public) list traffic and (relatively
> private) survey responses are less similar that your mail implies?

I think subsequent traffic has exposed more of the contrary thinking,=20
and I don=E2=80=99t want to belabour it here.

To the specific question of =E2=80=9Cwhere has this been said=E2=80=9D,  =
I=E2=80=99m=20
referring to the messages on the IETF discussion list, as well as=20
messages sent to the venue-selection mail drop address.  (That=E2=80=99s =
not a=20
discussion list, but the archive is public, in the usual IETF site=20
sources).

While we didn=E2=80=99t intend the request for input on specific cities (=
i.e.,=20
messages to venue-selection) to supersede the targeted questionnaire=20
about travel experiences, people=E2=80=99s responses there do reflect the=
=20
issue of US travel.

Leslie.


>
> That last wouldn't be surprising, but I'd hope that in that case
> some of the people who filled in the survey who adamantly said we
> ought continue to meet in the US would be willing to justify that
> on the list. If none were, then I think the IAOC ought consider
> that as a relevant input in their decision making. (Not as a
> winning argument, but as a relevant thing.)
>
> Thanks,
> S.


--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------


From nobody Fri Apr 14 15:45:58 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61137129B02 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 15:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 Gbb_zqg88-_3 for <ietf@ietfa.amsl.com>; Fri, 14 Apr 2017 15:45:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 5145B129B01 for <ietf@ietf.org>; Fri, 14 Apr 2017 15:45:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cz9yQ-0006ea-9D; Fri, 14 Apr 2017 22:45:50 +0000
Date: Sat, 15 Apr 2017 07:45:48 +0900
Message-ID: <m2h91qwqub.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
In-Reply-To: <8AC41042FC6544B50B0D40F2@PSB>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <16010f27-e86b-b17d-4a13-62645e0bdc89@cs.tcd.ie> <3DF53F6ACE338CACF247F910@PSB> <CAA93jw7ScrfQQc2FsN1mHupniC_CCyP=uO87A_imLpCFufH3mA@mail.gmail.com> <8AC41042FC6544B50B0D40F2@PSB>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v12rvo2xb4XpPWUMyFEW3G-i2i8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 22:45:56 -0000

attendees are not fungible


From nobody Sat Apr 15 02:36:07 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FBF12704B; Sat, 15 Apr 2017 02:35:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: <gen-art@ietf.org>
Cc: dhcwg@ietf.org, ietf@ietf.org, draft-ietf-dhc-relay-server-security.all@ietf.org
Subject: Genart telechat review of draft-ietf-dhc-relay-server-security-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149224895859.15792.12555844017714647455@ietfa.amsl.com>
Date: Sat, 15 Apr 2017 02:35:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6FKW2o07w8dX_fGawN2toTEbA-8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 09:35:59 -0000

Reviewer: Francis Dupont
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dhc-relay-server-security-??
Reviewer: Francis Dupont
Review Date: 2017-04-15
IETF LC End Date: 2017-03-13
IESG Telechat date: Not scheduled for a telechat

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: I talked with authors at the IETF meeting: my
comments were addressed.




From nobody Sat Apr 15 02:52:31 2017
Return-Path: <chopps@chopps.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60984127201 for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 02:52: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, RP_MATCHES_RCVD=-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 uvWJKTr7aSK7 for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 02:52:29 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id F13E61242F5 for <ietf@ietf.org>; Sat, 15 Apr 2017 02:52:28 -0700 (PDT)
Received: from pip.chopps.org (97-83-46-222.dhcp.trcy.mi.charter.com [97.83.46.222]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 5FDAE62E41; Sat, 15 Apr 2017 09:52:28 +0000 (UTC)
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
User-agent: mu4e 0.9.19; emacs 25.1.1
From: Christian Hopps <chopps@chopps.org>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-reply-to: <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
Date: Sat, 15 Apr 2017 05:52:26 -0400
Message-ID: <87inm6uhet.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rn9syjoTOoBplRjReZt9_ud1pok>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 09:52:30 -0000

--=-=-=
Content-Type: text/plain


Joel M. Halpern <jmh@joelhalpern.com> writes:

> There is a lot of value in face-to-face interaction.
> While we can not always get the interactions we want, virtual interaction is no
> replacement for face-to-face.  Being able to chat with people between meetings.
> Having folks in the same place to set up high-interaction discussions.  And
> multiple additional benefits.
>
> Yes, funding matters.  But in my view that is secondary to the actual benefit of
> the meetings.  Which is why I attend.

+1

Whenever I read messages that advocate for switching to remote only
meetings, I have to wonder, are those people just not getting what I get
out of f2f meetings? I find the meetings invaluable for the reasons you
list above.

Thanks,
Chris.

>
> Yours,
> Joel
>
> On 4/14/17 12:38 PM, Stewart Bryant wrote:
>>
>>
>> On 12/04/2017 15:30, Michael Richardson wrote:
>>> Right, so this is why it's better for everyone to be remote.
>>
>> Except that the IETF funding model requires attendees to pay their
>> meeting fee.
>>
>> - Stewart
>>
>>

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEEm56yH/NF+m1FHa6lLh2DDte4MCUFAljx7VsACgkQLh2DDte4
MCUGng//SgzHljzUUYyvSI+YyBOb8yCJlHmB71IZRG1ogYMICXphZqXH74JtaBjW
Hyx8vsJdw7SErlb0nE0sF8hhRTDDbkGpPhp8xrqTXivtym/YITVJJz1UKKBCocwx
TYv0w8WFJ2ss9BBsGwJYv47fCfBB8kin11u753UTxIqrxQkeM6IC6jJhprNUgnap
qcspKhEpqi7S60TZtxvxiwkqh6gVC31QQRJC+nMUSqv0u0XhdV+WFg8F32/3KBTm
XrlgbbKRsDNMcJE46OXUUJ1c7Wg55HuSFOnE6sOIJcBkaUnSkQ+RlEfurrusir75
ODAloiiojbxbeC154SIrf6zyfDg36P2sbrwoQ+tyMsYd0Y8SAKaq/2qDqgHut37N
8nucs3wjFTIV1WG9ZzXskP2doR7AM0WP1NtS58a615qDiNUuhwTip9UTUSgYNM0Q
SvMDYd0GhTC8f5I4p2y9+JgwVuTwIk9uk7YEu8B8c/tGLRzYk6iu2A+tgH3DkvwN
PXNM64GyTgT/jPIR7lPuxhDLWymr6N1wU7RtbAEC1ffrrLAny1ZDYNaP7fyU04Es
aFfNSKlHH3lewTfha7/MnPAhoZVUhhQ8vFdWh68Ftfmeo80IBUv0DQ8oE/HjPuv3
6l7ngpIy7n+jeKj/f3dMXpQKzN41x6/bgUmhSiHx0ipuyHVY77g=
=aTlG
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Apr 15 06:09:55 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84BCD128896; Sat, 15 Apr 2017 06:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 mj0CTJCRmJ6H; Sat, 15 Apr 2017 06:09:50 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071015.outbound.protection.outlook.com [40.92.71.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2293A1287A5; Sat, 15 Apr 2017 06:09:46 -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; bh=OXgxhhBfzMslQ+5KE5H88endtqGh3o3jbEyngfISabY=; b=DXGt3EqFrH1FcG7yTRrcsR6JvlPQ+UklxZ0gpExR0Fq+vaM1np3sPpaWjlJqS8DSoNyFUMSc9OS5k1oHaxjzpFCNdfACKqN9ET1G2vnHwsFyaF73/F93xP6VlkJfHaBDJwVGVA4AtDGmNsFGBCp+HwC9Xw3BNKqJriKLPGlf+lvju9fEVSov5Yn63n8ROmWQ29X+q31yGFEpAOydV/uaCXhTR/DNbdmdA2rnInKnkPFVY6PvVRO7SPrvhY9MqnulPigPFA8WiRLXv87uyxcCfmErOXEuPzq8ULajeDfgCx4rZ2nwM9eoUkA/3mFzCuvxyaXXdmarWjGlcmcuUAQW9w==
Received: from DB5EUR03FT036.eop-EUR03.prod.protection.outlook.com (10.152.20.52) by DB5EUR03HT058.eop-EUR03.prod.protection.outlook.com (10.152.21.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Sat, 15 Apr 2017 13:09:44 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.20.57) by DB5EUR03FT036.mail.protection.outlook.com (10.152.20.185) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Sat, 15 Apr 2017 13:09:44 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1034.013; Sat, 15 Apr 2017 13:09:43 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: int-area <int-area@ietf.org>
CC: intarea-ads <intarea-ads@ietf.org>, intarea-chairs <intarea-chairs@ietf.org>, ietf <ietf@ietf.org>
Subject: Google Statistics for IPv6 adoption.
Thread-Topic: Google Statistics for IPv6 adoption.
Thread-Index: AQHStemMObrieeNbo0ud4Z8rRPM6OA==
Date: Sat, 15 Apr 2017 13:09:43 +0000
Message-ID: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:FFE03545556BCDEBA2D3109C0666321BB487231BD3EB942A04FDC83748B4EE1D; UpperCasedChecksum:A30836456D95F638FCAD4CDEBBD3A6774D5DB242DC4A00769140B398718C6F91; SizeAsReceived:7836; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; DB5EUR03HT058; 5:/CqLmBwsopzT2jGHdKrJqfSoyqNnHVtsg8mmX40s6XRaOF+70TUS/v6lRus0OVXDuV1YWtiigho5fOuRK5uL/ZpDqNHy99VpXUV5wXHsNTj8GTaippG9L6w+OCiCuwhxPc6r5A9KbJmTmVYDBZjr+E2V4homnDfJcficxFAENNo=; 24:SlWrJD6oIuY73UvGwjhUSK7yUGppGg8V6NnuOtk47OCgPNL7p4TR5WE8TQqt1hNE+L5pWt+o8aHdzghnwJ9hJ2gdMdxbQrM9VBNqRpoUOPk=; 7:Geg3SWJUUBk6MSXQObAKjMDFV5DaTr+CU09yn8zLOIGJvAaQyutvQWnHb56OszmhFTko7uXjDVeFzyHYJxf8e5suRyeuJ96WrpYI0r+tfigw1jh+PxsXWEcj9N1GEbCqc4fjIQb/o5TTyjPtHcs+bOENk5RXph8t0MFg/jzv4AnSkwUm4zRHK4IoDLd1d+/rpiFKPq1xQpX6OiEMwXaXMQCc+oMGsG5PCMCsLzbwd+MDkwUeTBMIySsMQVrXasEMj4biUjQFztd2ott4pa0DixY81YNs9fv73r99N4M7PUz86DUB7Ro6IEpIrip+p74H
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR03HT058; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 40e0a035-f296-458c-c5d7-08d48400adee
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:DB5EUR03HT058; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:DB5EUR03HT058; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR03HT058; 
x-forefront-prvs: 02788FF38E
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_002_AM4PR0401MB22419992B651EBBA3FC9B6FEBD040AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2017 13:09:43.6420 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT058
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gvLw4zEb09mrrTwGOotmqUiqRZA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 13:09:52 -0000

--_002_AM4PR0401MB22419992B651EBBA3FC9B6FEBD040AM4PR0401MB2241_
Content-Type: text/plain; charset="utf-8"
Content-ID: <B44DB1A30E9050438FB4FF3E916E1841@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

SGkgYWxsLAoKUGxlYXNlIGNoZWNrIG91dCB0aGlzIGxpbmsgdGhhdCBzaG93cyB0aGUgc3RhdGlz
dGljcyBvZiB0aGUgSVB2NiBhZG9wdGlvbiBvdmVyIHRoZSBwYXN0IDEwIHllYXJzIG1heWJlIGl0
IHdpbGwgbWFrZSB5b3UgYmVsaWV2ZSB3aGF0IHdhcyBzYWlkIGVhcmxpZXIuCgogaHR0cHM6Ly93
d3cuZ29vZ2xlLmNvbS9pbnRsL2VuL2lwdjYvc3RhdGlzdGljcy5odG1sCgpSZWNlbnQgSVB2NiBh
ZG9wdGlvbiAoQXByaWwsIDIwMTcpIGlzOgoxNC44MyUgTmF0aXZlIC0gMC4wMyUgNnRvNCAtIDE0
Ljg3JSBUb3RhbAoKQmVzdCByZWdhcmRzLAoKS2hhbGVkIE9tYXI=

--_002_AM4PR0401MB22419992B651EBBA3FC9B6FEBD040AM4PR0401MB2241_
Content-Type: image/png; name="Screenshot_2017-04-15-15-07-48.png"
Content-Description: Screenshot_2017-04-15-15-07-48.png
Content-Disposition: attachment;
	filename="Screenshot_2017-04-15-15-07-48.png"; size=167709;
	creation-date="Sat, 15 Apr 2017 13:09:42 GMT";
	modification-date="Sat, 15 Apr 2017 13:09:42 GMT"
Content-ID: <236941C060443843A72D65F93C5E6312@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAABDgAAAeACAIAAACkA3BdAAAAA3NCSVQICAjb4U/gAAAgAElEQVR4
nOydZ0BUR/fwZwu9sxTpoIIgKFXEggXE3hVLorHGkkhijyY+xsSo0YgaSyyJUVExxlhQ7A1QEZGq
gEgoIr2XBZZdtrwfJpn3/rexLAuoOb9Pw92ZuWcut8yZOQUhAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAA4N2G0dUCdAbW1tZ9+/ZlsViNjY08Hq+rxQEAAAAAAAAAoBVoXS1AK8yY
MWPOnDmlpaVLlixRormJiUlISIinpyf+88SJE5cvX1apgAAAAAAAAAAAqB5mVwvQsaxcubJv374i
kejvv/9uamoqKirqaokAAACADsfCwuKjjz7y9va2sLBACLHZ7Ojo6PDw8JKSEmo1PT298ePHT5gw
AVdDCCUmJiYmJkZGRrLZ7C6Quy0MGzZs/PjxuBwVFRUZGUl+eq/HBQAAQPiQFRUHB4e+ffsihH77
7bdr1651tTgAAABAZzBs2LDVq1fr6emRI3jiPnTo0LVr12ZlZeGDTk5Ou3fvplZDCHl7e3t7e0+Y
MGHNmjViWs07hZ6eHnWMiYmJ5Kf3elwAAABU6F0tQAfSo0cPhBCXywUtBQAA4D+C2Az+3Llz586d
w9sIenp6W7ZsIdWos/nIyMhjx45FR0fjPy0sLJYuXdrZoreFNWvWiKkimPd9XAAAAFQ+5B0VDQ0N
hBCHw+lqQQAAAIBOwsnJiUzTjx07du7cOYQQm83Gjo4WFhZOTk5ZWVlLliwh1UJDQ4nd1OzZs3HN
oUOHdoH0ijFs2DBZ4r3X4wIAABBDSUVlypQpfn5+BQUFBw8epB7v3r370qVLRSLR7t27Kysr8UED
A4OJEyf6+PgYGRkJhcLi4uKoqKg7d+5Idtu7d+/p06c7ODioqamVlZVFRUXJEsDFxWX8+PGOjo46
OjpcLvft27eRkZEJCQn41wEDBkyePBm/rHV1dXfu3IkQevny5ZkzZxQXKSAgYNSoUfn5+adPn541
a5anp6eBgQGHw0lPTz99+jQZHUZPT2/SpEm+vr7GxsZcLvfNmzdXrlx5+fJlG68rAAAA0C6Ki4uP
HTuGy+QjQjV2wp8GMl/PysqiendgX47OEVU58JaRrF/f33EBAABIoqSiUlBQsGDBAkdHx7Nnz9bU
1JDj/v7+Li4u+fn5ZB5vb2+/YcMGS0tLhBCbzdbS0nJzc3Nzc/P29t61a5dAICBtBw0atGrVKnV1
dYQQj8dzdHR0dHSUako7ceLE+fPnM5lMPp/PZrONjIxMTEw8PDyOHj168+ZNhJCxsbGLi8s/I2Qy
cbm2trZNIpmYmLi4uBgYGOzcudPa2logENDpdD09PTMzMwcHh7Vr15JIx1ZWVhs3brS1tUUINTY2
mpiYmJqaenp6Hj58+O7du8pdYQAAAEAJSkpK8C4KFW9vb1ImZmD4T7EVsaysrLVr13asiO2DGH2d
O3du9uzZYr++v+MCAACQRElFJSEhoayszNzcfOjQoVeuXCHHcSDg+Ph4/CeDwVi1apWlpWVJScnh
w4dTUlLU1dXHjh07Z86cAQMGLFiw4LfffsM1DQ0Nly5dqq6u/vbt26NHj758+dLU1DQ4OHj06NFi
p3Z0dMRayp07d8LCwurr61ks1pdffunh4TF37tyoqCgOh3P9+vXr16+PGzdu6dKltbW1n3zyCWmu
uEgYS0vL2traAwcOREdHM5nMadOmBQcH29vbDx8+/Pbt27jOypUrbW1tCwsLDx06lJ6ebmRktGzZ
sgEDBixcuDA1NbW8vFy5iwwAAPB+QaPR9PT0dHR0tLS0tLW1NTU1GQwGk8lkMBhCoVAgEAgEgpaW
Fg6H09TU1NTUxGazuVxuR0vl5OREomNlZWURZ/rOx93dfdmyZc7OzgihzMzMI0eOpKamtqkHYvQV
GRmZmJgoqah0Ce0fFwAAgFSU91F5/vz5+PHj+/XrRxQVa2tre3t7oVB4//59fGTMmDEODg7Nzc3b
t2/Pz89HCPF4vCtXrmhra8+aNWvUqFEREREVFRUIobFjxxoaGnI4nB9++KG0tBQhVFFR8csvv2hp
aYkZ1Lq6ulZXV1dWVhKrs6qqqv379x8/flxXV9fT0zM2NlaO2IqLhOHz+T/99BM24uLxeKdPn/b2
9u7evbuzszNWVIKCgnr16sXhcH788ce3b98ihGpqanbt2nXw4EErK6vRo0eHhYUpfZERQjRE+8hv
g6O5B43WrsgHHF7jnfTTSfn329MJAACAJOrq6iYmJiwWy9DQkE6X/qZiMBgMBgMhpKWlpa+vT45z
OJzq6uqqqqra2lqRSKRy2agO9Gw2OzQ0VFZN6q4Lpri4WLUBsjZv3mxsbIzLzs7OmzdvnjZtmuLN
idFXVlbWsWPHnJycFGn17o8LAABAFsorKg8ePBg/fryzs7OhoSG2qhoyZAidTs/IyCguLsZ1/Pz8
EEJJSUlYJSBcvnx57Nix+vr6gwcPxhkY3dzcEELJyclYSyEUFBSInffKlSvUPRxMZWUlm83W19c3
NDSUL7biIpGexVxNSktLu3fvrquri/8cMGAAQiglJQVrKRiBQJCammplZYVXmJTG3WboVO8V7emB
oKWuM8lz2bi+i3649rEIqX42AADAfw0ajcZisSwtLQ0NDWk0JdMHa2lpWVlZWVlZ8Xi8srKy4uLi
5uZmVUmIQ2CRXCLHjh2Ts52ye/dusSPEF19VkNm81D9bBRt9YXVL8XQo7/64AAAAZKG8opKdnZ2T
k9OjR4+hQ4dGRESgf+2+4uLiSB38ecjOzhZry+FwSkpK9PX17ezs8BEzMzOEUF5enoJnNzMzGz58
uL29vZ6eHpPJpNFo2traCKFWP5aKiyQLPp+PEMJLgwgh7OtiZGQUEhIieSIjIyMFRyTJVO8Qd5sh
SjeXCpOhtmXyn1uuzABdBQAApaHRaN26dbO1tdXU1FRVn+rq6jY2NtbW1hUVFfn5+U1NTe3sEGsp
ZNuBGgLrfYQa6QvH76KGJ54wYYK3tzd4oWDMzMysrKxYLBaXy62oqMjNzSU+pZ3Zj6WlpYuLi4aG
RmVlZVJSEp48dDTu7u4fffSRk5NTq+u2XU5tbW1WVlZ4eDgYCgJyaFd44mfPnvXo0aNfv34RERGm
pqY9e/bkcrkPHjwgFfC2Q11dnWRb7IKPtQv0byjhhoYGRc47ZcqU2bNn4w8ktnUWiUSy7A3EUFwk
BcEdOjs7S908wbEBlMDCsLvKtRTCt5P+2BIxs4M6BwDgw8bY2Lhnz55aWlod0TmNRjMzMzM1NS0t
Lc3NzW3P3G7NmjVESzl27JiYlsJms/FEn0z38SzfyckJqwHvGmRfSE9PT9Kay8LCAld478Yliba2
9qhRo4YNG+bo6Dh27FjFG2pqamJ3UwcHB+qqZWNjY3p6+uXLl6kLqR3aj7u7+6JFi9zc3EhzNpt9
69atY8eOdai6Mm3atBUrVGOF0QkYGhr6+vr6+vru37+fasmiEvT19VksVn19fVVVlWp7xuAYS5A7
tRNol6Jy7969GTNmODs7GxgYDB06lMFgJCcn19fXkwotLS1aWlpSk1LhGTxxo2xpaUEI6ejotHpS
Pz+/+fPn02i0GzduXL9+ndiGhYWFKbJ+oLhICiIUChFC9+/ff/36teSvStswLB26Q7mGikCj0ecO
3HQ69oeOOwUAAB8eGhoaPXv2NDExkVOHz+fX1dU1NDQ0NTVxOBwej8fn8wUCAY1GYzAY6urq6urq
Wlpaurq6+vr6Ojo6UrfBaTSahYWFiYlJTk5OWVmZEqKuWbOG7D9ERkZKWjpFR0djD/thw4bhcMbv
ePReBWMAvHfjouLn5xcUFNSvXz/8jW7T9kWfPn3Wr19vbW0t+ZOOjo6vr6+Pj8+dO3dwuoIO7WfI
kCEbNmwQ0+T19PSCg4N79uy5fv36DtJV+vTp89lnn3VEzx3NihUrsrKy0tPT29/VyJEjg4KCHB0d
DQwM8BEul5uXlxcfH3/p0iWpi9SK4+joOHXq1L59+5qbm2OzGoFAUFhYmJqaev78eeL1QGXBggXY
QaCtHD58ODk5WcHKW7ZswdY9UhEKhU1NTQ0NDbm5uQkJCWlpaQp2JRKJvvvuO6njkoO1tfX//vc/
8mIvLy/ftGlTm3oQo12KSmVlZXp6uru7+5AhQ7y8vBBCjx8/plaoqqrS19fv1q2bZFt8kLit19TU
4Ki+rZ40ICCARqMlJiYeOXJECZkVF0lB6uvrDQ0NW1pabt26pYQ8UnE092qn63yr9DRz79D+AQD4
wGCxWM7Ozkym9K9Gc3NzeXl5RUVFY2OjVJ94kUjE5/P5fH5TUxMJFs9kMlksFnbEl9RY1NTUnJ2d
zczMMjMz8WKWgqxZs4aE+UIIFRcXU6NjsdnsyMjI8PBwXMfCwmL27Nmq9dnoCBITE4cPH0494u3t
TfxPiNvJezcuhJCtre3YsWMHDRokVT1QBEdHxy1btlB9YwQCQX19vYaGBrGSoNPpo0ePZjKZ27Zt
67h+jIyMVq1ahbWU9PT0u3fv1tXV9e7de/z48VpaWp6enkuXLj106JByw5TPrFmzsGlJZWVlaGio
gttHXYinp+eGDRvMzMzodPpHH330zTfftKc3Ozu7devWubq6ih3X0NDANi/jx4/fv39/dHS0cv3P
nz9/1qxZ2PyHwGAw7Ozs7OzsAgICjh8/LulBbWFh4ejoqMTppK6ny8Le3r5VtwWEkL+//7x58169
ehUeHi42XZfV1aRJkw4fPqy4JAihiRMnUuN8KLIDIZ/2ZqaPjY11d3cfOHCgk5NTfX292B2QkZHh
4ODQv3//EydOUDPEe3h4YI3t6dOn+Eh2drajo6OPj4+6ujp1EUVyhHjbhHznMCYmJgqaSisukoK8
fv3a1tYWrwCJeTdaWlq2VRPFBPX+SIlWbcXCwKGkTlGnIAAA/rPQaDQHBwcbGxupv1ZXVxcUFIi9
kxWEz+eXlZWVlZWpqalZWlpaWlpKmssaGxt7e3unp6cr7j5O1VLQvx4dhMTExMjIyJKSktDQ0DVr
1uAKw4YNw/1TP7GKn/Hd4T0aFzHxcnV1JW6fyhESEkK0i5qamvDw8Js3bzY2NiKEXFxcpk+fHhAQ
gH8dMWLE8+fPpaacVkk/wcHBeJby+vXrlStX4s2TqKiojIyMb7/9FiE0ZsyY48ePS1pb/Pjjj5mZ
mSdPnlT6IvTu3RsX9u3b9+5rKQih5OTkH3/8cc+ePYgivHI4ODj89NNPLBaLHKmtrW1oaNDU1CQ7
wMbGxps2bRKJRDExMW3t/5NPPpk3bx75k8fjVVdX0+l0Y2NjvHajq6u7YsUKPp+vEkc4oVBYVFTU
/n6k4uLismXLlr/++kuR5f4hQ4a0VVEZMkTVztXtbP/w4cO5c+diFTY2NpaawBEhFBkZGRAQYGRk
tHz58p9//hn/amlpuXTpUoRQSkrK33//jWveuXMnKCiIxWItWbKExB329fUdNWqU2BlxKkkvLy8b
Gxts92VnZ/fFF19gRUVNTU2+wIqLpCCRkZFDhw5lsVghISF79uwhb5+5c+dOmjQpLCzs6tWrbeoQ
IWSsYy550H26gYFVK6OTCq9JFPerFBtNZ4t+oKgAACAfBoPRu3dvqXGcamtrc3JyFPQtlE9LS0t+
fn5BQYGVlZWtra3Yvo2GhoaHh8erV69IKmGVEBkZmZWV9dFHHw0dOlRsHh8dHR0VFfUeGU1ReV/G
tWLFijFjxogd5HA4ampqsjbupBIYGNinTx9crqmpWbVqFTWq56tXr7Zu3VpcXDxnzhx8ZO7cuVIV
FZX007dvX1y4cOEC1cQrKipq+vTprq6uOjo6/fv3F1vVnT59ev/+/fv3729ubt6qcZosiPU7DlX6
yXF75frpNMIWvSFu9O10/f/f//5HtJTk5ORTp06Rni0tLT/66KMxY8bQ6XQmk7ly5cqUlBSqk0Kr
ODo6fvzxx7jM4/HOnz9/6dIlvDRjbm4+c+bMiRMn4vDrixcvfvr0KdUr5o8//iAZO1pl2bJl9vb2
eAg5OTmKS0hoaGjABp9UaDSavr6+g4ODl5cXvs4MBmPmzJlcLvfEiRPyO+zWrVtgYKDiQxgxYoS5
uZQZbHtor6LS3NyckpIyePBghJDkhlpRUdHvv/++dOnSYcOGubi4ZGdna2ho9O7dW1tbu7y8nHo1
c3Jyrly5Mn369JEjR3p4eBQVFenr63fv3l1y1SEyMrJfv35GRkZ79uzJz89nMpl2dnY0Go3L5Wpo
aBCrRFkoLpKC5OXlhYWFLVy40M/P78iRI9iM2N7evlu3bhwORywIsoKoMaXsDhlYqSWcrlGiN5+5
Rt0H6+Q+bhQ7rqupfEQyAAD+CzCZzD59+lDTnmC4XG5OTk6rhrIMBsPMzExPT09bW5tGozU2NnI4
nPLyclmugEKhsKCgoLS0tEePHmJfOzqd3rt376ysLLEQ9lIRM5GSQ1ZWFs6yQtzTlc4x0vlJDyWN
wQjvxbioxn4CgSAjIyMmJubOnTu///47dWm8VQIDA0k5LCxM6mf3+PHj/fv3x0Y41tbWPj4+CQkJ
HdEPCfUp6QlQUFCAV3XFjM/Nzc2x8sPj8XAM1XYitmT8LoO9fNtJcHCwg4MDLj969Gjz5s3UX4uL
i3fv3s1ms2fNmoUQMjIymjp1apt2rubOnUt2evft23fz5k3yU1lZ2f79+2tqahYuXIgQMjAw+Pjj
j/fv308q5Obm5ubmKnIWLy8vrKUghJS+DVpaWq5duybrVx0dneXLl48bNw7/OXv27MePH7e6Oj9q
1CjFFZWRI0cqWFNx2quoIIRiYmIGDx5cVlYm+dgjhG7fvl1fXz979mx7e3v84WlpaXn69Onx48fF
UraHhYXx+fwJEyaYmZmZmZkJhcKUlJQnT56IhbDIyMgIDQ1dsGCBhYUFXisqLS0NDw8fOXKkm5ub
IraAioukIFevXq2qqpo5c6a9vT3O0yIUCtPT00+cOKHaFMhN1Uq+fTrY4QUAgA8TJycnSS2lsrLy
9evXshyCzc3NfXx83N3dXVxcLCwspJr0lJWVZWZmpqSkJCQkFBYWiv3a0tKSmZlZWVnZq1cv6so6
jUZzcnISCARt9SRUhPZvMrybSQ/f/XHl5+fHxsbevHlTMm2aIqirq1O3QeQY3ty5c4fMEIYNGyY2
Y1FVP/iOFYlEkkEgSMRtMUv15cuX4zXWq1evZmZmyjqvymHQ1AQiRV2/1OlaCCGekNNqzc5n0KBB
uMDhcKhKApXTp0+PGzcOO354enoqrqhoamoSbT81NZWqpVA7DwwMxK4dfn5+smSQz/Tp03EhJyfn
0aNHSvTQKo2Njbt372YwGKNHj0YIqampzZ49+/vvv5daWSAQ4Le3p6entbW15ItaEmtra5ynBCHE
5/PbtC8qBxX0EhcXN3HiRDkVnj59+vTpUxwgv6mpKS8vT9amW3h4+OXLl3v37q2mppabm4vVBsmt
1bi4uLi4OCcnJ1NT06qqKvxgR0VFiVW7fv369evXlRbpzz///PPPPyXb7t69WzJ/1pMnT548eWJt
bW1jY9PS0vLmzRvVmihQsfPVthvwj1efUICeHKyElCgAAKgcGo0mFuBLJBLl5eVJnVCqq6sHBQWN
GjWKzPbkYG5ubm5ujqNyZWVl3b1798aNG2KJUyorKxsaGlxdXUl2XSxSz549O0JRaT8fatLDjhvX
s2fPbt++nZKS0p5O+vTpQ+6QV69eyQmo9fjx488++wxv4/To0aOD+sFbBDQaTVNTU8wkhMzbqDse
/v7+2Ka/sLDw+PHjckaqchg0Zl/D8dnsJ2x+60u0LvojzLQc75XuE4lUsAcilYcPHyq3ZWdra4sL
WVlZsqZeeKaHDfPkBMiSZPDgwSSOguQ8k/DkyROsqFhYWLi6urY1glmPHj18fX1x+caNG21q21aO
Hj06ePBgfLcTS0VJ0tLS3N3dEUJMJnPixIm//PJLqz1PnDiR3OQvXrzAQbbaj2rUHUUoKChQZL2E
w+EouAKUlZXVzv0KBUVSnMLCQkWUzvbAYNLsBminXqitK+YjhAYtZ/WZZvDiYrsi7gEAAEgiEol4
PB6JciMSiV69eiWpJGhoaEydOnXGjBnKWZk7OTk5OTnNmzfvypUr586do6or2LTYzc2N2jPO8Cs1
sBjwfiFn2qc4xOYHISTf1rq0tLS6uhoblZGkNCrvh7hs9erVS2zCjRNbI0omN01NzSVLlmCd59df
f1U6n4Fy8ISc1/VR462/KWhMTay+xBOK24cTGDQ1F4NALYaBH+vjp5WnO04k5bbsnj17hk2zXr16
Jaca+ddIjUO1atWqwMDAlpaWixcvnjlzhhyn2unICbaUlJT00Uf/hEHq1atXWxWVmTNn4u2LyspK
JRyb20RtbW1mZqaPjw9CiMVisVgsqalmcDVs8zlkyBBFFBXiRv/q1as2eQHJB0yC3jNcJ+m3cERY
S0EIJf9Ra2itjIc9AABAq2RlZeHVXx6P9+LFC0ktZcCAASdOnFiyZEk7fWF1dXXnzJkTFhYmFkBF
IBC8ePGCukpaUVEBWgpAoEY0bjXMJrmRDAwMiDOJavvJzs7GBbHQc5aWlmT1mmwiLVy4EJ83Ojpa
iVBU7adJUHO3ZF933QHBtj+5Goyi06THXuupO1CLYYAQctYP6GPYhhScSqDElt3OnTu3bt26devW
v/76S041ktlGUiF0c3ObOHGijo6OoaHhvHnzqN7OZPulvr5eTk4nqqeHIpGCqZibm2NPb4TQ3bt3
OzQlKAbnN8dITdeBEFJTU7t37x6RcMSIEfL7DAoKIo6Fd+/eVZXdFwJF5b2DRv8/qQbgew0AQMdR
XV399OnThISEZ8+eiQUg1tTUXLt27fbt2yUXlcV6yMrKSk5OTk5OzsrKku8HyGKxNmzY8P3331Md
Y0QiUUZGRm5ubkVFRV5enmod/4D3HerqeKthl6n7dWITYlX1ExkZiXX74cOHL168GHfr7u6+detW
bEGUlJSETTmcnZ0nTZqEEKqrq2trBFgVUsMrfFB2gElX92XNmmqz3U5H3FyHRqO7Gv7/5QMf4+Du
un6dK6MK0NHR6dmzJy5LBtSivnCYTCax9UKU6Ajyk0XW19eT26bVqE5iBAcHYyWKw+FcvHixTW2V
gxogl5qoQ6zOzZs3ycZIq17ypEJtbe3NmzdbjcGrOJ1n+gWohPSIuoHLWXrmTHYZHyHkOdOQXdrh
yjcAAP9ZBAIBziNBxcTEZMeOHeTDL0ZeXl50dHRycnJ2draY5wn6N729u7v74MGDXVxcJJv7+/v3
7Nlz06ZNJFqOSCRSrZku8MFAdUyXNeUiULO0ic0mVdVPenr6X3/9hS15Pv744xkzZrS0tJCJb21t
Lcn2+Pnnn2ODpTNnzshZqu8ESjivHpX/NtRsqR7TLMA8pIKb96zydAX3n+wFttoeBmr/ZzHC32wx
R1BXwpFnZ/WusXz5cpJCUdJ7OT4+npg5RUdHU+PjkRtDVqxCArkrFEzrh9HR0SGbFTExMVKtsFQO
2SYSCoWy9g/V1NSampqePHmCY4jLd6m3sbHx8PDA5cePHzc3N4Oi8oEjEokkkzRj+DxRYRLHc9Y/
VhZCAUr5U0qeNRod9Ryma2ijpqYJm2YAAKgSCwuLn3/+2dTUVOw4n8+/f//+hQsX5GcA4HK56enp
6enp4eHhVlZW06ZNGzNmjNin3cLCYt++fevXr+/MIEjA+wg1U3irYXmpRjXUVXMV9oMQOnLkCIfD
mTlzppaWlpqaGpmx5eTk7N69G6vf06ZNc3NzQwilpaXJN1jqHHIb4nSYxj7GwQghUw2H8Vabcxvi
EqouNAqq3QzFc93QESPAPORG8fYaXsc65aoECwuLRYsWkdjT9+7dk3SO4vP5ISEhrq6uXC5X7J1D
boxWLbJaWv4JoUZszBRh+vTpWNcVCASds53i5uZGgkC8efNGlmcUvm+vXr06evRoGo0m36V+woQJ
2NZLKBRiHxsVmn6BovIuIktLweQ+asx70shQowkFSMgXt/2yG6Bj108L/dsBu1ygp9mujL8AAABU
FixYIKmlxMbG/vLLL23NplxUVLR///5z584tW7aM5PzG6OnpffXVVwsWLGivuMAHjfzPpRzo9P+z
iqeqfjCnTp26detWQECAg4ODurp6XV1dcnIymR+bmZnNnTsXIcTj8RTxUe4cXtbe0GWynPX/eQy7
6/rZ6Xi9aUgw05CycapO1xppsfpa4dYmgTLp3TqUmTNn4nw1ampqLBbL3t6e6IqPHj3atm2b1FZ8
Pl9qtDGp/1/5KN6EyWTiSMEIoaSkpLYmHFcCMzOztWvXkqjxcXFxsmrii5aZmZmeno6Vajku9TiE
I0IoLS0NjwJ2VP7riISIzxVXUTQNGL7zjRBC7HJByh81xH1lyJcmCAAAQEWIxSzmcDgHDx5sT0jN
ioqKrVu3PnjwYP369VRjcTs7OwaD8S5kr+v8ZI6dw4c6rneBsrKyc+fOSf2JmjhFfqCqTiau6qw2
08hW+59UGAyaeg+9gbIqazOMRlqsvlG8/V1LruLq6urv7y92sKmp6eDBg1KzoHQh48aNI77sly9f
7tBz2draBgQEjB8/nmRTLS8vDw8Pl1WfaBp3797Figp2qSce9oSgoCAS0Y4kFIEdFUCcHkN1rDy0
uGzhs9+ru1oWAAA+ZGJiYkhWr6qqqq+//lqqg7uWllbv3r0dHBzMzMy0tLT4fH5dXV1hYWFmZqZU
Q+cnT54sW7Zsx44dJGZOSkrKu6CloHc1mWP7+VDH9S4zePBgvPxcVFTUyYlTWkUkEkaVHR5judFU
w6H12ggZqVsHmIfcKQ0Vit6J51QO2traCxYs0NLSunTpUlfL8v+ZMMk5wwAAACAASURBVGECLvz9
999yYh8rjoGBwfnz58UO0ul0TU1NakIqhFBDQ8P27dsl/Q8JRNO4devW/PnzcVCBUaNGSSoqxI2+
qqrq9u3bYs3bDygqHwKuE/VZDupFSZycRzLvOQAAAJUQERHB5/OHDBlSVFR09uxZyQxrfn5+kydP
9vHxkZqWHiFUUlJy//79iIgIsbYlJSVffPHF8uXL+/btm5OTc+DAgY4aQxuBZI6ASlBXV1+6dCk2
Mzt27BhxD7Czs+vfv7+JiQmPx3v79u3jx48lo1B0DgJRy73SveOtNukxzRSpb6Hl4m+6OLr8aEcL
pjiRkZFJSUkIIXV1dRMTE0dHxz59+jAYDFNT05CQEAcHh9DQ0K6WESGEhg4dSnxFVJXkkU6nk80N
OWRlZe3du1e+ByDRNHg83qNHj3Bidw8PDzGXeqobfUxMDPHkAdMv4P9j46PNclDPe9JUkNA17zUA
AP5TiESiyMjIyMhIyZ+8vLwWL14sNZYXFQsLizlz5syaNevSpUunTp2izsnq6+t37typYokBQAJV
ZatoUz+LFy8WS5xiYGCwatWqwYMHU7X6mpqas2fPdo5rtSTNAvbt4tDxVps0GXpSK/zNjumhN4iO
/hG4u65fA78qsbrrQwJg4uPjxY44OzuvX78e5/QcP358Xl5eh+6rKLgPPGXKFFwoLy+X+jpVLSKR
qKysLDs7+/79+4rkWqVqGhEREePGjWMwGJIu9SQbvUAgoKaqhB0V4B+Y6jSHQdrsMj5oKQAAdCFM
JvPzzz+fPHlym5rMmDHD39//+++/h+hegHJQIwW3uohL9XIW27JQVT9ykEycoqOjs3v3bskw30ZG
RitWrDA0NOwq2zA2v/xe6d4xlhsYNHWxnwqbUh9XnEitue7DCrbX8cEH+xqOa+RXZdY/7HRJFSIz
M/Prr78+fPgwzksbHBysuKJCohK3OvMmqmargYwRQu7u7u7u7riswiSPdXV13377rdhBgUBQX19f
WVnZpm06quacm5v78uVLvHMi5lJPstGnpqa+efOGHFciCIEsIHbt+43PJ0YIoeQ/pEQoBgAA6ByY
TOauXbvapKUQcLDj/v37q1wq4L8Ade7Vav4KagUx63xV9SOHzz77DCdOOXv2LE6c8vnnn2Mtpaqq
as+ePVOmTFm0aBFZlp49ezaZy3Y+Fdy8qLLDIiQUO/6y9iZCiM0vf1h2KLLoe5Juxc9kjq22R2dL
qTClpaX379/H5W7duhEvu1YhSXXw/04OimdcQQgFBwfjQlNTkwrjUwuFwlQJ0tLS3r59205jQuIl
b25uHhQUhMsjR44klmbEO0XlgKLyHqOpz1DXoadfbyWHLgAAQIfi7+8v9cNfXl5++/btkydP7tu3
7+effz537lxqaqqkXYS6uvq6deuUjg8L/JehTr/werkcqAkuxPyjVNWPLKZOndqnTx+EUHp6+oUL
FxBC2traw4YNQwiJRKKffvrp2rVrtbW1ubm5e/fuxf7KDAZDOeVfVbxtSomrPEM9Us7NLm1+Tf6s
4OZFFn0fXX60UVBFQ/Rh5ssV9MLvEqgB1rAZmCIomG9eU1OTmtZTfp8ODg5kaSYmJqbV+u8Cd+/e
raiowGXiPU8KZWVlRJNROWD69R7jGKiLEKrKbl13BwAA6DjEAhYjhFJSUsLCwlJSUkQi8UDqhoaG
kydPnjFjBnW2x2KxNDQ0ZKUeAwBZUFP3kEivsiD5f2pra2tq/k8CEFX1IxVq4hSSmd7b2xs/AllZ
Wc+ePaPW/+OPP3C2ckdHx1Y771Ay6x/qMFl9DcfhP9Nrpaya5zbE5TcmuhmM7ms0bkS3VZFFP7D5
5Z0moYWFxcCB/8RQfvnypdQIhBjq3pfirt7kxjAwMGCxWLIyxzs6OhJbqYKCAvl9zpgxg/h1YK31
3YfP58fExOCogB4eHjY2NjQajbjRR0dHd9ypu1JR6d+/f1NT08uXL1Xes7e3N7bSw2EKPhi0jf5P
CB0jW7XmeqHYQamIxDdvAQAAVMaTJ08WL16MTSMEAsHBgwcjIiIkVRRMbW3tyZMnb926tWXLll69
euGDycnJXaKlUBOJoA8ol8iHOi5JsrOzSdne3l5OTTMzMxLWrLS0tIP6kcqyZcvwLs21a9fIuj5J
ZyHZSU5ODpfL1dDQoKYV6ioSq//SZbK66/qx+eX5TUlS6whELam117LYMd7GU0dZroks+qFZoKSt
h4I7VAQWi7VixQpcPnv2rBxFBQfYxSi+iZGTk0PKAwYMkOX1Tt1SpjaRxMTEhKRHTEhIyM3NVVCS
Lufq1auTJk1iMpnYpR7968fC5/MjIiI67rxdpqj4+/uvW7dOKBSuW7euE5Jxvl+08JvVmOI2snVF
fOyRQkVTny55UAxekyj3sRQj2obmdy6hLAAA7yPFxcWrV6+eNGmSurr6uXPnXr9+3WqT0tLSlStX
zps3z83N7c2bN7/99lsnyCkJNZEI+oByiXyo45IkLS2tqakJW904OzszmUxZfsmDBw8m5oWSU0lV
9SPJoEGDsIlXcXEx9T4nC/BUP34Cj8fT0NBQYYzX9vCo4jcthkFewzOR3FVPjqDuccUJY3VbN4Mx
yTWXBaKWtp6ourr6p59+alOTgoICPp+PNyjkxxvs27cvKSsevSM2NpbH4+FVmEGDBslSVPr164cL
VVVVODiyLKibyR2d5FG1vH37NiUlxcfHB1F86BFCiYmJxcXFHXfezlBUFi1a5O7unpqaSo1fwePx
RCKRQCBoaWnzrdyhSJW2k6luLDM3sBM7mPqXiq0YM0ufq7ZDAAD+s6Snp6enp7epSXNz89GjXZx+
QTJzyIeRS+RDHZckPB4vNTV1wIABCCEDA4PJkyfLck3GxlSYx48fd1A/Yqirqy9btgwrNkePHqVu
GxL9RKqXtoaGBlI40G1HIxQJHpQdEIgUikxVzXtbXf1Wna7VVkVl+PDhSshWV1eXmZmJU6d7eHj4
+/s/evRIspqDgwNJV5+Xl5efn69g/7W1tS9evMCz8379+vn6+kqGPx42bBgWACGUnJwspzdtbW3i
if769Wsxk793n1u3buFLQc3WcuvWrQ49aWc405uZmdnb24vloHn27Nnq1au//PJLajizdwGp0nYy
9zLCO+EsJbV5nXAWAAD+y5iYmGzevPnChQsXLlzYvHmzpDcLALSTBw8ekPLs2bNtbGwk60ybNo0s
txcXF8fFxXVcP1QWLVqEE6fExMTgxCkE4ppsYWEh1srJyQlrL3V1dfL77zR4Qk6bFA+ekNNxwohB
3DzodPr69eslbf69vb1/+OEHHR0dsfpUVq1aFRkZefny5Tlz5oj9dP78eaFQiBBiMBhfffUV1mYJ
Q4YMWblyJS7zeLw//vhDjqhTp04loRo6IXeKyrl//76YpWJxcbEiWVnaQ1f6qCiyZ/rfJKssSSQS
0mgdqEZml3+AxsoAALxT2NjYHDp0SE/vn7Rxw4cP9/Hx+eKLL9619SngvebevXuTJk3CS9rGxsa7
du06evQomTzp6+vPnDmTRINFCMmaSqqqHyrdu3dHCNXX1+PEKVSSkpIaGxt1dHScnJwGDBjw9OlT
8tOMGTNwQY7HhRyoGTDecfDGUTuJiYm5evUq1k90dXVXrVo1e/bsnJwcNputpaVlbW1NEsAjhO7d
u3fz5k2xHtzc3Ih6M2/evGvXrlFVxISEhDt37owePRohZGxsvH379qysLJyd3cbGhhrwICIiQv7M
duzYsbhQWlr6PioqCKGoqKhZs2aRPx8+7PDkOe1VVPT09CZNmuTr62tsbMzlct+8eXPlyhXiH795
82YdHR28WuDi4rJz586WlpZNmzYhhJycnBYtWoQQ+uqrr6gdBgQEjBgxwtLSUl1dva6uLiMj48KF
C2IKnIuLy/jx4x0dHXV0dLhc7tu3byMjIxMSElqVVn5DOdJ2Pseiv1467McO6lwkEp6O/aGDOgcA
AMAsWrSIaCkYPT29hQsXbt68uatEAj5Ijhw5sn37dux63q1bt2+//XbFihUVFRXq6uoWFhbU+HJx
cXHXrl3r6H4I69atmzFjBo/Hk/SY5/F4WDVCCK1fv/706dNxcXH6+vrjxo0LDAxECAkEgjYlp6+u
rsYGfu7u7o8ePQpb9Ebxtl0FSRRTXV3dnn727t3L4/GmTJmClbRu3bpJhm4TiUQ3btzYt2+fZHNq
0AImk6mtrS22l7Vz504dHR1iPObk5OTk5CTWya1bt6iZECWZMGEC2T3ruGC+Hc3Vq1enTp2Kd/x4
PB41G30H0S5FxcrKauPGjba2tgihxsZGExMTU1NTT0/Pw4cP3717FyHk5ORE/v2GhoaGhobEI0VP
T0/S7WnZsmVY3eTxeDwez8rKysrKytfXd/v27SRQxsSJE+fPn48d3dhstpGRkYmJiYeHx9GjRyW1
ZCqtNpQjbedTXJvzovBxX+vBHdH5d1dntV4JAACgfWBrZkUOAkB7SE9P37Zt24YNG0hkJxaLRcJq
EZ4/f/7dd991Qj9U/vzzT1k/HTlyxMnJycXFxdDQMCQkJCQkhPrr6dOn09LSFDwLQig1NRW7eaxe
vZpOp8fHx5Nkhe8gGhoaPj4+xGiq/SHpDh06FBcXN336dE9PT7GNmpaWlpcvX168eDE2NlZq2/j4
+MzMTBwlLzo6uqSkRLLO5s2bx40bN23aNLEcLEKhMCcn588//8TZb+QwYcIEXGhoaLh06ZLiQ3un
KCkpSUpK8vPzQwjFx8eXl3d4KOp2KSorV660tbUtLCw8dOhQenq6kZHRsmXLBgwYsHDhwtTU1PLy
cmzqt3HjRrytuWPHDjm9eXp6Yi3l7Nmzf/31l0Ag8PT0XLFihamp6eLFi9esWYMQcnR0xMrGnTt3
wsLC6uvrWSzWl19+6eHhMXfu3KioKFmPpSIN2yRtJ3Ax4eecstQp3p+rsE+BoGXrtY9FSHrYUAAA
AAB4H4mPj//0008XLVrk5+dHDUSLycvLi4iIUCSIqqr6UYTm5uZ169aFhIQEBARQA3xVVVWdOXPm
ypUrbert6NGjfn5+WlpahoaGW7ZsUYmEnUNjY6NK4mokJiYmJiZqamp6eXmZm5vr6Og0NTVVVlYm
JiZSk6hIwufzQ0JCXF1duVyunIBg169fv379up2dXa9evYyMjEQiUU1NzatXr7AZWKssWbKkzUNS
jPnz53dmVxs3bmy1zsyZM1UgDUKoPYpKUFBQr169OBzOjz/++PbtW4RQTU3Nrl27Dh48aGVlNXr0
6LCwsDZ1iCPHFRYWnj9/Hh9JTk4+e/bsypUrHR0d9fT02Gy2q6trdXV1ZWXlwYMHcZ2qqqr9+/cf
P35cV1fX09NTlrqsdMOuJaUgKrUw+uP+G3uau7fTZaWZ13gn43Tim/uqkg0AAEA+SUlJxFiCoIiZ
LvBfZvr06co1rKqq2rVrF0LI19fX0tLSwMCgpaUFTyXb5Balqn4UobGx8ccffzxx4sSAAQNMTEwE
AkFeXl5cXJwSaYXKysp27NixceNGqonauw+Hw9m5c2dZWZmqOmxublZiRsfn8xXc1cnPz1c8aBjQ
fpRXVHDcg5SUFKylYAQCQWpqqpWVFckzpTgNDQ0IIWNjY3t7e/IuiI6OfvHiBUKIzWYjhK5cuSK5
xlBZWclms/X19UksBUmUbtjliESiM3Hbu1oKAACANvP77797eHhQ3VTYbPbvv//ehSKJUVlZKRaI
TGq+ObFqHVpHJXyo41IQyQCyXdtPq5SVlbV1/0Qqjx49ys7OxttBJMjVOwubzY6Liztx4oRUUysA
wCivqFhaWiKEjIyMxKwqsauQ5IZpqzx48GDcuHEmJia7d+9++fJlWlra8+fP3759K/nKMzMzGz58
uL29vZ6eHpPJpNFoOEkTycEkC6UbAgAAAG3lzZs3CxcuXLFiRZ8+fRBCL1++PHjwYJfPYqn89NNP
X331FckxIivfHLVaR9dRCR/quIBWKSkp+eEHCJYDfDgor6jo6uoihJydnaVunkhNYCSfmpqazZs3
z5s3z/tf5s2bl5ube/36deyaj5kyZcrs2bM1NTURQhwOp6mpSSQS0emtm0Up3RAAAABQjsrKynfZ
XD4+Pl6RfO2KVFNVHZXwoY4LAID/GsorKjj9zf3791+/fi35qxLmlQihwsLCbdu2mZiY+Pr6urm5
9e7du3v37iEhIba2tjhPvJ+f3/z582k02o0bN65fv15QUIAbhoWFyTffUrohAAAAAAAAAACdj/KK
Sn19PQ7ge+vWLRUKhBCqrKy8cePGjRs31NXVFy9ePHr06HHjxkVERFRWVgYEBNBotMTExCNHjrSp
T6UbAgAAAAAAAADQ+Shv+IQ3Uvr16yeWzwv9675CEIkUCob7888/h4eHU9O+8ni8s2fPIoSYTKa1
tTVCCO9+1NbWUhuamJhggy45KN5QQWkBAAAAAAAAAOg4lFdUIiMjeTwei8UKCQmhTvfnzp27f//+
iRMnkiM4nFerFlbFxcW6urqjRo2ysrIiB4cNG4YQEggEOEw19sL08vKysbHBFezs7DZu3IgFoIYh
F0PxhgpKCwAAAAAAAABAx6G86VdeXl5YWNjChQv9/PyOHDmSlZWFELK3t+/WrRuHw6EGmc7Kyho5
cqSLi0toaGhLS8uWLVukerCcO3fOxcXFzMxs7969r169ampqMjMzc3R0RAg9fPgQaxqRkZH9+vUz
MjLas2dPfn4+k8m0s7Oj0WhcLldDQ8PAwECWtIo3VFBaAAAAAAAAAAA6DkZ7Gr9+/bqgoMDa2trC
wsLa2tra2lpbWzsjI2PPnj0ZGRmkWk5OjoODg7W1NYvFMjU1/euvv/h8vqWlJd4tOXfuHK5WV1eX
lJRkZmbWrVs3a2trW1tbFotVX19/7dq1Y8eO4ToVFRUFBQU9e/Y0NDRksVhGRkbl5eW//vqrkZGR
mZkZn89/8OABQkiycwUbypK2PVcJAAAAAAAAAIC2opr8IdbW1jY2Ni0tLW/evJEVI9/Ozq5bt25F
RUXYiEsO+vr63bt319HRqa6ufvXqldQ6Tk5OpqamVVVVmZmZbRJVwYaKSwsAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAANDR0EQiUSefEp9RKBQKBAIej9fc3Mzlcq2srDpZDAAAAAAA
AAAAJCkqKtLQ0NDU1FRXV2cwGHQ6HSFEo9E6WQx6J58PAAAAAAAAAACgVUBRAQAAAAAAAADgnQMU
FQAAAAAAAAAA3jlAUQEAAAAAAAAA4J0DFBUAAAAAAAAAAN45QFEBAAAAAAAAAOCdAxQVAAAAAAAA
AADeOUBRAQAAAAAAAADgnQMUFQAAAAAAAAAA3jlAUQEAAAAAAAAA4J2D2dUCAAAAqB6RSJSeno7L
ZmZmZmZmXSsPAKiKkpKSqqoqhBCDwXBxcelqcT5wGhoa3rx5g8sODg46Ojqq6lkgELx69QqXLS0t
jY2NVdUzpuMkf494+fLlnTt3Xrx4UVVVRafTLSws1q5d6+jo2NVyAW0AFBUAAD5A+Hz+qlWrcPnT
Tz+dMWNG18oDAKri+vXr58+fRwjp6eldunSpq8X5wMnJyVm7di0u//zzz71791ZVzxwOh7yjVq5c
OW7cOFX1jOk4yd8L+Hz+/v37b968ST2Ym5vL5XK7SiRAOcD0S5wtW7YEBQUFBQW1OrMpKysL+pfs
7Gw5NXk83pgxY3DNvXv3qlRe4D0mLy9v6dKlkydP/uWXX0QiUVeLAwAfAvBYAW0lOjp61qxZM2fO
vH//flfL0jaUlvz9HbKCHDt2TExLwfw3d5bea0BREadPnz64UFNTU1JSIqdmcnIyKaekpMipmZOT
w+fzxfoHgNOnT+fm5jY2Nl6+fDkjI6OrxQGADwF4rIA2IRKJ9uzZU1VVVV1dHRoaSj7W7z5KS/7+
DllBCgoKLl++jMs6OjqrVq06c+ZMZGRkeHi4jY1N18oGtBVQVMShbo9mZmbKqfn8+XNSTkhIkFPz
9evXpAwmxf8Rnj17RjbccnNzpdYRCASkLBQKO0s0APiQea8fq4aGBvLeuHr1aleL859AJBKRe0Yk
Er1H94zSkrfa8LfffsM34aRJk1QlbWcSExNDyt98883YsWPNzc01NDRMTU2ZTHB5eM8ARUWcnj17
qqmp4TJxdJOEz+dTlZPU1NTm5mZZlYlTr7GxsaWlpYokBd57Pv74Y0tLSyaTOXr0aDc3t64WBwA+
BOCxAtoEnU4PCQnR1dXV0dH5/PPP1dXVu1oiRVFa8vd3yApCVpltbGz69evXtcIA7QQ0S3HU1NT6
9OmTlJSEEEpNTZVVLTMzs6mpifzJ5/PT0tJ8fHykVn7x4gUueHh40Gg0lcoLvMc4OTmdOnVKJBLB
XQEAqgIeK6CtjBo1atSoUV0thTIoLfn7O2RFqK2txQVbW9uulQRoP7CjIoW+ffviQl5eXkNDg9Q6
iYmJuKCrq4sLWLeRpKysrLq6GpfBQQWQBKZTAKBy4LECgP8sPB4PF7S0tLpWEqD9gKIiBVdXV1wQ
iURZWVlS6zx79gwXSEhBckQMqqPLfy0+IAAAAAAAAAAoB5h+ScHJyYlGo+G4lq9evfLy8hKrUF1d
/ffff+PyqFGjLl68yOfz3759W1FRYWpqKlaZOLro6OjY29tLPaNIJEpISHj48GFaWlplZaWmpqap
qam7u7u/v387N2EaGhpiY2OfPXuWl5dXWVkpEomMjIx69erl5+c3ePBgDQ0Nqa0+++wzPMCpU6cu
X768sLAwIiLi+fPnZWVlfD4/PDxccpjV1dV3797FJ+JyucbGxnZ2dr6+voGBgWTTSTmqq6vv37+f
kJCQl5fHZrO1tbUtLS09PT2DgoJaDd+BL+yjR4/S0tIqKipoNJqJiUmPHj3kD7+hoWHKlCm4vHfv
Xjc3t5aWlpiYmJiYmJycnOrqal1dXQcHh4EDB44ePZraCbUhlaVLl5JyZGQkaXLmzJlTp07h8t27
d6lNnj17tmnTJly+ffs2nU6vra198ODB48ePi4qK2Gy2kZGRs7NzQEDAwIEDpS4ef/TRRxUVFQih
KVOmfPbZZ1JHmpubS2Tbvn27LFte5S5jcXHxvHnzcHnz5s3+/v5Sq129evXAgQO4HBERoa2tLVmH
w+FER0fHx8dnZWXV1tYyGAxjY2NnZ+eBAwcOGDBAcedIkUj0ySeflJaWIoSMjY3PnTtHp0tfrKFK
tWPHDllWnVQWLVr09u1b9G/aFi6XGx0dHRsbm52dXV1draenZ2lp6e/vHxgYaGBgQFoVFBTcvXs3
OTm5tLSUw+EYGho6OzsPHTp00KBBsmQj4FM8fvz49evX9fX1+vr6FhYW3t7eAQEBVlZW8tsq92Yg
VFZW3rt3LykpKT8/v76+XktLy9zcvE+fPkOHDiULPWKEhobeunULIWRra3v8+HFZPU+aNAlb1c6e
PXvhwoVUgcnDtWXLlkGDBqWkpFy7du3Vq1eVlZWWlpYnT57Ev8p5rH777TecgcTLy2vnzp0Iofz8
/Pv37z9//ry0tJTP5+MX79ixY1tNCVdTU3P37t3Y2NiioiIOh8NisVxcXIYNG9a/f38ajfbVV1/h
PfZly5ZNmzZNfleI8sqlcuDAAXIT7ty5U/JLRMjPz7937x55RSs+io779GA3zmfPnmVkZFRWVnI4
HH19/e7du3t5eQUGBhoZGVErCwSC2bNn19TUIITGjBmzevVqWd0+efJky5YtuHzgwAFnZ2exCiUl
JbGxsfHx8cXFxVVVVdh/2tXVdciQIXJMr9euXYstvfv167d9+3YlxqvcecXAN1VcXFxRUVFjYyOL
xerVq9fw4cP9/PxULrlkQ+pHh9DU1BQUFITLrq6u+/btKy0tnTt3Lj4SGBi4YcMGWafYunUrdmpn
MpkXLlxo60ygqqrqwYMHz58/x7Yt+vr65ubm3t7e/v7+3bt3l6xfXV09c+ZMsYP37t27d+8e+fPy
5cvtnJAAnQ8oKlLQ1tZ2dnbGCsbLly8lKxDfFVtbWxsbGy8vr/j4eIRQSkoKeaQJaWlpuODh4SF1
5lFYWLh7927icI8QamlpYbPZubm5ly9f9vX1Xb9+PXVmoyAikejq1asnT54Us14rKSkpKSmJiorq
1q3b119/LT8KGZ/Pf/LkyY4dO+TkSBKJRJcuXTpx4gS1TllZWVlZWXx8/MmTJ0NCQgICAtoqP0JI
KBReuHDh1KlTLS0t5GB9fX19fX1mZuYff/wxceLETz/9VNakKjc3d/fu3WKf/4KCgoKCgqioKDMz
s88//3zgwIHyZeByudnZ2Tt37iQpfhFCNTU1NTU1SUlJly9f3r59e0cHSODxeHFxcT///DP1X1le
Xl5eXh4TE+Pn5/f111933Aa3Si5je4iPjw8NDSX2k5impqbCwsJ79+7Z2NisX79ecr4iFRqNNnLk
yLCwMIRQdXV1RkaGLGfr2NhYXNDX1/fw8GiTwDweLy0tbefOnVgjwlRXV1dXV6elpZ0/f/67775z
dnbm8/mnT58+d+4cNdcHfnCio6Pd3d3/97//yXnwnz9/vm/fvvLycrFTpKennz17dvr06QsXLpT6
wmnnm0EkEl24cOHEiRPUkKZsNpvNZmdnZ1++fLl///6rV69WeZptKnw+//fffz937pzSPXC5XKFQ
ePLkyT/++IN6/fGNHRkZ+cknn5DZmCQxMTF79+6lXsDi4uLi4uL79++7u7t//fXX9fX1SsvWJtoz
ig769CCEEhMTf/nlF6y3E6qqqqqqqp4/f37q1KnPP/989OjR5CcGgxEYGPjXX38hhB49ehQSEkJC
2ojx+PFjXLCwsOjVqxf1p4aGhrCwsCtXrlAvRUtLS0NDQ15e1cszxwAAIABJREFUXmRkpJeX1/r1
61kslhIjkoOqzhsVFSX2ksc31cOHD728vL766qsOfaYUp1u3bn369MFTo8ePH3O5XKmfYC6XS8xM
Bg4c2Cb1gM/nnz9//uzZs9RPP36/vXr16syZMyNHjly+fDmoHP8RwPRLOu7u7riQnp5ODXaJIYGJ
8fyMrENLBinmcDjEeEzqAlV6evrnn39OPhU0Gs3Y2JiakCg+Pn7VqlV1dXVtkl8oFO7du/fgwYPk
rcdkMi0tLc3MzEid0tLS9evXSy7jUcnIyNi2bZscLYXP5//4449HjhwhdbS0tIyNjRkMBv6zoaFh
x44dERERbZIfISQQCHbs2PHbb7+RVxW+OOSdKBKJIiIiNm7cKFW8xMTEL774gjo6HR0dfX198md5
efm333578eJF+WKkpKSsXbuWqqVQKSoq+vbbb4kADAbD71+oH9E+ffqQ460uk0ty6dKlbdu2yXKX
iouLO3LkSFv7VBBVXUalefjw4aZNm6haip6eHvX7VFBQQJYGFWHYsGGk/OTJE6l12Gw2cTkLDAxs
azjLZ8+erV+/nqqlUKmurv7mm2+qq6t//PHH8PBwWRkJU1NTd+zYIevXiIiIr7/+mmgpTCaTxWKR
R0MgEJw/f3779u2Szdv/Zjh48OCvv/5KtBT8VGpqalKHv2rVqsrKSqnNVcLFixfbo6UghBobG0ND
Q8W0RCphYWGyEuE9ePDghx9+kPU8pqamrlu3jqpAKoKbmxt+P1D37uzt7cl7g/rQEUQi0e7du5Ub
RQd9ehBCt2/f3rhxI9FSaDSaqamplZUVeY6am5tDQ0MjIyOprciD2dDQIOtx5vF4ZAUhKCiIuslQ
V1e3YcOGy5cvk0uhqalpY2NjaGhI6iQlJa1fv17WP045VHXee/fuyXnJJyUlbdy4UbWSS2JgYEDu
t27duuGD1I8a2SwlC7JcLpf464qRmppKvozUt26rcLncLVu2nDx5UuzTT30P37lzZ9WqVdhkgKCu
rk5EJSt3LBbLjwKZmQDvEbCjIh3yQDY3N+fl5fXs2ZP8JBQKyToBVlE8PT3xn8+fPxcKhdSZaHZ2
Nnl/SVpElJWVbdq0Cds5sFisTz/9dMCAAdj0pbi4+OLFiziOfkFBwb59+7799lvF5f/zzz9JTlZ3
d/c5c+b07dsXC1ZfX3/t2jUcFQd/MH755RdZs+fs7GyEEI1GGzhwoLOzs4GBQUNDA9U45/jx4w8e
PMDloKCgGTNm2NnZ0Wg0LpebkJBw5MgRPF07fPiwi4uLk5OT4kM4depUVFQULjs6Oi5atMjd3Z3J
ZIpEotevX588eRK/H1++fHnkyJEvv/yS2jY/P5/oDwwGY/bs2aNHjzY3N8fDj4qKOnHiBH7pHzly
xNzcfPDgwbLE+OOPPxBCNjY2c+bM6dOnD4vFamxsTElJOXr0aFlZGULozZs3UVFROHyKlpbW1q1b
cUPqNvqKFSukblUryIkTJxBC3t7eM2fO7NGjh66ublVV1aNHj4gWd+PGjeDgYGtra6VPIRUVXkbl
qKioCA0NxU8Qi8VauHDh4MGD8e1XVlZ28eJFnNKLy+Vu3779+PHjiiyw2djY9OrVC6c2evDgwaef
fip58yckJJDHdsiQIW0VG7uleXt7T58+3dHRUV9fn81mv3jx4vjx44WFhQih+vr6ZcuWYUOXIUOG
BAcHd+/enclkVldXP3/+/Ndff2Wz2QihxMTEhIQESXu8p0+fHjx4EJd79+69YMECNzc3JpMpFApf
v3594sQJnIs2Ojrazc1t8uTJ1LbtfDPExsaS5B4uLi741GpqaiKR6O+///7999/xU1lcXLxv374f
fvihrZdOQfB2t6amZkBAgK2traamZlsz0L958+bNmzc0Gm3cuHHjxo2ztrZmMplFRUURERHXrl3D
dX7//ffhw4eLXYGioqLdu3eT0wUGBk6ZMsXe3p5Go5WVlUVFRZ0/f15sJ0ERiHEm1cJtwoQJEydO
lNOqoaHh7t27Soyi4z49aWlpu3fvxuVu3brNmzfP398fq9A8Hu/JkycHDhzAt/eRI0f69+9PrIid
nJysrKyKiooQQk+ePJFqbJmamkqCbYo9mDt27CD5ysaMGTN9+nQS7qmoqOjUqVMPHz5ECL19+/b0
6dPLly9XfETyUdV5seWFu7t7cHCwk5OTgYFBfX19cnLy8ePH8YcmNzf32LFjcozi2o+zszP5fhEj
SQ0NDXKQMGjQoP379+PVipiYGKk76k+fPsUFTU3NNgUIPnToEJli9ejRY9GiRZ6enuTTf/bs2bi4
OITQmzdvvvvuu71795LNN11dXSLq0qVLcfoyT0/Pr776SvGzA+8gsKMiHarZg1jax+zsbLytr6Wl
hZ3jbW1t8dsWGz9QK5O2GhoaPXr0EDvL/v378TzPwsLil19+CQwMJDqApaVlSEgI8R94/PgxdYNe
PlwuNzw8HJd9fX137dpFtTrT19f/+OOPFy1ahP/MycmRky4GIWRubn7s2LEtW7bMmjVrzJgxwcHB
ZNUtIyMDb9YjhJYsWbJ+/Xr8wcbjHTRo0IEDB/C8ViAQ4Nm2grx58wZrCHgI+/bt8/b2xgsqNBrN
2dl5+/btZFEnMjKSuuMhEon27t2Lp9dMJnPbtm3z5s3DYuDhT5w48dChQ2QbPTQ0VP6qoa+v76FD
hwICAkxNTel0up6enr+//08//UQWsPGnqEOZM2fOjh07PD099fX16XS6qanp1KlTqe9fWZsDSqPy
y6gEDx48wALQaLSdO3eOHDmSPCDm5uafffbZkiVL8J/V1dWPHj1SsFty52BDAskKZNXW1NRUuQAY
EyZM2L59u4+Pj4GBAY1G09fXHzx48L59+4j5B9ZSPv744//973/Ozs7q6up0Ot3ExGTMmDE7d+4k
S8VEVyc0NDTs2bMHlwcPHhwaGurh4YEfDTqd7uLismPHjkGDBuEKJ0+e5HA4pG373wxES7GwsPjp
p588PT3xLIFGozk5OW3bto1MWZ49e1ZQUKDEpVMQb2/vc+fOrVq1atq0aePGjRs/fnxbe1BTU9u6
deuXX37Zs2dPTU1NJpNpZ2f3xRdfEN2gvLxc8gocO3aMLPQuX758w4YNvXr10tDQUFdXt7GxmTt3
7r59+6TufnQQyo2igz49CCFyg7FYrAMHDowYMYK8J9XV1YcPH/7999/jP7lcLlnkQv+aZeJyVFSU
1Fzp5MHs0aOHnZ0dOZ6RkUHW9RctWrR69WpqUForK6sNGzb4+vriP2/cuCHHRqBNqPa8kyZN2rVr
V//+/Y2MjOh0uqGh4fDhw48cOUIWuW7evJmTk6MSyduJvr7+gAEDcPnJkyeS4xIKhcRIb8iQIdQd
V/kkJiaSlRRfX9/9+/f369eP+unfunUrcUR5/fo1mScAHzCgqEjHwMCAOL6LvaaJTYivry95fvz8
/PBBvJZJIG3xuiP1p4yMDOzZghCSZX46bdo08pLCfqiKUF5ebmdn5+zs7OzsPHPmTKm7JePGjSOT
ITmKCo1G27p1q6wYAGfOnMEFHx+f4OBgyQqGhoZkDSkhIaG4uFjBIVy6dAmvWWpra69Zs0YyHRWd
Tl+xYgWxn46OjiY/JSUlkcs+b948b29vyf4tLS3JLL+hoeHGjRuyJDE3N9+0aZOkB4iFhQVZ0svI
yGjrgm6bGDZs2Lx58ySdKYcMGULWI8XU6faj2suoHHhJDCHUs2dP6ryEMHXqVHIPEGewVvH39ycX
k3xNCVwuF6/YIYRGjBihhKlet27dli5dKtnQwMCA6ldta2sr1X/A0dGRXG3JOeKNGzdwigADA4M1
a9ZImqUxGIwVK1bg442NjdQBtv/NQOzBhgwZImmYzmAw5s+fT/6UvwLSHszNzb/77rt2Wqh/9tln
/fv3lzxOjYchtvBUVlZG1ol9fX2nTp0q2bxnz57r1q1rj2BtQolRdNynByHE4/HwDTZjxgyq+RPB
zc2NeJSJuYCSN2pDQwNJPkYQCAQk3biYL2hFRYXzv0hVWel0OtlaxFYSio9IDio8r6Oj4/LlyyUf
SV1d3XXr1pFHUiw4RBcSGBiIC83NzZK5GV69ekUymbTJ7uv06dO4YGhouGHDBqmZKBctWkQM6S9e
vEjNaAd8kIDpl0w8PDzwOr3YG5NsSpKVEoSQt7c33mp//vw5UfdFIhFpS3KzEMgbx9XVVVacHBqN
NmLEiGPHjiHZeVoksbGxIbFiZKGrq6unp4e3hqqqqmRVGzhwoIODg9SfysrKiK/O9OnTZfXg6+ur
qanZ3NyMEMrIyFDE77ylpYWstI0aNUqWB6G2tvbQoUPxEi91mk4urLa2ttQYXBgvLy9vb2+8Hnbt
2rXZs2dLrRYcHCzLT93R0RGfi8PhcDgcqeGqVIJkJBMMXsbGdroqdwlQ7WVUDvKVkmWczWAwvvnm
G/yrWBwhORgbG/fr1w/P1R4+fChm/fXixQt8uyKEZEUqk4+bm5usAA/UrdoRI0bIMph2dnbGDm+S
rg7Esn/ChAmyZuomJiYkwsfLly/JrK79bwYyrsbGRqnNbWxsNm/ejMuyFjjaz7Rp01qNSyYfHR2d
sWPHSv3JyspKQ0MDLxKLXYH4+HiyJCHrqUTS3vYdhHKj6LhPD0KI2H3JwdLSEr+xxXwMrK2tnZ2d
8U+PHz8Wi3KWnp5OQhSIPZhDhw4dOnSo/JOS3WD0735m+1HheceOHSvrbdCzZ08vLy/8jn306NGy
ZcuUElbF+Pj46Ojo4PdAdHQ02WDBkGmSnp4esY1vlYKCArI0M336dD09PanVaDTawoULV61ahRBq
bGyMjY0dMWKEcqMA3gtgR0UmJBxQeXk5eZ82NDSQB4m6xuzu7o7XPNLS0sgnvLCwEBvjImkZVKQq
PJKQj315eblqTWvIa1EyWgBB6noGhuhgDAZDVugkhJCamhoZgoLb1jk5OWQrWX5Y2MmTJ2/evHnz
5s1EUxKJROTCDho0SP5shqwJVVRUYDtgSeQ4UlMdT6kGNipHVgAcqgyyJo7KofLLqBwkIEFJSUl4
eLhQKJSs4+np6e/v7+/vL+cmlIR82KqqqsQW/sl2io2NTavRXdsKVbWQE0GY/FtbWlqoNjDFxcUl
JSW4LCdYLUKIGJoSA3rFkfNmIBf59u3bZJ2CCpPJ9P+XVqOHK42c95KC0Ol0WXtlNBqN/JvEFmvJ
goi2tnab7rcOQrlRdPmnh8gsad9FlOro6GixX4l1q7u7OzX2g4JQd6Sl2pV1EAqeV378YmJRWV5e
TnYquhYNDY3hw4fjsqT1FzHEHT58uOLBSKgGKcR+VSqurq7kHpAamhX4kIAdFZmIualgG5uUlBS8
oubo6EiNNqirq+vq6pqWliYQCNLS0vBePIn3RaPRxAIp1tXVEeXnwoULYvFPqJAEqwih+vr6tgaL
rKioiI2NTU9Pz8nJqa2tbWxslKOWtAliliMUChcsWCCnJllGUnAdC/tTYqQa/BBsbGzEJkOVlZVk
9V3smktCde7Py8ujLn0pAvXTInUO3QmQT75qBejMyyiHESNGXLx4ETugnzhx4ubNmyNHjvTy8nJ0
dGznVNXPz4+sNz9+/JisKwuFQvKJ7YhVOuo9I2dqQv2JalWYn59Pyj/88IOcCDZEcRUL60xQ7s0w
a9as2NhYLpfb0tLy9ddfu7q6Dh8+3P3/sffeAU1d7+P/DQQT2YQlKqKolaWCCIKyFfeoq1Wrta3v
VkVxMkSUarWKooBbK1qt+HaLtVoHIoIiIIgLUQTZoAHCDCOs/P443/f53U/GJSQBoj6vvw6Xm3tP
Tu4953me84zhw/v16yeFj5zCgr+LgEsnjroZOHCg4n9fkd+iy5ae+vr65OTk58+fZ2VllZeX19bW
SqIeODk5HTx4kM/n19TUpKen48zgfD4f+/diy4hI3r9/n5iYmJmZmZeXV1tbW19f36l+uV1zX/I6
+PHjR5E+dV2Ph4cHen6Q9xfeVMnPz0eTNtFBvy8ca6qqqkpdCYpGo1laWqINZ3FVuYHPBlBUxGJg
YGBoaIgsxBkZGWivGUfOCWx0EgQxatQo5CWflpaGFJWMjAz0L3NzcwH3IbLIzuVyJUw72CFfzNra
2j///PPGjRudNE1jdwI+ny+wgy8OCa3+5BIEHXVDJ1ub9PT0qE8mOwt1Wd2DTwIFGUYmkxkcHLxt
2za0LfDx48e//vrrr7/+UlFRsbGxsbW1HTNmjHR6Uc+ePV1dXe/evUv8X++vzMxM/G5K5/fVqZB9
eMRpIALgTV3yEalnBlNT0+3bt+/cuRPd/fXr12iHWVNT087OztbWdvTo0eSdxs8MPJjCFW8/Fbpg
6Wlra7t27drp06elCB4gu2U+fPgQKyqZmZno4VdWVhZXtSk/P//QoUMCYaJdQBfcl+wEJd/Nc1lA
2xpIW4iPj8dCEY6A0tXVFedbKBI8pxkaGrZbIhMvTPJy5AMUFlBUqLCxsUFxhEgD4fP5OJJS2CUJ
O2ImJyejCHK8I4mrsmDIZYwkR/LNEA6H4+fnh7NkMhiMoUOHGhsba2pqYlP0mTNnsC++FEiROEXC
/pMNbx01nJOtgO3WQCR7NCnO7K8IKM4wGhoa7t+//86dO9euXcObeM3NzU+ePHny5MnRo0cdHBz+
85//kJPtSIiHhwdSVJD3F1pQsd/X4MGDO89zSWqkmDcEXjrZZwZra+sTJ05cvXr15s2bWLCoqamJ
iYmJiYlhMBiTJ09etGiROP/yTxo86XVeQFpn09lLT0tLy86dO3HUO8rUNHDgQB0dHQaDgaTP+/fv
U7gBjx07Fkm6cXFxXl5eaNsQ5/tycHAQubfz6tWrwMBA7IKrpaU1bNiw3r17q6qqItejqqqqS5cu
SfgtJKdr7kteB2VZteWLkpKSp6fn2bNnCYJ49OjRmjVr0FpA3pTu0MZjh94vvO6AkfGzBxQVKoYO
HYoUlczMzIaGBjabjYw6Ghoawv4wgwcP1tDQqK2tLS4u/vDhg4aGBk7xIezNTPba/O2334T3Z2SB
z+eHhIQgWYROp//yyy+TJk0Szg94+fJlWaY8HDhhamp67Ngxqa8jDFkybm5upojQEIY8wbXraUA2
+HXoLp89CjWMSkpKkyZNmjRpUmFh4fPnz9PT058/f45EZGQ7SElJ8fHxoXYIEcba2lpHRwdZ4xIS
EpCi0ql+X7JDnjcuX77cUW8cec0M6urq33///cKFC9++ffvy5ctXr17hDAQ8Hi8qKio2NnbXrl2y
1A5STPB7QdbkPy06dekhCOLSpUtYS5k6derChQuFK7Ln5uZSKCrYLbO6ujo9PR2Z+XCebhwXQaam
pua3335D2oK+vv6qVavs7e0FROTCwkK5Kypddl/y+yhjGgn54ubmhhSVxsbGZ8+eOTg4kKP+OlqE
Cm/GSvJ+4XVHoQYE6AwU3cu2e8FhKnw+Py8v7/nz5+hPkfXFlZSUcJrIFy9ekBMR4myMGLJHk4R+
U5Lz9u1b7KLm6+s7c+ZMybOYSw4WkkpLS+XrXUYenI5a6Mmfbdc3huxIoyBevwqCYg6jsbHxtGnT
AgICzp8/f/To0dmzZyOpq6WlZdeuXR31VFZWVsbayIMHD9ra2goLC3EQgtyLV8oFcoEOimR94pDv
zKCkpGRhYTFv3rzff/89Kipq9+7dOP61qqoqICCgUzNMdAt4/BUkoFkKOnXp4fF4uK7FlClTVq9e
LayltIuqqip++1AAfU5ODsohwWAwROZivnPnDvpFVFRUQkJCRC7QnUGX3Zf8vCmUa2X//v1x3g4U
RIT9vvr06dPRZCRYqJAkiSXOiCjFMwZ8WoCiQkXfvn3xm/Phw4cXL16gtrhkKdgfLCMjA0s8pqam
wvW/0D44aneonJYk4GyS6urqHQpl6xBGRkaoweVy5VvZjRxF19Eaz3p6evgna1dyJVv1pPAdUnDw
kilF+gS5DCM51Fu+sf40Gm3gwIHLli3bu3cv0lX4fP7Vq1c7eh1snS0rK3vz5g3OhiRdWqEugByQ
I0XlnM6bGeh0uo2NzZYtW3DdpIqKCoFqlZ2U+KErwbna37171zUh2nKnU5eezMxMbOeeNm2a1Nfx
8PBADWRBwB7X4koHYuHYwcGBOghbvnTZfclZNHr16tV5N5KCCRMmoMajR494PB5OzjZu3Lh240wE
wHuwlZWV1Fo0n8/H+zbCpbSBzwxQVKig0Wg48qSoqAgpKuSDAuDjr169wrK7cIAKQRB0Oh0fT0hI
kK+TJbZGoAK34k6TUVwg+7ORCwzLzoABA/BSSp3C//bt2z4+Pj4+PuHh4egIjUbDaVvj4uKod5Bx
RXkWi6WAAQkygg1vwuHU7SKXYSSLFFL04fXr1wf+h7iQXwsLCxxZK0XuF3IgSkJCAq6NiOUkRQNV
H0ftO3fudPTjMs4Md+/eRT/HX3/9Je6zX3/9NY5OwTFFCOw39eluR2CP36qqKinyPisCnbr0kHf5
KOoatbv0jBgxAj1FlZWVr1+/xvm+RPp9EQSBs6JTGNc7Q7GU432pT8OqmqGhoeQFo7oGXD+3sbHx
4cOHeM+2o35fxP8VKoRL8ZLJyMjAD5vkdVqATxRQVNoBF0CNi4tDwpaFhYU413AWi4WU+6KiIpwD
RFy6fSwM8Xg8XOJdJPfv38cJxCQBeyGXlpaKC3m/d++ejKnxv/rqK1y98erVq7i8gzBcLjcyMlLy
IE46nY4H59atW+KWUj6ff+PGjRcvXuCdLsT48eNRo6amhiL55uvXr/GUOnny5I7aftql25MX4y2v
jIwMcasg3kMQRvZh1NDQwOFG4rQIPp+Pw2QFaGhouP4/KJ5/vF0pXW0EbA68c+cOMjDTaDRxaYW6
HTqdjmW1jIwMHFEjDJ/PP3funIB7mIwzQ3FxMfo5zp07J+6tVFJSwhqywC+CN6m4XK646eLVq1eK
XGfa3t4e7xNSBB6gYp2y00mbNp239JA3UUtKSkSeU1hYSPHcIuh0Og45i4yMRH7Umpqa4kRS/GBT
7MBfvnyZ+qZSIMf73rx5U9wM9u7dO7zGSSH9SweeydvdkEflZVH7yJEj6FsMHDhQCicFExMTXHHu
woULFI7f+LllMBjUFVeAzwBQVNoBh6ngmYg6+tDBwQE1sD8MuR4LGVdXV7yHGxUVJU4WjI2NDQ4O
Xr9+PQrrlwS8f8rj8UTOknFxcXgLgpBWwlNSUvruu+9Qu6GhYevWrSINpdXV1Vu3bj19+rSfn5+E
CVUJgvj666/RRFlbWxsWFiayh+fPn8dGTVwmjCAIW1tbbPiMiIjAhSnJlJWVBQcHo3bPnj1l8VIQ
BzkeXbi+eBeAHzw2my1SGUhJSaEwjcs+jEpKSjg3ZWxsrHAtSD6fHxkZifUcASwtLfEYnjhxQuSi
xeVy8VeTzgEAF5bGkre9vb0iByzNnTsXyxB79+4V6QDW2tp67NixkydPrlixgnyCjDMDdnltaWmJ
iIgQKUa/ffv248ePqC1QmZ5cb+fatWvCny0uLg4JCRE+rjhoa2tjl7n4+HiRk3ZWVhZ5DDtKz549
8e+LR1K+dN7Sg13jCII4e/assIybk5MTGBiIjVYUSw8eZ7yp7uHhIa50IH600tLSBOxWBEG0trZG
RETcunWLfKS9ryIRcrxvdnb2/v37hQekpqYGvxQ0Gg0bVjobbG5AWQ2oT8brL55FpU5GsmDBAtTg
cDghISHiln5sC5g1a9ZnmWAQIAOKSjuYmpoKpGclF6QXRqBctJGRkbiM+3Q6PSAgAJug9u3bt3v3
bnIVxaysrJCQkB07dvD5/JaWFsmF3dGjR2MJ79SpU7///nt6enpFRUVJSUliYmJgYOD27dvJ9lSp
U8p6enpi2/P79++9vLzu3buHDaJcLvfWrVteXl4oCUFJSYnky4Opqen8+fNR+9GjRz4+Pi9fvsQf
z8vLCw4OPnnyJPpz0qRJ5GTtNBrN398fOY81Nzf7+/tHRkZip5f6+vro6OgVK1ZgIcDLy4vFYkk3
AhT07dsXtyMjIwsKClpaWioqKrqsKLKbmxuWeIKDg2/dulVbW8vn81EunfDw8MDAQOpKybIPI17A
GhsbN2zYkJqayuPxWltbORxOQkJCQEAAhabUs2fPRYsWoXZOTs6qVasSExPxc8vj8R4+fLhu3Tqs
/U6aNKkjw/P/6NWrF941RSis3xfC2Nh46dKlqF1XV7du3bqzZ89if26UuNnHx+fKlSsEQVRUVJDf
bhlnBktLS2yIuXXrVlBQ0Nu3b/FuYXV19d9//x0QEID+ZDKZAoVoLCwsyHuwERERbDabz+fX1dXl
5uaeOXNm5cqVFBuzCsKSJUvwirBv377Q0NCsrKympqampqbCwsIzZ86sXbtWCkdHjLKyMhb3b9++
/fz5cx6PJ3nBE0novKXH2NgYT8WpqamrV69OSkpis9nl5eWvXr0KDw9fsWIF+Sem+FIWFhYCJZKw
TUEYsqEqICDg1KlT2dnZ1dXV+fn5t27dWrZs2YULF8jny2vXTr73vXXr1vr16x8/flxZWdnW1lZd
XR0bG+vl5YXLIM6YMYO6ArIcIe+HREREoJVL3JPg6OgokHpL6iJUo0aNmjx5MmonJCSsWbPm2bNn
eOnPzc3duXPniRMn0J/Gxsbz5s2T7kbAJwSkJ24HZWXlYcOGYQ8Z7NwlDnNzcyaTiZMJUntPWlhY
BAQEBAcHI3kxOjo6OjqayWRqaGhUVFSQxXoPDw8stLWLlpbWypUrd+/ejf588OCBQFQrQRCGhoZt
bW1IvhG3R98uNBrN19d369atSBUpKyvbtWsXjUbT0dFpbm4mr9aqqqpbt27tUJW0RYsWlZSUoJ6/
fv16/fr1dDqdxWLV19eTlzd7e/tVq1YJfNbY2Hjr1q1btmxpbGxsaWk5ffr06dOnNTU1VVRUKioq
yJbghQsXTpw4Uapv3w7a2tq2trZouyArK2vJkiXoeGRZ+xpaAAAgAElEQVRkpBxrt1NgaGg4Z84c
5KDS2NgYGhoaGhoqcA5KqC3uCrIPo4uLS1RUFDLqFxUVYSlWwj7Mnj27qKjo5s2bBEEUFBQEBQUp
KyuzWKzm5maB7bvp06eLS3HRLp6enrjkkYqKisi0QgrFrFmzysvL0ZZIc3PzqVOnTp06pampSafT
Kysryb+Lt7c32bAi+8zg7+/v5+eXlZVFEERSUlJSUhKDwdDW1kaluPFpNBpt/fr1AoorjUZbvnz5
5s2b0Z8XLlwQEOMIgqDT6XQ6XXEqRQijr6/v7++/detWNM63bt0im8wRuFKwdHh4eCC1gcvl+vr6
ooMBAQFyVKE7aekhCGL16tVr1qxBD0NmZib+uTEqKir9+/dHj1BNTU1dXZ3INFY0Gs3T0xN7+BgY
GFCUDrS1tZ04cSLa+Wlubj579izKmUvG0tISJw+Q11aVHO/r6OiYmJiYkZHx66+/ijzBzMzsxx9/
lEu3JcHa2lpNTQ2ZKm7fvo2+o6GhoUhfQZSoLSYmBv1pZWUlyxrn5eVVXV2NgvIzMzP9/PzQ0l9b
W0tOJGhoaLh9+/ZPt6IRIDmwo9I+w4YNw+3Ro0dTBzOoqKiQJQMBY60wrq6uYWFhgwYNwkcaGxvL
ysrwUqGiouLt7b1hw4YOBVF4enr6+vqKyy9ua2u7f/9+/L2ysrKktjCpq6vv3Llz/vz5eFOez+dX
VFSQRU8rK6tjx44J52imBpn9fvzxR/wtkEUHayl0Ov2nn37aunWrSH8AW1vb8PBw8k1ramo4HA4W
47S1tQMDAxcvXtyhXnWI5cuXd28qyR9//JFs8xPA0tJyz5491FeQcRjpdPqWLVsoklROnTp1zZo1
4v5Lo9FWrVq1cuVKvBq1traWlZWRtRQGg7F06dKVK1dSfxEKnJyc8CM0ZswYhcr+KRIajbZ06VJ/
f39yWG1NTQ1Ze9TX19+zZ4+wT6OMM4O6uvru3btnzJiBpyMej8dms8mnGRgY/P777yKzijk4OHh7
e4ubyvT19UNCQshbkYrJmDFjtm7dKpzLEWFtbY1VQemYMWNGF5Sg6aSlZ8CAAbt37xYnp/bp02fv
3r3kx5IiJwF5C6XdFFKrV6+eOXOmyH/RaLRZs2bt2bMHB5eKdGSVDnndd968eevXrxdXXXfUqFG/
//57VwrlqqqqwhZACshlrDpa0koABoOxefPmxYsXCyz9ZC3FxcXlwIEDeIcW+LyBHZX2wdFdhKiC
9MLY2dnhDH3iAlTImJmZHT58+MmTJ0lJSenp6eXl5c3NzQYGBkZGRo6Ojs7Ozh0t64YYP378iBEj
bt++/eTJk8LCQh6Pp6enN3ToUHd3d/QtJk6ciGWy8vJyqfPzIoVh2rRpcXFxqamphYWFlZWV6urq
hoaGQ4YMcXNzs7S0lC5UXUlJacGCBePHj3/w4EFKSkpRUVFlZaW2tnbv3r0dHR1dXV319PQoPj5w
4MD9+/enpKQkJia+evWKw+E0Njbq6Oh89dVXjo6OLi4u7dZclxETE5ODBw+eO3cuNTW1pqZGQ0PD
1NS0M2raiENFRcXPz8/T0/Pu3bvp6ekcDqdHjx4sFmvo0KFjxoyxs7OTpK6WjMOoq6u7f//++/fv
x8fHZ2Vl1dTUqKmpGRgYjBgxwsPDw9TUlDqxm5KS0owZM9zc3BITE5OSkgoKCjgcTmtrq6am5sCB
A0eMGOHq6iqj556GhsaAAQOQibfz0nnLnXHjxjk5OcXHxz958iQrK6uiooJOpxsYGJiYmLi6uo4c
OVKcNiLjzKCurr5y5cqvv/768ePHKSkpHz9+5HA4dDpdV1d3yJAho0aNGj16NEUJtunTp9vY2Ny8
eTMtLe3jx49tbW3a2tpfffWVvb29u7s7g8H4JMq3OTo6njx58u7du48ePSoqKuLxeCwWy9LS0s3N
zd7enuwyJy6sggImk7l3796LFy/Gx8ez2Wwmk2lsbNwZ27CdtPQMGTIkIiLi3r17CQkJ2dnZXC5X
S0tr0KBBLi4u7u7uKioqurq606dPRyeLS+pA/K9GB4r2pPD7QtDpdC8vL09Pzzt37jx79qy0tFRJ
ScnQ0HDkyJHjx49H4VI//PADrm/W0VLCnX1fNTW1iRMn2tnZRUdHJyUllZSUcLlcXV1dCwuLsWPH
Sr1dLAseHh7a2tqXL19+8+ZNY2Ojrq6unZ2duJOxqCOXZCTKysoLFy6cMGFCfHx8cnIyWvoZDEbf
vn2HDRvm7u7e0QotwCcNreuTwaM7trW1tba2NjU1NTY28ni8rsx9DgAAgGGz2QsXLiQIomfPnpcu
XfokBGVAkcFPFCFvly0AUExiY2N37NhBEISdnR1qAJ8BxcXFDAaDyWT26NFDWVkZJbWXe4rUdgHX
LwAAvmhwnIabmxtoKYDsZGdn43bXBKQBQPdy9+5d1AC1HJA7oKgAAPDl0tLSgtOztuteAgAEQSQn
J6P0IeLA4fVMJhPn+AaAz5Xi4mKUL5hOp+PEgAAgL0BRAQDgy+XKlSsoFU+vXr2gwjHQLvn5+b//
/ntQUJC4qo7//vsvzhI5depUKWJUAOAToq2t7ciRI6jt6emprq7evf0BPj9gDgUA4MuCw+GgNDK3
b9/GHguLFi1CDrgAQEFUVBTKPhQQEDBp0qQpU6YMHjxYSUmJz+fn5+dfv379n3/+QWdqa2vPnTu3
WzsLAJ1CS0tLdXV1Q0NDQUHB5cuXUXp3Go0GDzzQGYCiAgDAl4W3tzeukIiwsbGRupQy8EWxdOnS
vLw8VBkDFVFRVlbW1tbmcrnkBFZMJnPLli2dUUkWALqd0tJS4ZT033//vbGxcbf0B/i8AQsiAABf
NBYWFps3b4btFEASevbsGRISsmTJEpxktrW1lcPhkLWUQYMGHTx4kKJAIQB8ZkybNm3BggXd3Qvg
8wR2VAAA+LKwsLBIS0tramoaMGCAp6fn5MmTIZAAkBwVFZV58+ZNmjQpKSkpMTGxoKCgtLQUlQcZ
OnSoo6OjnZ1d12fwBIAug8lkmpmZ5ebmqqioWFhYTJ8+fdSoUd3dKeCzBeqoAAAAAAAAAADw/wN1
VAAAAAAAAAAAAEQDigoAAAAAAAAAAAoHKCoAAAAAAAAAACgcoKgAAAAAAAAAAKBwgKICAAAAAAAA
AIDCAYoKAAAAAAAAAAAKBygqAAAAAAAAAAAoHKCoAAAAAAAAAACgcICiAgAAAAAAAACAwgGKCgAA
AAAAAAAACgcoKgAAAAAAAAAAKBygqAAAAAAAAAAAoHCAogIAAAAAAAAAgMIBigoAAAAAAAAAAAoH
KCoAAAAAAAAAACgcoKgAAAAAAAAAAKBwgKICAAAAAAAAAIDCAYoKAAAAAAAAAAAKBygqAAAAAAAA
AAAoHKCoAAAAAAAAAACgcICiAgAAAAAAAACAwkHv7g4AAAAAwKcKl8vNy8tD7QEDBqipqXVrdwCF
oLW19c2bN6jdu3dvFovVvf35MsnKyuLxeARBaGlpGRsbd3d3ACkBRQUAAAAApOT9+/c+Pj6ovW/f
PgsLi+7tD6AINDQ0rF27FrXXrFkzZcqU7u3Pl0lYWFhWVhZBEO7u7hs3buzu7gBSAoqKaM6dO3fy
5EnUjoyMNDQ0JP/3xYsXeGUSSc+ePTU1NY2Nja2srMaMGdO/f//O6yqZxsbGly9fpqamZmdnV1ZW
cjgcT09Pb2/vrrk70JXk5uYGBwez2ezx48cvX76cRqPJfs26urrg4OAXL15YWVkFBARoaGjIfk3g
M6asrCwlJSU1NbWwsJDD4TQ2NmpqahoaGlpYWNjZ2dnY2MjlsQSArqG+vn7GjBmyXGHTpk2urq7y
6g8AAAQoKp1EQ0NDQ0MDm81OTU09deqUo6Ojt7e3vr5+592Rx+Ndu3YtMjKysbGx8+4CKA5nzpzJ
yckhCCIqKsrV1dXS0lL2a967dy8pKYkgiJSUlH///ffbb7+V/ZrAZwmXyz137tzVq1dbWlrIxzkc
DofDycjIuHz5srGx8erVq4cPH95dnQQAAAA+dSCYvitITEz85Zdf3r5920nXz8vLW7JkSUREhICW
QqPRlJWVO+mmQOeRnJzs+T+QNiJMa2srbre1tcnlvuTriLyml5cX6tW2bdvkckfgU+TDhw8rVqy4
ePGigJYiQGFhoY+Pz8WLF7usYwAAAMBnBuyoyIq/v7+zs7PAwebm5srKyoyMjCtXruTm5hIEweVy
N23adOjQIQEvMtnJzs729/evqalBfxoZGU2fPt3Kyqpv376qqqpKSqCLfp589913eXl5paWl48aN
s7Kykss1x44dm5CQkJ6ebmZmNnHiRLlcE/jMKCsrW7NmTUVFBfrTwMBg5syZI0aM0NPTYzKZXC73
/fv3MTExMTEx6ITjx4+rqamBjz6g+Kiqqt65c0fkv4qKipYsWYLaXl5e4jzEwNcRAOQOKCqyoqKi
wmAwBA4yGAx1dXVjY+OxY8cePHjw5s2bBEFUV1dHREQEBgbK8e61tbUbN25EWgqdTl+xYsWkSZNg
F+VL4Kuvvjp9+jSfz5fj0qipqblnzx75XhP4nODz+aGhoVhLQSFwPXv2xCewWCwWi2VnZzdhwoSg
oCC0x3vkyBFbW9tevXp1T6cBQGLEmfbIUyKNRgMLIAB0GfCydS50Ot3b29vc3Bz9+eDBAzabLcfr
R0REVFZWEgTBYDBCQ0OnTp0KWsoXRWdoFKClAOKIj49PTU1F7TFjxvj4+JC1FDI2Nja+vr6ozePx
rl692kVdBAAAAD4jQFHpdJSVlclByc+fP5fXlbOzs//991/U9vPzw+oQAABAZ3Dt2jXUYDAYK1as
oLYru7i44Enp9u3bTU1Nnd4/AAAA4PMCXL+6AnJGppKSEtT4/fffHzx4QBCEoaHhmTNnxJmxKysr
v/32Wz6fTxDE0qVL58yZg/919+5d1LC1tXVxcemcvhM8Hi8+Pj4xMfHdu3cVFRUqKir6+vpDhw51
dXW1trZu9+Pv37+PjY198eJFUVERj8djsVh9+/YdNWqUq6srRQ0sLy8vlP78p59+mj9/PkEQaWlp
Dx48SE9PLy0tVVFRMTIysre3nzZtmq6urvDHk5OTN23ahNp37txRUlKqqqq6f//+o0ePiouLa2tr
dXR0zMzMPDw8Ro8e3e4GAo/Hi4uLe/ToUWZmZk1NjaamppGRka2trYeHR58+fag/y+fzU1NTHz58
mJGRUVpa2tbWpq2tbW5u7uDg4OLioqKigs/kcrkzZ84UvsLSpUtx+8aNG9jPMDIy8vTp06gdHR2N
Gnl5eT///DNqb9iwYezYseI6dvTo0StXrhAEoaamduHCBXRZct5tXBEiIiLiwoULAh+Pj4/39PRE
7YULFy5evDgmJiY4OBgdWbdu3aRJk0Tet62tbe7cuchZ0dzcfP/+/eJ6KJIPHz48fvz4yZMnJSUl
HA6HwWDo6+tbWlq6uLhYW1uL/CkrKiqwpQB9qYqKipiYmOTk5KKiopqaGl1dXRMTk7Fjxzo5OeFf
hM/np6enR0dHZ2Zmfvz4kSAIPT29YcOGTZgwwczMrN1+cjic+/fvp6Sk5ObmcrlclLTX1tbW2dnZ
1NRU3KfwUI8YMWLXrl0EQeTn58fExKSkpHz8+LGlpUVfX3/48OGTJ08ePHgwdQcqKyujo6MfP35c
XFzc0NCgq6trbm7u5uY2atQoGo3m7++flpZGEMSyZctmz57d7tdBFBYWpqeno/b48eMlSWM4fvx4
VPauoaEhJyeHYuikmyjISDfmZFJTU+/fv5+RkVFeXt6zZ8/evXs7ODh4enrq6emlp6ejshjKysq3
b9+W5GrC5OTkREdHp6WllZSU0Gg0FotlZmbm4ODg7OwsxU74ggULysrKCIKYOXOml5eXuDviCWTH
jh12dnbC57S1taE56vXr1xwOp7W1VUtLa9CgQWiKU1dXp+4GmuJiY2PT09PLy8uZTCZ6Sp2dnYcO
HSryI/g579+///Hjx7lc7j///BMXF1dcXNzY2Cic4VfGHioIzc3N8fHxcXFxOTk5FRUV6urqAwYM
GD169MSJE4W9xwWQZQ2iJi8vLzo6OiUlhc1mKykp6evrjxgxYuzYsYMHD25ra5swYQI67eDBg0OG
DMGfIq+wFy9e1NLSunfvXnR0dE5OTk1NzfTp0wWKIrS0tKSmpiYnJ6OXq6GhQVNT09TUFN1LR0dH
ZN+wGLB+/fqJEyfW19ffu3fv8ePHBQUFVVVV2traAwYMcHZ29vDw6NGjh4Tft0OCBKAggKLSFZDr
UeCodw8PD6SosNns7OxscZJHcnIy0lIIgiBH7fN4PCyezpo1qxN6TRAEkZSUFBYWhl3SCYJobm7O
z8/Pz8+/ceOGtbW1r6+vgYGByM9WV1cfOnQoNjaWfJDNZrPZ7KdPn544cWLhwoXffPMNtVG2qamp
uro6LCwsISEBH+TxeFlZWVlZWZcvXw4KCrK3t6e+QlJS0r59+7hcLj5YWlpaWloaHx/v4OCwceNG
ce4rBEGkpKSEh4eXlpbiIxUVFRUVFa9fvz579uycOXN++ukncV+hoKAgJCREINsbGoEHDx78+eef
GzZskFccPKJ///6mpqYoUVh8fLw4RYXP56NnjyAINze3dpdJSXBwcGAwGKgMcFxcnDhFJSMjA78C
48aNk/z6XC73r7/+unbtGn4dCIJobm7mcrm5ubk3btwYMWKEn58f9XrT1NR08+bNY8eONTQ04IMf
P378+PFjcnKypaVlUFAQi8WqrKwMDw9//Pgx+bMFBQUFBQU3btyYOXPmsmXLxP3oLS0tFy5cOHv2
bHNzMz6Inpk3b95ERkaiujfU0hWPx2trazt16tT58+fJ37ewsLCwsPDGjRvff//9okWLxH08Pj4+
LCyM/MCXlJSUlJTExMQMHz4cR7V1FFxpmyAICS0jzs7OWlpaqC1OHJF9opB9zGtra0NCQhITE/ER
Ho9XVVWVkZHx3//+18vLS1znJaSuru7YsWO3bt0iHywuLi4uLo6JienXr9+GDRvaVT47g8LCwt27
dwvMUWh6fPz48cmTJ1euXEnxnhYVFe3Zs+f169f4SHNzc21tbU5OTlRUlL29vZ+fH34AhGlubi4s
LNy4cSOyBXRGDxWE7OzsXbt25eXl4SOVlZWVlZVpaWlRUVE7duzo3bu3uM/KsgZR0NbWdvr06XPn
zpFnGDSdXrlyZcaMGQsWLJDkOlwud9euXU+fPhV3wtOnTw8fPlxQUEA+iPKYp6SknD59esWKFdS5
W+rq6p4+fbp7926yKFJWVlZWVvbkyZOLFy8GBgYOHDiQup/V1dWhoaHkWb1DggTQjYCi0hWQpSI1
NTXUsLW1VVdXR8LEo0ePxK1SDx8+RI2hQ4eSM4a9e/cOfbZnz542NjbNzc0PHz5MTk7Oz8+vqqrS
1NTs16/fmDFjnJ2d6XQpf+Vr164dOnSIfERLS6u1tRULQM+fP1+5cmV4eLjwJMtms319fT98+ICP
qKioaGhoVFZWommRx+OdOHHi/fv3vr6+FOaQDx8++Pn5iUvRy+PxfvvttyNHjhgbG4u7wtWrV//8
809x/01KSjp69CguISzA33//ffDgQfwnnU7X0tLicrlIHG9tbb1w4cLHjx8DAwOFbfmvX78OCAgg
//SqqqoMBqOqqgqNAJvNXrdu3ZYtW0aPHk0QhLKysoODAzqzsrIyMzMTtYcOHYqfGUlWo/Hjxx89
epQgiCdPnnC5XJHCWWZmJofDQW03NzfqC/bt2xd37OXLl/X19QRBsFisr776Cp9AEISampqTkxPK
9ZSWllZZWSlStkN1WgiCoNFoTk5O7X4dRHV1dWBgIB4TgiCQ4ba2traqqgodSUtL8/Pz27dvH4U8
+tdff7169Urcf1+/fr1z586NGzeuW7euqKhI3GlRUVE6Ojpoo08AHo+3bdu25ORkfIRGo+no6NTU
1OBMvnfv3n337t2OHTsodiTq6ur27t2Lt0xFfpHevXuLVETv378fHBxMFj7IvHjxwtfXFw9ahyAL
i4MGDZLkI1paWsJJEcnIPlHIPuZcLnfjxo3i0sc3NjaGhobKUqeooqJiw4YNKP0jQlNTE23zoj8L
CgrWr18fHBzcxVXt8/Ly1q9fT9ZamUymqqoqHvy6urpdu3ZxOByRJZVev369ceNGNCEQ/xt2Ho9X
V1eHjjx58mTt2rVhYWHidJXa2tqgoCAKLUXGHioIGRkZx48fx8MiQHFx8a+//nrw4EGRBiNZ1iAK
+Hz+gQMHbty4Ie6Ev//+Ozs7W5JLhYSEkE0YAty5c2fv3r14OqLRaHp6ej169GCz2ej1bGxs3Lt3
b0tLy9SpU8Vd5MGDB9nZ2eKSoRcWFvr6+oaGhlJU1q6srJRRkAC6EVBUugLyC49Xyh49eri7u//z
zz8EQcTGxv7www/CEw2Xy8WGCgGhBL9ygwYNevfu3e7du7FTGUEQHA4nNzc3Li7OxMQkICCgXWOD
MCkpKVhL0dHR+c9//jN69GgkAn78+PHq1atRUVEEQVRWVgYFBR09epSsDjU2Nm7evBkLH66urt9+
++2gQYNoNFpTU1NaWtrx48eRfeXBgwc6Ojri/BYIgkCCr7q6+jfffOPq6mpgYNDa2pqVlXX69GkU
7cPj8c6dO+fn5yfuCkhLsbW1/fbbbwcOHKiurs7hcB4+fBgREYHsr//+++/cuXORtE0mMTERrxAW
FhY//vijlZUVnU5va2vLzMz8888/nz17RhBEXFyclZXV119/Tf5sWVlZUFAQ0lLodPr8+fMnTJiA
9EwulxsTE4OK3vD5/O3bt0dERPTu3btnz564OAl5Y33lypUSOq4gnJ2dkaLS0tKSkpLi7u4ufA62
KrFYrGHDhlFfcOLEidjchffiraysNm/eLHCmh4cH+r34fH5SUpLITRWseI8YMUJClx6CIHbu3Im1
lEmTJs2ZM6dfv37oz+Li4tOnTyN7fEFBwZkzZ5YvXy7uOkhLmTZt2qRJk/r06cNkMsvLyxMTE0+c
OIF+rOfPny9durSyshKFlnl6evbu3butre3Dhw8xMTH//e9/0Yp79uzZyZMnC4tfhw4dwhLzwIED
lyxZYmNjQ6fT+Xx+Zmbm2bNnkZ6Wl5e3devWsLAwsu8fmby8vLy8PBqNNmXKlClTpvTt25dOpxcX
F//9999oxiAI4uTJk+7u7gK6a3FxMcrbhv4cO3bszJkz+/fvT6PR0D7ehQsXBEybkoOVNwMDA7n4
28hlopB9zI8fP461FBaL9dNPP9nZ2Wlra9fU1Lx9+/bixYuvXr0ibxp0iObm5i1btiAthU6nL1q0
aOLEiejJr66ujo2NjYiI4PF4DQ0NO3bsOHr0aJc5MvH5/ODgYJwx8rvvvps0aRLakCTPUQRBnDhx
Yvjw4QJue2w2e9OmTUhL0dXV/fnnnx0dHVVVVQmCKCkpuXLlyvXr1wmCKCwsDA8P//XXX0X2oaam
BnVgyJAho0aN0tXV5fF4+NWWsYeKA7I4GBsbL1y4cOjQobq6unV1dc+fPz927BhKrpOXl/fgwQPs
Z4WRZQ2i5v79+1hLQWPr7u5uaGjI4/HQvvHdu3clfOaRlqKvr4+uQBAEzu+Xnp6+Z88e1O7Vq9fi
xYudnZ2RPtbU1JSQkHDgwIHa2lqCII4ePTpq1Chxthv0epqbm3/77bcWFhZaWlo1NTXPnj37888/
0exRW1sbHBx88OBBcWZZJC3IIkgA3QgE03cFaMpGkOVCLER++PBBpPUiJSUF1fUTNj+/e/cONSor
K319fclaCpn8/HwfHx8JTSMYHo+3b98+1DYwMDhw4MD48ePxCtqrVy8vL69169bhWwg4bZ8/fx6b
DxcvXrxp06bBgwcjNaxHjx4ODg6HDh3C8S1RUVHUCQZ69ep16NCh+fPn9+7dm06nMxgMKyurHTt2
YPE9NjaW7PIhzMKFC3fu3GljY4MMmfr6+rNmzfL398cnkP3KEFwuNzQ0FLWdnJz27t1rbW2NJkEl
JSVzc/OdO3eOGTMGnXDq1CnyzglBEMePH0frq7Ky8vbt27///nu8G6aurj5jxozQ0FAmk0kQRHNz
M8WGjxQYGBjgsY2LixN5Dvb7Gjt2rBzzbI4YMUJTU5Pi1nl5efhB9fDwkPCyGRkZWF1fsmTJunXr
sChDEESfPn02bNiAd+3//fdfZGsUx4YNG1atWjV48GBUZcjAwGDGjBk7d+7EJ1RWVtJotG3btv34
4499+/ZVUlKi0+nGxsY//PADVoF4PB7ZhI94+vQp9u2xt7ffv3+/nZ0demZoNJqZmdm2bduw3Tcz
M/P8+fMU/VRRUdm2bdvq1asHDRrEZDLpdLqJicmqVaumT5+OTigtLRU2ZP7xxx/4XVi+fPmGDRuG
DBnCYDB69OhhbGy8aNGi8PBw/Bt1FGzYpnDm6RCyTxSyj3lWVhZOSdKnT58jR45MmDCBxWIpKSlp
a2s7ODiEhIRMmzZN6u8YFRWFfiY6nb579+4FCxZg/VxLS+vrr7/etWsX6jCbzUaJ7LuGjIyM9+/f
o7a3t/fChQux2ySao4KDg9FvwefzcRIFzP79+9HWupGR0eHDh8eOHYu0FIIgevfu7e3tjWNjHj16
RCHy0un0zZs3Hzx4cNGiRZMnT545c+aAAQPk0kOFwt7e/tChQx4eHvr6+kpKShoaGs7OziEhIXgX
RcD1kZB5DaKAx+MdOXIEtRkMRkhIyMKFC/v06UOn09XU1MzNzX19fcnrY7vMmzfvzJkzP//88/Tp
06dPn45n4//+97+ooaure+DAgXHjxuHviwy1v/32G+7S/fv3KW4xfvz40NDQMWPG6OjooHfT3d39
yJEjWDt9//49doYXieyCBNBdgKLSufD5/IsXL2IrspmZGXl30tLSEpsQBBziEY8ePUKNUaNGCQgH
xcXFqFFUVNTc3Eyj0aZPn3748OEbN278888/YVq3d4kAACAASURBVGFheLLgcrk7duyglt4EePjw
IU6jvHbtWpFFKidNmjRq1CjUvnfvHj5eW1t7+fJl1La1tf3uu++EP8tkMjdu3Ig1n3PnzonribKy
8tatW4Vdy1RUVHBkTktLS35+vrgruLm5LV68WHi3ysXFBQ++sNfHv//+ixwztLS01q9fL2ynUVZW
XrlyJTpeV1eHfymCIEpKSvCq8+2339ra2gr3avDgwYsXL0btR48ekcMJZAd7bCcnJwv7G+Tk5JBt
2HK8L51Ox7dOS0sT9i/Cwj2dTnd0dJTwsmVlZWb/Q6R7gJKSErYmNjY2kn1sBPDw8BDpLmVpaUl2
UJ42bZrIsOPJkycj9ZIgCLIfGuLMmTOooa2tvWHDBpF+SkuWLMERxleuXMFuM8J4eXnh94sMOeOC
gAGCzWbjKAt7e3uRoWuDBg3CWYM7Cn5K5WL1l8tEIfuYYy2FIAh/f3/hXT5lZWUvLy/prPWNjY24
zz/88IPI4HJLS0usfP7999/ifPbkDnnOFBlxhHJUoLaAipiRkfHkyRPUFjloBEHMnj0bi4AU6QdW
rlwpLt5Jlh4qFIaGhps2bRKOhDQyMsL9z8jIEPjpZVmDqHn8+HF1dTVqL168WGSc5Lhx4+bOnSvJ
1dzd3ZcsWSIyG0RTUxOat7/55httbW3hE6ysrPCbReGUi2w0wiOgpqa2adMmrPxQ6PmyCxJANwKK
SqfQ3NxcVlb28OFDPz+/48ePo4PKysrLli0jS8xKSkpYsBM2qDQ0NGCxQ9j8jDZMEQwGY+fOnd7e
3oMHD2YwGEwm08rKavv27ViqKywsxB4jkoBtGyYmJiNHjhR3Gs77lJmZiXZ+CIJ49OgRVooWLVok
znFWR0cHWzrT0tLITupkHB0dxTk+kY+jYjIiEee7TKPRcJRFeXm5wH/xtvi0adPEiWV6enojRoxA
bfIkixcMpD2K6xhWEuQ+P44ePRrN6cj7S+C/+KHq06cPHgF5gTcJ+Xw+OTQZQVa8yRkmqHF1dT3w
P8T9FmRdmuJhsLGxEfcv8mot0l+OIAgGg4G9KAWemcLCQmw2njNnjrhvR6PRfvrpJ9Suq6sTaZ4g
CEJNTW3y5Mki/9WnTx+8MONAI8STJ0+wrEPhst+us584cH5hqcPeyMg+Ucg+5uSsEtbW1uIyvNPp
dIonh4LExESk3dHp9ClTpog7DceJlZWVUQRsyBeyC5y48IkFCxYEBQUFBQUJJHHCpmtLS0tx0Ts0
Go1sthB5jqqqqrisGzL2UKGYO3euuHwtODa1oaFBYEtEljWIGuxBwGAwKB5LCZ95Cn1mz549aN6m
yPeDlQeUwk4kpqam4jK+GBoaYs/kzMxM4aUcIbsgAXQjEKMiK9u3b9++fXu7p9FoND8/P+E53c3N
DZnciouL379/Tw4mSUtLQxuRDAZD2LZKtsFv3LhR2GxPo9GWLVv29OlTtLRHRUXNnj1bkni71tZW
bJ2iNnvb2NgEBQXhTyGbCq4Hp6urSx0b6uLicuLECdTOyMgwMjISPkecEz9BSktA/N90BVJcQWAV
LCkpwfIQXgZEMnDgQGRZJNvXX7x4gRpfffUVRRIqfX39X3/9FUmW4jKnSYeGhsbo0aPj4+MJgoiP
jxcIl8dOWePGjZN7bcchQ4b06dMHbfcJ5P4qKyvDO1fiNAGpIX8RcTGX1JDFXJGPIgJLDAKGeeQs
jsD+GCKxtLQ0MDBAOXxevXolMmGRkpISRYVsdXV1JOIL9AEPr6qqqnyzyUnI4cOHUeiaSNasWUOW
imSfKGQf85KSEjyRopwW8gUL6FZWVhTbUGRXxtzcXIrHT46Q07ccOXLEx8dHuIempqYixTu8NUqd
KAm7D5SWllZXVwt7DCorK1O4nsrSQ4WCQrEXWMWw+5yMaxA1OMn4yJEj8R2lRvLUwCLBD4B08zZB
EE5OTn///Tdq5+Tk6OnpCZ8juyABdCOgqHQFpqama9euFek8YGpq2r9/f5S18PHjx2RFBZufnZyc
hGcTLFsPHz5c3BLLYDBmz56NovFKS0uLiookSWpRVlaGPTWxu7BINDU1hVP6YHcUCwsLajnYyMhI
U1MTOb7n5ORQFP1oF+n8JfAU2dbWRj5O3t/Yvn07RYkD/CuQ0ybiHJTtZkaSPO1VR/Hw8ECKSlJS
Un19PX5+CgsLsWeUfP2+EDQabfz48SjqBnl/4R1/7CvCYDCkTgT5/v37xMTEzMzMvLy82tra+vp6
ebnKkJ9ViucW/0vgvvhHV1VVpa5sQKPRLC0tkdCMI806BH5uBfpQWFiIGgMHDpRj6BEGy1ty8eSW
faKQfczJ+zPUc5104Hu9efNGwmSv2Cens+nfv//YsWNR9ouEhITnz5+PHTt21KhRFhYW1K591dXV
2Ph96dIlisxR5BKfNTU1HQ1tkrqHnxDkJ5+8DMm4BlFQX1+Pd2KlyLIjHfX19cnJyc+fP8/Kyiov
L6+trZVaLRGG/OaKc82QkC5zvAQ6BCgqnQKDwdDU1Ozdu7e5ubm9vb2VlRXFSjx+/Pg//viDIIjY
2FhcG6GpqQm7KIg0P+P3nNoYSd69zc7OlkRRITuVSe6fg8FrWLu7BDQaTV9fH8kf0uVL7STIHjUS
zv7kQcPbx1JHLcsOMpXV19c3NzenpKRgnQSbQgcPHtxJqRhdXV2RooJyf+F9efw8Ozk5URSuEUd+
fv6hQ4fIRnSFAj8nhoaG7e5TYZuffD0N8EMoSSlGKcC/GvlpJ6OsrCzgodHW1iZOq5F9opB9zMlb
qZLnoJMcXPuCx+NReLaQoQhbkjvr1q2j0WgowrCuru769evXr1+n0WhDhgwZOXKko6OjSNdQ8gBy
uVwJ4+uk+17S9fAzQMY1iALyD9EFVQ7b2tquXbt2+vTpznuwNTU1aTQa0jG68vUBugxQVGRFuIxu
R3FxcUGKCrJ2I/PAixcv0Cunrq4ucue3R48eaJtSYDdAAHL0mIS2OrKpo6O7unw+H8slkgijODRZ
nAtytyCFwRiH6JA/LuOeuCwwGAx3d3cUXPjw4UP8iGK/LxxfJHf69OljYWGRkZGBbocUFXKibSn8
vl69ehUYGIj35bW0tIYNG9a7d29VVVVk5q+qqrp06ZLcvkPHweEWkrhSYGleusKLcumDFOjr66Nk
weJk7qVLl+JcTwhyZXQycpkoZB9z8psul7KnAqDkuR2CPJN0Nj169PD39x8/fvylS5dSU1ORqMfn
89++ffv27dvIyMiBAwf+9NNPAvuf0u2nSfe9pOvhZ4CMa5CEV5bCYNQhWlpadu7cifb2if8l4hs4
cKCOjg6DwUDGhfv37+PcbtJBo9F69OiBZgPw3fosAUWl+zE0NBw6dCiKhEtISECKCjY/e3h4iHSv
1NTURO8ktQkBpeFD77CEib/Ikxd5714SaDSampoaEiYkmWqx2NGNMr0wZJfiy5cvd9RjAdfx7Ojo
yRc3NzekqDx+/LihoaFnz55sNhuFMXSo2KIUeHp6IkXl6dOnyDc9LS0NraPq6uodjUuuqan57bff
0NOur6+/atUqe3t7AdemwsLC7lVUsKOzJD86fmflKxxjeb2THrz+/fsjbbOmpobNZotMBighcpko
ZB9zrP8QMrjIU8BgMNBl58yZI1JhUwRsbGxsbGwqKipevHjx6tWr58+fYx/C9+/fBwYGTp8+feXK
lXjPijw9/vbbb5Kn7+uyHn4GyLgGUUB+/js7G++lS5ewljJ16lRygmlMbm6ujIpKW1sblm06w9wA
dDuQ9UshwOZtlPurtbUVv97iCodj7w5xFVQQ5HdYQjsrObZMio0OHJMgkJJIGD6fj10jROYu7C7I
LlvtfguKj8s36XBHGTZsGPJmaW5uRoHL2O/L2tq6k7yDEE5OTsipGuf+woq3m5tbR5XSO3fuIIcf
FRWVkJAQBweHzgjAkBEsSYhLO0MGP/bydb3AD14nOVKSvUxxxgipkX2ikH3MyaEO8t3dQuDe4rsr
LCwWy93dfdWqVSdPnjx79uyyZctw569fv06uUkIeNAn92bq4h58BMq5BFJDX904NiOLxeLhs0ZQp
U1avXt1Jnmbk6e6zCV4CyCjcev9lMnr0aCTYFRQU5OXlvX79Gq2a+vr64pI/YqHhzZs3FLZA8gKp
o6MjSWd0dXXxpooUaXOx0zCyqVNQXFyMzZzk8jLdDtlULFxipV1wbF9OTo7c+tRxlJSUsAKMKvng
ej6y5C2QBG1tbZynLi4urrm5GacqFqd4U4Cj8B0cHKhjprsRnHqosrKSWnrj8/m4UKN8g1nxg/fu
3bvOiArF9eaI/1t+RDpknyhkH/O+ffviNg7NlyP4cX358qXcfxGsrsvdW8zAwGD27Nl//PEH9hw+
d+4c7j/y20FtCYuXyx3qHn4GyLgGUcBgMPBjL+NWBjWZmZn4tZWlZGq7kKWUrsmYB3QxoKgoBFpa
Wg4ODqj9+PFjnOZ83Lhx4ozHuBhCfX099v4XhpxbnZztkQIlJSV88aSkJIozs7KyfP4H9g0dPnw4
apSUlGRlZVF8nFwPXmQptO4C1QJH7Tt37nT04zgz7Nu3bylMVk1NTb6+vmj02pXVpAOHpjx+/Lik
pARZwel0emdkYhUA60JPnz6Nj49HKxaLxZLih8a1RykMct0uo5DTAVNXXsvIyMAmUumqc4hjyJAh
qFFVVSV5rlLJ0dTUxAWdXr9+TX5/pUD2iUL2MdfT08MPlYxfRyT4XlVVVeJqiUgNNo1LGEVNprKy
EtcmEpd6TkdHZ/bs2fh8HENPp9Pxb5eQkNAZO1Ey9vAzQMY1iBps5UxKSuo8/2TyRhCFkZQ6yFYS
sKcA0YV5zICuBBQVRQFLAPfv38cRz+JK9hIEYWtri5fY06dPi3zb29racFkDExMTyX3Ksdk7Ozv7
5cuX4k6Li4t78eLFixcvPn78iDdhnJycsL0N140Whsvl4rrUlpaWnZSBSjrodDoO+M7IyMAbEcLw
+fxz584JbM2PHj0aeUu3trZS5O589uzZ8+fP0QAKiODiclZ2lMGDB6MSDTweb9++fUiad3BwkCKZ
G0JcQmdhRo0ahR4JPp9/+PBhdHDs2LFSeG1hKz6K5BYJfpa6CxMTE7z8X7hwgcJnMjIyEjUYDAZ1
9Y+OYm9vj9OYUkTs4AImUjBv3jx8i/3792MdUgpknyjkMuZYo37y5Ik4AzNKnUf9dUSCpwKCIE6c
OEEREpCTk3Pr1q0OXRwbj4WLmmPIMhwZBoPxzz//oCRaFPMbeaIg79vj1YrH4+GxFcn9+/els8LI
2MNPHRnXIGpwUYG6urrbt2+LO03cwyMh5JTK4hzUCwsLKb4a5sOHD+JWnMrKSvwVLCwsuiCPGdD1
gKKiKGDBLj8/H006/fr1oyjEQafT58+fj9pZWVknT54UPufChQvYVIktT5Lg4uKCk3WGhoaKTI/4
4sULLECQN3a1tLS+/vpr1E5MTLxw4YLwZ1taWnbv3o1dS7/77jvJ+9Y1zJ07F0sYe/fuFbn53tra
euzYsZMnT65YsYJ8Qu/evfFKcPbsWVxdi0x5efmBAwdQ29bWVkCHJEcTyejdPn78eNTABl1Zii1i
D2DqyCiCIBgMBlZ3sc2VQvGmAPsIpaWlCYdGtLa2RkREkIW8rsybRAYXyuBwOCEhISLFpvPnz2M9
YdasWVJrjCLR1tbGYx4fHy9SSc7KygoPD5f6FsbGxvhtraioWL9+PS6HIkx9fT2qZisSuUwUso/5
hAkT0JvO5/ODg4OF9wdaW1sPHTpE8TUp6N27N3a/zMrKCgsLE/lw5uTkbNy4MTQ09MCBA5JL2+bm
5qjBZrNxDBiZlJSUv/76S+RnVVVVcTLJqKgokW5vfD7//v37qK2urk4WAV1dXXv16oU/Ls4cExsb
GxwcvH79egppWBwy9hDB4XC6rC6N3JFlDaJm5MiROEYxIiJC5IbV3bt3cRVF6SCXNzl79qzwk5+T
kxMYGIi1d4on/+3bt6dOnRLWxltaWvbu3YstFJ3qYAZ0I6CoKApkwQ7RbgLZadOm4QiWCxcu7Nix
A+dCKSkp2b9/P9ZezM3NO5SOtkePHj4+PqhdXFy8cuXK2NhY7G9aUVERGRm5YcMGNPX0798fCxyI
RYsW4UkqIiIiODgYR2u0trY+e/ZszZo1OGhh3LhxdnZ2kvetazA2NsZZeurq6tatW3f27FnsB9/c
3PzkyRMfH58rV64QBFFRUSFgzV2+fDmSh5qbmzds2HD+/Hls8WpoaIiJiVmxYgWyRjOZzGXLlgnc
new6HxkZWVBQ0NLSUlFRIYXJUEA3YDKZOHpECsjhN9evX6+rq+PxeOLS/GOzK8LIyAj7JnUI8qMb
EBBw6tSp7Ozs6urq/Pz8W7duLVu2TEDG7a5U+qNGjZo8eTJqJyQkrFmz5tmzZ3h5zs3N3blzJ66w
bmxsPG/ePLn3YcmSJXhvc9++faGhoVlZWU1NTU1NTYWFhWfOnFm7dq0UnkJkvvvuO7wpwWazvby8
wsPDnz9/Xl1djZIOV1ZWvnjx4vTp099///2DBw/QmSwWS/jBk32ikH3M+/Xrh404eXl5y5cvj4mJ
qaysbGtrq66uTkpK8vHxQdnzpOOXX37BZojo6Oh169alpaXhF5nNZkdGRq5cuRLND0VFRZJf2c3N
DQuywcHBt27dqq2t5fP51dXV6enp4eHhgYGBFDPG4sWL0cd5PN7atWuvX7+OZfq2trbXr19v2bIF
u/5OmTKFbCCn0+kBAQH4yL59+3bv3o1/u7a2tqysrJCQkB07dvD5/JaWFumsLbL0EI3JvHnz5syZ
c/bsWSnu3u3IuAZRQKfTvb29UbuhoWHdunXnz5//8OFDa2trXV3dmzdvQkJCQkJCZO8/lk9SU1NX
r16dlJTEZrPLy8tfvXoVHh6+YsUKcn1G6twz586d27p169u3b3GK6vT0dB8fH7ztY2ZmJrDiAJ8N
kJ5YgXBzcyMbhts1PyspKQUFBfn6+iKXmNjY2NjYWCSmkLOJGxgYbNy4kZzuUBLs7Oy8vLyQ005Z
WdmOHTtoNBqLxeLz+WTB1NDQcMeOHQI5ARkMxrZt2wICApDiFBMTExMT07NnTw0NDQFpe+TIkWvW
rOlQx7qMWbNmlZeXo12j5ubmU6dOnTp1SlNTk06nV1ZWkq073t7etra25M/q6elt3bp106ZN9fX1
PB7vxIkTJ06c0NTUZDKZHA4HC1J0On3btm3CiQS0tbVtbW1R6FFWVtaSJUvQ8cjIyI7mhDUyMrK0
tMQxry4uLrIkcHRycsLbaMh9nCCIKVOmiPwRhw0bpqurizW0cePGSZc/1NbWduLEicgo29zcfPbs
WWHJg/wdP378KMVd5IKXl1d1dTWKdsjMzPTz86PT6SwWq7a2lvxKGhoabt++vTOqnejr6/v7+2/d
uhU9n7du3RJ2KDI0NJTFZUtJSWnTpk1hYWF3794lCILP59+8eZNalDc2Nt62bRsuuYiRy0Qh+5gv
Xrw4MzMThfOVlpYGBwcLnyP1oGlpaW3fvn3jxo1IxMzIyPD390c9rK6uJqeMNzExCQwMlHyiNjQ0
nDNnDvLxa2xsDA0NDQ0NFThHQ0NDnF5qbm7u7++PviyXy0Wvs46ODp1OLy8vJ89vQ4YMWbhwocDH
LSwsAgICgoOD0c8UHR0dHR3NZDLRb0c2n3t4eOBCxh1Clh4WFhaikvYEQZw+fXr27NnkVNSfCrKs
QdQ4OjrOnTsXPTx4hRI4R8aJgiCI1atXr1mzBlmOMjMzN2/eLHCCiopK//79kd9HTU1NXV0dOSkZ
RltbG73jCQkJIt8dLS0tPz8/BcwGCcgF+F0ViOHDh+OYM3Nzc3KtRnGwWKyQkBByTYyGhgby8mxt
bR0eHo636TvEzJkzt2zZgveI+Xw+h8Mhayljx449dOiQyES3hoaGYWFhZAtHQ0NDaWkpFj7odPrC
hQu3bdumsInPaTTa0qVL/f39yYGANTU1FRUVeIXQ19ffs2ePyB3noUOH7tu3D7tnoM+WlpbiJdzM
zOzQoUPW1tYi7758+XKRU7YUjBs3Drdl8fsiCMLS0nLKlCkSnqykpIQdzwhp/b4Qq1evnjlzpsh/
0Wi0WbNm7dmzByerpYiq6mwYDMbmzZsXL16Mn2pkTia/ki4uLgcOHJDk7ZaOMWPGbN26lZzelIy1
tfXu3btlvAWdTvf19Q0KCmo3CZu6uvrixYuPHDki7kzZJwrZx5zJZG7btk3c88lkMn19fWUx1vbv
3//gwYPYHRT3kCxpTZ069cCBA+J+NXH8+OOPFFvllpaWe/bsofj42LFjg4ODycOC8qeRJeCJEyfu
3r1bpJTv6uoaFhZG9k9ubGwsKyvDU5yKioq3t/eGDRukrnAidQ/JxceUlZU/URFWxjWImp9//nnx
4sUC21D4vjNnzly5cqXUPUcMGDBg9+7d4oxrffr02bt3L7nn4lKA2NjYbNmyBb0dwu+OiYlJSEiI
QoW5AvIFdlQUCGVl5XHjxiEjB1m4pIbFYv3666+vXr2KjY19+fJlaWkpjUbT09MbNmyYk5NTh6ws
wowZM2bkyJFxcXFPnjzJysqqqKhQUVHp3bu3tbW1h4cHTg8qEi0trYCAgDlz5jx8+DAtLY3NZnO5
XDU1NVNTU1tbWw8Pj04t5SEvxo0b5+TkFB8fj0eATqcbGBiYmJi4urqOHDmSQtHq37//vn37UlJS
EhMT09PTy8vLW1paevXqZWZm5ubmZmNjQ7F8mpiYHDx48Ny5c6mpqTU1NRoaGqamptIZBZ2cnA4e
PNja2qqlpSVOL5KcVatWDRo06M6dO7m5uTQarVevXhSRVHjrf8CAAbJkoKbT6V5eXp6ennfu3Hn2
7FlpaamSkpKhoeHIkSPHjx+PrvzDDz/k5uai85ubm0WWSe0ClJWVFy5cOGHChPj4+OTk5KKiosrK
SpQSdNiwYe7u7hIm35MFR0fHkydP3r1799GjR0VFRTwej8ViWVpaurm52dvbk11EOrrRSsbZ2Xn0
6NHPnj1LTk5++/ZtcXFxQ0ODqqqqjo4Oi8UyNze3sbExNzdv1xIh+0Qh+5irqalt3rw5LS3t3r17
6FVVVVXt27fvqFGjJkyYwGKxIiIi0JnSjRiLxQoKCsrKynr06FFaWlppaWltbS2LxTIwMBgxYoSb
mxvZ21NyVFRU/Pz8PD097969m56ezuFwevTogXLrjRkzxs7Ort2cTra2tn/88cfTp0+TkpIyMzPL
y8vr6+s1NDT69u07fPhwNzc3ExMTio+bmZkdPnz4yZMnSUlJaNyam5sNDAyMjIwcHR2dnZ1lr1Qo
XQ979er1008/Xbp0iclk/uc//1GogsIdRZY1iAIajbZw4UIXF5c7d+6kpKSw2WwajYYeSE9Pz4ED
B+K88MT/jYzvEEOGDImIiLh3715CQkJ2djaXy9XS0ho0aJCLi4u7u7uKioquru706dPRyRQ1qUeP
Hj1s2LB79+4lJSXl5eWhOsIDBgxwdXX18PD4pH9foF1oXZ/WE92xra2ttbW1qampsbGRx+MpbHkE
AACkZt++fSjQ9ueff/7mm2+6uzsAQRAEm83GfjIBAQHg2C0JYWFhqHSMoaEhdZ4rAPg8iImJwW6Q
Ungdy46XlxfyCnN3d9+4cWMX3x0gCKK4uJjBYDCZzB49euCdSak3SKXmk9wPBQBA8eHxeDgnD9nv
BeheyAmsul74+ETB9SLBwwT4QsApQxkMBs4CCgBdDygqAAB0CnFxcSiM0sLCAgoGdxnJycnPnz+n
OAGH1zOZTOnysH1moDBl6uyo2KtQRmdaAFAQLl++XF5eLu6/DQ0N0dHRqD18+PDu8qQFAAIUFQAA
OoOqqqpTp06hNqS37zLy8/N///33oKAgcVUd//33X5zQc+rUqbLEqHw2HDx48OzZszt37hSZ4LW2
thZn01JRUZExHQUAKAIxMTHHjh3bsGGDyIpYbW1tBw4cwDWFJE+gAgCdAaxSAADIh/r6+sbGxurq
6jdv3pw7dw7lYzUyMnJ1de3urn0pREVFoWxXAQEBkyZNmjJlyuDBg5WUlPh8fn5+/vXr1//55x90
pra29ty5c7u1swpBSUkJyrMcHx//7t27BQsWjBkzBuUXqqurS0lJOXnyJK72sGDBAih9DXzqtLW1
nTlzhiCI/Pz8X375Zf78+R4eHr169aLRaC0tLRkZGZGRkc+ePUMnW1tbOzo6dmt/gS8dCKYHAEA+
REdHC6S+pdFou3fvlj3VGCAhDQ0NAQEBuKQMQRDKysra2tpcLpecUYfJZAYHB+OcbF848fHx27dv
Jy+F6urqdDodlbDEB11cXAIDAz/RRLcAQKawsHDt2rW4gCZBEAwGQ01NraamhuwD2bdv37CwMG1t
7e7oIwTTdz8QTA8AwOcMqrYBWkpX0rNnz5CQkCVLlmCf8tbWVg6HQ9ZSBg0adPDgQdBSMC4uLocP
H7awsMBHuFxuVVUV1lJUVFQWL14MWgrw2WBsbHz8+HFynSsejydQZdXNze3AgQPdpaUAAAZcvwAA
kA96enr9+vUrKSnR0tKytbWdM2fOgAEDurtTXxwqKirz5s2bNGlSUlJSYmJiQUFBaWkpqlcwdOhQ
R0dHOzu7rjeJKTiDBg0KDw/PyMhISEhIT0//+PFjbW2tjo5Ov379RowYMW7cOMh6BHxm6Ojo+Pr6
zp8///HjxykpKR8+fOBwOOrq6r169bK2tnZzcxs4cGB39xEACAJcvwAAAAAAAAAAIAOuXwAAAAAA
AAAAAKIBRQUAAAAAAAAAAIUDFBUAAAAAAAAAABQOUFQAAAAAAAAAAFA4QFEBAAAAAAAAAEDhAEUF
AAAAAAAAAACFAxQVAAAAAAAAAAAUDlBUAAAAAAAAAABQOEBRAQAAAAAAAABA4QBFBQAAAAAAAAAA
hQMUFQAAAAAAAAAAFA5QVAAAAAAAAAAAPjWg0wAAIABJREFUUDhAUQEAAAAAAAAAQOEARQUAAAAA
AAAAAIUDFBUAAAAAAAAAABQOUFQAAAAAAAAAAFA4QFEBAAAAAAAAAEDhAEUFAAAAAAAAAACFAxQV
AAAAAAAAAAAUDlBUAAAAAAAAAABQOEBRAQAAAAAAAABA4aB3dwc+N2pqagoKClB78ODBDAaje/vz
OfHhwwcOh0MQhLKysrm5eXd3BwA+bV69enX37t2XL19yOBwlJSUjIyMfH5/Bgwd3d7++dGARAYAu
gM1ml5WVobaVlVX3dgagABQVOfPmzZtNmzahdkREhImJSff253Pi5s2bFy5cIAhCQ0Pj6tWr3d0d
APhUaWlp2b9//61bt8gHc3JyeDxed3UJwMAiAgBdQHR09OnTp3G7ezsDUACKCgAAwJfFH3/8IaCl
INTU1Lq+MwAAdDFlZWUpKSmpqamFhYUcDqexsVFTU9PQ0NDCwsLOzs7GxoZGo3V3HwHg/wGKCgAA
wBdEYWFhVFQUaqupqf3yyy+2trba2to1NTU6Ojrd2zcAADoVLpd77ty5q1evtrS0kI9zOBwOh5OR
kXH58mVjY+PVq1cPHz68uzoJAGRAUQEUAi6XO3PmTNT29vaePn169/YHUEAiIiKQ75+qqurff//d
3d35VImPj8ftwMBAOzs71NbX1++mHn1ZeHl5ZWVlEQTh4uKyefPm7u6OaJKTk7H72bFjx0xNTbu3
P4Bc+PDhw4YNG0pKSqhPKyws9PHx+fnnn7/55puu6RgAUACKCgAAwBfE27dvUcPY2BhrKQAAfN6U
lZWtWbOmoqIC/WlgYDBz5swRI0bo6ekxmUwul/v+/fuYmJiYmBh0wvHjx9XU1KZMmdJ9XQYAggBF
BQAA4IuiqqoKNfr169e9PQEAoGvg8/mhoaFYS/H09PT29u7Zsyc+gcVisVgsOzu7CRMmBAUFNTY2
EgRx5MgRW1vbXr16dU+nAYAgCKijAgAA8EXR1NSEGmQxBQCAz5j4+PjU1FTUHjNmjI+Pj7jX38bG
xtfXF7V5PB4k2AS6HVBUAAAAAAAAPluuXbuGGgwGY8WKFUpKVLKfi4sLrlR2+/ZtbNoAgG4BXL+o
aGtrS01Nffjw4evXrzkcTmtrq5aW1qBBg2xtbT08PNTV1SW5SFVVVUxMTEJCQnFxcW1trY6OjpmZ
mYeHx+jRo9vNAMjhcO7fv5+SkpKbm8vlclECQVtbW2dnZ5HRjWlpaf7+/qgtLgLy3bt3K1asIAhC
V1f33LlzIvtw8eLF48ePEwTBZDKvXr2qoqIicEJ2dnZMTMyrV69KSkoaGho0NDT69es3fPjwcePG
GRkZSTAq/w8cV0rmwIEDBw4cQO1du3aNGDFC3Mfz8/Pv3buXkpLCZrNbWlr09fWHDx8+efLkdovW
8fn81NTU2NjY9PT08vJyJpOJPuvs7Dx06FDJ+y/8RdavXz9x4sT6+vp79+49fvy4oKCgqqpKW1t7
wIABzs7OHh4ePXr0aPdqOTk50dHRaWlpJSUlNBqNxWKZmZk5ODg4OzsrKysLn0+OfL148aKWlta9
e/eio6NzcnJqamqmT5/u7e0t8JGKioqYmJjU1NTc3Nza2tr/j737jIvi2vsAPltglw5LUwRFUUGx
IQZQFEGU2GM0iSUmJvEmlkRTbZibaExi7yWaWBOMGmOJNVYUFQQUQYooUgxFl16Wsmx7XpzkZLJN
ZBfcPPf3feFnnJ2ZPTvMnDn/Oc3S0tLNzc3Pz2/YsGEeHh4tmsJz585xudzKysrLly9fv35d/33B
3pGqq6sbNmwYWfb19d2wYYPmN0okktjY2Pj4+Nzc3NLSUpVK5eDg4O3tHRQUNHDgwKdOoldRUXHh
woXY2NjCwsL6+npHR8du3bqFhoYGBgZyOJwFCxYkJSUxDDNz5swJEyYY6yw13bPmDOXl5RMnTlRb
efHixYsXL9L/Hjt2rCl52oULF1atWkWWDx06JBKJtG62bNky0mvfx8eH3s5qSktLL168mJSU9OjR
o+rqagsLC1dX1549ew4ePNjX1/epKSkvL79w4QL5E0ulUpFI1KFDh4CAgPDwcK0/hD1ix5IlS4KD
g5OTk0+ePHnv3r3S0lI3N7e9e/caN4UUHQeCLSYmhl7GU6dOnTZtmq7dm/0Qkcvlt27dio+Pz8jI
KC0tra+vt7W17dSpU9++fcPDw9UGeWOfH7YZM2bQ5VOnTj3rBJSPHz+OjY1NSEgoKioqKysTCATO
zs6+vr4hISF9+vR56kOQ5NXXrl3LyMgoLi5WKpX29vbdunULCgoKCQnRfDapMSSjM+QxUV9ff/Xq
1YSEhAcPHlRWVvJ4PHL7DxgwoH///ny+vqKXIftqlZ+fn5aWRpYjIiKaMmxGRETEvXv3SGJycnJ8
fHx0bZmdnR0dHZ2SklJQUEBuQ3d398DAwMGDB+vKHNQ8a26m6datW5cvXyYXuYWFhZubW1BQ0LBh
w5ycnNLS0j7++GOGYXg83u+//96Uo6kxemkBnhUCFZ3y8/NXrVpFO54SxcXFxcXFsbGxu3fv/uCD
D4YOHar/IFeuXNm4caNEIlE7QkxMTFBQUGRkpK7qV7lcfujQof3798tkMrqyvLy8vLz83r17UVFR
ERERs2bNUnse+/r6CgQCMmtbamqq1ps8Pj6eLJSVlT18+FBrmf7OnTtkISAgQO1JIJFItm3bpjY7
UkVFRUVFRUpKyk8//fTaa69Nmzbtqc8PAymVyr179x48eFClUtGV+fn5+fn5p06devPNN9944w1d
+xYUFKxZsyY9PZ2ukclkNTU1OTk5x44dCwgImD9/vp2dXfMSVltbe/v27VWrVtHWwAzDlJSUlJSU
JCQk/PLLL4sXL/by8tKz+44dO9TmuCgsLCwsLLx06VL79u0XLlyoPwyTSCQrV668ffu2rg2USuXh
w4f37dvHvrSqq6urq6szMzMPHjw4duzYd999V1dxxPAUNjY23rx5s3n3RVOoVKoTJ07s3buXfXyG
YR4/fvz48eMrV660adMmMjKSvjLUFBMTs379evbuRUVFRUVFly5d6t27d2RkZHV1tf40GH6WdGle
zmBqVCrV4cOH9+zZwx4jtaampqam5uHDh8eOHQsMDPzkk090FXRUKtXRo0f37NnDnqFSLBaLxeKE
hIS9e/fOmTNnyJAhehIgl8t379594MCBFkqhETX7IXL79u1t27bRSe4JMgptYmLivn373n///eHD
h7dcyiUSyY8//nj8+HF2Li2TySQSSW5u7qlTp/r27Tt//nxHR0ddR/jjjz9Wr16t9hQmf+grV67s
2bNn4cKFuuYUNzCjM+QxkZCQsHbtWvYjgGGYurq6goKCixcvenh4zJ8/X1fR35B9dSEhBxESEtKU
XQYNGkR/na5Ry6uqqrZu3RodHc1eSf46t2/f3rVr19SpU1977TU9tTeG52Y1NTWrV6+Oi4uja6RS
aWVlZUZGxs8//zx79mwDh1xv0dICNBFvyZIlz+WLVSqVSqVSKBRyuVyhUNja2j6XZOiSl5f3ySef
FBYW0jVCodDW1pb0MGMYRiaT3bhxQyAQqOWShYWFly9fJsscDueHH37QVW1aUFBQVVXVv39/zY+k
UulXX311+vRppVJJDyUSiWQyGV2TnZ0dHx/fv39/9hxtfD7//v37+fn5DMOYmZmFhoZqHnzbtm0V
FRVk2dHRUXOsdJlMtmnTJoVCwTDMK6+80rlzZ/pRXV3dwoULExIS2N9ob2/PTlh6enpubu6gQYP0
Vy4Tjx49sre3d3d3b9OmDR0z0dPT08fHx93dnbyYoUWBpKQkkl+Ym5vn5+frGaA2JSWlXbt2WuO0
9PT0Tz/9lH4XObFcLpdmlIWFhXFxcaGhoUKh8Knpp06fPk0eLRKJ5Ndff62trdW6WXV19dWrVwMD
A+3t7TU/LS8vnzdvXmJiIl1ja2trYWFBr7qqqqrLly/37t1b7ZUY+6p78ODB3bt32Z96e3sHBgaS
ZYVCsWLFiqNHj6pdWkqlkvzFGYa5f/9+ampqaGio5qs7o6RQKBRu2rSpifeFRCKpqKggF4NcLifF
NR6PFxgYSFZ26dLF39+f7q5UKjds2PDzzz/T4/P5/DZt2lhYWNA/ikQiiY6OfuGFF7SWkC5fvvzt
t9/qSh4pCpeVlZEicr9+/bp3726ss/RUzc4ZFArFo0ePyBkrKysjhW9y+7v/ZfDgwU15v5CTk3Pj
xg2y/Oqrr+oqJcfExDx69IhhGCcnp5EjR6p9umXLlgMHDqj9CpVKRaOCwsLC2NjYQYMGWVpaqu0r
l8tXrVp1+PBhesVaWFjY2to2NjaSAnFjY+P169ft7OzUynONjY20WqOkpEStgGVraztu3DijpFBT
cXGxSqUi57m8vJzkNiKRiJ7/Xr160fzKKA+Rc+fOLVu2rKqqih7H2dnZwcGhvr6e/Ci5XB4XFycS
ibp27Uq2USgUubm5JD1WVlZlZWVkfc+ePTt16kTWh4aGNrEysKqqKjIy8vr163SNUChs27Ytl8ul
N8Ljx48TEhLCw8O11jOTvPrJkyd0jaWlpbW1NY1Oa2trz58/7+XlpVk3YmBGZ8hjIjo6+quvvqqv
r6drbGxszM3N6R+xurr68uXLvr6+mp3UDdlXj9OnTz948IAsz549uym1+kKhsMNftMYJYrH4448/
Tk1NpWvMzMzs7e3pH1ehUNy5c6egoCAoKEjrNdPs3IySSCSRkZHJyclafwK5wouLi0tKShiG4XK5
U6dOZW9w9+7dlJQUsvzmm29qHqGFSgv/IjU1NXw+n8/n83g8LpdL6j9bfzJQDvtVR+sg30jyi8bG
xoaGBqlU2q5du1ZOhh4qlWrWrFnZ2dkMw/D5/Ndff33EiBGkTCORSC5durRz505yN3I4nE2bNrEf
h5otVfz9/SdOnOjl5WVtbV1WVnbt2rWdO3fSC33Pnj3u7u5qCVi3bh19F+vl5TV9+nQ/Pz8+n69S
qe7fv79///6bN2+ST729vdevX88uXpw6dWrjxo0Mw1haWh49elQtgxCLxex7tWPHjt9//73at6en
p3/00UdkOSoqytXVlX60Y8eOX3/9lSyHh4dPmjSpffv2XC63sbExKSlp27Ztjx8/Jp/OmDHjlVde
0XeW/6kp86ioNZ/gcDijRo0aNWqUu7s7n88vLCz87bffTp48ST51cXH56aef1IIlsVg8c+ZMUth1
dHR89913+/fvT8oZRUVFR44cOXHiBNly4MCBX375ZdPTr9aGrVu3bhMnTuzevbudnV11dfWdO3f2
7NlDT46Xl9eWLVvUno4ymezTTz8lr774fP4bb7wxfPhwEqRVVVVFR0fv3LmTPKFdXV23b9/Ofnho
XnXOzs5hYWHkb9emTZuAgACynv0WuUuXLtOnT+/duze9tPbu3UurYkaPHv3hhx+2XAqbcV80ZR6V
gwcP7tq1iyz37t176tSpvXr1IpdBdXX1yZMn9+3bR7IgLy+vbdu2qV0hhYWF7777Lk1GeHj4yy+/
7OnpyeFwyEvcQ4cOsd/iazb9MuQsPZUhOQM1Y8aMnJwchmGGDh1KW4o2neFNv2JjY+nN1a1bt7ff
frtHjx5mZmYqlSorK2v37t30IgwMDPz666/VjszOhYYNG/baa6916NCBw+FIpdJbt25t376dFG15
PN6mTZtoKZzR1rRJKBQOGTKkffv2QqFQpVKNHj3aKCnU76nzqBh+s9DmLgzDtGnTZtq0aYMGDSJV
B42NjTdu3Ni8eXNNTQ3DMAKBYM+ePZoBs+HzqCxcuJCepREjRrzyyit0lLnCwsJ9+/bRQHH8+PGz
Zs1S272kpGTmzJmk6pLP50+ePPnFF18kGZraU9jMzGznzp1ubm7s3Q3J6Ax5TJSUlLz99tvkBnd0
dHznnXcGDhxI9hWLxUeOHKFzrYpEol27drFvf0P21W/+/PmklYSLi8v+/fubuJceDQ0Nc+fOzc3N
Jf8dPHjwxIkTO3fuzOFwSGHghx9+oFV5L7/88uzZszUPYnhutn79+jNnzpBlkUj0zjvvvPDCC2Tu
2szMzF9++YUdR2k2/YqKitq3bx9ZVmskwrRkaeFfpLCwUCAQCIVCc3NzEqswzyNQQWd6LTIyMkiU
wjDMnDlzpk6dSt+8Wltbv/TSSytWrCB/KpVKRfuoaTV16tTly5f7+fnZ2tpyuVxnZ+fx48ezCwf0
3SR1+/ZtevcGBARs2rTphRdeIIVaDofj4+OzbNky2tz8/v37Bw8eZO9Oe3TU1dU9fPhQ7eC03ReR
m5urOfcTbczq6enJjlKkUumpU6fIcnh4+MKFCz09PcmFa25uHhQUtHHjRrr94cOH6UuRlmBmZrZs
2bIPP/ywc+fOQqGQz+d36NBh7ty5NMIpLi5m13cTmzZtIvlO27Ztt23bFh4eTt+Gurm5zZkzh7bG
vn79Oru295lERESsW7cuODjYwcGBy+Xa29uHhYV99913NKDNzs7WzBaPHTtGS7erVq2aMmUKLQLa
2dmNGzdu5cqV5DIQi8WnT5/Wk4BJkyb99NNP77777tixY8eOHUujlLy8PHq1BAQEbNiwwd/fn31p
ffvtt7TR/KlTp/Ly8loohc24L5pCKpX+/PPP9AeuWrWqT58+NBSxtbV9/fXXp0+fTv6bnZ2teYV8
//33tPw3a9ashQsXent7CwQCc3NzDw+PN954Y8OGDfqrf414ltQYmDOYDvqAb9u27erVq/38/EgR
hMPhdO3a9ZtvvhkwYADZID4+ntQPU2TmbLL83nvvzZ8/n4SRDMMIBILg4ODNmzeTXEihUOzZs0dP
Mvz9/Q8cOPDxxx9PmDBh1KhRNEoxMIVG14ybhd4Fjo6OmzdvHjp0KG3gZG5uHhYW9tVXX5H/SqVS
WntjRBkZGTQSmD59+ieffMIeC7tdu3YLFy6k+dKZM2fYwT/xww8/kCiFx+N9/fXXb775Jn24kKfw
unXryGtsmUym9oc2MKMz5DFx+fJl8ls4HM7KlSsjIiLovq6urrNnz37vvffIf8vLy69du2asffWj
TVWN1Ujp4MGDNEqZNm3a559/3qVLF3IbksLA1q1b+/TpQzY4duyYZqWH4blZVlYWjVLatWv33Xff
vfjii6TGw97ePigoaPXq1WPGjGn2b2yd0gI0BQIVLUiLBUJrg07SEZAs66p2ZBgmNDR02rRpmtFn
SEgIfYOl1vqWYZiffvqJLNjb2y9cuFBrLe306dNpL64jR47U1dXRj9zc3OjbNfbrBCI2NpYsBAUF
kQV2Oy6CdlBRa1EgFotpra7W9t8ODg40ZykvL2dX2Rvd7NmzaXMmNvYbU7U4LSMjg/7YBQsWaH0T
PGHCBPrusHkd70i8pNmWwMrK6vPPP6fFBbUSakNDA33/99Zbb2ntoufr60vDsN9++01XXWhYWNj0
6dO1VrUfPXqU7GVpafnpp59qXlpcLveDDz6gD7OrV6+2RAqbd180RXFxcYcOHXx8fHx8fCZOnKi1
8eGoUaPoV6sFKmKxmLZ1DggIGD9+vObunTt3pmN3ajLiWdJkYM5gOmjdY0hIiGYPAR6P99Zbb9H/
qv2NoqKiyEK/fv1effVVzYPb29vT1/O3bt3SNQm3q6vr0qVLdb2TNiSFxtW8m6WxsZHcBa+99prW
VqY9evSg7000HxOGKykp8fkLOwKkuFwubWjX0NBAS71EUVERrW+ZOHEiu20n1aVLFzr8wPXr19l9
eAzJ6Ax8TJC6SoZhOnfu3KFDB819x48fT7+XvhM0fF/96MkxSte1mpoa+rLA39//9ddf19xGKBRG
RkbSr9PsDGZ4bkajFEbHX4rH482ePftZ+/MQrVNagCZCZ3ot2DWMtbW1Wu/tKVOmDB48mGEYPT0x
NIfZIchrOdJusrS0lP1Rfn4+Dc1feeUVGxsbXUd45513SOV+bW1tbGwsu1t///79Dx8+zDBMUlIS
u/2VRCIhYVWnTp1ee+01Uq9648YNdsvsxsZG2sNB7fHALnzr6oMRHBxMn4u6Em84KysrzVbvRLt2
7ehwArSNNUErMXx9fXWN2MPhcIYOHUqaw5FhnZ5Vp06ddPXOdHV1HT58OGmzdP/+/dLSUicnJ/JR
XFwceZbw+Xw9MwGHhoaSUe1LSkqePHmidYA1raU3hmFkMhl9dUrePGndzNLScvDgweSNMrsAZMQU
NuO+aCIPDw9dA0xR1tbWNjY25BWj2hWSkJBAwwZdiWQYplevXro+MuJZUmOUnMFE0BtEVzbi4eHx
xRdfkGVPT0+6XiwW054/elqWBgQECIVC8lYlIyNDrVEQMWHCBD2jVzU7hUbXvJtlzZo1Tz2ym5sb
ucHJQYxr8ODB5PmoB7u6nnabJGjPFg6Ho7UZMP2WHTt2MAwjl8sfPXpEcnUDMzoDHxO0wK02kgfF
4/EWL15MPlXr523IvvqxO+w1fS9drl+/TmvA3njjDV0NgciLS9IQNykp6fHjxzSjMzw3U6lUV65c
Ict9+vTRNTIKn8/38/Nrxmuv1iktQBMhUNGCPRrPd99999lnn2nGKp06dXpqs109PVNpzzC1ByGt
zWAYJjg4WM/BfX19XVxciouLGYZJTU1lF0f8/f1JoHL37t3Gxkaa/SUlJZF+hIMGDerevbuNjU1N
TU1KSkpVVRV9T/PgwQPS9EUoFKr1EnZxcRGJRKTL+L59+7p06aLZi0AkEg0aNEhPso2Cy+Xqig85
HA7tban2AoY2e6NNDrSixY7i4mL2mTGKgQMH0s4VOTk5NFCh2VyPHj30vPRiN5/Izc3VWsDV1VEy
OzubPl369eunJ5Hjxo0jtfbsXsJGTGEz7gvjotVNtFstQZ9nlpaWuoYS0s+IZ0mNUXIGE9GjRw/y
vvzcuXMDBgx44YUX1Dbg8/lasxH6DoXH4+n5A5mZmXl6epK/ZnZ2ttYzoL8/cbNTaHQtd7PQLJQ9
rFlrYhdw1dJAuzh37dpVz5hgzs7OX375JXm54OLiQlYamNEZ+Jjw9vYmL9cfP378888/T5o0SfNR
5efnp/WYhuxroG3bttEOMJo++ugj9msXOnGko6Oj5lAibCEhIbTHYEZGBs3oDM/NioqKaDhH22Ea
kSmUFoBCoKKFp6dneHj4pUuXGIa5ceNGcnJyeHh4YGBg9+7djTXoJ82A1Dpy0MaylpaW+gcY4HA4
vr6+5AamA3oQpN+nTCaTSqUPHjygT3R2sxYejzdo0KAzZ86QMcLDw8PJR7QZgObAxHw+/6233lq3
bh3DMIWFhf/5z3+Cg4ODg4N79OhBHxKmgJ5bdqOaqqoq+uLw8OHDtLONJvYAO9XV1cbNejp27EiX
ad96hvUXvHfv3pQpU5pyKDqeTxOxh7DT2q6A8vDw0BxFpxVSyOi+L5qhpKQkNjY2PT09Ozu7srKy
trZWLSzRRDsbeHl5NWXMOk0td5aMkjOYiEmTJsXGxkqlUplMFhkZ6evrGxYW1rt3bzIyh54dadsY
pVL59ttv69mSvqFXe1Xf0ilsTU25Werq6uLj45OTk7OyskpLS2tqalo/LMnOzo6Li7t//35eXl5N
TU1dXd1TmzvSq5095qRWAwcOVFtjSEZn+GNi6NChR44cKSgoYBhmz549Z8+ejYiI6Nu3b5cuXZ46
1pYh++pHK1LYowA3G21T3b17d/39qtu2bWtra0uqr3Nycmgxw/DcjP30ZD9VjcJESgtAIVDR7pNP
PuFwOGQ2tNra2hMnTpw4cYLD4Xh7e/fr169///7swWSMiI6e7urq+tShFej7eLWHsUAg6NevHwlL
7t69SwIVMlQfwzAikYhUGfXv35+08rxx4wbNQWiXG82XiAzDjBgxoqGh4fvvvyeDSsfExJCBfdzc
3AICAl544QV/f38DZ7JrIexTJJFIdNWtqzF6E39bW1sO58+h9tgHJxkxwzBSqbSJLTGeNW3sqT+a
EW+3QgqNpaamZs+ePadOnXrWIQ3JOEgMwzzrqMFUy50lo+QMJqJTp05ff/318uXLyY9KT08n7UBs
bW1JHjJgwACto5HSpnoqlaqJp7d5tQ3NTqHpUCqVx48f37dv33Psp/To0aOtW7eyX583Eb1umzFv
gSEZneGPCaFQuGLFimXLlt2/f59hmCdPnvz4448//vijmZmZn5+fv79/cHAwu80bmyH76kfHEKdZ
nBoej6fWElKpVOqKauit99QXlGRQbPIXqayspOsNz83Y97XR5zIykdICUAhUtDM3N1+wYEFERMTh
w4dv3bpFSjwqlSozMzMzMzMqKsrLy+udd97RXy3YDLTOuilj89OcRXP6uYCAABKW3Llzh7zZTUtL
I/f2oEGDSNbg5+dHunMkJCRIpVKyTBtX6Kpifvnll1944YVffvmFDlHCMExRUdHx48ePHz/u6Og4
ceLEMWPGGKUtrBE1703SU9/BPysOh2Nubk7OG3uwfDpKQdM9a9rYb1Kb8X6uFVJoFGVlZfPnz6cj
YwoEgp49e3p4eNja2tJf/dNPP2n9Oc9092nVcmfJWDmDiejTp8+uXbuOHj1KJyBiGKa6uvrSpUuX
Ll0SCAQjR45844031Bqva44N9VTNvgibl0ITIZfLly9fTt4iMX8No+Tl5eXg4CAQCEj+f/nyZTq4
ZUtITU1dvHgxzeXs7Ox69erl5uZmaWlJng6VlZWkibImml03I6cyJKMzymPC1dV106ZN586dO378
OK0DlMlkCQkJCQkJ27dvDwoK+s9//sNu/2mUffVwdnYmWaKu8H7GjBl0DCsiJydHbQ2hUqnoWWrK
tLx0ghF2aGF4bsb+S+npbNY8JlJaAMq0SpOmxs/Pz8/Pr7y8PCUlJTU1NTk5mTYOyc7OXrx48dix
Yz/44AMjjipN39LpmuGLjUbwmjcqHaQ4LS2toaFBKBTSNpd0sCyBQBAYGBgTEyOVSpOTkwMDAx88
eEByebWBidW4u7t/8skns2fPvnvlctxqAAAgAElEQVT3bmpq6t27d+/fv0/u0rKysm3btkVHR3/7
7bcmNTc2O3D66quvtE6R1gqUSiXNo9l/NYFAQM78K6+8ovXxYDj2Q0UmkzVlaj+2Vkih4VQq1erV
q8kjmc/nv/feeyNGjNCciuvXX3/VGlHQp2ZT7j6tWu4sGStnMB3W1tZvvvnm1KlTMzMzaU5C/i5S
qfTYsWPR0dErV65kdwWkF22nTp1IL2pTS6GJOHz4MI1SRo8ezR5hn8rNzW25QKW6uppOXOjs7Dx3
7tyAgAC1VnP5+fm6AhVra2vyGrsZd6IhGZ2xHhNcLnfEiBEjRozIz89PTk5OS0tLTk4m4a5KpYqL
i0tMTPzss89oQwZj7auLp6cnGS26urpaLBY3r1qG4HA4VlZWJOpoSoGexifsoNHw3Iydqxu9NaOJ
lBaAQqDydCKRKCwsLCwsjGGY4uLia9euHTx4kNRjnjhxwt3dXW0SMUPQNo5NGfWItjPRfAi5ubm1
a9eusLBQLpffu3fPz8+PDLsuEAjYYxYFBweT51lcXFxgYCDtoNKUO1MoFAYEBJA6JYlEkpiYeOjQ
IfLku3fv3po1a5YsWfLUg7QatXm1nlcy2NXf7CTZ29uTDJ3+TY2O/XW1tbXPWmnQCik0XGZmJp29
Yd68eVoH0daDtjNh/5meScudJWPlDKaGy+V27969e/fukyZNksvlqampv/32G5kYpLKyctGiRXv3
7qVFT3oSyETvrTPv2DOl0BRIpVI66cSoUaPUZjNsHefOnSM3kZmZ2erVq591QmdbW1sSqDSx1Q2b
IRmd0R8TpBvMmDFjVCpVTk7OhQsXfvvtN7lcLpfLV65c6eHhoacNuSH7qunevfuRI0fIckpKSkRE
hCE/iuZyaqMmalKpVDQvYg+TbXhuxv5LVVdXG3fGcBMpLQBlKv0C/y1cXFwmTJjw/fff0yEvDxw4
8KxN4fWgL+cqKir03yEqlYqO3+/l5aW5AQ027t69m5ubKxaLGYYJCgpiv5bo168fedhfv35dqVTS
xsRax63Xw9raOiwsbOvWrXR6mRs3btDmN6aAtHkgy89xbib2FD3ssZ5oPnv37l0jXk5s7Ky8GX+a
Vkih4eigW9bW1qGhoc+6O+2U+eDBg+b9xpY7S0bMGQzEfi9u3EldyViiS5YsoROhlJeX00FIGdYt
I5FIWnqaxeal0BTcv3+fvoQ2ZMI7Q9A5KIKCgppRiKR3Im3+1HSGZHQt95jgcDheXl4zZ85cu3Yt
eWGvUqnIGOUtui/Rp08fWkvAnn6keWiAlJGRoX/LwsJCeimyR/E2PDdjjziqNl+n4UyktAAUAhV1
FRUVm/+ia8wcBweHCRMm0O2N2GOVPeYmHUteq4yMDPo+Q2t/Ejoy4+3bt+ljQ62qxNbWljQSq6qq
unPnDplDSnNgYmLXrl3ktNCpuNTweDz23E9Gzz4Mwefze/fuTZZv3LjxvNru0wZ4zD+zXfoXrKys
bKER2Tt27EgzX/1f8fvvv3/22WefffbZhg0bWjOFhqPv5xwcHPSMzqSreO3t7U0WKisrSX/WZ9Vy
Z8mIOYOB2K+om/HC+/z58yQb+fHHH3VtM27cONr3g11UZZ+ElphP3fAUmgL2e249s20YN8hUQ96L
MXrr9PRE8vQPnZmZqWdYvMbGxnnz5pHMihaaDcnoDHxMpKen08KDrluje/fudDhddgHDkH2fytbW
llYvp6enk/rAZqOnqKioiE6NqhX7i9iz3xqemzk5OdFLy8Cfo8lESgtAIVBRJxAITp48SYb5Is2l
tGL3oTRiE8kOHTrQIOHQoUN6hqyhMzQLBAKtI5GTQYoZhsnMzDx//jzDMBwOR3NceTq8486dO8kP
0RyYmEhJSSGnhVYia2KPhNPsvmUt9MKe5tRSqZSePa0uX7781HdFujx+/FhXCaCiooLOX9u9e3f2
I3zAgAG0HcuuXbv0tP3Nyck5e/ZsMxLG5/PpGTh79qyuzFelUp06dSolJYVOZdBqKXwqmgBdlxZ9
a1hcXKyr4/XFixd1FX3IsN1kWVfreYY1jYCmljtLRswZDEQH4WFYA5WqqaqqUrt+qMLCQpKNHDhw
QNdFyOVyaU7Czl27du1Kq7KPHj3KHqJUjUQiiYqKal6nWENS2BRGHINbK/a4i0VFRVq3yc/P1/N0
Y/45yUkz0knvRD11GnR2c030PlIoFHoGh71z505ycjLJrGh2amBGZ8hjor6+/sRf9DxBaBNT9pVj
yL5NMWnSJHphbNq0iUaSzTBw4EAaCtIJ5jVJJBL6J/b19WWPBG2U3Iz20klISNDV20omk9EpYp9J
65QWoIkQqKiztLSkPdGPHTumtVpApVLR93nW1tbGbQhOp18oKytbvXq11vzo4MGDtLQ0fvx4rSPP
CAQC0oJLpVKRp0WvXr00x/mmA5fRMofWgYkZ1sRM9+/fp/O2qmE//DTn4tDDwsKCPhqfPHnS9B2b
bvDgwW3atCHLx44d0/X8i46OXrFixaeffkqDimeSmZm5d+9ezVhLLpevXbuW5shqTTLc3NyGDRtG
lrOystavX6+1LJ6TkxMZGblu3brNmzc3IzweN24cOck1NTXr16/XdWnRygSapFZLoX60aCiVSrUG
G7RFgVQq1VoMunr1KruaSC2F9vb2tMFYTEyM1iskKyuLfQQ1LXqWjJUzGMjT05MWU44ePaqZjLq6
ujVr1uiJBsmCXC7fuXOn1rcSmZmZNBNgtxjhcrm0zra+vn7p0qVaexNVVVUtXbp037598+fPpwN2
NZ0hKWwK2gJeVxRhIPa0Evv379e8AnNychYvXkyjOK0XErverBkdrmjroKSkJM2QVaFQ7Ny5kx2o
qyXSzc2Nzqe5f/9+UtWvprS0dPPmzWTZ39+f3UHckIzOkMeEr68vPW+7du3SWv6WSCSxsbFkmV2p
bsi+TeHh4UHvnfLy8k8//VTXWwaGYerq6g4cOKDrUzs7u3HjxpHluLi4Q4cOaW4jl8tXrVpFb092
UwvC8NzsxRdfJH9llUq1YsUKzYhUoVBs3bpVz8/Uo3VKC9BEvOfV41mlUqlUKoVCQWbkaMZw6S2n
Xbt25LJTKBTR0dGWlpZt2rQho0wolcqMjIytW7fSyRNffvlldjVFYWEhjWHGjh3L7kDGFhcXR+4f
W1tbes8T7u7uZWVlpEY1Pz//1q1bbdu2dXFxIe/hcnNzt2/fTtunenh4zJ8/X9fAJrW1tey2RhMm
TOjWrZvaNlZWVgkJCezWAu+//77WAbs8PT0vXrxIBnKJjY2tr69v27YtyTtUKlVRUdHBgwfp+xVv
b++pU6dqTZVWXC73+vXrpBHdH3/84ePj4+Dg0NDQ0NjYSEcLSUpKIg1GBQLBxIkTdR3qyJEjpF2s
t7c3HeKMfIWPj8+FCxdIySM+Pv7Jkydt27YlrSOUSuXDhw937969d+9e8t/OnTvT+t+nYo9hmpaW
lpOT06ZNG0dHRzJrSnp6+ooVK2gXIB8fn9mzZ6t1Be7Ro8fVq1fJ8yknJycpKcnV1dXZ2Zn83cVi
8fHjx1euXElaBVhZWYWHh9NXs0286hwcHEhvYHKSk5OT3dzcnJycyHHy8vLYl9aIESNeeumlVk6h
nvuCYZjq6mraH6C6utrHx8fMzKy0tJQGMC4uLqdOnSIlMDJGn0gk4vP5FRUVaWlp27dvP3DgALtI
5O7urja/uLe395kzZ8hTMz4+vrS01MnJycbGRqFQFBUVnThxYu3atezx8vv166fWTtKQs6SfsXKG
U6dOkRutU6dOmvPlPRWPxysuLibJKC8vz8rK8vT0tLOzk8lkpaWlV65cWbt2LfsVo5OT08iRI+l/
XVxcsrKyyKx2Dx8+zMrKcnNzE4lE5Haoqqo6d+7c2rVryXBAQqHwww8/ZHdV79SpU3Z2NumgUlFR
ceXKFTs7uzZt2pBfKpFILl26tHz5cvKGVS6Xjxgxgj3EEC1UBQUF6eqLbGAKnyo7O5ucn4qKCnt7
e3d3d5VKVV1dTQ9i4M1iZ2eXlJREmv4XFRUlJiaKRCIzM7OGhobs7OwDBw5s2rSJXarjcDia2am5
uTmtVCwsLOzZs6eVlVVlZaWZmVlTLlcLCwsyCxnDMNHR0TKZzNramsfjicXiuLi41atXqzXX6dev
H5ndi/L19T1//nxjY6NSqbxy5QqXy23bti0pytfX18fExCxbtow09RQKhV988QX7LBmS0RnymDAz
MzMzMyPjeVRUVMTGxrq4uLi4uJD6JalUSn47rQmcMWMG7VFjyL5N1LNnz9zcXHLv1NbWnjlzpqys
TCgUWlhYkOEKq6urHzx4cO7cuZUrV9IoTiQSvffee2pjEvj6+sbFxZE4JCkpqaioyM3NjZwihUKR
kpKyfPlyOifb0KFDX3vtNbXEGJ6b2dnZ1dXVkVupsrLyypUr9vb2pHtJdXV1cnLy+vXr2ZcZl8tV
K5PcvXuXRtFvvvkm+6MWLS38i9TU1PD5fD6fz+PxuFwuyQNbZxQTNk7r94sl36hUKhUKRWNjY0ND
g1QqNe6gDYa7dOnSihUr2GscHBz4fH5paSn7jHl7e69Zs4Y9Ul58fPznn39Olnfu3KlrZty1a9eS
WKhdu3bkWmeTSqXLly9n32N8Pl8kEtXU1LAn33B1dV21ahVtC6GpsLDwrbfeov/ds2cPuwsadejQ
oZ07d5JlT0/PH374QdcBc3NzP/nkE3YLWmtraysrq/LycnYrC1tb23Xr1umfFVh/MqhFixbRStid
O3eScoaNjY2eroRTpkwhD+mxY8fOmTNH7dOrV6+uWLGC/f5GKBTa2NiUl5ezi7BDhgxZuHBh02/I
2bNnkzzX3t6+qqqKXCTkr1ZVVcVuhmRnZ7d+/Xqt1U15eXmRkZHszoVaj9ChQ4d169axY/smXnUM
w5ARY9jdf8lX1NXVsf+sAQEBS5cu1ZwMp6VTqP++qKurmzJlitq7RldXV3bV/IULF1atWqXr55Pt
lUol+Qk+Pj70pSx148aNpUuX6skYXV1dacOJmTNn0u5qVLPP0lMZJWeYMWMG6VYxdOjQBQsWNP3b
KbFYPGPGDP1zKdrY2JDZ5TRPskQimT9/Prt1u0AgsLe3J9OW05UcDicyMlJzUASJRLJ06VJaDCJb
Ojg4yGQy9nx2lpaWK1eu9PHxYe9IR2j86KOPRo0apSvxBqZQv/T09I8++kht5ahRo+hKw2+W3Nzc
jz76SM8MdGZmZp6envQHHj9+XHP+yoULF9Ix9KioqKgmDm5Lk6eLr68v7ak8efLkd955R22D1NTU
zz//nP0rbG1thUJhWVkZzav5fP7y5cv79Omjtq+BGV2zHxMqlWrjxo2nT5+ma3g8nkgkkslkarV/
mo8nQ/ZtIrlcvn79etIUvCk8PDyWLVumtXgmFosXLVrEHtPCwsKCnCL2eevXr9+SJUu0jpNueG7W
0NAQGRlJRyvVimbXPB5P7YKMiorat28fWdbaSKSFSgv/IoWFhQKBQCgUmpubk1iFeR6BCpp+aRce
Hr5ixQr2vUGGp2AXX4YPH75q1SrNWRoMJxAI/vvf/06bNo3e3nK5vLi4mH33hoSEbN68WU+UwjBM
u3bt6AYeHh5aoxSGNbMK87SBiTt27Lh582b2mGASiUQsFrOjFF9f3w0bNjxrlMIwzEsvvdQKMxIM
Hjx4/fr1nTt3pmsaGhpKSkpovmNmZjZnzpxm5ztkUCBS+iR/NbWy6erVq3U1ivP09NyyZQv7Hb/m
EUaPHr158+Zm10Dy+fxFixa9/fbbapcWfXjz+fx33nlH68O7dVKoh6Wl5dy5c/VvM2zYsHnz5uma
P8Tf33/Tpk10hO6srCzNwlxwcPDSpUt1pb9Pnz76AyGmJc+SsXIGA7m6un799de62pUJBIK5c+eO
GDFC1+7W1tarVq166aWX6C0mlUrFYjH7b+Hi4vLNN99ojQGsra2XL18+efJkeomqVKry8nJ2lNKj
R48dO3awo5RnYmAK9fP19dUTIxlFx44dV61apSuiaNeu3dq1a9mtT7UOHTFr1izN6KXpPvzwQ10D
93M4nPHjx69Zs4Y2RaYTDbP17Nlz48aN7FYA1dXVxcXFNK/28fHZunWrZpTCGJzRNfsxweFw5s6d
+8EHH9AqCIVCUVJSwo40BALBjBkzPvjgA83T0ux9m4jP58+bN++LL7546qtha2vradOmfffdd7q2
dHV1Xb9+PXsI+Pr6+uLiYlqs5/P5U6dOXbZsma7c2PDcTCgULlu2jI41qvlpMwapZ2vp0gI0EeZR
0cnf3//777+/ffv2zZs379+/X1paWldXZ2Nj4+7u3rt379DQ0GaUxZuOx+NNnTr1xRdfjImJiY+P
LygoqKioEAgE7u7uvXr1CgsLU6so12XAgAGksb5aExc2T09PMukK04SBid3d3ZcvX56enn7z5s2U
lJSSkpKqqiqhUNi2bdtu3boNGjSod+/ezbtphULh2rVrf/nll5iYGLFYLBQKPTw8DJmaShcfH59t
27YlJCTcvHkzLS2ttLRUJpO5uLi0bdu2f//+gwYN0uzJ80wGDBjQq1evixcv3rx5My8vr6qqys7O
rmPHjoMHDx4yZIj+yZJFItEXX3yRlZV1/fr1pKSk4uLimpoakUjk4uLSt2/f0NBQXdFm03G53ClT
pkRERFy5ciUxMZFcWvb29m5ubv379x88eDC7t/RzSaEeQ4YMsbe3//XXX+/du9fQ0ODo6KjZpSoi
IqJv376///57QkJCfn6+VCp1cnLq2bNnWFgYaaU5fPhwWgIrLS3VnOa5f//+u3fvPn/+/PXr1wsK
CqRSqUgk8vX1DQ0NDQgIYNckaC3lMC15loyVMxioR48e+/btO3369M2bN//444/6+npbW9v27dv3
69dv2LBhIpGIvqrUytra+oMPPhg3blxsbGxiYuKTJ0/Kysr4fL6joyNpsTlgwAA9s1WSUuaYMWOu
Xr1669at/Pz8iooKa2trV1dXb2/v0NBQX19fA4sOBqZQv7lz53bu3PncuXO5ubkcDqdNmzbswpBR
eHt779y58+LFizdu3Hj48KFEIrGzs+vcuXNISEhYWJiZmZmjo+PYsWPJxlpHnujQocOWLVsOHDhw
69at6upqGxubTp06Nf3FHJ/Pnz179rBhw86dO3fnzp3i4mIul+vq6tqvX7+IiAjSseett97Kzc0l
22udnNHT03Pjxo2JiYlxcXEkr5bL5W3atPHx8QkNDfXz89PTDs3AjK7Zjwkul/vSSy+FhobGxcWR
u4NUAdna2np5efXt23fw4MEikcjo+zbdoEGDBgwYcOfOnfj4+MzMzMLCwvr6ektLSwcHB5FI1K1b
Nz8/v27duj318razs1u0aNErr7xy7dq1pKQksVgskUisrKw6derk7+8/ZMgQZ2dn/UcwPDezsrL6
73//m5SUdPHiRfJnsrS0dHd3DwwMfPHFF0UiEW2moSuv1q+lSwvQFGj6BWAEtOlXWFhYZGTk804O
tCCxWEzbOrObJgIAgElZv349mTpGrZEwNAWafgEA/Puwh5FpiRo/AAAwCjpf5DMNQwomBYEKAMDf
4uPj2R21NdFhVYVCIZ0jEgAAWpNMJtu7d6+eEd4zMzNp28KnNmsHk4VABQDgT48ePfrmm2+++OIL
XbM6njlzhg75PXr06Oa1ewYAAANt2bJl//79y5cv1zoCYU1Nzbp168iymZlZWFhY66YOjAZPWQCA
Px07doyMObNo0aIRI0aMGjWqS5cuXC5XpVI9evToxIkTJ0+eJFva29u/+uqrzzWxAAD/o4qKisg4
yzExMQ8ePJgyZUpwcDAZR7G2tjYxMXH37t102pkpU6YYd2JuaE0IVAAA/jRjxoy8vDwyvcPZs2fP
nj3L4/Hs7e0lEgl7ZCShULhkyRLDh98BAIBmcHNzW7Ro0ddff61SqZ48ebJu3bp169ZZW1vz+Xw6
lRkREhIyZcqU55hUMBCafgEA/MnCwmL16tXTp0+nI6UqFIqysjJ2lNK5c+ctW7b4+vo+pzQCAAAT
EhKybdu27t270zUSiaSyspJGKWZmZtOmTVu8eLGeYazB9KFGBQDgb2ZmZpMmTRoxYsTNmzfj4uL+
+OOP4uJiMu9Ez549+/fv/8ILL2B6LwCA565z584bNmzIyMi4ceNGWlrakydPampqHBwc2rdv37dv
36FDh6Le+/8BzKMCAAAAAAB/wzwqAAAAAAAA2iFQAQAAAAAAk4NABQAAAAAATA4CFQAAAAAAMDkI
VAAAAAAAwOQgUAEAAAAAAJODQAUAAAAAAEwOAhUAAAAAADA5CFQAAAAAAMDkIFABAAAAAACTg0AF
AAAAAABMDgIVAAAAAAAwOQhUAAAAAADA5CBQAQAAAAAAk4NABQAAAAAATA4CFQAAAAAAMDkIVAAA
AAAAwOQgUAEAAAAAAJODQAUAAAAAAEwOAhUAAAAAADA5CFQAAAAAAMDkIFABAAAAAACTg0AFAAAA
AABMDv95JwBMzoEDB3bv3k2Wo6KiXF1d2Z/KZLKRI0fq2d3MzMze3t7Z2blHjx7+/v5+fn4cDqcF
k/uXhoaGu3fv3rp16+HDhxUVFWVlZcOGDZszZ04rfDUAAAAAGB0CFTAymUxWUlJSUlKSkZHxyy+/
eHp6fvjhhz169Gi5b5RKpcePH4+KimpoaGi5bwEAAACA1oSmX9Cy8vLyPvnkk1OnTrXc8adPn75z
5061KIXD4fB4vBb6UgAAAABoaahRgeYbNWrUrFmz1FYqFAqJRJKdnX369On4+HiGYVQq1aZNm5yd
nQMDA42bgIcPHy5YsKC6upr8t23btmPHju3Ro4e7u7ulpSWXizgcAAAA4N8KgQo0H4/HEwgEmust
LS1dXFz69+//+++/r127lvkrVtm9e7fW7ZunpqYmMjKSRCl8Pv/9998fMWIEalEAAAAA/n/AK2do
QcOHD584cSJZLi4ujo2NNeLBd+7cWVFRwTCMQCBYt27d6NGjEaUAAAAA/L+BQAVa1oQJE+ioX4mJ
icY67MOHD8+cOUOW58+f361bN2MdGQAAAABMAZp+PYVKpbp169a1a9fS0tJKSko4HI6Tk5OXl1dQ
UNDAgQM1GzLl5eW9++67ZHnhwoXh4eG6jrx9+/YjR44wDGNlZXXo0CHNQ5WXl1+4cCE+Pj43N1cq
lYpEog4dOgQEBISHh1tbW2seUCKRvPzyy2R5yZIlwcHBycnJJ0+evHfvXmlpqZub2969e5t7GprP
wcHB09MzNzeXYZiCggKy8ptvvrly5QrDMK6urj/99JOu8YsrKiomTpyoUqkYhpkxY8Yrr7xCPzp/
/jxZ8Pf3DwkJaclfAAAAAADPAQIVfXJyctasWZOVlcVemZ+fn5+ff+XKFRcXl/fff3/AgAHsTz09
PTt16pSTk8MwTExMjK5ARaVSkZI6wzChoaFqUYpKpTp69OiePXukUildKRaLxWJxQkLC3r1758yZ
M2TIED0pl8vlu3fvPnDgwDP82hZjb29PFiorK8nCkCFDyM8Xi8UPHz7s0qWL1h3j4+NJlMIwzKBB
g+h6qVR64cIFsjx+/PiWSTUAAAAAPE8IVHS6ffv2l19+yQ4VrKyseDweHWOquLj4yy+/nDlz5oQJ
E9g7RkREbN++nWGYhIQEiUSitfbj/v37ZWVlZDk0NJT9kVwuX7169eXLl+kaCwsLCwuLqqoqhULB
MIxEIlm+fHlNTc1LL72kK/FHjhy5d+/eM/7iliKRSMgCPRX+/v7W1tZk/fXr13UFKteuXSMLPXv2
ZM87+eDBA7KvhYWFn5+fTCa7du1afHz8o0ePKisrbW1t27dvHxwcPGjQID4fVzgAAADAvxKKcdo9
evSIRik8Hm/y5MnDhw8nZeXq6uorV67s2bOHlJW3b9/u6uo6cOBAuu+gQYNIoCKXyxMTE8PCwjSP
T7uVi0SiXr16sT/atWsXjVKGDRv22muvdejQgcPhSKXSW7dubd++/cmTJwzDfPfdd926devatavW
9JMoRSgUDhkypH379kKhkFZNtLL6+nrS7othmDZt2pAFc3PzsLCwkydPMgwTHR391ltvabb+kkgk
t2/fJstqFVOkwophmM6dOz948GDVqlVFRUX007Kystzc3KtXr3bo0GHRokVeXl4t8LMAAAAAoGWh
M70WKpVq/fr1JErh8/nffPPNtGnT6Bt9W1vbsWPHbt26VSQSkTVr166tqqqiu7u4uPTp04csX716
VetX0HZf4eHh7Ok+MjIyfv31V7L83nvvzZ8/39PTkxTiBQJBcHDw5s2bSUoUCsWePXv0/Ap/f/8D
Bw58/PHHEyZMGDVq1OjRo5/1PBjF+fPn5XI5Wfbz86Prafz2+PHjhw8fau6YmJhIapA4HA47DmQY
5sGDB2ShoqJi3rx57CiF7dGjR5999pnWgwMAAACAiUOgokVSUlJ6ejpZnjZtmr+/v+Y2bm5uCxYs
IMsSiYSOQEUMHTqULMTHx9fW1qrtm5OT8/jxY7I8ePBg9kdRUVFkoV+/fq+++qrm99rb29M5Fm/d
uqWrjO7q6rp06VKtrc5aU3Jy8g8//ECWhUJhcHAw/cjX19fZ2Zksax22+Pr162QhMDDQzs6O/VFh
YSFZKCgokMlkHA5n7Nix27ZtO3Xq1MmTJ9evXx8QEEA2kEgk3377Lbv9HgAAAAD8KyBQ0YJ21La0
tKTjaGnq27cvjWFIKyZqwIABpHcEaf2ltmNcXBxZaNeuHbvtllgsphuzR7hSExAQIBQKyXJGRobW
bSZMmGDEqRWfiVKprKqqSk5OXrdu3fz582mQMG3aNFoHxTAMl8ul4Vx0dLTaQerr6+lZ0hw2oKam
hi4LBILly5fPmTOnS5cuAoFAKBT26NHj66+/pjVI+fn5an8dAAAAADB96KOiTqVSxcfHk+Xg4GD9
xf3w8HDSj6KkpEQsFtPmYQP1w8cAACAASURBVDY2NgMGDIiJiWEYJiYmRq27PG0PNnToUHbfjLt3
75IFHo/Xo0cPXV9qZmbm6emZmZnJMEx2djYt7rOZm5vr/5lGceLEiRMnTjRly7Fjx6oNOcAwTGho
KBmXrLCwMDs7m92ZJCkpSSaTMQwjEAgCAwPVdqS98xmGiYyM1Kzy4nA4M2fOvH37Nqm5OnbsGHs6
FwAAAAAwfQhU1JWWltJysLe3t/6N2fUhubm57JGphgwZQgKVmzdv1tXVWVpakvX5+fm0c7lauy/a
R1ypVL799tt6vpfMyM5eMFn29vYzZszQGk116tTJ09MzLy+PYZjY2Fh2oELbfQ0cOJCeOoq2puvd
u7fa8NCUQCCYMGHCli1bGIYpLi4uKCjw8PAw9McAAAAAQGtBoKKOzvXBMIyTk5P+jR0cHOgyHbaY
6Nevn6WlZV1dnUwmS0xMpDEJra7p0qWLWtGZDlisUqlKSkqaklrNDjDPHZ/Pt7W1dXR07NatW+/e
vfv3729mZqZr44iIiO+//55hmOjo6DfeeIOsbGxspL1WtI6ZRnvnd+/eXU9K2H33Hz58iEAFAAAA
4F8EgYq6xsZGumxhYaF/Y3bDMLWYQSAQhIWFnT59mmGYa9eu0UCFtvsaNmyY2tGa0eebjIv1vIwd
O3bOnDmGHCEkJIQEKqSiqWPHjgzDpKSk1NXVMQxjbW3dt29fzb3Mzc3r6+sZhlEqlXoO7ubmRpfZ
w7IBAAAAgOlDoKKO3dCIvrnXhZSnCc16g9DQUBKoxMbG1tfXW1hYiMVi0rdEc8hd9hE6deq0Y8eO
5v6CfxNXV9eePXumpqYyDHPjxg0SqNDqlCFDhmitjbG1tSWBCvv8a+Lz+QKBgIR/GPgLAAAA4N8F
o36pYw/pW15ern9j2liLYRh7e3u1T3v16kXGuZLJZLdu3WJY7b769OlDB+el6CC8xcXFz2t+xtZH
a5bI2F8KhYL07WEYRm0QAoqeOl2jMxNKpZLGJ5odXQAAAADAlCFQUefk5EQDBjqxoC7Z2dl0uX37
9mqfcrlcWgq/du0a/ZfRmGqdaNu2LVmQSCT5+fnPnPR/pwEDBvB4PIZh/vjjj7y8vPT0dNLbx9nZ
2dfXV+sutGvKvXv39NR6FRcX02V2byIAAAAAMH0IVNRxOBzaL+Lq1avsLiua6AQgIpFIa19t2jUl
Nja2qKgoJSWFYRg+n691rCr2kMSXL19uVvL/fezs7IKCgshybGzsjRs3yPLQoUO5XO3XZ69evchC
XV0dGR5aK9KijOjSpYtxkgsAAAAArQKBihYRERFkobq6+tSpU7o2S09Pp6XkkSNHap2mo0uXLqSm
RSqVbty4kTToCgoKsrGx0dy4a9eutP/30aNH6ez1miQSSVRUFJlp5P8BOqXj5cuX6WADISEhurb3
9/d3dHQky/v27dPapV6pVB47dowsd+jQgT1yNAAAAACYPgQqWvj7+9MZVHbu3EnnYWQrKSlZsWIF
WbawsBgzZoyuo9GwJykpiSxoHXKXYRgul/v666+T5fr6+qVLl7LHSqaqqqqWLl26b9+++fPnP7UX
zb9CYGAgGWDt0aNHpNtP+/btO3furGt7Pp8/efJkspyVlbV7927NbQ4dOpSVlUWWNeeaZBhGKpWK
xeKnjpcAAAAAAM8FAhUtOBzOggULyNDDMplswYIFUVFRpaWl5NO6uroLFy68//77T548IWtmz55N
Os1rpVYzIBQKNadap4YNG0ZbhWVnZ8+ePfvixYt0bCuJRHL27NnZs2cnJyczDFNUVPR8hyc2FoFA
oNZvXnPsZjVjxoyhPVgOHTr07bff0l49RUVFmzZtotFLt27dNI+WmZk5adKkqVOnvv3222Kx2PCf
AAAAAADGheGJtfPw8Fi6dOmSJUsaGhrkcvm+ffv27dtna2trZmZWXl7OHpJr6tSpw4cP13Ootm3b
+vr6pqenk/+GhISwZ19Rw+Fw5s2bt3TpUhKKlJSUrFy5ksPhODg4yGSympoauqWlpeXSpUs1hw77
lwoNDT179iz9r552XwSXy/3iiy/mzZv3xx9/MAwTHR0dHR1NqmXIyMWEi4tLZGQkn69+nR8/flwi
kTAM8+TJk3Pnzr355pvG+iEAAAAAYBSoUdHJ399/w4YNPj4+dE11dXVZWRmNUuzt7RcvXjxt2rSn
Hmro0KF0WVe7L8ra2nr58uWTJ0+mxWuVSlVeXs6OUnr06LFjxw522v7tevfuTQfm6tatG3uuRl1E
ItHq1avZ09HU19ezo5Q+ffps2LChTZs2mvuam5trXQYAAAAAE4EaFX28vLw2bdqUmJgYFxeXmppa
VlbW0NDg4ODQtWvX/v37h4SEPHXqemLgwIFbtmxRKBR2dnZ9+vR56vZ8Pv+dd94ZM2bM1atXb926
lZ+fX1FRYW1t7erq6u3tHRoa6uvrq7Xv/r8Xj8cbOnTo4cOHmX/GdfqJRKIvv/wyNTU1Ojr67t27
xcXFHA7HycmpV69eAwcO9Pf317XjpEmT8vLycnNze/fuPWrUKOP8BgAAAAAwHk7rTyxIvlGpVCoU
isbGxoaGBqlU2q5du1ZOBgAAAAAAaCosLBQIBEKh0NzcnMfjkRkjWv8tOZp+AQAAAACAyUGgAgAA
AAAAJgeBCgAAAAAAmBwEKgAAAAAAYHIQqAAAAAAAgMlBoAIAAAAAACYHgQoAAAAAAJgcBCoAAAAA
AGByEKgAAAAAAIDJQaACAAAAAAAmB4EKAAAAAACYHAQqAAAAAABgchCoAAAAAACAyUGgAgAAAAAA
JgeBCgAAAAAAmBwEKgAAAAAAYHIQqAAAAAAAgMlBoAIAAAAAACYHgQoAAAAAAJgcBCoAAAAAAGBy
EKgAAAAAAIDJQaACAAAAAAAmB4EKAAAAAACYHAQqAAAAAABgchCoAAAAAACAyUGgAgAAAAAAJgeB
CgAAAAAAmBwEKgAAAAAAYHIQqAAAAAAAgMlBoAIAAAAAACYHgQoAAAAAAJgcBCoAAAAAAGByEKgA
AAAAAIDJQaACAAAAAAAmB4EKAAAAAACYHAQqAAAAAABgchCoAAAAAACAyUGgAgAAAAAAJgeBCgAA
AAAAmBwEKgAAAAAAYHIQqAAAAAAAgMlBoAIAAAAAACYHgQoAAAAAAJgcBCoAAAAAAGByEKgAAAAA
AIDJQaACAAAAAAAmB4EKAAAAAACYHAQqAAAAAABgchCoAAAAAACAyUGgAgAAAAAAJgeBCgAAAAAA
mBwEKgAAAAAAYHIQqAAAAAAAgMlBoAIAAAAAACYHgQoAAAAAAJgcBCoAAAAAAGByEKgAAAAAAIDJ
QaACAAAAAAAmB4EKAAAAAACYHAQqAAAAAABgcvjPOwEAACaqsLbko7gNlwtvC3hmr3Ya8m3ATCu+
xfNOFAAAwzBM2f790ocP6X/5Tk4u77//HNMD0BIQqABAy/o8ccc3d/ax13wbMHNRnzf17DLx4n9/
ybnEXiP7zzU+l9ci6dNt/IVFCcUZZHlT2uF6ufT7kIWtnIZWllfz+OeH53/K+v31zi9+3vetZhyh
RlbX7ZfJhbUldI2T0L7kzTOGpKpB0XgkN/rsHzdvldwT15dL5PV2ZtZuVk4BLt1f6jBoZPsBPM5T
Wgc0KBovFiYez4u5XZJZVFdaLq22NbNyFtr7OXUNadtnktcwB4GNnt1vl2ZuTvs15nFyYW2JkG/e
2dZ9bIeB7/tOcBLaG/K7nlVjfn5DZqbs8WN5WZmyoUElk4lefVXYrVtrpqHpGgsKSnfvZlQqukbo
4yOaOLFJ++bnl+7eTZZ5dnauH31Uum9fY16eIenhi0Quc+YYcgRoNmVtbd3du9KsLHl5ubKujuFw
uJaWZq6uwq5dLXr25JiZGeVb5MXFdamp0txcZVWVsr6eY2bGtbY29/AQ+vgIu3Z96u4quVyalVWf
mSl/8kQhkSgbGrjm5lwLC36bNoL27S169+Za6HtRpaiqksTFSbOzFVVVjErFtbYWeHpaBQWZuboa
5df9z0KgAgCt7eukvVM6R3SwbvO8E6JPUV0pjVKII7lX/r8GKhXSml9zo396cPbakxQDD/V54g52
lGK4Y3lXZ11bLa4vZ68sk1aVSatSy7N3ZZ7sauexe/Di4Da9dB3hSO6VT+M2PZI8Ya8sl1aXS6vv
V/1xMPvix3EbI/2mLej9hoCnpcC0MjkqMnG7UqUk/21slCWV3k8qvb8t4+hvL64KcvE1xq/US6Wq
S06WXLsmr6ho8e8yFqWy6uRJdpTyTOrT0uiyRffuRkoTPB+SuLiaq1dVUil7paKxUVFZ2XD/fs3V
q3YjRgh9fAz5CpVMVvX773XJyYxS+fdKhULZ0CAvLa27c8fc3d1+zBi+i4uuI9SnpVVfuKCormav
VDY0KBsa5BUVDffuVV+6ZBUUZBMayuFpeWXWkJVVceQI+zcqKivrkpPrUlPtIiKsAgIM+XX/4xCo
AEBrq5M3fBy78WjE8ueVgLP5cSPPfspec3v8nr5O3uw1NmaWHIajYv4uadmZW7dS+lqLVCE7mx8X
lfX7yUc3GpUyww+YWHJvS/oRw49Drbt74NObm/Vv86Aqf/DJ2b8M/Xp8x1DNTz+7uXnt3QP6jyBV
yL68tfNKUdKp4Wss+UL2R4eyLy5M2KZ1r+L6itFnP7s/8aCj0I69XqlScp9Ww9N08vLyymPHGgsK
nnXHkh07ZE/+js0EnTs7vv66sVL1VJLYWFlxcbN3b7h3jy5b9OxpjBTB81F19mxtQoKeDRTV1eW/
/GI/erRl377N+wqVVFq2f39jfr6ebRoLCkr37nWcOtXMzU1LIs+cqU1MfMq3yOWS69cbHz1ynDqV
Y27O/kheVlZx+LBKpi0LVSiqfv+d7+go8PJ6+i8BbdCZHgCeg2N5V3/Pv/m8U6GPjZnlzO4vs9fM
79165bwWpWJUN57cnX19Tduo0S+fX3gk94pRohS5UjHj2kpa82C4K0VJT41SCIVKOfnSl9nVhWrr
V6fsf2qUQkUXJc26vlpt5Ze3dtLlT3tNjhv3w9kR615w/rO1VZm0avu942q7fBS3ceTZT2PFqU38
Xj0aCwpKd+5sRpTyfCkqK2tiYpq9uzQvT1FTQ5b5Dg5mbdsaKV3Q2uqSkvRHKX9SqSpPn24sVL9/
m6jy9Gn9UQqhrK8vP3RIrWKHYZiamJinRilUY35+5cmTaislN27QKEXQsaPj1KmO06ZZ+P5V16pS
ad4O9ampxVu21KWkNLvW8X8HalQA4PmYc2Nd6qtRQp750zd9TrYEfxLo0j26KEnIM3+54+AX3QOf
d4qM4/PE77/9Z68ho9icfvhO6QMjHjAycbvaGieh/ZTOw9pZOWdVFfz88HydvIF+1KiULbm986ew
L+maorrSzxO/VztCe2vXlz0Ht7NyflxXdjY/LrPyEfvTHx+c/aTn5N6Oncl/n9SV3a/6gyy/5Dlo
TdCfPRz6Onl77B9HorsrRUmL/abRI8SKU7ek/apiVGfz426O+yHQgIZh8pKSsqgozXIVh8/nu7jw
HRw4QiFPJGr28VtO5enT2t8uN01DejpdFv5V2hN07Miz1lKlqaisVAvkzN3defZa+g5xte0OLUdZ
X1994YLaSoGnp3n79iqFQpqdza7xY5TKqhMnnGfNetZvkebm1qf+46UAh88X+vjwnZyUtbUNmZk0
6GUYRlFdXX3pkt3Ikew1Eo0ogmdjI/T25trYKCUSaXa2vPwf7U7r09KsBwxgx8+Nj/7MRriWlqLJ
k0mXG4Gnp7y0VCYWMwzTWFDAqFQMh/Pnb62vrzp3TllbW3n8uKKqyiYk5Fl/9f8UBCoA8Hw8rC5Y
nbL/v33fft4J0YnL4U7rOnJa15FP3/RfRapoNPox/5CI/5v4gxEPWFhbEidOY6/pbOt+c9wPtJ3V
/N6vv3BselWjhG5w4tF1mVJuxv3zufZrTrRaTdHcHq+uDvrAnPtnR5RVge9/dnPzxrRf2NscyY2m
gUppQxVdzw45XCwcvGzb3avMYxjmSX0ZXS9VyN6NWUGaC07yGmpIlKKSycoPHlSLUviOjtYDB1r4
+hqr83FLqE9LYw9F9cxUqnp2u68ePciCrsJcXUqKWqBi2a+fZe/ezU8AGEldSoqyoYG9xm74cKvA
v173DB2q1uBKVlwszc0VdOz4TN9SGx/P/i/HzMzxzTfN3d3Jf23Dw8uiothXSF1Kiu3QobTtVn1q
qkqhYB/B0t/fbsSIvzuiKJVVZ8/W3rrF3qY+LY0dqCjr6sgC39mZfW+atWtHAhVGqVTW1XGtrMj6
6nPnlLW1DMPw7Oys+/d/pt/7PwhNvwDgufn2zr68msfPOxX/67gcbkjbPgYeZM6NdbXyeqOkh3hQ
pd6W479932b3Buli5/Fhj9fYG1Q31j6u+ztsUKvecRTYrQmaQ6MUhmH4XN7qoA8cBf/oYZJWnqM1
PXzOP3rQ8rh/Pj2VrJYbK1N+yqjIZRjGQWCzYcBHOn9bE0iuXVN7j2vp7+88a5Zlnz6mHKUopdKq
c+cMOYI0N5eU4RiG4Ts5YcSkfy+1ig5zd/e/oxSGYRjG9sUXeTb/GG2vLjn5mb5C2dCgFhVbBQTQ
KIVhGI5AYDdmDHsDVWNjPavK7s9A4i9codBu5Mh/dJfncm1HjOAK/9F1TV6ifbwQDvefheq/qlAY
hqFNvKQ5OXUpf45ZYjdqlCnfziYCNSoA8Nw0KBrnxq4/8eKqZh8hp7roxKNrZ/PjcqqLntSXyZUK
J6F9L0evcLd+07qOVOvlfPLR9bHn5ms9jv/RPyt2Rrbvf3r4WrLc/Zcp5K058Vqn8ENDlzEMMzd2
/ea0w/9IxuRfO9qo99FcmRyl1g/7xks7Briq9wxOKr3/88PzVx/feVhVIJHXiwS27lYuYW59X+k0
RNeIUpWNkvk3t/z26BqH4bzccfCKgFnN6Ogv5JlHuAeO8wwZ3SHYWWjP+X7Asx6BOpp75cSja/S/
VnwLw4MWzSN0c/BUW9ND1EltTXVjLV1e3HfaLFYvI0u+kFa2UGZcfk9HrytFSXRNZePfDUXsBX+f
VfaVUC+X5lb/GWDTcY3vVeZ9k/Rng7q1QXNdLZrfKEtZXy+5+Y8eXJa9e9uPHt2UfUu++05rL3bp
w4dFS5eSZad33jH38FDfIDe3Pi1NVlAgr6pSyWRcoZBnY2Pevr2wW7emv+SuvnBBKfm7jotjZvas
bcBac7wvVWNjXUpKw4MH8uJiOmYu3/n/2LvP+DaqrGHgd0Zdsiz33mI7tpM4TrPjQKpDOumVhA0t
WR5KgN0ssI0F9oVdOrsLLEtPI0AK6Qmk9x6n2o5r3HuTLFl9Zt4PcsZXM5IsdwXO/5cP1vVIM5bt
+J6595wTKI2Lk48YQUgk/KfUfvghvpXId+FC2dChhuzs1kuXrHV1tNEojowMeOKJ7p+IRev1rVeu
GPPyKLWaMZtJuVwcE+M1ZkynUndovV5/44apsNBaX08bDOwFSGJj5cOHu6i6a8zN1R4/bm1uFvr5
KTMypImJzo7kfskUZbezC6H2nI27CIFAmpRkt6jiRqoJzlJZyVkP4ZdeEAUFCQMD8dDCXF4uHzHC
9rFywgRFWlr7JYlE3GADIYIkhYGBeBoMZ6WIkEqR0YgQsjY14Vu8rA0N7cfIZAghxmJhU1xkycnS
gQPd/2J/tSBQAQD0p72lZ/aWnpkTPa6zT6wzNL965csvc/dwsrcrWusqWusOlJ3/25Uv30l/5tkh
iwhEOHuRrlk8IIMTqByuuPzkoHmcw36usJtrhskDOIFHtb7xmTPv7Sqx2yFdZ2iuMzRfbcj74Ob3
s6PGfjXxz/wp72Mn3thd0hYYfJazs8Go3jblH+5f//iQ4WNDUqZHpHMqXHVNi7n1ubMfsg/jvSMm
hA7/Jm9fN182yot7K73eoOaOGLkjwfL29yreOwJ5d3yiWr3dwkW4IpD9OEIRFK4ItFVb3pj/0/iQ
4YtjMzRm3UsXPmHjKNv+Lpqhnzz1jm2nWUbYyMcSu7VdUH/1Kj6/JxUKfFd9j7PW16v37OFsoKL1
elqvt9TWtl6+LI6M9Jk7VxgQ4Pp1zOXl+qvtIZ9syBBLdTVnXagDNG3MzW1/hd6s96W/dq3l8GHa
YBcPUxoNpdGYCgu1p055T5nSYR0q2mjU7N9vty+IN83tzomMubnqPXvw51ItLYabNw23brmb2MAw
2jNndGfOMGa7DZ/tF3DypNfYscrx4/lPNVdUNG3bZiv4a6mtbdq6NXDVKodVs/gsNTV4pWCEkMMn
csItq1pNG42c5QtXZ6m2W5AnhEKRowLEotBQPFCxVFWxH3f4U23DrvLZCLzt/mcRh4cb1GqEEKXR
qPfvt5Uwbr1yhc1dEQUF2VZptMePU2o1QoiUyVQzZrhzagCBCgCgr3mLFfid7xfO/XtKeJpM6Oq2
IkeZrvaBfc8VtriqhqS3Gp87+2GZrvbd9B7u1jw2JCVY5od39jhYcZETqOgshjP2PUmWxj2AV63N
bi6euv95fKsS376ys2N2/fbogx/Herf/jW+1GvaUnMEP21l80mA1uf8GzotxMCnpsleufFGlb79x
+L/xL3FCr65JVEWHyPzxDJCNBT/Nimrfz80gZnOB3S6j4f4DAzvZgfFwxSV8qQQhtCBmIv7wDynL
157/CCFEMfQTJ//xxEm7gFBECm2LNp/d3mX7dksEos/H/7GbsTG+NQUhpBg5EgmFrZmZxtu3LbW1
jMFASCRCPz9pYqI8LY10eT++Q6bCwqatW12ve5jLy+u//NJ38WJXN4BpWrNvH7u/hZRKVTNmNKxb
16mLMRYVsZNyUVCQm5PILuBGFzy0waDeu9fa2Og9daqLw1ovX+bsAuLcj+/OiYy5uWycwMUw2pMn
CWEHUzjGam3assV1yhBjMmmPHbOUl/suW8bpEGLIzrY7O00bsrPdDFQojYYzIlCp+IdxZvyIYaiW
FvcDFU7bE9LLy263lZOzcJ7VIWNBASfe5nR9UaSnG3JybD/8+sxMfWYm5xVse94s1dW6uxk13lOn
sikrwDXIUQEA9LU3Up/EHxZrq96+vsn9p5soy8yf1rqOUljv3dh8oOx8566vIwKCXBI7GR85WnnF
StvtQDhRfZUzsnhABvtxvVE948DvXUcpNiXa6iVH/mrE0t9JRJL2f4xJghTw7uP2jUt1Of/FGqes
iJ82JTzNxfHukwhELw+3qwe9pejIs2feL9CUG6ym7Obi5Udf45QAfnUUd8uNM1aaKtXV/Cdr66LD
f8HHM8JGzo+xu1H9QvLS3wyc7vBFRKRwU8ar8d4RFa11f770P9vga6NWDVRxd1V1Cq3Xc/bMkN7e
9Z98otm3z1RUROt0DEXRer25oqLl6NG6Tz4xFRV1+Vy22+Tu7M5izObm7ds5N7BxurNn8S1nyoyM
LlTZcljvq8dpT550HTywdOfOcRItOBzkKmC/m905Ed3aqt6923GUchdjtbp+WfWePW4WNjAWFKh3
cQtt8zdBIUe9Dh1fG79andhBgUf+IGPoxK5R2v4spKNT8M9C867NyavT1uZm3dmzzdu348PiyEjO
NjZxZKRq2jSHMRJCSJGaKh85EjGMes8e2zdUHBPD7j0DHYIVFQBAX5sUNuLh+OmbC9tvh799fdPK
hBnx3hEunsX6vuiQLWWZNSF0+GujViWoIhuNLduLj/3z2kZ8P9ib19bZ7sTPirpf98RRhNChiksL
D/0Zf4Wz8z631XoSEG79JV40YNIn2e1/vTRm3aX6HDz/5FCFXfeAULn/fcHJ7MOXLnxS0WqXSBAg
9VkQMyFGGVrRWr+r5CQew1xtyPvy9u7nkpfYHsqEkocHTt+Y/xN7wMqBM/Ac8T7DaZyiEnt9cLeA
b494IXnpudpb2+8cZ0c+zdnxac4Ohwf/dcSjnMUQvol7nzlV7TRbd0zQkJ3T3ub0aiQJclPGazMj
7/tP1tYr9bm2L9ZLJJsROeaVEY/bfmbWnP3AtkI41C/uDynL3f76HLNUVXFaK7QcPOhsSkrrdE0/
/OC3fLkkti1dJ2D1atvTG775Bk8UlsTG+i1bZvuYzd9V797NiVJIuVw6aJBAqaRaWoy3b+Objhiz
Wb17d+BTT/Evg2pu1p5uT1IShYXh+/7dxFCUMS+PfcjW++pZ1vp6/FJtxFFR4vBwhJClpsZUbPd/
i+bgQengwQ6bkTt2d3LfzRO1HD/OSYRABCGJixMFBzNmM79mLp8xL48fZYmjoyVRUQxC5tJSc1kZ
/ilDVpZs8GDpoEHsiCwlpfXSJfZnjxAK5W5vxnMQDDicx/NiIXejCISQo3DIIYJzappmLBZnWewN
X3/tonORKDTUb8UK/teiGDNGFBamPX3aXFLS9o6RpDgsTHHffbZUK93Zs7YbEIRI5GOf3w9cg0AF
ANAP3huzZm/ZGXYDmJm2PH/2XwdmfuDOcw+W29Wj9JeoDsz8QCGUIYQiFEHD/OPVJh0eRVyozW4w
qgOkPgKCtB3Gb94iFYhtn3LT+NDhQTLfOkMzO3K44hIeqHDaWS6JnczOgItaKvEwAyE0PmTYzmlv
s6n/76Y/u/jwXw5WtH+Z/7q1ZU3yYnZD0WfjXo7zDt9fdg4hNDd6fPcnx13zUdbW640F7MO3Rz8d
IvfvwdcnCfLbjNcTVVFvX99EOe8j6SWSvZP+7NP23Tk7RSIQvTTs4T8Pf8RZ0s6K+Gkr4qfprcZ6
o1pAkCEyfyHZNqHcfue4LV+IQMQXE/7U/YjRgiXg2ri+cc5YrepduwKfeca2YaZ9+sWZS5Ek576y
MS+Ps0Iijoz0W7GC3XhDT5nStHkz3obPUltryMrihxB2jVNI0mfOHGd3l10wFRayU3NRaKiwd1rE
aE+dQnj6NUH4zJuHlzM25uU1bdnCxop0a6vhxg3XySqikBBJXJxAqWRoWnB3P093TsRYLHhRAYQQ
IRD4LV+OdzdvOXRIv2zEdwAAIABJREFUd97VWrH25Em7xyTpO38+nvajv3FDvXs3HhW3HDuGByqi
4GD/Rx7RnjpFqdVCX1+vCROEgYHITS7XglzpVAPELndL7PwTCaFQMXq0cuJEh0tDCCFxVJT/ww8z
FEVrtYhhSC8v9pfR2tzM9nz0Gjeul362f6kgUAEA9INQuf8bqU++cO5f7MhP5ed3lpzs8KY4QmjN
kMVL4x5gH/pLVJwYY2bkfXigwiDmTktVQCezF1wTEOTiARn43f2fyy+8NmqV7eNibVWBfXXdxdhW
sY35P9labdhIBKJNk1/DC5R5iWSfT/hjzHcL2ZFibVW+ujzRJ8r2UCaUvDryiVdHurvTqTeU6mpe
xbq2jwkawi8n0H0SgWhKeNr6/AO2jHaH4rwjJoaO6E5aiFwoJRBBdzR3kQul0V4h+EizScsWEngu
ebGzKm2dglfNakcQ0vh4UVgYIghTURGnDzel1baeP6/MyHDwROc4pWAJodB30SI8PYCUyXyXLKn7
73/xVRfDrVucQMWQlYVvP1OkpYlC7N4lN/VBvS/GbMaT9RFC8uHDOU1XpImJsuRkfC3CWFjoIlBR
zZypGD26Z09kKi7mrBUoRo/GoxSEkPe0aaY7dzjVdVmW2lpOFKoYOZJTnEA+bJilshIvumVtaLDU
1ODfPnFkpP/Ddjswf7XaMoI6+l+CEAj4/UY1e/fafolEQUHKcZ2uHPMrBzkqAID+8czghSl+8fjI
78/9B+817szYkJQFMRPZf/weIHhVWZtmrOZsT1lsn6Zyqf52s6ntLIcrLuOfCpH5j8UXW+yrgWWE
jeJMfxFC0V4hITK71YkLdVnIk6w58wFb+UpAkJ+N/yNn01SPePXKlxn71riIUhBCNxoLRvz46Ib8
A10+S7NJ+8bVdSnbV+apyzo+GvPSxU9s6f4RiqA30/6vyxeA41RnQggJvLwCV6/2W7FCOWmScuLE
gCee8J42jXMMXm7LTZytR5L4eH66s0Cl4lSk5TyLNhrxxikCb2/vyXa/F25irFZj/t2+NwTRS/u+
TMXFnOUp+XAHHYTwRhwIIQu2psQhiYvjRyndPxH/jA5TGkj7JiR2F8DLXJKnpvIPU4wZw31iQQH/
MIAQoo1G3blzdf/7n7MmKs7or11r+60hCNWcOfzdbsA1WFEBAPQPISn43/iXxu5un96V6mr+cW3D
P9ye8Bkp88Hyiz9XXLjRWFDcUq216J2176CdbxzqsvEhwwKkPg13K+TSDH208sri2AyEEL5rCyG0
ODaDncTTDM1pKZjTXPzAPgepHS0Wu4KY7mTe95ntd47vKzvLPvz90IfYbu496OOsbW9ctSsbFasM
WxI3OVjmV6Kt/q7wMPvmW2jrqpP/DJL5zox01eb5rdFPNxo1CCEzba1ordtfdu4wlkpUrK2a+dPa
a4vWu9mU5kTV1a9z21oifDruRaVI3mRq+SR7+66SU4WaCgttjfYKmRaZ/kLy0jjvcPe/ak5fCEQQ
vkuWcEoted13n7m0FM/ooHQ6a329+ztzKLWac8+eM2luH4+Oxtc6GIuF0mjYkIbTOEU1Y4azjTGu
GfPz2QhNHBbGvyfdI/jrDy1HjvB3qXFq0VIO17gQQgg5K9zUzRNx8k8IiaQTe65sr2DfS4eQSBy2
zhT6+Qm8vPAv0NroQf/P9AvlAw/YEvoZiqI0GmNBAVtlGCFEaTSNmzcHPvWUm6XJ6NbWlsOHbR8r
UlPFEREMTeszMw1ZWda6OtpiEchkoogIRVoam2YGOCBQAQD0m/uDhz6W8OD6/P3syHs3Nj8ycKY7
z92Qf+BPF/+Hl6/tY0JSsDg247OcnezIoYqLi2MzrDR1tNKu1I8terFpNmk5q0ZlutoyneP9Gzh2
uabftZhbnz/X3jglyiuY3fPWg4paKv9w4WN8ZEns5E0Zr0kEbdu+Xxu1avqB312pb9tgQzH0Yyfe
LHpou5fIaa4Rp9vmC8lLN+QfeOzEm+xIsbbq/ZvfcarSOWSwmp48/Y7t48WxGXOix11tyJvz80t4
peY8TVmepuzL27vXTXrlobgpHb6mQ6RUKo6K4o8r0tLwQAUhZKmu7kSgwpt8C3x9HR7JX2ah1Grb
oLm8XH/tGjsuTUjAMxw6BY+Feq/eF63l/hKZ3ekwSNOMyeS6LWPPnoiTRi90VNjXNc73l1sFGEOq
VPjB/LLCXdT5JKW7F9QnCw7OzyKJicEfeo0dq796le3SiBCiNBrd6dOu61azND/9ZKtIIfD29p4y
hdbrG7/7Dl8xo3Q6KjfXmJurSEvr1XZJ9y4IVAAA/emd9Gd2lZxUm9v+Ulpo63PnPvQVO93SYPOH
Cx9/ePP73r+6DiweYBeo2BZSLtXnaMztf/iDZL7jQtr3pruzt80hE8XdEdRf/nr5c3x5Z1RAEh5q
IoRuNtpVRDVSJjZl6LdJ89hIw7Uvbu+20O2bZ3wlyq8n/gV/rp/E+9uM1wdtXc4m/NQZmrcUHVmV
1ImKOo8mzNpdcnpnSXva8Ve397oTqLx5bb0tDUkl9vro/rWNRs2sn/6At9ZhGSnzyuN/j/eOSA1M
4n+Wr8PmGDaicO4qDWV/e941foK+syJI/Otpey5Nq/fuxbfsC3x9defO4UdyJtxUU5PtAFKhwBM2
GLO5vYpur+37Qgi5U4jZ8RMpqlPz7m6eiPvdcfKtcfU69q/gYpmLU9Csw5LHbnLQ3sdhej1vsFN9
gTjRI+MkgYQ7LhC4+VtmIx850piba8Q2xelv3HAnUDHm57M9kVSzZhFiMSdKwbVevixQqbzGjnX/
wn4lIFABAPSnIJnvP0Y/9eyZ99mRwxWX/CSuOor/WHyCE6UESH1WJ80ZHTQ4VB4gJoU3mwofP9GJ
Tu1dNjF0BL77q0xXe1tdwilMvCR2sgBL3uhUX0sPVKqr4RQI3llyEp/o8+ksBjbjfOXAGW4GKseq
7FalpkWkK0VyzjGJPlFD/AbgW+mOVWV2KlBBCM2OHotff42hsVxXG+nlYJ8M60Zj4bs3vrV9/G76
s6Fy/9czv2ajlPEhw/428nGpUPJR1lZbbWUrTb1xdd3u6e+4cz2kzG5FyNnEkb/zxM1Src6ejjhb
ztiX5c25bbNe/Y0bnM36rRcvIpcsdXWWw4cRQqKgIE79K/Ys4shIgfPUi+7qzPS0H0/E7Qfi5Fvj
6hU4033nr8D5/nZt5x4fwf/5NJuRnPsrzM/I6tTKFefHmP9qbePutVtxQZKQgAcqdGsrpVa73qDI
mM2aA22Jc9JBg6SJiaaiInYXmUCpVD7wgNDX15ifrzt3zhbw686cUYwZ04la2L8OEKgAAPrZ/w2a
/3Xu3qsN7ftYmkyuOge/fX0j/jBCEXRu3uf4zNLYV4sPQlKwIGbCl7l72JEjFZcP2hcmXjTArhaT
r8SbJEg8Z+alYQ+/m/5sb19qT2EYpjcSfvjKdXab7ENkjgt6hsoD8EAF705TqrNrm+grVnqLHWQU
cIoWIIQaTS0uAhWKoVef+qetm+eE0OG/HTQXIbT/bsaOt1ixe/q7vhIlQui+oOSspt/kqksRQocq
Llppii1q7AJnlw5jsdB6Pcmb4XGbbHRyiskJh5Dzdt2UWs19ru1iulwZlseA9XmU9dq+L8ReOYsg
Ql5+2f0+6H12Is53x3EhuM5cgIte7Jy9XvwfjK7hbzajNBr+zJ6704wgOpWexDkLrdMhhuHvOuN8
+fhuRqq5Gf8UIZM5/DYJeN1Lab3e9aW2HDli++pIqdRn1iyEEB7q+MybZyvjJo6KonU6/Y0bCCHa
aLRUVIijo1287K8QFB8AAPQzAUF+Ou5FN8vLNpu0bFqCzTNDFrq+/92rOC3qvys8dKn+NvswUOoz
PsSuJqmAIBPsO5fvKz2LVyv2cLYpeB/gLLw43FWFEKo32M0zJFiHnMQty2K+W8j+e+fuGggHuyDG
UjmKZ1gfZ22z/QSKSdHn4/9o+7llw6rh/gPZt0hICiaFtZW1NVJm1+E3SxzJbWyP5/KyLLyedEL/
TjSxEahUnCmpsyQKTvM7QiwW+vqinpvRMiZTe4kqkuzVQEUUEGB/bsbElhrzpBNxvpWUTuci0nD8
Cvap87Re77BBpLWpidbr7Z4YFNSpEzkjCg3ltLE3O9ryxKmhLFCpOrX1i1NkgqEoW1NF7lnsB/H6
y3Wfflr70UfsP93dbiccnHcJOVoywpkrKlqvtK0JKx94gPTyQni8RBBiLBNGPGAA+3Fnv9G/BhCo
AAD6X3rQkNXu7djhZ88nqripxi6aAzqDp0N0yqSwkfhGtQt12fiCw+LYyfyb6DMi7UqC3laXrM9z
XFq3xdz698yv+2YFw03eYoWgF8oQ84Ur7PLCD1Vc4pd0K9XV3GyyK8MainWcjLIv+ryz+KRtGYRj
251j+EMRKeSvsbBKtNWvXP7C9vErIx9L8mm798lmEHFS+RVYB0kD5dbWLGFgIGfvE97pon3wit3W
OESS/AjHDm/zDydH35ifz79zT7e2clL2xRERtkRkoocCFUNuLru9TRIV5ayOVo+QxMVxbrdrT550
tl9If+OGWxnwvXAifgISXrSA5WKlRYLNfW0c/hTpOT9Fjp7YNYRAILZvp4Ovm7Whae5Pl+ufYR5x
eDhnoxTel8bGWl/P2aOIn4W0Xyox5uU5zKUx5OTYPRYIXGxQZGhavWePbclRHBWlYAtD3/0dJAQC
/LLxrWg9lSP0SwJbvwAAHuGt0U/vKD7ZaOqg5oyE5O5vOVx5eeGASezDFnPrK5c/d/0iUgH3pt21
hvz0LnXrE5HChQMmfYXt/sLh9b5Yjwyc+e9bW/CRp06/KxWIl8fbZWdmNd157MSbmQ25Wov+/TF2
9YvNtOU/t7buKT1DIDQvZsLzyUtEZB/9Z04gwvrbM66PWXP2g/9m/8g+DJD61D/iIBLLarrz5rX1
eerSBFXUX0c+ymmqkxE26nxteyWoJlPL6pNvbcx4lf1KdRbD4yfe5ERxk0LbG/NNj0jH227eVpf8
3+l3Ph33Er5W8+6Nb/E6ywihKeFpLvKInjr9ri1eGuw74OVhv2HH2ZWcVovdjiy9tT04kbjdtF6e
mqo9fpx9aCou1p4+rRw/nh3RXbjAmeFJBgzg7PbhpAtb6+sZmiawYkfyESPwF2HM5qbt2/2XL2eT
BBizufnHHznTa7ahhyQmJuy111x/IXUff4zfyJcmJfktW8Y5pm/qfdmQCoU0Ph7fgWNtamr87ju/
JUvwAImhad3p09pTp0iJJGDVqk4tVfXIicQxMaRMZqsWZaM7e1YyYAAeW7YcPepw9cBGFBwsCgnB
D2i9fFkSFYWXZTPm5uou2SXUCQMCOKGCpbpae+oU1dQk8PNTTpzYqVaespQUfBXFUlWlu3DBC+vc
0nL0KGVfHo3TExPZyvseP26pqCBlMvmoUZxCC4REIklIMN5uX8RuvXJFOngwW2ubsVjU++1KfRAi
Ef5jJomNxXsQWZuamnfv9pk7Fw8ktCdPcvrSSKKinBWfQAjpTp2yhUaEUOgzB7sBd/c1GYpiKIo9
BZ4mBAkqfBCoAAA8gr9U9Vb600+eetv1YVFewX4Sb3wXzec5uwQEOT9mgogUXqnP/SR7e4m2mvMs
znb6EDk34eH35/9zvi4rWOZnsJo+Hru2U1e+ODbDYaASIPWZEOKgy9uIgIRlcVO2FB1hR8y0ZcWx
1z64+f2MyHR/qarBqDlbc/NU9XXblrAPbn4f6RX8QvJS9vjnz/7r89u7bB+frrlRoq3u7DX3uxJt
9f27n9Ra9Aih640F+8vOXV+8Id67vZXHbwZOf+f6Jnxx7IeiI1fqcxfHZgTL/Mpb634oPIzXAkYI
qcRec6Pbuz6vTpr7ac4OPJL5Jm/f0corS2InhysCG4zq/WXnrjdy29u9MHQpcuLbgoO2wm4EIr6c
8Cc84InyCrZtTstsyK3RN4bcXdi5XN92I1YiEPlL3S0yqxg9uvXSJbzJhvbYMVNeniQuDpGk6c4d
c5l9Y0qSVE6cyHkRzq1iSqdr+PxzcXQ0Q1HSxERpQoI0MVEUHIx3/DCXltZ+/LFs8GCBUklptcbb
tzlVboUBAT27NYs2Gs1sB0mBoFf3fdkoJ082FhXhd83NpaW1//mPNDFRGBiIaJpSq40FBbatPrTB
0Pjtt4GrV3dhnac7JyJIUpaSghcnYCyWho0bZYmJwqAg2mg0FRV12HZQOWFC09at7Y8pqmnrVkls
rDgyEhGEubyc3xRSOWEC/tDa0NCwbp1tGm2pqzPduRP45JPuh22yYcO0J07g4VbLwYOm/HxxdDSi
adOdO5xdhcKAAE4vEYaiGjdutNztCWMqKWEoihPMeKWn44EKY7E0btggTUoSBgUxBoPh9m1OkpUs
JQXfXaZITdVfu4b/hTDcvGkuKZEmJQmUSlqvNxUVWeyb0iBHjTJZ1oYG3dm2ex9eY8cKsU2A7Rk1
DGMqKJAmtZUBxMM50nkh6V8tCFQAAJ5iVeLsr3L3XKrLcXGMkBSsSprz3o3N7AiDmP9m/4jfwufj
7LpJVEXh1boQQkbKvDH/J4SQj9irs5P+jLCRvhIlv8/JogGTnCVP/2/cS9ca8vI1dvs9MhtyMxty
HR7/xe3dzwxeaFtMMFLmr/P2cj774X3P99miSo/4oeiILUqxabUaNhccxPuxDPKJeT556b9u/YA/
q7Cl4u3rm5y95ptpT+LBwDD/+LVDH3r/5nf4MaW6Gs4I7jcDp0+PSHf22QRV5ITQ4aeqrz89eAGn
JcuDUfdfrr+NENJZDLN+/sPbo5/xEXttLjzI5lNNCU9z/xtESqW+8+c3fvcdPn8yV1Y63OWPEFKO
HcvfMyOOijLm2v04WerqbFMuob8/SkhACPkuXFj/1Vf4DV26tdXhHiGEECES+S5a1PX+GI4Yc3LY
BpeSmJieyntxQRQS4j11asvBg/ggY7HgCzs4WzjhsK98r55IOXGiISvLriMkRRlyclCOq/8ecdJB
g+TDhtmytFmmO3dMd+44PF6WnCwbavdTrb9+Hf/ZYMxmw82bygwHq8QOkRKJasaM5p078UFTcbGJ
DU1xBOEzezbnp8tSUcEJEvSZmZxARRwdLR8xAt8ax1itzt5kUqHwfuABfEQUGqpIS2u1X1miWlo4
IzjZkCHShARnnyVEImlSkiE7WxgQ4GUf+EkHDmSDT/WePd4Ggyg42FRayi7pEBJJZze//RpAjgoA
wFOQBPnpuBfJjlIgXhnx2BDfzm2k5qRikwT5fPKSTl+fE2JStCCGez8bOdn3ZeMrUR6c9e9kP7da
Eccqww7O+hc7zbXSFGW/i9rKUA6zLzwZvzIbf+Td9GfxTX2u/W7osjVDFnMG30l/5tEEd3uozY+Z
8PXEv7g4YHTQ4JNzPt034/1/jn6K86lnhywKkrU1TLzWkD/9wO/Sd63+KGubbURICl4d+YSbl2Ej
iY/3mTPHneZ3spQUh3NH+fDhHVZ6FQYF+S1d6k65MFuU0qmdP+7os3pfOK8xY5STJrkZcSknTuxC
lNL9E5Eyme+CBa7bffBrwXGoZs92MaXGSeLi7DYpIYQc5Ut0NoNClpLidf/9HR9HEKrp0/nVrty8
ANXMmWL7Lo2OTyKR+C1dyg+GVTNmuN+6RzpwoM+CBS4OEKhUvosWBT75pO/ChYT9768kLo7dvEcb
DOo9e+q//LLl0CH2i1KOGwdbv/ggUAEAeJBRAUlPD3b1ZwAh5C1WHHnwI7aeEoeQFHx43/OcfGi8
gq3NH4f/ZlbUfd25VByn9hdCyF+iwvMl+GKUoRfmf/lC8lIXfUUEBLk2ZfmNxZsiFO2leLxEMk46
/oNR999z7VnmRI/Fk/JJgpwbPZ5zjJAUbJvy5of3Pc/voIILlPpsynjtX/e9wP8USZDrJ73y9cS/
BEhdFRL1l6j+O+7FHdPeEruRRvJg1P0qMbdWaYDUZ9+M94Md1VAWk6L1k14ZHTS4w1fmkI8Y4f/w
w0JO/SgMIRKpZs3yXbDA4VSYlMl8Fy50sZPeRhIfH/DEE67v44rCwwMef1yamOjmlbuJ1utNJSW2
jwmBoMtd7btAOXGi/4oVLt5bhJDQz89/5UrlpEn9dSJJXJzfsmXOdp3JR4xQPfig67MTQqHfQw8p
J01y1fBRJFKOH+//8MP8Y2SDBtn9aBEEu1vJfd5Tp6pmznRRmpn08vJduFCR7mAlUxwRwclZd3gB
hEjk//DDitRUF4G9KCQk4NFHOQUk7j6f8F20SPXgg64X9Eip1Hv6dL8VK9yJJUQhIQ6jer+lS0Wh
oQ6fIh81ymvcOIef+pW7l7YKAAB+Dd5IfXJr0dF6XtFYXIjc/+iDH+0rO/ttwcHztVl1hmapUDxA
GTY1PO3ZIYtilKE3Ggs35LcncO8tPfPx2LX4zFhMivZMf29zwcHNhQevNuSrzVqlSB7lFfJAeKqj
E3ZgcvgoH7GXGmtIv2DAxA6bZiiEsn/f/7uXh/9ma9HRI5WXs5uL6w1qhFCYImCAMnR21NgFAybi
IQprY8bfXrzwyf6ycwRCs6PHvpe+pgvX3L9GBSTtmPbWq1e+KtCUx3tHvDbqifuCHdzUJAny90Mf
Wp0094eiI0crr2TW59Yb1a1Wg1IkD5H5pwUNmhYxetGADKnA1ZrAE4mzl8dN3Xbn2KGKS5frc2oN
za1Wg0rkFSz3SwscNCU8bdGASd2P9NICB2Ut+faT7B93l5wqbKmw0NZIRfDUiNEvJC9N9HE0PXKD
JDY26JlnDDk5xtxcS1UV1drKWCykTCYMDJTGx8tHjHB9T12akBD4f/+nO3/eXFxMabWIYUipVBgU
xCnqKgoODnjiCVNRkTE311xWRmm1tMlESiSkl5c4KkqWlCSJj3d2iu4wZGezKRyS2Nje6GfigiQ+
Pig+3piXZywoMJeV0TodbTaTEolAqRSFhsqGDJHExrqzotWrJ5LExwetWaO/fNmQl0c1NTEWCymX
i6Oi5KNGSWJiLFVVHZ+eIJQTJyrS0vQ3bpiKiqwNDbasGFIms+WEyIcNI3lNQmzE0dG+CxdqT560
tUBRTpzYtY1JitGjZcnJ+hs3TIWF1sbGtguQy0VBQZKBA+UpKc6W/giJxO/hhzU//2ypqiKlUvmw
YXhJCbsjhULVgw8q0tMNN2+a7tyxajSMwUCIRKRcLoqIkCUlSZOSXC9tKVJT5cOGGW7dMhUVmaur
ab2esVhIsZhUKEShoZLYWFlycodhf4dIhSJg1Sp9ZqYhK8taX09bLKRUKg4PV6Sl9dJv2S8AwfRc
zyY32c5I0zRFUWaz2Wg0mkymcF4xPgAAAAD8UjWsX8+2iPFdsECWktK/1wMAwFVWVkokEqlUKhaL
BQIBaatL3qNZau6ArV8AAAAA6FO0Tsc2D7HlH/fv9QAAPBNs/QIAAABAnyK9vML+9rf+vgoAgKeD
FRUAAAAAAACAx4FABQAAAAAAAOBxIFABAAAAAAAAeBwIVAAAAAAAAAAeBwIVAAAAAAAAgMeBQAUA
AAAAAADgcSBQAQAAAAAAAHgcCFQAAAAAAAAAHgcCFQAAAAAAAIDHgUAFAAAAAAAA4HEgUAEAAAAA
AAB4HAhUAAAAAAAAAB4HAhUAAAAAAACAx4FABQAAAAAAAOBxIFABAAAAAAAAeBwIVAAAAAAAAAAe
BwIVAAAAAAAAgMeBQAUAAAAAAADgcSBQAQAAAAAAAHgcCFQAAAAAAAAAHgcCFQAAAAAAAIDHgUAF
AAAAAAAA4HEgUAEAAAAAAAB4HAhUAAAAAAAAAB4HAhUAAAAAAACAx4FABQAAAAAAAOBxIFABAAAA
AAAAeBwIVAAAAAAAAAAeR9jfFwAAAKDTvj/boDVQ7MOoAMmM4T79eD0AAABAj4NABQDwy7HnSlON
2tKdV1DKBMvHBvTU9Ximm6X6CwVafGTKUFVssJR9WFxnOnxT7fpFhAJCJiJVCkGYrzghVCaX9N36
vJVmSutN5Y3mZp1Va6AsFEPRzCMTA6WiPt0jYDTTBTXGwhojSaB5aX5deAWThd56vtFgptkRiZB4
dFJQNy+spN5UXGus11oNJspCMQKSkIhIX4Uw3E+cFC4TCwnO8Toj9d2Zhq6da3iMYnS8Fz6iNVA3
Slsrm8ytRppBSCYmQ3xEKVHyAG9RF7+ejkRERFRWViKEDhw4MHPmzG6+2vr16x9//HF8pLCwMC4u
rpsv6wl0Ot2xY8e2bNkiEonWr1/f4fEMw2RnZx87duzkyZOlpaV37txRKpWhoaHDhw9PTU2dNWtW
WFhY710twzBXrlw5ePDguXPnsrOzm5ubg4ODIyMjR48ePX78+ClTpkgkkg5fxGq1Hj9+/MiRI5cu
XSotLdXpdDExMYMHD546deqMGTP8/f27cGHV1dUHDhzYvHnz8uXLf/vb3/IPaG5u9vPryn8ICKFv
vvmG8+MHIFABAADQaVaK0VKU1khVNJqvFOkGhsrSB3r1dqhgstDXS/S3K/VmK9OrJ3KBopniOlNB
taGyyUwzCCEUpOriFPx8gQ6PUrqvTmM5mdPS3GrFB2mKsVCUzkiVN5oy7+hGxXmlRMl78KS44jrT
iWyNhWr/7uiMVGENdafWODpemRLdW+ftQRs3buSM7N2793e/+12/XEyPsFqt58+f37Fjx4YNG5qb
mxFCK1eu7PBZBQUFf/vb37Zs2YIPNjc3l5WVXbx48fPPP0cIvfjii3/+85+7PCl3obS09IUXXti9
ezc+qNVqCwsLjx8//s4778THx3/00Ueu49KrV6/+/ve/P3XqFD5YX19/+fLlDRs2hIeH//Of/1y5
ciVBcEN3h7Ra7dGjR7ds2fLDDz/YRpYvX97JLwt0BQQqAADQk8xWZv2JOnxkVKzXqFhFf11PH6AZ
lFdlqGg0TR/uG6DsrT8rpfWmU7dbenZm3ykVTeaCakNpvalHwqSqZnNBlaH7r8MqbzQduqGhaFfX
ZqGYC/ladatKKVCTAAAgAElEQVR1wiDvHjy1TXOr9ViW4wugGXShQKuSC6IDO74L3o9ycnKOHz/O
Gfzmm2+ee+45gUDQL5fUZQzDZGVl7d27d926dYWFhZ167okTJx588EG9Xu/6sPfff//o0aN79uyJ
iIjoxpVyHTp06JFHHqmtrXVxTGFh4axZsz766KPnnnvO4QEnTpyYP3++RqNx9gqVlZWPPvpocXHx
q6++6iJWsVgs586d27lz58aNG21hHuhjEKgAAADoAa0m+sDV5oXpfl7Snp/S3SrTX8jX9ssySpPO
mldluFNrbDX1WIxEM+hMbk9+OXozffRWB1EKK7fSEKAUDo7ogfUNf6/2WcS14lb2AkJ8RMOiFQKS
yKnUl9SZbIPXS1o5gUpeleFaceuwGEVimIx0675279qzZw9/8NatW5cvXx4zZkzfX0/XlJeXHzhw
YMOGDefPn+/C02/evDl//vwOoxSba9euPfzww4cPHxaLxV04F19WVtbSpUtdBBi4559/Pjk5OSMj
gzNeVla2ePFid17k9ddfT0xMfOihhzjjDMPcunVrz54969evLyoqcvPiuy8hIaHPznWvgEAFAPDL
EeYrlokd7D7SGumGFrvclQBvkVLq4Ei55B67b9o3fBVCbzn2zjDIZKUbtVZ8kw9CyGihT+a0PDjS
t2fPfrvScD5fyx8XCwk/L6FcIhALCGHvzHPdSdfpgmvFOrX9Bq1uv2ArZ52HIFB0oMRHLjSa6dIG
E2clKvNO66Bwue0+skREjhzg1opfXYulotHMPlRIBXhqU62m7VdMIiJnjfAVCgiEUIS/eNv5Rttu
tLoWC80g9htlMNMXC3RGC336dovOSKXF2eW69D2r1fr11187/NSPP/54rwQqFy9e7Oalvvzyy5wp
fnh4+OOPPx4XF6fT6S5evPjtt9/inz116tSOHTv4c/0uMBgMK1eu5Jx9/Pjxixcv9vPzKy8v/+KL
L0pKSvDPvvbaa/xA5ZVXXmlsbMRHpk2bNnfuXKlUeu3atS+++MJiaf9zsHbt2ilTpgQE2KUm/ve/
/3W2VtMhmUy2YcMGd468cuXKxx9/zD4cO3bs/fff37WT/oJBoAIA+OVIdTLXuV1hOG0fqAwKkw2K
kPXJRf0SxIdIR/DmshaKuVSoyy63u/Na2WSuUVtCfHosc7pBazmXx41SQn3FKVHyPthH5OYaRado
9NSNErduV7uvtN6EPyQJNGukb5hv201uk4Xem9ncpGsPjQxmulptth0gEhDOfnE4dlxqwh8OCpfh
W2ZMlrZYyFchsEUpNgHeQlugwjDIaKbZugvn8rRGC40QUkjI4TH9vzfy7NmzzrZIrVu37rXXXvPy
6udQyh34FLwLCgoKDh48iI8sW7bs888/V6lUtodr1qx55JFHpk2bhh+za9euHglUduzYcf36dXzk
T3/60xtvvCEUtk1WV69e/cADD9y6dYs94PTp04WFhfHx8exIcXHxpk2bOC/y5ptvspv3Fi9ePG3a
NPaNqq6u3rlzJyct3mSy+4XqFKlU+sgjj7hz5E8//YQ/XLNmjZsJM78q0EcFAABAV4gExNhE5cBQ
KWc8v7onUy/O5mrxaIEg0NhE5ZxRvv2V7aCUCSTdqxlwJrfF2qPxD00zOiOFj8QESdkoBSEkEZH8
UKSzSzqVTWZ8WVIoIIY4CfUJZDfZwudeDGr7wssaTEW1RtvH9yd6iwT9Pz/78ccfnX2qsbHxyJEj
fXkxPWjy5MnJycluHpyfn88ZeeONN9goxWbq1Klr1qzBRy5evNidK2Rt3boVfzh8+PDXX3+djVIQ
QoGBgX//+985z8rNzcUf7t+/H38YERHx17/+FU8xmjRp0gsvvIAfs27dOtcXJpVKezx1Pjs7m83L
RwiFh4fPmTOnZ0/xywArKgAA4Fh5o6moxljXYm01UlaaEQtJuZgMVokGBEsi/bmzZKOF3niy3uHr
ZN7RZd7RIYRIEq2eHMz5rMFM36k1ljea1a1Wo4W2UoxISCqlZLCPOClM5t9ruek9JS3Oq6DaiI/U
t1gQQjoj9f2ZBnw+PiBIMjWF2+yFopkNJ+ut2BayEB/R3NS2OkIldSZ2Q5HN2ERlp5IrGAZl3tHl
VRlMViZQKbo/Udm1tzRAKYwKkMQGS/28hLsuN9Vpupivkl9tqGxq3z0lJInuBy2cDXgIIR85dwcj
v8hBZ0sC3CxtxR/GBkk5AZtYSJqtFEKoxUgxDGLDEw0WEdmeYqWYM7ltq2QDgiQDgvo/w16j0XDq
fb344ovvv/8++/D777+fP3++w+dWVVWFh4ezD0UikcFgoChq9+7de/bsyczMrKmpiYuLS01NnTNn
zvTp0/l5+Xv37p07dy778IEHHjhy5Ehzc/M333yzc+fOmzdvarXaq1evjhgxws0vRyQSzZ8/f/bs
2RkZGZGRkY888khWVpY7T7z//vuzs7PxkdjYWP5hQ4cOxR+WlJQwDNPN1QCTyXTo0CF8ZOXKlfwa
xKmpqZyRpia7hT5OZs7SpUv5S2Fz5szBv7nnz59vbGzkVysODAxcsmTJjBkzxo8f7+Pj8/3337v9
1XTsyy+/xB+uWbNGoej/dUUP5Ol/AgEAoO81aq2nbrfU2+8WM1lok4VubrXmVhkCvUUTB3v7eXXr
v1CKZq4Wt2aV6TkTTduJGrTW7HJ9fIh0XJI3v/eF5/CSChQSEk80bzXStvFAlagOCzOqmx1sSqls
Mlvtv/yYwPYlmuwKuy1S4X7izqaAXytuvVrcNsOuVpt/ut689L4A999Pb5lgzEBlbLCkRyoEmCz0
xQId+9BLKghSie7UGl08xR0SESkSEPhPkdHCjaP41dI61fqmSWfFs1MQQkN5NY4DlELbwk6rkTp5
uyU1ViEkiaxyPRtq+iiEtlSii4U625ESITE2sefrj3XBoUOH8NSICRMm/P73v8fnslu3bv3ggw/c
KW9lsVhu3Ljx/PPPnz17lh28cuXKlStXPvvss9mzZ3/66aeRkZEuXqGxsbGkpGT+/Pk3btxgB90s
OxYSErJz584JEyZ0rWqwr6+vr2/HOWYNDXaNd4YPH979PUuNjY1Go93vAr6hi+Xjw73ZIRK1bzRl
GObMmTP4Z1NSUvgvkpiYyBnJzc0dO3Ys+zAtLe348eNjxoyRSrkrxj2isrLSVuKZtWLFit440S8A
BCoAAGCnpN50LEtj5d2lxtW3WHZdbpo8RBXT1ZvBVpo5eF2N31x3qLDGqNFTc0b5Cj1gb4wzAvtE
doZpe+tiAiV4oGK00HUaC6frSLn99JcgUHxI28zAZKGrmu0+mxItN5jpW2X6ikaTrdWjRET6eQlj
g6RJ9vkSrOJ6u6mP3kRXNZtj3N42FqQSdblNCt/5fLvGKfcnKDmX12UhPiL8nSypN6UPZPD9VPn2
q14EgSL8OvGje6O0Ff99CPER8RemkqPkJXdTZfKrDPm84su2rWK1GkvO3fgzLd6rL1uFuvDdd9/h
D5ctWxYWFjZ37ly8Dti+ffueeuopd15typQpzkrZ7tu3r7q6ev/+/cHB3MVVlq1yLh6lILcDlfj4
eIfz+x7U1NTE2SvVIwkqISEharVd4Qq53MFdifLycs5IVFQU+7FOpysrK+O8LP9FAgMDOSM1NTX4
wwkTJrhxyV23YcMGPCpbvXo1/lUAnEf8BwEAAB6ivsVy7FYHUYqNlWKOZWvqNF1MXT2Z3dJhlMJe
EqeRvEehaUZvf7deerfwWnyIlBM7lDVyU1Sr7N+EIG8RO3MtazAz2PdBKCB0RvqHsw3XS1obtFaT
laEZZDDTlU3m07ktP15sbNHb5WnY8IOX/iqDW9VsLsCyd6IDJV2OcvmG2Sej6030/szmqmazhWLU
euuFAm2O/dpUQqjM/QhBb6Lv1Np945IjHcwgw3zFo+O9nL27iWGyIZFymkGnb7fYvq0hPqIeKZHc
faWlpbt27cJHbMniixYtwgfXr1/PMG7tl3PdcCMzM/OVV15xcUB9fT2nTSFCiCT7ecLGMIxarT52
7Nj8+fPxqgODBg168sknu//6JEmq7OFLJSzOd8rX13f48OHsQ35VZYfRDkmSnFilpaWl65feSWq1
+t///jc+smrVqj47+z0HVlQAAKDdqdvcRGeJiIwOkCgkpM5EldWbTNjOfivFnMxpWXKfP0JIKiIf
mxSEELJQ9ObTdvsiRsQobPNI9pZ/k85aZL/hRy4hR8V6hfqIKBpVNZsz7+jwFILcSkNqXK/3fe+a
nAoDJ67zkbf9ZfGSCgK8RfgOuqomM8J2vLeaKE4bdXzuztl6R9PM6dtOJxNNOuveq83zUn05e7QS
QmUN2vYwz1smwLPM+wyncYqtDkEPvn6Yrzg1zutKUfu+sroWy75Mx9PlIJVobFInzn6ztBWvZ6C0
r0qMGx6jCPQWXS9prVFbbE8hCOSvFA2NlNuKLlwrbrUVHxOQRG80neyavXv34g8nTJhgW5SYOnUq
Pn7x4sXr16+7mSiiUql+85vfDBo0yGq1/vzzzz///DP+2a+++uq3v/3t6NGj3b/I/uo4+dlnnz39
9NPOPjto0KB9+/a5s1usR5SXl3Om+E8//TSe2sEPVJztSeM0ftHpdA4P6w1bt26tr29PaJwwYUJ6
enqfnf2eA4EKAAC0uVNrbNTazZsDvUUzR/iwEYLBTP90rbkBO6a51ZpfZUgIkyGE7mY+cMMJkiQ4
SRHlvIWFyUNUYX5tfzj9lUKxkDiZ0z4ppxlU1mBO4NXX6l8Mg3IrDRcLuX/go7CNVQOCJHi8Uddi
sVDtW5LK6u33fSEUh82ANfYrJB3mnLcaKX4Xl+QoOUkS+VUGk5UO9BaNjvfql010V+0bp4wcoOjx
tpgjByikIvJSodZ1lvzAUOnYRG/3285YKCbPfhNXUrirut7hfuJwPzFFM61GmkFIISHZN1ytt94o
acsXGhYt91F4xAyEYZj169fjI8uWLbN9EBoaOn/+fPwW/o4dO9wJVAYPHrxnz564uDjbw+eff/7D
Dz988cUX8WO2bdvmOlCJiYlZuXJlYmKiQqFoaWnhp3r3u7Vr17788ssu9rD1LIqi1q5di0/xVSoV
ZzMeRTlYVnUHTfdYO1fXTCbThx9+iI88++yzUJXYBY/4bwIAADwBZx+/gCSmDFXh6xgyMTk1xWfb
+UZ81aWo1mgLVNwX4SeRDbGbp4ba3+aPCZSctH9Ki74n+wN21p06Y6PO7gLMFrpRZ+WnaCtlgkQs
oIoLll7CIhmaRuWNptigtgMqmuwCtkCVCJ++G3gZ4QghoYCIDpCoFAKzhSmtN2nty/JWNpkrGs0R
/nZv5uAI2eB+7Zmj0VM3scYp/kphSnSvlPcJ8xV5ywQNWqc/KmIhEekv6VRthuxyPb6KKBQQ7ryZ
ApLw5lUeO5XTtlzpoxCOjPWUniSZmZmZmZn4CN4kZNGiRXigsm7dur/85S8yWQfvwOuvv85GKQgh
giDWrl178ODBw4cPs4M//PDDu+++62yGOnfu3HXr1nUtIb5vyOVyqVTa5cCgC95+++3t27dzRlyX
JfBA+/bty8vLYx9GRUXNnj27H6/H83niRgIAAOgX1fap2+F+YqWMO9lSygSRAXbz4Gp1p9NU/JXC
hFAp/o8zXZGISM6IqZPFZHtWo9Z6p9aI/6toMvOjFJJE45KUJHa3XikTBHrbbTTHi0dx6oANsM9x
52cKBXmLHhob8MBQVWqs1/2JyqX3+/O7qXCSMTzBaWw/IUGgcUnevXH/tLDG+OPFJhdRCkLIbGWO
ZWmOZWlcHIOjGZRdYbecEhfMrUrsppwKfY3aghAiEJowyLu/MoX4ODkP48ePx5PRObu/KisrT5w4
0eFr8uvhEgTx6KOP4iMVFRUVFRXOXuHdd9/15CgFIaTX6//5z3+OHDny5MmTHR/dbZs3b+Yk9ixZ
smT16tV9cOoeRNP0v/71L3zk2WefdZhFA1iwogIAAAgh1KKnOGWCnZV7CvERF9e1LwVYKabFQHnz
Qho3VTSZS+qMTTqrRk9ZKMZZHr+bWbz9SCggJg725neYiQmUcNNUEEII1WkseBVdAqG4ELu9bZyu
8FIROQPbhocQEpDE5GTVD2cb8JCppvNxY6/KqzLgtcuSwmTBPVdGjFXZZD6Z04K/Y0IBERMo8ZYL
TBamrMGkNbTf+S6sMUpEpDtJMoXVhlb7NSt+VWJ36E305bsLa4nhshAfEU0z2RWGolqjutVqpRiJ
iAz0Fg2OkEUF9GlPFYPB8M033+Aj7L4vm+Dg4IULF+7YsYMd2bp168yZM7twLk7vEYRQZWWlswUB
fhHe/jJr1qzTp08jhCiKam5uvnTp0meffcZWC6itrZ03b9758+cHDRrUe9dw4MCBxx9/HB8ZNmzY
p59+iveCvCecPHkSL1otEomgKnGH7rHvMQAA9BI9fxeTkywC/ri2S4FKRZP5fJ62uZMNwj1TmJ94
XKLSYdZBfIj0Mpbk3WKgbHEdpwJYoLfIddpGkErELycgEhDxIdJbZe2rKEYLrTNSPZ4B0jWcxiky
MZk+sCdz6G1oBp2yj1KUMsHskb7seuB9CcrjWRq8fkN2uX5AoIRNi3LmZpnd8lSYr7hrvYPO5LbY
lgTlEnLMQCU/18tgpssaTGUNpqQw2YTBfZdkf+LEierqanwE3/dls2jRIjxQ2bx58zvvvBMUFNTZ
c/FL4mq1nlvNjxUVFYVXzp0/f/4TTzwxY8aMoqIi24hGo3n99de3bNnSSxdw4sSJJUuWWCztNyAi
IiK2bdsWEBDAP7jLyR59U6vg448/xh+uWrXKnc48v3IQqAAAAEKONhqJnGRd8/+iuVPOmCO/ynDq
dku3m5L3DwIhoYAQi0gfuSDQWxQfInUxf1XKBAFKIT4rLas3JUfJOYWJ+bV63Uz45mwtQwjpTbSH
BCrn87X4qpG/Uphdbjf1b261W6+gGHTtbnvKodFyN9+B4jojJ1dnfJI3vmuRJNCkId7VarMe68uZ
Va53HaiUN5qa7BOThjiqSuzG5ZnY/ir3JyjFQmL35WZnW9RyqwxeMsHIAX3UopszvZbL5Zs2beIc
w2luaLFYDhw48Nhjj3X2XPxiuwYDt9XMPSE+Pv7NN99cvnw5O7J169b333+/N9JFLl68OH/+fLyW
V2Bg4J49ewYOHOjweP42KmdZNGaz3f8/SmXP30HguH79+s6dO/ERzjIRcAgCFQAAQKi9Zlc7yslu
Kws/pOlk53iNnjqTp8WjFJJAUYGSKH+JQkqKBCRCaG9mk+fs9kqL8xrRjbljTJC0Qdu+sFDRZE4M
l3Fa0MSHcGuaSUR276qzaJBzGELI3Pm4sTdo9FSBfXmGikYzp787h5Vi2NWnQREyNwMVTm6VREhw
ygkghAQkEeEvwZswdrhH7kapXUyllAkGdL7xi9nKnMtrq18XHSCJDZaW1pvYXvUyMZka56WSCUoa
TNlletu37WZp67BouaD3s1jq6uo4fR71ev0bb7zR4RM3btzYhUDFZOLW+uswKd9jjR8/njOSnZ3d
44HKzZs3582bp9G0p1SpVKrdu3e7KLzGjzccRoNWqxWvHoYcpRX1uC+++AJ/OHny5LS0tN4+6S8A
BCoAAIAQQjIxd1tRq9FxwUqdgTve2Q4nt8pa8Wk3QaApQ316sP2fp4kPluItPmrU5rIGEx6nOdz3
JZcIEGqfTLeaHN8ZNVm4YYm4PwoQ8zF9lVfE+UGV8n6SbeT240YLTdMM6SQeaNBaOEteg1xWJXbm
QoG21UQjhMRCYtwgJbKvzT1hkLetHEKYn9hgom2b08xWpkZtCe9oW1r3HThwAN9Q5L7jx4/n5OQM
Hjy4U8+qra3ljPTBXfzOam5uxpcaxGKxwx4p/ER/TlP57svLy5s3bx7+pkml0h07dtx3330unqVQ
KCIiIvAqBZytfTacKAUhFBoa2r3r7UBJSclXX32FjzzzzDNQldgdUPULAAAQQkgpE0jsF0ZqNY5v
fnOWAoQCorMdIarsq10Fq0S/4CgFIeQtFwQo298is5Vh+2nYxPCKdyGEguz3dLUYKH6dMYRQXQt3
rukhDTqcBQw9jtOy3MiL3O6O2717BIGcRSkIoesldsspIgHRhS7y1c3mvMq2+9mpsV4KiQBhYRWB
EL7yg+9D0xn7ougtf5eX+zi1wtyRlZXFGfHA/IQ//vGPIRhnLefxVQ6bnl2RKC0tnTdvXklJCTsi
Eol+/PHHyZMnu34iQRCTJk3CR65fv84/LD8/nzOSkJDQtUt107p16/CoOCYmZtasWb16xl8MCFQA
AKBNkMruJm55o5l/F19vojlZ4EHeIte7VGjejXWD/ct6y7kT63s0d8WFmEC7nV2cFAX+vi9kP4tF
CDEMyirnlh62UExRjd32Kh+FsFN9QnqPlFdjupfIJXaLUSYLXdnEjbEZBlXa7zpzsQyoM1IldXbv
alyItLPvKk0zp3O1th/kIJUo+W65MHZHJUEifH8XnhLWhaSvzrp9+/axY8e6/PRvvvnGxWoMv805
wzCcbWYDBgwIDw/v8gX0Ek7sdPDgwZqaGv5hR44c4YyEhYX11DVUV1cvWLAAbzaCENq8ebObM3vO
ksu2bdv4RQsOHDiAP0xPT3eYmt9TGhsbOWn0a9asuXc3/vUxj7jtBAAAniAxTIrvS7FSzNFbmhnD
fdkpmtnKHLml5syiEsLsJtlC3vSvkZc3TJIEQu0vUqs245twGAadyW3xnASVHhEXIr1yhzt7swnw
FvH71SCE/LyEob5iPAHjZqk+xEfEVkCmaeZ4loazzBIbzF2cya825lbqTRYmUCUaHecll/TdHbrf
PtBB0+7j2Ro8j0UiJB6d5KCclN5EXyrS1WssEhGRFC5LCLWb4oT5ijk5+qdvt8we5Yvvpjub18JJ
uA/xcVol+UapHg+VCYRSOl+V+MqdVnWrFSFEkmjCoPZCXoK70RtDI4pm2FgF/7XqgwSV3bt3c0by
8vJc3FbftGnTI488wj4sKio6e/Ys5+Y96/XXX09NTR0wYAA78sUXXxw8eBA/ZsWKFR6482fcuHH4
Q61W+9RTT3399df+/v7sYGZm5osvvogfFhUVlZKS0iMX0NDQsGTJkmvXruGD69evX7JkiZuvMHv2
7GeffZZ9WF1d/cYbb7z11ltsXa+LFy9+9NFH+FO6kHHUKd9//z1b0BkhJJVK8VIEwDUIVAAAoE1s
sNT3TiteL7hGbfnhbENMoEQuJfUmurTexJkWq+SCgSF2s0aSJCRCAu/PWNZg2pfZrJILLBQzKtZL
JRf4eQnxe94aPbU3s3lIpFwqItWt1vxqg+u2ffcilVzgrxTyYzbkZN+XzcgBigPNZvatpGjm5+vq
SH9JgFJoppjServ2IAghmZgcal+Z6naF4XRuWzJ3c6u1TmNZlO7XB/PgHkTRzL6rzeq7P5Y1agtF
22WMRAWI5RISr+jVYqC2nW9s66NiZSoazWpeFeyBoY5v6JqtDJ5zjxAK8xN3djddk856s6xtd19K
lAIvCqeQtgWKDEIldSa2eQ7ebKe3i7ZZrdZ169bhI2PGjHG9+Ye/6Wjbtm3OApWcnJy0tLTHH398
8ODBNE0fOXLkhx9+4ByzdOnSTl937xs7duyoUaMyMzPZkd27d2dmZj7xxBMDBw40Go2XLl1av349
ZzXpxRdfxFuaaDQavA/MBx98sHbtWnfOrtFoVqxYgXcaQQhlZGRIpVLX5Y/T09NjYmJsH0dFRa1e
vRpPCHnvvfdu3LixYMECuVx+69atTz/91GhsvzsQGBi4YMECdy6vawwGw4cffoiPrFq1qgcXoH7x
IFABAIB2GcmqPVea8Ju7RgudW+W4iqiAJDKSVfy7okEqUbn9NpuqZnNVM0IIJUfKERIkhck4m3Nq
NZZa3rZvnLUvNu33rphAicNAxeG+L5twP3FylBxvk8IwyNZwg38wgdDEwd6cvumc75261VrVbOZ3
pfRk1WoLJ8zIrTTggYqAJNLjlcez7X5+LBRTYL8pDhfhL3YWH2aV6Tl17bpQlVgkIKIDJCV1Jm+5
IDXWrl5cpL8k5263+zO5LUYL7a8UVTeb8++uLIkERIhvz/fExJ07d46TpbB48WLXTwkPD58xY8bP
P//MjmzatOnNN990mGuOEGpsbHz//fedvdratWt7agmiZ0kkkn//+9+TJ0/GQ5GKior/9//+n7On
ZGRkuO4QT5LurmF+9tlnhw8f5gweP378+PHjrp+4Z88eNlBBCP3973/fu3cvnoh/6NChQ4cOOXzu
e++9Fxzcwcpnd+zatau4uBgf6e0FnF8YyFEBAIB2AUrh5GSV0I2yUUIBkTHEO4jXxAO5MbGLC5G6
WEZwyGEe+b0lzlFAEqAUuu6VOWagcmCo00iGRRIofaCS39ec4qX7OGmr4LkoXsIG/4saGCodFetu
/egApXDKUMeNz2maya6w20XmLRN09mcVIaSUCaam+MxL88sYouKk7EcHSoJVbb81JitzNk+750rT
5SId+0WlRCvcrMvcZdu3b+eMTJkypcNnLVy4EH+o1Wo5u7lYrst5TZo06ZVXXunwdP1l3LhxW7du
lUo7/qVDCE2YMGHLli2u0y3c3+HGr+DcNWFhYT/++KOzGBL3pz/9aeXKlT1yUoesVitnOWXq1Kmp
qam9d8ZfHghUAADATkygZO4oX34bQVyAUjh7pG9ssOO/5VEBkmHRHcwapwxVJTiff8cESiLsy7Py
t+7cc3zkQn5fyJigDuZDBIEyhqjGDFRKnCdzKyTkzBG+KdEO4sNo+0m2TEyG9vLd+h4X6ivm1M6O
dhQ5jIr1mpri4zoDhyTQkEj53DQ/Z5nxuVVGTkjchWJfrCCVKEjl4N2emuLjrENoQqjM/YirazQa
zcaNG/GRwYMHDx06tMMn8nd/Oasb9umnn3KiGtbSpUu3bt3qzhy6H82fP//y5ctTp051cYyvr+9b
b73186y3jTcAACAASURBVM8/BwYGun61fknFGTt27PHjx11UCQsMDPz888//8Y9/uL/g0wVHjx69
cuUKPvL000/33ul+kWDrFwAAcAV4ixaM9iutN5XUm2o1FoOJMlOMWEDIJIIglSgmUNLhPeb0gV6h
vqKcCkN9i8VkoUmSkIpIf6WQnUeSJDFpiCopXJ5Toa9VW/RmGiEkFZPB3qKkcFmEvzirXF+BbQ/T
GqlGrdVfeW//px0TJOE0O493EuxxpETLE8Kk+VXGskaTptVqtDAMYmQi0l8pig6QJIRJnaWdjIr1
omimsMZotjIBSuGYgUpJJ5ve9DuxkJgx3Od8vrZBaxULifgQ6ahYx6VgBwRJogMD79QaS+tNDVqL
0UybKUZAEhIh4asQBvuIB4XLXEcynLpqYiExKKLnaxPJJeSC0X7Z5YY7tUa13mqlGLGQDPQWDoqQ
d2H1prMOHz7Mqa67bNkyd2arcXFx48ePP336NDty4MCBwsJCfjd0f3//bdu2/fTTTzt27Dh//nxN
TU1sbGx6evr8+fOnTJnigTn0fMnJyQcPHrx8+fKRI0fOnj1bVFRUVVXl7+8fGhqampo6ZsyYmTNn
Ogu3rFa733H++9M3hg0bdvDgwRMnThw9evTChQslJSVarTYmJiYpKWnatGnTp0/v1R1fNpys/bi4
uJkzZ/b2SX9hiL5qSNXOdkaapimKMpvNRqPRZDJ5YJE+AAAAAHi4iIiIyspKhNCBAwf6ZRZYVVXF
mcP015V4iLy8vKSkJPbhoUOHXC/OAM9UWVkpkUikUqlYLBYIBLZgvu/D7HvsxhIAAAAAAPBYeGtL
kUg0cuTIfrwYcK+DQAUAAAAAAPSMXbt2sR8/+uijeA8WADoLAhUAAAAAANAD8vPzv/32W9vHIpHo
hRde6N/rAfe6ezsvEwAAAAC/ZgkJCSEhIQgh10VyQd/Au8f85S9/SU5O7seLAb8AEKgAAAAA4F51
7Nix/r4E0IZhmMmTJ589ezYnJ2fu3LkvvfRSf18RuOdBoAIAAAAAALqLIIiHHnpo3rx5O3fufPDB
BxWK3m2JA34NIFABAAAAAAA9QyaTrVixor+vAvxCQKACAAAAANBFYWFhfd+SDoBfCaj6BQAAAAAA
APA4EKgAAAAAAAAAPA4EKgAAAAAAAACPA4EKAAAAAAAAwONAoAIAAAAAAADwOBCoAAAAAAAAADwO
BCoAAAAAAAAAjwOBCgAAAAAAAMDjQKACAAAAAAAA8DgQqAAAAAAAAAA8DgQqAAAAAAAAAI8DgQoA
AAAAAADA40CgAgBCCAkEgv6+hF+Ov//97/19CQAAAAC450GgAgAAAAAAAPA4EKgAAAAAAAAAPA4E
KgAAAAAAAACPA4EKAAAAAAAAwONAoAIAAAAAAADwOBCoAAAAAAAAADwOBCoAAAAAAAAAjwOBCgAA
AAAAAMDjQKACAAAAAAAA8DgQqAAAAAAAAAA8DgQqAAAAAAAAAI8DgQoAAAAAAADA40CgAgAAAAAA
APA4EKgAAAAAAAAAPA4EKgAAAAAAAACPA4EKAAAAAAAAwONAoAIAAAAAAADwOBCoAAAAAAAAADwO
BCoAAAAAAAAAjwOBCgAAAAAAAMDjQKACAAAAAAAA8DgQqAAAAAAAAAA8DgQqAAAAAAAAAI8DgQoA
AAAAAADA40CgAgAAAAAAAPA4EKgAAAAAAAAAPA4EKgAAAAAAAACPA4EKAAAAAAAAwONAoAIAAAAA
AADwOBCoAAAAAAAAADwOBCoAAAAAAAAAjwOBCgAAAAAAAMDjCPv7An6NKIq6ePHi9u3b9+/fn5eX
5/4TTSbToUOHTp06deHChYqKiubm5vDw8P/P3r3HVVXm/f+/OEoagwSouAHPmDamJsZtgCCGed+j
JmZKjTNOaaYhokFlmhqacnvAA6Y2pmZTv8TwpmE8gycENBNTQy1MQQ5KaIq4VbZsYP/+WH1Xuw1s
zuwFvJ5/XXuva13rAzOP4t26Dr17937uuef+8pe/9OnTp6EqzM7OTkxMPHTo0NWrV7Oystq3b+/q
6urh4eHv7+/v79+mTZsajnP27NnExMTk5OTs7OycnByVSuXm5ubj4+Pv7+/p6WlmZmb89tTU1B07
diQlJeXm5qpUKh8fn6CgIF9f32pvBAAAQLOna3Ll5eXl5eWlpaWPHj1Sq9W3bt3Ky8tr+jJMIjMz
c82aNf369ZN++SqVqub37tu3r2fPnkb+p3z99dd/+eWXelZYXFy8fPnytm3bVvWUwYMHp6SkVDtO
fn7+1KlTjVQbFBSUlZVV1e1arfbdd9+t9MaZM2c+evSonj9mRebm5g0+Zqv14YcfmroEAABQd3l5
ebdu3VKr1Y8ePSotLZX+em/6Mnij0hTu3buXkJDw5ZdfxsfH122E6Ojo0NBQ4322bduWkpKyf//+
7t271+0pWq02ODh427ZtRvqcPn36+eefj4+PHzFiRFV9CgoKRo8enZaWZmScmJiYs2fP7t+/v1u3
bhWvrlq1asWKFUIIW1vbyZMnd+vWLTs7+7PPPlOr1R9//LGDg8OHH35Y058KAAAAzZCZTqdr4kdK
TywvLy8rKyspKdFoNI8ePVKpVE1cRhOQp3ht3769sLCwYgeVSpWXl1ftOAcPHhw5cqT8cdSoUf/4
xz969+5tY2Nz8+bNpKSkNWvW3Lp1S7o6aNCg5OTkxx57rA4Fr1y5Un6PYWNjEx4ePmLEiA4dOmg0
moyMjK1btyYkJEhX7ezs0tPTXV1dKw6i0+nGjBmzZ88e6WOPHj1mz57t6enZvn37oqKi06dPr1+/
/scff5Su+vj4HD582MrKSn+EvLy8Xr16aTQaZ2fnI0eOPPnkk9L3ly9fHj58eF5enpWV1c8//9yl
SxeDR6elpRUVFQ0fPrwOP7uFhUVZWVkdbkRFERERixYtMnUVAACgjq5fv96mTRsbGxtra2sLCwtz
c3MhhAnm3jf9S5zWM/Vr8+bNFX/h7u7uHTt2lNo1mfpVVlY2cOBA+faoqKiysjKDPllZWQMGDJD7
bNmypQ7V5uTk2NraSiM4OTmdPXvWoINWq33//fflp0yfPr3ScXbv3i338fPzu3XrlkGHO3fu6Oeu
L774wqDDjh07pEsbN240uLR169aq7nr48KGHh4cQYubMmbX7yXU6HVO/GhRTvwAAaNYUMvWLXb8a
kf5/obezswsJCTl27NjFixfd3d1rPsiFCxfOnj0rtV9++eU5c+ZIoVZf165d9edr7dq1qw7VxsbG
qtVqqb1hwwb95COxtLSMiIjw8/OTPn7yyScFBQUVx5HjmZWV1ZYtWxwdHQ062Nvbb9myRQ5Fn3zy
iUEH+S1TxRrkzJabm2twad26ddJks9GjR1fxIwIAAKDZIKg0usDAwNjY2Ozs7OjoaF9fX0vL2q0L
unLlityeOHFiVS/dBg4cOHToUKl97Nix8vLy2tb59ddfS43evXuPHTu20j5WVlZz5syRPyYmJhp0
yM/Pl9+ovPHGGz169Kh0HJVKFRwcLLVTU1N/+ukn/aslJSVS4/HHHze4UV7lX1xcrP99enr6woUL
hRBvvvmmkcUzAAAAaC4IKo1o6NChOTk5cXFx48ePt7Ozq9sg9+7dk9vOzs5GesovajQazYMHD2r1
lBs3bpw6dUpqBwYGGiwa0efj4yNflW+R6S+gf+GFF4w8MSAgQG6fO3dO/5K8/bFBGhFCyD+X/hbJ
Wq12zpw5Wq1WpVJFREQYeSgAAACaC4JKI+rbt2+ly81rxd7eXm7fvXvXSM+bN2/KtxjZX7hSWVlZ
clt/SUyl9QwaNEhqnzlzxuCq/vufp556ysg4+lfltfUSeWeF8+fPG9x14cIFqdG5c2f5y61btx4+
fFgIsWrVKnn9DwAAAJo1gorSPfPMM3J73759VXW7ceOGvCXXiy++aGFhUaun6AcVNzc3453lbbjS
0tLkaVqSy5cvy23jO7k5OTnJb5kMpn55e3tLL20WL16sP2BOTs7ixYulto+Pj9TIzMycO3euEGLc
uHETJ040XjkAAACaC4KK0rm6uk6fPl1qb9iwYe/evRX7FBcXh4WFaTQa6eNbb71V26fo755c7Sw1
JycnqaHVag3mmMlvdZycnGxsbIwMYm5uLr9u+vXXX/Uvubi4SAtO8vLyPDw8Zs+evX79+nffffeZ
Z565evWqEOL999+Xzr4sLy8PDw8vKiqys7NbuXIlJ9YDAAC0GBz42Ax89NFHFy9eTE5OFkKMGjVq
3rx5EydO7NmzZ5s2be7cufPdd98tX75cuiqE2Lhx4+DBg2v7CP28Ue0ZLPrzyh48eKA/OU3eN6zi
Zl8VyYnozp07Bpfmzp179+7dqKgotVq9bt06/UszZsyQz+jYuXPnN998I4SIjIys8zGXAAAAUCCC
SjPg4OCwa9eu4OBgad/hZcuWLVu2rGI3Ozu7qKioKVOm1OER+kGl2mlj1tbWcttgvbu89L8mm5vJ
C+IrBhVLS8tVq1aNHTs2JiYmKSkpOzvb2dnZ19d34sSJ/v7+0puT/Pz8sLAwIcSwYcPq9lMDAABA
sQgqzUOHDh2+/vrruXPnrlixotIOLi4uR44c6dWrV93Gr8N2xpXeWFpaWodBqjoS3tvb29vbu6q7
Pvjgg/z8fCsrqzVr1uhnp7rR6XTsGNZQ+GUCAFobMzMznU5npCHPB0HNEVSah8LCwvfee+/TTz+t
qkNeXt7f/va3qKgoLy+vpizMVPbt2yedcblw4cL+/fvXf0AzMzP+CdJQIiIi+GUCAIB6YjF9M/Dr
r7+OGTNGTimjR4+OjY394YcfMjIykpOTly5d6uDgIIQ4deqUt7f3/v37TVpsUygsLAwNDRVCDBgw
YPbs2aYuBwAAAA2PoKJ0Op0uJCQkJSVF+vjPf/4zPj5+/Pjx/fr1c3d39/b2njdv3rlz5+Rj6SdO
nHj69GnT1dsUli5dKh3YsnbtWun0+uLi4u3bt48ZM8bV1bVz584jR47csGFDUVGRqSsFAABAHRFU
lC4xMTEmJkZqL1y4cNq0aRU34XVxcdmxY4eLi4sQQq1Wh4aG1natSJ039jVYNF+3cYxvZGwgJSUl
KipKCBEaGurr6yuEyMnJCQgIeO2113bv3p2Xl5efn3/w4MGZM2c+99xzly5dqkM9AAAAMDmCitJt
375datja2s6aNauqbp07d5bOPRRCnDx58sSJE7V6Srt27eS2wRmOFWm1WrltsJexvOPww4cPq32o
/CD9DY6Ne/DggfRL6Nq164IFC6RvgoKCUlNThRCDBg366KOPli9f7ufnJ4S4dOnSuHHj5KNdAAAA
0IwQVBTt0aNH8fHxUvt//ud/pLUoVQkICJDb8lSxGrK1tZXb8sGRVZEPSxEVgsoTTzwhNQzOcKzU
7du3pUa1R0zK1qxZc/bsWakh/Ta++uqrkydPCiEmTZqUmpo6f/78d99999ChQ+Hh4UKIjIyMTZs2
1XBwAAAAKAdBRdFu3rwpv5qQzmI3Qj7oXQiRmZlZqwfJAUMIcevWrWqrkhq2trb6CUfoHVpfVFRk
fIlIWVlZXl6e1HZ2dq5JkefPn1+8eLEQ4q9//euLL74ofblz506psXTpUvlgFgsLiw8++ECaC/fF
F1/UefNlAAAAmApBRdH0Dxip9hxG/Q7VTt8yoH+se05OjvHO6enpUmPw4MEGa1SefPJJuX39+nUj
g+Tn58tvZvr06VNthSUlJbNnz9ZqtQ4ODpGRkdJimPLy8uPHjwshBg4c6Obmpt/fzs7Ox8dHCHH1
6tWavN4BAACAohBUFE1/TpTxv/vFH2dbdejQoVYP0n9d8+233xrpeevWrXPnzkntp59+2uCqflCR
5mhV5eLFi3K7JudUbt68+dixY0KIFStWyO+OiouLpQUzPXr0qHiL3O3+/fvVjg8AAABFIagoWvv2
7eW3DQcPHjS+ekQ/YPTu3btWD3J0dBw2bJjUjouL01+FYiApKUluS68s9A0cONDKykpqy6trKnXw
4EG5/eyzzxov78qVK/PmzRNCjBw58u9//3vFDpXuNiYdB6vfAAAAQHNBUFE0MzOzcePGSe28vLyv
vvqqqp7FxcWrV6+WP1aMENUKCgqSGgUFBZ9//nmlfbRarfwUKysraXMtfY6OjhMmTJDasbGx3333
XaXj5OTkyGvc/f39u3TpYqSwsrKysLAwtVptY2MTFRWlP9msbdu20tbG165dq3hjbm6u1JDOWgEA
AEAzQlBRutdff10+ZiQkJCQhIaFinwcPHoSGhkpb9Aoh/va3v+lPwZJoNJqYmJjo6OiqjoMMDAzs
2LGj1H7nnXeOHj1q0KG0tHTBggXSFltCiFmzZukvwZdNnTpVbk+ZMiU7O9ugQ2Fh4dSpU+W3Q2+9
9Val9chiYmL+85//CCEWL17ct29f/UtmZmbSSZfnzp0zmBqnVqulPZrd3NwcHR2NPwIAAABKQ1BR
uu7du0dGRkrthw8fvvDCC1OmTNm7d+9PP/2UlZX1/ffff/rpp0OGDPn000+lPi4uLhERERXHCQsL
e+WVV0JDQ5999tlKNy92cnJasmSJ1NZoNP7+/uHh4cePH79y5cqlS5fi4uJGjRq1fPlyqYODg8Pb
b79dacF+fn7y7KwLFy54enquXr06LS0tMzPz3Llzn376qZeXV2JiotRh+PDhY8eONf4bCAgImD59
uqen58yZMyteffnll4UQWq120aJF8gEvOp0uKipK2hVg8uTJ1e5DAAAAAKUxa/rp+9ITy8vLy8rK
SkpKNBrNo0ePVCpVE5dhQkOHDk1OThZCqFQqeYteI3Q63fz58+W4YoRKpfrmm28GDx5s8H15ebmt
ra280/GiRYs+/PDDireXlZWFh4evXbvW+FPatm174MABI7PLCgsLx40bJ619N6Jfv3779++v4f/0
hYWFlZ4L+eDBg4CAAOk9j5eXV2BgoLW1dUJCwp49e4QQPXv2TElJkd8UGWFhYaG/xxrqIyIiYtGi
RaauAgAA1NH169fbtGljY2NjbW1tYWFhbm4uqlgS3Kh4o9IMmJmZLVu2bNeuXcaPUnnllVdOnjxZ
MaUIIczNzfW3AO7cuXOlI1hYWKxcuTI6OtrICYxDhgw5evSo8TUw9vb2u3btCgkJMdJn0qRJ+/bt
q3lArer0+nbt2sXExHh5eQkhUlNTw8PDZ82aJaWU3r17x8XF1SSlAAAAQGl4o2ICtX2jIisuLk5I
SEhOTj516lReXl5hYaFKpXJ3d/f29h4xYkS/fv2M3Hv69OmwsLDMzMzAwMDIyEjj68tv3Lhx8ODB
xMTEy5cvX7t2zdbW1s3NzcPDIyAgYNiwYfK5itW6cOFCQkLC0aNHr127lpub26lTp65du/r4+AQE
BFS701etFBcXx8bGxsXFpaWllZSUPP300y+++OKkSZOqijcV8UalAfFGBQCAZk0hb1QIKoAQBJUG
RVABAKBZU0hQYeoXAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIK
AAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQ
HIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAA
AABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUh
qAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAA
AMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIK
AAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMWxNHUBAAAAQEtz+UaxWlMuhHB3trF9
zMLU5TRLBBUAAACggW28sDuzKF8IMX9IoKeLm6nLaZYIKgAAAEADO3z78AV1uhDi1Xv/5SkIKnXB
GhUAAACgsVxXF5m6hOaKoAIAAAA0lgz1VVOX0FwRVAAAAAAoDkEFAAAAgOIQVAAAAAAoDkEFAAAA
gOKwPTEAAADQYNTFZZfzNWVlOlMX0uwRVAAAAIAGc11dtOPSufulD0xdSLNHUAEAAAAaxuUbxQey
L0Xd+MDUhbQEBBUAAACgYWy8sPv0rz+YuooWgqACAAAA/MGZzN8mbg3q3q5WNx6+ffjC/fRGqKg1
IqgAAAAAf+BxKEBq6KadMG0lrRnbEwMAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQ
HIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAULnMO3dr2FNdXJZfWKLT6Rq1nlbF
0tQFAAAAAAr1/a2M7k941qTnjovf7slK+0Vzs7FLaj0IKgAAAEB9pd39YXfhTlNX0aIw9QsAAACA
4hBUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAAColz1nCu+oS01dRUvD
OSoAAABAvYw+8xdTl9AC8UYFAAAAgOIQVAAAAIC60Jm6gJaNqV8AAABAjeiEMPt/7VN5OUtPfiOE
6G7nbMKSWjCCCgAAAFCNzWmpe7LShBCjunlM8/ASQuQ+yN9duFMI8efSfiYuroUiqAAAAACVS8rN
uHO/TAiRkJ+6u/DfQohO9tbThJep62oVCCoAAABA5T7O/ERq/Nm2ytcmOh1rVRoFi+kBAACAust6
mGXqElomggoAAABQdw/LH5i6hJaJoAIAAABAcQgqAAAAQDXKylmI0tQIKgAAAEA1fnxwQWpk3L4R
vueIaYtpJQgqAAAAQE0dLzocdeMDU1fRKhBUAAAAACgOQQUAAACA4hBUAAAAgNq5fKM4747W1FW0
cJxMDwAAANTOS0mzL6jTTV1FC8cbFQAAAACKwxsVEygrKzt16tSuXbv27t2bkZFRt0Hu3buXnJx8
6tSp9PT0jIyMmzdvuru7nzhxokEqzM7OTkxMPHTo0NWrV7Oystq3b+/q6urh4eHv7+/v79+mTZsa
jnP27NnExMTk5OTs7OycnByVSuXm5ubj4+Pv7+/p6WlmZmb89tTU1B07diQlJeXm5qpUKh8fn6Cg
IF9f32pvBAAAaFRq7X1Tl9DyEVSaVFZWVnx8/LZt29LT04UQKpWqDoMUFBRs2LBh7dq1arVa/3ud
rgHOIdJoNNHR0REREQ8fPpS/vH379tWrV48dO7Zq1arBgwevWbPGy8vL+Di//PLLggULtmzZov9l
UVHRpUuXDhw4IIQICgqKjIzs2rVrpbeXlpbOnz9/xYoVBvf+85//nDlzZlRUlLW1dZ1/RgAAgHrK
1mSZuoSWj6DSFO7du5eQkPDll1/Gx8fXc6jdu3fPmDHj+vXrDVKYAa1WGxwcvG3bNiN9Tp8+/fzz
z8fHx48YMaKqPgUFBaNHj05LSzMyTkxMzNmzZ/fv39+tW7eKV1etWiWlFFtb28mTJ3fr1i07O/uz
zz5Tq9Uff/yxg4PDhx9+WNOfCgAAAM0QQaURyVO8tm/fXlhYWP8BP/3002nTpul/M2bMGF9fX3d3
dzs7O3t7+3qOv3btWjml2NjYhIeHjxgxokOHDhqNJiMjY+vWrQkJCUIIjUYzYcKE9PR0V1fXioPo
dLqpU6fKKaVHjx6zZ8/29PRs3759UVHR6dOn169f/+OPPwohMjIyJk+efPjwYSsrK/0R8vLyIiIi
hBDOzs5Hjhx58sknpe+Dg4OHDx+el5e3bNmy1157rUuXLgaPTktLKyoqGj58eD1/DwAAADA5gkoj
2rZtm0GuEEK4u7sXFRUVFBTUdrT9+/frjxYcHBwaGtqrV6/6Vvn/5ObmLlmyRGo7OTklJCQMGDBA
vtq/f/9x48YtXLgwMjJSCFFUVLRs2bJNmzZVHGfv3r179uyR2n5+frGxsY6OjvJVDw+PoKCgV199
VZoAlpycvHPnzkmTJumPkJKSotFohBALFiyQU4oQwt3dPSIiYsqUKVqtNjk52SCoFBcXz5gxIy0t
bebMmevXr6/fLwMAAAAmxq5fjaisrExu29nZhYSEHDt27OLFi+7u7rUdqrCwMCQkRGrb2Njs2rXr
448/bsCUIoSIjY2VF71s2LBBP6VILC0tIyIi/Pz8pI+ffPJJpXFr8+bNUsPKymrLli36KUVib2+/
ZcsWW1tbeRyDDnl5eVKjYg0DBw6UGrm5uQaX1q1bJ73GGT16dBU/IgAAAJoNgkqjCwwMjI2Nzc7O
jo6O9vX1tbSsy1usyMjIq1evSu0vvvjipZdeatAahRDi66+/lhq9e/ceO3ZspX2srKzmzJkjf0xM
TDTokJ+fv3v3bqn9xhtv9OjRo9JxVCpVcHCw1E5NTf3pp5/0r5aUlEiNxx9/3ODGtm3bSo3i4mL9
79PT0xcuXCiEePPNN40sngEAAKhWYtYlU5cAIQgqjWro0KE5OTlxcXHjx4+3s7Or8zg3b96U5zLN
mjVr/PjxDVTg727cuHHq1CmpHRgYaLBoRJ+Pj498Vb5Fpr+A/oUXXjDyxICAALl97tw5/Uvy9scG
aUQI8eDBA4M+QgitVjtnzhytVqtSqaTFLQAAAHVWVKKuvlONqYvLqu+EyhBUGlHfvn0rXW5eW7t3
75bWbNjY2Lzzzjv1H7CirKzft9iTp1dVyt7eftCgQVL7zJkzBlevXLkit5966ikj4+hfldbWy+Rd
m8+fP29w14ULF6RG586d5S+3bt16+PBhIcSqVas6duxo5KEAAABN7MJ9DrCvI4JKM/Cvf/1Laowf
P97FxUVqa7XagoKCn3/+uaCgoLS0tJ6P0A8qbm5uxjvLC9zT0tLkaVqSy5cvy23jp8Q4OTnJb5kM
nona4wAAIABJREFUpn55e3tLL20WL16sP2BOTs7ixYulto+Pj9TIzMycO3euEGLcuHETJ040XjkA
AACaC4KK0t29e/f48eNSe9SoUUKIlJSU6dOnOzs7d+rUyd3dvVOnTi4uLqGhoT/88EOdn6K/e3K1
s9ScnJykhlarlediSW7evCn3sbGxMTKIubm5/Lrp119/1b/k4uIiLTjJy8vz8PCYPXv2+vXr3333
3WeeeUZaqPP+++/37NlTCFFeXh4eHl5UVGRnZ7dy5UpOrAcAAPW0OS11zZndpq4CQrA9sfJlZGTI
bRcXlxkzZlTcJqugoCA6Ojo6OnrZsmXvvfeeuXmt86d+3njssceMd5ZXtEs36p/fIu8bVnGzr4rk
RHTnzh2DS3Pnzr17925UVJRarV63bp3+pRkzZixatEhq79y585tvvhFCREZGdu/evdonAgAAGJd2
94cT94+YugoIQVBRPv31G3Pnzk1JSTHSed68eWq1etmyZbV9in5QsbCwMN7Z2tpabhusd793757U
qMnmZvKC+IpBxdLSctWqVWPHjo2JiUlKSsrOznZ2dvb19Z04caK/v7/05iQ/Pz8sLEwIMWzYsClT
plT7OAAA0OzodLommDHRNE9BbRFUlE7/wBAppbi5uc2fPz8gIEClUpWUlPz4448bN27cvn271Ccy
MvK5556TJonVXHl5ed3KM7ixbqtl9A+c0eft7e3t7V3VXR988EF+fr6VldWaNWv0s1Pd6HQ6dgxr
KPwyAQDNV7bqYcMOqCnWREREyPNBUHMEFaWT31FI/P39d+zY0aFDB+mjtbX14MGDP/vssz59+rz3
3nvSl+Hh4SNGjKj/3+5Ktm/fvm3btgkhFi5c2L9///oPaGZmxj9BGgr/OAYANF/TDm0SmckNOKDN
Yzb8a7FuWEyvdEVFRXL7v/7rv/7v//5PTin6wsPDx40bJ7UzMjIOHTrURPWZQmFhYWhoqBBiwIAB
s2fPNnU5AAAAaHgEFaXTf6OyePHi9u3bV9rN3Nw8PDxc/nj06NFGr8x0li5dKh3YsnbtWun0+uLi
4u3bt48ZM8bV1bVz584jR47csGGDfsYDAABA88LUL6V79OiR3B42bJiRnp6eniqV6vr160KIpKSk
Wj2lzgvIDBbN120c4xsZG0hJSYmKihJChIaG+vr6CiFycnJeffXV1NRUuU9+fv7Bgwc3btwYGxvb
t2/fOpQEAAAA0+KNitLVfKmJubm5l5eX1DY4QrFa7dq1k9sGZzhWpNVq5bbBXsbyjsMPH1a/EE1+
kP4Gx8Y9ePBg1qxZQoiuXbsuWLBA+iYoKEhKKYMGDfroo4+WL1/u5+cnhLh06dK4cePko10AAADQ
jBBUlE7/j3iNRmO8s7x8Ra1W1yQqyGxtbWv+FPmwFFEhqDzxxBNSw+AMx0rdvn1balR7xKRszZo1
Z8+elRoODg5CiK+++urkyZNCiEmTJqWmps6fP//dd989dOiQNBEuIyNj06ZNNRwcAADg1oN71XdC
kyCoKJ38p7+o7LwRA/q7A9dq1y/9p9y6dct4Z/kdha2trX7CEXqH1hcVFRlfIlJWVpaXlye1nZ2d
a1Lk+fPnFy9eLIT461//+uKLL0pf7ty5U2osXbpUPpjFwsLigw8+cHFxEUJ88cUXdd58GQAAtB6Z
d+7+77Hj39/9wdSF4DcEFaXr06eP3NY/pb5S+fn5UsPNza0mRy7K9I91z8nJMd45PT1dagwePNjg
KU8++aTcllbLGClVfjOj/zNWpaSkZPbs2Vqt1sHBITIyUloMU15efvz4cSHEwIED3dzc9Pvb2dn5
+PgIIa5evVqT1zsAAKCV+/5WxvuX5+Y8yjJ1IfgNQUXp9A8JOXLkiJGeJSUl0l/tQohnn322Vk/p
2bOn3P7222+N9Lx169a5c+ek9tNPP21wVT+oSHO0qnLx4kW53atXr2or3Lx587Fjx4QQK1ascHV1
lb4sLi6WFsz06NGj4i1yt/v371c7PgAAABSFoKJ0Tz311MCBA6X2Z599ZuTlQFJSUmFhodQ2cqB7
pRwdHeUtxeLi4vRXoVR8ityWXlnoGzhwoJWVldSOj4838sSDBw/K7Wpj1ZUrV+bNmyeEGDly5N//
/veKHSrdbUyn0xk0AAAA0FwQVJTOwsLirbfektoFBQVLly6t9M/uR48eLVmyRP74l7/8pbYPCgoK
kp/y+eefV9pHq9WuXr1aaltZWUmba+lzdHScMGGC1I6Njf3uu+8qHScnJ0de4+7v79+lSxcjhZWV
lYWFhanVahsbm6ioKP3JZm3btpW2Nr527VrFG3Nzc6WGdNYKAAAAmhGCSjPwyiuveHh4SO21a9eu
XLmyrKxMv4NGo3n77beTk5Olj1OnTtWfyiX3iYmJiY6OPn36dKVPCQwM7Nixo9R+5513Kh4ZWVpa
umDBAmmLLSHErFmz9Jfgy6ZOnSq3p0yZkp2dbdChsLBw6tSp8t5icgyrSkxMzH/+8x8hxOLFiw0O
RTEzMxs6dKgQ4ty5cwZLYtRq9YkTJ4QQbm5ujo6Oxh8BAAAApSGoNAPt2rXbuHGjfCrie++9N2bM
mLi4uB9++OHMmTP/+te//Pz8Nm7cKF3t1q3bRx99VHGQsLCwV155JTQ09Nlnn01JSanYwcnJSX4n
o9Fo/P39w8PDjx8/fuXKlUuXLsXFxY0aNWr58uVSBwcHh7fffrvSav38/OTZWRcuXPD09Fy9enVa
WlpmZua5c+c+/fRTLy+vxMREqcPw4cPHjh1r/McPCAiYPn26p6fnzJkzK159+eWXhRBarXbRokXy
AS86nS4qKkraFWDy5MkWFhbGHwEAAAClMWv66fvSE8vLy8vKykpKSjQazaNHj1QqVROXYUJDhw6V
3n6oVCp5i95qHThwIDAw0PghJy4uLt988438+kVWXl5ua2srn6yyaNGiDz/8sOLtZWVl4eHha9eu
NV5J27ZtDxw4UHGBiqywsHDcuHHS2ncj+vXrt3///hr+T19YWFjpuZAPHjwICAiQ3vN4eXkFBgZa
W1snJCTs2bNHCNGzZ8+UlBT5TZERFhYWBu+pUGcRERGLFi0ydRUAANTOroxTLyfNafBh/2zbL/2V
fzb4sI3q+vXrbdq0sbGxsba2trCwMDc3F1UsCW5UvFFpNkaOHHn8+HH57PmKxowZc+TIkYopRQhh
bm6uvwVw586dKx3BwsJi5cqV0dHRRk5gHDJkyNGjR42kFCGEvb39rl27QkJCjPSZNGnSvn37ah5Q
qzq9vl27djExMdKvJTU1NTw8fNasWVJK6d27d1xcXE1SCgAAAJSmFkdtwOQGDx58+PDho0eP7t27
9+zZs5cvX37ssce6d+/u5eX1wgsveHt7G0m6mzZtCgsLy8zMDAwMfPXVV6vqZmlpGRIS8tJLLx08
eDAxMfHy5cvXrl2ztbV1c3Pz8PAICAgYNmyYfK6iEQ4ODtHR0dOmTUtISDh69Oi1a9dyc3M7derU
tWtXHx+fgICA2m6gbISbm1tiYmJsbGxcXFxaWlpJScnTTz/94osvTpo0qap4AwAAAIVj6hcgBFO/
GhRTvwAAzRFTv2RM/QIAAACAyhFUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAAACgO
QQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAA
ACgOQQUAAACA4hBUAAAAACgOQQUAAACA4hBUAAAAACgOQQUAAACtXVrOr0m5GaauAn9gaeoCAAAA
ABN7LXX+BXW6qavAH/BGBQAAAIDiEFQAAAAAKA5BBQAAAIDisEYFAAAArVR+YYmpS0CVCCoAAABo
pfz2zJQa1pZmpq0EFRFUAAAA0EpdLr4gNf5s28+0laAi1qgAAACgtbtXct/UJcAQQQUAAACtXc6j
LFOXAEMEFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgEFQAAAACK
Q1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDiWpi4A
AAAAaGpHr2Sdyss1dRUwhqACAACAVmfHtQOfZn5h6ipgDFO/AAAAACgOQQUAAACA4hBUAAAAACgO
QQUAAACA4hBUAAAAACgOQQUAAACA4rA9MQAAAFqRvHtF+36+mFn0SyM/x8zG/DE7C3t7S0dtmc7K
wqyRH9cCEVQAAADQinyb/9ObZ8Ibb/w25jbD/zR60OPPuVh3lb757OhNB1ur7h3a/NmtLYml5ggq
AAAAQMPwaOc10XHqnyzaSx9LRakQwlJY3lZrb6u1F3IfevX+U/eObUxaY7NBUAEAAAAagN+f/vsV
x2lCiG/VR888OJmlyVCX3xNC2Jr/qZtN70HthvyX7bBD6Xe9Smyfcm1r6mKbAYIKAAAAUF/92z77
iuO0n4t//PrOlpxHmfqX1OX3fnh4+oeHpw/f2zPBYarI6PO4jUUXJ96rVINdvwAAANDylZTq8gtL
8gtL7j0sa4zxxzv848yDE6vy5xmkFH05jzJX3Zh35sGJb3++3xg1tDC8UQEAAEDLt/5M4ubLu4QQ
D8seNPjg3rYB6rK7mwtW1qTz5oKV7S3s+1/3fFL1WINX0pIQVAAAANDyZaivXi6+0EiDD2jn+fXt
bTXv//XtbcNuDSCoGMfULwAAAKBe7pT+eu3RlZr3v/boyu68I41XT8tAUAEAAADq5afi87W95dui
1MaopCUhqAAAAAD1kvXo59rfcrkxKmlJCCoAAABAvRSW/lr7W243RiUtCUEFAAAAgOIQVAAAAIB6
sRLWtb3FpW2nxqikJSGoAAAAAPWiFSW1vcXb+c+NUUlLQlABAAAAmtrL3f1NXYLSEVQAAACAJjXU
ecC4bn6mrkLpCCoAAABAg9DVpJO5mdm65+Y0diktAEEFAAAAaBBm1WYVczOzPSNXDXDo1TQFNWuW
pi4AAAAAaDHMqrxgZubn/MyaIbP6k1JqhqACAAAANCI7K9sXu3q/1N1vTBcfU9fSnBBUAAAAgEY0
wXXs5mEzTF1F88MaFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgEFQAAAACKQ1ABAAAAoDgE
FQAAAACKQ1ABAAAAGpGtjYWpS2iWCCoAAAAAFIegAgAAADSip9r3NHUJzRJBBQAAAGhEf7JqZ+oS
miWCCgAAAADFIagAAAAAUByCCgAAAFq4Dw7vTy04Z+oqUDuWpi4AAAAAaFxLry4xdQmoNd6oAAAA
AFAcggoAAAAAxSGoAAAAAFAcggoAAAAAxSGoAAAAAFAcggoAAAAAxSGoAAAAAFAcggoAAAAAxSGo
AAAAAFAcggoAAAAAxSGoAAAAAFAcS1MXAAAAADSWzWmpe7LSTF0F6oI3KgAAAGix0u7+sLtwp6mr
QF0QVAAAAAAoDkEFAAAAgOIQVAAAAAAoDkEFAAAAgOKw65cJlJWVnTp1ateuXXv37s3IyKjnaAcO
HPjv//5v+aNOp6vngEKI7OzsxMTEQ4cOXb16NSsrq3379q6urh4eHv7+/v7+/m3atKnhOGfPnk1M
TExOTs7Ozs7JyVGpVG5ubj4+Pv7+/p6enmZmZsZvT01N3bFjR1JSUm5urkql8vHxCQoK8vX1rfZG
AAAANHcElSaVlZUVHx+/bdu29PR0IYRKparngHfv3g0NDW2I0n6j0Wiio6MjIiIePnwof3n79u2r
V68eO3Zs1apVgwcPXrNmjZeXl/FxfvnllwULFmzZskX/y6KiokuXLh04cEAIERQUFBkZ2bVr10pv
Ly0tnT9//ooVKwzu/ec//zlz5syoqChra+s6/4wAAABQPoJKU7h3715CQsKXX34ZHx/fsCNHRkZe
vny5oUbTarXBwcHbtm0z0uf06dPPP/98fHz8iBEjqupTUFAwevTotDRje5bHxMScPXt2//793bp1
q3h11apVUkqxtbWdPHlyt27dsrOzP/vsM7Va/fHHHzs4OHz44Yc1/akAAADQDBFUGpE8xWv79u2F
hYUNPv6JEyf03znU39q1a+WUYmNjEx4ePmLEiA4dOmg0moyMjK1btyYkJAghNBrNhAkT0tPTXV1d
Kw6i0+mmTp0qp5QePXrMnj3b09Ozffv2RUVFp0+fXr9+/Y8//iiEyMjImDx58uHDh62srPRHyMvL
i4iIEEI4OzsfOXLkySeflL4PDg4ePnx4Xl7esmXLXnvttS5duhg8Oi0traioaPjw4Q34OwEAAIBJ
sJi+EW3bts3Ly2vNmjX6KcXd3b1jx471H/zhw4ezZs2q/ziy3NzcJUuWSG0nJ6eTJ08uWbLEx8en
d+/e/fv3nzBhwt69e99//32pQ1FR0bJlyyodZ+/evXv27JHafn5+33777cyZMwcPHtyrVy8PD48Z
M2akpqaOHDlS6pCcnLxzp+EZTCkpKRqNRgixYMECOaUIIdzd3aUAo9Vqk5OTDe4qLi6eMWPG888/
HxISUp/fAwAAQMNytLWqvhMqIKg0orKyMrltZ2cXEhJy7Nixixcvuru713/wdevWnTlzRgjRrVs3
T0/P+g8YGxurVqul9oYNGwYMGGDQwdLSMiIiws/PT/r4ySefFBQUVBxn8+bNUsPKymrLli2Ojo4G
Hezt7bds2WJrayuPY9AhLy9PalSsYeDAgVIjNzfX4NK6deuk1zijR4+u4kcEAABAs0FQaXSBgYGx
sbHZ2dnR0dG+vr6Wlg0w3e6HH35YtGiR1F65cqWTk1P9x/z666+lRu/evceOHVtpHysrqzlz5sgf
ExMTDTrk5+fv3r1bar/xxhs9evSodByVShUcHCy1U1NTf/rpJ/2rJSUlUuPxxx83uLFt27ZSo7i4
WP/79PT0hQsXCiHefPNNI4tnAABAK/H59+f+99jx/z12/NaDe6auRfh1fsbUJTRLBJVGNHTo0Jyc
nLi4uPHjx9vZ2TXUsCUlJbNnz9ZqtUKICRMmjBs3rv5j3rhx49SpU1I7MDDQYNGIPh8fH/mqfItM
fwH9Cy+8YOSJAQEBcvvcuXP6l+Ttjw3SiBDiwYMHBn2EEFqtds6cOVqtVqVSSXPDAABAK7cqY9P7
l+e+f3nulYeZpq4FdURQaUR9+/atdLl5PW3ZsuXo0aNCCHt7++XLlzfIoSJZWVlyW55eVSl7e/tB
gwZJbWnumb4rV67I7aeeesrIOPpXpbX1MnnX5vPnzxvcdeHCBanRuXNn+cutW7cePnxYCLFq1aoG
Wf8DAAAAkyOoNDNXr16dO3eu1F6+fHlV55DUln5QcXNzM95ZXuCelpYmT9OS6O+VbPyUGCcnJ/kt
k8HUL29vb+mlzeLFi/UHzMnJWbx4sdT28fGRGpmZmdIvZNy4cRMnTjReOQAAAJoLgkpzUl5eHh4e
Li15DwgI+Mc//tFQI+vvS1btLDV5SYxWq5XnYklu3rwp97GxsTEyiLm5ufy66ddff9W/5OLiIi04
ycvL8/DwmD179vr16999991nnnnm6tWrQoj333+/Z8+e4v/9QoqKiuzs7FauXMmJ9QAAwEBZmc7U
JaCOOEelOdmxY8e///1vIYSVlVVUVJSRlSS1pZ83HnvsMeOd5RXt0o329vbyR3nfsIqbfVUkJ6I7
d+4YXJo7d+7du3ejoqLUavW6dev0L82YMUPeSGDnzp3ffPONECIyMrJ79+7VPhEAALQ2Pz68YOoS
UEcElWbjxo0bYWFhUjsiIqJfv34NOLh+ULGwsDDe2draWm4brHe/d++3jTVqsrmZvCC+YlCxtLRc
tWrV2LFjY2JikpKSsrOznZ2dfX19J06c6O/vL705yc/Pl34hw4YNmzJlSrWPAwCgaeh0OulfVXKj
Ue+tz+MqDlLzp9TncTWvp1Gf0jS6PN7J1CU0VwSVZmPevHnSuSUDBw4MDQ1t2MHLy8sb5MbS0tI6
DKJ/4Iw+b29vb2/vqu764IMP8vPzrays1qxZo5+d6kan07FjWEPhlwkAMDmNq8bUJfzmtZ/7R0RE
yPNBUHMEleZh9+7dn3/+udSOjo7Wn3zVOu3bt2/btm1CiIULF/bv37/+A5qZmfFPkIbCP44BACa3
a8ebQm3qIoQQQvDvxDpjMX0zcOfOHfmYxbffftvIS4ZWorCwUHqnNGDAgNmzZ5u6HAAAADQ8gkoz
sGTJEmm3qx49esyfP9/U5Zje0qVLpQNb1q5dK51eX1xcvH379jFjxri6unbu3HnkyJEbNmwoKioy
daUAAACoI6Z+KV1SUtLatWul9urVq5944onGeEqdl6kZLJqv2zjGNzI2kJKSEhUVJYQIDQ319fUV
QuTk5Lz66qupqalyn/z8/IMHD27cuDE2NrZv3751KAkAAACmRVBRtPv378tTmyZNmjR69OhGelC7
du3ktsEZjhVptVq5bbCXsbzj8MOHD6t9qPwg/Q2OjXvw4MGsWbOEEF27dl2wYIH0TVBQ0MmTJ4UQ
gwYNCgwMtLKy2r9//7Fjxy5dujRu3Ljjx4936NChhuMDAABAIQgqirZ69epz584JIWxsbIKDg/Pz
8yvt9ujRI7l948YNud2hQ4eabBMshLC1tZXbGk01u2TIh6WICkFFfuFjcIZjpW7fvi01qj1iUrZm
zZqzZ89KDQcHByHEV199JaWUSZMmbdmyRdryOCwsbO7cuatWrcrIyNi0aROL2AAAAJodgopypaen
y39hazSaIUOG1OQulUolt69fv965c+ea3KU/o+zWrVvGO8vHz9va2uonHKF3aH1RUZF0YHxVg5SV
leXl5UltZ2fnmhR5/vz5xYsXCyH++te/vvjii9KXO3fulBpLly6VD2axsLD44IMPYmJi8vLyvvji
iwULFpibsxwLAACgOeGvN+WSFtA3Df1j3XNycox3Tk9PlxqDBw82eGPz5JNPyu3r168bGSQ/P19+
M9OnT59qKywpKZk9e7ZWq3VwcIiMjJQWw5SXlx8/flwIMXDgQDc3N/3+dnZ2Pj4+QoirV6/W5PUO
AAAAFIWgAiGE6Nmzp9z+9ttvjfS8deuWNBtNCPH0008bXNUPKtIcrapcvHhRbvfq1avaCjdv3nzs
2DEhxIoVK1xdXaUvi4uLpQUzPXr0qHiL3O3+/fvVjg8AAABFIago19ixY3U1M2rUKPku/e9rOO9L
COHo6Dhs2DCpHRcXp78KxUBSUpLcll5Z6Bs4cKCVlZXUjo+PN/LEgwcPyu1nn33WeHlXrlyZN2+e
EGLkyJF///vfK3aodLcxnU5n0AAAAEBzQVDBb4KCgqRGQUHB559/XmkfrVa7evVqqW1lZeXn52fQ
wdHRccKECVI7Njb2u+++q3ScnJycTZs2SW1/f/8uXboYKaysrCwsLEytVtvY2ERFRelPNmvbtq20
tfG1a9cq3pibmys1pLNWAAAA0IwQVFoLjUYTExMTHR19+vTpSjsEBgZ27NhRar/zzjtHjx416FBa
WrpgwQJpiy0hxKxZsyo91GXq1Klye8qUKdnZ2QYdCgsLp06dKu8t9tZbbxmvPCYm5j//+Y8QYvHi
xQaHopiZmQ0dOlQIce7cOYMlMWq1+sSJE0IINzc3R0dH448AAAAtQ+zFdFOXgAZDUGktwsLCXnnl
ldDQ0GeffTYlJaViBycnpyVLlkhtjUbj7+8fHh5+/PjxK1euXLp0KS4ubtSoUcuXL5c6ODg4vP32
25U+yM/PT56ddeHCBU9Pz9WrV6elpWVmZp47d+7TTz/18vJKTEyUOgwfPnzs2LHGKw8ICJg+fbqn
p+fMmTMrXn355ZeFEFqtdtGiRfIBLzqdLioqStoVYPLkyRYWFsYfAQAAWobwtP9VF5eZugo0DLYn
bhXKy8u3b98ufzx06JC3t3fFbq+//vqlS5fWrl0rfYyKipLOgDfQtm3bb775xsgCmLVr1+bk5Ehr
3wsKCsLCwirt1q9fv88//7zaFNGhQ4dNmzYVFhYanNkieeWVV7Zt23by5MmtW7f+9NNPgYGB1tbW
CQkJe/bsEUL07NkzODjY+PgAAKDFyHmU9e7xLza98A9TF/KbDtacOl13vFFpFczNzfW3AK4qY1hY
WKxcuTI6OtrI+SdDhgw5evRoxWX0+uzt7Xft2hUSEmKkz6RJk/bt26d/6otxVZ1e365du5iYGC8v
LyFEampqeHj4rFmzpJTSu3fvuLg4eT4bAABoDf6V+/8dvZJl6ip+06ENf4fUHW9UWotNmzaFhYVl
ZmYGBga++uqrVXWztLQMCQl56aWXDh48mJiYePny5WvXrtna2rq5uXl4eAQEBAwbNkw+V9EIBweH
6OjoadOmJSQkHD169Nq1a7m5uZ06deratauPj09AQEC1O33VnJubW2JiYmxsbFxcXFpaWklJydNP
P/3iiy9OmjSpqngDAABaqoflD0Ydm/aYeTtTF4L6Mmv6nVulJ5aXl5eVlZWUlGg0mkePHtX8v6wD
jcHCwqKsjCmtDSMiImLRokWmrgIA0BqZbX7O1CX8wZ9t+6W/8k9TV1Fr169fb9OmjY2NjbW1tYWF
hbm5uajiNIhGxdQvAAAAAIpDUAEAAAAahSV/a9cDvzwAAACgUZg3+XSploSgAgAAADSK3rbdTV1C
M0ZQAQAAABrF41a2pi6hGSOoAAAAAFAcggoAAAAAxeHARwAAADR7JaW622qtqatAQyKoAAAAoNlb
dipuR+ZBU1dhqLO9talLaMaY+gUAAIBm70bxzcvFF0xdxR/0bd+zq20nU1fRjPFGBQAAAGh4Ef2D
x7t7mrqKZow3KgAAAEDDs7bgL+164dcHAAAANDw3+/amLqF5I6gAAAAADW+AQy9Tl9C8EVQAAAAA
KA5BBQAAAIDiEFQAAAAAKA5BBQAAAPgDJ+sOpi4BBBUAAADgjzq26WjqEkBQAQAAABraAEfmGsYR
AAAgAElEQVR3U5fQ7BFUAAAAAEO6aSfqfO+fbfudHbe94WpppQgqAAAAABSHoAIAAABAcQgqAAAA
ABSHoAIAAABAcQgqAAAAABSHoAIAAABAcQgqAAAAABSHoAIAAABAcSxNXQAAAABQd6fycpae/CZD
c9HUhfzOweZxU5fQEhBUAAAA0FzphMh9kL+7cKepC/mDoZ2eMXUJLQFBBQAAAM2P9CJFCPFr6U1T
12Lo6Sd6mrqEloCgAgAAgOZHgS9S0LBYTA8AAAA0pLbWFqYuoSXgjQoAAADQYHTTTpi6hBaCNyoA
AAAAFIegAgAAADSMthbtTF1Cy0FQAQAAABpG97bdTV1Cy0FQAQAAABpG18c7mbqEloOgAgAAADQM
58cIKg2GoAIAAAD8gWvbOuaNTu3+1LCVtGYEFQAAAOAPXNrVMai80MWjYStpzQgqAAAAaGYybt4p
LTN1EZXx6tzb1CW0HBz4CAAAgGbmmf9MdGnTzdRVGHKy7mDqEloU3qgAAACgmXlY/uBy8QVTV2HI
2YaV9A2JoAIAAABUolstD0XxdOzfSJW0TgQVAAAAoBLtannMvJONbSNV0joRVAAAAIC66Na2+9mX
Ppc/DnTqZcJiWh6CCgAAAFAX7SzaDXDodXTUx7ppJ6b3/PtQ176mrqhFYdcvAAAANAN594r2/XxR
CGFr+bipa/kDv87PCCEGd3Dv0JapXw2JoAIAAIBm4Nv8n948E27qKqr0+p/9TV1CS8PULwAAAACK
Q1ABAAAAoDgEFQAAAACKQ1ABAAAA/sDC3MzUJYCgAgAAAPzRcNVAU5cAdv0CAACA4n1w/P9OFJw3
dRWGLHjv0pgIKgAAAFC6+OsJF9Tppq7C0LOOA0xdQkvG1C8AAADgd2NUI6TGY1a8MTElggoAAADw
u2GdB1pbmAshvhv/Sazvmkr7dGzTYdGgKa/29Wza0loXpn4BAAAAv3Np2+npji6VXvJ1GvKntpYh
fScEuA5q4qpaIYIKAAAA8AddbZ0rfnl01MddbZ0rvYTGQFABAAAAKvd8t6dE0m9tv87PmLSWVoeg
AgAAAFSuvfXjumknTF1FK8ViegAAACiUTuhMXQJMhjcqAAAAUKg+X0yXsoq1JTsFtzoEFQAAACjU
5eILUlD5s20/U9eCpsbULwAAAACKQ1ABAACA0ul0LFZpdQgqAAAAULqL9y+YugQ0NYIKAAAAAMUh
qAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAAAMUhqAAAAABQHIIKAAAA
AMUhqAAAAAC/s7bgL2RFsDR1AQAAAIAhdXHZfU2ZMBNC19SPHurWp6kficoQVAAAAKAsvb+YJjV0
uiaPKUK0t3686R+KiggqAAAAUJbLxRdMXQJMjxl4AAAAABSHoAIAAAAFKSk1wXQvKBBBBQAAAAry
n6vfmboEKAJBBQAAAIDiEFQAAAAAKA5BBQAAAIDiEFQAAAAAKA5BBQAAAIDiEFQAAAAAKA4n0wMA
AABCCNH/T/3G9HzW1FXgN7xRAQAAAIQQ4lnHAYs9ppi6CvyGoAIAAABAcQgqAAAAgBBCdP9TJ1OX
gN8RVAAAAAAhhOhp19nUJeB3BBUAAAAAikNQAQAAAETPx3s427Y3dRX4HUEFAAAAEOuGhHp17m3q
KvA7ggoAAAAg/qebh6lLwB9w4KMJlJWVnTp1ateuXXv37s3IyKj5jXfv3j1w4EBKSsr3339//fp1
tVrt4uLSp0+f55577i9/+UvPnj0bqsLs7OzExMRDhw5dvXo1Kyurffv2rq6uHh4e/v7+/v7+bdq0
qeE4Z8+eTUxMTE5Ozs7OzsnJUalUbm5uPj4+/v7+np6eZmZmxm9PTU3dsWNHUlJSbm6uSqXy8fEJ
Cgry9fWt9kYAANC8nMl8oNPphBAePR43dS1QCjPp/xNNSXpieXl5WVlZSUmJRqN59OiRSqVq4jJM
IisrKz4+ftu2benp6UIIlUqVl5dXkxtLS0s/+eSTjz76qKCgoKo+M2bM+Oijj5544on6VKjRaKKj
oyMiIh4+fFhph8GDB69Zs8bLy8v4OL/88suCBQu2bNlSVYegoKDIyMiuXbtWerW0tHT+/PkrVqyo
eGnmzJlRUVHW1tbGC6gtCwuLsrKyhh2z1YqIiFi0aJGpqwAANCdmm5+TGpF/XpRwPfVo4aEmLqBb
2+6Zk75s4ocq1vXr19u0aWNjY2NtbW1hYWFubi6EaPr/UswblaZw7969hISEL7/8Mj4+vg63379/
//XXX4+NjTXebdOmTSkpKfv3769z6tNqtcHBwdu2bTPS5/Tp088//3x8fPyIESOq6lNQUDB69Oi0
tDQj48TExJw9e3b//v3dunWreHXVqlVSSrG1tZ08eXK3bt2ys7M/++wztVr98ccfOzg4fPjhhzX9
qQAAQPOx6ed/5TzKavrntrNo1/QPhXEElUYkT/Havn17YWFhnQcJCQmRU0rbtm2Dg4Off/55FxcX
S0vLGzdu7N27d926dVqtVgiRnp7+6quvHjp0yMrKqg7PWrt2rZxSbGxswsPDR4wY0aFDB41Gk5GR
sXXr1oSEBCGERqOZMGFCenq6q6trxUF0Ot3UqVPllNKjR4/Zs2d7enq2b9++qKjo9OnT69ev//HH
H4UQGRkZkydPPnz4sEG1eXl5ERERQghnZ+cjR448+eST0vfBwcHDhw/Py8tbtmzZa6+91qVLF4NH
p6WlFRUVDR8+vA4/OwAAUAKTpBQoE4vpG9G2bdu8vLzWrFmjn1Lc3d07duxY80H+/e9/b9++XWoP
GDDg+++/X7FixYgRI/r27evu7u7n57dy5cqkpCR7e3upz/Hjx6t991Kp3NzcJUuWSG0nJ6eTJ08u
WbLEx8end+/e/fv3nzBhwt69e99//32pQ1FR0bJlyyodZ+/evXv27JHafn5+33777cyZMwcPHtyr
Vy8PD48ZM2akpqaOHDlS6pCcnLxz506DEVJSUjQajRBiwYIFckoRQri7u0sBRqvVJicnG9xVXFw8
Y8aM559/PiQkpA4/PgAAABSFoNKI9Nc82NnZhYSEHDt27OLFi+7u7jUcoby8XA4PNjY2X331Ve/e
leyaN2TIkI0bN8ofY2Ji6lBtbGysWq2W2hs2bBgwYIBBB0tLy4iICD8/P+njJ598UumCmc2bN0sN
KyurLVu2ODo6GnSwt7ffsmWLra2tPI5BB3ndTsUaBg4cKDVyc3MNLq1bt056jTN69OgqfkQAAAA0
GwSVRhcYGBgbG5udnR0dHe3r62tpWYvpdj/++OP58+el9vTp0/v06VNVz/Hjx8uLPXbv3i29kaiV
r7/+Wmr07t177NixlfaxsrKaM2eO/DExMdGgQ35+/u7du6X2G2+80aNHj0rH+f/Zu/O4qsu8/+MX
qwiegBAUEERRXHIXc0pwQTGnSQ1rlMrynkktcw8qKzcsdcYkt8zJzGmZKUxv+znuoLkgudHtAlky
KrIoqSnhEVkOcH5/fLu/95nD4bCdw/d7Dq/nXxfnXOe6PlAP5e33WgIDA6dPny6109LSfvrpJ8N3
y8vLpUarVsbnfri7u0uNkpISw9czMjIWLlwohHjppZfMbJ4BAACArSCoWNHgwYNzc3O3b9/+9NNP
e3p6NmCE8+fPy+0RI0aY6ens7Gy4N6O+W2KuX79+8uRJqR0TE2Nmi0tkZKT8rvwRmeEG+scee8zM
jNHR0XL77Nmzhm/Jxx8bpREhRHFxsVEfIYROp5s7d65OpwsMDJTWhgEAAMDWEVSsqHv37ia3m9fd
L7/8IrdrPcvLMAtJp8jVXXb2/21ck5dXmeTt7d2/f3+p/f333xu9e+nSJbn90EMPmRnH8F1pb71M
/k7lp0myzMxMqREQECC/+Mknnxw8eFAIsXLlynrt/wEAABBC9Pfq3c+ns9JVwBhBRdWee+657P9l
Zt2XJDc3V2oEBgZW3xlinmFQCQ4ONt9Z3uCenp4uL9OSZGVlyW3zycrX11dOVkZLvyIiIqSHNkuW
LDEcMDc3d8mSJVI7MjJSaly5cmXevHlCiHHjxk2YMMF85QAAANWlj9/w2ch4pauAMY4nVrUHH3yw
jhc4FhcXHzt2TGo/+eSTTk5O9ZrIcKlYravUfH19pYZOpysuLja8e/HmzZtyHzc3NzODODo6BgUF
FRUVif98cCSEaNeu3cKFCxcsWJCfnx8eHv7nP/85NDQ0Ly9v8+bNt2/fFkK8+eabnTp1EkJUVVXF
x8cXFRV5enq+99573FgPAADqq4N7R6VLgGkEFTuxb9++goICqT1+/Pj6flze+yGEaNmypfnO8o52
6YPyychCCPncsLo80pET0Z07d4zemjdv3q+//pqYmKjVatesWWP41rRp0+Rbz7ds2fLNN98IIZYv
X96xI3/KAACAevudTy+lS4BpLP2yB1qtVr6pfeTIkfKyqLozDCq1Po0xfIRitN/97t27UqMuh5vJ
G+KrBxVnZ+eVK1empqZOnz69R48eGo0mLCxsypQpBw4cWL9+vfTBgoKCuLg4IcSwYcNefPHFWqcD
AChCr9fX2mj8Z+vSs9ZGXTpUbzRgurrXY8HpaprX5CyNmc78t2lmOqUMb9ffsMJaG3V5Vz3fnU3j
iYo9WLBggbzLfOnSpQ1YAVVVVdWwqY0+WFFR0YBBDC+cMRQREREREVHTp+bPn19QUODi4rJq1SrD
7NQwer1e3gCDRuKHCTRner1e+muopob0S5vUMN+zMR+p+2cNO9RxFpMfMdOoSwfrTdeYn5jFpzMz
lGhruf8L6ylzR8qSb9LkOFFLnQ39icnrQVB3BBWb9+mnn8qLoxYtWhQeHq5sPU1jz549mzdvFkIs
XLiwd+/ejR/QwcFBuokFjZeQkMAPEwBQL4s27lNq6lXz/6LU1DCPpV+27dtvv506darUjoqKeuON
N5Stp2kUFhbOnj1bCNGnT585c+YoXQ4AAAAsj6Biw86cOTN+/HidTieECAkJ+fTTT2vdB28fli5d
Kl3Ysnr1aun2+pKSkk8//XTMmDFBQUEBAQGjRo1av369dKQYAAAAbBFLv2zVv//97yeffFI6rtfT
0/O///u/G3O5ZIMP9jXaNN+wccwfZGzk2LFjiYmJQojZs2cPGTJECJGbm/vss8+mpaXJfQoKCvbv
3//hhx9u3bq1e/fuDSgJAAAAyiKo2KRr166NGzdOuuHRzc1t27Zt/fr1a8yAHh4ectvoDsfqpGc4
EqNnOPKJw/fv3691UnkiwwOOzSsuLp41a5YQIiQkZMGCBdIrsbGxx48fF0L0798/JibGxcVl7969
hw8fvnDhwrhx444ePern51fH8QEAAKASLP2yPXfu3JkwYYJ8zNeXX345YsSIRo6p0WjkdmlpqfnO
8mUpolpQka+nNLrD0STpcZCowxWTslWrVp05c0Zq+Pj4CCG+/PJLKaVMnDgxLS3t7bfffv311w8c
OBAfHy+EuHjx4oYNG+o4OAAAANSDoGJj7t279/zzz8vLnD777LOYmJjGDysHDCHErVu3zHeWr5/X
aDSGCUcYXFpfVFRkfotIZWVlfn6+1Pb3969LkefOnZMOvX3uuefGjh0rvbhlyxapsXTpUvliFicn
p/nz57dr104I8cUXXzT48GUAAAAohaBiS8rKyl5++eU9e/ZIX65Zs+aFF16wyMiG17pLK8rMyMjI
kBoDBgww2qPStWtXuX3t2jUzgxQUFMhPZrp161ZrheXl5XPmzNHpdD4+PsuXL5c2w1RVVR09elQI
0bdv3+DgYMP+np6e0sWXly9frsvjHQAAAKgKQcVmVFVVvfbaa//85z+lL5csWSLt1rCITp06ye0T
J06Y6Xnr1q2zZ89K7V69ehm9axhUpDVaNfnhhx/kdufOnWutcOPGjYcPHxZCrFixQj42oKSkRNow
ExoaWv0jcrd79+7VOj4AAABUhaBiM955551169ZJ7fj4+Pnz51tw8NatWw8bNkxqb9++3XAXipEj
R47IbemRhaG+ffu6uLhI7R07dpiZcf/+/XL74YcfNl/epUuX3nrrLSHEqFGjTD5EMnnamHzFrNwA
AACArSCo2IYPPvhg8eLFUnvKlCny2icLio2NlRo3btz47LPPTPbR6XTvv/++1HZxcRk6dKhRh9at
W48fP15qb9269dSpUybHyc3Nlfe4R0VFtW/f3kxhlZWVcXFxWq3Wzc0tMTHRcLGZu7u7dLTx1atX
q38wLy9Pakh3rQAAABjp4N6x9k5QCEHFBiQlJc2cOVNqx8bGrlu3zmhnSF2UlpYmJSWtXbv29OnT
JjvExMS0adNGar/22muHDh0y6lBRUbFgwQLpiC0hxKxZswy34MsmT54st1988cWcnByjDoWFhZMn
T5bPFnvllVfMV56UlPSvf/1LCLFkyRKjS1EcHBwGDx4shDh79qzRlhitVvvdd98JIYKDg1u3bm1+
CgAA0Dx5OHnU3gkK4R4Vtdu/f7+82Klv374LFiyQD90y74EHHjA89jcuLu7DDz+U2qmpqREREUb9
fX1933nnnalTpwohSktLo6Ki4uLixowZExAQUF5e/tNPP23cuFFer+Xj4/Pqq6+anHfo0KEvvPDC
559/LoTIzMwcOHDg66+/Pnjw4AcffPDu3bunT59etWrVjz/+KHUePnz4k08+af4biY6Ofvnll8+c
OTNjxozq7/7xj39MTk7W6XSLFi3asGGDtPBMr9cnJiZKpwJMmjTJycmplh8WAABoftq2aDPIv4vS
VaBGDk2/fF+asaqqqrKysry8vLS0tKysLDAwsInLUNDgwYNTU1OFEIGBgfIRvSZVVVV5eXmZ2TFi
xurVq2fPni2Po9Fo5EsYFy1aJC8kM1RZWRkfH7969WrzI7u7u+/bt6/6BhVZYWHhuHHjpL3vZvTs
2XPv3r11/E9fWFho8l7I4uLi6Oho6TnPoEGDYmJiXF1dk5OTd+3aJYTo1KnTsWPH5CdFZjg5OVVW
VtalEtQqISFh0aJFSlcBALAZ1++UBW4b1vTzTun4/MYR05p+XvW7du1aixYt3NzcXF1dnZycHB0d
RQ1bgq2KpV+qptfrG5ZSjDg6OhoeARwQEGCym5OT03vvvbd27VozNzA+8sgjhw4dMpNShBDe3t7b
tm2Tl6uZNHHixD179tQ9oNZ0e72Hh0dSUtKgQYOEEGlpafHx8bNmzZJSSpcuXbZv316XlAIAABTR
5YupXb6YOmy3ud8ZLM7X1a8pp0ODsfSrudiwYUNcXNyVK1diYmKeffbZmro5OzvPnDnzqaee2r9/
f0pKSlZW1tWrVzUaTXBwcHh4eHR09LBhw+R7Fc3w8fFZu3bt1KlTk5OTDx06dPXq1by8vLZt24aE
hERGRkZHR9d60lfdBQcHp6SkbN26dfv27enp6eXl5b169Ro7duzEiRNrijcAAEANskoym37SNi3a
3Cq/KYTo7mP6n26hEiz9AoRg6ZdFsfQLAFBHDhsfbfpJe2h6ZmozhBBbh6x6usvApi9A/Vj6BQAA
AACmsfQLAAAATeT7K8V6vd7BwaF/R8XOBW76JwNoGIIKAAAAmkj4gWipceLxpIHtghWpYWr3x7Pv
9nNwcOjtF6RIAagjggoAAACaWl5xwUChTFCZ0WuMIvOivtijAgAAgObCj7OJbQdBBQAAAM2FXwsu
WLMZBBUAAAAAqkNQAQAAAKA6BBUAAAAAqkNQAQAAAKA6HE8MAAAABZz5Oa+JZ+zn1Wtmn9FNPCka
jKACAACApvbh+d1NP2n/B3v/V9gfmn5eNAxBBQAAAE3tUOEBpUuA2rFHBQAAAIDqEFQAAADQLPyu
bRelS0A9EFQAAADQLDzg4qF0CagHggoAAAAA1SGoAAAAAFAdggoAAAAA1SGoAAAAAFAdggoAAAAA
1SGoAAAAAFAdggoAAAAA1SGoAAAAAFAdggoAAAAA1XFWugAAAADYv7v3K4rLqpSuAraEoAIAAACr
e//Mjq+u7Fe6CtgSln4BAADA6q6X3MwqyVS6CtgSggoAAAAA1SGoAAAAAFAdggoAAACaBVcnfvW1
JWymBwAAgD3r/UDPEUHhQojBwd2UrgX1QFABAACAPXu4dZ+Vg6YoXQXqjedfAAAAAFSHoAIAAABA
dQgqAAAAsGe+bhqlS0BDEFQAAABgz/r6dla6BDQEQQUAAACA6hBUAAAAAKgOQQUAAADWpS2pLK/Q
K10FbAz3qAAAAMC6wrdNu627qXQVsDEEFQAAAFhXVkmm0iXA9rD0CwAAAHarlbOHv8ZL6SrQEDxR
AQAAgH3qoemZ8cxHSleBBuKJCgAAAOxTT69QpUtAwxFUAAAAYJ9auXAnvQ0jqAAAAABQHYIKAAAA
ANUhqAAAAABQHYIKAAAAANUhqAAAAABQHYIKAAAArEWv1+uVrgE2igsfAQAAYC2fnzlXcPeu0lXA
JhFUAAAAYC0rL27I1GYoNbuvG/eo2DCWfgEAAMA+9fXtrHQJaDiCCgAAAOxQmCa0vbe30lWg4Qgq
AAAAsENL+80Y4BemdBVoOIIKAAAAANUhqAAAAABQHYIKAAAAANUhqAAAAABQHYIKAAAAbEzPB3op
XQKsjgsfAQAAYEsW954xttOAX8u0w3bNULoWWBFBBQAAALbkIa/QPj7c5Gj/CCoAAACwKw4ODkqX
AAsgqAAAAMCW+Gu8zLx76IkPhBC/lGg7eT3YVBXBKggqAAAAsLzyCv1trU6v11t85EEBXaRGD03P
TG2G0btDA/pZfEYoglO/AAAAYHlH8n4cumtG9v3sppzU3cmjKaeDVfFEBQAAAJZXVK7NKsls4kk7
unds4hlhPQQVAAAAWMzJ/Nylx78RQtzW3bL44O5OHl01oRYfFupEUAEAAIDF5BUX7CzcYqXBO7p3
/H7838x0CGnV1kpTo+mxRwUAAAB2wr8lQcV+8EQFAAAANk9aFfZQ60ClC4HFEFQAAABg8/p69jz2
9PtKVwFLYukXAAAALOba3buKzNvdq7Mi88J6CCoAAACwmB+KLllv8CD3Greg+LpprDcvFEFQAQAA
gG1o5/EfQcXhfwkh+vryRMXesEcFAAAANunz6Lhfy7RCiAnJS/w1XkqXAwsjqAAAAMBipOTQNPr4
/PYUxa9Fm0EBXZpsXjQNln4BAADAYk7dPtf0k3LPo10iqAAAAMAy8u8W5ZRmW298v5YPmHx9Utjj
1psUSmHpFwAAACzjX5dOW2nkDu4dN0e92qd1mMl323t7W2leKIigAgAAAMtIyfveSiN7ungMDehX
07sD/EwHGNg0ggoAAAAaS6/XCwfxP7+et/zIU7+z+JiwCQQVAAAANNaC1O3ZRQW5ZVbcoILmhqAC
AACAxtpxLTlTm6F0FbArnPoFAAAAQHUIKgAAAABUh6ACAAAAQHUIKgAAAABUh830AAAAMEFbUplV
UCqEaNXCoUugu9LloNkhqAAAAMCE/bnpfzwyVwjRQ9Mz45mPFKmhg3tHReaFGrD0CwAAACrl4eSh
dAlQDEEFAAAAgOoQVAAAAACoDkEFAAAAKtXTK1TpEqAYggoAAABUyrPFA0qXAMUQVAAAAKBSUQF9
lC4BiiGoAAAAwBy9Xn/9Tpm2pLLppw54wLvpJ4VKEFQAAABgTvb97GG7Zyb+z/9r+qkfDQhr+kmh
Elz4CAAAAHPuVxVnlWReL+lr8t0rd379+vz5u+X3LD4vtz02cwQVAAAA1O5W8d3qL2ZdL9mTk/lm
1jxrzKhxbmWNYWErCCoAAACo3aX7V4QQer3ewcFBL/RCCAfh8NSROZnaDCvNOLB1b6EXwsFKw0Pt
CCoAAAAwIfOX/Oovfnbm7M93tRna89KXer3eegX4ummsNzjUj6CigMrKypMnT27btm337t0XL16s
+wd1Ot2RI0cOHjx46tSp3Nzc27dvh4SEhIaGRkVFRUdHd+rUyVIV5uTkpKSkHDhw4PLly9nZ2V5e
XkFBQeHh4VFRUVFRUS1atKjjOGfOnElJSUlNTc3JycnNzQ0MDAwODo6MjIyKiho4cKCDQy3/QpKW
lvbVV18dOXIkLy8vMDAwMjIyNjZ2yJAhtX4QAAA03vWSm4Zf/lxy47mdHyT/cuAX3f+97u7oYb0C
+vp25i/95szBqjnYJGnGqqqqysrK8vLy0tLSsrKywMDAJi5DEdnZ2Tt27Ni8eXNGRoYQIjAwMD/f
xL9VmHTmzJlXX3318OHDJt91cXF544033njjjVatGrWas7S0dO3atQkJCffv3zfZYcCAAatWrRo0
aJD5cX7++ecFCxZs2rSppg6xsbHLly8PCQkx+W5FRcXbb7+9YsWK6m/NmDEjMTHR1dXVfAH15eTk
VFmpwKmLdikhIWHRokVKVwEAaKypBzZ8fOULBQvYOmTV010GKlhAs3Xt2rUWLVq4ubm5uro6OTk5
OjoKIZo+NPJEpSncvXs3OTn5H//4x44dOxo2wokTJ0aNGlVUVFRTB51O9+677164cOHzzz/38Gjg
v23odLrp06dv3rzZTJ/Tp0+PGDFix44dI0eOrKnPjRs3Ro8enZ6ebmacpKSkM2fO7N27t0OHDtXf
XblypZRSNBrNpEmTOnTokJOT8/e//12r1X7wwQc+Pj6LFy+u63cFAAAAG0RQsSJ5idenn35aWFjY
4HFu3bo1btw4OaUMGzZs6tSp3bp1a9my5c2bN7/99tuVK1dqtVohxPbt27t16/buu+82bKLVq1fL
KcXNzS0+Pn7kyJF+fn6lpaUXL1785JNPkpOThRClpaXjx4/PyMgICgqqPoher588ebKcUkJDQ+fM
mTNw4EAvL6+ioqLTp0+vW7fuxx9/FEJcvHhx0qRJBw8edHFxMRwhPz8/ISFBCOHv7//tt9927dpV
en369OnDhw/Pz89ftmzZn/70p/bt2xtNnZ6eXlRUNHz48IZ9+wAAQFZe0dSLbgAjXAIKWCMAACAA
SURBVPhoRZs3bx40aNCqVasMU0pYWFibNm3qNc6aNWsKCgqk9pw5c/bt2xcbG9u7d++wsLCIiIiF
CxeeOHGiXbt2UocVK1ZIMaC+8vLy3nnnHant6+t7/Pjxd955JzIyskuXLr179x4/fvzu3bvffPNN
qUNRUdGyZctMjrN79+5du3ZJ7aFDh544cWLGjBkDBgzo3LlzeHj4tGnT0tLSRo0aJXVITU3dsmWL
0QjHjh0rLS0VQixYsEBOKUKIsLAwKcDodLrU1FSjT5WUlEybNm3EiBEzZ85swLcPAAAMHclryK8T
ltXbz8Q/iaL5IKhYkeGeB09Pz5kzZx4+fPiHH34IC6vHHat3795du3at1A4PD//LX/5SfXtG9+7d
P/roI6mt0+mSkpIaUO3WrVulxzJCiPXr1/fp08eog7Ozc0JCwtChQ6Uv//a3v924caP6OBs3bpQa
Li4umzZtat26tVEHb2/vTZs2aTQaeRyjDvK+neo19O3721VTeXl5Rm+tWbNGeowzevToGr5FAABQ
Vxd+uXa56LqCBbg7eXT2DlCwACiOoGJ1MTExW7duzcnJWbt27ZAhQ5yd67fcLjU1Vc4Pc+fOrenE
rVGjRg0YMEBq//Of/6yoqKhvnV9//bXU6NKly5NPPmmyj4uLy9y5c+UvU1JSjDoUFBTs3LlTak+Z
MiU0NNTkOIGBgdOnT5faaWlpP/30k+G75eXlUqP6wQDu7u5So6SkxPD1jIyMhQsXCiFeeuklM5tn
AABAHf1QdOlc0XkFC+jkYfq3CDQfBBUrGjx4cG5u7vbt259++mlPT8+GDfLdd98ZDlhTN0dHx5iY
GKktnSlcr1muX79+8uRJqR0TE2O0acRQZGSk/K78EZnhBvrHHnvMzIzR0dFy++zZs4ZvyWHMKI0I
IYqLi436CCF0Ot3cuXN1Ol1gYKC0NgwAADTe7YpbSk3t7uQxLKCvUrNDJQgqVtS9e3eT283rJTMz
U2qEhobKG1FMMlwodenSpXrNYhhs5OVVJnl7e/fv319qf//990bvGs770EMPmRnH8F2jTTXyWdXn
zp0z+pT80wgI+L9nwZ988snBgweFECtXrqzv/h8AAKBCHd07Lv7dc0pXAYURVNTu9OnTUqN3797m
exreRXPlypV6zWIYVIKDg813lje4p6eny8u0JFlZWSbrqc7X11d+ymS09CsiIkJ6aLNkyRLDAXNz
c5csWSK1IyMjpcaVK1fmzZsnhBg3btyECRPMVw4AAGyFl2ujroaDHSCoqFpZWZl83pevr6/5zl5e
XnLbzI0rJhmeS1brKjW5Ep1OJ6/Fkty8eVPu4+bmZmYQR0dH+XHTL7/8YvhWu3btpA0n+fn54eHh
c+bMWbdu3euvv96vX7/Lly8LId58881OnToJIaqqquLj44uKijw9Pd977z0urwUAwD448nc6uEdF
5Qw3adR65bxhMJD339eRYd5o2bKl+c7yjnbpg97e3tXnrX7YV3VyIrpz547RW/Pmzfv1118TExO1
Wu2aNWsM35o2bZp86/mWLVu++eYbIcTy5cs7duxY64wAAMAmDGxdy0ISNAc8UVE16ToRiZOTk/nO
hjvg7927V6+JDINKrRMZno9stN/97t27UqMuh5vJG+KrBxVnZ+eVK1empqZOnz69R48eGo0mLCxs
ypQpBw4cWL9+vfTBgoKCuLg4IcSwYcNefPHFWqcDgCam1+tratTawbKfbfx0dR/EIrPUOp1er2/M
dHX8WRnOYqbRyFkUnE7+sqbpFGf+u6tebV2+qQb/VBs5HRqAJyqqVlVV1TQftNREDTgWWfznhTOG
IiIiIiIiavrU/PnzCwoKXFxcVq1aVf1umfrS6/XyBhg0Ej9MNHN6vV5aiSo1jL6sS0P6taa+nzU5
u8Wna/AsapjO5LyWGtNMo8H/TZWdLje4IX+nW0rO1avSSZ5ybaKGb1lY7kcnTW2lWeT1IKg7ggps
0p49ezZv3iyEWLhwYa3HDNSFg4ODtDEGjZeQkMAPEwBs2vXC8n/umqFgAe1DQhZNnqZgAVADln7B
9hQWFs6ePVsI0adPnzlz5ihdDgAA9uazc8ezSjKVrgLNHUEFtmfp0qXShS2rV6+WzhgoKSn59NNP
x4wZExQUFBAQMGrUqPXr19f36DMAACCEuF5YnnhlldJVACz9slNmrpY3qcEH+xptmm/YOOYPMjZy
7NixxMREIcTs2bOHDBkihMjNzX322WfT0tLkPgUFBfv37//www+3bt3avXv3BpQEAECzFZ/28e2K
m0pXARBU1M3wpOCysjLznQ03std6lrERDw8PuW10h2N1Op3OZIXC4MTh+/fv1zqpPJHhAcfmFRcX
z5o1SwgREhKyYMEC6ZXY2Njjx48LIfr37x8TE+Pi4rJ3797Dhw9fuHBh3LhxR48e9fPzq+P4AAA0
cz/euL3j5/+ndBWAECz9UjnD/GB0tWJ1hh0MP1gXGo1GbhueiWyS4SUtRkHlwQcflBpGdziadPv2
balR6xWTslWrVp05c0Zq+Pj4CCG+/PJLKaVMnDgxLS3t7bfffv311w8cOBAfHy+EuHjx4oYNG+o4
OAAAmHFs9f2qWn7lAJoGQUXVXF1dAwMDpXZeXp75zr/++qvcrst9i4bkgCGEuHXrlvnO8vXzGo3G
MOEIg0vri4qKzG8RqayszM/Pl9r+/v51KfLcuXPSobfPPffc2LFjpRe3bNkiNZYuXSpfzOLk5DR/
/vx27doJIb744osGH74MAECzohfiZrnyi77CNKHDgrspXQWUR1BRu4EDB0qNs2fPmr8wKDc3V27X
95p2w/6G45iUkZEhNQYMGGC0R6Vr165y+9q1a2YGKSgokJ/MdOtW+x9G5eXlc+bM0el0Pj4+y5cv
lzbDVFVVHT16VAjRt2/f4OBgw/6enp6RkZFCiMuXL9fl8Q4AAM3coUvZfz189G55/e6MtrgO7h1P
PrXhmbChypYBNSCoqF2fPn2kxo0bN7Kyssz0lNZESTp06FCvWTp16iS3T5w4YabnrVu3zp49K7V7
9epl9K5hUDGsp7offvhBbnfu3LnWCjdu3Hj48GEhxIoVK4KCgqQXS0pKpA0zoaGh1T8id7t3T+E/
cwEAUL+vru57M2teblm2smV4OHl4udZvqy3sFUFF7R555BG5nZKSUlO3ioqKb775Rmr37NmzvkGl
devWw4YNk9rbt2833IVi5MiRI3JbemRhqG/fvvKBYzt27DAz4/79++X2ww8/bL68S5cuvfXWW0KI
UaNGvfDCC9U7mDxtTH4AZf5JFAAAUIkn/KO/GBmvdBVQC4KK2g0aNEjewpGYmGi4EcXQ7t27z507
J7VjY2MbcExwbGys1Lhx48Znn31mso9Op3v//feltouLy9ChQ406tG7devz48VJ769atp06dMjlO
bm6uvMc9Kiqqffv2ZgqrrKyMi4vTarVubm6JiYmGi83c3d2lo42vXr1a/YPyrp76noEGAAAUEdNh
SB+f2tdZoJkgqKhdy5Yt5cvXr169On369OoLmS5cuDB9+nSp7ebm9swzz1Qfp7S0NCkpae3atadP
nzY5UUxMTJs2baT2a6+9dujQIaMOFRUVCxYskI7YEkLMmjXLcAu+bPLkyXL7xRdfzMnJMepQWFg4
efJk+WyxV155xWQ9sqSkpH/9619CiCVLlhhdiuLg4DB48GAhxNmzZ422xGi12u+++04IERwcXN+j
BQAAgCIecKnfsaWwbwQVGzBt2rSwsDCp/eWXXw4bNuyLL744f/785cuXT5w4sXTp0t/97nfyr+lv
vfWWyXVfcXFxzzzzzOzZsx9++OFjx45V7+Dr6/vOO+9I7dLS0qioqPj4+KNHj166dOnChQvbt29/
4okn/vrXv0odfHx8Xn31VZPVDh06VF6dlZmZOXDgwPfffz89Pf3KlStnz579+OOPBw0aJK9hGz58
+JNPPmn+24+Ojn755ZcHDhw4Y8aM6u/+8Y9/FELodLpFixbJF7zo9frExETpVIBJkyY5OTmZnwIA
AABq49D0y/elGauqqiorK8vLy0tLS8vKyuRDeJuDwYMHp6amCiECAwPlI3rNO3/+/KhRowoKCsx3
e/bZZzdv3iyf0iurqqrSaDTyJYyLFi1avHhx9Y9XVlbGx8evXr3a/Czu7u779u2rvkFFVlhYOG7c
OGnvuxk9e/bcu3dvHf/TFxYWmrwXsri4ODo6WnrOM2jQoJiYGFdX1+Tk5F27dgkhOnXqdOzYMflJ
kRlOTk6VlZV1qQS1SkhIWLRokdJVAADqZ+qBDR9f+ULZGrYOWfV0l4HK1gAhxLVr11q0aOHm5ubq
6urk5OTo6Chq2BJsVTxRsQ29evU6cODA73//+5o6uLi4JCQkfPzxx9VTihDC0dHR8AjggIAAk4M4
OTm99957a9euNXMD4yOPPHLo0CEzKUUI4e3tvW3btpkzZ5rpM3HixD179tQ9oNZ0e72Hh0dSUtKg
QYOEEGlpafHx8bNmzZJSSpcuXbZv316XlAIAABT3avf/6u0XpHQVUBHn2rtAHbp3775z587U1NQD
Bw4cP348Jyfnzp077du379ix4/Dhwx977DGTR/TKNmzYEBcXd+XKlZiYmGeffbambs7OzjNnznzq
qaf279+fkpKSlZV19epVjUYTHBwcHh4eHR09bNgwk1nIiI+Pz9q1a6dOnZqcnHzo0KGrV6/m5eW1
bds2JCQkMjIyOjq61pO+6i44ODglJWXr1q3bt29PT08vLy/v1avX2LFjJ06cWFO8AQAAapMYMVXp
EqAuLP0ChGDpl0Wx9AsAbJHiS7/0U79TcHYYYukXAAAAVEFbUllewbVjUBeWfgEAADR34dum3dbd
VLoK4D8QVAAAAJq7rJJMpUsAjLH0CwAAAIDqEFQAAAAAqA5BBQAAAIDqEFQAAAAAqA5BBQAAAIDq
EFQAAAAAqA5BBQAAAIDqEFQAAAAAqA5BBQAAAArroempdAlQHYIKAAAAANUhqAAAAABQHYIKAAAA
ANUhqAAAADRreqULAExyVroAAAAAKOaL88ev3dEpXQVgAkEFAACg+Uq9efbjK18oXQVgAkEFAAAA
Shri+4iLM/sRYIygAgAA0ExpSyrLK5TfohKm6fTWwCeVrgKqQ1ABAABojlKyL8w4tvq27qbShQgh
RIjGX+kSoDoEFQAAgOaoqFybVZKpdBVAjVgOCAAAAEB1CCoAAABQUph3gNIlQI0IKgAAAFBSSKu2
SpcANSKoAAAAQEmuTvxGChP43wIAAABKGtNpgNIlQI0IKgAAAABUh6ACAAAAxXRw76h0CVApggoA
AACU0cG9o8a5ldJVQKUIKgAAAFCGh5NHfO8JSlcBlSKoAAAAQDHPdxumdAlQKYIKAAAAANUhqAAA
ADQ7v9zVaUuqlK5C9PQKVboEqJez0gUAAACgqf35YOLZogxla3BwcGjlolG2BqgZQQUAAKDZyS7N
zivPVmr2VQPe6NMmSAgRovFXqgaoH0EFAAAATaqde9uhAf2UrgJqR1ABAABoLv5y+KgQIkN7XulC
gNoRVAAAAJqLN7PmSY0emp7KVgLUilO/AAAAmoWU7Atyu6DkhoKVAHVBUAEAAGgWTv58UW7frrip
YCW9/YIUnB22gqACAABgz25rK6TG9zezlK1E1tk7QOkSYAMIKgAAAPYsu/BXqXFRe1nZSoB6IagA
AADYswP53wshyiv0P97PVLoWoB4IKgAAAPbs3O1/CyGO5P2odCFA/RBUAAAA7Nb1wvLMexlCiLTr
agkqHk4eSpcA20BQAQAAsFv7rqZLjXO/XFK2EtlrPf6kdAmwDQQVAAAAu/U/v/xbaqhnJ/2k7sOU
LgG2gaACAABgtzIKLwmV7aQP0fgrXQJsA0EFAADAPpVX6H+4lyHYSQ/bRFABAACwT1fuFEo30O/L
SVe6lt90cO+odAmwGQQVAAAA+7Q7+7d8cv6OWnbSc+QX6o6gAgAAYJ/O/u9O+izV7KQH6o6gAgAA
YJ++LzwnhKis1OeWZStdC1BvBBUAAAA7JJ/0pZ7zvoQQbTw0SpcAm0FQAQAAsEMHrl5QugRjUzo+
f2DMSqWrgM0gqAAAANihg/nfK10C0CgEFQAAADukrShWugRjLZwdlC4BtoSgAgAAgKawbujLSpcA
W0JQAQAAAKA6BBUAAAAAqkNQAQAAAKA6BBUAAABYXUy7kUqXABtDUAEAAIB1RbZ+ZPvji5WuAjaG
oAIAAADr6vpAJ6VLgO0hqAAAAABQHYIKAAAAANVxVroAAAAAWNic5K+P3DijdBVAoxBUAAAA7M3B
2wezSjKVrkIIIdq2aPNSjyeG+vdVuhDYHoIKAACAvams1CtdghBCLO49Y2ynAX18OitdCGwSe1QA
AADszY/3VfE45SGvUFIKGoygAgAAAEB1CCoAAACwvM6aTv4aL6WrgA0jqAAAAMDyVv9u1qCALkpX
ARtGUAEAAIDlPd4hXOkSYNsIKgAAAABUh6ACAAAAQHW4RwUAAMB+3L1f8e+fy5SuArAAnqgAAADY
j4RTX4YfiFa6CsACCCoAAAD2Q1tRbMHR3J08LDgaUC8EFQAAAJjW0b2j0iWg+SKoAAAAAFAdggoA
AAAA1SGoAAAAAFAdggoAAAAA1SGoAAAAwAQ/Vz9PF079gmK48BEAAMAeXL9T5uDgUFmlt9SAY9s9
JoRIu3OiAZ/1dfWzVBlotggqAAAANm9O8td7bxwQQjzo1krpWoQQwt+trdIlwOYRVAAAAGzewdsH
s0oyhRAPOfVUuhYhhHiiXYTSJcDmsUcFAADAfmTfv6J0CUII8V8PRSldAmweQQUAAMB+3K8qVroE
sbT/rM7eAUpXAZtHUAEAAIAlvdU/VukSYA8IKgAAALAYBwcHpUuAnSCoAAAAwGK+/cM6pUuAnSCo
AAAAwGKGBvRTugTYCYIKAAAAANUhqAAAAMAy2KACC+LCRwAAAFjAoSc+ULoE2BWCCgAAgA3TW3Pw
sDpfh+Lr6sfuFFgWQQUAAMBWjdm6xqrjDwnqJr6vU882LdpYtRI0QwQVAAAAW7WzcIvU6KHpaY3x
B/iFWWNYoC4IKrakrKwsOTn56NGjJ06cyM/PLywsDAwM7NKly6OPPvqHP/yhW7dulpooJycnJSXl
wIEDly9fzs7O9vLyCgoKCg8Pj4qKioqKatGiRR3HOXPmTEpKSmpqak5OTm5ubmBgYHBwcGRkZFRU
1MCBA2vdb5eWlvbVV18dOXIkLy8vMDAwMjIyNjZ2yJAhbNQDAMCI3qorwGrTwb3jzicWK1kB7JGD
vsn/v5ZmrKqqqqysLC8vLy0tLSsrCwwMbOIybM7evXtnzZp16dKlmjr8+c9/XrZsWZs2jXrwWlpa
unbt2oSEhPv375vsMGDAgFWrVg0aNMj8OD///POCBQs2bdpUU4fY2Njly5eHhISYfLeiouLtt99e
sWJF9bdmzJiRmJjo6upqvoD6cnJyqqystOyYzVZCQsKiRYuUrgIAmgWHjY9KjZaOHiVVxZYdfErH
5zeOmCZPYUYPTc+MZz6y7OxQ0LVr11q0aOHm5ubq6urk5OTo6CiUONKN44ltw9q1ax9//HEzKUUI
sXnz5sGDB1+5cqXBs+h0uunTp7/xxhs1pRQhxOnTp0eMGJGcnGxmnBs3bowePdpMShFCJCUljRo1
Kjs72+S7K1eulFKKRqORksmsWbM0Go0Q4oMPPli2bFmdvh8AAJoNi6cUQHEEFRuwf//+2bNny18+
8cQT27Zty8jI+Pe//52WlrZs2TJfX1/praysrPHjx5eUlDRsotWrV2/evFlqu7m5zZ8//+jRoz/9
9NPZs2e3bNkycuRI6a3S0tLx48fn5eWZHESv10+ePDk9PV36MjQ0dN26dadOncrKyjp9+vSHH34o
L1G7ePHipEmTdDqd0Qj5+fkJCQlCCH9//1OnTq1bt+7VV19ds2ZNenp6u3bthBDLli3LycmpPnV6
evrBgwcb9r0DAABAVQgqaldVVfXmm2/KXyYmJu7YseOpp57q0aNHp06dHn300TfffPPUqVN9+vSR
Onz//fdffvllAybKy8t75513pLavr+/x48ffeeedyMjILl269O7de/z48bt375YrKSoqqumxxu7d
u3ft2iW1hw4deuLEiRkzZgwYMKBz587h4eHTpk1LS0sbNWqU1CE1NXXLli1GIxw7dqy0tFQIsWDB
gq5du8qvh4WFSQFGp9OlpqYafaqkpGTatGkjRoyYOXNmA759AABgpK3HA0qXgGaNoKJ2mZmZZ86c
kdp//OMf586dKy0TNBQSEiI/CRFCbNu2rQETbd26VavVSu3169fLyUfm7OyckJAwdOhQ6cu//e1v
N27cqD7Oxo0bpYaLi8umTZtat25t1MHb23vTpk3SOi5pHKMO+fn5UqN6DX379pUa1Z/nSI9chBCj
R4+u4VsEAAD10OvBTkKIV7v/l9KFoJkiqKid4b6UCRMm1LSNqW/fvoMHD5bahw8frqqqqu9EX3/9
tdTo0qXLk08+abKPi4vL3Llz5S9TUlKMOhQUFOzcuVNqT5kyJTQ01OQ4gYGB06dPl9ppaWk//fST
4bvl5eVSo1WrVkYfdHd3lxpGy9syMjIWLlwohHjppZfkJWoAAKDxEiOmmu8wJnDk0gGTm6YYNCsE
FbW7e/eu3Pb39zfTMyzst5POS0tLi4vrt6Pu+vXrJ0+elNoxMTEuLi419YyMjJTflT8ik7emCCEe
e+wxMzNGR0fL7bNnzxq+JR9/XH2zjfx9GR6RrNPp5s6dq9PpAgMDpbVhAACgyawZ/NKYTgOUrgJ2
iKCidt7e3nL7119/NdPz5s2b8kfkJw91ZHj6lry8qqZ6+vfvL7W//974rlrD5z8PPfSQmXEM3/3x
xx8N35LPqj537pzRpzIzM6VGQECA/OInn3wi7aFfuXJlI09nBgAA9RWiMfcPqUCDEVTUrl+/fnJ7
z549NXW7fv26fGTw2LFjnZyc6jWLYVAJDg4231ne4J6eni4v05JkZWXJbfN34/j6+np6ekpto6Vf
ERER0kObJUuWGA6Ym5u7ZMkSqR0ZGSk1rly5Mm/ePCHEuHHjJkyYYL5yAAAA2AqCitoFBQW9/PLL
Unv9+vW7d++u3qekpCQuLk46KUsI8corr9R3lsLCQrkt54eayKch63Q6ozVm8lMdX19fNzc3M4M4
OjoGBQVJ7V9++cXwrXbt2kkbTvLz88PDw+fMmbNu3brXX3+9X79+ly9fFkK8+eabnTp1EkJUVVXF
x8cXFRV5enq+99573FgPALBj5RX663fKvr9SnHW9gfcQALbFWekCULt33333hx9+kA7kfeKJJ956
660JEyZ06tSpRYsWd+7cOXXq1F//+lf5uN4PP/xwwIB6rxM1zBstW7Y039lwXVlxcbHh4jT53LDq
h31VJyeiO3fuGL01b968X3/9NTExUavVrlmzxvCtadOmybeeb9my5ZtvvhFCLF++vGPHjrXOCACA
7TqS9+OMY6uzSjK5Bh7NBE9UbICPj8+2bduefvpp6ctly5b17t3bw8PD2dnZz8/viSeekFKKp6fn
pk2bpk2b1oApDINKrcvGXF1d5bbRfnd567+zc+0ZWN4QXz2oODs7r1y5MjU1dfr06T169NBoNGFh
YVOmTDlw4MD69eulDxYUFMTFxQkhhg0b9uKLL9Y6HQAARvR6vVHDqoM3cpaicm1WSWZjy2qQHpqe
tfZR6odpwenqMos1vjvUhCcqtsHPz+/rr7+eN2/eihUrTHZo167dt99+27lz54aN34DjjE1+sKKi
ogGDVFZWmnw9IiIiIiKipk/Nnz+/oKDAxcVl1apVhtmpYfR6PSeGWQo/TJjk4OAg/QVfvdGAz1p1
uuqDNGAW9U/XgMEbM4vRZ9UzXeNZ9b+L4SzZ/r8teSgtKU1ISPhtcGvuY9+/f/+FLfv1en1pUGn1
dyf9Ei41Gv9nftP8DOsynTVIg8vrQVB3BBXbUFhY+MYbb3z88cc1dcjPz3/++ecTExMHDRrUlIUp
Zc+ePdIdlwsXLuzdu3fjB3RwcOBPEEtJSEjghwkAFjf1wAZxRQgh3Fq6yX/MLt6433ozPvbYY093
GSiE2PbVS0L7H2/1fqDn36eucRDsDoUVsfTLBvzyyy9jxoyRU8ro0aO3bt16/vz5ixcvpqamLl26
1MfHRwhx8uTJiIiIvXv3KlpsUygsLJw9e7YQok+fPnPmzFG6HAAA7FAH9469/YKMXmzboo0Qwt3J
Y0z7wYI1ULAygora6fX6mTNnHjt2TPryo48+2rFjx9NPP92zZ8+wsLCIiIi33nrr7Nmz8rX0EyZM
OH36tHL1NoWlS5dKF7asXr1aur2+pKTk008/HTNmTFBQUEBAwKhRo9avX19UVKR0pQAAWF5l5W8R
IfumiRVZluLh5NHZO8DoxdGBI4UQHd07jg4dwGGbsDaCitqlpKQkJSVJ7YULF06dOrX6nwvt2rX7
6quv2rVrJ4TQarWzZ8+u716RBv9ZY7RpvmHjmD/I2MixY8cSExOFELNnzx4yZIgQIjc3Nzo6+k9/
+tPOnTvz8/MLCgr2798/Y8aMRx999MKFCw2oBwAANfvxfqYQ4tCl7CF7FDhLpoemp49bqwF+YU0/
NZobgoraffrpp1JDo9HMmjWrpm4BAQHSvYdCiOPHj3/33Xf1msXDw0NuG93hWJ1Op5PbRmcZyycO
379/v9ZJ5YkMDzg2r7i4WPohhISELFiwQHolNjY2LS1NCNG/f/933333r3/969ChQ4UQFy5cGDdu
nHy1CwAA9uSrq/vyyrNr79dQni4eJl8Pcm/7dOgQ680LyNhMr2plZWU7duyQ2o8//ri0F6Um0dHR
cvvYsWPyYrC60Gg0clu+OLIm8mUpolpQefDBB6WG0R2OJt2+fVtq1HrFpGzVe7dW7AAAIABJREFU
qlVnzpyRGtJP48svvzx+/LgQYuLEiZs2bZJOLo6Li5s3b97KlSsvXry4YcMGNnYDAFBf3b3+7yjR
lx76Q/bd/kII/5ZtfN00T3So941tQAPwREXVbt68KT+akO5iN0O+6F0IceXKlXpNJAcMIcStW7dq
rUpqaDQaw4QjDC6tLyoqMr9FpLKyMj8/X2r7+9fpbMVz584tWbJECPHcc8+NHTtWenHLli1SY+nS
pfLFLE5OTvPnz5fWwn3xxRcNPnwZAIDmKaTlf1yjPKPXmMSIqYkRU8d2HPA7/64hGmseigz8L4KK
qhleMFLrPYyGHWpdvmXE8Fr33Nxc850zMjKkxoABA4z2qHTt2lVuX7t2zcwgBQUF8pOZbt261Vph
eXn5nDlzdDqdj4/P8uXLpc0wVVVVR48eFUL07ds3ODjYsL+np2dkZKQQ4vLly3V5vAMAgA25fqes
ssqKp261cvaY3Xt09dc7eweMDg233ryAIYKKqhmuiTL/e7/4z9VWfn5+9ZrI8HHNiRMnzPS8devW
2bNnpXavXr2M3jUMKtIarZr88MMPcrsu91Ru3Ljx8OHDQogVK1bIz45KSkqkDTOhoaHVPyJ3u3fv
Xq3jAwBgQ4btnnmh6JKVBvdw8hgW0O8h33ZWGh+oI4KKqnl5eclPG/bv329+94hhwOjSpUu9Jmrd
uvWwYcOk9vbt2w13oRg5cuSI3JYeWRjq27evi4uL1JZ315i0f///XVD18MMPmy/v0qVLb731lhBi
1KhRL7zwQvUOJk8bk6+Ytd5dswAAKCKrJPNeRbGVBv804t21Q16y0uBA3RFUVM3BwWHcuHFSOz8/
/8svv6ypZ0lJyfvvvy9/WT1C1Co2NlZq3Lhx47PPPjPZR6fTybO4uLhIh2sZat269fjx46X21q1b
T506ZXKc3NzcDRs2SO2oqKj27dubKayysjIuLk6r1bq5uSUmJhouNnN3d5eONr569Wr1D+bl5UkN
6a4VAABs11VtgdEr/DMc7B5BRe3+/Oc/y9eMzJw5Mzk5uXqf4uLi2bNnS0f0CiGef/55wyVYktLS
0qSkpLVr19Z0HWRMTEybNm2k9muvvXbo0CGjDhUVFQsWLJCO2BJCzJo1y3ALvmzy5Mly+8UXX8zJ
yTHqUFhYOHnyZPnp0CuvvGKyHllSUtK//vUvIcSSJUu6d+9u+JaDg4N0uNnZs2eNlsZptVrpjObg
4ODWrVubnwIAAJX7+NxBo1ey71vrbGJ/jZeVRgbqxWnx4sWKTKzX6/V6fWVlZUVFRWVl5QMPPKBI
Gern7e3dqlUraaGUTqf7xz/+kZeX5+zsXFVVpdVqs7Ozd+3aNXXq1L1790r927Vr9/nnn1e/mWT2
7Nnz5s3bt2/fxx9/PGLECKOt50IIDw8PT0/PnTt3CiEqKio+++yze/fuubm56XS6n3/+OTU1NS4u
Tn7S4uPj8/nnnxsd+SUJCQnJzs4+d+6cEOLmzZtfffWVo6Oji4tLaWlpTk7Ozp07p0yZcvLkSanz
8OHDly5d6uhoLjC3bdv23r17Tk5OH374obyuTFZWVrZz586qqqqioqLf//730okCer1++fLlUryZ
NWvW8OHDa/05L1myhFOMLeXIkSPVn7YBABpj6pEVHTXB/1N4Xn5Fp9eZ6d8Ynwx9w0ojw1ZotVpn
Z2dnZ2cnJydHR0dpjX2D7wdvMIemf24ozVhVVVVZWVleXl5aWlpWVhYYGNjEZdgQvV7/9ttvL1++
vNaegYGB33zzzYABxqebV1VVaTQa+aTjRYsWmQyolZWV8fHxq1evNj+Lu7v7vn37zKwuKywsHDdu
nLT33YyePXvu3bu3jv/pCwsLTd4LWVxcHB0dLT3nGTRoUExMjKura3Jy8q5du4QQnTp1OnbsmPyk
yAwnJyfDM9bQGAkJCaQ+ALAsh42PPuY3Yv/NA00wl35q/a6Nhv25du1aixYt3NzcXF1dpawilAgq
LP2yAQ4ODsuWLdu2bZv5q1SeeeaZ48ePV08pQghHR0fDI4ADAgJMjuDk5PTee++tXbvWzA2Mjzzy
yKFDh8zvgfH29t62bdvMmTPN9Jk4ceKePXvqHlBrur3ew8MjKSlp0KBBQoi0tLT4+PhZs2ZJKaVL
ly7bt2+vS0oBAED9mialAOrBExVbUlJSkpycnJqaevLkyfz8/MLCwsDAwLCwsIiIiJEjR/bs2dPM
Z0+fPh0XF3flypWYmJjly5eb319+/fr1/fv3p6SkZGVlXb16VaPRBAcHh4eHR0dHDxs2TL5XsVaZ
mZnJycmHDh26evVqXl5e27ZtQ0JCIiMjo6Ojaz3pq15KSkq2bt26ffv29PT08vLyXr16jR07duLE
iTXFm+p4omJBPFEBAItz2Phok83FExWo5IkKQQUQgqBiUQQVALC4pgkqDg4Oer2eoAKVBBXn2rsA
AACgGbgSu+2jH3YpXQXwG/aoAAAAQAghQjT+y383RekqgN8QVAAAAACoDkEFAAAAgOoQVAAAAACo
DkEFAABA1Zr6hFZAHTj1CwAAQI1O5ucuPf6NEKKjp7/StQAKIKgAAACoUV5xwc7CLUKIbmU9lK4F
UABLvwAAAFTtx/uZSpcAKICgAgAAAEB1CCoAAAAQvq5+SpcA/AeCCgAAAERIq7ZKlwD8B4IKAAAA
xKmn/6Z0CcB/IKgAAAAAUB2CCgAAAADVIagAAAAAUB2CCgAAAADVIagAAAAAUB2CCgAAgOpcvHY/
/45O6SoAJTkrXQAAAACMPX10bqY2Q+kqACXxRAUAAACA6hBUAAAAmjtfVz+lSwCMEVQAAACau64P
hCpdAmCMoAIAANDcdX2gk9IlAMbYTA8AANCsLe49Y1L3YUpXARjjiQoAAECz9pBXaIjGX+kqAGME
FQAAAACqw9IvAAAAFTmZn7v0+DcFJTeULgRQGEEFAABARfKKC3YWbmnKGf01Xk05HVBHLP0CAABo
vtydPAYFdFG6CsAEggoAAEDz9ZAnN6hApQgqAAAAzdSCntNPPf03pasATCOoAAAANC8d3DtKjV4P
cs8j1IugAgAAoCLX7t619hQeTh5SIzwg2NpzAQ1GUAEAAFCRH4ouWXsKRwcHqcE9j1AzggoAAEDz
8pBnRyGEn6uf0oUA5hBUAAAAmpcRQeFCiLZubZUuBDCHCx8BAABUQd9UEz3g4iGECPZo01QTAg1B
UAEAAFDeoUvZJ/PzhBAX71xvgun8XP3YoAKVI6gAAAAo76ur+z6+8kWTTefXok3f1mFNNh3QAOxR
AQAAaI7aejygdAmAOQQVAACAZsfHrdWjgV2VrgIwh6ACAADQ7PTxCfNybaV0FYA57FEBAABoXvw1
XhGij9JVALXgiQoAAEAz4uDgMCigS6fWDypdCFALnqgAAAA0C4ee+EBu9/HprGAlQF0QVAAAAJqF
oQH9lC4BqAeCCgAAgJ1zd/LozSMU2Br2qAAAANi5sFah3z35odJVAPVDUAEAALBzb/f5k9IlAPVG
UAEAALBzIzo8pHQJQL0RVAAAAOyTu5OH1OBuR9giggoAAIB9GtL6USFED01PpQsBGoKgAgAAYJ/a
ebQVQni6eChdCNAQBBUAAAD79Lu2XXpoenb34mBi2CSCCgAAgH16wMUjpFXbMO8ApQsBGoKgAgAA
YLd6eXcOadVW6SqAhuBmegAAAIXp9ZYf00E4jOjwkKuTY6827Sw/OmB9BBUAAADFZF0v0ZZWlVdU
lZRVWXbkqqlpQojBwd04mxg2iqACAACgmKeOzMnUZgirHSJMSoHtYo8KAACA8qyx+guwaQQVAAAA
5f1cekPpEgB1IagAAAAo73bFTQuO5ufqZ8HRAEUQVAAAAOxNlwdClS4BaCyCCgAAgL2Jat9d6RKA
xuLULwAAAAWUV+hva3V662yiH+rf1xrDAk2JJyoAAAAKOJL349BdM7LvZ1tj8D6tw6wxLNCUeKIC
AACggKJybVZJpjVGbt+qLdenwA7wRAUAAMC2eTi3cnBwkL/s07qzgsUAlsITFQAAABt26IkPvFpo
fi3TCiFeS9uYXni+jw/rvmAPCCoAAAC2qoem55CAvg7it8cpo0LC0wvPs5Me9oGlXwAAAHbCydFB
CDE0oJ/ShQAWQFABAACwH7192KACO0FQAQAAsFWGe+glfQgqsBfsUQEAAGhqeiG0JVWNHGRR/xdD
NG3lDSoSggrsBkEFAACg6dy9X1FcVvV8cmLjL1FZ3P/F6i8SVGA3CCoAAABN5/0zO766st9KVz0K
dtLDjhBUAAAAms71kpuNTyl+rn7Teo6u/jqPU2BP2EwPAABgYwJatmHdF+weT1QAAABsxhP+0XH9
x3q10Jh8N0Tj38T1ANZDUAEAALAZ/i3bsgsFzQRLvwAAAACoDkEFAADANvTx7BnmHaB0FUATIagA
AADYhscDI0NatVW6CqCJEFQAAABsgH7qd319OdQLzQhBBQAAwDaM6PCQ0iUATYegAgAAYBu8XFv1
9gtSugqgiRBUAAAAbEZnNtOj2SCoAAAAWJ22pFLpEgAbQ1ABAACwrtvaimvaIqWrAGwMQQUAAMC6
0q/nZhb+W+kqABtDUAEAALCuLf8+rHQJgO0hqAAAAFiRtqTywC8HpfbWHzIaNoiDcLBcRYBtIKgA
AABY0Xe5OXnl2VI7Pv0v5Tp9fUeY0vH5qqlplq4LUDtnpQsAAACwZ99kH5XbuWXZuwqKFSwGsCE8
UQEAALCW8gr9np9ThBDakqpf7uqEELcrbipdFGAbeKICAABgLWlXr0rrvhad/WDThQ5KlwPYEoIK
AACAtWy5dERq5JVnyztVANQFS78AAACsZe+NlMYP0sKZI7/QHBFUAAAArCW3zAJPUYb49238IIDN
IagAAAAAUB32qAAAAFje9cLygkKd0lUANownKgAAAJa3+PtPwg9EK10FYMMIKgAAAKrW2y9I6RIA
BbD0y1bdvXs3NTX15MmTGRkZFy9evHnzZlhY2HfffWeRwXNyclJSUg4cOHD58uXs7GwvL6+goKDw
8PCoqKioqKgWLVrUcZwzZ86kpKSkpqbm5OTk5uYGBgYGBwdHRkZGRUUNHDjQwaGWM0zS0tK++uqr
I0eO5OXlBQYGRkZGxsbGDhkypNYPAgBgTzp7ByhdAqAAgortuXHjxvr161evXq3Vag1f1+v1jR+8
tLR07dq1CQkJ9+/fl1+8ffv25cuXDx8+vHLlygEDBqxatWrQoEHmx/n5558XLFiwadMmwxeLioou
XLiwb98+IURsbOzy5ctDQkJMfryiouLtt99esWKF0Wc/+uijGTNmJCYmurq6Nvh7BAAAgPoRVGzM
zp07p02bdu3aNWsMrtPppk+fvnnzZjN9Tp8+PWLEiB07dowcObKmPjdu3Bg9enR6erqZcZKSks6c
ObN3794OHUxc07ty5UoppWg0mkmTJnXo0CEnJ+fvf/+7Vqv94IMPfHx8Fi9eXNfvCgCAJmeBfzsE
mj2Cii35+OOPp06davjKmDFjhgwZEhYW5unp6e3t3cjxV69eLacUNze3+Pj4kSNH+vn5lZaWXrx4
8ZNPPklOThZClJaWjh8/PiMjIyjIxJJZvV4/efJkOaWEhobOmTNn4MCBXl5eRUVFp0+fXrdu3Y8/
/iiEuHjx4qRJkw4ePOji4mI4Qn5+fkJCghDC39//22+/7dq1q/T69OnThw8fnp+fv2zZsj/96U/t
27c3mjo9Pb2oqGj48OGN/DkAANBgeiEchBi7dc3F0h+UrgWwbQQVm7F3717DlDJ9+vTZs2d3/v/s
3XtclGX+8PFrGEAERkUQ5SChIGrlGXRNSaQwd8sSa83MzX3SLNdz0mYlGrrmrxSPpT2umdXzK43W
trSDYpkH0hQTjykpyDk1RBwQnAHm+eNu750GGAbmHmYGPu8/en1n7uv+XtdAIl/v69Cjh1L58/Ly
li5dKsWdOnXas2dP//795av9+vUbN27cokWLli9fLoQoLS197bXXNm7cWDvPF198sWvXLimOiYlJ
SUnx8/OTr0ZGRk6YMGHixInSBLCDBw9u37590qRJxhkOHTpUWVkphEhMTJSrFCFEREREUlLSlClT
9Hr9wYMHTQqVioqK6dOnp6enz5w5c/369dZ9MQAAaLSs6zc+PnVKCBHQrt3Oku1Kpb1b00epVIBz
Ydcv51BSUjJr1iwp9vDw+OSTT958800FqxQhREpKirzo5a233jKuUiSurq5JSUkxMTHSy7fffvvK
lSu182zatEkK3NzcNm/ebFylSHx8fDZv3qzRaOQ8Jg3y8/OloPYYBgz47WjevLw8k0tr166VHuOM
GTOmno8IAIAN/XjtwkuZC17KXLDyQh3/kAegsShUnMPy5csvXbokxR988MGjjz6qeBcff/yxFPTs
2XPs2LF1tnFzc5s3b578MjU11aRBUVHRzp07pfiZZ54JCwurM09QUNCMGTOkOC0t7fz588ZXdTqd
FHh7e5vc6OnpKQUVFRXG758+fXrRokVCiGeffdbM4hkAAJqBItvbCCGiOvblcQpaMwoVJ3D16lV5
LtPs2bMfe+wxxbsoLCz84YcfpDg+Pt5k0Yix6Oho+ap8i8x4Af0DDzxgpse4uP+egZWRkWF8Sd7+
2KQaEUKUl5ebtBFC6PX6efPm6fX6oKAgaXELAAB2lH0rW5E8ex5e+afQKEVSAc6IQsUJ7Ny5U1qz
4eHh8cILL9iii+zs//5IladX1cnHx2fQoEFSfPz4cZOrFy9elOO77rrLTB7jq9LaellQUJAUnDx5
0uSuM2fOSEFg4H93lH/nnXe++eYbIcTKlSs7d+5splMAAJrBrZpyRfJ0cPd+fejUfh3DFckGOB0K
FSfw/vvvS8Fjjz0WHBwsxXq9/sqVKz///POVK1eqqqqs7MK4UAkJCTHfWF7gnp6eLk/TkmRmZsqx
XG/UqVOnTu3bt5dik6lfw4cPlx7aLFmyxDhhbm7ukiVLpDg6OloKsrKyFixYIIQYN27c448/bn7k
AAA4nWd6s/YSrRSFiqO7cePGgQMHpPihhx4SQhw6dOi5554LCAjo0qVLREREly5dgoOD58yZc+rU
qSb3UlJSIsdy/VCfTp06SYFer5fnYkmuXr0qt/Hw8DCTxMXFRd7d+NdffzW+FBwcLC04yc/Pj4yM
nDt37vr16//+978PHDhQWqjz0ksvhYeHCyFqamoSEhJKS0vbt2+/YsUKTqwHALQ8I0J6NdwIaInY
ntjRXbhwQY6Dg4OnT59ee5usK1eurFu3bt26da+99tqLL77o4tLo+tO43mjbtq35xvKKdulG4/Nb
5H3Dam/2VZtcEV2/ft3k0oIFC27cuJGcnKzVateuXWt8afr06YsXL5bi7du3f/rpp0KI5cuXd+/e
vcEeAQAA4Cx4ouLojNdvLFiwoHaVYuzll19euHBhE3oxLlTUarX5xu7u7nJsst795s2bUuDq2nAN
LC+Ir12ouLq6rly58uDBgzNmzLj77rs1Gk1ERMQzzzyzd+/et956S7qxqKho/vz5QoiRI0dOmTKl
we4AByFvB2T5vkBNuMVMEst7UaS7+gKDwSAHFt7ShE9h3EuL6a7OXpTqznx7a3qxvDtFPlQTPl3T
ctqdUh/Kwk+neHfm+zW+Wt8t1nRn61sc8/8ZJ8ITFUdnfGDIoUOHhBAhISGvvPJKXFxcUFCQTqf7
6aefNmzYsHXrVqnN8uXL77nnHmmSmOVqamqaNjyTG5u2Wqa6urrO94cPHz58+PD67lq4cGFRUZGb
m9vq1auNa6emMRgM7BimFL6YEEKoVCrpb2hLgiZka0IvlndXO38L7s6mvTQteTN312S1UxV0dBFt
GrrNYm1VbY1/ltrrQ9m030blVORHh/U/dprcnTwfBJajUHF08jMKSWxs7EcffeTv7y+9dHd3j4qK
evfdd3v37v3iiy9KbyYkJIwaNcr6390d2ZdffrllyxYhxKJFi/r162d9QpVKxU8QpSQlJfHFBNAK
fXLhh3/u/0qpbGHe4fwsRSvH1C9HV1paKsd/+MMf/vWvf8lVirGEhIRx48ZJ8YULF/bu3dtM47OH
kpKSOXPmCCH69+8/d+5cew8HAAAAyqNQcXTGT1SWLFnSoUOHOpu5uLgkJCTIL/ft22fzkdnPsmXL
pANb1qxZI51eX1FRsXXr1ocffrhr166BgYGjR49+6623jGs8AACspK2oPp5Vnn6pLLPQ9DxiALbA
1C9Hd/v2bTkeOXKkmZZDhgwJCgoqKCgQQuzfv79RvTR5Y1+TRfNNy2N+I2MThw4dSk5OFkLMmTNn
xIgRQojc3NyJEyempaXJbYqKinbv3r1hw4aUlJQ777yzCUMCAMDEkV8uzExbI4To6d398/gFtu4u
1LuLrbsAHBxPVByd5UtNXFxchg0bJsUmRyg2yMvLS45NznCsTa/Xy7HJXsbyjsO3bt1qsFO5I+MN
js0rLy+fPXu2ECI0NDQxMVF6Z8KECVKVMmjQoH/84x+vv/56TEyMEOLcuXPjxo2Tj3YBAMAapTpt
ZsWZzIoz2ZXZzdDdAL+IZugFcGQUKo7O+Jf4yspK843l5StardaSUkGm0Wgs70U+LEXUKlQ6duwo
BSZnONapuLhYCho8YlK2evXqEydOSIGvr68Q4sMPPzx8+LAQYtKkSWlpaa+88srf//73vXv3ShPh
Lly4sHHjRguTAwBgxs1bde9RaSMP3BHZnN0BDohCxdHJv/qLus4bMWG8O3Cjdv0y7uXatWvmG8vP
KDQajXGFI4wOrS8tLTW/RKS6ujo/P1+KAwICLBnkyZMnlyxZIoR48sknH3nkEenN7du3S8GyZcvk
g1nUavXChQuDg4OFEB988EGTN18GAEB2pPhkc3Y3LLBnc3YHOCAKFUfXu3dvOTY+pb5ORUVFUhAS
EmLJkYsy42Pdc3NzzTc+ffq0FERFRZn00qtXLzmWVsuYGar8ZMb4M9ZHp9PNnTtXr9f7+vouX75c
WgxTU1Nz4MABIcSAAQNCQkKM27dv3z46OloIcenSJUse7wAA4Dj6tutr7yEA9keh4uiMDwn59ttv
zbTU6XTSb+1CiMGDBzeql/DwcDk+cuSImZbXrl3LyMiQ4r59TX+MGhcq0hyt+pw9e1aOe/To0eAI
N23a9N133wkh3njjja5du0pvVlRUSAtmwsLCat8iNysrK2swPwAAjqOPTx1/rwGtDYWKo7vrrrsG
DBggxe+++66ZhwP79+8vKSmRYjMHutfJz89P3lJsx44dxqtQavcix9IjC2MDBgxwc3OT4s8++8xM
j7t375bjBsuqixcvvvzyy0KI0aNHP/XUU7Ub1LnbmHwWrJXH9AIAYImC35/RbI3YoEFKpQKcF4WK
o1Or1X/729+k+MqVK8uWLavz1+7bt28vXbpUfvnggw82tqMJEybIvbz33nt1ttHr9atWrZJiNzc3
aXMtY35+fuPHj5filJSUo0eP1pknNzdXXuMeGxt7xx13mBlYdXX1/PnztVqth4dHcnKy8WQzT09P
aWvjy5cv174xLy9PCqSzVgAAaJrCEt3xrPKyygZWPJ4tvahUj7F3NDwpGmjxKFScwBNPPBEZ+dvW
H2vWrFmxYkV19e82HqmsrHz++ecPHjwovZw6darxVC65zbZt29atW3fs2LE6e4mPj+/cubMUv/DC
C7WPjKyqqkpMTJS22BJCzJ4923gJvmzq1KlyPGXKlJycHJMGJSUlU6dOlfcWk8uw+mzbtu3zzz8X
QixZssTkUBSVSnXvvfcKITIyMkyWxGi12u+//14IERIS4ufnZ74LAADM2HRu58S0eXuupjZPd15q
r1CNRdvMAC0bhYoT8PLy2rBhg3wq4osvvvjwww/v2LHj1KlTx48ff//992NiYjZs2CBd7dat2z/+
8Y/aSebPn//EE0/MmTNn8ODBhw4dqt2gU6dO8jOZysrK2NjYhISEAwcOXLx48dy5czt27HjooYde
f/11qYGvr+/zzz9f52hjYmLk2VlnzpwZMmTIqlWr0tPTs7KyMjIy/vnPfw4bNiw19bef9ffdd9/Y
sWPNf/y4uLjnnntuyJAhM2fOrH31z3/+sxBCr9cvXrxYPuDFYDAkJydLuwJMnjxZrVab7wIAADMK
K65mVpwprmqmg7kG+rCSHhBCCFXzT9+XeqypqamurtbpdJWVlbdv3w4KCmrmYTidr7/+Oj4+3vwh
J8HBwZ9++qn8+EVWU1Oj0Wjkk1UWL1786quv1r69uro6ISFhzZo15kfi6en59ddf116gIispKRk3
bpy09t2MPn36fPXVVxZ+60tKSuo8F7K8vDwuLk56zjNs2LD4+Hh3d/c9e/bs2rVLCBEeHn7o0CH5
SZEZarXa5DkVmiwpKWnx4sX2HgUAKGba3o3/zPpAftnb6+4/tZ/Qt2N4xzaaLh3cAju6B/q4127W
ZDMjnlof85z1eYAmKygoaNOmjYeHh7u7u1qtdnFxEfUsCbYpnqg4jdGjRx84cEA+e762hx9++Ntv
v61dpQghXFxcjLcADgwMrDODWq1esWLFunXrzJzAOHTo0H379pmpUoQQPj4+n3zyyaxZs8y0mTRp
0pdffml5gVrf6fVeXl7btm2TvixpaWkJCQmzZ8+WqpSePXvu2LHDkioFAAAzftH+7mSwnIrs5MKF
k89MGHP8wSe/f37TuZ3KdvdHjnoEhBBCNOKoDdhdVFTUN998s2/fvi+++OLEiROZmZlt27bt3r37
sGHDHnjggeHDh5updDdu3Dh//vysrKz4+PiJEyfW18zV1XXWrFmPPvro7t27U1NTMzMzL1++rNFo
QkJCIiMj4+LiRo4cKZ+raIavr++6deumTZu2Z8+effv2Xb58OS8vr0uXLqGhodHR0XFxcY3dQNmM
kJCQ1NTUlJSUHTt2pKen63S6vn37PvLII5MmTaqvvAEAwHLZldnGL2/IL796AAAgAElEQVTVlMtx
ZsWZzJJ+l6/dlh6qKOJP3ShUACGY+gVImPqlIKZ+AWhh+nz07Bnt6fqu+rr6+7r5vzl8bsql/dZP
/Qrz6n7xyf9nZRLASg4y9YsnKgAAAE1XXHW1uOrqjdvKHKLSux1HPQK/oVABAACw1idnz+TfLmi4
XUPuCx5ofRKgZaBQAQAAsNbHxVsUyRPs2UWRPEALwK5fAAAAjuIOtoEB/oNCBQAAwFFE+UfYewiA
o6BQAQAAqFdmYYW+qpm2SPVUezVPR4BToFABAACo18pzWy9UnGmevrp7dm+ejgCnQKECAABQL5Nj
6W1K3dzHVAAOjUIFAACgXibH0tvUYL/+zdYX4PgoVAAAABzCXX5B9h4C4EAoVAAAAOyvk7v/nP4P
23sUgAOhUAEAALC/zm0623sIgGOhUAEAALC/UG/OpAd+h0IFAACgbs10fooQQoiAthQqwO+42nsA
AAAAjqhYW3U4U9s8pz32bdf3mb73NUNHgBOhUAEAAKjDvsLjfz4+r3n6GuLXL8o/onn6ApwFU78A
AAAAOBwKFQAAAAAOh0IFAAAAgMOhUAEAAADgcChUAAAAADgcChUAAAA7U7uo7D0EwOGwPTEAAIB9
dGnTuVv7ACHEuB5R9h4L4HAoVAAAAOxjTNCoTfdPt/coAAfF1C8AAAAADodCBQAAwD66eLWz9xAA
x0WhAgAAYB99O4bbewiA46JQAQAAAOBwKFQAAAAAOBwKFQAAAFOZhRX51/X2HgXQqrE9MQAAgKmE
H9ZmlJ62aRfh3mE2zQ84O56oAAAAmMquzM7TZdu0i79G/Mmm+QFnR6ECAABgBzP6jvF0V9t7FIDj
olABAAAwVV1tsGn+/u37dHD3/lO3SJv2Ajg1ChUAAABTOZW2nfcV5dvfpvmBFoDF9AAAoOXLLKy4
WVGtUqkiAjw0bRuecHWrprwZRgXADAoVAADQ8m04szOrtEgI8crQ+CHBIWZaGgyGX27YfGPiP3Tp
aesuAGdHoQIAAFq+b4q/OaM9LYR4qvwPQ4S5QmXXuUv/78J+W4+nnZuXrbsAnB2FCgAAwH/tLEr9
+NcPbNpFn3Z9bZofaBlYTA8AANCs5t49PjLQ3FMdAIInKgAAoDWw9XbDjTIuYnAHd297jwJwdDxR
AQAALZ+ttxs2725NH+OXVCmAJShUAABAy8d2w4DToVABAACtmq6qmWaFeaq9RK2nKwDqQ6ECAABa
kevaKpN3Pr90VI6LtVW2q1t6eHW3UWagRaJQAQAArUj6jVO130zNPicFL+5LOVn8s+Kd9ukQJoT4
P70eFEL4tGGBCmARChUAANDafZ2TLgXv/LI+o/wHxfN7u2mEEJPvjBVC9GoXrnh+oEWiUAEAAK1d
hg2eopjo5tm9g7u3tEwFgCUoVAAAQGt36uZpW3fRSxMmhOju2f1O30Bb9wW0DBQqAACgtftVfzXr
+g2bdjHAt4cQQq0SwZ5dbNoR0GJQqAAAAIi0/J9smn9Il55CiMF+/d3V/PYFWIQ/KgAAAOKbghOK
51SpVEKIbp7dhRAPh0cJIdQuqntDeiveEdAiudp7AAAAAPZ3tDhDwWwDO/Sd1X9MqHfAzqz0PXnH
/9Clp/R+lH9EB3e2JwYsQqECAAAgciqzE3Z9W+elJ7qOvaDN+rGuA1jqM6hjv79GPCiE8HL13pN3
PDqol/R+F6921g8VaCWY+gUAACBu1ZQnFy6s85K3m2ZQx36Wp3o4aNTYsCgpjvKPUKtED5/fdvr6
U7dIK8cJtB48UQEAAGhAkKa95Y1fiXxicOee8ss724fZYERAy8cTFQAAgAbc1aERxUZU5wjjlz07
Bis9HKBVoFABAACwocl3jrT3EACnRKECAABgQ6GaAHsPAXBKFCoAAAAN4JRGoPnxpw4AAKABnNII
ND8KFQAAgAZwSiPQ/ChUAAAAADgcChUAAICG7XvoTXsPAWhdKFQAAEALl1H8sxyfvVqQsOtbQ+OT
xAQOVHBIABpEoQIAAFq4jOJMOf6+7NvkwoVCNKFUEf7u/soNCkADKFQAAEALd7L4oiJ5/Nt0ViQP
AEu42nsAAAAAtmU89cuYQYjDmdpz+RUK9nW3po+C2YDWjEIFAAC0Rt9lXtmVefbjX9/J02XbeywA
6kChAgAAWriauhakfJi745+FHzT7WABYijUqAACghdNX1yiSZ1TXQYrkAWAJnqgAAACY08ZVJQWz
+o3RtFUfvXLhxLWff7l9xaTZnR3Ce3QIGBt6r0qomn2MQAtEoQIAAFqdzMIKXZWlOxSPCBggBaGa
gFcHTRFCrDnx2bxjr5s0S+o347GeQxQcJNDKUagAAIBWZ0X6Z4dLM5p8e7Bnl9pv3uHjY8WIAJii
UAEAAC2codYSlY+ubrlVU97khJ7uapVQGYRB4+qtrSqT3ozyj2hyQgC1UagAAIAWTl9rlpc1VYoQ
4k/dImumpUmxatM91qQCUB92/QIAAC2crtrS5SgAHAeFCgAAaOF0+mp7DwFAozH1CwAAtFgGgyjW
6vP1OTbthf2IAVugUAEAAC3W4Z+1hwsvlFeX2a4Lw7TvbZccaM0oVAAAQAukrajWtFUvPfXm2bIz
9h4LgKZgjQoAAGhRdFWGYznXjvxyQQhx7OYPebpse48IQFNQqAAAgBblxC95W858W6rTCiGKq67a
ezgAmohCBQAAtCjZN4veLlhr71EAsBaFCgAAaFEu/loihMi5UWrvgQCwCoUKAABoOTILKz7J+1oI
cfzaz7paB9IDcCLs+gUAAFqIYm3Vwcs5J8uPCiGOl5z815FiKxPerekzqusgJYYGoNF4ogIAAFqI
whLd+uy3pTiz4syszKnW5/xL75Ge7mrr8wBoLJ6oAACAFuLstQLpcYpEkS2/+vv26O9rfRoAjcYT
FQAA0ELs/+VHew8BgGIoVAAAQEugqzKcvHnK3qMAoBgKFQAA0BIUlugyK87aexQAFEOhAgAAWoLT
V/M4hx5oSShUAABAS/BNAQtUgBaFQgUAALQER4tP2nsIAJREoQIAAJyejRao+LTxVjwnAAtRqAAA
AKd3+mq+LRaoDPSLUDwnAAtx4CMAAHA+BoNBpVLJL1Pzjivexav9Zo7o2kvxtAAsxBMVAADgfKbv
X31DVya/PHZd+RNU7uoQFhM4UPG0ACxEoQIAAJxPWtGFYSnzj2eVayuqhRBny04r3sUdPj6K5wRg
OQoVAADgZAxCCCHOlZ+efWR5ZlGFEMIWC1Si/FmgAtgTa1Sc3tdff/3HP/5RfmkwGKzPmZOTk5qa
unfv3kuXLmVnZ3fo0KFr166RkZGxsbGxsbFt2rSxMM+JEydSU1MPHjyYk5OTm5sbFBQUEhISHR0d
Gxs7ZMgQ47nFdUpLS/voo4/279+fl5cXFBQUHR09YcKEESNGNHgjAKAFK9ZWHc7U6qsMQojvy779
4GJfg+FP9h4UAOWpFPm9tlGkHmtqaqqrq3U6XWVl5e3bt4OCgpp5GC3DjRs3hgwZkpmZKb9j5Te0
srJy3bp1SUlJt27dqrNBVFTU6tWrhw0bZj7PL7/8kpiYuHnz5voaTJgwYfny5aGhoXVeraqqeuWV
V954443al2bOnJmcnOzu7m5+AI2lVqurq6uVzdlqJSUlLV682N6jANBipWafm3loTf7t7Fs15UKI
CI+7era9e2fJdmV7WTxoyquDpiibE3AWBQUFbdq08fDwcHd3V6vVLi4uQojm/5dinqg4t+XLlxtX
KVbS6/UzZszYsmWLmTbHjh27//77P/vss1GjRtXX5sqVK2PGjElPTzeTZ9u2bSdOnPjqq6+6detW
++rKlSulKkWj0UyePLlbt245OTnvvvuuVqt98803fX19X331VUs/FQCgZSnVaTMrzsgvMyvPZlYq
fILKwA59qVIAu2ONihP7/vvv63zm0GRr1qyRqxQPD4+FCxceOHDg/PnzGRkZ27dvlyuTysrK8ePH
5+Xl1ZnEYDBMnTpVrlLCwsLWr19/9OjRzMzMY8eObdiwoXfv3tKlCxcuTJ48Wa/Xm2TIz89PSkoS
QgQEBBw9enT9+vXPP//82rVr09PTg4ODhRCvvfZaTk5O7a7T09O/+eYba78KAIBW7//0Yi4ZYH8U
Ks7q1q1bs2fPVjBhXl7e0qVLpbhTp06HDx9eunRpdHR0z549+/XrN378+C+++OKll16SGpSWlr72
2mt15vniiy927dolxTExMUeOHJk5c2ZUVFSPHj0iIyOnT5+elpY2evRoqcHBgwe3bzd9WH/o0KHK
ykohRGJiYq9e/93APiIiQipg9Hr9wYMHTe6qqKiYPn36/fffP2vWLGu+DgAATOoVa+8hAKBQcVpr
1649fvy4EKJbt25DhgyxPmFKSopWq5Xit956q3///iYNXF1dk5KSYmJipJdvv/32lStXaufZtGmT
FLi5uW3evNnPz8+kgY+Pz+bNmzUajZzHpEF+fr4U1B7DgAEDpKD28xzpkYsQYsyYMfV8RAAALNLB
3dveQwBAoeKcTp06JS9WXrFiRadOnazP+fHHH0tBz549x44dW2cbNze3efPmyS9TU1NNGhQVFe3c
uVOKn3nmmbCwsDrzBAUFzZgxQ4rT0tLOnz9vfFWn00mBt7fp3xOenp5SUFFRYfz+6dOnFy1aJIR4
9tlnzSyeAQA4u6ISXf510znDAFokChXno9Pp5s6dKy3tGD9+/Lhx46zPWVhY+MMPP0hxfHy8m5tb
fS2jo6Plq/ItMuMF9A888ICZHuPi4uQ4IyPD+JK8/bFJNSKEKC8vN2kjhNDr9fPmzdPr9UFBQdLc
MABAC2P4z9kpyWmHduWazv4F0CKx65fz2bx58759+4QQPj4+r7/+uiJbxWVnZ8uxPL2qTj4+PoMG
DTpy5IgQQpp7ZuzixYtyfNddd5nJY3z1p59+Mr4k71V98uTJwYMHG186c+a3bV4CAwPlN9955x1p
Df3KlSs7d+5splMAgJP64niJEMK7rTq5cKG9xwKgmfBExclcunRpwYIFUvz666/Xdw5JYxkXKiEh
IeYbywvc09PT5WlaEuO9ks2fjdOpU6f27dtLscnUr+HDh0sPbZYsWWKcMDc3d8mSJVIcHR0tBVlZ
WdIXZNy4cY8//rj5kQMAnJG2ojrx/JJNWe+vOvuulan83f3NN/BUew31N10hCcAueKLiTGpqahIS
EqQl73FxcX/961+VylxSUiLHcv1QH3lJjF6vLy8vNz578erVq3IbDw8PM0lcXFy6du1aWloqhPj1
11+NLwUHBy9atCgxMTE/Pz8yMvLpp58OCwvLy8vbsmVLcXGxEOKll14KDw8X//mClJaWtm/ffsWK
FZxYDwAt0rnigozyHzLKTecbN4F/m85XdVfNNOju2f37sRus7wiA9ShUnMlHH33073//Wwjh5uaW
nJxsZiVJY8lrP4QQbdu2Nd9YXtEu3ejj4yO/lPcNq73ZV21yRXT9+nWTSwsWLLhx40ZycrJWq127
dq3xpenTp8sbCWzfvv3TTz8VQixfvrx79+4N9ggAcEZ55UXN1peaf/ICHAaFitMoLCycP3++FCcl
JfXp00fB5MaFilqtNt/Y+BGKyXr3mzdvSoGra8P/a8kL4msXKq6uritXrhw7duy2bdv279+fk5MT
EBAwYsSIxx9/PDY2VnpyUlRUJH1BRo4cOWWKAucHGwwG65NAUt8XU6VSGQwG6TsoBVLLBoMm3GJl
d9b0Yq/u6uu3zu9Cs3VniUYNyeQWW3dn/Qdskd1Z2Ys13z5bG+zXX/znh5iCH0qRr1gT/oA0YcC2
vteaL1HzdKfgCI3vNXMV9aFQcRovv/yydG7JgAED5syZo2zympoaRW6sqqpqQpLq6uo63x8+fPjw
4cPru2vhwoVFRUVubm6rV682rp2axmAwyAtgYKX6vpgW/kVr5W/8jb3Xmu6s/FCKd2e+lyZ3V/s7
aEkvjQrMfAoz/5vZqLs6u1akuzrbKP7pzAdKdWf+QyneXV4HIczNJm6EyopK8w1yc3KkDSTNDMn8
1Sb/uavz9qZ9xZT6EaHgHy5L7m2GW+zYnTwfBJajUHEOO3fufO+996R43bp1xpOvWqcvv/xyy5Yt
QohFixb169fP+oQqlYqfIEpJSkriiwlAQZ9c+GHz/q8VSeXR1kNo673659DRf7v7oZjAgYr0BcBK
7PrlBK5fvy4fs/j888+becjQSpSUlEjPlPr37z937lx7DwcA0EKMv+MBqhTAcVCoOIGlS5deunRJ
CBEWFvbKK6/Yezj2t2zZMunAljVr1kin11dUVGzduvXhhx/u2rVrYGDg6NGj33rrLWlLMQAAZK78
4gM4D6Z+Obr9+/evWbNGiletWtWxY0db9GJ+LrgZJovmm5bH/EbGJg4dOpScnCyEmDNnzogRI4QQ
ubm5EydOTEtLk9sUFRXt3r17w4YNKSkpd955ZxOGBABokaJ8+2eUnq7vqruaOgZwIBQqDq2srEye
2jRp0qQxY8bYqCMvLy85NjnDsTa9Xi/HJnsZyzsO37p1q8FO5Y6MNzg2r7y8fPbs2UKI0NDQxMRE
6Z0JEyYcPnxYCDFo0KD4+Hg3N7evvvrqu+++O3fu3Lhx4w4cOODv38DxXgCAVs7f3X96nzF9Owfb
eyAA/otCxaGtWrUqIyNDCOHh4TFjxoyioro3kr99+7YcFxYWyrG/v78l2wQLITQajRxXVjawI4p8
WIqoVajID3xMznCsk3R6o7DgiEnZ6tWrT5w4IQW+vr5CiA8//FCqUiZNmrR582Zpy+P58+cvWLBg
5cqVFy5c2LhxIwu7AQDm+bfp/OogBXa6B6AgChXHdfr0afk37MrKyqFDh1pyV1BQkBwXFBQEBgZa
cpfxjLJr166ZbywfP6/RaIwrHGF0aH1paal0YHx9Saqrq/Pz86U4ICDAkkGePHlS2vT2ySeffOSR
R6Q3t2/fLgXLli2TD2ZRq9ULFy7ctm1bfn7+Bx98kJiY6OLC03wAgFC7cJwF4DT47c1xSQvom4fx
se65ubnmG58+/dvs3qioKJMnNr169ZLjgoICM0mKiorkJzO9e/ducIQ6nW7u3Ll6vd7X13f58uXS
YpiampoDBw4IIQYMGBASEmLcvn379tHR0UKIS5cuWfJ4BwDQGtwb3KvhRgAcA4UKhBAiPDxcjo8c
OWKm5bVr16TZaEKIvn37mlw1LlSkOVr1OXv2rBz36NGjwRFu2rTpu+++E0K88cYbXbt2ld6sqKiQ
FsyEhYXVvkVuVlZW1mB+AEBrMCFihL2HAMBSFCqOa+zYsQbLPPTQQ/Jdxu9bOO9LCOHn5zdy5Egp
3rFjh/EqFBP79++XY+mRhbEBAwa4ublJ8WeffWamx927d8vx4MGDzQ/v4sWLL7/8shBi9OjRTz31
VO0Gde42ZvjPidoGo6O1AQBO53pZtY0ye6m9Gm4EwE4oVPCbCRMmSMGVK1fee++9Otvo9fpVq1ZJ
sZubW0xMjEkDPz+/8ePHS3FKSsrRo0frzJObm7tx40Ypjo2NveOOO8wMrLq6ev78+Vqt1sPDIzk5
2Xiymaenp7S18eXLl2vfmJeXJwXSWStoThSHAJTy3dmb3+T8pGDCOb0my3G4V3chhEqoPN34jQhw
OPyxbC0qKyu3bdu2bt26Y8eO1dkgPj6+c+fOUvzCCy/s27fPpEFVVVViYqK0xZYQYvbs2XUe6jJ1
6lQ5njJlSk5OjkmDkpKSqVOnynuL/e1vfzM/8m3btn3++edCiCVLlpgciqJSqe69914hREZGhsmS
GK1W+/333wshQkJC/Pz8zHcBAHBYs0698PGv7yiYcHjn/nI82K+/Ydr3NdPSfnhso4JdAFAEhUpr
MX/+/CeeeGLOnDmDBw8+dOhQ7QadOnVaunSpFFdWVsbGxiYkJBw4cODixYvnzp3bsWPHQw899Prr
r0sNfH19n3/++To7iomJkWdnnTlzZsiQIatWrUpPT8/KysrIyPjnP/85bNiw1NRUqcF99903duxY
8yOPi4t77rnnhgwZMnPmzNpX//znPwsh9Hr94sWL5QNeDAZDcnKytCvA5MmT1Wq1+S4AAADgaNie
uFWoqanZunWr/HLv3r3Dhw+v3ezpp58+d+7cmjVrpJfJycnSGfAmPD09P/30UzMLYNasWZObmyut
fb9y5cr8+fPrbNanT5/33nuvwSrC399/48aNJSUlJme2SJ544oktW7YcPnz4nXfeOX/+fHx8vLu7
+549e3bt2iWECA8PnzFjhvn8AIBW4t2YV1RC5en+3793RnW700x7APZFodIquLi49O7d+/jx49LL
+moMtVq9YsWK7t27JyYmlpaW1tlm6NCha9asMb/83cfH55NPPklKSlq/fn19bSZNmrR8+XLjU1/M
q+/0ei8vr23btk2cODHtP+RLPXv2TElJkeezAQBaub9GPCiEuCeo1+JBU4QQFTrDY2FsAgY4LgqV
1mLjxo3z58/PysqKj4+fOHFifc1cXV1nzZr16KOP7t69OzU1NTMz8/LlyxqNJiQkJDIyMi4ubuTI
kfK5imb4+vquW7du2rRpe/bs2bdv3+XLl/Py8rp06RIaGhodHR0XF9fgTl+WCwkJSU1NTUlJ2bFj
R3p6uk6n69u37yOPPDJp0qT6yhsAgOPLLKw4nlWm09com7aDuzeH0ANOQdX8m/NIPdbU1FRXV+t0
usrKytu3b1v+L+uALajV6upqW21/2dokJSUtWrSozj2jAcBySd/veCfzX3m6bKUSGqZ9r1QqoGUr
KCho06aNh4eHu7u7Wq12cXER9ZwGYVMspgcAAI6osOKqglVKN8/uSqUC0DwoVAAAgMMpLNHdVnTS
F2c7Ak6HQgUAADic93648PP1QnuPAoA9sZgeAAA4EF2VoVirfzn3WWXTtnVj4RzgZChUAACAAzmd
W5aeVa5szme6/2XT/dOVzQnA1ihUAACAPUmPUIQQbmqVXzu3j3L/nZy10d6DAmB/FCoAAMCeThUW
bzt1SgjRxVvzZL9+v1ZqFe9C7cK8L8D5UKgAAAB72pW3P7kwWQgR7N7tl7IpP99UeA19N8/uG2IV
XvECoBlQqAAAAHsqrLgqBfm67OTChYrnD/bsrHhOAM2A7YkBAIDdHM8q11UZbNrFXR16CNv2AMAm
eKICAADs5nhWWbG2SqlsL9z9f3749aRKZTh+LbOs6retw6L8I1Qq1qgAzodCBQAA2M1zWePaungq
lW1iz5g37nlGCDH/0KZV57ZKb/bxD1YqP4DmxNQvAABgT7dqmn5qSrh3dzlePGhKf98eUnxf0ED5
/Sj/iCbnB2BHFCoAAMBZRfn0lYJX+818ddAU+f17gnpJQTfP7nXcBsAZMPULAADYgbaiOrOo0mDF
Ovep4Y96uXpL8SPhUcaXOrj/9r6X2qvJ+QHYF09UAACAHRzP+3V35iWVaPoy9/E9YoZ37i/F8qQv
Y2FePE4BnBiFCgAAsIPvrh16Jfc5a56oxHUdJAV1zu+6W9OHE1QAp0ahAgAAmpW2ovp4VnlmyS9N
ziBvN+yudhFC3NU+rHYbF5Wqj0+PLt7tmtwLAPuiUAEAAM2qQFv60bkfcm4WNe32MXdEfxz7mhT3
7RwshAhrH1i7mU8br54dA1PHrGjyOAHYF4vpAQBAszpT8vOqokSDoYmTvt4fmdjB3XvQj/2EEKGa
ACFEbODA2s36+0bM7PuwNeMEYF88UQEAAE5j5p3jpR29No6YJ78pPVcxMaRLz+YbFgAboFABAADO
IS5g2Prhc6XY+BhH6bmKiT+GRjbTsADYBoUKAABoPtqKam1FTdPmfU2LeKz2m8+FP1VnY/koFQBO
ikIFAAA0n8yiirN5txRMaPxoBUBLwmJ6AADQHAwGoVKJDy5+uaP4s6ZlaO9Zx+8tffzrWKACoAWg
UAEAADZ0PKvseFa5ECIisG1opzantafzdNlNSxXVuY718TxRAVoqChUAAGBDx6+f3FWSfqHy7NCy
kUMLRxbcutLkVCw7AVoVChUAAGBD6TdO7SzZLoTIrDjz3tX1Xd27NS1P33Z9FR0XAEfHYnoAANB8
mjzvy6eNl7IjAeDgKFQAAICtFJbodFVNPIHeRB+fHorkAeAsKFQAAICt7DpeUqytUiRVWPs6TnUE
0IKxRgUAACjvVGFxkKb9s1nxSiW8y49tiIHWhScqAABAee+f+/ZiaaGCCevcmxhAC8YTFQAAoLy0
ksOhBUpO1mJvYqC14YkKAABQ0g1dmRCirKp8V+5BpXKyNzHQCvFEBQAAKGlv9lkpSNceUSonexMD
rRCFCgAAUNji9C0qlSiuumZlnoEd+o4JiyrVlRn0HooMDIAToVABAAAKO1d+2tNFgWcggzr2e3XQ
FCHEmhOfWZ8NgHNhjQoAAFDerZpyBbP179xVwWwAnAKFCgAAcHT9/SLsPQQAzY1CBQAAKGZ/7nkF
s7VxVUkBexMDrRCFCgAAUMxH5xTb6UsIMYAHKUArRqECAAAU839zN12vLFMqWzs3diUGWi8KFQAA
oKSUS/vtPQQALQGFCgAAUNL31w9bn8RT7aVSqcL9OlqfCoCT4hwVAACgJOs3Jn6i61g3tcvcvo/3
92VXYqD1olABAACOxdtNs+n+6fYeBQA7Y+oXAABwLHd06GDvIQCwP56oAAAABVy+dvvXm3pFUj3Z
M0aRPACcGoUKAACwSmGJbufx68VVVwtu51ifzcvVK1QTYH0eAM6OQgUAADSdwWD4/uqJ57LmKZVw
VJdhSqUC4NQoVAAAQNO9m3E4/7pOwYQTe45UMBsA50WhAgAAmm71+feyyrMUTHhf14EKZgPgvNj1
CwAAWMXKg1Mmhv1Rjkf639PB3dvqEQFoCShUAABAU+iqDEUlOoPBYGWeZYOnCiG8Xb2FEOPDR6iE
SoHBAXB+FCoAAKAprt3UfX78ur7KqkLF29UrVBMQ3WXAH4OHC+lS0CAAACAASURBVCFG3xGp0OgA
OD3WqAAAgEa7WVH9/qkjL2e91OQMMYEDhRD9OoYLIZZETvlVqz/xayYbEwOQUagAAIBG+9cPvx6+
lmFNhn0PvSnHMYEDP7nwwz1+/a0eF4CWg0IFAAA02gtZzxZXXVUwoVcb1wEBXRVMCMDZUagAAABL
3bxV1c7TVQhhZZXi7+5v8k5v38DevoHW5ATQwrCYHgAAWOq1H/5981ZVUYm1Jzz6t+ls8k6oJoAF
KgCM8UQFAABY6sOcT/u365delGdlnrZu7EEMoAEUKgAAwFJ5uuzFZ9/IrDxrTRJvV+97AnspNSQA
LRWFCgAAaFhhie66tkoIYWWVIoQYFzxq9dA5SgwKQEtGoQIAABp2ICvH+hlfkqguESoVU78ANIBC
BQAANOzD3H/tvPa5Iqke6halSB4ALRu7fgEAgIZlV2YrksdL7cXuXgAswRMVAABgTmGJbtfxEp2+
RpFskR37KpIHQItHoQIAAMw5e+NictGafN1lRbL1941QJA+AFo+pXwAAoF5ncm+d/eV6ZsWZWzXl
TU5yZ4dwOX6wW6QS4wLQ8lGoAACAem09deRw0QUrkyT1myGEePKOeCFEXNdBCgwLQCvA1C8AAGDK
YBA/ZpcdzypLLlxoZSovtZefxs3f3f/+bnceLT6lyPAAtAYUKgAAwFTqqRuf5u/+9vo31qfq5tk9
JnBgz3Zhf414sLS82vqEAFoJChUAAGDqzcz3LlSezaw4o1TCwZ17CSEeCecEFQCWolABAAC/o62o
3lmyXalsapUQQkzqFSOE4AQVAJZjMT0AAPidc8UFSqXSuHmNvONOIUR/3x5K5QTQSvBEBQAA/E5e
eZEiee7sEP7W8LkxgQMVyQagteGJCgAAsImkfjOoUgA0GYUKAACwCT+Nm72HAMCJUagAAACb4HEK
AGtQqAAAgP8yGOw9AgAQQlCoAAAAY0cuas/lV1if525NH+uTAGjN2PULAAD8xiDE/5zdcOLGKXsP
BAAoVAAAgBBCiGJt1eFM7QXtpTxdtpWpVCrVfXf0VmRUAFotChUAACCEED/+mjn/3Jr829ZWKUKI
j+9d9VjPIdbnAdCaUagAAAAhhCjVaTMrzliZxNvVO9I/ItyvoyJDAtCaUagAAADFjAse9d6oBHuP
AkBLwK5fAADAIg8FxHXz7G6+zejQyOYZDIAWj0IFAABYJKBtFy+1l/k2QwN6Ns9gALR4FCoAAMBS
rmZ/cfB39w/VBDTXWAC0cBQqAAC0arf1NUKIohKdtqKmwca924WZu9re3FUAaBQKFQAAWrUV6Z9d
Ki7Z+sOFr7PONdjY201j5mqEJly5cQFo7dj1CwCAVi23/JeX0/73418+bLBlG1fV7SpDMwwJAARP
VAAAgCVVihBigF+ErUcCADIKFQAAYBGNq6e9hwCgFaFQAQAAllK7qIxferl6xQQO7OrZRaVSqVSq
dm2ZUg5AMfxAAQCglTIYhErVcDNjPX1+t/vw02GPrRvx7GVt0WVtkRCCvYkBKIhCBQCA1qVYW3U4
UyuE6KhxHdrD3C5eJlQqVbBnF+N3lgx9UggRqgmgRAGgOAoVAABal4ulhWsu/m+eLruHV/edES9a
fqO72qVtm/9OGv9j57gO7t42GCAACEGhAgBAa5NXXvRN6U4hREV1ubB4t2F/d/8+/kE+Hu3kd0aF
DLTF8ABAQqECAEArlafL3nH0eumtaksad/HoEtouQCX+u6hlbPhgmw0NAChUAABoxeb9NNvClj07
BgqDkOsUf3d/1qUAsCm2JwYAoPXK02Xn6bIbbNalTee/3f2QSqUSQtyt6SOE6N0+zOaDA9C6UagA
ANCKGCxelGLskTuiYwJ/W5GiVgkhxMjAQcoNCgDqwNQvZ3Ljxo2vv/760KFDP/74Y0FBgVarDQ4O
7t279z333PPggw+Gh4cr1VFOTk5qaurevXsvXbqUnZ3doUOHrl27RkZGxsbGxsbGtmnTxsI8J06c
SE1NPXjwYE5OTm5ublBQUEhISHR0dGxs7JAhQ1QN7d6flpb20Ucf7d+/Py8vLygoKDo6esKECSNG
jGjwRgBAfVJP3Tj3a0Vj71ow6Ak57urV5eTN03/qFqnouADAlMrQtH9asYLUY01NTXV1tU6nq6ys
vH37dlBQUDMPw7lUVVW9/fbb//jHP65cuVJfm+nTp//jH//o2LGjNR1VVlauW7cuKSnp1q1bdTaI
iopavXr1sGHDzOf55ZdfEhMTN2/eXF+DCRMmLF++PDQ0tM6rVVVVr7zyyhtvvFH70syZM5OTk93d
3c0PoLHUanV1tUXLSdGgpKSkRYsWUU8CjmnA/84r1l+1ZLqXLEITduGJD+SX0799+/3sf5VPSbXB
6AA4hIKCgjZt2nh4eLi7u6vVahcXFyFE8//NztQvJ1BWVjZx4sRZs2aZqVKEEBs3boyJiSkoKGhy
R3q9fsaMGS+++GJ9VYoQ4tixY/fff/+ePXvM5Lly5cqYMWPMVClCiG3bto0ePTo7u+6/KVeuXClV
KRqNRqpMZs+erdFohBBvvvnma6+9ZtHnAQDUklH+Q6OqFCHEC/0fN37pp3Ed5NNX0UEBQB0oVBxd
dXX1rFmzUlJSpJeenp4vvPDC7t27z549e+HChX379iUkJLi5uUlXT58+PXHiRL1e37S+1qxZs2XL
Fin28PBYuHDhgQMHzp8/n5GRsX379lGjRkmXKisrx48fn5eXV2cSg8EwderU9PR06WVYWNj69euP
Hj2amZl57NixDRs29O7dW7p04cKFyZMn1x5tfn5+UlKSECIgIODo0aPr169//vnn165dm56eHhwc
LIR47bXXcnJyanednp7+zTffNO2zAwDq82jYCOOXU3o9GO0/wF6DAdB6UKg4un//+99bt26V4v79
+//4449vvPHGqFGj7rzzzoiIiJiYmBUrVuzfv9/Hx0dqc+DAAbmqaZS8vLylS5dKcadOnQ4fPrx0
6dLo6OiePXv269dv/PjxX3zxxUsvvSQ1KC0tre+xxhdffLFr1y4pjomJOXLkyMyZM6Oionr06BEZ
GTl9+vS0tLTRo0dLDQ4ePLh9+3aTDIcOHaqsrBRCJCYm9urVS34/IiJCKmD0ev3BgwdN7qqoqJg+
ffr9998/a9asJnx8AEBt3q5eQgiT4+dDNQF/6h5lpxEBaEUoVBxaTU2NXDx4eHh8+OGHPXv2rN1s
6NChGzZskF9u27atCX2lpKRotVopfuutt/r372/SwNXVNSkpKSYmRnr59ttv1zkVbdOmTVLg5ua2
efNmPz8/kwY+Pj6bN2+W5nFJeUwa5OfnS0HtMQwY8Nu/4dV+niM9chFCjBkzpp6PCACtmraiuqhE
16hbRgTU/eRkWGAdfxkBgLIoVBzaTz/9dPLkSSl+7rnn5ElTtT322GPdunWT4p07d0pPJBrl448/
loKePXuOHTu2zjZubm7z5s2TX6ammq6kLCoq2rlzpxQ/88wzYWF177IfFBQ0Y8YMKU5LSzt//rzx
VZ3ut79Hvb29TW709PSUgoqK321Zc/r06UWLFgkhnn32WXmKGgDA2Ednjzy7d2Ojbrk/eFC4d3cb
jQcAzKNQcWinTp2S4/vvv99MS1dX1/vuu09+WVJS0qiOCgsLf/jhBymOj4+XF73UFh0dLV+Vb5HJ
S1OEEA888ICZHuPi4uQ4IyPD+JK8/bFJNSKEKC8vN2kjhNDr9fPmzdPr9UFBQdLcMABAbek3Tu0s
MZ1ta0aEJmxs6L1dvNqJ5t4fFACEoFBxcL/++qscN7iDc/v27eVY2kXOcsa7b8nTq+rk4+MzaNBv
h3wdP37c5OrFixfl+K677jKTx/jqTz/9ZHxJ/qTy0yTZmTNnpCAwMFB+85133pHW0K9cubJz585m
OgUAWMjf3f+lQRNCNQFh7QMbbg0ANkCh4tCefPLJ7P8wM+9LkpubKwVBQUG1V4aYZ1yohISEmG8s
L3BPT0+Xp2lJMjMz5dh8ZdWpUye5sjKZ+jV8+HDpoc2SJUuME+bm5i5ZskSKo6OjpSArK2vBggVC
iHHjxj3++O820AQANJl/m86TI/4khBgbei/HIgGwC06md2gdO3a08ADH8vLyQ4cOSfHYsWPVanWj
OjKeKmb8ZKZOnTp1kgK9Xl9eXm589uLVq1flNh4eHmaSuLi4dO3atbS0VPz+wZEQIjg4eNGiRYmJ
ifn5+ZGRkU8//XRYWFheXt6WLVuKi4uFEC+99FJ4eLgQoqamJiEhobS0tH379itWrOCvUgBQist/
fqLGBA6070gAtFoUKi3E119/XVRUJMXjx49v7O3y2g8hRNu2bc03lle0SzfKOyMLIeR9wyx5pCNX
RNevXze5tGDBghs3biQnJ2u12rVr1xpfmj59+uLFi6V4+/btn376qRBi+fLl3buz3BMA6lVUoiur
rLG8fWcvjTAIoTLdmxgAmg2FSkug1WpfffVVKR41apQ8LcpyxoVKg09jjB+hmKx3v3nzphS4ujb8
v5a8IL52oeLq6rpy5cqxY8du27Zt//79OTk5AQEBI0aMePzxx2NjY6UnJ0VFRfPnzxdCjBw5csqU
KQ121yCDofmWi6pUKqm7+gLpM0qB+ZbGgYXJreyuwV4kZrIp212jPl19/Tb2G2RhL/btrj6KdGfJ
d81y1nx/m627JnOQ7p7du/FC5VnL80wK+6OZwdj9W9aEey1Prsif2Sbc0szdKfgFseTeBjVPd3b8
+lvyRYAJCpWWIDExUV5lvmzZsib8YaipacQ/s5m5saqqqglJqqur63x/+PDhw4cPr++uhQsXFhUV
ubm5rV692rh2ahqDwSAvgLG1Jvwabc3vxE3uzppelixZ0pzdmc/WYHJFurP8szhFdyZ3mb9q66BO
dNfYXnZ2+bq+7uqUsSM1+5ODwtCU77h51nyWJvSuSE4zf4hsd4sdu7PpN6i+b1nzdNdst9T++svz
QWA5ChWnt3XrVnly1OLFiyMjI+07nubx5ZdfbtmyRQixaNGifv36WZ9QpVLxE0QpSUlJixYtsuT3
FQDNZvEmSwuV9u6aUp121cLlNh0PADSIXb+c27fffjtt2jQpjo2NffHFF+07nuZRUlIyZ84cIUT/
/v3nzp1r7+EAQMtxt6bPvofWd2nDVu8A7I8nKk7sxIkT48eP1+v1QojQ0NCtW7c2uA6+ZVi2bJl0
YMuaNWuk0+srKiq2b9++Y8eOEydOVFdX9+3bd8yYMZMmTWpwBzMAaPHm7vk4q7TI8vb9/Xo8c9dD
thsPAFiIQsVZ/fzzz2PHjpW2623fvv2//vWvrl27Njlbk2fpmCyab1oe8xsZmzh06FBycrIQYs6c
OSNGjBBC5ObmTpw4MS0tTW5TVFS0e/fuDRs2pKSk3HnnnU0YEgC0GN8Uf3NGe9rCxr4e3kKIJZEK
7FACAFaiUHFKBQUF48aNk0549PDw+OSTTwYOtGqfey8vLzk2OcOxNukZjsTkGY78BOPWrVsNdip3
ZLzBsXnl5eWzZ88WQoSGhiYmJkrvTJgw4fDhw0KIQYMGxcfHu7m5ffXVV9999925c+fGjRt34MAB
f39/C/MDQCsXoQmXdiUGALtjjYrzuX79+uOPPy5v8/Xhhx/ef//9VubUaDRyXFlZab6xfFiKqFWo
yMdTmpzhWCfpcZCw4IhJ2erVq0+cOCEFvr6+QogPP/xQqlImTZqUlpb2yiuv/P3vf9+7d29CQoIQ
4sKFCxs3brQwOQC0MOevXk/Y9W3p7TJ7DwQAmoJCxcmUlZX95S9/kac5vffee/Hx8danlQsMIcS1
a9fMN5aPn9doNMYVjjA6tL60tFQ6db4+1dXV+fn5UhwQEGDJIE+ePCntIPzkk08+8sgj0pvbt2+X
gmXLlskHs6jV6oULFwYHBwshPvjggyZvvgwAzstgMJwp+Tm5cGGeLtvCW9q5eXu684sBAEfBzyNn
cvv27eeee+7LL7+UXq5du/app55SJLPxse7SjDIzTp/+ba5zVFSUyRqVXr16yXFBQYGZJEVFRfKT
md69ezc4Qp1ON3fuXL1e7+vru3z5cmkxTE1NzYEDB4QQAwYMCAkJMW7fvn176eDLS5cuWfJ4BwBa
mD2Z2V9ePGdh44cC4iI0YZ898D+hPh3YWxyAg6BQcRo1NTUvvPDC//7v/0ovlyxZIq3WUER4eLgc
HzlyxEzLa9euZWRkSHHfvn1NrhoXKtIcrfqcPfvfA5J79OjR4Ag3bdr03XffCSHeeOMNeduAiooK
acFMWFhY7VvkZmVlTHsA0LoYhJh2JPHdgn9a2P7uTsFP9/xTTODAv/Z80KYDAwDLUag4jaVLl65f
v16KExISFi5cqGByPz+/kSNHSvGOHTuMV6GY2L9/vxxLjyyMDRgwwM3NTYo/++wzMz3u3r1bjgcP
Hmx+eBcvXnz55ZeFEKNHj67zIVJ9pxGbBADQGmQWVrz7/fnc25bO+BJCPHvXQ8/ePUYI0cHd22bj
AoDGoVBxDm+++earr74qxc8884w890lBEyZMkIIrV6689957dbbR6/WrVq2SYjc3t5iYGJMGfn5+
48ePl+KUlJSjR4/WmSc3N1de4x4bG3vHHXeYGVh1dfX8+fO1Wq2Hh0dycrLxZDNPT09pa+PLly/X
vjEvL08KpLNWAKCVWHlu65QzT1vS8m5NH+m/oZoAShQAjoZCxQls27Zt1qxZUjxhwoT169ebrAyx
RGVl5bZt29atW3fs2LE6G8THx3fu/NtRxC+88MK+fftMGlRVVSUmJkpbbAkhZs+ebbwEXzZ16lQ5
njJlSk5OjkmDkpKSqVOnynuL/e1vfzM/8m3btn3++edCiCVLlpgciqJSqe69914hREZGhsmSGK1W
+/333wshQkJC/Pz8zHcBAC2G5U+Qu3l292njLYRw5XcBAA6Jc1Qc3e7du+XJTgMGDEhMTJQ33TKv
Xbt2xtv+zp8/f8OGDVJ88ODB4cOHm7Tv1KnT0qVLp02bJoSorKyMjY2dP3/+ww8/HBgYqNPpzp8/
v2nTJnm+lq+v7/PPP19nvzExMU899dT7778vhDhz5syQIUP+/ve/33vvvR07drx58+axY8dWr179
008/SY3vu+++sWPHmv8gcXFxzz333IkTJ2bOnFn76p///Oc9e/bo9frFixdv3LhRmnhmMBiSk5Ol
XQEmT56sVqsb+GIBQEvxSMraC5VnG24nRIhX5whN+MFfD0f59rf1qACgCVTNP31f6rGmpqa6ulqn
01VWVt6+fTsoKKiZh+EUampqOnToYGbFiBlr1qyZM2eOnEej0ciHMC5evFieSGasuro6ISFhzZo1
5jN7enp+/fXXtReoyEpKSsaNGyetfTejT58+X331lYXf+pKSkjrPhSwvL4+Li5Oe8wwbNiw+Pt7d
3X3Pnj27du0SQoSHhx86dEh+UmSGWq2urq62ZCRoUFJS0qJFi9g4CGhmmYUVNyuqo74ZZWH7Ob0m
t3PzXnr6rTm9Jq+591mbjg2AcykoKGjTpo2Hh4e7u7tarXZxcRH1LAm2KR73OjSDwdC0KsWEi4uL
8RbAgYGBdTZTq9UrVqxYt26dmRMYhw4dum/fPjNVihDCx8fnk08+kaer1WnSpElffvml5QVqfafX
e3l5bdu2bdiwYUKItLS0hISE2bNnS1VKz549d+zYYUmVAgCOT1vRwD+mPLp/ruVVihBiUKeIvh3D
VSrV8M48UQHgiJj61Vps3Lhx/vz5WVlZ8fHxEydOrK+Zq6vrrFmzHn300d27d6empmZmZl6+fFmj
0YSEhERGRsbFxY0cOVI+V9EMX1/fdevWTZs2bc+ePfv27bt8+XJeXl6XLl1CQ0Ojo6Pj4uIa3OnL
ciEhIampqSkpKTt27EhPT9fpdH379n3kkUcmTZpUX3kDAE6nuKxK01aZiaxeaq/y6vI+/sHSyzv4
UQnAITH1CxCCqV+KYuoXYAvHs8oGdveu78+VQYi+Hz17RnvaklQjOg39uSyr4C+fCiFcNg2rmZam
3DABtAQOMvWLJyoAADiHohJdoI977feLtVVHMrX6Kkv/5XFk4KC/+sRKcbh3d8XGBwCKolABAMA5
lFVUi7pmae0rPD7+x+ctnyIxomuv/n4RUjzS/x6lhgcAyqJQAQDACdyuMtwuq4qo9X4TZnDHBA6U
41Hd77JqWABgM+z6BQCAw/mu8EeTd4q1VcXaqtotD/+sPZdfYfnjlIEd+hq/fLT7vU0bIQDYGk9U
AABwOBnFPxs/95AUa/W1W05Ln3+27IzlmQd17GfVyACgufBEBQAAh3NZW1T7IYmuymB8morU4JfK
q43KHKSp96QsAHAoPFEBAMDhZBT/XOf78mkqhddvHy/KP3utoLiqcYXKXR3CFBgfANgehQoAAA5n
f9EJUdeJBcVafWinNkKI5755+0Ll2cyKRkz6kkQGhlg/PABoBhQqAAA4osvaom6aQJM3i0r0hddv
u7u67CzZ3tiEKqH6g3+/UE2AQgMEANuiUAEAwBFlFP9sUqjk6bKTz20R50QPr0af0ni3ps/pJ/5v
7c3EAMBhsZgeAABHdLL4osk7FdXlmRVnMivOHLlxpGk5a+8kBgAOi0IFAABHZPL0I+tWVp7+shQ3
agG9xs1bwVEBQLOhUAEAwBHllP0ihJC2KDYIsTl/08e/vtOEPJ8/8D/h3uz0BcD5sEYFAADHcllb
JP33hq5s3hc7gz07V+hF6e2yRiUZEzhqZ+GehwLiYgIHTuz+x88u77fNYAHAVihUAABwLFKhIoTY
+P3xrdfWN+peT7WXSojy6vLEwRN3/ntPQNsuQoh5Ax++euum8gMFAFti6hcAAA7q5cyXGntLD6/u
/xM1y9/dP8o/wlPtJb3Zwd376btjlR4dANgWT1QAAHAs+mpD0278n8hZscGDenQI/DL7uBBiQPs+
8qUo/whlBgcAzYVCBQAAB1Ksrcov1jXt3hcHPiEFT0TECCFGdBl4Xde4lS0A4DgoVAAAcCCzvnv7
UPHhJtwoT/QSQvyl90ghxKiQyEs3CxUbGQA0LwoVAAAcyJmyM3m67CbcGOZlugfxiJBeIleJMQGA
PbCYHgAAp9elTefnB46p/f6IkF7NPxgAUARPVAAAcAg3b1WV364pqrzShHsXD3r6rxEPKj4kALAj
ChUAAP4/e3ce39R15g38udZqa/WCLRsbDHiBsJktbGEJaSAlG2knJOn0nSwkTTvtJIH0M+00G+mk
k3SakGbpDknaTptA2gYKTQiUNcVmsbGNbbBkY0uWLcnapSvpLrrSff849kXIC7YhDSTP9498rq7O
XSRMuD+f85xzVdhSv+vdjo+98VEHlSenP/jo9Ns+jVtCCKHPEAYVhBBC6LPkCPAOPx/hks1uh4Vp
Hu3hOrn25aWPfBo3hhBCny0MKgghhNBn6fWGv37QvW8MEQUAHpzy1bduevKK3xJCCF0NsJgeIYQQ
+mfghcGXcTzirR5bSgGAZxbcdxl3hBBCVzUMKgghhNAVMFQOkd7t8Aekl6IIIoCPFvbU+QPsGNdk
zJJpSvWFYzsWIYSufhhUEEIIoSvAS8eHebfV7W8OtAGACNDj54630X+r8/+67tjtdbeZR9md8ty8
DQuyZwNAuWby5dwwQghd5bBGBSGEEBo1mknoMmWpe+ocXUXZZUO1/9BaW5ZrBICHPni3OnKIjPXK
ytAM1X4oT0x7YPO8DauLli3d/cDi/DkgAlCjv3uEELoWYI8KQgghNGofd9Wm7akLNvpoYaj2/3DV
+2nBEeDf8bwhVaTEktFRXVSn0D5edTsALCmsyFPkf3nCPIrCmIIQ+tzCoIIQQgiNWo3TnLbHwbg7
A0EAaPC1pb3FC+Ih/4G3O/9890c/HPMVp2gmN371nVJdX1HK/OzZyydMG/PZEELo6odBBSGEEBq1
jpBz4M7jzlZRFNu9/sO2c6n7W93+WDIaEaLVkYNjvuL1ObOklAIAr6941KjUjvlsCCF09cOgghBC
CI1ae6xj4DRfx9wNQEGN0/zciT+KcOHdD621ANAR7bicK+ZrDKkvy7OLLudsCCF09cOgghBCCI2a
KIpH7OfSdp4ONAJQtBA9GjyQur+6tx5GX5GS5oaCKqxIQQh9oWBQQQghhEYtzEePOc6J4oVuEz4u
dvNWX/8kxS2ebumthlDTGC5xW+HNdxWvLlSbZuhmAsD8ogmXd8sIIXSNwaCCUJ/UBw6EEBqene+0
hntTpwa2x5yxZPQf3a1+WgCArU2HzI5YXUd0T5PTzneO4RLz8yv/snbzH7/0dI5KBwCpBSoIIfRF
gOuoIIQQQhcMXCBlKHuc+3jhmyp5X1hx824AOGI/ezhwAAD+z/qXUy6LN+FmEmMc8XXHlPkAsLJo
7lTDSXvMNbaTIITQtQt7VBBCCKEL/tZZCwA0kximTavbDwA+wb2rNX1R+T87/uoT3OTd6shBC9M8
tu4UjVxTlVdOtq/LKZqgKRjDSRBC6JqGQQUhhBC64JTbDABmT2CYNh9a68jGz86+n/bW2GJJqrnG
WQBwfc5saU+5sWiaofwyT4sQQtccDCoIIYTQBT4mUu+y/727bpg2f2k/QjZqw8dJ78rll7jNz55F
NublzNbINDcVz5NOunbS/MpsLFBBCH3hYFBBCCGELjBH2pvd3f9w1Q/VoNXtr44eItuxZPSdloM9
fu531bYQF7mc626afS/ZUMmpKZopt06anzoZ8dLxuAg9QugLB4vpEUIIoQsiQvRDW92ZcBMviEo5
xQlJlfyiX+rtbD+VOkngB937znp7dge2X+Z176tY+UR1vpt3LzdVtQTbq3IvGuu1IL/iMs+PEELX
HOxRQQghhPr8yXwCAPZ79tv5zg5/AACe/Pv7XDwJACKACBBmhLTOFgvTfPkphayUYlKbAICiqPn5
lZd5QoQQ+hzAHhWEEEIIAMBHC/vspwHAJ3gA4GjXuan5hG2jRAAAIABJREFUS3/W9RocgB9cv25L
9TE738kkIsfp41fkci8vfOxYT+sH3fsAoFRrAoAJmoIzYZiSm52nm3dFLoEQQtc0DCoIIYS+uI45
zEuL+rovTnstTYE26a1DzvoHhCUA8Hb31i7adfndJqk0Ms2Ts++dqD5BgsqcvAoAKNYUAkBVXjmV
upAkQgh9UeHQL4QQQp9bvDDcdFw0k/j5mb9KL0M8fSbUJJWfnA401rvsABBLRq9gSpmUNRkAbjIt
BYD5RROW5S0GgEWmSgAwafRX6ioIIfQ5gEEFIYTQ55aXjg/z7nGXudrTmLonlox2xjrItoVtafF0
X/Fb0sg0AHBv+UoAKNUVTtWXAcDaSfMBYE5uOYkxCCGEAIMKQgihzzEfLQzzboinbWznaWdX6s5Y
MiptH3IMOUnxmMkyMgDgvoqV0p58ZT7ZmJBtJDEGIYQQYFBBCCH0OUazCfFSazG+1dy3KEo4lkh7
66S/cUDzMSpQ9aWRx6bffWP+ktS3KvVTyEZVbrlShtUpCCHUB4MKQgihzy0fLVyyLn23Y583HP/V
310ftNemvWVhmq/Undwxfs03K+/OV+bPzC/+95m3p741O+fCkil3TFx+BVa5RwihzwWc9QshhNDn
lo+OD5VTRACybmMX1/nTU/t/1PHCFb96lkwjisAko9MMZQDw4uJHbjItWZBfkbZ6483FFyYjnpNb
nrogPUIIfZFhUEEIIfT55KMFXhDJAvOp+x0B3hmIv3v2hJ3vJFnll7Zffxo3UKGdLCQBAJ6cc8dZ
r8Oo1P5L5cKBzWYVFEvbE7KNn8adIITQtQiDCkIIoWtPhz84OecSz/SckAQALx0vylYCgCiKpLNi
z/lTv7V8VB05KLX0Ce5P4yZvKJhz2FkPAA9U3GotdA7axqTRl+oKpZdVueWDNkMIoS8grFFBCCF0
7TnpMo+wpTfcN/HX2w01vCDWno8cdjWkppRPA1kd5ebieRkUlaPWAUBqGklFVlBBCCE0EPaoIIQQ
uvbUOrruue76kazgTrN9QeWE/4zrH/HjngYz2/Ip3ZVGpokmogDwlUnLP/HWLJ8wraqj7OvTbhzm
ELKCCkIIoYGwRwUhhNC156D72MCdxxxmAKCZi2YZ9kf6XvK8uKXj1d2B7Zc5l1eZdjIALMybPfCt
9aW3AMDqohuKs0wFqgKjUvuNGbffXDJvYEuEEEKXhEEFIYTQNYYXxPrIybSdNJP42FYriiLNJlLX
eYz05xY747z8WpRnZn77lqIbAOAbFXffVnhz2rvfmnl7uXbKjxc/UqgzVuqmAMDSIhzZhRBCY4RB
BSGE0DWm3mUfuJNmE+aAAyhoCbY7Ajz0RxSaTfT4uV//vdceGbycfVRm5ZStKJxDUdTcwpJvzbg9
dSrhLJlmQX7FLRPnV+WWLy2qnI1l8QghdHkwqCCEELoG+GjBEeDPOHwA0OLpHtig2l1/LnwegLIH
g++1HRYBaDYRS0YBxF+eqn604y7LZZSmXGcsIxtKWcb8ogkgQlVu+dpJ8/MV+VKbOYaZAPD60sfJ
y9TVURBCCI0BBhWEEELXgFpH16ley4fWWgCo9jRK+3uj4b+2nxJFkeGS5yPnLY6YkBBPeBqsHs4Z
iO/xv/eK89nfOreO6loDl1w8tu7nZGP5hGmlukKtXEtePj9/g9RmZs5FyzguK5k6qosihBBKg0EF
IYTQNWC/va495Pio+x8AYKWdAEAKUX5z5sAea21b0Olm6Fgy+vum4+bI+YbYyQPnnCd6zQfCeyxM
s53vHNW1tix6bFLWZADQKbQAMClrslGprTLMvLv0FqNSCwD3TVhHWj464zZSWw8AX5960exepCVC
CKExw6CCEELo6hWO9ZXCH/c2munzLZEmmkn0xHoB4LTHIgK827HXRYf+u+YDM30eAH7Z87ozQvsE
97uOP+zwvTWGK95WePMTM+/RyDQAsGXRY1kyDdmek1fx9clfJm3mmkqk9usn3AIAWTIN1s0jhNCV
hUEFIYTQ1evDZqcIQDOJ1lgzAPgEd21PVxfXAQAhnj7c3nk22tTJdn7k2k9mJfYJ7jp/AwAcDP9t
VNMQa+UaMotXYaZJ2vPwtNvmGGbOzS0HgJtL5s0qKCZvPTrjNunAhabKccp8UqCCEELoCsKgghBC
6Or1XOvzAGJtT5dPcPNxEQBea9wdS0YBACj4TeuHAJBIiD7BfcxXQw4ZW9H8xln3Li2okl5mUNQT
M+8BgBWmuSuK5gLA4sLKQVeXv6NsQYV28qrxWDqPEEJXGAYVhBBCVy8L2+KjE2QlRz8bBoD9gd3k
reOWyD73fgCghSgAjLYQJc2mWfcsNk0DAJNGDwAqOWyYeisArJ28QK/QAMCgKYWYlVv5/KKvXc7V
EUIIDYRBBSGE0FWKF0QA2NXUdsxdDwCkCqWvOwXgt543yQKO3ZcXUQBgjnGWUaldMWEqAMzKKQOA
r1XeSJLJ0qLKsryc4Q/fWHX7wInCEEIIXSb5Z30DCCGE0OBa3X4A2Gb7v27OCgPGdF3OMvM6uYb0
wxAvLHiYbEzX9pWaPFB5q/Ru1aWWbizPLhrznSCEEBoK9qgghBC6uvhogfSl/LX9FAA0Rk9e5rCu
gV5d8P2VRXPJ9gzdzLWT5pPt4qyCLKUMcHJhhBC6CmBQQQghdHVpDzlqOyIiwH7XMUgZ63UF6RWa
D1a/NHD/dGOZFFoQQgh9tjCoIIQQurpY/D2/PrvHF463RJquyAlNqgKygKOEoiijUrsgZxYAyFKq
SxYX4looCCF0tcCgghBC6LP3ruUw2bA4GIZP7vFv/2nNJ5dThZLqgcq1ZNFGAJhuLAOAKbnZALCk
aOoM3czr8y7MSnzHlOuvyBURQghdPgwqCCGErjyrh7tkG1KIQuxsO0U23mo+aPYEfIL7lz2vX/5t
PFz2VZOq4Htz75P2/N9Nz2jkmqq8cgDYPP9hRcZFs3Up5Th5F0IIXS1w1i+EEEJXntXNlo5TDd+m
1e1XQ1Z5oZqiqIO91S2e7mx5/ie+GhFEuLxJvSRrxt/w7dl3kMr4hXmzbbSrKrd8tWkpiAAUGJXa
BXlVStnlXwchhNCVhz0qCCGErrzfd/75km3+0nn4aHvv7+obeUH0Ce7fnTv0SZvbzDTX0IfGfF2t
XLO0YI70Mk+nIJMLZ1DUveUr/7VsLQCsnjBPWvYkS5GxonDOoKdCCCH02cIeFYQQQlfe6dAl6uB5
QWz1Od/yP1VlmOkIh0QQd9k+qVPYR9WRopFpookoRVGi2DeK7ImZ9zw5+97sd1aTl9IcxOP1+nWl
y8n2vRU3SmdYWjB75JdDCCH0z4Q9KgghhEYhtbBkKD5a6Oatw7f/2Hx+t3uXne/sYDpf6XgVAMxM
84HwnpHfyVzjrHLtZAD4y80vlmoLN133gE6h3TT7nkGXQPnGdbeV6grJYvOpDYwaRRaO/UIIoasS
9qgghBACXhBHWEfuCPADi0+6w6FivUF62RkI+gQ3OafZweTq5EXZyrTL/bjpHbJASoiPjK0cZV7O
bC4ZNWoUd05ctq50+V/bT8UpxqjoCyEFqvxe7sJppe6UNF8qnjuGSyOEEPonwB4VhBBC4KXjqS9p
JjFUS2sgKI2zkpAl5CUnXGZRFL10nBPEP5gPtQTbyX6pd6W6w30sfJBsd4941XkyxXBW/0TDWcqM
SbnZz819iBSczCoo3jRrvVR88mDlrTN0M0d4ZoQQQlchDCoIIfRFRzOJcDySuuesr2eoxjutR4C6
0Pfio4XucOjjrrrUNsd6GwCg2l2//5xrr3t/iKdJy+oOt9kRMztib7bsGMN9lmkmA8CawqXk5czs
sgcq1kpVKNLILmJ92Ypc9SBjwBBCCF0rcOgXQgh9Tox8+BYAWBxMRVEm2abZRHVPa+W4xaQ7whHg
Lf6e68eXUCmBhGYSukwZAJwNtjv83PgcFQD4aIETkn9uP9nBdKSe3Ey3AYArGH/3/M8aoyf99N0A
8NNT+1ycuzcSAoADoVHUopCKeQAo0ZiMKu0DFbfu7NkvimKh1pCaTFLNz55VlVe+uHDqyK+CEELo
aoNBBSGEPie8dDytFGQgKcw0eXsqisrITrOvJ8Bf6FGxR13naUfagRYnM3eS9nRnpDXWEo5HxoMK
ADoDwbZAz2HH6dSWNJPoYm0AsLPzaHXkIACYI+ebuua879glJpMWtmVUH+rfym+NJ5LvdnwEAIWZ
pg1l05cXTQMRAGBabtFQR904fh6I8OKiR0Z1LYQQQlcVHPqFEEKfEyOZj8sR4MnGn217pZ1tQYeZ
Pi+9PNPbbY/2AgUA4KMFsvPllndoNvFJu9vOdzYH2sjOEy5zo7/tdPAMAEiFK52BoC/hBgBpCi93
jH7m1FZzrGm0KWVl0dzf3vjUH7/0zDhlPgCM1xnWlS43KrUmVQEAlOoH704BgLWl81K7gxBCCF2L
MKgghAYxkkdeSHnqRVcDi4O55B+bxRMAgKauWHvsQjI57W1juCT0P9i3hNo90XCQj0LKH/HpQKPV
w1qYZgAIx/pK7Y+56097LF1cZyIhPl/9gSPAOQLcQdu5tGr7I+7qXb73Rvtx8pX5h257k2yvHLcE
AKYbp5CXj1T8i0mVP8yxUuEKQgihaxcGFYTQILx0fPisQjOJYSaGuiQfLaQefjmnuuL+yelrhJlw
JGoDjZe81lHXaauHc0bCIe7CWK9QPELq3Ql3NNzBdPyxqcYbjp/2WkRRtHo4C9vS3BUjnSQxPkla
msPt+4N7AMDGdv7k3C9u3PMfTx3+4P3OvRdfFuwjntcrVb6qQNp+fM6dVYaZ+sy+BU8WmirumfRl
uGLfHEIIoasRBhWEvugGPpfTTCLCJNLmq03FC6IzwNNsAoZ4zh5+1A0viJyQ9EWEC1dkLxFUruDT
/CVd8lpX9maG/55HdaruUGj4yOcI8EfcNY4Af9DaIi3ICACnA42d7IUs0UQ3hfnoHzo+MnsCe3v+
ARTs6TgFAJ/4qkmPyu6uT3hBNPfEujgbOSSWjMaSUQvT/I7ndVKXMlrjs0xkQyvvm6ordc6upUWV
BqV2QUElebl20vwqUzEO7kIIoc83DCoIfdENfBqm2QTNJny0INUnpDbjBdFLx70RwRngfbSQ9pxN
Yg/NJEj7gc/N5BBngPf1HygdMsxNDpqmRvb5Rq25KzZ8gyvb5WLzckO9NUyGGVR15CDNCsM0qHPa
T0eOt3sDewO7yWKLBJOMxVN+DOJC0s530kL0+bqtbr4XAD7pbQCA33n6BmIdCx86bOk9YO71xcey
UOOgdt/y0gxjOQDcW7qGrDdfoStLbXB9wdTUFeUfqLj1Sl0aIYTQ1QmDCkJfdL4Bo7ycJDmwCU5I
Sjulp3MyKozEGF5IOgN86uFtTi5DrrI4GQ8dB4Dm7ph4cRayuBhyfkcg3n8DAgBYPUM+r/towTfg
kf2SnTCjJX3AgREobY8zyA9Y8HAUUuMfAPjCQ0YL8iUPH8mk75ZmEkwiyseHu7NDjrpYMnrQfcwf
90h34gjwdr4zlohK57FwZwGAjyf3B/f0xHp5Qazx1wCAlG1iyegbLTv+4NomXvboK7KG4/8rW1uV
W777yy8BwA8W3Ldh6q35yvws5UX/QmF9PEIIfdFgUEHoiy7Cimm/uecEkRPEtOdpR4AXAWgm4Qzw
TV0xHx0nUcERiJPD+ztGBIW+EABOd0R5QfSFhbReF2eAp5kkAESYhKM/Eflowerh0p55pQf0QTOJ
80pXkkifd+DlLE4m/dLU2AeAWT2stE2+1aH4IwlOSEpXT+3Ukv7b1NUfMNiEhW1pctsHnoe05OLi
P3w1ANAQPUGKRtpDDgDoCDsBwM53kj8XsydAjiIzdMUS0bou78Aikz2B98Y2xEtSoMoHgLUly6bq
p/xu1dMURZXqCh8p/5dSbeE95SuLs0w3FFSltsf6eIQQ+qLBoILQteHTq/Amg4VSH7v9tJDWieGj
BWeAd/h5q4dzBOKkF4U82UuBwRngyWO3UpsniqKPjjsCPFCUw39RV4k3LJBk0p9zeNIz46Pjab8t
J0UsNJMgd5J6h7wgkqfqyyF9pbwgOgK8zcuRD0Vd/G37aMERiKfu8YYFCsDqZtPPOAK8IPojgnR1
XhCbvd2DtrQ4GC/NOwO8xcECgNXDkbznowWzg5HOsLPtFGkfYRIA4GIHGYvV2hMDgP1nAm1MCwA0
Rk+S/faoUxThnLdvEfp9Z511HZFfNuxPnbPLznf+vqlmDJ9UopVrKYpaWTR3Sf5FweP7sx4EgB8v
evjhaRcGcf1g/n0ksSzJr8pSyi7nugghhK51GFQQ+iyNvNBC+n2/xcEM33L4wwdy+HlIKYdwBHia
EUiRiTcsWD2cjxZInIgnRKuHS+3KqOvo+3W+NyyQMOOj4wp9kY8WeEH00XFRFF3BuHQD5p4YRYEz
wEsDvSwOlvSxSDmkqSsmin3DvUQAi5Px0QIniFLXAbnbyx/6JX0Q8ulEEXr8vNXDkuFM0v1wQtKV
8pHJfkeANzvZMXSpeOk4Gxd9tBBhElxc9NFxM9M8sJmPFrwRwUfHSaKjmYTVzXW6WUeA7/FzzV0x
Hy1YHIyPFmoCNSSx7O04CwCWYPpCjTSTON4WqbaET/SaU+tSACAcS9S00Y3+vkVRtlh+sbO16V33
W2ln+GXvj0f/QS/YPO+hLYseO3Tbm8fW/XyWfhYALMybXa4rK84ylWmnlOoLvzp5hdRYWml+iqFw
yXhcVx4hhL7QcGV6hNI5Avwll/e+fDST0GXKnAEeQKnLvPRvji1OZsaELArAGxHKRRjVWH3SY5Cr
G+TvuzSIyBHgC41KkiJoNgFAAQAvJOs6GJNRQcJGZy831ICrmjbaR8e9tMALospQZPPyAFDXEdWp
ZT4hWTpOZQmwcydratoiqdUdESZBxkH5IvGU74SbOE5l9bCOQNzk5y0OVqmgOEEEgLnQt9RH5DIq
6es6IvMmawHAR8dJHiN5wBngC7MVNg8HQEWYRIRJVBRlAoAzwIsgOvt/Krx0nAIgvUDDX0haAz71
JS+IflogA+ecQd7q4brZTpI0Un/qfHS8uSvmEzzgyQcAmk1YPSwviG1OlhfEWDL69nGXQDEKWUVD
7OTxTs/NalNXIAgAPUxv2m04A7yd76w+2+mLe9Lequ3yZuZyDb6+oFJDH+rmrGlh5nJo5Zo7Ji7f
NOseqbZkYd7sM+Ezz87ZcC7cDgBLx1WBeCGcpKoqKEktnUcIIfQFhD0qCKUjD8Gf9mIaVg/HxUWa
TZARU8M3Th2S5KMFGGVFsZeOD/VU3f/YHW/uilIXViLvuwDNJH204ArGSX+IzTv4YCeLgyUV+ZEB
vRw0m+AF0RsRLE7G5uHS6jpqO6JkDzl/mE0AgI9OkDjko+PR/vnHyEtpZiqa7RsPdqGwZATRhRdE
mklw/Sfx0QmaTTR1xRyBOOnhcQb6PmmTPSb12HCCKH0hjgAfYRJAQVNXjPyJDIpmEqmVOWTNmf6B
W3FOSHgjAs0kHQG+xt1g5zubu2Kp0YsMNgOAavoQiQ01Fpp8UYeDB3yC+0Bozx/c2/7q2VnTbfMJ
7t91/tnsjHkTbgAIcrR0ErJh9bB2vvO37jf2BNKXXLQwzTvdu+ojJ6Q9Y1vwJI00v/DmeRv+cNMz
qRXwq0vmAsDi8ZUbpt0GAOvLVgxVH48VKQghhDCoIJSOZhNcXLzitdqElElcAd4R4DlBlCa/gqEH
aHn7izScAd4Z4OP9D/fDDOhKNUwz8tidGk5SUxNJJtLhQ5WPW5zM8JXlNjcHg037O0iwYRIRNmFx
slYPxwui2clK98kLoqf/0d/fN7RM6OuQ6a94GZ4jwEuxh1wowiT80QvVOCkbgiPQN39W/9RYcauH
szhYRyAuin2RLDVlAYDVw5G85AzwbDwhjYtrssd8EYH8REXYpJ23nrR6Gv1tzgDvTbiZZMzq4VLv
/7iFJo0tTFM310kuYec7D4R27/Fvb4ie2BN4ryF6opuzHgzuBoBz0aa6jmgNfQgAOmId5Kt753QD
maKgztl9MLhn0C/kQHjPDu+2K9WF8rUpXwYAjVzz33O+DQC3FN/w5Ox709osL7muQJVvVGqNSu3E
7Oy1k+ZfkUsjhBD6XMKhXwil80cEXyTuCMSlgUYDkUFKIz+n1N7q4cgIq54AL5dlRLhEhEmUF6mh
/2mbDNCyOBgy7og43kYDgCPAk1TjoePjs5VWD1s42BC1gfdGswnyC3sfLaQNAKPZhCiKUjip64ik
1ayP/DMO9/HZBAwxeVcqihTQUxcV6KeeQcIlREiZPmvg0KlB+eg4zST7umIiAlBQ2xFNDUupnzfC
JCgAMSW9kJoQAPAJnlx5PvT/QTR1xVZcp3cGeUeAJ2O9vBHB6klInSTNXTGVnPLRQo+fPx9y2vlO
JhHl+VimutgX95BODFLVU22hnX5e+rBt7Fkz21KeOZ0C6kBoN4kiO3x9NSR2vpMca2Fb7HwnWYqx
m7ceOOeaZsr5te1XWRkbMxN573jeuCL9JACgV2rDfGTQt6oMM390/cONvvap+snryq7/nWXWh2sH
qWzJz9I9WrkeRAAKFuRXXJG7Qggh9HmFPSoIpaPZBHk8lVIK3T+RriR1VfW0GaISweDAczbZYyKA
jxa63BxFQY+fiwtim4uhmQTNJkgPidnJkKoJUQSpULuuI9IT4MlSG9VmOrWfxxGIc3Ex7cZIr0va
Kh+kGL3TzUnrokgV+aQvRSoQJ50AcoHL4ujcUHpZ9qetxkJb3dwwS5TEBZF0WZAJAJq6YmTur5FU
jACANF+ZKEJzV1QUB+nSkZCOtb/VBXhB9AluMgEAWQrTzDYDQCwZpQB4QbR6WIqC5q6Yzc15w0Jd
R5QshUnyBhlUVtcR9dHC0bPhzrDDwjSb2ZZOptMruC1MEwDY+Y6mQPuZrqjFwZCjLExzdeSgCKJP
6D0Y2hNNRkhKGcovXX2pIJaM7uzd1dwV8wne33f/4SPfXy2DFesPTyvXDLp/1+qXTKp86WW+8sL2
JF1hqa7w/256euuqJ0t1hf859z5qiJi/ce4duBwKQgihkcCgglA6b1hwBXheEHuG+HU+Kb+G/jE/
zV0xsb9Gwuxk4oGA1LK/uELw0YKfFpq6YmE2QWZhIk/jkb6qjLi5J0ZCSF1H9HRnhIzv4gWxqSvW
bIumNob+fh4yxZY0d60oAi+ITV1Rq4dzBi+OVX3rnHDSXXkjAmmfmnNqLH3lDYaoL5MdUVDJ6q+I
GLlhDvHRQtqKJWl6AnyTPUYzCfIN8IJI/mic/X1Nw+ufJwCOnA2PpP27xzxkMcS09ddrwgcBRAvT
TOqLeEG0OBgSY5wBzuphU1PKkZYwkFVK2ATNJhrCTd2c1cI02fmOxuiJbt4KAO+432wKtp3uuDAE
qyF6Yo9/OwB0c9Y9ge0/6n5y+Fv1CRfu8GBodzQZ8QvuGvrQnsD2S37Mgf57wcN3Fa+WXi7Mmw0A
/1q2dkXhnAcqbwWANflf+uqENTcVLJHazM6tAICq3HJSAX9v+Yr0k/bDEnmEEEIjhEEFoYvQTEIf
9ZodF1WNk8oQ6E8jpLbE6uE4IUnKpiNMosZCWz2czc3FbV2c1Uoa11hosb+r5IytL4qcscfSikZY
Qaxpi/hoIRxLWj1sU1cMAJq6ok1dUV4QyQxaaffTv7pi0uJkmrpiTV0xm5erNtOkRDu1MS+IvCBG
mESXhyedLX2F4BQ0dUV5ISkXOACQC5x0V4aoVyFw+qh3+KwiF7jiXvNov2GTb+zDkNocjI8WwsxF
315PgI+wCX5AZxFB5vWCiwt1ho9D0kApcqCd7/x7eHfquxb2rFdwV0cOskLfQDKpHMXm5YP9g6Ms
THNdR4QT+npISM+GT+i1853dvNUf99T018p3853dbCeA+Ivel3b43jIzTTWRQyR72PnOWDKamkMu
KZaMPt31TTLJslR/Mju3fPPs7wx1yPLCuTq5ZoK2EAAMSt39FWv/snYz6RLRyDXfnX2vVq5984Yn
KIp6dPptZdrJLy565NHKu79UcqHCZHlx5cjvECGEEBoJrFFBqA/NJCJcEgAK/VazJo/sFEWgKOAE
USWnoH8YDy8kyVPvxDylxcnQbMIXEXy0YHVzNJsQMpKyYFAUxSNnQ2QaYYuD4QXR5mXJg2/bxU/S
WRzd5ugbfNXmuvCWxcFygw1n0ke9ophFMg9pX9cRUckz6joi0rO4M2WGZVKIL3UK8QnR6mFzdQqa
SZzuiAJQeSGH11A02dFkmTBfuoRc4PVRX+p15QInyFWpe0x+6yi/YwCAnJCjo2hWFkfHVLrRHkv6
sqT+KABwBvj9jXGxv8aDiydPd0QrijJFgOauWK5OTr6owmzl8BMP+AR3rjzfwjRXZM6oCR8sydsg
vdXNdjZGT5IGB0K7c+X5AOKewPZuztrcFSNP8zSbsPOdufL8rAxNDX2wInMGAPw9vLsic0Z15NAS
7SrSLVOROYN0zsSS0djFdSN2vrM+eqIhegIADoR2w+VJq4+vyqt4e8VT7V5/6s6XFz5W77L/wfaB
Vq797cqn3rF8uK50+f/UvfurFRuzVToAKFDlu7jeRyvu/urk5XUeC+kJKdUV3lQ0t6qgOMImF8gm
PFxNkURUNQ4LThBCCF1hGFQQ6mP1cPosuY+O5wR7oGQeABUXxDYnU1GU6acFpZyyejheSFo9nFKe
AQA2N6eUU2QmqxozTbMJ2skAAO3yR5iEbGLcGYibspXW/jl5pUJtsmHydbpyJ5GNLlklpGWA/ncH
MvmsEbbYFxGyOFoucGFNHi+IvJCAi6cONjsYX0TI08rJbLyTHWc6imZxgmhzs/GE6Azwe+oC5IZy
Q464XKWPeqVjM1k6LlOljdEy+a3d+ZVygVMm+OJesyBX5oQcjEqXxdGZLA0APkMRAOij3rAmDwCG
iiImv1Uf9Zb0mlsmLyV7pA8yzJ9OLBnNytBA/0xcmbQkAAAgAElEQVTNdr6zRDkp9fsEgGozDQBh
NkEGYjkCvEqeoc2UkRp6qfJ+4DkboieyMjS58vy+nBDesz5vAwBURw6SjAEAdq4zV55vZpvJaiSN
0ZOxZDSWjGoytCQV7A68V6VZWKKctCewfXHcHROj3ZzVznc2RE8wiaiFafEJ7sX6VRb27KAf0MK2
WNiWYb6BMZuZXXbotjeNSq0jXJu6f964iidn35v8SCzUGUt1hZvnbQCAHauflRqMzzS5uN7F42ZT
FPW9ufdJ+78583aKonSZMgDtv5V+pTFgaYt24IAuhBBCVxwO/UIIACC3oKS5K+YNx52BeCYXyQ05
oX/18XAs4aXjnCBa3ZwjEJfWX6fZRJujr5MktYgl1Ouj2zv3NQbFvgUTL5olqdjdN1bK5O/7hXpO
yGG4uO8ii6PTejMuutVQT4c95KOFnJBDIfBk4Faapq7YkbNhZ4A/fDZscTKkhwQAbG6uriNKqtWl
e84NOw1RbxYXAQByttywc5KzCQCkoV+5IcdkRxP5LxnuVepoIpGjousUAExynJELnD7qnX/uYwDQ
R72kmXQGEnvIuK/JjjNkXBlJRyZfp0IYbjJosnJI6h5pkqtUFidD0sjhs2GSD8kyNbwgDjqBcg19
kGw0xE40RE/Y+U4L27I78B4AkJP/zv1mLBklZSQ1kUMA0M6c7eY7ob/LopvrBBAPhPY0xE50c9Y9
/u1ktt+G2Mka+pBPcO/wbmuMntwT2E7Gbr3QvQlg7BOpTTeWkSVKjBcnwIla08qiuRM0JgBIq1PX
K7S/vfFpkiKyVBkTtSYAKFTnA8CKojkAMCN/wjPXf23Qyy0rnAMAZXk5cHFhSVVuubR9e+myWdnl
ldopY/5QCCGE0FAwqCAEvCBu/N8/RbikKxh3BHjySJ0bclgcDC8kT3fGyIgji5PxeGjpEBhivl1F
Ip4R5/khljqZ7GgiGya/TR/1ygVu4AAqk68zN9STtpM88csFLjfsJMHG5OtUCNwE9yBVIqlVGT5a
yAs5srgwACRCQXLPUrwh6aK416yPerM4erKjKbVrRbr0JMeZEGvPDTkmO5smO5smei3kW8rkIsVu
S3nAoo/6JjuaxgesZLqwBef2Vthrszh6emd1bqinoqt2VtshAJF8CpPfBgAl7laST3JCjkyOJr0Z
A+mjXvJW6nCmbrbTPFj/w8jnU7bznVL4ORM91RA7eSC0m2QVAPAm3B18swjiDl/fMiMN0RM7vNui
yYti557gjnc8bxwM7SaxxCe4yeFSSQl5OeaFSsiS7VIseXjardcZpgBAx31/em7eBgAoyiwAgMO3
/+zQbW++tvSJ5+Zt+MvNL1blVVAURd56sHKtlCtWFs1dV7p8UV7VrcXLlpnmkMT0g3n3DtUZUmYs
hItjyUCzxhUvLqqcm1d+GfkLIYQQGhwO/bqWxOPxI0eOHDhw4OTJk11dXT6fr7S0dMqUKatWrbr5
5pvLysqu1IVsNtv+/fv//ve/nz9/vrOz02g0lpSUzJ8/f9WqVatWrVKpVJc+BQAA1NfX79+//5NP
PrHZbF1dXePHj58wYcKyZctWrVq1cOHCS05ReuzYsXfffffIkSN2u338+PHLli279957V6wYcinr
Mas207mmEgBwBHjyJG2IevVRb7Mm1yeoyOM+L4hkjBMZ4DQoUsXR/6AvDlyFpdht1ke9AKLJZ5UL
nELglrQdBoBMjq7oqu0uqMwJObrzK4vdlrhMkXpgbshRbq/1GW7PS6luzws7w5q8yc6mjqJZ0s6K
rtrUUpOYSifIVTkhh0LgTL7OuFwVU+nkAjfBbSZHkRPqY33JBwCy2ItGfGUBP72zWh/1vqJzPOZs
kirvwxmCPikncSWvpxUApriaFDIqCTDl/NFMLgIAi2xHM6Pe2W2HM9RqdcizQulSBm3kcCPj35ds
uFkzKR715oadDo1uf/T3VZOul740MkWyQuANUW9N8pAGVFkZWTcZbgeA3YHtdr4zUzb4FLojYWGa
dwfeI9HCznVGk5FoMlJDXyhYb4ye9IsFAJA6KfCBcPqyiVKvzhimAB6Ioqip+innQu0AsCBn1in/
mVcXP97ga1tXuvyuj79vjTjvr1xb723PVGYYFdrN8zY8X7ft9pJlLr6X5Jl1pcvXlS4HgFJdYYPP
ctbr+Enz24/PWJ/69+WByltnZJdN1BYecxsv+fdoeu74S7Ypzy6KJqOhIRZXQQghhC4HBpVrRn19
/aZNmw4fPpy6MxAI1NfX/+lPf1IoFN/73ve+973vabWXNVKcZdnXX3/9+eefj8UuLCLu8/nOnz9/
+PDhl19+ecGCBa+++urSpUuHP4/L5XrmmWe2bt2aujMUCp09e3bv3r0AcO+997744oulpaWDHi4I
wlNPPfW///u/acf+6le/+s53vvPKK68olZdY2m/kHAG+rX8OqCyOziQdBSxd7LbY86dKsUQf9eqj
vqz+oEJKPlLPU9FV6zMUKfp7KvRRX1iTJxWgF7st3fkVJAkoBK7CXgcA5fY6kmryQj3FbksWF46p
9GRAVEylkwusIFeTa+X7rXkhR27ISXJUJkfnhhxygSt2m1OHfmVxdG6oB6AvqCgEvrK3tmXy0ryw
M6bSFbvNpO5lsqMpN9RD7j91Xq9SR1NYk6tIOeEEr2Wiz6KKhQHgY1Xv3bGiCZAZzhBCVLxG5V8f
Gw8AdhlTksgEAFmcS8YBADyCPR90oQyB8nV+rPavYYHiaADQHdpFTtusoCckhNezzA8mg2dsH32g
dH6Yca5d6BUBKBB9gqcADPO7axIKlY/SZNAt3YrOcbLcHb63Vhluo4CqoQ8yyWhmhkZKg1K1yfB8
grshemJt4c3VnoOkr+M83/xJeJD1SRqiJxquzHLtFyHP/eJgK8X8+7T1c/LK8jL1d+37frl28jen
rj9VfWZF0RySPTYv2OCiQ0aFdrKhcJLeRM6zIGfWvRUrB56qKre8Krd8p/LoA/FbSYZJfYv0nyhk
l077K4vmakeQBqtyy4McjUujIIQQuuIwqFwbjh8/fsstt4RCoaEaxOPxF1544ezZs7/73e80mjH+
pjkej3/7299+6623hmlz6tSpL33pS7t27Vq9evVQbXp7e2+//fba2tqhGgDAe++9V19f/9FHH02a
NEjJ+Msvv0xSik6nu//++ydNmmSz2d5++22apt98883c3NzNmzeP9FNdypGWMHlsnOw4AwCklqPE
Y0ltIxe4yY4zcoEnBd+5IUeBr9OVO4kUkcflSoXAV9hrG9Q3zuisJodksWGTz6qPemunralqO1zs
NvsNJjLKa17rvv580hcSit0W8l9X7qTJziYAyOLoGZ01DeUrs7hIhb2ur3Qk5CClI1ksTU4ljVLz
GYqK3ea8UI8h5of+vh2FwE1yNrlyS+UCpxc4UuYuF7jJzqZQVg4FoghUYczVoqCnx3XS2ZQRu/TB
1UxY2m5R0DUqf0ls/G80tjAVD2UIAHB3bPxGY/OffAukNrqk/BVd+6vBmRuy69ew+eEMQQT4Mnth
ZUAA2GRoupsZ3yVj/tq690HtyRJFpp1nACAQq4G8rKMde5+K3aBLRH7LHHmILvmtoVsEcCd8AGDn
OxUJGxlYFUtGpxjpo07ntIJJr5hf2lT4QwoolYI6ETw+R7sQAEQR+gtC+sLMdt+282wLp22roT8h
d7LD+xYtfAqJZAhbFj02OXPyIU/1T5suWt5kmWnOz5Y9AQCHHacB4N+n3f3QjFW/ODdLGpR1f/na
IB+hKGqFqUo6au2kBVV5FUMN3DIqtc/NfWhgfiDRJS3ADOVm0yV+JUFU5eGUXwghhK48atDf7X2q
yBWTyWQikeB5nmVZjuPGjx//T76Na4jH45k9e7bT6SQvb7zxxm984xvTpk3LzMx0u90HDx58+eWX
abpvuM5TTz31wgsvjO1CP/nJT/7zP/+TbKvV6u9+97urV6/Oz89nWdZsNm/btm3fvn3kXYPB0NTU
VFJSMvAkoijecccde/b0DZKZMmXKE088sXDhQqPRGAqFTp069cYbb5w7d468u2zZsgMHDigUFw1z
6u7uLi8vZ1m2sLDw4MGDU6dOJfstFstNN93U3d2tUCja2tomTpyYduna2tpQKHTTTTeN6lP/+u+9
ACAXuC/V/bGjcGZuqCc33PdVn520pKNollzgqtoOZXERfdTbnV/RPGlpVdshhcAxal1Yk0f6RniZ
MoujvYYiKXvEVLosjhbkqqAml+x05U4a7RIioZzxBn9fscqOrJ5b2AJ9Ug4ACYVKFr/Q79GdXylP
8PqIV5ng5QJnKZkvyJUhTV6Ju7XYbSF3Qlq6cie5ckqr2g4BgCBX+Y1F58N127McPw3OkM72G43t
4ejE40r/Yj6nRunXiwp9Ut4tY/4l99RqLv+RyMQN2fXhDKEkkRmi4hsjZc/rW8/13rRX3atPKmqU
fgDYqrFtiE7cprGVJDKvE3Q1Cv+53psAYK/avYTPCVLxxflH9Ul5OCN9vuCvaZc3yXu6Al3/G7ve
mfBt1reWJDLtsgtTNm8wrf6T63AI+irvDbJMvVyTq81u8LXdO+7BG3V3LJulmL7r9pNrdqkgq64j
MnNCFgD4aOEVyy9jycg/QgdH9f0P5f6KtR90HBUpMSLERv6/UJMq33n/TgAI8pHSP35lmmHKcU/j
EzPvCXD0AxVrVxbNJc2oXy9x/eveAo3+mMO8tCh9cZIGX5tUNGKlnSPMG2P23X/85uUbHvlUL4EQ
Qp9bogjJZCIcBorK0GopmQyunc7nnp4elUqlVquVSqVMJsvIyIAB87X8E2BQuQY8/fTTP/rRj8j2
E0888eMf/zht4NPZs2fXrFnT3d0NAAqForGxcdq0aaO9it1unz59Ogk848aN27dvX1VVVWoDQRCe
ffbZF198kbz85je/+Ytf/GLgefbs2XP77beT7ZUrV77//vt5eRdNOxsIBL72ta+RAWAA8Pvf//7r
X/96aoP33nvvvvvuA4Cf//zn3/rWt1LfeuuttzZs2DDoUQzDLF++vLa29jvf+c4bb7wxwk/tCPB/
qwuUOpsqu2rlAtedX5ETckqP9ZaS+ZYJ8xY175bih09fKFJUXsghyFWDTrcFAKR4YyRXr1H6F/M5
w7chA6v2qt07snpuYfOlrDK8pFKVwXOgUgOXPidv2g1sz3K8n9nzJ98CcictCnqjoWk1V3Bc6b+b
Kdqsa10czzkrp6fHdXvVbgBICxjk5bbAnE2GpuJEZjhDSM0Vkn3eJS2K8Bbt+Q3Rie9n9rQoRr2e
/QiV6gqttPO2kmXdMdevlv2AScRm55a/Zzn0reoXR34SCkAE0MuzMmSyYP8Pw9srn9pcu80WcS0a
N7t63c//2vWP6/RTjnnqHzryP9L/RSmK0is0IT6ybtLynZ1HAYCCvmVG7ixdVpVbQaYABoDNdduq
cssfPPyjwAMfp+WNW3Y++9G656kBBU6fidRchBBCaKQSiciJE8zZs/GeC1PjKMaPz7ruOs3ChSCT
fYa3NkJXSVDBWb+uduFw+PXXXyfb8+fPf+mllwaWZ1x33XW/+tWvyHY8Hn/vvffGcKH3339f6pb5
2c9+lpZSAEAulz///PMrV64kL3/5y1/29vYOPM+vf/1rsqFQKLZu3ZqWUgAgOzt769atOp1OOk9a
A5K4AGDgPcyZM4ds2O32tLdee+01MthMikkjtLB59/SOYyR1FLstUkoJZwg5Yceq2j+m1q/nhp15
/bNvSTu7Ln40f07XOuiFBv5KYHuWg3RBDNWgS8Y8Z2gVAfaq3Wfl9Bbt+WNKf2ozEaBLxpA9e9Vu
stGsoDN4DgCGTykA8Iru/PuZPeQQcuyOzJ4WBf2qtr1G6d9kaA5nCB+r3HYZQ1IKAKR1g5CXGw1N
oQyhRUEPmlIAYEN2/UZDs13GbNa3fnopBQCstBMA9tg/afC1Ldz54Mrd385+Z/VIUgrVX8VvyFBv
Dcy5TTvtu0zlq4v+g7y7PHvBAxW3knKR+eMqgYI7Jy4rzy56oOJWo1L3xMx7AGBF4ZyDt74xJ6/C
oNR+cPNLP138RKm20P/Ax0/MuKdMO/ntFU8/ULFWutwTM+9ZV7qcHJjWK/Kdivuvnhm0MKUghNBo
MefO9b7xRnj//tSUAgDxnp7Q/v29b7zBtA7+nIAGwqBytfvkk0+k/LBx48ahZty65ZZbFizoqxP4
wx/+IAjDLcI9qB07dpCNysrKdevWDdpGoVBs3LhRerl///60Bk6nc/fuvkW1H3nkkSlTBl9dYfz4
8d/+9rfJ9rFjx1ov/hvL830DewZODJCVlUU2GOaiB+KmpqZnn30WAB599NFhimcGKspW5oUdg771
irY9N+SQ5pkdSHqY3KI736ygf6OxNSvoLhnzflZPtdIvAogA4QyhWunvkjG/0dg26/s+Jnm475Ix
+1S91apA6nmqlf7tWT0iwEdqtwiwydh8Vk7vyOr5WNVrlzEkMGwyNJNcsVftflXbvsnY/HB2fbXS
v8nQ1KKg96rdD2fXiym5BQC2Z/W09EcRcgMiQLOCPt4fkz5WuzfrW/eq3Dsy06dFHomBg7jSDBVg
PhPSr4NKEpmbImXk5ZbQjC2hGfcmJr3vnnsLm/+rtgl3+3Oq6vp+Nr4lVNCHD68O6gFgiqGQPdea
CAbJW3+5+X9eXfx4tkr/zsqnVxbNrcotJ4Hk8ZnrD93+plGpfW7+hi+Nn2dUalMDCSkseW7eQwNv
77brpmBhOkIIXaNidXWBHTsSQxcVJ0KhwPbtsbq6f+ZdXbuwmP5qV11dLW0vX758qGYZGRl33XXX
qVOnAIDMKVxePopfhTocjhMn+laxuOuuu9KKRlItW7ZMoVDE43EAOHHiRNr4q9QC+jVr1gxzxZtv
vvmll14i2w0NDVIhCgBIYSwtjQBANBpNawMA8Xh848aN8Xh8/Pjxzz///DAXHSjucg26v0bp36qx
rWHza1SBTfSUGqV/CZ8DACLAWQXdoggXC5k1qsDdsaJwhvB+Zs91cd1xlX+Ltp202aI7rxdt18X1
ZxXhGoV/uqDvljF2GbMpUmaXMduybIvi2Zt1reEM4WNVb5iKr2HzAeBVbfvHKl2Lgn4/01HTXyIC
AJsMF6a+/VNmDwDsVfduipSRDEP2kx6PTYYmALDLmC3a9q0a2yPyiau5gulx3ava86vZ/IxMeCg6
MZwhbMuytSjCqT0bNUo/+cij+vauLCq18h1A118boxcVhqS8u7/jKLXxdEHfIg9TAIv4nOMX9zUN
pTiR+Xx46nP6VgMot/pmT0hkdsuYamXfDGbrL8x1B/qkXN/mLM7PLElkLrN4Y+7GuSxLZUNVbnno
/X365csBIKuqamXRXBDFV5c8JhWp3zlxGTlD3yooSu2Lix+5nOwRa2jIGtC7iBBC6GrDtLUF96RP
ZD+o4J49GXq9ejSPal9MGFSuds3NfQ+pU6ZMKS4uHqZl6kCp9vb2UQWVzs4LRd7S8KpBZWdnz5s3
7/jx4wBQN+D3Ae3t7dL29OnThzlP6rtSbT0hFSw1NjZef/31qW9J30ZR0YXFTLZt23bgwAEAePnl
lwsKCoa56KBkBoMQDJIH320am16Ur2ELXtGdB4AN2fXTBT3AlPW5pz72LilOZG7WtdrlTIs8XJLI
bFHQ5PkeAN7S2FI7DcjOj1Xu1JcAsD6vtlkWAoAd0BcwWhR0i4KWEgIJD6R96qiwNOEMQeqfSSVl
jy268wDwiu78K7rzpB59m8YGAHvV7ivbuUFRo65z04mKDKUyLMREUVws5NXIvUviuauZcQ9HJ67P
PdWsoJ8PVwLALWzBx+reHZmO930LgKQv3Xm7jKlR+q8T9D8MVe5Vu5+MlG00Nq1h89fHxm80Nn+k
dpckMs/Jw1pR8Uh04llFOEQJFECTgqYAaCpenMhcw+avYfP3qt3T47oJiUwAeDiaPitDqsV8zvS4
jgIgXShLFSXXuzOCoRB99GgiGMzIzFRXVvp37Lj/nnsAIO5yfb1gaa6uMMmyIsvKDAZSN6loaUtO
nZqRmUnOmQgEZNnZl/6mRBEoKhEMhvftw6CCEEJXP3rASJNhhPfvx6BySRhUrnakkwQAZs+ePXzL
1AkJOjo6RnWV1KAyYcKE4RtPnTqVBJXa2lqe51NrZiyWC7P6Dj9Bwrhx4wwGA5lwOW3o1w033EA6
bX74wx+uWLGioqJv5tOurq4f/vCHZHvZsr5fWnd0dHz/+98HgK985Sv33HPPJT7nAAqTSbNw4dZ/
vG3PYD5W9bYo6JJE5hbtefI0H84QapT+NXnVIsDqvOrUOvKWjAuJAkY8tImklH+y1HsbVUohC6JP
zMq3Rd2imASKCvERUq0utdmy6LH9DR/1ZImNvjZp51Qu36zyAAWiKN5ZuuyIoyHER0hNuVGlu1U3
/f++sqXB12Y5U/Mvi9c/9uHm55f9B/fzrcrS0vvYiCYaX8PkkKmF746Nny4YyDlLEpmvBmds1dia
FfQSLnsRn0Oq/7f5+3L1JnrKYj57MZezTWO7mxlPJlwmExu8ojtfklDfwhaEqDhZ8mUJn72Y65vG
YHpctz425CKet7D5hpTZC55wmYK7dkF/bvFv365ZuJBtbY01NsqNxsDOndrrr0/qcoO7dmXo9clw
OGvWLOWkSfS+fRRFZVVVxV0u3mqNHD067rHHKJUq7nIpCwuTDEMyTCIQSITDQjAIoigzGOijR7Nm
zaKPHk0yTGjvXkqt1lRVJRlGZjRKmQchhNBVIlZfL3g8I28veDyx+vqsYX87jDCoXNU4jpNmJR43
btzwjY1Go7Q9zIorgwoEAtK2wWAYvrF0J/F4PBqNpgYVt9sttVGr1cOcJCMjo6SkhNyn1+tNfau4
uPjZZ5995plnuru758+f/9BDD02ZMsVut7/11ls+nw8A/uu//qusrAwAksnkd7/73VAoZDAYfvKT
n4xtdM0OtX2ToVnqFhj4KC91U1yyEuOfSZpOqu9l/0qCI+/ioCjKoNCIANkqHcke0rGPz1hflVde
qi00qnRW2rmyaO5rTTvqfWYA2Dzv4c11Ww876kt1hY2+tsdnrn+s/M5whjDpj181KDW2iKsqr2Ll
WdPZpz94ven9J2p++tzcDZNWFhmV2o3Vr73WsqP+K+8E+QiQRQlvLAeAN7/yEgBw99+vKi39Oh9R
d3RTajXT2Eiyyg1Tp1JqdXDnTjLe9xauoFlBv5hzi8C7kiwrkg8uikBRJYnMkth4oKhNkTJ9Ug4U
JYoimSHtSXoK+cB9E6ZRVN/kaeRYgKHmXhMBllz81sCW0RMnACC4cyd5SR89GuqfxRsA2P4QTh85
Ej1xIhEMJlmWvMxQq6PHjytLS3mrVVlaKi8oYE6eTFw83JG3WlOvEjlyBABkRmP2unXKtOm5RTER
CsmMRvJtXPyOGDlyRLNoUcawfyW/mBLBoCzl/5wIITRm7OhL5FmzGYPK8DCoXNVSizQuueR8ajCQ
6u9HSKr9AIDMS/2yVqpoJwdmpwxika47cLKvgaRE5Penj3H6/ve/HwwGX3nlFZqmX3vttdS3vvWt
bz333HNke/v27R988AEAvPjii5MnT77kFQf1++4jn9Ik3UNlBjKJrVGptUVcQ7W8v2Ltby0f3l+x
dqf16ERV7l0VX2rwWXZZP3l8xvpSXWGprnBl0dzsdy5MG7Bl0WOzVIWnnS1TCsvFeHxD7U/JvLoT
taZQPEq2yVUMSu2cvApRFF9d/PicvAoAeMfyN5JJAOCJ6p+SCamkM5N5n56b99BO69Gq3PJSXeHO
1T9+8PCP7q/48ua6bSBChlptBFhXunxFUdU75g8/WP3S601bQITHZ64/5Kyryi0nIeq5+RuskSHX
/VCVlgIpMZ86VXopGffNb8ZdrvDevbNWrvy3M/vy1t+fZFneao27XAqTST11apJlw3v3xhobc+6+
W3nihHbRIkqt5m02EEW2tTWrqkpuMpFT8VZrVlWVobVVZjTKjEYSgZIsq66s5G22JMcp8vPjbjeI
oqKgQD11qspq5W2jKN0hOWSgRDCYSHkZPX6cbJB/2NjWVhjxv3CJYND7zjsyo1E9dSrJHhlqNdPa
2hd4jEbOalWYTAqTKREMygyGJMdFjx8HUdQsXgwAGSoVazYrS0szVKokx2Wo1VK2STIMUFTqnrTY
k/ZYT4LxRR+fYQCgr8NnQGSSDpP2p59hiOsOifytSUnpF25AFOMuV9ztFpNJDXkOSGksXT2wa5du
xYq0n7cvioHf9sCvXRSBoiLHj2sXLep7CQD9vx1IO5az2VQTJyZZlnz/SZaN9/aqSKKmKLIHKEpk
mL6hj+RYUZQOGeR+AMgvHahBb5WsdsBxGSrVhV9bAIzohwehK0QqI4w7Bp+bZxhjOOSLBoPKVY1N
eeiRXWrW7dQK+EgkMqoLpQaVS14otQslrd49HO5byFwuv/SPllQQPzCoyOXyl19+ed26de+9996R
I0dsNlthYeGKFSvuueeeVatWkX+xnE7nk08+CQA33ngjWVxlbKpyy8ly4IMTIXVBC70sa05+JQA0
+NpCfAQA/q38yw9UrM0/3zvj3AtvrfzBa03vN/rbAOCOiTesK11ui/S+0/q3Un1hqa7QGnYecdX/
W/mX15UuX1e6PMhH5v75gb+sfvGIs/7OicsafG1Bnn6t+f1SnclKux6fsd6o0G5Z/NidE5cZldqV
RXODfORB8YUtix6THuxm55Y3+toMSm39V94hAeDG8r4RcTeW3bCx+jWg4PEZ6wGgVFfY4LXYoq47
Jy4PcrSUFkg6ur/8wrS5H6x+yajUDpqvSI04eeuxGXdX5Za/uvhxac+zcx8M8pG3VzxF5rMiO99e
8bS0bVBo3lrx1NgyIaVSKSdOzLn//gy1+tbKSlEUKZVKVVmpqqwk56dUKsOdd8qMRtXUqar+iRlI
n4N2xYrUU5GdWQsXkpc599/P22xsa6tuxWAUBvcAACAASURBVAoA4Gw2mcGgMJlCu3bJjEbt8uXa
FStCu3bFGhszZ88m6QgoSkz5iyn2V/b/k5+MEsGglHYkvNXK97+b9rs9+uhR+uhRAMhQq5MsqzCZ
lCYTmSJTyh5xl0tmNGao1ZRaTZqR/SLLKkwmqr8LKBEMZs2eLQKIXN8k3ZRKBQAix/FWKzmDzGBI
hEIZBgMAyNRqzmZTlZaKoij09gKAurJSCAYpihKCQQCQG43kB4M1m5UTJ4ocJ7IspVZTKhVFUeTk
cqORd7kAQGkyZajV8d5emcHAms0AQK4iclzc5SJ/NJRaLXVGZajVnNksN5mSoRBntWbOni3LzBRF
kZyEt1rDLKtZtKjvcVmtJvlNbjSSlwAgBALy7GxKpeJsNrnRCKJIkhhp0PfZeV6m1ydCISEUkpP7
AQDSw0kmv1apRJ4ng/qAomQGA+leI1++0NsrLygg4wllRiNrscj0evKp4eL0K8vOBlEU3G55QYHI
MEmOkxmNiUCAfFJyeJJlE8GgwmQid5gIBklvW5JhGLNZnp2dZJhEKBR3uchfB95mkxuNGQYD2QAA
mcFA/qLyNpvIsnGXizWb5Uaj0D/ZHfmR4KzWvvvvn5VE+skh/yW3QanV5GeSfEDpR4v8LEH/QEr1
1KmKgoIkx8VdLtXEiSIA+WkhP5DkouQS0gb5DkWWJb93kBkMQm9vkmXlKcWKUkdihlrN22wZBoPc
aJQbjeRPSggGMzIz/397dx4fVXkvfvzMkskEEpKQEAbIwh40kBK2EDZDaCTc1mpsBUIB9SdyI7xE
W5BXq1ctvVV7r3UpXkHFmxZ4ASItil4hC0hYJOwJYTFsTTIBskIWAkwms/z+OHI8zEyGrDOT5PP+
w9dzznnOc76zBOd7zrNY7ty5feqUb2ysvL6YCFmtVnNdndrfX8yyTNXV3hERgkLh1bevxWAwlZdL
X36Vv7/4ki0Gg/aBBwSr1WowKHx8fsz87yZR5upqm+d4jWVlXmIvUK32xwr3ZmKCE/IMzVFB+jI3
/5RWXMVJgOJNpdad6/wUi8FQ89VX/g8/7PjRaHtfzp74tFwbGanUas0t/OklCIK5hbeVuyEWfPRo
165dk96ZlStX/td//ZeTytXV1b17/9AvZcmSJR9++GHzL/TKK6+8+eabYlmv1ztccl7y5ptvvvLK
K2K5oKAgMvLHxbPHjRsnjrAfNWpUfn6+84vOmDHj22+/FQRhwIAB0topzffMM8+kpaV5eXkdO3bs
vgN4nFh/cefTe98QDld615pNowLCLNoinwaFQrD4qJQb/iVcqBN8VNbUSOGG4cW+MX/9w1bxLOuv
IoSeauG2SfHNVeG2SRAEIaynUHJL6KG2vjzKGqRRLjnyQ8+sHmrrrcYfumb9PFTxbdkP9QVB6KH+
sSw2+7NQxeFKQRCE645Wk7y3vvXJIdafBCo/uiBcqLunEfHuY5C31WpV3DC2+p1xTrrHaV/oApcL
9fefNGjQ53l5Vqt1TkzMX37xi7BVq8TLzYyMXDdnztXa2pzCwtqGhu/Ly3/1k5+kHTny+syZoQEB
/8jLswpC0gMP5BQWPqjThYrj6W3uEAt2d3zv7r/Z0CDWr71zx79Hj89zc2dGRoYGBtreyXb5v9sA
PFadwdBLqxX/a7+/pKYmLCCgzmAQBEHc9Ndqpf021cRNQRBqDQZBEMJkv/7FE8VClE5XUlMjCIK/
VnumrEwQhJE63ZmyspE6Xa0sr5a3X2cw1BoM/lptSU1NL63W/26o4qZ4VDxFHk/J3dzY3kidrpej
7qzS+2AT8NmyMvG6YhhiZfFC4guRhyeFYf8O27/PbdT/bicRT+MhCz7yRAWd0s6dO9PS0gRBeO21
19qSpQiC8OSwf4voqYtfPEbctBgMdUrTb3L+GuGr+8MLPzyoqTHWZ187mVjT691XN4t7bFYTl1t/
ceffCr7Z2/hdK/6ea4z14hOJ5nj/9NZTNy6lnXuZZTc6yBZBEMQ7dl9+abFYpP216ek/GTFiZE2N
NBnXL+/WXKbVioVIrVYQhNqMDPGure/EiYbz529mZ2siIlQBAWJfI1NNzQ8dtAIC6tLTFT4+EbGx
qoCA23l5YTqdl073qk4nCEJjWVnlxx9rR4zoGRt7Mzu799y5N9avF7y91YGB4sh7KQuyNjSYa2vV
ISFKHx+LwSD28rLvqGO1WsVvjPxBkPVu50DFvRWEu3XkZY91T5CyF+JK8odR3Zz0vFEQPxRH3bfE
z8j1zyS7EvF3s/2vZ3GPmC1IR6XcQyrIqzlpTaoQpdPJNyfd7TkpFpoKo5dWKxai7nbElbdmT2w/
rOVDyOxfqXgJ6UI2Edq8cIfV5O+JkyylFV9jdW/HIyQhIVFB51NdXf3CCy8IgjB69OgXX3yx7Q3G
9x8jlcURF/H9Yx6N+HGcRoDGVz5sQ7BbTVzu0Yhp2ddyWxdJ87MUQRDi+48Z6NePLKWjKbVav/h4
+R7/pCTB0XAUeSeTH2rKVhPqGRurjYxUyfoUyQU99ZTYT0ZqX+Kl0/nFx4ud07yfekoQhOB///em
orVpXAxS/Oks9YxqLCtrLC9XabVKf39LQ4MgCObqai+dThUQYK6pUWq1ZoPBKhtgYNPzROwCp/Dx
8erbt7G8XBB+/OnpFRDQWFMj9RGSIpHeK4c/4pVarTg8RmrKajAovL3F2ZnFvlLmmhqlt7fi3tEv
Sq1WpdU21tSInc0EhUKMs6G42CcyUq3TGYuKGhwOMbp7FcudO6rAQHmhsaxM6eMjdqxqrKi4Jzap
41zfvmLfM4drulkaGrx0uh/eGdnl7F+m40LbNd2UzRwMP34cUoT3fjo/fsR366v8/aVuTo3l5Uqt
9oe+gt7et0+d8tLpxEZUAQE/zNAtO1cQBFVAQGN5ufgxmWprvSMiGsvKxFPkn5TybsLvFRAgaLXi
B6T08THV1IhXNDm60S7vnHbP+3HnTmNFhfh5aSIirAaDxWAQOy6KEZprasQ/hB+/Wt7eloZ7HmtL
3eRs3+Tmf4JOTmnLuR5yuQ461zWntNMbomj5s26N0w4sEEhU0Bm98cYb4oIt77//vjjHwJ07d7Zu
3bp9+/bc3Fyz2RwdHf3II4/Mnz//vjOYNUU+bKOlAjS+r4/5fy7IH8Sh7R19FQiC4OXonl8rJtES
e1E7PFGp1SqbuLMoCILfvSNtnLBpXJ47SUPGtbL1Vbskv7sF74ED/ZxVdI92n2rMQ+Yus8nnm2Lz
9ZM2XfBJNfVGWQwGcdaNdrmKdHdAvqepfy7sKzdV31xTIw4BkipIAz/EQ2LKJz9dfp9CbMQmF7VP
TeV3GcRD6rvvmMMk0DmlViuOZWoqh2wj8d80892WbV6LFL+TSzt5/vnDeK2AAHFhaPl7KBbE75J4
VB0QoAoIMFy6dGPTpha9BO3IkS2q3w2RqHRNTpaWd6jVv6ptBs23rh3nExnbOHjw4DvvvCMIwgsv
vPDQQw8JgqDX6+fNm/fdd99JdUpLSzMyMtasWbNt27YHH3ywFSG1kcvyhxY9gQHgCdo9qfCELKVT
aOqNUmq17bimqn2O4eSmRlO3Lex3yoMXK0g3UMRD7TV5XVPvUqu/ZmJgHfctlVpuaiKgNl7a4Y0q
ifxt1w4dqh0+3CBbUM457fDh2qFD2xJbd0Ci4tHkMwU3NDgaXS1jMv04zPq+cxnb6Nmzp1Q2Gu8z
/LqxsdFhhIJsxuHbt2/f96LShQKbs0q3IAiCcOvWrWXLlgmCMHDgwFdffVXcM3fu3JycHEEQxo4d
m5yc7OXltWvXruzs7HPnzj3++OP79+8PCQlpZvsAAACt45+UZLxyxdKMn0DKHj163dvLFw4p3R0A
nJHnD/IZhB2SV5Cf2Bx+fj8+dTfcbxiofJEWm0RFmnbMZg1Hh8TVG4VmLDEpee+993Jzc8VCUFCQ
IAibN28Ws5T58+d/9913r7zyysqVK3fv3r1ixQpBEM6fP7927dpmNg4AANBqqsDA3nPnKu+3Hp3S
x6d3Soq62XdpuzMSFY+m0Wik6YlLSkqcV66R9cJsznqLcr1l805UVlY6rywtP+/n5yfPcATZovW1
tbW1joaZSsxmszQlcb9+zeooderUqT/+8Y+CIPz6179+9NFHxZ1bt/4wX/Abb7whLcyiUqn+4z/+
IzQ0VBCEjRs3yudrAgAA6CCasLA+qanaqKimBuhro6L6pKZqQkNdHFgnRdcvTxcbG7t9+3ZBEPLy
8pwvHKHX66VyS5dpl9eXt+PQ6dOnxcL48eNtxqiMkI2SvHr1qpNHJaWlpdKTmQceeOC+ERqNxhdf
fLGxsTEoKOitt94S3weLxbJ//35BEGJiYsLDw+X1/f39p06dumXLlsuXL1dVVdH7CwAAuICqV6/e
v/qV8cqVhoKChitXxFUdVb16eQ8Y4D1iBClKi5CoeLrRo0eLiUp5efmFCxfkqyvaEPtEiQYNGtSi
qwyVDec6fPjwwoULm6pZWVmZl5cnlqOjo22OyhOV3NxcJwPZz549K5WHDRt23wg/+eST7OxsQRD+
+7//W1qP8s6dO+KAmSFDhtifIlWrr68nUQEAAC6jCQ3VhIZ64MSDnQtdvzxdXFycVM7Kymqqmslk
+uKLL8TyqFGjWpqoBAcHT58+XSxv375dPgrFxr59+6Ty1KlTbY7GxMRIE47t2LHDyRUzMjKk8oQJ
E5yHd+nSpZdfflkQhKSkJIdJlMMHTda7M5pbWz61OQAAANyLRMXTTZ48WRrC8c4779Q0MR34N998
c+rUKbE8d+7cVkwTPHfuXLFQXl6+fv16h3UaGxvfffddsezl5RVvN2t+cHDw7NmzxfK2bduOHj3q
sB29Xi+NcU9ISIi4dw0yG2azefny5Tdv3tRqte+88468s1mPHj3EqY2LiorsT5RG9bR0DjQAAAC4
HYmKp/Px8ZEWXy8qKlq6dGl9fb1NnXPnzi1dulQsa7XalJQU+3YMBsNnn322evXqY8eOObxQcnJy
3759xfJLL720d+9emwomk+nVV18Vp9gSBGHZsmXyIfiSRYsWSeVnnnmm2G5Z6Orq6kWLFklziy1Z
ssRhPJLPPvvsq6++EgThj3/8o01fMoVCMW3aNEEQ8vLyrl69Kj908+bNQ4cOCYIQHh7e0qkFAAAA
4HaqP/zhD265sNVqtVqtZrPZZDKZzeZevXq5JYxOITo6+p///Kc4me/p06ezsrJ8fHwUCkV9ff2F
CxfWr1//9NNPS9MBv/baa9KMWHIvvPDC7373u/T09HXr1v30pz+1GXouCELPnj39/f2//vprQRBM
JtP69evr6+u1Wm1jY2NZWdmBAweWL18uPWkJCgrasGGDzZRfooEDBxYWFoqPdyoqKrZs2aJUKr28
vAwGQ3Fx8ddff/3ss88eOXJErDxjxow33nhDqXSWMOt0uvr6epVKtWbNGvuFLBsaGr7++muLxVJb
Wztr1iyVSiUIgtVqfeutt8T0ZtmyZTNmzHD+DgMAAEBy8+ZNtVqtVqtVKpVSqRS76rR6ffBWU7i+
+754RYvFYjabjUajwWBoaGiQJuGFQ/n5+UlJSaWlpc6rzZs3Ly0tTZqlV2KxWPz8/KRFGF9//XWH
CarZbF6xYsX777/v/Co9evRIT0+3H6Aiqa6ufvzxx8Wx706MGjVq165dzfzoq6urHa4LeevWrcTE
RPE5z+TJk5OTkzUaTWZm5v/93/8JgjB06NCDBw9KT4oAAABwX1evXvX29tZqtRqNRsxVBHckKnT9
6hyio6N37949a9aspip4eXmtWrVq3bp19lmKIAhKpVI+BXD//v0dNqJSqd5+++3Vq1c7mVY4Li5u
7969TrIUQRACAwP/8Y9/PP/8807qzJ8/f+fOnc1PUJtavb5nz56fffbZ5MmTBUH47rvvVqxYsWzZ
MjFLiYyM3L59O1kKAABAZ8QTlc7EbDYfOHBg9+7dOTk5xcXFN27ciIiIGDx48IwZM2bOnOlwil7J
sWPHli9f/q9//Ss5Ofmtt95yPr782rVrGRkZWVlZFy5cKCoq8vPzCw8PHzduXGJi4vTp0x3mQg6d
OXMmMzNz7969RUVFJSUlOp1u4MCBU6dOTUxMvO9MXy1y586dbdu2bd++/fjx40ajMTo6+tFHH50/
f35T6Q0AAACa4iFPVEhUgC6oqKgoIyPjwIEDBQUFer1erVYPGDBgzJgxkyZN+vnPfx4UFNTMdnJz
c7Oysg4cOFBcXKzX6wcMGBAeHj516tSEhITY2NjW/YNVXl7+zTff/P3vf09NTZ03b17zTywuLs7K
ytq9e/fly5cLCwsDAgLCwsLGjRuXkJCQkJDQ/PwZAAA4R6JCogK0v+rq6lWrVq1Zs0ZcCtOev7//
qlWrli5dKp/o2V5ZWdmrr7766aefNlVh7ty5b7311sCBA5sZWENDQ3Z29meffbZp0yYxtk2bNjUz
UTEYDKtXr161apU0zsrG+PHj33vvPbEHIAAAaCMSFRIVoJ1dvHjxiSeekFbUcSIlJeVvf/tbU08h
ysvLf/7znx8/ftx5I5GRkbt27brv6qL5+flffPFFWlqaXq+X729motLY2JiampqWlua8mlar3bFj
x8MPP3zfBgEAgHMekqg4u6UKoBOpqqqaPXu2lKUMHDhw6dKlEydO7NOnj9lsvnz58saNG7dt2yYe
3bJly+DBg//0pz/Zt2O1WhctWiRlKUOGDHnxxRdjY2MDAgJqa2uPHTv2wQcffP/994IgnD9//skn
n9yzZ4/9tNGCrIvXgQMH2vK63n//fSlL0Wq1K1asePjhh0NCQgwGw/nz5//3f/83MzNTEASDwTB7
9uzTp0+HhYW15XIAAMBTWF3OYrFYLBaTydTQ0HDz5s3KysorV664Pgygi/ntb38r/V3PnTv3xo0b
9nXWrl0r//MvKCiwryOupSOKj4+vrKy0qXDjxo2kpCSpzsaNG+0bMZvNDrOXmJgYqbxp06b7vii9
Xi8t19OnT5/c3FybCo2Njb///e+lNlNTU+/bJgAAcO7KlSuVlZU3b95saGgwmUzir3fXh8H0xEBX
UFRU9O6774rlcePGrVu3zuGMZ6mpqfJpo7/55hv7Op988olY8PLy+vTTT4ODg20qBAYGfvrpp1L+
8NFHH9k3YrVa5YNkJk+e/PHHH1+9evXPf/5zC16VIGzbtu3mzZti+cMPPxw9erRNBbVavWrVqvj4
eCmY8vLyFl0CAAB4JhIVoCvYt2+fVF65cqWT6aefe+45qfzdd9/ZHC0tLZWeqDz77LNNzXk9YMCA
pUuXSo0UFBQ4rDZo0KBVq1adOnXqwIEDixcvbmoBHyc+//xzsRAZGfnYY485rOPl5fWb3/xG2szK
ymrpVQAAgAciUQG6gmPHjknlKVOmOKk5YsSIPn36iOWSkhKbo/IB9DNnznTSTmJiolTOy8uzOapU
Knfv3l1QUPDaa69FR0e3bvjdtWvXjhw5IpaTk5Md9iUTTZ06VToqnQIAADo1EhWgKygtLRULWq1W
p9M5qalQKKTeXPYzFF+6dEkqR0VFOWlHflQcW29zlRkzZmg0mvsF7kxhYaFUlg9usRcYGDh27Fix
fOLEibZcFAAAeAgSFaAr+OCDDwoLCwsLCwsKCpw/vmhoaJDyipEjR9ocvXDhglR2Pml4nz59/P39
xXJTXb/aSJ6ohIeHO688YsQIsXD8+HGj0dgR8QAAAFdiemKgK2j+8I8zZ85I5enTp9scraioEAt9
+vTRarVO2lEqlWFhYbW1tYIgVFVVtSDWZquurpbKUlLUFKk/W2Nj461bt9r4MAcAALgdT1SA7mXz
5s1iITAw0H4UijTFlv1kX/ak5OHGjRvtF+CPbt26JZV9fHycV+7Ro4fDEwEAQCdFogJ0I/n5+R98
8IFYfumll3r37m1Toa6uTizYD1+xJy1s74JERaVSOa8sf4Ry586djogHAAC4EokK0F3U19enpqaK
y5sMGTJkyZIl9nVMJlMrWjabzW0NzhGLxeLiEwEAgOcgUQG6BYvFsnz58pycHHHzf/7nf+476gMA
AMCNSFSAbuHtt9+Wlpz//e9/n5SU5N54AAAAnCNRAbq+v//977/73e/E8iOPPPL666+7Nx4AAID7
IlEBurivvvrq6aefFsvjx49PS0uTBsHba90S8s4nMm611gUjNG8mAAAA4OFIVICu7MCBAykpKWI5
MjJy27Ztzucdlgau3L59+76NS+sqBgYGti1Mx3r27Gl/raaIkwSI7juXMQAA8HwkKkCXlZeXl5yc
LKYcoaGhO3bsiIiIcH6KNGFxc9ZwvH79uljooHH5fn5+UtlgMDivLK0AI5CoAADQJZCoAF3TpUuX
kpOTxVwiKCjoq6++ioyMvO9Z0vrutbW14qrzTTGbzVeuXBHL/fr1a3O8DsiXeamsrHReuaKiQiz4
+fnJMxwAANBJkagAXdC1a9cef/zxoqIiQRD8/Py+/PLLmJiY5pw4YsQIqXz16lUnNUtLS6WHGA88
8EDrY23a4MGDpbJer3de+fTp02Jh/PjxjFEBAKALIFEBuprq6uo5c+aIP9y9vLw+//zzKVOmNPNc
eaKSm5vrpObZs2el8rBhw1oV6X0MHTpUKh8+fNhJzcrKyry8PLEcHR3dEcEAAAAXI1EBupTbt28/
+eSTBw8eFDc3bdrUoiVTYmJivLy8xPKOHTuc1MzIyJDKEyZMaHmk9xccHDx9+nSxvH37dvkoFBv7
9u2TylOnTu2IYAAAgIuRqABdh9FoTE1N/frrr8XNdevWPfHEEy1qITg4ePbs2WJ527ZtR48edVhN
r9evXbtWLCckJNx3jH6rzZ07VyyUl5evX7/eYZ3GxsZ3331XLHt5ecXHx3dQMAAAwJVIVIAuwmKx
rFy5cuPGjeLmX/7yl0WLFrWiHflZzzzzTHFxsU2F6urqRYsWSdNwLVmypFXxNktycnLfvn3F8ksv
vbR3716bCiaT6dVXX83JyRE3ly1bJh+CDwAAOi+GnAJdxBtvvPHXv/5VLC9cuPCJJ54oKSlpzol9
+vSRr9gYHx+/cOHCDRs2CIJw5syZ2NjYlStXTps2rXfv3nV1dceOHXvvvfe+//57sfKMGTMee+yx
9n4p98T2n//5n4sXLxYEwWAwJCQkLF++/Be/+EX//v2NRmNBQcEnn3widUILCgr67W9/23HBAAAA
V1JYrVYXX1K8osViMZvNRqPRYDA0NDQMGDDAxWEAXUl+fv5PfvKT1p176NChuLg4+Z7q6urHH388
Ozvb+YmjRo3atWtXi/54MzMzZ86cKZY3bdo0b968+55iNptXrFjx/vvvO6/Wo0eP9PR0BqgAANB2
V69e9fb21mq1Go1GpVIplUpBEBQKhYvDoOsX0BXI12Vvu8DAwH/84x/PP/+8kzrz58/fuXOnC24x
qFSqt99+e/Xq1U6WlYyLi9u7dy9ZCgAAXQldvwA4EBQUtHr16sWLF2dmZu7du7eoqKikpESn0w0c
OHDq1KmJiYkdNNOXQ2q1+vnnn//lL3+ZkZGRlZV14cKFoqIiPz+/8PDwcePGJSYmTp8+3dvb22Xx
AAAAF6DrFwAAAIAf0fULAAAAABwjUQEAAADgcUhUAAAAAHgcEhUAAAAAHodEBQAAAIDHIVEBAAAA
4HFIVAAAAAB4HBIVAAAAAB6HRAUAAACAxyFRAQAAAOBxSFQAAAAAeBwSFQAAAAAeh0QFAAAAgMch
UQEAAADgcUhUAAAAAHgcEhUAAAAAHodEBQAAAIDHIVEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAgHakcHcAAIDOR6VShYaGhoWFBQcHBwUF9erVS6PReHl5CYLQ2NhoNBrr
6uquX79eVVVVUlJy5coVs9ns7pABAJ0MiQrQmSiVynHjxsXExPTu3dtqtV67du3o0aMFBQXujgvd
hVqtjoyMjI6OjoiIUKvVzTzLZDIVFxfn5+efP3/eZDJ1aIQAgC6DRAXoNIYOHZqYmBgUFGSz//jx
4+np6W4JCd2Hr6/vxIkTx4wZo9FoWt2I0Wg8efLk4cOH6+vr2zE2AECXRKICdAJBQUGJiYlDhw5t
qsKOHTtOnz7typDQfXh7e0+bNm3s2LHNf4TinMlkOnHixP79+xsaGtqlQcDeyJEjJ0yYoNPplEql
WwKwWCxlZWVHjx49c+aMWwIAugASFcCjeXt7T5kyJTY21vn/a69du5aWluayqNB9REVFJSYm+vr6
tnvL9fX1WVlZZ8+ebfeWgVmzZo0dO9bdUfzgxIkTu3btcncUQKfUPrfHALQ7hUIRHR2dkJDQs2fP
+1YOCQlxQUjoVjQaTVJSUnR0dFMVTCZTSUmJXq+vqqq6fv26wWAwGo3iiVqtNigoKDg4ODw8PCws
zOGjGF9f3+Tk5CFDhqSnp4snAu1i5MiRnpOlCIIwduzYkpISnqsArUCiAniiAQMGzJw5s3///g6P
3rhx4+jRo0lJSdKe9uqTA4j8/f1TUlKCg4PtD1mt1osXL+bn51+8eNHhXF4Gg6Gurq6iokLcVKlU
w4YNGzVq1PDhwxUK28f40dHR/fv337JlS21tbbu/CnRPEyZMcHcItiZMmECiArQCP24Az+Ln5zdj
xoyRI0c6PGo0Gg8cOHD06FFfX195ogK0o5CQkHnz5tl397JYLHl5eTk5OdXV1c1vzWw2FxQUFBQU
BAYGxsXFjR492qYfY3Bw8NNPP715gdBgJwAADeVJREFU82YptwHaQqfTuTsEWx4YEtApkKgAnkKl
Uk2cOHHKlCniYhT2Tp069e233966dcvFgaFbCQkJefLJJ729vW326/X69PT0tuQS1dXVO3fuPH78
eFJSUnh4uPyQr6/vk08+uX79enIVtJ1NJvzBBx+4ZdqGFStWSGV3DegHOjsSFcAjDB8+PDExMTAw
0OHRq1evZmZmXr161cVRobvx9/efN2+eTZZisVj27dt36NAhq9Xa9ktUVFRs3LgxLi4uPj5e/uvN
29t73rx5f/vb3+gDhvbV0NBgMBjcHQWA1iBRAdwsODh45syZgwYNcni0vr5+z549Z86caZffiIAT
Go0mJSXFpseXwWDYunVrSUlJO17IarUeOnSopKRkzpw5Wq1W2u/r65uSkpKWlsbYegCAQKICuJFW
q502bdr48ePtRxgLgmA2m48cOXLw4EF+tME1kpKSbEbP37x5c8uWLR3UHaukpGTDhg0pKSl+fn7S
zuDg4KSkpK+++qojrggA6FxIVAA3UCgUMTEx8fHxPXr0cFjhwoULWVlZLRqyDLRFVFSUzUzEBoOh
47IUUUVFxZYtWxYuXCh/rhIdHX358mXWVwEAkKgArhYeHj5z5sy+ffs6PFpVVZWZmfmvf/3LxVGh
O/P29k5MTJTvsVgsW7dudcHQ9oqKiq1bty5YsEA+XiUxMfHSpUusWw8A3RyJCuA6/v7+M2bMePDB
Bx0eNRgM+/fvP378uMVicXFg6OamTZtmMzRl37597TsuxYmSkpLs7OyEhARpj6+v77Rp07KyslwT
AADAM5GoAK6gVqsnTZo0adKkplZmzM3N3bt37+3bt10cGODr62uzjLderz906JArY8jJyRk6dKh8
zuKxY8fm5OTU19e7MgwAgEchUQE63IMPPvjTn/60V69eDo/q9frMzMyysjIXRwWIJk6cKM+fLRZL
enq6i2eZs1qt6enpixYtkjqAqdXqiRMn7t6925VhAAA8CokK0IH69u07c+ZMm7XtJHV1dXv27GHQ
MNxIrVaPGTNGvicvL88tqy5WVFTk5eXJgxkzZkx2drbJZHJ9MAAAT0CiAnQIHx+f+Ph4mx41EpPJ
dOjQoZycnMbGRhcHBshFRkZqNBpp02q15uTkuCuYnJycmJgYabZujUYTGRlJJg8A3RaJCtDOlErl
2LFjH3roIfmMq3Lff//97t27WX4bnsBmSuKLFy+6cVLs6urqCxcuREZGSnuio6NJVACg2yJRAdrT
oEGDHn744T59+jg8WlFRkZGRUVxc7OKoAIdUKlVERIR8T35+vruCEZ0+fVqeqERERKhUKrPZ7MaQ
AADuQqICtI+AgIDExET5byy5O3fuZGdnnzx50sVjlAEnQkND5cPoTSbTxYsX3RiPIAgXL140mUxS
VGq1OjQ0lNweALonEhWgrTQazZQpU2JjY1Uqlf1Rq9V64sSJ7Oxsg8Hg+tgAJ8LCwuSbJSUlbn92
YTabS0pKBg0aJO0JCwsjUQGA7olEBWiTqKioxMREm8XyJIWFhZmZmZWVlS6OCmiO4OBg+aZer3dX
JHJ6vV6eqNgECQDoPkhUgNZLSkoaN26cw0M1NTW7d+8uKChwcUhA8wUFBck3q6qq3BWJnE0YNkEC
ALoPEhWglaKiohxmKY2NjQcPHjxy5AjrP8DD2SxCev36dXdFImcTRlMrpQIAujwSFaCVxo8fb7/z
zJkze/bsuXnzpuvjAVpKvoKKIAgeMozKJgybIAEA3QeJCtBKOp1OvllaWpqRkXHlyhV3xQO0lJeX
l3zTaDS6KxI5mzBsggQAdB9KdwcAAAAAALZIVIBWKisrk2/269fvqaeeeuyxx/z8/NwVEtAijY2N
8k0P6WRlE4ZNkACA7oNEBWilY8eO2e8cOXLkkiVLJk+eLF9HD/BMNp2stFqtuyKRswnDQzqkAQBc
j0QFaKWzZ88eP37cfr+Xl9f06dNTU1NHjBjh+qiA5qurq5NveshEwDZh2AQJAOg+SFSA1ktPT//i
iy/q6+vtDwUEBPzqV7/69a9/3adPH9cHBjSHzUTAHrK0ok0YHjJpMgDA9UhUgDY5e/bsmjVrDh06
ZDab7Y8OGjRo8eLFSUlJHtKpBpCzWVoxPDzcXZHI2YThIctQAgBcj0QFaCuj0fjtt9+uXbv2/Pnz
9kcVCsW4ceOWLl06duxYhULh+vCAppSUlMg3w8LCVCqVu4IRqVSqsLAw+R6bIAEA3QeJCtA+ampq
tm3btmnTpsrKSvujPj4+s2bNevbZZyMiIlwfG+DQlStXTCaTtKlWq4cNG+bGeARBGDZsmHwiCpPJ
xNpEANBtkagA7amwsHDdunUZGRkOF/kOCQlZsGDBL3/5S39/f9fHBtgwm83FxcXyPdHR0e4KRjRq
1Cj5ZnFxscNOlQCA7oBEBWhnFovl2LFjH3744YkTJxxWeOCBB5577rlp06ax5DbcLj8/X745bNiw
wMBAdwUTGBg4fPhw+R6b8AAA3QqJCtAh7ty5s2vXrnXr1un1evujarV62rRpzz33XFRUlOtjAyTn
z5+XL1SiUCji4uLcFUxcXJx8HJfRaHQ47gsA0E2QqAAdqLy8fMOGDdu3b3e4FkSvXr2Sk5MXLlyo
0+lcHxsgCILJZDp58qR8z+jRo0NCQlwfSUhIyOjRo+V7Tp48KR9CAwDobkhUgA537ty5NWvW7N+/
3+GvrvDw8EWLFv3sZz/r0aOH62MDDh8+LP9mKpXKpKQkF89Qp1AokpKSlMof/5dkMpkOHz7syhgA
AJ6GRAVwBZPJtH///rVr1547d85hhZiYmCVLlkyYMEH+Ww1wgfr6epvxVOHh4ZMmTXJlDHFxcTbL
p5w4ccLhUqoAgO6Dn0SA69TW1m7fvn3Dhg3l5eX2R7Va7cMPP7x48eLBgwe7PjZ0Z/v377fJCh56
6CGb9Uw6TlhYWHx8vHxPfX39/v37XXN1AIDHIlEBXE2v13/66ac7d+68ffu2/dHg4OB58+bNnj3b
jZMvobtpaGjIysqS71EqlXPmzHHBYJWQkJA5c+bYPEjMyspqaGjo6EsDADwciQrgBlar9eTJk2vW
rDl69KjVarWvMHz48NTU1ISEBI1G4/rw0A2dPXvWZi5grVabkpLSoblKSEhISkqKVquV78zPzz97
9mzHXRQA0FmQqABuYzAYMjMzP/7448LCQvujKpVq0qRJS5YsGTVqlItHNqN7Sk9Pr6qqku/x8/Nb
uHBhB/UBCwsLW7hwoZ+fn3xnVVVVenp6R1wOANDpkKgAblZVVbVp06bPP/+8urra/qivr++jjz76
1FNPDRgwwPWxoVsxGo1btmyxGayi1WoXLFgwefLkdsyWFQrFpEmTFixYYPMspb6+fsuWLfJ1XQAA
3RmJCuARLly48NFHH+3du7exsdH+6IABA55++ulHHnmkZ8+ero8N3Udtbe3mzZttxocolcrp06cv
WLCgXbqBhYSELFiwICEhwWZcSkNDw+bNm2tra9t+CQBA10B/EsCz+Pn5zZgxY+TIkQ6PGo3GAwcO
HD161NfX9/nnn5cf+tOf/uSSANH1hYSEzJs3z9fX12a/xWLJy8vLyclx+PTvvgIDA+Pi4kaPHm0/
B3d9ff3mzZsrKipaGTEg8/LLL3vaPO8Wi+XNN990dxRA56NydwAA7mE0GgsKCi5fvty3b1+b7vuC
IKhUqsGDB0dFRRkMhqFDh8oPMZ0r2sutW7e+//77IUOG2CxCqlAo+vXrN378+H79+pnN5urqaodT
QdhQqVSRkZHTp09PSkrq37+/fReyqqqqjRs33rhxoz1fA7qxYcOG2f/j6V6lpaW5ubnujgLofHii
AngohUIRHR2dkJDQnO5eJpPpz3/+swuiQveh0WiSkpKio6ObqmAymUpKSvR6fVVV1fXr1w0Ggzi8
RKPRaLXaoKCg4ODg8PDwsLAwtVrdVCP5+fnp6emMS0E7Gjly5GOPPebuKO7x5Zdfnjlzxt1RAJ0P
iQrg0by9vadMmRIbG+u8J8O1a9fS0tJcFhW6j6ioqMTERPtuYG1XX1+flZXFTMToCLNmzRo7dqy7
o/jBiRMndu3a5e4ogE6Jrl+ARzObzYWFhefOnQsMDOzdu3dT1b799lv696MjVFZW5ubmqtVqnU7X
Xv3+TSbTsWPH/vnPf5aWlrZLg4CNS5cu3bhxo1evXj179nTX9O4Wi6W0tHTPnj2HDh1ySwBAF8AT
FaDTGDp0aGJiYlBQkM3+48ePs/QEOpqvr+/EiRPHjBnTlkVIjUbjyZMnDx8+bDMJMgAA9khUgM5E
qVSOGzcuJiamd+/eVqv12rVrR48eLSgocHdc6C7UanVkZGR0dHRERISTkSc2TCZTcXFxfn7++fPn
TSZTh0YIAOgySFQAAC2mUqlCQ0PDwsKCg4ODgoJ69eql0Wi8vLwEQWhsbDQajXV1ddevX6+qqiop
Kbly5YrZbHZ3yAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAuMz/B32WuMb6
KO+yAAAAAElFTkSuQmCC

--_002_AM4PR0401MB22419992B651EBBA3FC9B6FEBD040AM4PR0401MB2241_--


From nobody Sat Apr 15 07:01:49 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB8B128D44 for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 07:01: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, RP_MATCHES_RCVD=-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 u3BdorD1JWmi for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 07:01:45 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2FD81275AB for <ietf@ietf.org>; Sat, 15 Apr 2017 07:01:42 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0EBAA203B8; Sat, 15 Apr 2017 10:26:35 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 790CC636BB; Sat, 15 Apr 2017 10:01:41 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian Hopps <chopps@chopps.org>
cc: "Joel M. Halpern" <jmh@joelhalpern.com>, ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-Reply-To: <87inm6uhet.fsf@chopps.org>
References: <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <20170404211526.GA25253@gsp.org> <003F08E0-D80E-40F7-AB15-6588B7B140CF@tzi.org> <20170410180555.GA20454@gsp.org> <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sat, 15 Apr 2017 10:01:41 -0400
Message-ID: <6566.1492264901@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qCKkWeuP0YX8LiIe3EN7Sq_osS4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 14:01:47 -0000

--=-=-=
Content-Type: text/plain


Christian Hopps <chopps@chopps.org> wrote:
    >> Yes, funding matters.  But in my view that is secondary to the actual
    >> benefit of the meetings.  Which is why I attend.

    > +1

    > Whenever I read messages that advocate for switching to remote only
    > meetings, I have to wonder, are those people just not getting what I
    > get out of f2f meetings? I find the meetings invaluable for the reasons
    > you list above.

Oh, I get it completely!
And there is a fax effect on f2f meetings.  This is why we are willing to put
up with the hassle of travel in the first place.

My argument is as follows:  if a significant number of people can not attend
in person due to visa, travel, etc. issues, then the value of the meeting
declines.   The people that we interact with a high bandwidth become the same
set of people who can get through.  Our views become myopic.

So in the case where we can not have everyone in the same place, then it
would be fairer to have "everyone" remote.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAljyJ8UACgkQgItw+93Q
3WWI3AgAoxzcJZuVjb0rWvxR1uWaBk4W5GIwF58aB2kp1WwQl8gsu5TOZ4NjLVCe
nxG7wAGzeWgSQYN25hQsCcifKNW8JogY7Is8B0M7EEenvDIpY8XxJCBN72Py/kdm
zKtlTRrx1i8uWXzt2A+aUVTJvavYQdAZHvn6yg20DbiyBaxGMIZWHpESvINk43AK
M5zpPQry0zdnaUN6asUgubGtzPUEbPtThM1Zi7kB86/OkPB7kMbKixqZc/gwiSzj
57wbmugnQ0yIUXWt8ns/FYp9nIS/o5VWX1RBmiwEL8YMhLRIddg85R9x3pRuHRKm
Jo0Drtyf3n9WsIApHG7F1u5rjZ2T7g==
=Mpvb
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Apr 15 08:22:14 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE990127ABE for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 08:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 EdGLPshCOwJd for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 08:22:12 -0700 (PDT)
Received: from nm3-vm6.bullet.mail.gq1.yahoo.com (nm3-vm6.bullet.mail.gq1.yahoo.com [98.136.218.149]) (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 73787126C2F for <ietf@ietf.org>; Sat, 15 Apr 2017 08:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1492269731; bh=OBwSgOjiya7wczT5dxRuwPGMRaxgCdHkyvDUfzEfhTg=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=UMLcf2G0d9YJDeJwZ1O50uaioY0NWPeiUGs1C1uy9ZpT9gxN574svWAqEHghArFsxIDWX7y94kWeHCadH9juscxEjClsXR6yKnbe8W3a9Ds/o7tUoW+Wjv/0cBMvfFtyYGBortKjphhQIOWbL+ZoAgRWw8q/NiPVX41DgU41pmtqCINSb/cHBHlS5fyzal66frOKKXdfAF+BC+C/TBILivsRraxoiyeIFSVeX3YKDw8sFlPk6mva4iNUJmEl9tTlm0GQ5PNivUxUqDc0OjrFhtb9+hCvQavMdGlJvEnekeoQLYMk1uOjrWzEdxBSwrKzZkNW3KodhVAPt0NQS4UeSA==
Received: from [98.137.12.188] by nm3.bullet.mail.gq1.yahoo.com with NNFMP; 15 Apr 2017 15:22:11 -0000
Received: from [98.137.12.231] by tm9.bullet.mail.gq1.yahoo.com with NNFMP; 15 Apr 2017 15:22:11 -0000
Received: from [127.0.0.1] by omp1039.mail.gq1.yahoo.com with NNFMP; 15 Apr 2017 15:22:11 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 815545.70911.bm@omp1039.mail.gq1.yahoo.com
X-YMail-OSG: RxxGZ5wVM1nMHuffMzTCpf5gIBdbfUv7nwi6H5HBYUWHmBuWDXeKqblp3Hh2W09 0391vnJBcdC4ik9Y9ynhEd1c6RJ2IOC1RfooBzSvEbRk4B7547fktTZn9dG4ckqv1HFgP36uu3gW 8tzbXiu2k0BXfHnYBNw9LSFdFqDG78XiqfAHF7RC2t7lsR3vyDbtcdoBnBZRtAx3w.HCCbylKplX 63biw4oBR3ZHxdGoBk3RXOpbpcC8CQNHs0AzzaMYY2eUiOFpJpx0zBoBljVO.Gikr.mXSBMs26ww AYM7ZSvOWbTdKEDY5Mo.8MWaqjw3dtwgu6b.2TxwcGP0hHqmVv9AQv2fZm5j3Ug_vpRmvEHNICCo kv2iFHP77vxBYtZxHBhnmJIqcvq50lKr.cJnk9iKeaM1sBd_VQIxkj_qy6zAfaNZ.ZqCi4MUP8eu xjtZt1xD_Jedf.KoFqkuSttQdvES_z4kJJ3vecHPGKF2qL.k2hYldl5cwp3zU2Fe9r50Y9yEJ3pe ncudZj0FqUMEM6XDf_wYUZsmzULetv.A5bMalBOT2GHtFkiMo0Qs-
Received: from jws300037.mail.gq1.yahoo.com by sendmailws107.mail.gq1.yahoo.com; Sat, 15 Apr 2017 15:22:11 +0000; 1492269731.441
Date: Sat, 15 Apr 2017 15:22:10 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
Reply-To: <nalini.elkins@insidethestack.com>
To: Christian Hopps <chopps@chopps.org>,  Michael Richardson <mcr+ietf@sandelman.ca>
Cc: <ietf@ietf.org>
Message-ID: <2058830378.1115716.1492269730755@mail.yahoo.com>
Subject: Re: IAOC requesting input on (potential) meeting cities
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <2058830378.1115716.1492269730755.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9408 YahooMailBasic Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mvvV4KJ2malDJmLlF-yeWMuO02Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 15:22:13 -0000

=20
 Christian Hopps <chopps@chopps.org> wrote:
=20
 >> Whenever I read messages that advocate for switching to remote only
 >> meetings, I have to wonder, are those people just not getting what I
 >> get out of f2f meetings? I find the meetings invaluable for the reasons
 >> you list above.
=20
> Oh, I get it completely!
> And there is a fax effect on f2f meetings.=C2=A0 This is why we are willi=
ng to put up with the hassle of travel in the first place.
=20
 > My argument is as follows:=C2=A0 if a significant number of people can n=
ot attend in person due to visa, travel, etc. issues, then the value of the=
 meeting declines.=C2=A0  The people that we
 > interact with a high bandwidth become the same set of people who can get=
 through.=C2=A0 Our views become myopic.
=20
> So in the case where we can not have everyone in the same place, then it =
would be fairer to have "everyone" remote.
=20
 I wonder.  People have been talking a good deal about how in the US we clu=
ster with like minded people.   So, in some ways, clustering in remote hubs=
 in place of the larger meeting reinforces this effect.

I suspect that with all remote hubs, we will connect / pay attention to peo=
ple we know already at other remote hubs.   But, we got to know them probab=
ly by f2f meetings.  So, this makes the barrier to entry to real participat=
ion in the IETF that much higher.

I know that in India, at one of the universities, there have been remote hu=
bs with hundreds of students.  But, they were observers not really particip=
ants.  Still, I suspect we don't know who they were, what they thought or a=
ny of it.

I wonder if a more global rotation of f2f meetings to places where we don't=
 normally go to and where some regulars will be uncomfortable because of in=
 your face poverty, maybe food you don't like so much, and the rest of it i=
s closer to the answer.  =20

IMHO, we are in a situation where many countries are in a bit of turmoil, i=
ncluding the formerly stable-ish U.S., U.K., etc.     I suspect this will t=
ake a while to settle down.   I understand Mr. Trump has already raised mon=
ey for his re-election bid.   In some ways, I feel that now we are experien=
cing what many other people have long experienced in their own countries (o=
r even parts of the U.S.) that is, an environment that is not necessarily o=
f their own choosing.   But, we have to make the best of it.   I suspect it=
 will not be over soon.   It is also not clear how much is bluster and what=
 will actually change. =20

Having said that, for many reasons, being OK with being uncomfortable in a =
f2f meeting to achieve a higher goal may not be all bad.   When I was young=
, I lived at the edge of the bush in Africa for two years.   I had no runni=
ng water.   My only "media" contact was BBC on the shortwave radio after 10=
pm.   It was two of the happiest years of my life.   One thing I learned is=
 that many things you think you need, you don't.   And, it is all worth it =
for the learning and understanding you gain of others.

Nalini


From nobody Sat Apr 15 10:15:36 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13617126DCA; Sat, 15 Apr 2017 10:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 K8i0LywUlYxS; Sat, 15 Apr 2017 10:15:32 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::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 2AC45129416; Sat, 15 Apr 2017 10:15:32 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id h67so83805940qke.0; Sat, 15 Apr 2017 10:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Vtk9+xooRg8KgzZhbpNBeA9e08Xv32Ai+lu5HJutI08=; b=rDNm77FDA4KCFwgXlwSPL3JMIqF6Kyw2WUXqWa4Ok04Mv/VK4G/qpNObH4jS7d+PHj p+EK68d2smlBLwhTAxkh2iRVcuhIiA5s2g2UKh4O2U6fkMpRtJoSe8TfUMo95R9cRc8n DGySaVChq3B8zbvRFKv8lEOjJhb43ivkSD/rob9y7tlz8kAVmhp2vd39P98hBPi2QppE tGcTLVL/Q45GZgeCpMm3pndA/zwkogZah0zqA84AgZl3bW0+SXwyQOffSCTZ7UXFjd7O MVUDeBikT2LWPhXKhE/qexn5P1px8O5N7mTIZiD+Tr0h1Rmqm7iA7kQI97d97M6ItwZE tRYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Vtk9+xooRg8KgzZhbpNBeA9e08Xv32Ai+lu5HJutI08=; b=S+qpLm4Z3xjUwtIPWlO4wAsFIlG7j0iMnjaGnhyjvfOBjaPpAlwc/C4eYyQkcfukr3 TFGcUooHlydZ4KSlblMxImE5WPkbRafP3sZ5uiFFvCkN7XL8+AsaqnaamP8LO42yiLcX mg5oWxvwCV++Nukd6z1mh3NoMXfhE6EYQYQAPkk6JuKCso2lRBXZ4W5c5Y7b6mCfVUgv KPTlGOrhsT4q9BaWG/u7/Mx0lJ6z6yX9f6ET7rdVWSWlaqqq3RihmN2a3PjHtp1Uyg/6 fezndkzI5/QxbrXAk6CeQLZfIKpq4Hh28dj+0qgdM2tdNgv0GqUX7O8OezeU05+tdC+t g1/g==
X-Gm-Message-State: AN3rC/47mbYIJr51LjuEmMuTULenpXSCX/O7dqEyy62hg+05BwUR/+xc CSdJfRjR+kNNNiluxCOeaNZcQ0NKMw==
X-Received: by 10.55.19.104 with SMTP id d101mr2469270qkh.220.1492276531277; Sat, 15 Apr 2017 10:15:31 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.93.5 with HTTP; Sat, 15 Apr 2017 10:15:30 -0700 (PDT)
In-Reply-To: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Sat, 15 Apr 2017 13:15:30 -0400
X-Google-Sender-Auth: q_sMWEmKYz7RADjZaLmrC-re_EE
Message-ID: <CAL9jLaa+zTSj9g1QMQAEPDiVqEmGG3OtChuu5NvA3feTX2mrjw@mail.gmail.com>
Subject: Re: Google Statistics for IPv6 adoption.
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: int-area <int-area@ietf.org>, intarea-ads <intarea-ads@ietf.org>, ietf <ietf@ietf.org>, intarea-chairs <intarea-chairs@ietf.org>
Content-Type: multipart/alternative; boundary=001a11400a988db46e054d37b40c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b20T5N_3MKdv_YkYsMwHjWMtrAA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 17:15:34 -0000

--001a11400a988db46e054d37b40c
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar <eng.khaled.omar@hotmail.com>
wrote:

> Hi all,
>
> Please check out this link that shows the statistics of the IPv6 adoption
> over the past 10 years maybe it will make you believe what was said earlier.
>

'what was said earlier' - citation requested.


>
>  https://www.google.com/intl/en/ipv6/statistics.html
>
> Recent IPv6 adoption (April, 2017) is:
> 14.83% Native - 0.03% 6to4 - 14.87% Total
>
> Best regards,
>
> Khaled Omar

--001a11400a988db46e054d37b40c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:eng.khaled.omar@hotmail.com" target=3D"_blank">eng.khaled.oma=
r@hotmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi al=
l,<br>
<br>
Please check out this link that shows the statistics of the IPv6 adoption o=
ver the past 10 years maybe it will make you believe what was said earlier.=
<br></blockquote><div><br></div><div>&#39;what was said earlier&#39; - cita=
tion requested.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0<a href=3D"https://www.google.com/intl/en/ipv6/statistics.html" rel=
=3D"noreferrer" target=3D"_blank">https://www.google.com/intl/<wbr>en/ipv6/=
statistics.html</a><br>
<br>
Recent IPv6 adoption (April, 2017) is:<br>
14.83% Native - 0.03% 6to4 - 14.87% Total<br>
<br>
Best regards,<br>
<br>
Khaled Omar</blockquote></div><br></div></div>

--001a11400a988db46e054d37b40c--


From nobody Sat Apr 15 10:52:36 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EBDD12922E; Sat, 15 Apr 2017 10:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.146
X-Spam-Level: 
X-Spam-Status: No, score=-0.146 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 QjLm7eviDx4O; Sat, 15 Apr 2017 10:52:25 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-oln040092067013.outbound.protection.outlook.com [40.92.67.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D74D124281; Sat, 15 Apr 2017 10:52:25 -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; bh=2Uuyny40c7yMku2/r+t2avQKj1g/b+HYEUMk7AfYFEQ=; b=TEoXJDz5CyAubFeeQZV5eJxOakN7lQ/eIPhxxg8jboAXLvPGUmQ1pI9EaZA3K3DUkkO1qvWlxsa/fXU+b5GwSF1ShXCWTqfm7JqiecJdbBGHHExfgu5Gs5Fk9Z/CPmU0ci/IFvY618uXo8CWQIEJhPF5P6iJAL+Sc3oeMyHW/G/FlURcTVfh6W4WcLOgOILelxu+0E2sCrFRdFZ87qlfE/PolT+SxjpF7kzcPn8hlH4KT6rXUABX1BMSctnGc5haIoXZCBtcltSbsLHJhBltNgyyGZfKNcloGFBkXf9nrohJ8bfP8eiKXAxIrBguDZ0u2S748Lo5T78C4ULsEb3liQ==
Received: from AM5EUR02FT065.eop-EUR02.prod.protection.outlook.com (10.152.8.57) by AM5EUR02HT003.eop-EUR02.prod.protection.outlook.com (10.152.8.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Sat, 15 Apr 2017 17:52:23 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.8.52) by AM5EUR02FT065.mail.protection.outlook.com (10.152.9.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Sat, 15 Apr 2017 17:52:23 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1034.013; Sat, 15 Apr 2017 17:52:23 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
CC: "int-area@ietf.org" <int-area@ietf.org>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Google Statistics for IPv6 adoption.
Thread-Topic: Google Statistics for IPv6 adoption.
Thread-Index: AQHStemMObrieeNbo0ud4Z8rRPM6OKHGq/AAgAAIk3A=
Date: Sat, 15 Apr 2017 17:52:23 +0000
Message-ID: <AM4PR0401MB2241F94B536F114D83190A14BD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com> <CAL9jLaa+zTSj9g1QMQAEPDiVqEmGG3OtChuu5NvA3feTX2mrjw@mail.gmail.com>
In-Reply-To: <CAL9jLaa+zTSj9g1QMQAEPDiVqEmGG3OtChuu5NvA3feTX2mrjw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:9D9B6F54CA7E90502FE05CE401C9B33784DEFEFC969016AAE24B40E6F95D1F42; UpperCasedChecksum:AE03A5ED14940F6C9D07CEC0E22E58C03A58235E911BC83A2BE53F5D0FBEF25C; SizeAsReceived:8318; Count:42
x-tmn: [VjPDzs/GdplTmEDyXZNtAUhxzaF6MWQ1]
x-microsoft-exchange-diagnostics: 1; AM5EUR02HT003; 5:qkvpgu/cCxu8AEYKIIVKVuYZul/Tl1q6sXqgnqjPq0g77/8lXsbgng29JG4OsmJxZsHK9NGP0EI5i9nrb246wuYT2f2TEEGRBkKtBxzhAiIEE3BgN1M/MCWqNNK2QqK8Xvgz7+5ZhBwI+5oMMcEeDQ==; 24:1oM4JQv6l5jwab00vvp19jqctBhdCDxvAfcdkIUYUocAICmsyZpkSi8+AH0CaJ29YiB8xkxP1Kzg+/WkWuXeeJ0/dHAdH8Wx09hKVNqEYP4=; 7:9/aRrO8dgEVI+s+gYCyCCXstF+GVFvV51sw3s3Bwm1b4eMJ2Rzesjqzb351EZzW21fE7qUTKy0me/++qA7txAqhn9Qk8SsKaAtDOQwrwkX7CdPNQCYLrgvkPpQAfamdbXq5eqOT5eOvWJfWAkSWFbsnqmx0JHliqssH9co8rSPLwFlaKhOKctBKRaY2kEb/9n9h4CxhdIXmDMs2IdWuHMvYqYt3gLz6TtE9brQ4Wtqc3Cpdk1CQrFC/BcarK3jTbW0r2i1r72m4rXuzlcpZmBL1UhE1gECt0aOnWfMutIFAxGROEo3w5QwRvMGbExviz
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR02HT003; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 4b2ace8a-c27a-4a69-4bfe-08d484282be8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR02HT003; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR02HT003; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR02HT003; 
x-forefront-prvs: 02788FF38E
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241F94B536F114D83190A14BD040AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2017 17:52:23.4973 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT003
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pxERKcNDwoApYP79Ysy7iZ73GPM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 17:52:28 -0000

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

SGkgQ2hyaXN0b3BoZXIsDQoNCj4gJ3doYXQgd2FzIHNhaWQgZWFybGllcicgLSBjaXRhdGlvbiBy
ZXF1ZXN0ZWQuDQoNCldoYXQgSSBzYWlkIG1lYW5zIHRoYXQgc2luY2UgSSB3cm90ZSB0aGUgSVB2
MTAgSS1EIG9uIEdvb2dsZSBibG9nZ2VyLCBJIHdyb3RlIHRoYXQgdGhlIGRlcGxveW1lbnQgb2Yg
SVB2NiBpcyBhYm91dCA1JSBvZiB0aGUgSW50ZXJuZXQgdHJhZmZpYywgYW5kIEkgZ290IHJlc3Bv
bnNlcyBmcm9tIHNvbWUgSUVURiBtZW1iZXJzIEp1c3QgY2xhaW1pbmcgdGhhdCB0aGlzIGlzIGEg
d3JvbmcgcGVyY2VudGFnZSBhbmQgdGhlIHJlYWwgZXhjZWVkcyA2MCUgYW5kIGdhdmUgbWUgc29t
ZSBleGFtcGxlcyBvZiBtb2JpbGUgcHJvdmlkZXJz4oCZIHN0YXRpc3RpY3MuDQoNClNvLCB0aGlz
IEdvb2dsZSBzdGF0aXN0aWNzIGNvbmZpcm1zIHdoYXQgSSBoYWQgc2FpZCBlYXJsaWVyIGJlY2F1
c2UgSSBnb3QgdGhpcyBwZXJjZW50IGZyb20gc29tZSBvbmxpbmUgc3RhdGlzdGljcyB0aGF0IGJl
bG9uZ3MgdG8gdGhlIElQIGFkZHJlc3MgYXNzaWdubWVudCBwcm9jZXNzLg0KDQpJIHdvdWxkIGxp
a2UgdG8gdGhhbmsgR29vZ2xlIGZvciB0aGUgZWZmb3J0cyBtYWRlIHRvIG1ha2UgdGhpcyBtZWFz
dXJlbWVudHMgYW5kIHByb3ZpZGUgYSByZXNwZWN0ZnVsIGFuZCByZWFsIHN0YXRpc3RpY3MgdGhh
dCBkZXNjcmliZXMgdGhlIHJlY2VudCBzaXR1YXRpb24gc28gd2UgY2FuIG1ha2UgZGVjaXNpb25z
IGJhc2VkIG9uIGl0Lg0KDQpCZXN0IFJlZ2FyZHMsDQoNCktoYWxlZCBPbWFyDQoNCg0KRnJvbTog
Y2hyaXN0b3BoZXIubW9ycm93QGdtYWlsLmNvbSBbbWFpbHRvOmNocmlzdG9waGVyLm1vcnJvd0Bn
bWFpbC5jb21dIE9uIEJlaGFsZiBPZiBDaHJpc3RvcGhlciBNb3Jyb3cNClNlbnQ6IFNhdHVyZGF5
LCBBcHJpbCAxNSwgMjAxNyA3OjE2IFBNDQpUbzogS2hhbGVkIE9tYXINCkNjOiBpbnQtYXJlYTsg
aW50YXJlYS1hZHM7IGlldGY7IGludGFyZWEtY2hhaXJzDQpTdWJqZWN0OiBSZTogR29vZ2xlIFN0
YXRpc3RpY3MgZm9yIElQdjYgYWRvcHRpb24uDQoNCg0KDQpPbiBTYXQsIEFwciAxNSwgMjAxNyBh
dCA5OjA5IEFNLCBLaGFsZWQgT21hciA8ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPG1haWx0
bzplbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+PiB3cm90ZToNCkhpIGFsbCwNCg0KUGxlYXNl
IGNoZWNrIG91dCB0aGlzIGxpbmsgdGhhdCBzaG93cyB0aGUgc3RhdGlzdGljcyBvZiB0aGUgSVB2
NiBhZG9wdGlvbiBvdmVyIHRoZSBwYXN0IDEwIHllYXJzIG1heWJlIGl0IHdpbGwgbWFrZSB5b3Ug
YmVsaWV2ZSB3aGF0IHdhcyBzYWlkIGVhcmxpZXIuDQoNCid3aGF0IHdhcyBzYWlkIGVhcmxpZXIn
IC0gY2l0YXRpb24gcmVxdWVzdGVkLg0KDQoNCiBodHRwczovL3d3dy5nb29nbGUuY29tL2ludGwv
ZW4vaXB2Ni9zdGF0aXN0aWNzLmh0bWwNCg0KUmVjZW50IElQdjYgYWRvcHRpb24gKEFwcmlsLCAy
MDE3KSBpczoNCjE0LjgzJSBOYXRpdmUgLSAwLjAzJSA2dG80IC0gMTQuODclIFRvdGFsDQoNCkJl
c3QgcmVnYXJkcywNCg0KS2hhbGVkIE9tYXINCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw
YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlzdFBhcmFncmFw
aCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxl
LXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbWFy
Z2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAx
cHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwi
c2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJl
cGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3
RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtz
aXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2
LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0i
MTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEi
IC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBs
YW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3Jk
U2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIENocmlzdG9waGVyLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jmd0Ow0KPC9zcGFu
Pid3aGF0IHdhcyBzYWlkIGVhcmxpZXInIC0gY2l0YXRpb24gcmVxdWVzdGVkLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5XaGF0IEkgc2FpZCBtZWFucyB0aGF0IHNpbmNlIEkgd3JvdGUgdGhlIElQ
djEwIEktRCBvbiBHb29nbGUgYmxvZ2dlciwgSSB3cm90ZSB0aGF0IHRoZSBkZXBsb3ltZW50IG9m
IElQdjYgaXMgYWJvdXQgNSUgb2YgdGhlIEludGVybmV0IHRyYWZmaWMsIGFuZCBJIGdvdCByZXNw
b25zZXMgZnJvbSBzb21lIElFVEYgbWVtYmVycyBKdXN0IGNsYWltaW5nIHRoYXQgdGhpcyBpcyBh
IHdyb25nIHBlcmNlbnRhZ2UgYW5kDQogdGhlIHJlYWwgZXhjZWVkcyA2MCUgYW5kIGdhdmUgbWUg
c29tZSBleGFtcGxlcyBvZiBtb2JpbGUgcHJvdmlkZXJz4oCZIHN0YXRpc3RpY3MuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlNvLCB0aGlzIEdvb2dsZSBzdGF0aXN0aWNzIGNvbmZpcm1zIHdoYXQg
SSBoYWQgc2FpZCBlYXJsaWVyIGJlY2F1c2UgSSBnb3QgdGhpcyBwZXJjZW50IGZyb20gc29tZSBv
bmxpbmUgc3RhdGlzdGljcyB0aGF0IGJlbG9uZ3MgdG8gdGhlIElQIGFkZHJlc3MgYXNzaWdubWVu
dCBwcm9jZXNzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHdvdWxkIGxpa2UgdG8gdGhhbmsg
R29vZ2xlIGZvciB0aGUgZWZmb3J0cyBtYWRlIHRvIG1ha2UgdGhpcyBtZWFzdXJlbWVudHMgYW5k
IHByb3ZpZGUgYSByZXNwZWN0ZnVsIGFuZCByZWFsIHN0YXRpc3RpY3MgdGhhdCBkZXNjcmliZXMg
dGhlIHJlY2VudCBzaXR1YXRpb24gc28gd2UgY2FuIG1ha2UgZGVjaXNpb25zIGJhc2VkIG9uIGl0
LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPktoYWxlZCBPbWFyIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBjaHJpc3RvcGhlci5tb3Jyb3dA
Z21haWwuY29tIFttYWlsdG86Y2hyaXN0b3BoZXIubW9ycm93QGdtYWlsLmNvbV0NCjxiPk9uIEJl
aGFsZiBPZiA8L2I+Q2hyaXN0b3BoZXIgTW9ycm93PGJyPg0KPGI+U2VudDo8L2I+IFNhdHVyZGF5
LCBBcHJpbCAxNSwgMjAxNyA3OjE2IFBNPGJyPg0KPGI+VG86PC9iPiBLaGFsZWQgT21hcjxicj4N
CjxiPkNjOjwvYj4gaW50LWFyZWE7IGludGFyZWEtYWRzOyBpZXRmOyBpbnRhcmVhLWNoYWlyczxi
cj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogR29vZ2xlIFN0YXRpc3RpY3MgZm9yIElQdjYgYWRvcHRp
b24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gU2F0LCBBcHIgMTUsIDIwMTcgYXQgOTow
OSBBTSwgS2hhbGVkIE9tYXIgJmx0OzxhIGhyZWY9Im1haWx0bzplbmcua2hhbGVkLm9tYXJAaG90
bWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5lbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb208L2E+
Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IaSBhbGwsPGJyPg0KPGJyPg0KUGxlYXNlIGNoZWNrIG91dCB0aGlzIGxpbmsgdGhhdCBz
aG93cyB0aGUgc3RhdGlzdGljcyBvZiB0aGUgSVB2NiBhZG9wdGlvbiBvdmVyIHRoZSBwYXN0IDEw
IHllYXJzIG1heWJlIGl0IHdpbGwgbWFrZSB5b3UgYmVsaWV2ZSB3aGF0IHdhcyBzYWlkIGVhcmxp
ZXIuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj4nd2hhdCB3YXMgc2FpZCBlYXJsaWVyJyAtIGNpdGF0aW9uIHJlcXVlc3RlZC48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21h
cmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGJyPg0KJm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS9pbnRsL2VuL2lwdjYv
c3RhdGlzdGljcy5odG1sIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS9p
bnRsL2VuL2lwdjYvc3RhdGlzdGljcy5odG1sPC9hPjxicj4NCjxicj4NClJlY2VudCBJUHY2IGFk
b3B0aW9uIChBcHJpbCwgMjAxNykgaXM6PGJyPg0KMTQuODMlIE5hdGl2ZSAtIDAuMDMlIDZ0bzQg
LSAxNC44NyUgVG90YWw8YnI+DQo8YnI+DQpCZXN0IHJlZ2FyZHMsPGJyPg0KPGJyPg0KS2hhbGVk
IE9tYXI8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM4PR0401MB2241F94B536F114D83190A14BD040AM4PR0401MB2241_--


From nobody Sat Apr 15 11:47:34 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9535E129456; Sat, 15 Apr 2017 11:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 brEdt9ahyWLb; Sat, 15 Apr 2017 11:47:23 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 82D2B12783A; Sat, 15 Apr 2017 11:47:23 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:393d:652c:6409:ddf8] (unknown [IPv6:2603:3015:3603:8e00:393d:652c:6409:ddf8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 4D0AF5408BA; Sat, 15 Apr 2017 14:47:21 -0400 (EDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-6FED0A38-EFE2-47DC-8A24-3ED36D34AE2B
Mime-Version: 1.0 (1.0)
Subject: Re: Google Statistics for IPv6 adoption.
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <AM4PR0401MB2241F94B536F114D83190A14BD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Date: Sat, 15 Apr 2017 14:47:20 -0400
Cc: Christopher Morrow <morrowc.lists@gmail.com>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <40315FF7-DD5D-4A3D-BCA5-C6D4C17CE8A9@puck.nether.net>
References: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com> <CAL9jLaa+zTSj9g1QMQAEPDiVqEmGG3OtChuu5NvA3feTX2mrjw@mail.gmail.com> <AM4PR0401MB2241F94B536F114D83190A14BD040@AM4PR0401MB2241.eurprd04.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a4DdVmx6ck0Df_zCKJTQ5GkyIBU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 18:47:26 -0000

--Apple-Mail-6FED0A38-EFE2-47DC-8A24-3ED36D34AE2B
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

There is not a correlation between this graph and traffic the way you purpor=
t hence the [missing citation] aspect of the discussion. An enterprise actua=
lly moves less traffic than a consumer on a per user basis, so if a home is I=
Pv6 enabled and runs a lot of YouTube, Netflix, etc the bits per IP are not e=
qual.=20

Enterprise, eyeball and wholesale networks have vastly different traffic cha=
racteristics. If you use the Alexa top 1000 or 1 million you see many IPv6 e=
nabled sites as they are hosted on cloudflare which dual stacks by default v=
s other CDNs that don't.=20

Using one datapoint, an ad network (google) is helpful to understand what br=
owser users might look like but a set top box without a browser may move sig=
nificantly more bits and not be apparent at all in the IPv6 stats at google.=
=20

Hope this helps.=20

Jared Mauch

> On Apr 15, 2017, at 1:52 PM, Khaled Omar <eng.khaled.omar@hotmail.com> wro=
te:
>=20
> Hi Christopher,
> =20
> > 'what was said earlier' - citation requested.
> =20
> What I said means that since I wrote the IPv10 I-D on Google blogger, I wr=
ote that the deployment of IPv6 is about 5% of the Internet traffic, and I g=
ot responses from some IETF members Just claiming that this is a wrong perce=
ntage and the real exceeds 60% and gave me some examples of mobile providers=
=E2=80=99 statistics.
> =20
> So, this Google statistics confirms what I had said earlier because I got t=
his percent from some online statistics that belongs to the IP address assig=
nment process.
> =20
> I would like to thank Google for the efforts made to make this measurement=
s and provide a respectful and real statistics that describes the recent sit=
uation so we can make decisions based on it.
> =20
> Best Regards,
> =20
> Khaled Omar
> =20
> =20
> From: christopher.morrow@gmail.com [mailto:christopher.morrow@gmail.com] O=
n Behalf Of Christopher Morrow
> Sent: Saturday, April 15, 2017 7:16 PM
> To: Khaled Omar
> Cc: int-area; intarea-ads; ietf; intarea-chairs
> Subject: Re: Google Statistics for IPv6 adoption.
> =20
> =20
> =20
> On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar <eng.khaled.omar@hotmail.com>=
 wrote:
> Hi all,
>=20
> Please check out this link that shows the statistics of the IPv6 adoption o=
ver the past 10 years maybe it will make you believe what was said earlier.
> =20
> 'what was said earlier' - citation requested.
> =20
>=20
>  https://www.google.com/intl/en/ipv6/statistics.html
>=20
> Recent IPv6 adoption (April, 2017) is:
> 14.83% Native - 0.03% 6to4 - 14.87% Total
>=20
> Best regards,
>=20
> Khaled Omar
> =20

--Apple-Mail-6FED0A38-EFE2-47DC-8A24-3ED36D34AE2B
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>There is not a correlation between thi=
s graph and traffic the way you purport hence the [missing citation] aspect o=
f the discussion. An enterprise actually moves less traffic than a consumer o=
n a per user basis, so if a home is IPv6 enabled and runs a lot of YouTube, N=
etflix, etc the bits per IP are not equal.&nbsp;</div><div id=3D"AppleMailSi=
gnature"><br></div><div id=3D"AppleMailSignature">Enterprise, eyeball and wh=
olesale networks have vastly different traffic characteristics. If you use t=
he Alexa top 1000 or 1 million you see many IPv6 enabled sites as they are h=
osted on cloudflare which dual stacks by default vs other CDNs that don't.&n=
bsp;</div><div id=3D"AppleMailSignature"><br></div><div id=3D"AppleMailSigna=
ture">Using one datapoint, an ad network (google) is helpful to understand w=
hat browser users might look like but a set top box without a browser may mo=
ve significantly more bits and not be apparent at all in the IPv6 stats at g=
oogle.&nbsp;</div><div id=3D"AppleMailSignature"><br></div><div id=3D"AppleM=
ailSignature">Hope this helps.&nbsp;<br><br>Jared Mauch</div><div><br>On Apr=
 15, 2017, at 1:52 PM, Khaled Omar &lt;<a href=3D"mailto:eng.khaled.omar@hot=
mail.com">eng.khaled.omar@hotmail.com</a>&gt; wrote:<br><br></div><blockquot=
e type=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" 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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Christopher,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;
</span>'what was said earlier' - citation requested.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">What I said means that since I wrote the IPv10 I-D on=
 Google blogger, I wrote that the deployment of IPv6 is about 5% of the Inte=
rnet traffic, and I got responses from some IETF members Just claiming that t=
his is a wrong percentage and
 the real exceeds 60% and gave me some examples of mobile providers=E2=80=99=
 statistics.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, this Google statistics confirms what I had said e=
arlier because I got this percent from some online statistics that belongs t=
o the IP address assignment process.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would like to thank Google for the efforts made to m=
ake this measurements and provide a respectful and real statistics that desc=
ribes the recent situation so we can make decisions based on it.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled Omar <o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> <a href=3D=
"mailto:christopher.morrow@gmail.com">christopher.morrow@gmail.com</a> [<a h=
ref=3D"mailto:christopher.morrow@gmail.com">mailto:christopher.morrow@gmail.=
com</a>]
<b>On Behalf Of </b>Christopher Morrow<br>
<b>Sent:</b> Saturday, April 15, 2017 7:16 PM<br>
<b>To:</b> Khaled Omar<br>
<b>Cc:</b> int-area; intarea-ads; ietf; intarea-chairs<br>
<b>Subject:</b> Re: Google Statistics for IPv6 adoption.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar &lt;<a h=
ref=3D"mailto:eng.khaled.omar@hotmail.com" target=3D"_blank">eng.khaled.omar=
@hotmail.com</a>&gt; wrote:<o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0in=
 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">Hi all,<br>
<br>
Please check out this link that shows the statistics of the IPv6 adoption ov=
er the past 10 years maybe it will make you believe what was said earlier.<o=
:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">'what was said earlier' - citation requested.<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0in=
 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal"><br>
&nbsp;<a href=3D"https://www.google.com/intl/en/ipv6/statistics.html" target=
=3D"_blank">https://www.google.com/intl/en/ipv6/statistics.html</a><br>
<br>
Recent IPv6 adoption (April, 2017) is:<br>
14.83% Native - 0.03% 6to4 - 14.87% Total<br>
<br>
Best regards,<br>
<br>
Khaled Omar<o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>


</div></blockquote></body></html>=

--Apple-Mail-6FED0A38-EFE2-47DC-8A24-3ED36D34AE2B--


From nobody Sat Apr 15 13:54:17 2017
Return-Path: <prvs=12782475d1=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C777612946C for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 13:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9JwctbPZQ1jv for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 13:54:13 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9190D127444 for <ietf@ietf.org>; Sat, 15 Apr 2017 13:54:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492289651; x=1492894451; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: Mime-version:Content-type:Content-transfer-encoding:Reply-To; bh=Anj68qevhdi7OeFJYX5YIXFH7ZXK7g5eMtjHfwKnviA=; b=b8Qrm4E6qOqbE 3grtJyNdqwgVxDMASci3/khYCX/zx64gip0wd72oKyXcANO7/ga5IJ+5wrEFJqOA YgpppfxvF54Hzy8sQelmTBPZiygQMnkrLuRr9dV+QMAYR7Aftbd1EDMvQNb/qfZ9 4WOTOEogo3TJ6Q2scd1wHWsBiHQM+s=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=KBuBCWNYoS/2qsWz/TtEy7HvfwyYFpejeVVJWxv20205EzsRFYrGWOeWWG4a w/btIXG9XM4y2bIrMITUb+M5S9PQIRY/sBuvV2EqArVGLC6MRngcLrW31 Da37rT+iCf3BP2QQyJOn1iiziQ5PjNMavDlyGv0+pLR6GGt09VbM7I=;
X-MDAV-Processed: mail.consulintel.es, Sat, 15 Apr 2017 22:54:11 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 15 Apr 2017 22:54:10 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005409061.msg for <ietf@ietf.org>; Sat, 15 Apr 2017 22:54:10 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170415:md50005409061::E/udKB8bE4J9QkNy:000017O5
X-Return-Path: prvs=12782475d1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Sat, 15 Apr 2017 22:54:09 +0200
Subject: Re: Update on feedback on US-based meetings, and IETF 102
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es>
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XHat-Zp1s4usDeCoXD1xyoH0IS8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 20:54:16 -0000

Hi all,

I=E2=80=99ve been pointed out in a private message that the last part of my=
 sentence in the message below, could be interpreted as a disparage of the =
education of individuals in the IAOC.

I just want to apologize if somebody understood that, as it was clearly not=
 my intend. The mistake comes from the way we are used to say =E2=80=9Cfalt=
a de educaci=C3=B3n=E2=80=9D or =E2=80=9Cmaleducado=E2=80=9D in Spanish whe=
n somebody should have done something that he promised and didn=E2=80=99t t=
hat, as it is the case, and instead I should have used =E2=80=9Cimpolite=E2=
=80=9D.

This shows something that I believe most of the native English IETF partici=
pants usually don=E2=80=99t realize when having discussion (I=E2=80=99m ref=
erring here in general, also technical discussions) with non-native speaker=
s, and how difficult is for the others. Maybe we should switch to Chinese a=
s the default IETF language, or Spanish, as they have more speakers worldwi=
de than English!

I=E2=80=99m still believe that IAOC attitude is not justified at all, and i=
f we don=E2=80=99t have answers from them by next Monday, we should conside=
r a recall process. Hopefully is not the case.

Regards,
Jordi

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MARTINEZ <jordi.=
palet@consulintel.es>;
Responder a: < jordi.palet@consulintel.es>;
Fecha: viernes, 14 de abril de 2017, 01:24
Para: <ietf@ietf.org>;
Asunto: Re: Update on feedback on US-based meetings, and IETF 102

Well, for some countries what Trump said, has already been a fact, for exam=
ple the prohibition to have computers on board. Is not that the case?

Whatever we want to decide, cancel SF or not, it may highly depend on budge=
t, we like it or not. And that means that we need answers:

    If we cancel San Francisco, how much that is going to cost to the IETF =
for each of two planned meetings?
   =20
    Can we cancel the actual hotel contract considering the new US situatio=
n? If not, has this been considered for new contracts to avoid this problem=
?
   =20
    Otherwise there is any reason that can justify the lack of transparency=
 in this?

The problem is so big for this community that I don=E2=80=99t even agree th=
at the IAOC should take the decision. It must be a collective one, especial=
ly when the IAOC is demonstrating thru facts that they don=E2=80=99t care t=
hat we are discussing and wasting our time without the minimum relevant dat=
a, this is disrespectful and even more, not responding to emails since even=
 since years ago, shows lack of education=20

Regards,
Jordi




**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sat Apr 15 14:21:03 2017
Return-Path: <prvs=12782475d1=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F01A812948F for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 14:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJFPZA_a14yz for <ietf@ietfa.amsl.com>; Sat, 15 Apr 2017 14:20:59 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264BF126B6D for <ietf@ietf.org>; Sat, 15 Apr 2017 14:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492291257; x=1492896057; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: Mime-version:Content-type:Content-transfer-encoding:Reply-To; bh=x9Egf1tnb1kKi+VbgdT+7LcfHwtzJgS8gz9btyTJZvs=; b=AyOwzuoGsT06w Imx7MD1gI5hbxF4FvXtioo2IqlgKsDm/F4eRpDyB0mbW3EReOvt5JUzj/r6ADLfy IgjVmOpJZx0d6v0wqFOjnbrQE0rj/ogbJZDOp1NcZLy5gbKJaUki37l6AQufJBMo ngqn2vX8RtyhYKQN+QOdxS3TIPYE+Y=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=UcutvCMUaCPq0jBt3HVgJHYQq+Jo8IHXaKfRX6lx27dboVE7vzZaxl5cLWLw YflVFUgI5gRMyCCdY4hJpkGQyUdFfX2QOC21S04h8uYXJuH62y96123Sz 9m5jqZJqI3yTYSMWoRfiOYcV2Sq89VbixyD3lSzWD7mOyVb4vIRTcw=;
X-MDAV-Processed: mail.consulintel.es, Sat, 15 Apr 2017 23:20:57 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 15 Apr 2017 23:20:56 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005409066.msg for <ietf@ietf.org>; Sat, 15 Apr 2017 23:20:56 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170415:md50005409066::NJH6cVqKFgjm6D0Q:000014MZ
X-Return-Path: prvs=12782475d1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Sat, 15 Apr 2017 23:20:56 +0200
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Message-ID: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es>
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zEY5vCbTh53wHN6DkVrajmFuWTk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 21:21:01 -0000

Stats are always a reference, but if you look only to a single data set, yo=
u will have a broken view.

Look at the data of the mobile operators in many countries, that only deliv=
er IPv6 connectivity, such as US, India, few EU countries, now Japan, or ev=
en wireline providers in every continent of the world, that have IPv6 penet=
ration figures much higher than what Google average is showing.

For those that work every day deploying IPv6 since many years ago, we have =
seen a trend change, the light at the end of the tunnel, already a few year=
s ago.

Regards,
Jordi
=20

-----Mensaje original-----
De: Int-area <int-area-bounces@ietf.org> en nombre de Khaled Omar <eng.khal=
ed.omar@hotmail.com>
Responder a: <eng.khaled.omar@hotmail.com>
Fecha: s=C3=A1bado, 15 de abril de 2017, 19:52
Para: Christopher Morrow <morrowc.lists@gmail.com>
CC: "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int=
-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org"=
 <intarea-chairs@ietf.org>
Asunto: Re: [Int-area] Google Statistics for IPv6 adoption.

    Hi Christopher,
    =20
    >
    'what was said earlier' - citation requested.
    =20
    What I said means that since I wrote the IPv10 I-D on Google blogger, I=
 wrote that the deployment of IPv6 is about 5% of the Internet traffic, and=
 I got responses from some IETF members Just claiming that this is a wrong =
percentage and
     the real exceeds 60% and gave me some examples of mobile providers=E2=
=80=99 statistics.
    =20
    So, this Google statistics confirms what I had said earlier because I g=
ot this percent from some online statistics that belongs to the IP address =
assignment process.
    =20
    I would like to thank Google for the efforts made to make this measurem=
ents and provide a respectful and real statistics that describes the recent=
 situation so we can make decisions based on it.
    =20
    Best Regards,
    =20
    Khaled Omar=20
    =20
    =20
    From: christopher.morrow@gmail.com [mailto:christopher.morrow@gmail.com=
]
    On Behalf Of Christopher Morrow
    Sent: Saturday, April 15, 2017 7:16 PM
    To: Khaled Omar
    Cc: int-area; intarea-ads; ietf; intarea-chairs
    Subject: Re: Google Statistics for IPv6 adoption.
    =20
    =20
    =20
    On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar <eng.khaled.omar@hotmail.c=
om> wrote:
   =20
    Hi all,
   =20
    Please check out this link that shows the statistics of the IPv6 adopti=
on over the past 10 years maybe it will make you believe what was said earl=
ier.
   =20
   =20
    =20
   =20
    'what was said earlier' - citation requested.
   =20
    =20
   =20
   =20
   =20
     https://www.google.com/intl/en/ipv6/statistics.html
   =20
    Recent IPv6 adoption (April, 2017) is:
    14.83% Native - 0.03% 6to4 - 14.87% Total
   =20
    Best regards,
   =20
    Khaled Omar
   =20
   =20
   =20
    =20
   =20
   =20
   =20
   =20
   =20
    _______________________________________________
    Int-area mailing list
    Int-area@ietf.org
    https://www.ietf.org/mailman/listinfo/int-area
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sat Apr 15 18:31:18 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19CEF1292D3; Sat, 15 Apr 2017 18:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 We-RDQ8ZoN3Q; Sat, 15 Apr 2017 18:31:07 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065073.outbound.protection.outlook.com [40.92.65.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3AE126579; Sat, 15 Apr 2017 18:31:07 -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; bh=EuOFD2OEJmsrsM66IKsNfPUnBJ4eoA1dZcShCsrcHcc=; b=fh7Ehmjqqm7a8rHWvE7ESyvmqHjdrC7GtcouEBEhPzNbZdGGBI1P7H622ykDTIUda74RwIagdZy4uPIhQL1v5a7Ex1HbjjBNbz9ANqc1M4u/Wv3nEbGBFvpQLZSMsdYde3q7jz1JPc0EYqXFAGZ7jsqx62A0VBS5W6PSGNpF9ZY3kw+WxhBPTMDrEc0tEMlhCuJOPg2tvynAOg0Q2wkPs7+HH21uOkuOgR3i5YKmTNfqrOYckVkMKJdPZbGWzw1e5AcOR6j+vIN+JMH3cNq/FH9V3MR2jxopQ02DSpJ+PLCTxYilQNeddTZmTc74xwtrPx5/lZIvaVNPeOvCefLL+A==
Received: from HE1EUR01FT005.eop-EUR01.prod.protection.outlook.com (10.152.0.59) by HE1EUR01HT069.eop-EUR01.prod.protection.outlook.com (10.152.1.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Sun, 16 Apr 2017 01:31:04 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.0.52) by HE1EUR01FT005.mail.protection.outlook.com (10.152.1.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Sun, 16 Apr 2017 01:31:04 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1034.013; Sun, 16 Apr 2017 01:31:04 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Subject: RE: [Int-area] Google Statistics for IPv6 adoption.
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
Thread-Index: AQHSti47/uaUGNjULEOCU6EGG8PHPKHHMY2w
Date: Sun, 16 Apr 2017 01:31:03 +0000
Message-ID: <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es>
In-Reply-To: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: consulintel.es; dkim=none (message not signed) header.d=none; consulintel.es; dmarc=none action=none header.from=hotmail.com; 
x-incomingtopheadermarker: OriginalChecksum:C0F215908BE8B5C56269E4A52495D9B3326B0F6BA6F5374A0252CE77F5CD90EF; UpperCasedChecksum:A4C0D9C5D2FFB840E31F19C84FC6EBCF3A5DF52330D471E6B3734BD2309C85B2; SizeAsReceived:8230; Count:42
x-tmn: [wT48Fy/aVXCVUrlCR8Cj9t1hSjuOv75l]
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT069; 5:HwTFZYOpFDreqMOyGZYCVXO7YtAwHZU9+ZQufNdrrjqBLz6V9/RsbaJ/3hgEdxgNrhGAYBKB/MXgq7GQdhi74+WhBmLWTaNYTwMO+ayv8+NNeI7WtmdYI1c0ALK5R4zpwDOn+2ytlBiOi8c+4/qpww==; 24:1XgGwdeqJVegvBhvrFg8VKwhveqo/R8TpNxjpcLLs0sP/zhlhcWl7b8mhAX13YD34RcbgeFL/0FsKE9DczStcQEoLgVDlTp9sXmOs2lzWKE=; 7:CpkzxLbb8+lE0rlykbo87D5kOj5l8CRFoYgZnjYvRRNXBt2twZWt7OxZevTAf+YJba7SbxctUE1rlivNM+TmDX13NIdvjkdNtJXW/G3BRi7qNO+2JjhMGdb5Smc1qPRisEQexLZ38D19P9v372AgiQN49Ad4v7Wdexk+0OW0v7PoTTB7n0ITrYuvAFb8iBesap7fkMcBrSqZVRNeuHoXw0MkNyXlKHRHr47AUBouqhf0KzfJKNGt6iuUiRlET7BPJ38qDUFSAXPTttwfM/vZjXcm7kpkGrJUwdip3n6cIv7TFgTOHby6Wg00E2ZhdE7m
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT069; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: a590cf80-2a06-4663-0f66-08d484683f6a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR01HT069; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT069; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT069; 
x-forefront-prvs: 0279B3DD0D
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2017 01:31:04.0592 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT069
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pJnFaq-QttY0xKp8vEkemHZenoc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 01:31:09 -0000

SGkgSm9yZGksDQoNCkludGVybmV0IGlzIGEgZ2xvYmFsIG5ldHdvcmsgdGhhdCBjb3ZlcnMgdGhl
IHdob2xlIHdvcmxkIChvZiBjb3Vyc2UgaXQgaXMga25vd24gYnkgYWxsKSwgYSBzaW5nbGUgaG9z
dCB0aGF0IHJlc2lkZXMgaW4gb25lIHJlZ2lvbiBzaG91bGQgYWNjZXNzIHJlc291cmNlcyBldmVy
eXdoZXJlLCBpdCB3aWxsIGJlIGEgc2hhbWUgd2hlbiB0aGlzIG9uZSBob3N0IGNhbiBhY2Nlc3Mg
b25seSByZXNvdXJjZXMgZnJvbSB0aGUgc2FtZSBJUCB2ZXJzaW9uIHRoYXQgaGUgdXNlcy4NCg0K
SXQgaXMgZ29vZCB0aGF0IElQdjYgaXMgZGVwbG95ZWQgb24gdGhlIG1vc3Qgd2VsbC1rbm93biB3
ZWJzaXRlcyAoc3VjaCBhcyBHb29nbGUsIEZhY2Vib29rLCBldGMuKSBidXQgdGhhdCBkb2Vzbid0
IG1lYW4gdGhhdCB0aGUgSW50ZXJuZXQgaXMgb25seSB3ZWJzaXRlcywgdGhlcmUgYXJlIG1hbnkg
b3RoZXIgcmVzb3VyY2VzIChzZXJ2aWNlcyksIGV2ZW50dWFsbHkgYWxsIG11c3QgYmUgYXNzaWdu
ZWQgYW4gSVAgYWRkcmVzcy4NCg0KVGhlIGNhc2UgaXMgdG8gYWxsb3cgSVB2NCBvbmx5IGhvc3Rz
IHRvIGNvbW11bmljYXRlIHdpdGggSVB2NiBvbmx5IGhvc3RzIChmb3IgNi10by02IGFuZCA0LXRv
LTQgaXMgbm90IHRoZSBwcm9ibGVtKSwgc28gZGVwbG95aW5nIGEgc29sdXRpb24gZm9yIHRoYXQg
ZGl2aXNpb24gcHJvYmxlbSBzaG91bGQgYmUgaW50cm9kdWNlZCBBU0FQIG9yIHRoZSBJbnRlcm5l
dCB3aWxsIGhhdmUgYSBiYWQgcmVwdXRhdGlvbiBkdWUgdG8gdGhlIHNlcGFyYXRpb24gYmV0d2Vl
biBob3N0cy4NCg0KVGhlIElFVEYgc2hvdWxkIHRha2UgdGhhdCByZXNwb25zaWJpbGl0eSBvdmVy
IHRoZSBzaG91bGRlciwgYmVjYXVzZSB0aGluayBhYm91dCB0aG9zZSB3aXRoIElQdjYgb25seSBh
ZGRyZXNzLCB0aGV5IGNhbiBhY2Nlc3Mgb25seSAxNSUgb2YgdGhlIEludGVybmV0LCB3aWxsIHRo
ZXkgaGF2ZSB0byB3YWl0IHNvbWUgb3RoZXIgeWVhcnMgdG8gYmUgYWJsZSB0byBhY2Nlc3MgZXZl
cnl0aGluZyBvbiB0aGUgSW50ZXJuZXQsIEkgZG9uJ3QgdGhpbmsgdGhleSBzaG91bGQgZG8gdGhh
dC4NCg0KQW55d2F5LCBJIHRoaW5rIHRoZSBzb2x1dGlvbiBpcyBvbiB5b3VyIGhhbmRzIG5vdywg
dGhlIGRlY2lzaW9uIHRvIHB1Ymxpc2ggaXQgaXMgbm90IG15IHJlc3BvbnNpYmlsaXR5LCBidXQg
SSdtIHN1cmUgYSBzb2x1dGlvbiB3aWxsIGJlIGZvdW5kIGZvciB0aGlzIHByb2JsZW0gcmVnYXJk
bGVzcyBpdCB3aWxsIGJlIElQdjEwIG9yIHNvbWV0aGluZyBlbHNlLg0KDQpCZXN0IFJlZ2FyZHMs
DQoNCktoYWxlZCBPbWFyDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRm
IFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSk9SREkgUEFMRVQg
TUFSVElORVoNClNlbnQ6IFNhdHVyZGF5LCBBcHJpbCAxNSwgMjAxNyAxMToyMSBQTQ0KVG86IGlu
dGFyZWEtYWRzQGlldGYub3JnOyBpbnQtYXJlYUBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgaW50
YXJlYS1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbSW50LWFyZWFdIEdvb2dsZSBTdGF0
aXN0aWNzIGZvciBJUHY2IGFkb3B0aW9uLg0KDQpTdGF0cyBhcmUgYWx3YXlzIGEgcmVmZXJlbmNl
LCBidXQgaWYgeW91IGxvb2sgb25seSB0byBhIHNpbmdsZSBkYXRhIHNldCwgeW91IHdpbGwgaGF2
ZSBhIGJyb2tlbiB2aWV3Lg0KDQpMb29rIGF0IHRoZSBkYXRhIG9mIHRoZSBtb2JpbGUgb3BlcmF0
b3JzIGluIG1hbnkgY291bnRyaWVzLCB0aGF0IG9ubHkgZGVsaXZlciBJUHY2IGNvbm5lY3Rpdml0
eSwgc3VjaCBhcyBVUywgSW5kaWEsIGZldyBFVSBjb3VudHJpZXMsIG5vdyBKYXBhbiwgb3IgZXZl
biB3aXJlbGluZSBwcm92aWRlcnMgaW4gZXZlcnkgY29udGluZW50IG9mIHRoZSB3b3JsZCwgdGhh
dCBoYXZlIElQdjYgcGVuZXRyYXRpb24gZmlndXJlcyBtdWNoIGhpZ2hlciB0aGFuIHdoYXQgR29v
Z2xlIGF2ZXJhZ2UgaXMgc2hvd2luZy4NCg0KRm9yIHRob3NlIHRoYXQgd29yayBldmVyeSBkYXkg
ZGVwbG95aW5nIElQdjYgc2luY2UgbWFueSB5ZWFycyBhZ28sIHdlIGhhdmUgc2VlbiBhIHRyZW5k
IGNoYW5nZSwgdGhlIGxpZ2h0IGF0IHRoZSBlbmQgb2YgdGhlIHR1bm5lbCwgYWxyZWFkeSBhIGZl
dyB5ZWFycyBhZ28uDQoNClJlZ2FyZHMsDQpKb3JkaQ0KIA0KDQotLS0tLU1lbnNhamUgb3JpZ2lu
YWwtLS0tLQ0KRGU6IEludC1hcmVhIDxpbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnPiBlbiBub21i
cmUgZGUgS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4gUmVzcG9uZGVy
IGE6IDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+DQpGZWNoYTogc8OhYmFkbywgMTUgZGUg
YWJyaWwgZGUgMjAxNywgMTk6NTINClBhcmE6IENocmlzdG9waGVyIE1vcnJvdyA8bW9ycm93Yy5s
aXN0c0BnbWFpbC5jb20+DQpDQzogImludGFyZWEtYWRzQGlldGYub3JnIiA8aW50YXJlYS1hZHNA
aWV0Zi5vcmc+LCAiaW50LWFyZWFAaWV0Zi5vcmciIDxpbnQtYXJlYUBpZXRmLm9yZz4sICJpZXRm
QGlldGYub3JnIiA8aWV0ZkBpZXRmLm9yZz4sICJpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyIgPGlu
dGFyZWEtY2hhaXJzQGlldGYub3JnPg0KQXN1bnRvOiBSZTogW0ludC1hcmVhXSBHb29nbGUgU3Rh
dGlzdGljcyBmb3IgSVB2NiBhZG9wdGlvbi4NCg0KICAgIEhpIENocmlzdG9waGVyLA0KICAgICAN
CiAgICA+DQogICAgJ3doYXQgd2FzIHNhaWQgZWFybGllcicgLSBjaXRhdGlvbiByZXF1ZXN0ZWQu
DQogICAgIA0KICAgIFdoYXQgSSBzYWlkIG1lYW5zIHRoYXQgc2luY2UgSSB3cm90ZSB0aGUgSVB2
MTAgSS1EIG9uIEdvb2dsZSBibG9nZ2VyLCBJIHdyb3RlIHRoYXQgdGhlIGRlcGxveW1lbnQgb2Yg
SVB2NiBpcyBhYm91dCA1JSBvZiB0aGUgSW50ZXJuZXQgdHJhZmZpYywgYW5kIEkgZ290IHJlc3Bv
bnNlcyBmcm9tIHNvbWUgSUVURiBtZW1iZXJzIEp1c3QgY2xhaW1pbmcgdGhhdCB0aGlzIGlzIGEg
d3JvbmcgcGVyY2VudGFnZSBhbmQNCiAgICAgdGhlIHJlYWwgZXhjZWVkcyA2MCUgYW5kIGdhdmUg
bWUgc29tZSBleGFtcGxlcyBvZiBtb2JpbGUgcHJvdmlkZXJz4oCZIHN0YXRpc3RpY3MuDQogICAg
IA0KICAgIFNvLCB0aGlzIEdvb2dsZSBzdGF0aXN0aWNzIGNvbmZpcm1zIHdoYXQgSSBoYWQgc2Fp
ZCBlYXJsaWVyIGJlY2F1c2UgSSBnb3QgdGhpcyBwZXJjZW50IGZyb20gc29tZSBvbmxpbmUgc3Rh
dGlzdGljcyB0aGF0IGJlbG9uZ3MgdG8gdGhlIElQIGFkZHJlc3MgYXNzaWdubWVudCBwcm9jZXNz
Lg0KICAgICANCiAgICBJIHdvdWxkIGxpa2UgdG8gdGhhbmsgR29vZ2xlIGZvciB0aGUgZWZmb3J0
cyBtYWRlIHRvIG1ha2UgdGhpcyBtZWFzdXJlbWVudHMgYW5kIHByb3ZpZGUgYSByZXNwZWN0ZnVs
IGFuZCByZWFsIHN0YXRpc3RpY3MgdGhhdCBkZXNjcmliZXMgdGhlIHJlY2VudCBzaXR1YXRpb24g
c28gd2UgY2FuIG1ha2UgZGVjaXNpb25zIGJhc2VkIG9uIGl0Lg0KICAgICANCiAgICBCZXN0IFJl
Z2FyZHMsDQogICAgIA0KICAgIEtoYWxlZCBPbWFyIA0KICAgICANCiAgICAgDQogICAgRnJvbTog
Y2hyaXN0b3BoZXIubW9ycm93QGdtYWlsLmNvbSBbbWFpbHRvOmNocmlzdG9waGVyLm1vcnJvd0Bn
bWFpbC5jb21dDQogICAgT24gQmVoYWxmIE9mIENocmlzdG9waGVyIE1vcnJvdw0KICAgIFNlbnQ6
IFNhdHVyZGF5LCBBcHJpbCAxNSwgMjAxNyA3OjE2IFBNDQogICAgVG86IEtoYWxlZCBPbWFyDQog
ICAgQ2M6IGludC1hcmVhOyBpbnRhcmVhLWFkczsgaWV0ZjsgaW50YXJlYS1jaGFpcnMNCiAgICBT
dWJqZWN0OiBSZTogR29vZ2xlIFN0YXRpc3RpY3MgZm9yIElQdjYgYWRvcHRpb24uDQogICAgIA0K
ICAgICANCiAgICAgDQogICAgT24gU2F0LCBBcHIgMTUsIDIwMTcgYXQgOTowOSBBTSwgS2hhbGVk
IE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4gd3JvdGU6DQogICAgDQogICAgSGkg
YWxsLA0KICAgIA0KICAgIFBsZWFzZSBjaGVjayBvdXQgdGhpcyBsaW5rIHRoYXQgc2hvd3MgdGhl
IHN0YXRpc3RpY3Mgb2YgdGhlIElQdjYgYWRvcHRpb24gb3ZlciB0aGUgcGFzdCAxMCB5ZWFycyBt
YXliZSBpdCB3aWxsIG1ha2UgeW91IGJlbGlldmUgd2hhdCB3YXMgc2FpZCBlYXJsaWVyLg0KICAg
IA0KICAgIA0KICAgICANCiAgICANCiAgICAnd2hhdCB3YXMgc2FpZCBlYXJsaWVyJyAtIGNpdGF0
aW9uIHJlcXVlc3RlZC4NCiAgICANCiAgICAgDQogICAgDQogICAgDQogICAgDQogICAgIGh0dHBz
Oi8vd3d3Lmdvb2dsZS5jb20vaW50bC9lbi9pcHY2L3N0YXRpc3RpY3MuaHRtbA0KICAgIA0KICAg
IFJlY2VudCBJUHY2IGFkb3B0aW9uIChBcHJpbCwgMjAxNykgaXM6DQogICAgMTQuODMlIE5hdGl2
ZSAtIDAuMDMlIDZ0bzQgLSAxNC44NyUgVG90YWwNCiAgICANCiAgICBCZXN0IHJlZ2FyZHMsDQog
ICAgDQogICAgS2hhbGVkIE9tYXINCiAgICANCiAgICANCiAgICANCiAgICAgDQogICAgDQogICAg
DQogICAgDQogICAgDQogICAgDQogICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCiAgICBJbnQtYXJlYSBtYWlsaW5nIGxpc3QNCiAgICBJbnQtYXJlYUBp
ZXRmLm9yZw0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaW50LWFy
ZWENCiAgICANCg0KDQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioNCklQdjQgaXMgb3Zlcg0KQXJlIHlvdSByZWFkeSBmb3IgdGhlIG5ldyBJbnRlcm5ldCA/
DQpodHRwOi8vd3d3LmNvbnN1bGludGVsLmVzDQpUaGUgSVB2NiBDb21wYW55DQoNClRoaXMgZWxl
Y3Ryb25pYyBtZXNzYWdlIGNvbnRhaW5zIGluZm9ybWF0aW9uIHdoaWNoIG1heSBiZSBwcml2aWxl
Z2VkIG9yIGNvbmZpZGVudGlhbC4gVGhlIGluZm9ybWF0aW9uIGlzIGludGVuZGVkIHRvIGJlIGZv
ciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsKHMpIG5hbWVkIGFib3ZlLiBJZiB5b3UgYXJlIG5v
dCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGJlIGF3YXJlIHRoYXQgYW55IGRpc2Nsb3N1cmUsIGNv
cHlpbmcsIGRpc3RyaWJ1dGlvbiBvciB1c2Ugb2YgdGhlIGNvbnRlbnRzIG9mIHRoaXMgaW5mb3Jt
YXRpb24sIGluY2x1ZGluZyBhdHRhY2hlZCBmaWxlcywgaXMgcHJvaGliaXRlZC4NCg0KDQoNCg==


From nobody Sun Apr 16 01:32:47 2017
Return-Path: <prvs=12793c0608=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F50127449 for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 01:32: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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QkLeX73dkiWu for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 01:32:37 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0CD127342 for <ietf@ietf.org>; Sun, 16 Apr 2017 01:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492331555; x=1492936355; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=Hx2F6ylKCt2/EM0HF68x4VGMx DskVTnNOF9muYXEwjo=; b=lXbpSHNa26PwCBk7I2rgRln5VO7ZzZSNIYsE/rb7c 1LfdLftKbBX473zVRRF6+929fY+Q4cBE3w6svZw1urpcY/Xo8WW8WP09Yc3Jfw/6 YA/wUgG+VSFNKNnCtXTIijOwzorrlDrTfuqRQy1ySEVYQyIDlus4yF52JRS+vRyd l4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=kO0TPf5HCMTOA9Ep4f6/kLceruC8j1rz6d5LwNl43bg8y27OC8jd/Tp3IoP4 mevZfsLV04TgGs8O/uAt4TpAjGI/5uH+OElsQYb864M3W00d67LpQ4SdB EaQ/I8sqOiRM1IWNoh6O1VTEdaWkyQd0SrP/MVK2bwj8NOb8P77mvE=;
X-MDAV-Processed: mail.consulintel.es, Sun, 16 Apr 2017 10:32:35 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 16 Apr 2017 10:32:34 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005409172.msg for <ietf@ietf.org>; Sun, 16 Apr 2017 10:32:33 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170416:md50005409172::a6HlNQQum7IuhfWz:00001VR2
X-Return-Path: prvs=12793c0608=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Sun, 16 Apr 2017 10:32:30 +0200
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Message-ID: <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es>
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LlgnYMwOox1st7AlfjtH7hagrvw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 08:32:40 -0000

And actually, in general, nobody complains that any hosts in IPv4 is not ab=
le to access resources at IPv6 hosts. This is why we have the transition me=
chanism, that are being deployed in parallel to the IPv6 deployment.

Nobody is so crazy to just deploy IPv6 and do not provide those transition =
mechanisms.

If that happens, clearly is the fault of somebody that doesn=E2=80=99t know=
 how to do his job. This can happen exactly the same if your protocol becom=
es approved and some folks don=E2=80=99t update their hosts or routers to c=
omply with your protocol, right?

Saludos,
Jordi
=20

-----Mensaje original-----
De: Khaled Omar <eng.khaled.omar@hotmail.com>
Responder a: <eng.khaled.omar@hotmail.com>
Fecha: domingo, 16 de abril de 2017, 3:31
Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>, "int-area@ietf.org" <int-area@ietf.org=
>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org"=
 <intarea-chairs@ietf.org>
Asunto: RE: [Int-area] Google Statistics for IPv6 adoption.

    Hi Jordi,
   =20
    Internet is a global network that covers the whole world (of course it =
is known by all), a single host that resides in one region should access re=
sources everywhere, it will be a shame when this one host can access only r=
esources from the same IP version that he uses.
   =20
    It is good that IPv6 is deployed on the most well-known websites (such =
as Google, Facebook, etc.) but that doesn't mean that the Internet is only =
websites, there are many other resources (services), eventually all must be=
 assigned an IP address.
   =20
    The case is to allow IPv4 only hosts to communicate with IPv6 only host=
s (for 6-to-6 and 4-to-4 is not the problem), so deploying a solution for t=
hat division problem should be introduced ASAP or the Internet will have a =
bad reputation due to the separation between hosts.
   =20
    The IETF should take that responsibility over the shoulder, because thi=
nk about those with IPv6 only address, they can access only 15% of the Inte=
rnet, will they have to wait some other years to be able to access everythi=
ng on the Internet, I don't think they should do that.
   =20
    Anyway, I think the solution is on your hands now, the decision to publ=
ish it is not my responsibility, but I'm sure a solution will be found for =
this problem regardless it will be IPv10 or something else.
   =20
    Best Regards,
   =20
    Khaled Omar
   =20
    -----Original Message-----
    From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of JORDI PALET MART=
INEZ
    Sent: Saturday, April 15, 2017 11:21 PM
    To: intarea-ads@ietf.org; int-area@ietf.org; ietf@ietf.org; intarea-cha=
irs@ietf.org
    Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
   =20
    Stats are always a reference, but if you look only to a single data set=
, you will have a broken view.
   =20
    Look at the data of the mobile operators in many countries, that only d=
eliver IPv6 connectivity, such as US, India, few EU countries, now Japan, o=
r even wireline providers in every continent of the world, that have IPv6 p=
enetration figures much higher than what Google average is showing.
   =20
    For those that work every day deploying IPv6 since many years ago, we h=
ave seen a trend change, the light at the end of the tunnel, already a few =
years ago.
   =20
    Regards,
    Jordi
    =20
   =20
    -----Mensaje original-----
    De: Int-area <int-area-bounces@ietf.org> en nombre de Khaled Omar <eng.=
khaled.omar@hotmail.com> Responder a: <eng.khaled.omar@hotmail.com>
    Fecha: s=C3=A1bado, 15 de abril de 2017, 19:52
    Para: Christopher Morrow <morrowc.lists@gmail.com>
    CC: "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" =
<int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.=
org" <intarea-chairs@ietf.org>
    Asunto: Re: [Int-area] Google Statistics for IPv6 adoption.
   =20
        Hi Christopher,
        =20
        >
        'what was said earlier' - citation requested.
        =20
        What I said means that since I wrote the IPv10 I-D on Google blogge=
r, I wrote that the deployment of IPv6 is about 5% of the Internet traffic,=
 and I got responses from some IETF members Just claiming that this is a wr=
ong percentage and
         the real exceeds 60% and gave me some examples of mobile providers=
=E2=80=99 statistics.
        =20
        So, this Google statistics confirms what I had said earlier because=
 I got this percent from some online statistics that belongs to the IP addr=
ess assignment process.
        =20
        I would like to thank Google for the efforts made to make this meas=
urements and provide a respectful and real statistics that describes the re=
cent situation so we can make decisions based on it.
        =20
        Best Regards,
        =20
        Khaled Omar=20
        =20
        =20
        From: christopher.morrow@gmail.com [mailto:christopher.morrow@gmail=
.com]
        On Behalf Of Christopher Morrow
        Sent: Saturday, April 15, 2017 7:16 PM
        To: Khaled Omar
        Cc: int-area; intarea-ads; ietf; intarea-chairs
        Subject: Re: Google Statistics for IPv6 adoption.
        =20
        =20
        =20
        On Sat, Apr 15, 2017 at 9:09 AM, Khaled Omar <eng.khaled.omar@hotma=
il.com> wrote:
       =20
        Hi all,
       =20
        Please check out this link that shows the statistics of the IPv6 ad=
option over the past 10 years maybe it will make you believe what was said =
earlier.
       =20
       =20
        =20
       =20
        'what was said earlier' - citation requested.
       =20
        =20
       =20
       =20
       =20
         https://www.google.com/intl/en/ipv6/statistics.html
       =20
        Recent IPv6 adoption (April, 2017) is:
        14.83% Native - 0.03% 6to4 - 14.87% Total
       =20
        Best regards,
       =20
        Khaled Omar
       =20
       =20
       =20
        =20
       =20
       =20
       =20
       =20
       =20
        _______________________________________________
        Int-area mailing list
        Int-area@ietf.org
        https://www.ietf.org/mailman/listinfo/int-area
       =20
   =20
   =20
   =20
    **********************************************
    IPv4 is over
    Are you ready for the new Internet ?
    http://www.consulintel.es
    The IPv6 Company
   =20
    This electronic message contains information which may be privileged or=
 confidential. The information is intended to be for the use of the individ=
ual(s) named above. If you are not the intended recipient be aware that any=
 disclosure, copying, distribution or use of the contents of this informati=
on, including attached files, is prohibited.
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sun Apr 16 05:06:38 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E7E12741D; Sun, 16 Apr 2017 05:06:36 -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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 LdDnflDm4lqT; Sun, 16 Apr 2017 05:06:35 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 32F3B124D6C; Sun, 16 Apr 2017 05:06:35 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Apr 2017 12:06:35 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id D763BD788D; Sun, 16 Apr 2017 05:06:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=ZJunYXOPlSDE27AO+s18JwO9KOo=; b= FhEECMFFR8GqL66wxZuOA58Oueyup4syLKZw/HAaxJJ53Xt5sussoEapoIfsi1qm aLTdvx14P6h/UIfeOV8aMgeRgByhLH+NRb9+Yww877N78GcuynibbDKfiWN2f0dl uoX6ywMBsrRXxAg9KlTeavOxjTLjpiosOuHh3c+kb4U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=ZmpN3sXojJXmJM1CVckrf5C IoJHXqk5jR9owwvFrkVUA19vwwWP58EcwfC+CMaNyxP8lCDVbROB4eAGmr5szC/z V6GMW5fyKNeTVrzwCl/T/ZNsq8jv/01j2IVpI6xvUfJJGrvYQ29pOqLGSwTxPliY bJKxuQazwIOwSb7JIFko=
Received: from h.hanazo.no (77.16.75.18.tmi.telenormobil.no [77.16.75.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 65EAAD788B; Sun, 16 Apr 2017 05:06:34 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2584AA9DBB5D; Sun, 16 Apr 2017 14:06:30 +0200 (CEST)
From: otroan@employees.org
Message-Id: <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_22D5E9C8-A319-45BD-9EDF-24D27908AFE2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
Date: Sun, 16 Apr 2017 14:06:29 +0200
In-Reply-To: <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
To: jordi.palet@consulintel.es
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gdyo7VxwAnfHZ5-hrYltuPlX7TE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 12:06:37 -0000

--Apple-Mail=_22D5E9C8-A319-45BD-9EDF-24D27908AFE2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Jordi,

> And actually, in general, nobody complains that any hosts in IPv4 is =
not able to access resources at IPv6 hosts. This is why we have the =
transition mechanism, that are being deployed in parallel to the IPv6 =
deployment.

This is not true.
The plan was for a short period where hosts were dual stack and then as =
soon as IPv6 was everywhere, turn IPv4 off.
That's not where we are. I would expect the number of  IPv6 only =
networks and services to grow. Possibly without IPv4 support at all, or =
where the cost and responsibility of legacy support will be pushed out =
towards the IPv4 only users.

> Nobody is so crazy to just deploy IPv6 and do not provide those =
transition mechanisms.
>=20
> If that happens, clearly is the fault of somebody that doesn=E2=80=99t =
know how to do his job. This can happen exactly the same if your =
protocol becomes approved and some folks don=E2=80=99t update their =
hosts or routers to comply with your protocol, right?

The transition has turned out to be a real pain.
I understand the problem Khaled set out to solve.
Unfortunately his solution is not practical nor deployable.
And we have in fact tried many of the same flavours of solution before.
Given Khaled's apparent non-interest in two-way communication I wouldn't =
imagine any number of emails would help in that regard.

Best regards,
Ole

--Apple-Mail=_22D5E9C8-A319-45BD-9EDF-24D27908AFE2
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-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY815FAAoJEL7aWKiYQt92sJwP/AltEf3MK+gK9QqVtNj4Fk9M
3jR3eJUegO/8CdfwhWF0XD7rZ7OL/xYN4ZOc9n39xmcRTbxyhOzmKkkmd068deHC
JNpl+pBg5iJQJyENYiG15htoxjhOHhNmbOhCEZFitu5H6Xnp8NP/Haph90QMZZPL
GsbAMp+jynAuTdUqWI7w/KKWM5RUPBue2PRdgjXNamOitVwhYeMlYX3Jnv1WixFw
42te9knUmgANDOZdsJVglhmqIrN5isZq+l3WydZggwooMzv/hPU46ea+f+PfDALZ
2VUZH3vXa+BsPuKPWi+v1VS+oUESPl40Mi3WDyFIZoTL7SwIrexiae224MXznoX4
pt1U6bfnRJOLOBqSXC/LlV96XzGDX8DTx/VUCym4VFEU8gNLdoYjsRdO0S3eRBZV
DcHM4F9a1eOnDSfgjIH0QhRsQLyRqViHQYRsZb+QSLlP/z8+P9tqEPV31zNf+6az
pBGTJDYHPZ1Mp+nLhhhNvkK+C84CSDmnlM82Ro6UvLKeSoIBXk2im6SUXN3IFWcj
pRl9E3Ko6j9PeKojWwkh1hEaO5TC22AXu+6PjoOU+uWXd4UGwEQQNWm3oeVI6NtZ
9Wtr39ajASOeiuMEQF5rvU6loE7Qcps9IVGV7h8N1ZICeJpNjLQsUbijLsgT/BDu
UnMQywGXq0bp1xzuMWyY
=5Fiq
-----END PGP SIGNATURE-----

--Apple-Mail=_22D5E9C8-A319-45BD-9EDF-24D27908AFE2--


From nobody Sun Apr 16 05:53:34 2017
Return-Path: <dmznr@icloud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8B4127BA3 for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 05:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.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 jR8DoUrsINJg for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 05:53:31 -0700 (PDT)
Received: from st14p25im-asmtp003.me.com (st14p25im-asmtp003.me.com [17.162.181.61]) (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 24AFC12706D for <ietf@ietf.org>; Sun, 16 Apr 2017 05:53:31 -0700 (PDT)
Received: from process-dkim-sign-daemon.st14p25im-asmtp003.me.com by st14p25im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OOI00N006FAV800@st14p25im-asmtp003.me.com> for ietf@ietf.org; Sun, 16 Apr 2017 12:53:30 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=4d515a;  t=1492347210; bh=78QtlwOZG5LRQObbcu5ldlJJFHESU/PNwJXS8Wznbzs=;  h=From:Content-type:MIME-version:Date:Subject:Message-id:To; b=juyzYWV+LT9OVaqBTewN6jXMunjCPNxuPAd5exXMrysgHtpKFF5vWKZ25wNPgWyBn yy8I0IUCedf8zf+DnlDOgM/gL3bffvEHuCBTxKSEtajYXXVrxCa1N1q+BtxBmNWFak FDoW5OZMqEbUxdZmNKro/CBdpr5OSC0wSVn3UV4/tJakLeDcxVqUfQRQte60FCY76O KZk6dDAPDoYCZDgWWO3PUuwbHxO6I5dYTIHrveEp5MVX3FEnDsX38XHoM8jnK29NMF 2TzC5+hVNsGb1NdJdfVqiYuxhpYfNiqPz6sPU7vcqFQxpjOVKlaq4tAwxz60zo/Uen /icccQh7oqAlA==
Received: from icloud.com ([127.0.0.1]) by st14p25im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OOI00O2D6H0AO00@st14p25im-asmtp003.me.com> for ietf@ietf.org; Sun, 16 Apr 2017 12:53:30 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-16_11:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704160115
From: Nori Demizu <dmznr@icloud.com>
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sun, 16 Apr 2017 21:53:24 +0900
Subject: Re: www.watersprings.org
Message-id: <6D629815-DEE4-4FC6-895C-C3E51EC0EE09@icloud.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4Gl5XTxBoZCf8rWrjGv0ftW922g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 12:53:32 -0000

If you remember of www.watersprings.org, and if you have visited there,
you may be interested in the newly added CGI that searches IDs and RFCs
and lists them with their ancestor and descendant documents.

It is available at http://www.watersprings.org/

If you try some examples listed there, you'll see what the CGI can do.

Regards,
Nirothis Demizu


From nobody Sun Apr 16 06:05:47 2017
Return-Path: <prvs=12793c0608=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBD2128D3E for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 06:05: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbX4btF63s5m for <ietf@ietfa.amsl.com>; Sun, 16 Apr 2017 06:05:44 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F7C9128B92 for <ietf@ietf.org>; Sun, 16 Apr 2017 06:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492347942; x=1492952742; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=FPl0qJOBq8mYX9JJvBStMiCap cLQAlY0NfTG63rc1YQ=; b=B0o/sBEvDgDVWGpkROG95+fFHPb+bXDO2c5mPwdq+ 6iLDHjRYOdt74p4pn5pMlWa/FpQNzKyXdUB502du0EqX7EivEXkoCvW5K8mvRprS pdEW6YpIPAefNCQFNkB+ltwBuG8B8kfuHwNKgllrjtdU0Qfwyz42jeXakZ8MPbxY +0=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=YogCNipNELfijeKgYdusK9emWhEtnTGFD1YjvB+rUHaRkW7c5WN/8euUudCc p7R7XkTheppHsOw9wtJPnbubom51aKvfE1wVR6SvrTGPYNbe0RrFHdsi+ SYsNxM5P1VrZ9hJ3oxQLBYrDZPjjXnM/8E0N+2i7MAnDs26rrataFg=;
X-MDAV-Processed: mail.consulintel.es, Sun, 16 Apr 2017 15:05:42 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 16 Apr 2017 15:05:41 +0200
Received: from [100.127.23.20] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005409216.msg for <ietf@ietf.org>; Sun, 16 Apr 2017 15:05:39 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170416:md50005409216::nqFxz4SnlNQSAU68:00000da/
X-Return-Path: prvs=12793c0608=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Sun, 16 Apr 2017 15:05:35 +0200
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Message-ID: <C45F68F4-378B-49DF-8597-F04FFE202A9D@consulintel.es>
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es> <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org>
In-Reply-To: <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4iS3eVmxroC6bzPKLi1hyqUPdso>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 13:05:46 -0000

I agree that that was the plan (and it is in the medium term), but my respo=
nse is to Khaled specific point that seems to say (I understood that at lea=
st) that only 15% can access (now) to IPv6-only.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de <otroan@employees.org>
Responder a: <otroan@employees.org>
Fecha: domingo, 16 de abril de 2017, 14:06
Para: <jordi.palet@consulintel.es>
CC: "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int=
-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org"=
 <intarea-chairs@ietf.org>
Asunto: Re: [Int-area] Google Statistics for IPv6 adoption.

    Jordi,
   =20
    > And actually, in general, nobody complains that any hosts in IPv4 is =
not able to access resources at IPv6 hosts. This is why we have the transit=
ion mechanism, that are being deployed in parallel to the IPv6 deployment.
   =20
    This is not true.
    The plan was for a short period where hosts were dual stack and then as=
 soon as IPv6 was everywhere, turn IPv4 off.
    That's not where we are. I would expect the number of  IPv6 only networ=
ks and services to grow. Possibly without IPv4 support at all, or where the=
 cost and responsibility of legacy support will be pushed out towards the I=
Pv4 only users.
   =20
    > Nobody is so crazy to just deploy IPv6 and do not provide those trans=
ition mechanisms.
    >=20
    > If that happens, clearly is the fault of somebody that doesn=E2=80=99=
t know how to do his job. This can happen exactly the same if your protocol=
 becomes approved and some folks don=E2=80=99t update their hosts or router=
s to comply with your protocol, right?
   =20
    The transition has turned out to be a real pain.
    I understand the problem Khaled set out to solve.
    Unfortunately his solution is not practical nor deployable.
    And we have in fact tried many of the same flavours of solution before.
    Given Khaled's apparent non-interest in two-way communication I wouldn'=
t imagine any number of emails would help in that regard.
   =20
    Best regards,
    Ole
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sun Apr 16 08:15:44 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA759127286; Sun, 16 Apr 2017 08:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 f88MkAzXUiUi; Sun, 16 Apr 2017 08:15:33 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065034.outbound.protection.outlook.com [40.92.65.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95A0B120454; Sun, 16 Apr 2017 08:15: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; bh=GrVD/342f7xzPeqKDIQsCRbea8MncnTswyzuqXUt8OE=; b=I3XoupGVcEK+XF+WErZmI9JfgejpDJwtDS9U2N4qJMwL7sJXpx7EjXUidn5bx6S/tYOxX+pPCY5PfQafObEmKRjBGK+unvtn+Z1yuzeVnKwrN4GqGXPWkkl33U0ZCZonDy3mlajA7DvAhzXgrMyhqT8llRYD7GLWRKVyW+DToZS04J/yrk3+LUTRf0U0bRi1EUCUuggUzU7a5Hp0IePJrfMwgvtDxt+/vyzVaaTN01rvXu0RMSyaon1AuE8zy+9AyKkpzuQLCbhSkTuOdYqD+ckHCYkaoo1os6IMW24an2QrWBHEEOEEvCuWpcLoUU4jvCJM1eL9clzZLUtvByFL0w==
Received: from HE1EUR01FT052.eop-EUR01.prod.protection.outlook.com (10.152.0.56) by HE1EUR01HT234.eop-EUR01.prod.protection.outlook.com (10.152.1.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Sun, 16 Apr 2017 15:15:27 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.0.54) by HE1EUR01FT052.mail.protection.outlook.com (10.152.1.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Sun, 16 Apr 2017 15:15:27 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1034.013; Sun, 16 Apr 2017 15:15:27 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "otroan@employees.org" <otroan@employees.org>
CC: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Subject: RE: [Int-area] Google Statistics for IPv6 adoption.
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
Thread-Index: AQHSti47/uaUGNjULEOCU6EGG8PHPKHHMY2wgAB6DwCAADvJgIAAKxiQ
Date: Sun, 16 Apr 2017 15:15:27 +0000
Message-ID: <AM4PR0401MB2241979B2A5B4A639D02083FBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es> <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org>
In-Reply-To: <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: employees.org; dkim=none (message not signed) header.d=none;employees.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:34FD15B4297091F5621866F7DA653A2B2A3DA9C05F64C74BD18D5E21E05808EB; UpperCasedChecksum:E317EA5F08BD876225D1E191476BCEAF68A7D9FDEFC3F8E3F1DF13BA73710C54; SizeAsReceived:8434; Count:42
x-tmn: [tvbwVIhp4BfBeHSjb0gjCDvmbFDOzcev]
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT234; 5:uFHs4KPBjsnaYSd7mJ0GY5vdApWUiFYj+xre1TebhRXorndzxHpQHvYttO6cUbr/E7VznRk1Gvlo3vvDwdBGfWElTB83wiInhm8c1Hq4S5k6CnRAqV0bNhMykiNwOB70lHk1hQVjuZegb0SYpuD2Iw==; 24:3G00IEU39vjdF5RRzEOo8cr6as3FxMIdnXq0G4IPIqNu6LZs9U1jpzRH9SGPrFG0txY5bkVudA/KOfMC55Ghwj1iS0E03Az0QJEXKRgeeIY=; 7:VZWDVFMdBedUSwnAKfxzRih5Mi5cneyWENzUTVmqGAb9ld3G46zdY4hlZb20M83eYXHjLNI2o9uc9608Z2a1T7dOjVUMpffj/XwwoKt0IbL7i9RyRFf3WAev5juICt1jm/rIzk1gZ3GstTjMNFAwS9SvAqBt5WGyZFlYPdDymew2EiVZaXULGriyqXzEQGUaPIv5c0oo9rR2pZM1sLRMIvHJXZvV6WooDwgOpTKvIkzN1v70RAClezJONwQgsE4fMAoMVZpz49TqeR+TcV61ZQP1pm5u7ZewSqeF9qu1Jc1sze3YQexP4GXVfOgo8j4n
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT234; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 98cbd751-9cc6-4af8-e8f6-08d484db69a6
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:HE1EUR01HT234; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT234; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT234; 
x-forefront-prvs: 0279B3DD0D
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2017 15:15:27.0492 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT234
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K4tlZtvrnDyFygm7RaReXticvJA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 15:15:35 -0000

SGkgT2xlLA0KDQo+IFRoaXMgaXMgbm90IHRydWUuDQpUaGUgcGxhbiB3YXMgZm9yIGEgc2hvcnQg
cGVyaW9kIHdoZXJlIGhvc3RzIHdlcmUgZHVhbCBzdGFjayBhbmQgdGhlbiBhcyBzb29uIGFzIElQ
djYgd2FzIGV2ZXJ5d2hlcmUsIHR1cm4gSVB2NCBvZmYuDQpUaGF0J3Mgbm90IHdoZXJlIHdlIGFy
ZS4gSSB3b3VsZCBleHBlY3QgdGhlIG51bWJlciBvZiAgSVB2NiBvbmx5IG5ldHdvcmtzIGFuZCBz
ZXJ2aWNlcyB0byBncm93LiBQb3NzaWJseSB3aXRob3V0IElQdjQgc3VwcG9ydCBhdCBhbGwsIG9y
IHdoZXJlIHRoZSBjb3N0IGFuZCByZXNwb25zaWJpbGl0eSBvZiBsZWdhY3kgc3VwcG9ydCB3aWxs
IGJlIHB1c2hlZCBvdXQgdG93YXJkcyB0aGUgSVB2NCBvbmx5IHVzZXJzLg0KDQpUaGF0J3MgdHJ1
ZS4NCg0KPiA+IElmIHRoYXQgaGFwcGVucywgY2xlYXJseSBpcyB0aGUgZmF1bHQgb2Ygc29tZWJv
ZHkgdGhhdCBkb2VzbuKAmXQga25vdyBob3cgdG8gZG8gaGlzIGpvYi4gVGhpcyBjYW4gaGFwcGVu
IGV4YWN0bHkgdGhlIHNhbWUgaWYgeW91ciBwcm90b2NvbCBiZWNvbWVzIGFwcHJvdmVkIGFuZCBz
b21lIGZvbGtzIGRvbuKAmXQgdXBkYXRlIHRoZWlyIGhvc3RzIG9yIHJvdXRlcnMgdG8gY29tcGx5
IHdpdGggeW91ciBwcm90b2NvbCwgcmlnaHQ/DQoNClRoYXQncyByaWdodCwgYW5kIHRoZXJlIHNo
b3VsZCBiZSBhIHBsYWNlIGxpa2UgdGhlIElFVEYgdGhhdCBzaG91bGQgb3JnYW5pemUgdGhpcyBw
cm9jZXNzIHVudGlsIGFsbCB0ZWNobm9sb2d5IGNvbXBhbmllcyBwcmVwYXJlIHRoZSB1cGRhdGVz
IGFuZCB0aGVyZSBzaG91bGQgYmUgYSBmbGFnIGRheSBmb3IgdGhlIGRlcGxveW1lbnQsDQpJZiBh
IGhvc3Qgc3RpbGwgbm90IHVwZGF0ZWQsIHdpbGwgbm90IGdhaW4gYWNjZXNzIHRvIHRoZSBJbnRl
cm5ldCB1bnRpbCB1cGRhdGluZyB0aGUgT1MuDQoNCkJlc3QgcmVnYXJkcywNCg0KS2hhbGVkIE9t
YXINCiAgDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmIFttYWlsdG86
aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Ygb3Ryb2FuQGVtcGxveWVlcy5vcmcN
ClNlbnQ6IFN1bmRheSwgQXByaWwgMTYsIDIwMTcgMjowNiBQTQ0KVG86IGpvcmRpLnBhbGV0QGNv
bnN1bGludGVsLmVzDQpDYzogaW50YXJlYS1hZHNAaWV0Zi5vcmc7IGludC1hcmVhQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtJ
bnQtYXJlYV0gR29vZ2xlIFN0YXRpc3RpY3MgZm9yIElQdjYgYWRvcHRpb24uDQoNCkpvcmRpLA0K
DQo+IEFuZCBhY3R1YWxseSwgaW4gZ2VuZXJhbCwgbm9ib2R5IGNvbXBsYWlucyB0aGF0IGFueSBo
b3N0cyBpbiBJUHY0IGlzIG5vdCBhYmxlIHRvIGFjY2VzcyByZXNvdXJjZXMgYXQgSVB2NiBob3N0
cy4gVGhpcyBpcyB3aHkgd2UgaGF2ZSB0aGUgdHJhbnNpdGlvbiBtZWNoYW5pc20sIHRoYXQgYXJl
IGJlaW5nIGRlcGxveWVkIGluIHBhcmFsbGVsIHRvIHRoZSBJUHY2IGRlcGxveW1lbnQuDQoNClRo
aXMgaXMgbm90IHRydWUuDQpUaGUgcGxhbiB3YXMgZm9yIGEgc2hvcnQgcGVyaW9kIHdoZXJlIGhv
c3RzIHdlcmUgZHVhbCBzdGFjayBhbmQgdGhlbiBhcyBzb29uIGFzIElQdjYgd2FzIGV2ZXJ5d2hl
cmUsIHR1cm4gSVB2NCBvZmYuDQpUaGF0J3Mgbm90IHdoZXJlIHdlIGFyZS4gSSB3b3VsZCBleHBl
Y3QgdGhlIG51bWJlciBvZiAgSVB2NiBvbmx5IG5ldHdvcmtzIGFuZCBzZXJ2aWNlcyB0byBncm93
LiBQb3NzaWJseSB3aXRob3V0IElQdjQgc3VwcG9ydCBhdCBhbGwsIG9yIHdoZXJlIHRoZSBjb3N0
IGFuZCByZXNwb25zaWJpbGl0eSBvZiBsZWdhY3kgc3VwcG9ydCB3aWxsIGJlIHB1c2hlZCBvdXQg
dG93YXJkcyB0aGUgSVB2NCBvbmx5IHVzZXJzLg0KDQo+IE5vYm9keSBpcyBzbyBjcmF6eSB0byBq
dXN0IGRlcGxveSBJUHY2IGFuZCBkbyBub3QgcHJvdmlkZSB0aG9zZSB0cmFuc2l0aW9uIG1lY2hh
bmlzbXMuDQo+IA0KPiBJZiB0aGF0IGhhcHBlbnMsIGNsZWFybHkgaXMgdGhlIGZhdWx0IG9mIHNv
bWVib2R5IHRoYXQgZG9lc27igJl0IGtub3cgaG93IHRvIGRvIGhpcyBqb2IuIFRoaXMgY2FuIGhh
cHBlbiBleGFjdGx5IHRoZSBzYW1lIGlmIHlvdXIgcHJvdG9jb2wgYmVjb21lcyBhcHByb3ZlZCBh
bmQgc29tZSBmb2xrcyBkb27igJl0IHVwZGF0ZSB0aGVpciBob3N0cyBvciByb3V0ZXJzIHRvIGNv
bXBseSB3aXRoIHlvdXIgcHJvdG9jb2wsIHJpZ2h0Pw0KDQpUaGUgdHJhbnNpdGlvbiBoYXMgdHVy
bmVkIG91dCB0byBiZSBhIHJlYWwgcGFpbi4NCkkgdW5kZXJzdGFuZCB0aGUgcHJvYmxlbSBLaGFs
ZWQgc2V0IG91dCB0byBzb2x2ZS4NClVuZm9ydHVuYXRlbHkgaGlzIHNvbHV0aW9uIGlzIG5vdCBw
cmFjdGljYWwgbm9yIGRlcGxveWFibGUuDQpBbmQgd2UgaGF2ZSBpbiBmYWN0IHRyaWVkIG1hbnkg
b2YgdGhlIHNhbWUgZmxhdm91cnMgb2Ygc29sdXRpb24gYmVmb3JlLg0KR2l2ZW4gS2hhbGVkJ3Mg
YXBwYXJlbnQgbm9uLWludGVyZXN0IGluIHR3by13YXkgY29tbXVuaWNhdGlvbiBJIHdvdWxkbid0
IGltYWdpbmUgYW55IG51bWJlciBvZiBlbWFpbHMgd291bGQgaGVscCBpbiB0aGF0IHJlZ2FyZC4N
Cg0KQmVzdCByZWdhcmRzLA0KT2xlDQo=


From nobody Sun Apr 16 08:18:54 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 739FD12709D; Sun, 16 Apr 2017 08:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 Ln6Vn3f2ufrE; Sun, 16 Apr 2017 08:18:51 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065095.outbound.protection.outlook.com [40.92.65.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76D57120454; Sun, 16 Apr 2017 08:18:50 -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; bh=XPruf9rC2d7tfBzMHxmKxx9A7aFbgDrnSnT6QRXj8bY=; b=A0jPh4nJ0HGCK/6rWKV1v4y9JnuCYbUvJixEe6h2DUw7iteGw6HNvIJ90uyhHts+blbwn3+cbcuTzHqvZN9W9WDR+43F24po8z0KMOYh5YIddc5mzsKYRFyP+iFgcOSfqGzpjQf411b1K72G4EBWbXKAiETPFL8n0bV075RW77jkOMf+CuFAdR08hUiAbEycyFzupfL7bYLWB8htgWjrx+W0x26WVi1pBr1UXkwuUmfykOlE1jWFoZZ2wXLwmKY8GXcSk5oe6o7uz3vRuyWq+OVz5j/gbt+EofHaaT8dSrCS+22gljhZZyFB3E1sy6pujMzomY34YgSBG8T1m5QfYQ==
Received: from HE1EUR01FT052.eop-EUR01.prod.protection.outlook.com (10.152.0.57) by HE1EUR01HT037.eop-EUR01.prod.protection.outlook.com (10.152.0.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Sun, 16 Apr 2017 15:18:47 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.0.54) by HE1EUR01FT052.mail.protection.outlook.com (10.152.1.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Sun, 16 Apr 2017 15:18:47 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1034.013; Sun, 16 Apr 2017 15:18:47 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
CC: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>
Subject: RE: [Int-area] Google Statistics for IPv6 adoption.
Thread-Topic: [Int-area] Google Statistics for IPv6 adoption.
Thread-Index: AQHSti47/uaUGNjULEOCU6EGG8PHPKHHMY2wgAB6DwCAADvJgIAAEIOAgAAktTA=
Date: Sun, 16 Apr 2017 15:18:47 +0000
Message-ID: <AM4PR0401MB22411E83E18A63D33E306E01BD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es> <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org> <C45F68F4-378B-49DF-8597-F04FFE202A9D@consulintel.es>
In-Reply-To: <C45F68F4-378B-49DF-8597-F04FFE202A9D@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: consulintel.es; dkim=none (message not signed) header.d=none; consulintel.es; dmarc=none action=none header.from=hotmail.com; 
x-incomingtopheadermarker: OriginalChecksum:A6DC2D4A35583EDE2E5B780957AA95CA3D5FC086D7ECE2A441A28757BD0DE4F7; UpperCasedChecksum:D94CC8A85E3DB673A3C52173936D59EBC4684CFCB14FA12FEADB48545524D06A; SizeAsReceived:8505; Count:42
x-tmn: [vInLFG8m7lv8SY1vCIxbUsoniQENxcFL]
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT037; 5:7tWWDLhVobn4aqm2+zJhkiJv++rNFsJ84G19o15bYJ4UtTsQunB2g8e/D9GZ7W1yqlTgPAT3+HVoZ3j+y876w7bPzccXCwhg1QCGT1+XjkB8Mxt9whKCBqLv1Bg82uSsHyhrXGjXhldqdPnFC0iQLg==; 24:S97heX5Xb5+QrrgBwJCT0wk5sLqjg1oPUpkv6DalduDJcFPgOwA+yND0ztMKch3MqkNMBVXHVINwEW0aCXDXMd7NLfha3WUyWtz1fDwqmJE=; 7:apz+4vAHyX8l/UQEQ5xtAQUUPSq4U0Ni93xI6ylRLvXApeHPPWqAcFHuIGZmc+N2GxQ4s5WEvbqflKTUDHIKbhfrq++gVXNXRq5YyMPiNOg9zbzHy3vMjdNBD8FtUoCOSDE9VERzckGxOSyd7owg8ZlC8xhTS3YAU5j3NsJSRGPPgD5oQpQD/5At5QKPrnzv7syJRzutIRUeB0US/2MgYhatkpp1ukvNNgVPO8jyFi9HdefC15Aj/a1rFyFx4s+YjsIoxjWJLfpK5uA87P5BfJmZhB9/bkb6Y710qpCNPp4IYr0Msm9x4SGr8RELF3Ik
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT037; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 6ef7e3cc-b9d6-4f9c-2e28-08d484dbe12f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR01HT037; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT037; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT037; 
x-forefront-prvs: 0279B3DD0D
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2017 15:18:47.6332 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT037
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1w1d-DpYxihQP4dM-eSmxSLLJ6E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 15:18:52 -0000

Sm9yZGksDQoNCj4gSSBhZ3JlZSB0aGF0IHRoYXQgd2FzIHRoZSBwbGFuIChhbmQgaXQgaXMgaW4g
dGhlIG1lZGl1bSB0ZXJtKSwgYnV0IG15IHJlc3BvbnNlIGlzIHRvIEtoYWxlZCBzcGVjaWZpYyBw
b2ludCB0aGF0IHNlZW1zIHRvIHNheSAoSSB1bmRlcnN0b29kIHRoYXQgYXQgbGVhc3QpIHRoYXQg
b25seSAxNSUgY2FuIGFjY2VzcyAobm93KSB0byBJUHY2LW9ubHkuDQoNClRoaW5rIGFib3V0IHdo
ZW4gdGhlIHBlcmNlbnRhZ2Ugd2lsbCBiZSA1MCUsIGl0IHdpbGwgYmUgYSByZWFsIGRpdmlzaW9u
IGZvciB0aGUgaW50ZXJuZXQgZm9yIGJvdGggSVB2NCBvbmx5IGFuZCBJUHY2IG9ubHkgaG9zdHMu
DQoNCkJlc3QgcmVnYXJkcywNCg0KS2hhbGVkIE9tYXINCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCkZyb206IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZiBKT1JESSBQQUxFVCBNQVJUSU5FWg0KU2VudDogU3VuZGF5LCBBcHJpbCAxNiwgMjAxNyAz
OjA2IFBNDQpUbzogaW50YXJlYS1hZHNAaWV0Zi5vcmc7IGludC1hcmVhQGlldGYub3JnOyBpZXRm
QGlldGYub3JnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtJbnQtYXJl
YV0gR29vZ2xlIFN0YXRpc3RpY3MgZm9yIElQdjYgYWRvcHRpb24uDQoNCkkgYWdyZWUgdGhhdCB0
aGF0IHdhcyB0aGUgcGxhbiAoYW5kIGl0IGlzIGluIHRoZSBtZWRpdW0gdGVybSksIGJ1dCBteSBy
ZXNwb25zZSBpcyB0byBLaGFsZWQgc3BlY2lmaWMgcG9pbnQgdGhhdCBzZWVtcyB0byBzYXkgKEkg
dW5kZXJzdG9vZCB0aGF0IGF0IGxlYXN0KSB0aGF0IG9ubHkgMTUlIGNhbiBhY2Nlc3MgKG5vdykg
dG8gSVB2Ni1vbmx5Lg0KDQpSZWdhcmRzLA0KSm9yZGkNCiANCg0KLS0tLS1NZW5zYWplIG9yaWdp
bmFsLS0tLS0NCkRlOiBpZXRmIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmc+IGVuIG5vbWJyZSBkZSA8
b3Ryb2FuQGVtcGxveWVlcy5vcmc+IFJlc3BvbmRlciBhOiA8b3Ryb2FuQGVtcGxveWVlcy5vcmc+
DQpGZWNoYTogZG9taW5nbywgMTYgZGUgYWJyaWwgZGUgMjAxNywgMTQ6MDYNClBhcmE6IDxqb3Jk
aS5wYWxldEBjb25zdWxpbnRlbC5lcz4NCkNDOiAiaW50YXJlYS1hZHNAaWV0Zi5vcmciIDxpbnRh
cmVhLWFkc0BpZXRmLm9yZz4sICJpbnQtYXJlYUBpZXRmLm9yZyIgPGludC1hcmVhQGlldGYub3Jn
PiwgImlldGZAaWV0Zi5vcmciIDxpZXRmQGlldGYub3JnPiwgImludGFyZWEtY2hhaXJzQGlldGYu
b3JnIiA8aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpBc3VudG86IFJlOiBbSW50LWFyZWFdIEdv
b2dsZSBTdGF0aXN0aWNzIGZvciBJUHY2IGFkb3B0aW9uLg0KDQogICAgSm9yZGksDQogICAgDQog
ICAgPiBBbmQgYWN0dWFsbHksIGluIGdlbmVyYWwsIG5vYm9keSBjb21wbGFpbnMgdGhhdCBhbnkg
aG9zdHMgaW4gSVB2NCBpcyBub3QgYWJsZSB0byBhY2Nlc3MgcmVzb3VyY2VzIGF0IElQdjYgaG9z
dHMuIFRoaXMgaXMgd2h5IHdlIGhhdmUgdGhlIHRyYW5zaXRpb24gbWVjaGFuaXNtLCB0aGF0IGFy
ZSBiZWluZyBkZXBsb3llZCBpbiBwYXJhbGxlbCB0byB0aGUgSVB2NiBkZXBsb3ltZW50Lg0KICAg
IA0KICAgIFRoaXMgaXMgbm90IHRydWUuDQogICAgVGhlIHBsYW4gd2FzIGZvciBhIHNob3J0IHBl
cmlvZCB3aGVyZSBob3N0cyB3ZXJlIGR1YWwgc3RhY2sgYW5kIHRoZW4gYXMgc29vbiBhcyBJUHY2
IHdhcyBldmVyeXdoZXJlLCB0dXJuIElQdjQgb2ZmLg0KICAgIFRoYXQncyBub3Qgd2hlcmUgd2Ug
YXJlLiBJIHdvdWxkIGV4cGVjdCB0aGUgbnVtYmVyIG9mICBJUHY2IG9ubHkgbmV0d29ya3MgYW5k
IHNlcnZpY2VzIHRvIGdyb3cuIFBvc3NpYmx5IHdpdGhvdXQgSVB2NCBzdXBwb3J0IGF0IGFsbCwg
b3Igd2hlcmUgdGhlIGNvc3QgYW5kIHJlc3BvbnNpYmlsaXR5IG9mIGxlZ2FjeSBzdXBwb3J0IHdp
bGwgYmUgcHVzaGVkIG91dCB0b3dhcmRzIHRoZSBJUHY0IG9ubHkgdXNlcnMuDQogICAgDQogICAg
PiBOb2JvZHkgaXMgc28gY3JhenkgdG8ganVzdCBkZXBsb3kgSVB2NiBhbmQgZG8gbm90IHByb3Zp
ZGUgdGhvc2UgdHJhbnNpdGlvbiBtZWNoYW5pc21zLg0KICAgID4gDQogICAgPiBJZiB0aGF0IGhh
cHBlbnMsIGNsZWFybHkgaXMgdGhlIGZhdWx0IG9mIHNvbWVib2R5IHRoYXQgZG9lc27igJl0IGtu
b3cgaG93IHRvIGRvIGhpcyBqb2IuIFRoaXMgY2FuIGhhcHBlbiBleGFjdGx5IHRoZSBzYW1lIGlm
IHlvdXIgcHJvdG9jb2wgYmVjb21lcyBhcHByb3ZlZCBhbmQgc29tZSBmb2xrcyBkb27igJl0IHVw
ZGF0ZSB0aGVpciBob3N0cyBvciByb3V0ZXJzIHRvIGNvbXBseSB3aXRoIHlvdXIgcHJvdG9jb2ws
IHJpZ2h0Pw0KICAgIA0KICAgIFRoZSB0cmFuc2l0aW9uIGhhcyB0dXJuZWQgb3V0IHRvIGJlIGEg
cmVhbCBwYWluLg0KICAgIEkgdW5kZXJzdGFuZCB0aGUgcHJvYmxlbSBLaGFsZWQgc2V0IG91dCB0
byBzb2x2ZS4NCiAgICBVbmZvcnR1bmF0ZWx5IGhpcyBzb2x1dGlvbiBpcyBub3QgcHJhY3RpY2Fs
IG5vciBkZXBsb3lhYmxlLg0KICAgIEFuZCB3ZSBoYXZlIGluIGZhY3QgdHJpZWQgbWFueSBvZiB0
aGUgc2FtZSBmbGF2b3VycyBvZiBzb2x1dGlvbiBiZWZvcmUuDQogICAgR2l2ZW4gS2hhbGVkJ3Mg
YXBwYXJlbnQgbm9uLWludGVyZXN0IGluIHR3by13YXkgY29tbXVuaWNhdGlvbiBJIHdvdWxkbid0
IGltYWdpbmUgYW55IG51bWJlciBvZiBlbWFpbHMgd291bGQgaGVscCBpbiB0aGF0IHJlZ2FyZC4N
CiAgICANCiAgICBCZXN0IHJlZ2FyZHMsDQogICAgT2xlDQogICAgDQoNCg0KDQoqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQpJUHY0IGlzIG92ZXINCkFyZSB5
b3UgcmVhZHkgZm9yIHRoZSBuZXcgSW50ZXJuZXQgPw0KaHR0cDovL3d3dy5jb25zdWxpbnRlbC5l
cw0KVGhlIElQdjYgQ29tcGFueQ0KDQpUaGlzIGVsZWN0cm9uaWMgbWVzc2FnZSBjb250YWlucyBp
bmZvcm1hdGlvbiB3aGljaCBtYXkgYmUgcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwuIFRoZSBp
bmZvcm1hdGlvbiBpcyBpbnRlbmRlZCB0byBiZSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVh
bChzKSBuYW1lZCBhYm92ZS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBi
ZSBhd2FyZSB0aGF0IGFueSBkaXNjbG9zdXJlLCBjb3B5aW5nLCBkaXN0cmlidXRpb24gb3IgdXNl
IG9mIHRoZSBjb250ZW50cyBvZiB0aGlzIGluZm9ybWF0aW9uLCBpbmNsdWRpbmcgYXR0YWNoZWQg
ZmlsZXMsIGlzIHByb2hpYml0ZWQuDQoNCg0KDQo=


From nobody Sun Apr 16 10:02:31 2017
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53ACB127775; Sun, 16 Apr 2017 10:02:29 -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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, UNPARSEABLE_RELAY=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 tznRhHyQNMcl; Sun, 16 Apr 2017 10:02:28 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id EB05D127735; Sun, 16 Apr 2017 10:02:27 -0700 (PDT)
Received: from dummy.name; Sun, 16 Apr 2017 17:02:27 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_2C966588-8643-4E8B-80E3-A977A81DCD37"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <AM4PR0401MB2241979B2A5B4A639D02083FBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Date: Sun, 16 Apr 2017 13:02:25 -0400
Cc: "Stephen D. Crocker" <steve@shinkuro.com>, "otroan@employees.org" <otroan@employees.org>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Message-Id: <120F5DC0-AB17-448F-83E3-E633CBF7B1C3@shinkuro.com>
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es> <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org> <AM4PR0401MB2241979B2A5B4A639D02083FBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cXiy_tfqd1oFI1tv8__cdRcyhVU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 17:02:29 -0000

--Apple-Mail=_2C966588-8643-4E8B-80E3-A977A81DCD37
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

There was a flag day for the transition from NCP to TCP/IP.  There will =
never be another flag day.  Any transition solution, whether from IPv4 =
to IPv6 or a successor protocol elsewhere on the stack, has to be =
designed to permit overlap and interoperability during the very long =
period when both the old and new protocols will be operating.

Further, there will have to be two incentives at work for the transition =
to succeed.  One is in favor of the the new protocol.  The other is =
against the old protocol.  If the former is missing, the new protocol =
won=E2=80=99t be adopted.  If the latter is missing, the old protocol =
will persist indefinitely.

To repeat: there will never be another flag day.  If this is one of your =
assumptions, step back and think about the problem again.

Steve


> On Apr 16, 2017, at 11:15 AM, Khaled Omar =
<eng.khaled.omar@hotmail.com> wrote:
>=20
> That's right, and there should be a place like the IETF that should =
organize this process until all technology companies prepare the updates =
and there should be a flag day for the deployment,
> If a host still not updated, will not gain access to the Internet =
until updating the OS.


--Apple-Mail=_2C966588-8643-4E8B-80E3-A977A81DCD37
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; -webkit-line-break: after-white-space;" =
class=3D"">There was a flag day for the transition from NCP to TCP/IP. =
&nbsp;There will never be another flag day. &nbsp;Any transition =
solution, whether from IPv4 to IPv6 or a successor protocol elsewhere on =
the stack, has to be designed to permit overlap and interoperability =
during the very long period when both the old and new protocols will be =
operating.<div class=3D""><br class=3D""></div><div class=3D"">Further, =
there will have to be two incentives at work for the transition to =
succeed. &nbsp;One is in favor of the the new protocol. &nbsp;The other =
is against the old protocol. &nbsp;If the former is missing, the new =
protocol won=E2=80=99t be adopted. &nbsp;If the latter is missing, the =
old protocol will persist indefinitely.</div><div class=3D""><br =
class=3D""></div><div class=3D"">To repeat: there will never be another =
flag day. &nbsp;If this is one of your assumptions, step back and think =
about the problem again.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Steve</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 16, 2017, at 11:15 AM, Khaled Omar &lt;<a =
href=3D"mailto:eng.khaled.omar@hotmail.com" =
class=3D"">eng.khaled.omar@hotmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Cambria; font-size: 18px; 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-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">That's right, and there should be a place like =
the IETF that should organize this process until all technology =
companies prepare the updates and there should be a flag day for the =
deployment,</span><br style=3D"font-family: Cambria; font-size: 18px; =
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-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Cambria; font-size: 18px; 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-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">If a host still not updated, will not gain =
access to the Internet until updating the OS.</span><br =
style=3D"font-family: Cambria; font-size: 18px; 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-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_2C966588-8643-4E8B-80E3-A977A81DCD37--


From nobody Sun Apr 16 10:26:07 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94573126C22; Sun, 16 Apr 2017 10:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.392
X-Spam-Level: 
X-Spam-Status: No, score=-0.392 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.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 l9g4lgbYYXOr; Sun, 16 Apr 2017 10:25:58 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 13228120724; Sun, 16 Apr 2017 10:25:58 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3GHSBmD021491 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 16 Apr 2017 10:28:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492363692; bh=svqI3EyS3sBqMW2wFzyYFJIG9iYVNzvDWFpwyXy4cbc=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=aYvLiyLS5Ey2MDL3bhYPCqvmo5A8t1BavpFv/USD3CZ6lX/j9IB+/PmuAdj6M9Zag DYvjX+uyQzygRlmcDB4Umb1o7quMrSan/LS/CaBAQNS0nT+TwRQWTF5TNLfutgN06H m2R89xhgzgEsFOl339wH4+l3vG45ck89V/VSO7qQ=
Subject: Re: [Int-area] Google Statistics for IPv6 adoption.
To: Steve Crocker <steve@shinkuro.com>, Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
References: <1DD1280A-CAF0-4555-87E3-730A609C9423@consulintel.es> <AM4PR0401MB224193019197157A8DC495CBBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <FF381A9D-A312-4DEC-90E6-8FF3A595789D@consulintel.es> <8A03EE98-1C94-4A82-A0E3-B1A144B6B1AB@employees.org> <AM4PR0401MB2241979B2A5B4A639D02083FBD070@AM4PR0401MB2241.eurprd04.prod.outlook.com> <120F5DC0-AB17-448F-83E3-E633CBF7B1C3@shinkuro.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <dec307bb-47c5-ac22-d498-a76dce563b03@dcrocker.net>
Date: Sun, 16 Apr 2017 10:25:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <120F5DC0-AB17-448F-83E3-E633CBF7B1C3@shinkuro.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yuL6LZtS250ev2KKhLyJebK2V60>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Apr 2017 17:25:59 -0000

On 4/16/2017 10:02 AM, Steve Crocker wrote:
>   Any transition solution, whether from IPv4 to IPv6 or a successor 
> protocol elsewhere on the stack, has to be designed to permit overlap 
> and interoperability during the very long period when both the old and 
> new protocols will be operating.

Given the amount of time any Internet-scale transition must/will take, 
the term 'transition' is tending to be problematic, because it 
encourages of tone of temporariness.

When the scale is one or more decades -- as we seem to be seeing 
regularly -- the better model is long-term dual-stack with 
interoperability support (gateways and tunnels.)


> Further, there will have to be two incentives at work for the transition 
> to succeed.

+1, but the challenge is figuring out who to incentivize and making sure 
the incentives are powerful and real (and usually immediate.)  We all 
have a tendency to imagine incentives that are convenient to our goals, 
whereas those doing the uptake often prove remarkably uncooperative to 
our view...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 17 16:00:30 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD3D1242F7; Mon, 17 Apr 2017 16:00:21 -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_HELO_PASS=-0.001, 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=microsoft.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 YeJzoQCAjaeM; Mon, 17 Apr 2017 16:00:17 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0107.outbound.protection.outlook.com [104.47.36.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89491286AB; Mon, 17 Apr 2017 16:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3Z3RglyQQF+6Uu9MogXhgZRakBbd4MaKZUEgzrjEDGg=; b=Q+Nc5lNjQioJTb2fUrCyOINf2o7zbcJuOegwYQLxCfBp07utkV9pIpC/stkGuo5CE6DBNz+vtQrj5pkb+/TPly+CFO1TsdC0Jd8p20wK3iL+I3C6Hb326ZSNG7hVlO78zKIOklJs1SQj43cBhpdFgwKj/bg7TORFexqR/4AxvDY=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2123.namprd03.prod.outlook.com (10.164.2.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.10; Mon, 17 Apr 2017 23:00:14 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1034.013; Mon, 17 Apr 2017 23:00:14 +0000
From: Orit Levin <oritl@microsoft.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kAAbW6QgADEG3NQ
Date: Mon, 17 Apr 2017 23:00:13 +0000
Message-ID: <CY1PR0301MB2122E2E3ED639D1E1D85A8AFAD060@CY1PR0301MB2122.namprd03.prod.outlook.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com> <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com> <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
In-Reply-To: <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [130.217.31.226]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2123; 7:z4+LZfQnD+ZkOutVtivsZlOPd6Qe26vIxjfBak2qY+XAogsDKavWtxmIugCIA1pszSzNoUofJqlozivv5IX5M9lU7HTvxIeC4cimzA/vFbhQl4ct+vxH2vLHRntGWFABkKLAdO+Mn2Q4CSJg+ekfxlWcRndR9plpLNY/FNQ0n3kr4VkAD37+N4KuV4pKWdpUMVii18mBnqcBZMvkl71cvumz0jeg6kDkeqjSLdvuZi3S/erjTfBREX3mJkwQIxVHSXYlaKbsZcdU4b8xBJrazChIAhAs+EuRnDvfDHJ6gWwDVEhniISEWl9v99KDUlouIX0rwOZJ9cXdw7gToXXkzhoX9iPReeNR6Wgi/csAyRQ=
x-ms-office365-filtering-correlation-id: 3be57a2a-018c-4451-dbc0-08d485e58210
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CY1PR0301MB2123; 
x-microsoft-antispam-prvs: <CY1PR0301MB2123AC233EF855D13F7F3DC1AD060@CY1PR0301MB2123.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(131327999870524)(788757137089)(95692535739014); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123555025)(20161123560025)(20161123562025)(6072148); SRVR:CY1PR0301MB2123; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2123; 
x-forefront-prvs: 02801ACE41
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39450400003)(39400400002)(39860400002)(39840400002)(39410400002)(377424004)(13464003)(129404003)(377454003)(5660300001)(7736002)(8676002)(54356999)(8936002)(81166006)(50986999)(76176999)(38730400002)(189998001)(66066001)(6116002)(2501003)(10090500001)(5005710100001)(33656002)(3846002)(122556002)(74316002)(10290500002)(102836003)(93886004)(305945005)(2900100001)(53546009)(6436002)(230783001)(99286003)(7696004)(4326008)(2950100002)(55016002)(9686003)(6506006)(6306002)(2906002)(53946003)(54906002)(86612001)(77096006)(25786009)(53936002)(6246003)(86362001)(3280700002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2123; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2017 23:00:13.9886 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2123
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lwaMSorZVgNIVinY7XRMp_cAsyM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 23:00:21 -0000

Dear Les,

I see that you "agreed" to correct two typos only.
I disagree with your reasons for not making the document more readable and =
complete. Note that "more complete" doesn't necessarily mean "more prescrip=
tive". It means removing ambiguities that will continue hurting interoperab=
ility of new and existing implementations.=20
Since your guiding principle is "don't rock the boat / don't describe what =
to do - only what NOT to do", I see no point in arguing point-by-point.=20
I know that different Areas have different standards for their documents, s=
o I leave it to your community.

Thanks,
Orit.

-----Original Message-----
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]=20
Sent: Thursday, April 13, 2017 8:06 PM
To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02

Orit -

It is obvious you spent a lot of time on this review - and I do want to be =
respectful of that.
However, there is a larger context here which I think has a significant bea=
ring on handling of many of your comments.

RFC 6822 was published over 4 years ago. Multiple interoperable implementat=
ions exist. The bis version makes some modest - but significant changes. Ho=
wever, we deliberately strived to keep the bis version as consistent as pos=
sible with RFC 6822 in order to minimize the possibility that aspects of th=
e specification which had NOT been changed would be reinterpreted simply be=
cause the wording had changed. So, in cases where you suggest (below) that =
a different wording is desirable I am very reluctant to make such changes b=
ecause of the above concern.
If I do not indicate any response to a particular comment you can interpret=
 as meaning:

"Unnecessary changes relative to RFC 6822 are not desirable."

Inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 13, 2017 4:59 PM
> To: Les Ginsberg (ginsberg); gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Hi Les,
> Sorry for the delay in response.
> Your feedback was very helpful. Below is a refresh of my comments. I=20
> tried to make them more pointed and some are new.
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> General:
> 1) For implementers who are familiar with the history and the intent=20
> of this extension, the information in the draft is probably sufficient=20
> to serve as a check list for implementing a multi-instance IS-IS=20
> router. For all other readers, the document doesn't contain an=20
> overview of the new mode of operation, i.e. where the instances are=20
> not a configuration and an internal implementation choice only, but=20
> are exposed through the protocol to achieve the stated objective.=20
> Lacking such an overview, the reader needs to reverse-engineer the logic =
behind the documented guidance.

[Les:] I am not sure I understand your concern. You seem to be suggesting t=
hat readers won't know when to use MI and when to simply create multiple no=
n-MI instances of the protocol.
The short answer to that is that it is not the purpose of this document to =
make that decision. We have provided some new functionality - it is up to t=
he user to decide when it is appropriate to use the new functionality and w=
hen it is not. We have provided some guidance in Sections 3 and 4 - but thi=
s is non-normative - as it should be.
But your use of "reverse-engineer" confuses me, so likely I do not understa=
nd your point.

As regards new vs old readers, the new version of the document provides as =
much (or as little) guidance as RFC 6822 - so I do not see why new readers =
would have any more issues than new readers of RFC 6822 had 4 years ago.


> 2) The draft talks about "extensions" in plural. Based on a single=20
> extension on the wire and the overall goal of the new mechanism, I=20
> would say that it is a single extension only.  How many protocol=20
> extensions does this document define? If they can be clearly=20
> separated, then it needs to be clarified throughout the document.=20
> Otherwise, the language throughout the document needs to be changed from =
"extensions" to "the extention".

[Les:] There are multiple changes in protocol behavior described - hence th=
e term extensions is correct.

> 3) Editorial: Please, compare (Diff) the current draft with the=20
> published RFC 6822. You will find that various RFC Editor corrections=20
> got lost in this bis document. Some repeating examples of the lost=20
> corrections are "instance- specific", " topology (or topologies)" and "Ty=
pe-Length-Value".

[Les:] Noted - thanx.

> My comments below are a result of a reverse-engineering exercise.=20
> Please, consider incorporating the suggested clarifications to improve=20
> the document readability. I might have misunderstood some of the=20
> parts; in such cases, please, provide an alternative text.
>=20
> Abstract
> 1) Add clarification: "This document is not backwards compatible with=20
> RFC 6822."

[Les:] This statement is made explicitly in the Appendix - and I believe th=
at is where it belongs for reasons I have previously stated.

> 2) Par. 2, replace the first two sentences with: "Configuration of=20
> multiple protocol instances within a router allow the isolation of=20
> resources associated with each instance. This document introduces a=20
> new mode of operation where the protocol instances are not a matter of=20
> configuration only, but are exposed through the new protocol extension=20
> to achieve the objective stated above."
> 3) Par. 3 uses both present and future time. Does it mean before and=20
> after the extension? Please, clarify by spelling out the intent and/or=20
> changing the grammar.
>=20
[Les:] The sentence will in any case be changed when the document becomes a=
n RFC - not worth discussing.

> 1. Introduction
> 1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the=20
> Introduction to improve its logical flow (also related to the next commen=
t).
> 2) Par 4, sentence #2 says "This document defines an extension to=20
> IS-IS to allow non-zero instances...". My assumption is that the=20
> intent of this draft is to define a single extension, which will=20
> improve the routing operations in a number of ways. If this is the=20
> case, the quote needs to be replaced with "The MI-IS-IS extension,=20
> defined in this document, also allows so-called "non-zero instances"..." =
.
> 3) Par 4, sentences #4 and #5 are not sufficient to describe the new=20
> mode of operation introduced by this extension. Below is my attempt to de=
scribe it.
> Please, correct, if I got it wrong.
> "IS-IS router instances that support this extension are preconfigured=20
> with unique non-zero Instance Identifiers (IIDs) giving them the name=20
> "non-zero instances". In addition, MI RTRs MAY (or SHOULD ?) implement=20
> the legacy (or so-called "standard") instance of the IS-IS router for=20
> backwards compatibility with legacy IS-IS routers. IID #0 is only used=20
> by MI-RTRs to convey information associated with such standard=20
> interface if implemented. See section 2.6 Interoperability Considerations=
 for more details."
> 4) Par 4, replace the two "may" with "can" to clarify the intent.
> 5) Par 5, change "defined" to "described" since the examples are not=20
> normative.
> 5) Par 5, add references to the (sub)sections containing the=20
> description of the two methods.
> 6) Par 7, move the last paragraph before listing the two examples and=20
> adjust the text accordingly, to improve the logical flow.
> 7) In the end of the Introduction add a reference: "This RFC is not=20
> backwards compatible with RFC 6822. Differences between this document=20
> and RFC 6822 are described in Annex A." ... so that others don't skip=20
> it by mistake as I did earlier...
>=20
 [Les:] Reading of the Appendix is optional - the new version is usable wit=
hout any need to refer to RFC 6822 - and that is its primary purpose.

> 2. Elements of Procedure
> 1) It seems that this section (informational) and its subsections=20
> (normative) use present and future times and, at times,  the normative=20
> language inconsistently both within the sections and among the=20
> sub-sections. Please, explain the reasons and improve consistency accordi=
ngly.
> 2) Par 1, clarify the scope by adding "within a routing domain" at the=20
> end of the first sentence.
> 3) Par 1, after the first sentence add a new sentence alone the=20
> following lines "Routers form adjacencies and exchange routing updates=20
> only if their IIDs correspond." This explains the basic premise of the wh=
ole mechanism.
> 4) Par 2, change "may" to "can" or "might" for consistency.
>=20
> Section 2.1
> 1) Par 2, change "may" to "MAY".
> 2) Par 3, remove "supported by legacy systems" from the first sentence=20
> to avoid confusion. My understanding is that IID #0 is reserved  for=20
> use by MI- RTRs that also implement the standard instance and=20
> advertise it in IIH using IID-TLV.
> 3) Par 3, change "except where noted" to "except as noted in section=20
> 2.6.2 (?)".  This is an excellent place to explain the logic behind=20
> this MUST NOT statement or, at least, state the general circumstances=20
> where IID #0 is included in IID-TLV.
> 4) Par 9 (4th after the picture), change "as described later" to " as=20
> described in section 2.6.2 (?)".
> 5) Par 13, change "recommended" to "RECOMMENDED".
> 6) Editorial: Par 13, change "particularf" to "particular".
>=20
[Les:] #6 - Agreed.

> Section 2.2
> 1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as=20
> well and which packets are used to advertise it.
> 2) Rephrase "marks ... by including" to "MUST include" to use=20
> requirements language.
>=20
> Section 2.3
> Editorial: Replace "normal" with "usual".
>=20
> Section 2.4.1
> 1) Par 1. Replace "IID #0" with "standard instance".
> 2) Par 1. Replace "instances other than IID #0" with "non-zero instances"=
.
> 3) Par 2 second sentence. What does it mean "normal expectations"? Is=20
> this a network configuration requirement? Please, clarify in the text.
>=20
> Section 2.4.2 Improve language consistency
> 1) Verbs are used inconsistently: some are used in present time,=20
> others in future time.
>=20
> Section 2.5, replace "exists" with "MUST be performed".
> Section 2.5.1, replace "only operates" with "MUST only be performed".
> Section 2.5.2, replace "This requires" with "It is REQUIRED".
> Section 2.5.2 third sentence, after "inconsistent" insert "due to=20
> their configuration". (Please, correct me if I am wrong.)
>=20
> Section 2.6.1
> 1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid"=
.
> 2) Par 2, remove "(IID #0)".
> 3) Par 2, replace "non-zero IID" with "non-zero instance".
> 4) Par 5 NOTE, replace "IID #0" with "standard instance".
>=20
> Section 2.6.2
> Replace all four appearances of "IID #0" with "standard instance".
>=20
> Section 3.1
> Replace the two "MAY" to "can".
>=20
> 7 Security Considerations
> Discuss possible additional security considerations (or the lack of=20
> them) related to the exposure of "instances" on the wire.
> Reason: Beyond the normal IETF procedure, this is especially important=20
> because "multiple instances allow isolation of resources..." Can this=20
> isolation, if observed or interfered on the wire, be damaging beyond=20
> the previous "standard instance" situation.
>=20

[Les:] There are no security concerns associated with the use of multiple i=
nstances.
Security reviews of the document have been satisfied w the current contents=
.

   Les

> Thanks,
> Orit.
> -----Original Message-----
> From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> Sent: Saturday, April 8, 2017 4:23 PM
> To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Orit -
>=20
> Thanx for the review.
> Responses inline.
>=20
> > -----Original Message-----
> > From: Orit Levin [mailto:oritl@microsoft.com]
> > Sent: Thursday, April 06, 2017 8:27 PM
> > To: gen-art@ietf.org
> > Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> > Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area=20
> > Review Team (Gen-ART) reviews all IETF documents being processed by=20
> > the IESG for the IETF Chair.  Please treat these comments just like=20
> > any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-isis-mi-bis-02
> > Reviewer: Orit Levin
> > Review Date: 2017-04-06
> > IETF LC End Date: 2017-04-07
> > IESG Telechat date: 2017-04-13
> >
> > Summary: This draft is "ready with issues" for publication.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > 1. Add text explaining the reason (or reasons) for replacing the=20
> > original RFC
> > 6822 from 2012.
> > Reason: It is a "bis" draft and there is no mention about it in the tex=
t.
>=20
> [Les:] Note that the latest revision of the draft correctly identifies=20
> the draft as obsoleting RFC 6822. Previous versions had incorrectly=20
> identified this as an update to RFC 6822.
> This is then the new Standard for the IS-IS MI support.
>=20
> There are two classes of future readers of this document:
>=20
> a)Readers who are unfamiliar with RFC 6822. For them what changed=20
> between RFC 6822 and this document is irrelevant.
>=20
> b)Readers who are familiar with RFC 6822. For them it is useful to=20
> know what changed - which is described in Appendix A.
>=20
> In order not to distract readers of type "a" - as well as to provide=20
> an "uninterrupted" description of the normative behavior I believe=20
> placement of the change description in an Appendix improves the=20
> readability of the document.
>=20
> Does this make sense to you?
>=20
> > 2. In Abstract, state clearly that this standard introduces the=20
> > support for instances vs. other already existing concepts also=20
> > listed in the Abstract (i.e., circuits, adjacencies,  topologies, etc.)=
.
>=20
> [Les:] The Abstract currently says:
>=20
> "This draft describes a mechanism that allows a single router to share
>    one or more circuits among multiple Intermediate System To
>    Intermediate System (IS-IS) routing protocol instances."
>=20
> Previous to this extension, a router could have multiple instances of=20
> the IS-IS protocol, but multiple instance could not be run over the same =
interface.
> So we are not introducing "instances", but we are introducing the=20
> ability to enable multiple instances on the same interface.
>=20
> > Reason: The wording is not clear about what is the new feature vs.
> > what are the new benefits vs. what was the original baseline
>=20
> >3. Throughout the
> > document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> > Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are=20
> >used  interchangeably throughout the document. It seems that they all=20
> >refer to the  same thing - the implementation of the original=20
> >protocol without the concept  of instances. Please, correct me if I am w=
rong.
>=20
> [Les:]  I don't think this is possible without seriously compromising=20
> the document. For example:
>=20
> Section 2.1
>=20
> " IID #0 is reserved for the standard instance supported by legacy
>    systems. "
>=20
> Changing this to  " Standard instance is reserved for the standard instan=
ce ..."
>=20
> Is clearly nonsensical.
>=20
> Later in Section 2.1
>=20
> "When the IID =3D 0, the list of supported ITIDs MUST NOT be present."
>=20
> What is being discussed here is what is the correct behavior when an=20
> MI- capable router sends a PDU associated IID #0 and includes the new IID=
 TLV.
> Replacing this with "When the standard instance..." loses the=20
> important point that the value of the IID in the IID TLV in this case is =
"0".
>=20
> Hope this helps clarify things.
>=20
> > 4. In section 2 par 3, change "support" and "operates" to "MUST=20
> > support" to use requirements language.
>=20
> [Les:] I am on the fence as regards this change. Section 2 is an=20
> introduction to the following sub-sections - which define the=20
> normative behavior. But the introduction itself is not defining=20
> normative behavior - it is providing a context in which the protocol=20
> extensions defined in the following sub- sections can be understood.
>=20
> I am more inclined to change the "MAY" used later in the same=20
> paragraph you mention to "may" so it is consistent with the rest of this =
section.
>=20
> ???
>=20
>=20
> > 5. In section 2 par 2, change "may" to either "can" or "MAY" to=20
> > clarify the intent.
>=20
> [Les:] Did you mean Section 2.1 para 2?
> If so I agree to the change.
>=20
> > 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on t=
he wire.
>=20
> [Les:] There are numerous places in the document where the legal use=20
> of IID
> #0 is discussed. I do not understand how a reader would conclude that=20
> IID #0 is never sent on the wire.
>=20
> > Explain the concept of the "standard interface" (see previous=20
> > comment)
>=20
> [Les:] There is no mention of "standard interface" - did you mean=20
> "standard instance"?
>=20
> If so, Section 1 paragraph 4 states:
>=20
> "Legacy routers support the standard
>    or zero instance of the protocol."
>=20
>    Les


From nobody Mon Apr 17 21:03:52 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 126E4120454 for <ietf@ietfa.amsl.com>; Mon, 17 Apr 2017 21:03:51 -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 VQFepdJJ0Mja for <ietf@ietfa.amsl.com>; Mon, 17 Apr 2017 21:03:49 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 99C301270A7 for <ietf@ietf.org>; Mon, 17 Apr 2017 21:03:49 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id c198so74634742pfc.1 for <ietf@ietf.org>; Mon, 17 Apr 2017 21:03:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:from:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=lVXVsKsWhXkECvocbZ50mKQ4RmTRHxFFA2s+B2AK4Sw=; b=UMuG3AbyGmlRIrgm0qTo+ztXFNcnOm2njfrZT5leERLb8jkracUqskhLi5IAa3Ce/9 N/QsfJARsaCx+kj3zOz+n0SIbpTjDI08gIgqbOlGo94h2VlIlrCaE8Y95jzltu0U74yY M4faJBF6eeU0eGfzZ9pHbkSzg/S4fRiFQ2QsNsjNK49docHFfL/hoffIvgK7mQVnaTdv OeqTVmSP2stfNcspZIO9IbboPeQP+s5T0zCmVo8OtqI+x23BrVT+y5n1qkwoQcPWGOU+ cOnzh8lGpydmm3r4elXyBvlZCEnmJmn5INuhRxG0UfApwLtRUvifvx0vgxJa852H4E4C KHfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:from:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=lVXVsKsWhXkECvocbZ50mKQ4RmTRHxFFA2s+B2AK4Sw=; b=PeFTv3KgLCr1HDaX3F0PmE0d+t6ispLHEoE3SJxqz9jAYK2m0ukc0zMY9r0PiZvHGs j6e+OQSwJ/MGYctS9+M7FbuT7HrmFsQFUxWlDjYOxkrUF5NF6+LdnEIUe1W1mioPUhv9 GddKDDAQ0yGyonOjeHFYFZ7CGbG+W4faEmB2aUpGztlSAp0Tqr3Sp5cr+dqtM/hTvNYF 4vQUbPl/xRwos4BYY5CW/VRvFGgSE6IwJVm1zwrUST022kOhhjHaLYwPI3SBWIdMbcSj CO3G95dEVBUdsabRotSL7YM651EAbyUZ+u7orQXBu1fJWVTnmHqPirM5xXMM6UrGBZIL veDA==
X-Gm-Message-State: AN3rC/6vw+kRCP2cXOEFJnfrMrCyFfJA6KIFBHUAw4uena/zjZ8aAhuE i9wLEvo9X3MSFQPb
X-Received: by 10.84.225.18 with SMTP id t18mr20011570plj.118.1492488228914; Mon, 17 Apr 2017 21:03:48 -0700 (PDT)
Received: from ?IPv6:2406:e001:3f9b:1:28cc:dc4c:9703:6781? ([2406:e001:3f9b:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g66sm10986565pfj.11.2017.04.17.21.03.46 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Apr 2017 21:03:47 -0700 (PDT)
Subject: =?UTF-8?Q?RIP_Bob_Taylor:_Internet=2c_desktop_PC_pioneer_powers_dow?= =?UTF-8?Q?n_at_85_=e2=80=a2_The_Register?=
To: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <742fd30c-f9e1-d787-c695-fcd9332a39e3@gmail.com>
Date: Tue, 18 Apr 2017 16:03:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W4PeozZDBmyRgXZMSKg3r2s8zOI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 04:03:51 -0000

Here is sad news about somebody we all owe a lot to:
http://www.theregister.co.uk/2017/04/17/obituary_bob_taylor/

Regards
   Brian Carpenter



From nobody Mon Apr 17 23:49:17 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D66127077; Mon, 17 Apr 2017 23:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 2F4hiGK-YXXS; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 1CB6D1201F2; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c80so25193812lfh.3; Mon, 17 Apr 2017 23:49:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=Gg1sfv5x2Bu/sbnTz4vsZOvQUKRhIquqmIoNHeqfRxczIua2KNSpmvm2lHLqY6VnRL LxtPwi1cA8EnTDCXqPgXUyexNoSXQBQQb26857mvSThe+a6uz9NZldlp66WoC8ndLYJy x1ThhMGfN1Z1UaSQr98bg/ftIX2RQpLakVqOgN9TcV+szLNtguiaZ9SaAVL+gRaxgegb pW51A4Qk13gA/I9FfopvNwVFkO7UJUu17EOIDbp+Dtdk6GuZz5/t+FH/smQ1SCo6gODO 2Ph1tUrnXcJ+Cy2g9SgWcsFx9jtS+HkghaxV7L4YZ8q2Mu1ltPZEzvziHnJ0ldk9eQ+I UDWg==
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=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=gZrSf/7eRV2Li+glLB6UxSgcSEKVvoDWku/NO8G7WNQfgv8cugS2MuHzuNhu/3akPp Dq8jAnJXjBXxq2v160RTjc91jYJF9lpyeXpCuKbhm1DB1xxOG1sqj7cCHZJJKtDfZaaQ iRk/WRRVkQkeAmuEb5ajLBW4J710u8Gl7MWpPdjWVKGTVCQXq4/nVWs9C0YljKI0nYAl mLofFjcck/JZJkpn+nAl+wf9r7zh+W7xAPq/U459OnW8Gjk5iBLCqaFXSa01ngEyEoXN Okq5kBTBrB3gwsLXM5CFc73PL18vudvXlfhC5iemsqPjR5TCCoEb+5P6Ab5JuTXF47cV ocaA==
X-Gm-Message-State: AN3rC/5Jzmytpy9S5dF0kW1vmHys7Je9RreFlMrbz535Q/Q9v/mm0T6g SAU12lJ8/sBH+6hi+vuFHd3CCH74WQ==
X-Received: by 10.25.79.27 with SMTP id d27mr2802667lfb.76.1492498153390; Mon, 17 Apr 2017 23:49:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.5 with HTTP; Mon, 17 Apr 2017 23:49:12 -0700 (PDT)
In-Reply-To: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
References: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 18 Apr 2017 16:49:12 +1000
Message-ID: <CABkgnnUFBGngUzqM0GjpwyvF0w9pCB3eqFgxL8LY_R1otp49dw@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-httpbis-encryption-encoding-08
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/umxsWAYrMeLwex4yAvU6QkZGlEw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 06:49:17 -0000

Thanks Pete,

On 6 April 2017 at 15:52, Pete Resnick <presnick@qti.qualcomm.com> wrote:
>       A "keyid" parameter SHOULD be a UTF-8
>       [RFC3629] encoded string, particularly where the identifier
> might
>       need to appear in a textual form.
>
> I presume that simply means "might need to be rendered" and does not
> include "might need to be typed in by someone", correct? The former is
> easy; the latter probably requires a bit more text.

Indeed.  Until we have a good copy-and-paste version of the Unicode
typed/spoken/interpretive-danced input problem for security
identifiers, it is not a goal to have specifications casually tackling
problems that are outside their (and maybe anyone's) capabilities.

I made the suggested change in the editor's copy.


From nobody Tue Apr 18 05:47:46 2017
Return-Path: <hvdsomp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D45B312EB88; Tue, 18 Apr 2017 05:47:31 -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 JkQQnjBunmpA; Tue, 18 Apr 2017 05:47:29 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 05FDF12420B; Tue, 18 Apr 2017 05:47:29 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id c45so123688668qtb.1; Tue, 18 Apr 2017 05:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lsAj+8l6lI8C4/5VmvmY1YQ0PuxbxkFimPzx4OG+Ucg=; b=kVFBzdI8Y3UxFPQ4GjXLSxNulNR1YSu2SfzzFqQNUhqE6gA1vAjRd5o01rOHd0nkr2 13M6SH4iucDzFh3qSIDYffOIOM/e5km9lAiltLu4uz3ijwfT9z0MIct5SWEwYGl0bHr4 bu5O4HSpP8I1o56sjGLjt22+UPd5tBIE6T4iXDk7pgW6vRuDQUhzkiOU+MXENw7edYS9 dR5OmkiWAdRnEIl58XcnOQPo9cXegxGL5+9Jx68df/DTjTurJDZMimh4jEbR6vz6sDbC 16qiXV0BcAr9HPSBztgmj9RRpYxtnw+3wyckMM4PKkzDfIgHuVF4V/wFuJYMk58NevpH +org==
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=lsAj+8l6lI8C4/5VmvmY1YQ0PuxbxkFimPzx4OG+Ucg=; b=KoyG2fW14GBjX661JMEBcreXt1stXg6fDfqnpouh+zj87evLXqdPeerOAjTVafXkHW +jn8ing+XbMO3mYSQ3C0e91YfsQYlAYvg+kw8lL90IFNbgtb3XG5sb75EhcHsR+aq5vy Q3w9jEAEafYIeDot1BAOqxAgNMzwbg8ReC9rSQpBR/8cW3ttcADMIFW/BRNrMMHpqXYW 0bX1rJKu0pZclpU7Ydbk3jhBiK8aXy1MAGjCX/9F3v2SzGnQXYb0Lk/zXL/1Q4jqOzsz Wu/rmT0va25mNOVydGNyGW0EIDA7HwpgBnVfzduDJGsW5KZ3AbSE2Bc3CMR7rQjgVMpk uJwQ==
X-Gm-Message-State: AN3rC/40XV7Wzb/BZU4TZ/6sGhyJfb0y61pZHSDWiVUTYHgpgeq/1Vzo 6ck9kpbqab704nMg6Qhy6A9yJg7AGg==
X-Received: by 10.200.36.240 with SMTP id t45mr12970125qtt.230.1492519648189;  Tue, 18 Apr 2017 05:47:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.45.162 with HTTP; Tue, 18 Apr 2017 05:47:27 -0700 (PDT)
In-Reply-To: <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org>
From: Herbert Van de Sompel <hvdsomp@gmail.com>
Date: Tue, 18 Apr 2017 14:47:27 +0200
Message-ID: <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com>
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Carsten Bormann <cabo@tzi.org>
Cc: Mark Nottingham <mnot@mnot.net>, art@ietf.org, ietf@ietf.org,  "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org,  Herbert Van de Sompel <hvdsomp@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140eede73628d054d704f68
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vlSgZNVxO4gE_OT4NeBWVM4qAWQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 12:47:32 -0000

--001a1140eede73628d054d704f68
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

hi Mark, Carsten,

Sorry to be a bit late to the game.

Two things:

1. I would be very interested in documents serialized according to
application/link-format+json as described in the I-D, especially in the
context of an I-D Erik Wilde and I are authoring regarding Link Sets, see
https://datatracker.ietf.org/doc/draft-wilde-linkset-link-rel/

2. Regarding Mark's comment "This means that any constraints upon RFC6690
documents are also
mirrored into these formats": Mark mentions IRIs as a concern. I am also
concerned about the rules for interpretation of (the Context IRI of) links
as described in Section 2.1 of 6690 (
https://tools.ietf.org/html/rfc6690#section-2.1). It seems to me that these
also introduce constraints that go beyond 5988. I may be mistaken with that
regard because I have never fully understood that section of 6690 (i.e. the
use of "base URI", "origin", "Context URI"). But, when compared to 5988,
the section comes across as imposing constraints that are intended to allow
the straightforward use of relative URIs in constrained environments as a
means to decrease the payload. If my interpretation is correct, then I
would very much favor spec-ing the json link format in terms of 5988 rather
than 6690.

Cheers

Herbert Van de Sompel



On Tue, Apr 11, 2017 at 9:33 AM, Carsten Bormann <cabo@tzi.org> wrote:

> Hi Mark,
>
> thank you a lot for another thoughtful review.
>
> I don=E2=80=99t have an opinion yet on what we should do here, so I=E2=80=
=99ll supply some
> more background first.
>
> The present spec is first and foremost intended to round-trip with RFC
> 6690, which is indeed stuck a bit on HTTP Link header field syntax.
> However, the way this is used in practice is not meant to inherit the
> complexities of HTTP header field coding.  E.g., for CoRE Resource
> Directory and its DNS-SD compatibility, we want to represent a DNS-SD
> instance identifier (which is UTF-8) as a link attribute.  This is not a
> problem in JSON or CBOR, but also not in the way RFC 6690 is being used,
> i.e. as a UTF-8 based format.
>
> I haven=E2=80=99t checked yet what 5988bis brings to the table and how to=
 track
> this in 6690 or possibly a 6690bis.  There is no point in Big Web and Thi=
ng
> Web diverging here, so we should follow the lead.  But maybe that would
> touch both 6690 and the present document once 5988bis is done.
>
> More importantly, we haven=E2=80=99t really put a lot of thinking into IR=
I
> support.  The CoAP data type =E2=80=9Cstring=E2=80=9D which is used for U=
RI components such
> as Uri-Path is UTF-8, so we could embrace them by extending the rules in
> section 6 of RFC 7252 to cover IRIs.  I=E2=80=99m sure that, in practice,=
 CoAP
> implementations already do this =E2=80=94 it is not distinguishable in th=
e CoAP
> packet whether the (decomposed) CoAP Uri components have been derived fro=
m
> URIs or IRIs.  But the metadata formats (6690 and its JSON/CBOR
> representations; various other JSON and CBOR based formats, e.g. from OCF=
)
> are still based on RFC 3986 URIs, except where they also use the CoAP
> decomposed form (e.g., CORAL).
>
> While this is outside the scope of the CoRE WG, I personally would like t=
o
> explore how link-format+cbor/+json could be useful for the Big Web.  If
> embracing IRIs there is all we need to make this happen, maybe that can b=
e
> added with a warning that IRIs have to be converted back to URIs for 6690
> link-format.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
> > On Apr 11, 2017, at 05:49, Mark Nottingham <mnot@mnot.net> wrote:
> >
> > Reviewer: Mark Nottingham
> > Review result: Ready with Issues
> >
> > This specification is a relatively straightforward mapping of the
> > format described in RFC6690 (itself a serialisation of RFC5988bis
> > links) into JSON and CBOR. I don't have deep knowledge of CBOR, but
> > given the editorship of the document, I trust it's seen adequate
> > review in that regard.
> >
> > The only potential issue is how this is achieved. Rather than defining
> > two new serialisations of RFC5988bis links (into JSON and CBOR), it
> > describes how to re-serialise RFC6690 documents into JSON and CBOR.
> > This means that any constraints upon RFC6690 documents are also
> > mirrored into these formats; e.g., the target IRI is constrained to be
> > a URI in 6690, and therefore can also only be a URI in JSON and CBOR,
> > despite these formats' ability to easily convey non-ASCII content.
> >
> > In other words, the specification currently defines these link formats
> > in terms of the Link header (as defined in section 5 of RFC5988) --
> > along with all of the foibles of HTTP header syntax -- rather than
> > their abstract model (defined in Section 3).
> >
> > Whether or not this is a problem depends on what's desired; if 6690 is
> > seen as effectively a profile of 5988, then it makes sense to express
> > it in those terms. If the full range of links capable of being
> > expressed in 5988 is desired, creating new serialisations of 5988
> > links (without a hop through 6690) is preferable.
> >
> > If the current approach is kept, it'd be nice to clarify this
> > situation a bit in the Introduction.
> >
> >
> > _______________________________________________
> > art mailing list
> > art@ietf.org
> > https://www.ietf.org/mailman/listinfo/art
> >
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>



--=20
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/
http://orcid.org/0000-0002-0715-6126

=3D=3D

--001a1140eede73628d054d704f68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">hi Mark, Carsten,<div><br></div><div>Sorry to be a bit lat=
e to the game.</div><div><br></div><div>Two things:</div><div><br></div><di=
v>1. I would be very interested in documents serialized according to applic=
ation/link-format+json as described in the I-D, especially in the context o=
f an I-D Erik Wilde and I are authoring regarding Link Sets, see <a href=3D=
"https://datatracker.ietf.org/doc/draft-wilde-linkset-link-rel/">https://da=
tatracker.ietf.org/doc/draft-wilde-linkset-link-rel/</a></div><div><br></di=
v><div>2. Regarding Mark&#39;s comment &quot;<span style=3D"font-size:12.8p=
x">This means that any constraints upon RFC6690 documents are also</span></=
div><span style=3D"font-size:12.8px">mirrored into these formats&quot;: Mar=
k mentions IRIs as a concern. I am also concerned about the rules for inter=
pretation of (the Context IRI of) links as described in Section 2.1 of 6690=
 (<a href=3D"https://tools.ietf.org/html/rfc6690#section-2.1">https://tools=
.ietf.org/html/rfc6690#section-2.1</a>). It seems to me that these also int=
roduce constraints that go beyond 5988. I may be mistaken with that regard =
because I have never fully understood that section of 6690 (i.e. the use of=
 &quot;base URI&quot;, &quot;origin&quot;, &quot;Context URI&quot;). But, w=
hen compared to 5988, the section comes across as imposing constraints that=
 are intended to allow the straightforward use of relative URIs in constrai=
ned environments=C2=A0as a means to decrease the payload. If my interpretat=
ion is correct, then I would very much favor spec-ing the json link format =
in terms of 5988 rather than 6690.</span><div><span style=3D"font-size:12.8=
px"><br></span></div><div><span style=3D"font-size:12.8px">Cheers</span></d=
iv><div><span style=3D"font-size:12.8px"><br></span></div><div><span style=
=3D"font-size:12.8px">Herbert Van de Sompel<br></span><div><span style=3D"f=
ont-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8px">=C2=
=A0</span></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Tue, Apr 11, 2017 at 9:33 AM, Carsten Bormann <span dir=3D"ltr">&lt=
;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Hi Mark,<br>
<br>
thank you a lot for another thoughtful review.<br>
<br>
I don=E2=80=99t have an opinion yet on what we should do here, so I=E2=80=
=99ll supply some more background first.<br>
<br>
The present spec is first and foremost intended to round-trip with RFC 6690=
, which is indeed stuck a bit on HTTP Link header field syntax.=C2=A0 Howev=
er, the way this is used in practice is not meant to inherit the complexiti=
es of HTTP header field coding.=C2=A0 E.g., for CoRE Resource Directory and=
 its DNS-SD compatibility, we want to represent a DNS-SD instance identifie=
r (which is UTF-8) as a link attribute.=C2=A0 This is not a problem in JSON=
 or CBOR, but also not in the way RFC 6690 is being used, i.e. as a UTF-8 b=
ased format.<br>
<br>
I haven=E2=80=99t checked yet what 5988bis brings to the table and how to t=
rack this in 6690 or possibly a 6690bis.=C2=A0 There is no point in Big Web=
 and Thing Web diverging here, so we should follow the lead.=C2=A0 But mayb=
e that would touch both 6690 and the present document once 5988bis is done.=
<br>
<br>
More importantly, we haven=E2=80=99t really put a lot of thinking into IRI =
support.=C2=A0 The CoAP data type =E2=80=9Cstring=E2=80=9D which is used fo=
r URI components such as Uri-Path is UTF-8, so we could embrace them by ext=
ending the rules in section 6 of RFC 7252 to cover IRIs.=C2=A0 I=E2=80=99m =
sure that, in practice, CoAP implementations already do this =E2=80=94 it i=
s not distinguishable in the CoAP packet whether the (decomposed) CoAP Uri =
components have been derived from URIs or IRIs.=C2=A0 But the metadata form=
ats (6690 and its JSON/CBOR representations; various other JSON and CBOR ba=
sed formats, e.g. from OCF) are still based on RFC 3986 URIs, except where =
they also use the CoAP decomposed form (e.g., CORAL).<br>
<br>
While this is outside the scope of the CoRE WG, I personally would like to =
explore how link-format+cbor/+json could be useful for the Big Web.=C2=A0 I=
f embracing IRIs there is all we need to make this happen, maybe that can b=
e added with a warning that IRIs have to be converted back to URIs for 6690=
 link-format.<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
&gt; On Apr 11, 2017, at 05:49, Mark Nottingham &lt;<a href=3D"mailto:mnot@=
mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Reviewer: Mark Nottingham<br>
&gt; Review result: Ready with Issues<br>
&gt;<br>
&gt; This specification is a relatively straightforward mapping of the<br>
&gt; format described in RFC6690 (itself a serialisation of RFC5988bis<br>
&gt; links) into JSON and CBOR. I don&#39;t have deep knowledge of CBOR, bu=
t<br>
&gt; given the editorship of the document, I trust it&#39;s seen adequate<b=
r>
&gt; review in that regard.<br>
&gt;<br>
&gt; The only potential issue is how this is achieved. Rather than defining=
<br>
&gt; two new serialisations of RFC5988bis links (into JSON and CBOR), it<br=
>
&gt; describes how to re-serialise RFC6690 documents into JSON and CBOR.<br=
>
&gt; This means that any constraints upon RFC6690 documents are also<br>
&gt; mirrored into these formats; e.g., the target IRI is constrained to be=
<br>
&gt; a URI in 6690, and therefore can also only be a URI in JSON and CBOR,<=
br>
&gt; despite these formats&#39; ability to easily convey non-ASCII content.=
<br>
&gt;<br>
&gt; In other words, the specification currently defines these link formats=
<br>
&gt; in terms of the Link header (as defined in section 5 of RFC5988) --<br=
>
&gt; along with all of the foibles of HTTP header syntax -- rather than<br>
&gt; their abstract model (defined in Section 3).<br>
&gt;<br>
&gt; Whether or not this is a problem depends on what&#39;s desired; if 669=
0 is<br>
&gt; seen as effectively a profile of 5988, then it makes sense to express<=
br>
&gt; it in those terms. If the full range of links capable of being<br>
&gt; expressed in 5988 is desired, creating new serialisations of 5988<br>
&gt; links (without a hop through 6690) is preferable.<br>
&gt;<br>
&gt; If the current approach is kept, it&#39;d be nice to clarify this<br>
&gt; situation a bit in the Introduction.<br>
&gt;<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; art mailing list<br>
&gt; <a href=3D"mailto:art@ietf.org">art@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/art</a><br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
art mailing list<br>
<a href=3D"mailto:art@ietf.org">art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/art</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Herbert V=
an de Sompel<br>Digital Library Research &amp; Prototyping<br>Los Alamos Na=
tional Laboratory, Research Library<br><a href=3D"http://public.lanl.gov/he=
rbertv/" target=3D"_blank">http://public.lanl.gov/herbertv/</a><br><a href=
=3D"http://orcid.org/0000-0002-0715-6126" target=3D"_blank">http://orcid.or=
g/0000-0002-0715-6126</a><br><br>=3D=3D</div>
</div></div>

--001a1140eede73628d054d704f68--


From nobody Tue Apr 18 06:41:30 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E99D12EC51; Tue, 18 Apr 2017 06:41:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-grow-large-communities-usage-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
Date: Tue, 18 Apr 2017 06:41:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kxD0XmWLvkkL1LoEdJXCu3DmwJM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 13:41:16 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-grow-large-communities-usage-??
Reviewer: Stewart Bryant
Review Date: 2017-04-18
IETF LC End Date: 2017-04-21
IESG Telechat date: Not scheduled for a telechat

Summary:

This is mostly a well written document, although unfortunately there
are a number of matters that really need to be looked at.

Major issues:

Abstract

   Examples and inspiration for operators to use BGP Large
Communities.

SB> Even if you just copy the Introduction, the Abstract should really
be expanded
SB> to help the reader understand whether or not they want read the
RFC
SB> or if they had read it what it was about.

============

5.  Security Considerations

   Operators should note the recommendations in Section 11 of BGP
   Operations and Security [RFC7454].

SB> You do not address the question of whether there are new
considerations, or considerations
SB> that are of increased importance? Is there is text somewhere
SB> that discusses the integrity and synchronization of the
parameters
SB> and any consequences that arise?

===========

Minor issues:

2.2.  Action Communities

   Action Communities are added as a label to request that a route be
   treated in a particular way within an AS.  The operator of the AS
   defines a routing policy that adjusts path attributes based on the
   community.  For example, the route's propagation characteristics,
the
   LOCAL_PREF (local preference), the next-hop, or the number of
AS_PATH
   prepends to be added when it is received or propagated can be
   changed.

SB> Although these are well known to the target audience, I think you
SB> need some references in the above para.


Nits/editorial comments: 

6.  IANA Considerations

   None.

SB> A little briefer than normal. 


From nobody Tue Apr 18 06:57:45 2017
Return-Path: <aretana@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3D612EC82; Tue, 18 Apr 2017 06:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.121
X-Spam-Level: 
X-Spam-Status: No, score=-13.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_HTML_ATTACH=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 MLd-hFo8HQPc; Tue, 18 Apr 2017 06:57:40 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09ED912EC9E; Tue, 18 Apr 2017 06:57:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=125121; q=dns/txt; s=iport; t=1492523860; x=1493733460; h=from:to:cc:subject:date:message-id:mime-version; bh=TxqjEgbpGI6k28SWo+l/otFetqWi7I6fW98QBdX9A84=; b=h12JDD6tmpHrU6Hsel+dmUVNKnXkIna4siWkBuy6hYAngEbhl8jKz7Wy i1S2Ff4VJDIOxhCsT/GnGqj/95RHwB8JO3KFkku1dfoVx4q4O4jM2w1Tj WxKXsbQr8JMbN1KVIjULqOn6DafFm0RXqeM4saJklkw8bmP+q8ZuKnqEd A=;
X-Files: Diff_ draft-ietf-sidr-bgpsec-protocol-22-download.txt - draft-ietf-sidr-bgpsec-protocol-23.txt[1].html : 75707
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C8AQCSGvZY/4cNJK1CGhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJuOithgQsHg1+CBoIfhXCnRIIPMIQagVocg1gVKhgBAgEBAQE?= =?us-ascii?q?BAQFrHQuFGhwBCAo6EhIBQAEJAgQwJwQOBQkFBooFDjGoWBCBIIImK4p3AQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBDg+GUoFcASuGBYEGFjoVglougjEFhReEFQeNAYI?= =?us-ascii?q?yhDwBg32DBoEAhVaFEIIAGTyBC4NRiF2BOohrhnuEJwEfOBVwYxVEEQGEGzYDH?= =?us-ascii?q?IFjdQEEhkoBJAeBA4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,219,1488844800";  d="html'217?scan'217,208,217";a="409018703"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Apr 2017 13:57:37 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v3IDvbJG007116 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 18 Apr 2017 13:57:37 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 18 Apr 2017 08:57:36 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Tue, 18 Apr 2017 08:57:36 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-sidr-bgpsec-protocol@ietf.org" <draft-ietf-sidr-bgpsec-protocol@ietf.org>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>
Subject: Modification to draft-ietf-sidr-bgpsec-protocol after IESG Approval
Thread-Topic: Modification to draft-ietf-sidr-bgpsec-protocol after IESG Approval
Thread-Index: AQHSuEu7elkQV/cZ6UWBAunm2r6P1g==
Date: Tue, 18 Apr 2017 13:57:36 +0000
Message-ID: <6F27B6F2-25AB-4D8D-B6E1-866E147B6CAA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: multipart/mixed; boundary="_004_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/usHYiAEvdqWgpFLpsdIbRCICg-c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 13:57:43 -0000

--_004_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_
Content-Type: multipart/alternative;
	boundary="_000_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_"

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

SGVsbG8hDQoNClRoaXMgbWVzc2FnZSBpcyB0byBpbmZvcm0gdGhlIGNvbW11bml0eSBvZiBhIG1v
ZGlmaWNhdGlvbiB0byBkcmFmdC1pZXRmLXNpZHItYmdwc2VjLXByb3RvY29sIGFmdGVyIElFVEYg
TGFzdCBDYWxsIGFuZCBldmVuIElFU0cgQXBwcm92YWwuICBJIHdpbGwgZ28gZm9yd2FyZCB3aXRo
IHRoZSBwcm9wb3NlZCBjaGFuZ2VzIHVubGVzcyBJIGhlYXIgc2lnbmlmaWNhbnQgb2JqZWN0aW9u
IGJ5IEFwcmlsIDI2dGgsIDIwMTcuDQoNCg0K4oCcQkdQc2VjIFByb3RvY29sIFNwZWNpZmljYXRp
b27igJ0gKGRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtcHJvdG9jb2wpIFsxXSB3ZW50IHRocm91Z2gg
SUVURiBMYXN0IENhbGwgaW4gZWFybHkgRGVjZW1iZXIsIDIwMTYgWzJdLiAgVGhlIElFU0cgYXBw
cm92ZWQgcHVibGljYXRpb24gc29vbiBhZnRlciwgYW5kIHRoZSBkb2N1bWVudCBpcyBub3cgc2l0
dGluZyBpbiB0aGUgUkZDIEVkaXRvcuKAmXMgcXVldWUgd2FpdGluZyAoYWxvbmcgd2l0aCA2IG90
aGVyIGRlcGVuZGVudCBkb2N1bWVudHMgWzNdKSBmb3Ig4oCcRXh0ZW5kZWQgTWVzc2FnZSBzdXBw
b3J0IGZvciBCR1DigJ0gKGRyYWZ0LWlldGYtaWRyLWJncC1leHRlbmRlZC1tZXNzYWdlcykgWzRd
LCB3aGljaCBpcyBhIE5vcm1hdGl2ZSByZWZlcmVuY2UuICBBZnRlciBkaXNjdXNzaW9uIGluIHRo
ZSByZWxldmFudCBXR3MgKHNpZHIgKyBzaWRyb3BzIGFuZCBpZHIpIFs1XSwgd2Ugd2FudCB0byBy
ZW1vdmUgdGhhdCBkZXBlbmRlbmN5Lg0KDQpbVGw7ZHIgdmVyc2lvbl0gIEl0IHdhcyB0aG91Z2h0
IHRoYXQgQkdQc2VjIHdvdWxkIG5lZWQgZXh0ZW5kZWQgQkdQIG1lc3NhZ2VzIGJlY2F1c2Ugb2Yg
dGhlIHNpZ25hdHVyZXMgaW5jbHVkZWQgaW4gdGhlIFVwZGF0ZXMuICBCdXQgd2l0aCB0aGUgY3Vy
cmVudCBhbGdvcml0aG1zIFs2XSwgaXQgaXMgZXhwZWN0ZWQgdGhhdCB3ZSB3b3VsZCBwYXNzIHRo
ZSBjdXJyZW50IG1heGltdW0gQkdQIG1lc3NhZ2Ugc2l6ZSAob2YgNGsgb2N0ZXRzKSBpZiB0aGUg
QVMgcGF0aCBsZW5ndGggaXMgY2xvc2UgdG8gNDAg4oCTIHRoZSBjdXJyZW50IGF2ZXJhZ2Ugb2Jz
ZXJ2ZWQgb24gdGhlIEludGVybmV0IGlzIDwgNCwgYW5kIHRoZSBtYXhpbXVtIGlzIDE1IFs3XS4g
IElPVywgdGhlcmXigJlzIG5vIHJpc2sgb2YgbmVlZGluZyBiaWdnZXIgdXBkYXRlcyBhbnkgdGlt
ZSBzb29uLg0KDQpJ4oCZbSBhdHRhY2hpbmcgdGhlIHByb3Bvc2VkIGRpZmZzICgtMjMgaGFzIG5v
dCBiZWVuIHBvc3RlZCB5ZXQpLiAgUGxlYXNlIHRha2UgYSBsb29rLg0KVG8gc3VtbWFyaXplLCB0
aGUgY2hhbmdlcyBhcmU6ICgxKSByZW1vdmUgbWVudGlvbiBvZi9yZWZlcmVuY2VzIHRvIGRyYWZ0
LWlldGYtaWRyLWJncC1leHRlbmRlZC1tZXNzYWdlcywgYW5kICgyKSBhZGQgdGhlIGZvbGxvd2lu
ZyB0ZXh0IGluIFNlY3Rpb24gNC4xLiAoR2VuZXJhbCBHdWlkYW5jZSk6DQoNCiAgICBBbGwgQkdQ
c2VjIHVwZGF0ZSBtZXNzYWdlcyBNVVNUIGNvbmZvcm0gdG8gQkdQJ3MgbWF4aW11bSBtZXNzYWdl
DQogICAgc2l6ZS4gIElmIHRoZSByZXN1bHRpbmcgbWVzc2FnZSBleGNlZWRzIHRoZSBtYXhpbXVt
IG1lc3NhZ2Ugc2l6ZSwNCiAgICB0aGVuIHRoZSBndWlkZWxpbmVzIGluIFNlY3Rpb24gOS4yIG9m
IFJGQyA0MjcxIFtSRkM0MjcxXSBNVVNUIGJlDQogICAgZm9sbG93ZWQuDQoNCltGb3IgZWFzaWVy
IHJlZmVyZW5jZSwgSSBwdXQgdGhlIHJlbGV2YW50IHRleHQgZnJvbSA5LjIgYmVsb3cuXQ0KDQpU
aGUgcmVzdWx0IGlzIHRoZW4gdGhhdCBkcmFmdC1pZXRmLXNpZHItYmdwc2VjLXByb3RvY29sIGRv
ZXNu4oCZdCBkZXBlbmQgb24gZHJhZnQtaWV0Zi1pZHItYmdwLWV4dGVuZGVkLW1lc3NhZ2VzLiAg
SW5zdGVhZCwgd2hlbiByZWZlcnJpbmcgdG8gdGhlIHNpemUgb2YgdGhlIG1lc3NhZ2VzLCBpdCBk
ZXBlbmRzIG9uIHJmYzQyNzEsIHdoaWNoIGlzIHRoZSBiYXNlIEJHUCBTcGVjaWZpY2F0aW9uLiAg
SWYgdGhlIHNpemUgaXMgaW5jcmVhc2VkIGxhdGVyIChieSBkcmFmdC1pZXRmLWlkci1iZ3AtZXh0
ZW5kZWQgbWVzc2FnZXMgb3IgYW55IG90aGVyIGRvY3VtZW50KSwgdGhlbiByZmM0MjcxIHdvdWxk
IGhhdmUgdG8gYmUgVXBkYXRlZCBhbmQgQkdQc2VjIHdvdWxkIGJlIGFibGUgdG8gdXNlIHRoYXQg
ZmFjaWxpdHkgZnJvbSBCR1AgKHdpdGggbm8gVXBkYXRlcyB0byBCR1BzZWMpLg0KSW4gdGhlIHNw
aXJpdCBvZiBmdWxsIGRpc2Nsb3N1cmXigKYgIEJlc2lkZXMgQkdQc2VjIG5vdCBuZWVkaW5nIGV4
dGVuZGVkIG1lc3NhZ2VzLCBJIHJldHVybmVkIGRyYWZ0LWlldGYtaWRyLWJncC1leHRlbmRlZC1t
ZXNzYWdlcyB0byB0aGUgaWRyIFdHIGZvciBtb3JlIHByb2Nlc3NpbmcgYXMgYSByZXN1bHQgb2Yg
bXkgQUQgcmV2aWV3LiAgVGhpcyBhY3Rpb24gdHJpZ2dlcmVkIHRoZSBkaXNjdXNzaW9uIHRoYXQg
bGVkIHRvIHdhbnRpbmcgdG8gY2hhbmdlIHRoZSBkZXBlbmRlbmN5Lg0KDQpQbGVhc2UgbGV0IG1l
IGtub3cgaWYgeW91IGhhdmUgYW55IGNvbmNlcm5zLg0KR2l2ZW4gdGhhdCB0aGlzIGRvY3VtZW50
IGhhcyBhbHJlYWR5IGJlZW4gYXBwcm92ZWQgYnkgdGhlIElFU0csIHRoZSBwcm9jZXNzIGdvaW5n
IGZvcndhcmQgaXM6DQoNCi0gY29uc3VsdCB0aGUgV0cgKGRvbmUhKQ0KLSBpbmZvcm0gdGhlIElF
U0cgb2YgdGhlIGludGVudCAoZG9uZSEpDQotIGluZm9ybSB0aGUgaWV0ZkBpZXRmLm9yZyBvZiB0
aGUgY2hhbmdlcyAodGhpcyB0aHJlYWQpDQotIHB1Ymxpc2ggYW4gdXBkYXRlZCBkcmFmdA0KLSBj
b250aW51ZSB0aGUgcHVibGljYXRpb24gcHJvY2Vzcw0KDQpFYWNoIHN0ZXAgbWF5LCBvYnZpb3Vz
bHksIHJlcXVpcmUgYWRkaXRpb25hbCBkaXNjdXNzaW9uIGFuZCBjb3VsZCByZXN1bHQgaW4gY2hh
bmdlcyB0byB0aGUgY3VycmVudCBwbGFuLg0KDQpUaGFua3MhIQ0KDQpBbHZhcm8uDQoNCg0KWzFd
IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtc2lkci1iZ3BzZWMt
cHJvdG9jb2wvDQpbMl0gaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9pZXRm
LWFubm91bmNlL3RQNGhacEk0SW9jcHdpTHQwaTJRRUtkUFcxRS8/cWlkPWVmMTQ1NzQ4ZDk2NzJi
MDliOTllMTIwMmQzZDQzZjc2DQpbM10gaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvY2x1c3Rl
cl9pbmZvLnBocD9jaWQ9QzMwNg0KWzRdIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9j
L2RyYWZ0LWlldGYtaWRyLWJncC1leHRlbmRlZC1tZXNzYWdlcy8NCls1XSBodHRwczovL21haWxh
cmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL3NpZHIvNm1sUUdTUm45dGZCTEQ4bkd5T1RvSWU1NjJz
Lz9xaWQ9ZTNmZDBjYjhkM2E3ZDk0MTAzOTg3OTZiYTRjYjc3ZmINCls2XSBodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1hbGdzDQpbN10gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvOTgvc2xpZGVzL3NsaWRlcy05OC1zaWRyb3BzLWRlY291
cGxpbmctYmdwc2VjLWRvY3VtZW50cy1hbmQtZXh0ZW5kZWQtbWVzc2FnZXMtZHJhZnQtMDAucGRm
DQoNCg0KDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDI3MSNzZWN0aW9uLTkuMg0K
OS4yLiAgVXBkYXRlLVNlbmQgUHJvY2Vzcw0K4oCmDQogICBJZiwgZHVlIHRvIHRoZSBsaW1pdHMg
b24gdGhlIG1heGltdW0gc2l6ZSBvZiBhbiBVUERBVEUgbWVzc2FnZSAoc2VlDQogICBTZWN0aW9u
IDQpLCBhIHNpbmdsZSByb3V0ZSBkb2Vzbid0IGZpdCBpbnRvIHRoZSBtZXNzYWdlLCB0aGUgQkdQ
DQogICBzcGVha2VyIE1VU1Qgbm90IGFkdmVydGlzZSB0aGUgcm91dGUgdG8gaXRzIHBlZXJzIGFu
ZCBNQVkgY2hvb3NlIHRvDQogICBsb2cgYW4gZXJyb3IgbG9jYWxseS4NCg0K

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eTpDYWxpYnJpO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFu
LkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7
DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0Kc3Bhbi5tc29JbnMNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJbXNvLXN0eWxlLW5hbWU6IiI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTsNCgljb2xvcjp0ZWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9y
dC1vbmx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+
DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5r
PSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+SGVsbG8hPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5UaGlzIG1lc3NhZ2UgaXMgdG8gaW5mb3JtIHRo
ZSBjb21tdW5pdHkgb2YgYSBtb2RpZmljYXRpb24gdG8gZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1w
cm90b2NvbCBhZnRlciBJRVRGIExhc3QgQ2FsbCBhbmQgZXZlbiBJRVNHIEFwcHJvdmFsLiZuYnNw
OyBJIHdpbGwgZ28gZm9yd2FyZCB3aXRoIHRoZSBwcm9wb3NlZCBjaGFuZ2VzIHVubGVzcyBJIGhl
YXIgc2lnbmlmaWNhbnQNCiBvYmplY3Rpb24gYnkgQXByaWwgMjY8c3VwPnRoPC9zdXA+LCAyMDE3
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPuKAnEJHUHNlYyBQcm90b2NvbCBTcGVjaWZpY2F0aW9u4oCdIChkcmFmdC1p
ZXRmLXNpZHItYmdwc2VjLXByb3RvY29sKSBbMV0gd2VudCB0aHJvdWdoIElFVEYgTGFzdCBDYWxs
IGluIGVhcmx5IERlY2VtYmVyLCAyMDE2IFsyXS4mbmJzcDsgVGhlIElFU0cgYXBwcm92ZWQgcHVi
bGljYXRpb24gc29vbiBhZnRlciwgYW5kIHRoZSBkb2N1bWVudCBpcyBub3cgc2l0dGluZyBpbg0K
IHRoZSBSRkMgRWRpdG9y4oCZcyBxdWV1ZSB3YWl0aW5nIChhbG9uZyB3aXRoIDYgb3RoZXIgZGVw
ZW5kZW50IGRvY3VtZW50cyBbM10pIGZvciDigJxFeHRlbmRlZCBNZXNzYWdlIHN1cHBvcnQgZm9y
IEJHUOKAnSAoZHJhZnQtaWV0Zi1pZHItYmdwLWV4dGVuZGVkLW1lc3NhZ2VzKSBbNF0sIHdoaWNo
IGlzIGEgTm9ybWF0aXZlIHJlZmVyZW5jZS4mbmJzcDsgQWZ0ZXIgZGlzY3Vzc2lvbiBpbiB0aGUg
cmVsZXZhbnQgV0dzIChzaWRyICYjNDM7IHNpZHJvcHMgYW5kIGlkcikgWzVdLA0KIHdlIHdhbnQg
dG8gcmVtb3ZlIHRoYXQgZGVwZW5kZW5jeS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPltUbDtkciB2ZXJzaW9uXSZuYnNwOyBJdCB3YXMgdGhvdWdodCB0aGF0IEJH
UHNlYyB3b3VsZCBuZWVkIGV4dGVuZGVkIEJHUCBtZXNzYWdlcyBiZWNhdXNlIG9mIHRoZSBzaWdu
YXR1cmVzIGluY2x1ZGVkIGluIHRoZSBVcGRhdGVzLiZuYnNwOyBCdXQgd2l0aCB0aGUgY3VycmVu
dCBhbGdvcml0aG1zIFs2XSwgaXQgaXMgZXhwZWN0ZWQgdGhhdCB3ZSB3b3VsZCBwYXNzIHRoZSBj
dXJyZW50DQogbWF4aW11bSBCR1AgbWVzc2FnZSBzaXplIChvZiA0ayBvY3RldHMpIGlmIHRoZSBB
UyBwYXRoIGxlbmd0aCBpcyBjbG9zZSB0byA0MCDigJMgdGhlIGN1cnJlbnQgYXZlcmFnZSBvYnNl
cnZlZCBvbiB0aGUgSW50ZXJuZXQgaXMgJmx0OyA0LCBhbmQgdGhlIG1heGltdW0gaXMgMTUgWzdd
LiZuYnNwOyBJT1csIHRoZXJl4oCZcyBubyByaXNrIG9mIG5lZWRpbmcgYmlnZ2VyIHVwZGF0ZXMg
YW55IHRpbWUgc29vbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQi
PknigJltIGF0dGFjaGluZyB0aGUgcHJvcG9zZWQgZGlmZnMgKC0yMyBoYXMgbm90IGJlZW4gcG9z
dGVkIHlldCkuJm5ic3A7IFBsZWFzZSB0YWtlIGEgbG9vay48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQiPlRvIHN1bW1hcml6ZSwgdGhlIGNoYW5nZXMgYXJlOiAoMSkgcmVtb3Zl
IG1lbnRpb24gb2YvcmVmZXJlbmNlcyB0byBkcmFmdC1pZXRmLWlkci1iZ3AtZXh0ZW5kZWQtbWVz
c2FnZXMsIGFuZCAoMikgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCBpbiBTZWN0aW9uIDQuMS4gKEdl
bmVyYWwgR3VpZGFuY2UpOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IEFsbCBCR1BzZWMgdXBkYXRlIG1lc3NhZ2VzIE1VU1QgY29u
Zm9ybSB0byBCR1AncyBtYXhpbXVtIG1lc3NhZ2U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7IHNpemUuJm5ic3A7IElmIHRoZSByZXN1bHRpbmcgbWVzc2FnZSBleGNlZWRzIHRo
ZSBtYXhpbXVtIG1lc3NhZ2Ugc2l6ZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7IHRoZW4gdGhlIGd1aWRlbGluZXMgaW4gU2VjdGlvbiA5LjIgb2YgUkZDIDQyNzEgW1JGQzQy
NzFdIE1VU1QgYmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGZvbGxvd2Vk
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+W0ZvciBlYXNpZXIg
cmVmZXJlbmNlLCBJIHB1dCB0aGUgcmVsZXZhbnQgdGV4dCBmcm9tIDkuMiBiZWxvdy5dPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5UaGUgcmVzdWx0IGlzIHRoZW4g
dGhhdCBkcmFmdC1pZXRmLXNpZHItYmdwc2VjLXByb3RvY29sIGRvZXNu4oCZdCBkZXBlbmQgb24g
ZHJhZnQtaWV0Zi1pZHItYmdwLWV4dGVuZGVkLW1lc3NhZ2VzLiAmbmJzcDtJbnN0ZWFkLCB3aGVu
IHJlZmVycmluZyB0byB0aGUgc2l6ZSBvZiB0aGUgbWVzc2FnZXMsIGl0IGRlcGVuZHMgb24gcmZj
NDI3MSwgd2hpY2ggaXMgdGhlIGJhc2UNCiBCR1AgU3BlY2lmaWNhdGlvbi4mbmJzcDsgSWYgdGhl
IHNpemUgaXMgaW5jcmVhc2VkIGxhdGVyIChieSBkcmFmdC1pZXRmLWlkci1iZ3AtZXh0ZW5kZWQg
bWVzc2FnZXMgb3IgYW55IG90aGVyIGRvY3VtZW50KSwgdGhlbiByZmM0MjcxIHdvdWxkIGhhdmUg
dG8gYmUgVXBkYXRlZCBhbmQgQkdQc2VjIHdvdWxkIGJlIGFibGUgdG8gdXNlIHRoYXQgZmFjaWxp
dHkgZnJvbSBCR1AgKHdpdGggbm8gVXBkYXRlcyB0byBCR1BzZWMpLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdCI+SW4gdGhlIHNwaXJpdCBvZiBmdWxsIGRpc2Nsb3N1cmXigKYm
bmJzcDsgQmVzaWRlcyBCR1BzZWMgbm90IG5lZWRpbmcgZXh0ZW5kZWQgbWVzc2FnZXMsIEkgcmV0
dXJuZWQgZHJhZnQtaWV0Zi1pZHItYmdwLWV4dGVuZGVkLW1lc3NhZ2VzIHRvIHRoZSBpZHIgV0cg
Zm9yIG1vcmUgcHJvY2Vzc2luZyBhcyBhIHJlc3VsdCBvZiBteSBBRCByZXZpZXcuJm5ic3A7IFRo
aXMgYWN0aW9uDQogdHJpZ2dlcmVkIHRoZSBkaXNjdXNzaW9uIHRoYXQgbGVkIHRvIHdhbnRpbmcg
dG8gY2hhbmdlIHRoZSBkZXBlbmRlbmN5LiZuYnNwOyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQiPlBsZWFzZSBsZXQgbWUga25vdyBpZiB5b3UgaGF2ZSBhbnkgY29u
Y2VybnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5HaXZlbiB0aGF0IHRo
aXMgZG9jdW1lbnQgaGFzIGFscmVhZHkgYmVlbiBhcHByb3ZlZCBieSB0aGUgSUVTRywgdGhlIHBy
b2Nlc3MgZ29pbmcgZm9yd2FyZCBpczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQiPi0gY29uc3VsdCB0aGUgV0cgKGRvbmUhKTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij4tIGlu
Zm9ybSB0aGUgSUVTRyBvZiB0aGUgaW50ZW50IChkb25lISk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LSBp
bmZvcm0gdGhlIGlldGZAaWV0Zi5vcmcgb2YgdGhlIGNoYW5nZXMgKHRoaXMgdGhyZWFkKTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0Ij4tIHB1Ymxpc2ggYW4gdXBkYXRlZCBkcmFmdDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
Ij4tIGNvbnRpbnVlIHRoZSBwdWJsaWNhdGlvbiBwcm9jZXNzPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0Ij5FYWNoIHN0ZXAgbWF5LCBvYnZpb3VzbHksIHJlcXVpcmUg
YWRkaXRpb25hbCBkaXNjdXNzaW9uIGFuZCBjb3VsZCByZXN1bHQgaW4gY2hhbmdlcyB0byB0aGUg
Y3VycmVudCBwbGFuLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+
VGhhbmtzISE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkFsdmFy
by48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0Ij5bMV0gPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1wcm90b2NvbC8iPg0KaHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1wcm90b2NvbC88L2E+IDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0Ij5bMl0gPGEgaHJlZj0iaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9h
cmNoL21zZy9pZXRmLWFubm91bmNlL3RQNGhacEk0SW9jcHdpTHQwaTJRRUtkUFcxRS8/cWlkPWVm
MTQ1NzQ4ZDk2NzJiMDliOTllMTIwMmQzZDQzZjc2Ij4NCmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0
Zi5vcmcvYXJjaC9tc2cvaWV0Zi1hbm5vdW5jZS90UDRoWnBJNElvY3B3aUx0MGkyUUVLZFBXMUUv
P3FpZD1lZjE0NTc0OGQ5NjcyYjA5Yjk5ZTEyMDJkM2Q0M2Y3NjwvYT4NCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0Ij5bM10gPGEgaHJlZj0iaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvY2x1c3Rlcl9pbmZv
LnBocD9jaWQ9QzMwNiI+DQpodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9jbHVzdGVyX2luZm8u
cGhwP2NpZD1DMzA2PC9hPiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+WzRdIDxhIGhyZWY9Imh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtaWRyLWJncC1leHRlbmRlZC1tZXNz
YWdlcy8iPg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1pZHIt
YmdwLWV4dGVuZGVkLW1lc3NhZ2VzLzwvYT4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPls1XSA8YSBocmVm
PSJodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL3NpZHIvNm1sUUdTUm45dGZC
TEQ4bkd5T1RvSWU1NjJzLz9xaWQ9ZTNmZDBjYjhkM2E3ZDk0MTAzOTg3OTZiYTRjYjc3ZmIiPg0K
aHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9zaWRyLzZtbFFHU1JuOXRmQkxE
OG5HeU9Ub0llNTYycy8/cWlkPWUzZmQwY2I4ZDNhN2Q5NDEwMzk4Nzk2YmE0Y2I3N2ZiPC9hPg0K
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQiPls2XSA8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1hbGdzIj4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLXNpZHItYmdwc2VjLWFsZ3M8L2E+IDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5b
N10gPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvOTgvc2xpZGVzL3Ns
aWRlcy05OC1zaWRyb3BzLWRlY291cGxpbmctYmdwc2VjLWRvY3VtZW50cy1hbmQtZXh0ZW5kZWQt
bWVzc2FnZXMtZHJhZnQtMDAucGRmIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdz
Lzk4L3NsaWRlcy9zbGlkZXMtOTgtc2lkcm9wcy1kZWNvdXBsaW5nLWJncHNlYy1kb2N1bWVudHMt
YW5kLWV4dGVuZGVkLW1lc3NhZ2VzLWRyYWZ0LTAwLnBkZjwvYT4NCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDI3MSNz
ZWN0aW9uLTkuMjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij45LjIuJm5ic3A7IFVwZGF0ZS1TZW5kIFByb2Nl
c3M8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdCI+4oCmPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNwOyZuYnNwOyBJ
ZiwgZHVlIHRvIHRoZSBsaW1pdHMgb24gdGhlIG1heGltdW0gc2l6ZSBvZiBhbiBVUERBVEUgbWVz
c2FnZSAoc2VlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNwOyZuYnNwOyBTZWN0aW9uIDQpLCBhIHNp
bmdsZSByb3V0ZSBkb2Vzbid0IGZpdCBpbnRvIHRoZSBtZXNzYWdlLCB0aGUgQkdQPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQiPiZuYnNwOyZuYnNwOyBzcGVha2VyIE1VU1Qgbm90IGFkdmVydGlzZSB0aGUgcm91
dGUgdG8gaXRzIHBlZXJzIGFuZCBNQVkgY2hvb3NlIHRvPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiZuYnNw
OyZuYnNwOyBsb2cgYW4gZXJyb3IgbG9jYWxseS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_--

--_004_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_
Content-Type: text/html;
	name="Diff_ draft-ietf-sidr-bgpsec-protocol-22-download.txt -
 draft-ietf-sidr-bgpsec-protocol-23.txt[1].html"
Content-Description: Diff_ draft-ietf-sidr-bgpsec-protocol-22-download.txt -
 draft-ietf-sidr-bgpsec-protocol-23.txt[1].html
Content-Disposition: attachment;
	filename="Diff_ draft-ietf-sidr-bgpsec-protocol-22-download.txt -
 draft-ietf-sidr-bgpsec-protocol-23.txt[1].html"; size=75707;
	creation-date="Tue, 18 Apr 2017 13:57:35 GMT";
	modification-date="Tue, 18 Apr 2017 13:57:35 GMT"
Content-ID: <4FE1BA813C783B4AA8DBEB7A3EFAAC39@emea.cisco.com>
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPgo8IS0tIHNhdmVkIGZyb20gdXJsPSgwMDQ5KWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
dG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQgLS0+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3Lncz
Lm9yZy8xOTk5L3hodG1sIj48aGVhZD48bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNv
bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYtOCI+IAogICAKICA8bWV0YSBodHRwLWVxdWl2
PSJDb250ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9InRleHQvY3NzIj4gCiAgPHRpdGxlPkRpZmY6
IGRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtcHJvdG9jb2wtMjItZG93bmxvYWQudHh0IC0gZHJhZnQt
aWV0Zi1zaWRyLWJncHNlYy1wcm90b2NvbC0yMy50eHQ8L3RpdGxlPiAKICA8c3R5bGUgdHlwZT0i
dGV4dC9jc3MiPiAKICAgIGJvZHkgICAgeyBtYXJnaW46IDAuNGV4OyBtYXJnaW4tcmlnaHQ6IGF1
dG87IH0gCiAgICB0ciAgICAgIHsgfSAKICAgIHRkICAgICAgeyB3aGl0ZS1zcGFjZTogcHJlOyBm
b250LWZhbWlseTogbW9ub3NwYWNlOyB2ZXJ0aWNhbC1hbGlnbjogdG9wOyBmb250LXNpemU6IDAu
ODZlbTt9IAogICAgdGggICAgICB7IGZvbnQtc2l6ZTogMC44NmVtOyB9IAogICAgLnNtYWxsICB7
IGZvbnQtc2l6ZTogMC42ZW07IGZvbnQtc3R5bGU6IGl0YWxpYzsgZm9udC1mYW1pbHk6IFZlcmRh
bmEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgfSAKICAgIC5sZWZ0ICAgeyBiYWNrZ3JvdW5kLWNv
bG9yOiAjRUVFOyB9IAogICAgLnJpZ2h0ICB7IGJhY2tncm91bmQtY29sb3I6ICNGRkY7IH0gCiAg
ICAuZGlmZiAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0NDRjsgfSAKICAgIC5sYmxvY2sgeyBiYWNr
Z3JvdW5kLWNvbG9yOiAjQkZCOyB9IAogICAgLnJibG9jayB7IGJhY2tncm91bmQtY29sb3I6ICNG
Rjg7IH0gCiAgICAuaW5zZXJ0IHsgYmFja2dyb3VuZC1jb2xvcjogIzhGRjsgfSAKICAgIC5kZWxl
dGUgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUNGOyB9IAogICAgLnZvaWQgICB7IGJhY2tncm91bmQt
Y29sb3I6ICNGRkI7IH0gCiAgICAuY29udCAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAK
ICAgIC5saW5lYnIgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9IAogICAgLmxpbmVubyB7IGNv
bG9yOiByZWQ7IGJhY2tncm91bmQtY29sb3I6ICNGRkY7IGZvbnQtc2l6ZTogMC43ZW07IHRleHQt
YWxpZ246IHJpZ2h0OyBwYWRkaW5nOiAwIDJweDsgfSAKICAgIC5lbGlwc2lzeyBiYWNrZ3JvdW5k
LWNvbG9yOiAjQUFBOyB9IAogICAgLmxlZnQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRERE
OyB9IAogICAgLnJpZ2h0IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5s
YmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOUQ5OyB9IAogICAgLnJibG9jayAuY29u
dCB7IGJhY2tncm91bmQtY29sb3I6ICNERDY7IH0gCiAgICAuaW5zZXJ0IC5jb250IHsgYmFja2dy
b3VuZC1jb2xvcjogIzBERDsgfSAKICAgIC5kZWxldGUgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9y
OiAjOEFEOyB9IAogICAgLnN0YXRzLCAuc3RhdHMgdGQsIC5zdGF0cyB0aCB7IGJhY2tncm91bmQt
Y29sb3I6ICNFRUU7IHBhZGRpbmc6IDJweCAwOyB9IAogICAgc3Bhbi5oaWRlIHsgZGlzcGxheTog
bm9uZTsgY29sb3I6ICNhYWE7fSAgICBhOmhvdmVyIHNwYW4geyBkaXNwbGF5OiBpbmxpbmU7IH0g
ICAgdHIuY2hhbmdlIHsgYmFja2dyb3VuZC1jb2xvcjogZ3JheTsgfSAKICAgIHRyLmNoYW5nZSBh
IHsgdGV4dC1kZWNvcmF0aW9uOiBub25lOyBjb2xvcjogYmxhY2sgfSAKICA8L3N0eWxlPiAKICAg
ICA8c2NyaXB0Pgp2YXIgY2h1bmtfaW5kZXggPSAwOwp2YXIgb2xkX2NodW5rID0gbnVsbDsKCmZ1
bmN0aW9uIGZvcm1hdF9jaHVuayhpbmRleCkgewogICAgdmFyIHByZWZpeCA9ICJkaWZmIjsKICAg
IHZhciBzdHIgPSBpbmRleC50b1N0cmluZygpOwogICAgZm9yICh4PTA7IHg8KDQtc3RyLmxlbmd0
aCk7ICsreCkgewogICAgICAgIHByZWZpeCs9JzAnOwogICAgfQogICAgcmV0dXJuIHByZWZpeCAr
IHN0cjsKfQoKZnVuY3Rpb24gZmluZF9jaHVuayhuKXsKICAgIHJldHVybiBkb2N1bWVudC5xdWVy
eVNlbGVjdG9yKCd0cltpZCQ9IicgKyBuICsgJyJdJyk7Cn0KCmZ1bmN0aW9uIGNoYW5nZV9jaHVu
ayhvZmZzZXQpIHsKICAgIHZhciBpbmRleCA9IGNodW5rX2luZGV4ICsgb2Zmc2V0OwogICAgdmFy
IG5ld19zdHI7CiAgICB2YXIgbmV3X2NodW5rOwoKICAgIG5ld19zdHIgPSBmb3JtYXRfY2h1bmso
aW5kZXgpOwogICAgbmV3X2NodW5rID0gZmluZF9jaHVuayhuZXdfc3RyKTsKICAgIGlmICghbmV3
X2NodW5rKSB7CiAgICAgICAgcmV0dXJuOwogICAgfQogICAgaWYgKG9sZF9jaHVuaykgewogICAg
ICAgIG9sZF9jaHVuay5zdHlsZS5vdXRsaW5lID0gIiI7CiAgICB9CiAgICBvbGRfY2h1bmsgPSBu
ZXdfY2h1bms7CiAgICBvbGRfY2h1bmsuc3R5bGUub3V0bGluZSA9ICIxcHggc29saWQgcmVkIjsK
ICAgIHdpbmRvdy5sb2NhdGlvbi5oYXNoID0gIiMiICsgbmV3X3N0cjsKICAgIHdpbmRvdy5zY3Jv
bGxCeSgwLC0xMDApOwogICAgY2h1bmtfaW5kZXggPSBpbmRleDsKfQoKZG9jdW1lbnQub25rZXlk
b3duID0gZnVuY3Rpb24oZSkgewogICAgc3dpdGNoIChlLmtleUNvZGUpIHsKICAgIGNhc2UgNzg6
CiAgICAgICAgY2hhbmdlX2NodW5rKDEpOwogICAgICAgIGJyZWFrOwogICAgY2FzZSA4MDoKICAg
ICAgICBjaGFuZ2VfY2h1bmsoLTEpOwogICAgICAgIGJyZWFrOwogICAgfQp9OwogICA8L3Njcmlw
dD4gCjwvaGVhZD4gCjxib2R5PiAKICA8dGFibGUgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMCIg
Y2VsbHNwYWNpbmc9IjAiPiAKICA8dGJvZHk+PHRyIGlkPSJwYXJ0LTEiIGJnY29sb3I9Im9yYW5n
ZSI+PHRoPjwvdGg+PHRoPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91
cmwyPWRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtcHJvdG9jb2wtMjItZG93bmxvYWQudHh0IiBzdHls
ZT0iY29sb3I6IzAwODsgdGV4dC1kZWNvcmF0aW9uOm5vbmU7Ij4mbHQ7PC9hPiZuYnNwOzxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXNpZHItYmdwc2VjLXBy
b3RvY29sLTIyLWRvd25sb2FkLnR4dCIgc3R5bGU9ImNvbG9yOiMwMDgiPmRyYWZ0LWlldGYtc2lk
ci1iZ3BzZWMtcHJvdG9jb2wtMjItZG93bmxvYWQudHh0PC9hPiZuYnNwOzwvdGg+PHRoPiA8L3Ro
Pjx0aD4mbmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0
Zi1zaWRyLWJncHNlYy1wcm90b2NvbC0yMy50eHQiIHN0eWxlPSJjb2xvcjojMDA4Ij5kcmFmdC1p
ZXRmLXNpZHItYmdwc2VjLXByb3RvY29sLTIzLnR4dDwvYT4mbmJzcDs8YSBocmVmPSJodHRwczov
L3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMT1kcmFmdC1pZXRmLXNpZHItYmdwc2VjLXByb3Rv
Y29sLTIzLnR4dCIgc3R5bGU9ImNvbG9yOiMwMDg7IHRleHQtZGVjb3JhdGlvbjpub25lOyI+Jmd0
OzwvYT48L3RoPjx0aD48L3RoPjwvdHI+IAogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgTS4gTGVwaW5za2ksIEVkLjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgTS4gTGVwaW5za2ksIEVkLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgTkNGPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+SW50ZXJu
ZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgTkNGPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5JbnRlbmRlZCBzdGF0dXM6IFN0
YW5kYXJkcyBUcmFjayAgICAgICAgICAgICAgICAgICAgICAgICAgSy4gU3JpcmFtLCBFZC48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5JbnRlbmRlZCBzdGF0dXM6IFN0YW5kYXJkcyBU
cmFjayAgICAgICAgICAgICAgICAgICAgICAgICAgSy4gU3JpcmFtLCBFZC48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDEiPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
RXhwaXJlczogPHNwYW4gY2xhc3M9ImRlbGV0ZSI+SnVseSAyMCw8L3NwYW4+IDIwMTcgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTklTVDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj5FeHBpcmVzOiA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5PY3RvYmVy
IDUsPC9zcGFuPiAyMDE3ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBOSVNUPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
SmFudWFyeSAxNiw8L3NwYW4+IDIwMTc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5BcHJpbCAzLDwvc3Bhbj4gMjAxNzwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICBCR1BzZWMgUHJvdG9jb2wg
U3BlY2lmaWNhdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgICAgICAgIEJHUHNlYyBQcm90b2NvbCBTcGVjaWZpY2F0aW9uPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDAyIj48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAg
ICAgICAgICAgICAgICBkcmFmdC1pZXRmLXNpZHItYmdwc2VjLXByb3RvY29sLTI8c3BhbiBjbGFz
cz0iZGVsZXRlIj4yPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAg
ICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1wcm90b2NvbC0yPHNwYW4gY2xh
c3M9Imluc2VydCI+Mzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+QWJz
dHJhY3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5BYnN0cmFjdDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBCR1BzZWMs
IGFuIGV4dGVuc2lvbiB0byB0aGUgQm9yZGVyIEdhdGV3YXk8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBCR1BzZWMsIGFuIGV4dGVuc2lv
biB0byB0aGUgQm9yZGVyIEdhdGV3YXk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFBy
b3RvY29sIChCR1ApIHRoYXQgcHJvdmlkZXMgc2VjdXJpdHkgZm9yIHRoZSBwYXRoIG9mIGF1dG9u
b21vdXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBQcm90b2NvbCAoQkdQKSB0
aGF0IHByb3ZpZGVzIHNlY3VyaXR5IGZvciB0aGUgcGF0aCBvZiBhdXRvbm9tb3VzPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzeXN0ZW1zIChBU2VzKSB0aHJvdWdoIHdoaWNoIGEgQkdQ
IHVwZGF0ZSBtZXNzYWdlIHBhc3Nlcy4gIEJHUHNlYyBpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHN5c3RlbXMgKEFTZXMpIHRocm91Z2ggd2hpY2ggYSBCR1AgdXBkYXRlIG1l
c3NhZ2UgcGFzc2VzLiAgQkdQc2VjIGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBp
bXBsZW1lbnRlZCB2aWEgYW4gb3B0aW9uYWwgbm9uLXRyYW5zaXRpdmUgQkdQIHBhdGggYXR0cmli
dXRlIHRoYXQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpbXBsZW1lbnRlZCB2
aWEgYW4gb3B0aW9uYWwgbm9uLXRyYW5zaXRpdmUgQkdQIHBhdGggYXR0cmlidXRlIHRoYXQ8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNhcnJpZXMgZGlnaXRhbCBzaWduYXR1cmVzIHBy
b2R1Y2VkIGJ5IGVhY2ggYXV0b25vbW91cyBzeXN0ZW0gdGhhdDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIGNhcnJpZXMgZGlnaXRhbCBzaWduYXR1cmVzIHByb2R1Y2VkIGJ5IGVh
Y2ggYXV0b25vbW91cyBzeXN0ZW0gdGhhdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
cHJvcGFnYXRlcyB0aGUgdXBkYXRlIG1lc3NhZ2UuICBUaGUgZGlnaXRhbCBzaWduYXR1cmVzIHBy
b3ZpZGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwcm9wYWdhdGVzIHRoZSB1
cGRhdGUgbWVzc2FnZS4gIFRoZSBkaWdpdGFsIHNpZ25hdHVyZXMgcHJvdmlkZTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgY29uZmlkZW5jZSB0aGF0IGV2ZXJ5IEFTIG9uIHRoZSBwYXRo
IG9mIEFTZXMgbGlzdGVkIGluIHRoZSB1cGRhdGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBjb25maWRlbmNlIHRoYXQgZXZlcnkgQVMgb24gdGhlIHBhdGggb2YgQVNlcyBsaXN0
ZWQgaW4gdGhlIHVwZGF0ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHIgaWQ9InBhcnQtMiIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5z
a2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC0yIj48ZW0+IHBhZ2UgMSwgbGluZSAz
ODxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRo
PjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC0yIj48ZW0+IHBhZ2Ug
MSwgbGluZSAzODxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRl
cm5ldCBFbmdpbmVlcmluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEludGVy
bmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVy
aW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUYXNrIEZvcmNlIChJRVRGKS4gIE5v
dGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZTwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIFRhc2sgRm9yY2UgKElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdy
b3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB3
b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50
IEludGVybmV0LTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHdvcmtpbmcgZG9j
dW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQt
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0
cmFja2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RyYWZ0
cy9jdXJyZW50Ly48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgSW50ZXJuZXQt
RHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9u
dGhzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFy
ZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBv
ciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRl
ZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJl
ZmVyZW5jZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRpbWUuICBJdCBpcyBp
bmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhh
biBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jl
c3MuIjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9
ImRpZmYwMDAzIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUg
b24gPHNwYW4gY2xhc3M9ImRlbGV0ZSI+SnVseSAyMDwvc3Bhbj4sIDIwMTcuPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUg
b24gPHNwYW4gY2xhc3M9Imluc2VydCI+T2N0b2JlciA1PC9zcGFuPiwgMjAxNy48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Q29weXJpZ2h0IE5vdGljZTwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPkNvcHlyaWdodCBOb3RpY2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgQ29weXJpZ2h0IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25z
IGlkZW50aWZpZWQgYXMgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQ29w
eXJpZ2h0IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMg
dGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBkb2N1bWVudCBhdXRob3JzLiAgQWxs
IHJpZ2h0cyByZXNlcnZlZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBkb2N1
bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhl
IElFVEYgVHJ1c3QncyBMZWdhbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRo
aXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVn
YWw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8g
SUVURiBEb2N1bWVudHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBQcm92aXNp
b25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAoaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24g
dGhlIGRhdGUgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAoaHR0cDovL3Ry
dXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2Y8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQu
ICBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRo
ZXNlIGRvY3VtZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHIgaWQ9InBhcnQtMyIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lw
cGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
dG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC0zIj48ZW0+IHBhZ2UgMiwgbGluZSAyMTxz
cGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxz
bWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMu
aWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC0zIj48ZW0+IHBhZ2UgMiwg
bGluZSAyMTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAxLiAgSW50cm9kdWN0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgIDI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAxLiAg
SW50cm9kdWN0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgIDI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMS4xLiAgUmVxdWlyZW1l
bnRzIExhbmd1YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgMzwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMS4xLiAgUmVxdWlyZW1lbnRzIExhbmd1
YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgMzwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgMi4gIEJHUHNlYyBOZWdvdGlhdGlvbiAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICAzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgMi4gIEJHUHNlYyBOZWdvdGlhdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICAzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDIu
MS4gIFRoZSBCR1BzZWMgQ2FwYWJpbGl0eSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgIDM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDIuMS4gIFRoZSBC
R1BzZWMgQ2FwYWJpbGl0eSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMi4yLiAgTmVnb3RpYXRpbmcgQkdQc2Vj
IFN1cHBvcnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMi4yLiAgTmVnb3RpYXRpbmcgQkdQc2VjIFN1cHBvcnQg
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgMy4gIFRoZSBCR1BzZWNfUGF0aCBBdHRyaWJ1dGUgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICA2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
My4gIFRoZSBCR1BzZWNfUGF0aCBBdHRyaWJ1dGUgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA2PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDMuMS4gIFNlY3Vy
ZV9QYXRoIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDMuMS4gIFNlY3VyZV9QYXRoIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMy4yLiAgU2lnbmF0dXJlX0Jsb2NrIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgMy4yLiAgU2lnbmF0dXJlX0Jsb2NrIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
NC4gIEJHUHNlYyBVcGRhdGUgTWVzc2FnZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gIDExPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgNC4gIEJHUHNl
YyBVcGRhdGUgTWVzc2FnZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
IDExPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDQuMS4gIEdlbmVyYWwgR3VpZGFu
Y2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDQuMS4gIEdlbmVyYWwgR3VpZGFuY2UgIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDQiPjx0ZD48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICA0
LjIuICBDb25zdHJ1Y3RpbmcgdGhlIEJHUHNlY19QYXRoIEF0dHJpYnV0ZSAgLiAuIC4gLiAuIC4g
LiAuIC4gIDE8c3BhbiBjbGFzcz0iZGVsZXRlIj4zPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj4gICAgIDQuMi4gIENvbnN0cnVjdGluZyB0aGUgQkdQc2VjX1BhdGggQXR0
cmlidXRlICAuIC4gLiAuIC4gLiAuIC4gLiAgMTxzcGFuIGNsYXNzPSJpbnNlcnQiPjQ8L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDQuMy4gIFByb2Nlc3NpbmcgSW5zdHJ1
Y3Rpb25zIGZvciBDb25mZWRlcmF0aW9uIE1lbWJlcnMgLiAuIC4gLiAgMTg8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDQuMy4gIFByb2Nlc3NpbmcgSW5zdHJ1Y3Rpb25zIGZv
ciBDb25mZWRlcmF0aW9uIE1lbWJlcnMgLiAuIC4gLiAgMTg8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgNC40LiAgUmVjb25zdHJ1Y3RpbmcgdGhlIEFTX1BBVEggQXR0cmlidXRlICAu
IC4gLiAuIC4gLiAuIC4gLiAuICAxOTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgNC40LiAgUmVjb25zdHJ1Y3RpbmcgdGhlIEFTX1BBVEggQXR0cmlidXRlICAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxOTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgNS4gIFByb2Nlc3Np
bmcgYSBSZWNlaXZlZCBCR1BzZWMgVXBkYXRlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIx
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgNS4gIFByb2Nlc3NpbmcgYSBSZWNl
aXZlZCBCR1BzZWMgVXBkYXRlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIxPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDUuMS4gIE92ZXJ2aWV3IG9mIEJHUHNlYyBWYWxpZGF0
aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjI8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgIDUuMS4gIE92ZXJ2aWV3IG9mIEJHUHNlYyBWYWxpZGF0aW9uIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgNS4yLiAgVmFsaWRhdGlvbiBBbGdvcml0aG0gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAyMzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNS4yLiAg
VmFsaWRhdGlvbiBBbGdvcml0aG0gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAyMzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgNi4gIEFsZ29yaXRobXMgYW5kIEV4
dGVuc2liaWxpdHkgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDI3PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgNi4gIEFsZ29yaXRobXMgYW5kIEV4dGVuc2liaWxp
dHkgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDI3PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgIDYuMS4gIEFsZ29yaXRobSBTdWl0ZSBDb25zaWRlcmF0aW9ucyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgIDYuMS4gIEFsZ29yaXRobSBTdWl0ZSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgMjc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgNi4yLiAg
Q29uc2lkZXJhdGlvbnMgZm9yIHRoZSBTS0kgU2l6ZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAyODwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNi4yLiAgQ29uc2lkZXJh
dGlvbnMgZm9yIHRoZSBTS0kgU2l6ZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAyODwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICA2LjMuICBFeHRlbnNpYmlsaXR5IENvbnNpZGVy
YXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDI4PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICA2LjMuICBFeHRlbnNpYmlsaXR5IENvbnNpZGVyYXRpb25zICAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDI4PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICA3LiAgT3BlcmF0aW9ucyBhbmQgTWFuYWdlbWVudCBDb25zaWRlcmF0aW9ucyAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAgMjk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICA3LiAg
T3BlcmF0aW9ucyBhbmQgTWFuYWdlbWVudCBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAgMjk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0i
ZGlmZjAwMDUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgOC4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDM8c3BhbiBjbGFzcz0iZGVsZXRlIj4z
PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA4LiAgU2VjdXJpdHkg
Q29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMzxz
cGFuIGNsYXNzPSJpbnNlcnQiPjI8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgIDguMS4gIFNlY3VyaXR5IEd1YXJhbnRlZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMzM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDguMS4g
IFNlY3VyaXR5IEd1YXJhbnRlZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMzM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMDYiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICA4LjIuICBPbiB0aGUgUmVtb3ZhbCBvZiBCR1BzZWMgU2ln
bmF0dXJlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDM8c3BhbiBjbGFzcz0iZGVsZXRlIj40PC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDguMi4gIE9uIHRoZSBS
ZW1vdmFsIG9mIEJHUHNlYyBTaWduYXR1cmVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMzxzcGFu
IGNsYXNzPSJpbnNlcnQiPjM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
IDguMy4gIE1pdGlnYXRpb24gb2YgRGVuaWFsIG9mIFNlcnZpY2UgQXR0YWNrcyAuIC4gLiAuIC4g
LiAuIC4gLiAgMzU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDguMy4gIE1p
dGlnYXRpb24gb2YgRGVuaWFsIG9mIFNlcnZpY2UgQXR0YWNrcyAuIC4gLiAuIC4gLiAuIC4gLiAg
MzU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgOC40LiAgQWRkaXRpb25hbCBTZWN1
cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzNjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgOC40LiAgQWRkaXRpb25hbCBTZWN1cml0eSBDb25z
aWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzNjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgOS4gIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDM3PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgOS4gIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDM3PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAxMC4gQ29udHJp
YnV0b3JzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
Mzk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAxMC4gQ29udHJpYnV0b3JzICAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMzk8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMTAuMS4gIEF1dGhvcnMgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzOTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgMTAuMS4gIEF1dGhvcnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzOTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICAxMC4yLiAgQWNrbm93bGVkZ2VtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDQwPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAxMC4y
LiAgQWNrbm93bGVkZ2VtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDQwPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAxMS4gUmVmZXJlbmNlcyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNDA8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAxMS4gUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNDA8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgMTEuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0MDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgMTEuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA0MDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyIGlkPSJkaWZmMDAwNyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDExLjIuICBJbmZvcm1hdGl2ZSBS
ZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+NDI8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAg
MTEuMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij40MTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+ICAgQXV0aG9ycycgQWRkcmVzc2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjQ0PC9zcGFuPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBBdXRob3JzJyBBZGRyZXNzZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9
Imluc2VydCI+NDM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjEuICBJ
bnRyb2R1Y3Rpb248L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4xLiAgSW50cm9kdWN0
aW9uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQgZGVz
Y3JpYmVzIEJHUHNlYywgYSBtZWNoYW5pc20gZm9yIHByb3ZpZGluZyBwYXRoPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgQkdQc2VjLCBh
IG1lY2hhbmlzbSBmb3IgcHJvdmlkaW5nIHBhdGg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIHNlY3VyaXR5IGZvciBCb3JkZXIgR2F0ZXdheSBQcm90b2NvbCAoQkdQKSBbUkZDNDI3MV0g
cm91dGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzZWN1cml0eSBmb3IgQm9y
ZGVyIEdhdGV3YXkgUHJvdG9jb2wgKEJHUCkgW1JGQzQyNzFdIHJvdXRlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBhZHZlcnRpc2VtZW50cy4gIFRoYXQgaXMsIGEgQkdQIHNwZWFrZXIg
d2hvIHJlY2VpdmVzIGEgdmFsaWQgQkdQc2VjPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgYWR2ZXJ0aXNlbWVudHMuICBUaGF0IGlzLCBhIEJHUCBzcGVha2VyIHdobyByZWNlaXZl
cyBhIHZhbGlkIEJHUHNlYzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdXBkYXRlIGhh
cyBjcnlwdG9ncmFwaGljIGFzc3VyYW5jZSB0aGF0IHRoZSBhZHZlcnRpc2VkIHJvdXRlIGhhcyB0
aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB1cGRhdGUgaGFzIGNyeXB0b2dy
YXBoaWMgYXNzdXJhbmNlIHRoYXQgdGhlIGFkdmVydGlzZWQgcm91dGUgaGFzIHRoZTwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZm9sbG93aW5nIHByb3BlcnR5OiBFdmVyeSBBUyBvbiB0
aGUgcGF0aCBvZiBBU2VzIGxpc3RlZCBpbiB0aGUgdXBkYXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgZm9sbG93aW5nIHByb3BlcnR5OiBFdmVyeSBBUyBvbiB0aGUgcGF0aCBv
ZiBBU2VzIGxpc3RlZCBpbiB0aGUgdXBkYXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBtZXNzYWdlIGhhcyBleHBsaWNpdGx5IGF1dGhvcml6ZWQgdGhlIGFkdmVydGlzZW1lbnQgb2Yg
dGhlIHJvdXRlIHRvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWVzc2FnZSBo
YXMgZXhwbGljaXRseSBhdXRob3JpemVkIHRoZSBhZHZlcnRpc2VtZW50IG9mIHRoZSByb3V0ZSB0
bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhlIHN1YnNlcXVlbnQgQVMgaW4gdGhl
IHBhdGguPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdGhlIHN1YnNlcXVlbnQg
QVMgaW4gdGhlIHBhdGguPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0ciBpZD0icGFydC00IiBjbGFzcz0iY2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNr
aXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy90b29scy9yZmNkaWZmL3JmY2RpZmYucHlodCNwYXJ0LTQiPjxlbT4gcGFnZSA1LCBsaW5lIDUw
PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+
PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy90b29scy9yZmNkaWZmL3JmY2RpZmYucHlodCNwYXJ0LTQiPjxlbT4gcGFnZSA2
LCBsaW5lIDU8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgY2FzZSB0aGF0IHN1cHBvcnQgZm9yIG11bHRpcGxlIHZlcnNpb25zIGlzIG5lZ290aWF0
ZWQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY2FzZSB0aGF0IHN1cHBvcnQg
Zm9yIG11bHRpcGxlIHZlcnNpb25zIGlzIG5lZ290aWF0ZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIEJHUHNlYyBjYW5ub3QgcHJvdmlkZSBtZWFuaW5nZnVsIHNlY3VyaXR5
IGd1YXJhbnRlZXMgd2l0aG91dCBzdXBwb3J0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgQkdQc2VjIGNhbm5vdCBwcm92aWRlIG1lYW5pbmdmdWwgc2VjdXJpdHkgZ3VhcmFudGVl
cyB3aXRob3V0IHN1cHBvcnQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGZvciBmb3Vy
LWJ5dGUgQVMgbnVtYmVycy4gIFRoZXJlZm9yZSwgYW55IEJHUCBzcGVha2VyIHRoYXQgYW5ub3Vu
Y2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZm9yIGZvdXItYnl0ZSBBUyBu
dW1iZXJzLiAgVGhlcmVmb3JlLCBhbnkgQkdQIHNwZWFrZXIgdGhhdCBhbm5vdW5jZXM8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRoZSBCR1BzZWMgY2FwYWJpbGl0eSwgTVVTVCBhbHNv
IGFubm91bmNlIHRoZSBjYXBhYmlsaXR5IGZvciBmb3VyLTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHRoZSBCR1BzZWMgY2FwYWJpbGl0eSwgTVVTVCBhbHNvIGFubm91bmNlIHRo
ZSBjYXBhYmlsaXR5IGZvciBmb3VyLTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYnl0
ZSBBUyBzdXBwb3J0IFtSRkM2NzkzXS4gIElmIGEgQkdQIHNwZWFrZXIgc2VuZHMgdGhlIEJHUHNl
YzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGJ5dGUgQVMgc3VwcG9ydCBbUkZD
Njc5M10uICBJZiBhIEJHUCBzcGVha2VyIHNlbmRzIHRoZSBCR1BzZWM8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIGNhcGFiaWxpdHkgYnV0IG5vdCB0aGUgZm91ci1ieXRlIEFTIHN1cHBv
cnQgY2FwYWJpbGl0eSB0aGVuIEJHUHNlYzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIGNhcGFiaWxpdHkgYnV0IG5vdCB0aGUgZm91ci1ieXRlIEFTIHN1cHBvcnQgY2FwYWJpbGl0
eSB0aGVuIEJHUHNlYzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaGFzIG5vdCBiZWVu
IHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkLCBhbmQgdXBkYXRlIG1lc3NhZ2VzIGNvbnRhaW5pbmc8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBoYXMgbm90IGJlZW4gc3VjY2Vzc2Z1
bGx5IG5lZ290aWF0ZWQsIGFuZCB1cGRhdGUgbWVzc2FnZXMgY29udGFpbmluZzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhlIEJHUHNlY19QYXRoIGF0dHJpYnV0ZSBNVVNUIE5PVCBi
ZSBzZW50IHdpdGhpbiBzdWNoIGEgc2Vzc2lvbi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICB0aGUgQkdQc2VjX1BhdGggYXR0cmlidXRlIE1VU1QgTk9UIGJlIHNlbnQgd2l0aGlu
IHN1Y2ggYSBzZXNzaW9uLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHIgaWQ9ImRpZmYwMDA4Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUi
Pk5vdGUgdGhhdCBCR1BzZWMgdXBkYXRlIG1lc3NhZ2VzIGNhbiBiZSBxdWl0ZSBsYXJnZSwgdGhl
cmVmb3JlIGFueTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIEJHUHNlYyBz
cGVha2VyIGFubm91bmNpbmcgdGhlIGNhcGFiaWxpdHkgdG8gcmVjZWl2ZSBCR1BzZWMgbWVzc2Fn
ZXM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBTSE9VTEQgYWxzbyBhbm5v
dW5jZSBzdXBwb3J0IGZvciB0aGUgY2FwYWJpbGl0eSB0byByZWNlaXZlIEJHUDwvc3Bhbj48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIGV4dGVuZGVkIG1lc3NhZ2VzIFtJLUQuaWV0Zi1p
ZHItYmdwLWV4dGVuZGVkLW1lc3NhZ2VzXS4gIFBsZWFzZSBzZWU8L3NwYW4+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3Bh
biBjbGFzcz0iZGVsZXRlIj4gICByZWxhdGVkIG9wZXJhdGlvbmFsIGd1aWRhbmNlIGluIFNlY3Rp
b24gNy48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My4gIFRoZSBCR1BzZWNf
UGF0aCBBdHRyaWJ1dGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4zLiAgVGhlIEJH
UHNlY19QYXRoIEF0dHJpYnV0ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBU
aGUgQkdQc2VjX1BhdGggYXR0cmlidXRlIGlzIGFuIG9wdGlvbmFsIG5vbi10cmFuc2l0aXZlIEJH
UCBwYXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIEJHUHNlY19QYXRo
IGF0dHJpYnV0ZSBpcyBhbiBvcHRpb25hbCBub24tdHJhbnNpdGl2ZSBCR1AgcGF0aDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYXR0cmlidXRlLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIGF0dHJpYnV0ZS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgVGhpcyBkb2N1bWVudCByZWdpc3RlcnMgYW4gYXR0cmlidXRlIHR5cGUgY29kZSBmb3IgdGhp
cyBhdHRyaWJ1dGU6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBkb2N1
bWVudCByZWdpc3RlcnMgYW4gYXR0cmlidXRlIHR5cGUgY29kZSBmb3IgdGhpcyBhdHRyaWJ1dGU6
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBCR1BzZWNfUGF0aCAoc2VlIFNlY3Rpb24g
OSkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQkdQc2VjX1BhdGggKHNlZSBT
ZWN0aW9uIDkpLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgQkdQc2Vj
X1BhdGggYXR0cmlidXRlIGNhcnJpZXMgdGhlIHNlY3VyZWQgaW5mb3JtYXRpb24gcmVnYXJkaW5n
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIEJHUHNlY19QYXRoIGF0dHJp
YnV0ZSBjYXJyaWVzIHRoZSBzZWN1cmVkIGluZm9ybWF0aW9uIHJlZ2FyZGluZzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhlIHBhdGggb2YgQVNlcyB0aHJvdWdoIHdoaWNoIGFuIHVw
ZGF0ZSBtZXNzYWdlIHBhc3Nlcy4gIFRoaXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICB0aGUgcGF0aCBvZiBBU2VzIHRocm91Z2ggd2hpY2ggYW4gdXBkYXRlIG1lc3NhZ2UgcGFz
c2VzLiAgVGhpczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9InBhcnQtNSIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGlu
ZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvdG9v
bHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC01Ij48ZW0+IHBhZ2UgMTMsIGxpbmUgNDU8c3Bh
biBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21h
bGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmll
dGYub3JnL3Rvb2xzL3JmY2RpZmYvcmZjZGlmZi5weWh0I3BhcnQtNSI+PGVtPiBwYWdlIDEzLCBs
aW5lIDQ1PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGF0dHJpYnV0ZSBTSE9VTEQgTk9UIGJlIHJlbW92ZWQsIHVubGVzcyB0aGUgcGVlciBkb2Vz
bid0IHN1cHBvcnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhdHRyaWJ1dGUg
U0hPVUxEIE5PVCBiZSByZW1vdmVkLCB1bmxlc3MgdGhlIHBlZXIgZG9lc24ndCBzdXBwb3J0PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBCR1BzZWMuICBJbiB0aGUgY2FzZSB3aGVuIGFu
IGlCR1AgcGVlciBkb2Vzbid0IHN1cHBvcnQgQkdQc2VjLCB0aGVuIGE8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBCR1BzZWMuICBJbiB0aGUgY2FzZSB3aGVuIGFuIGlCR1AgcGVl
ciBkb2Vzbid0IHN1cHBvcnQgQkdQc2VjLCB0aGVuIGE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIEJHUCB1cGRhdGUgd2l0aCBBU19QQVRIIGlzIHJlY29uc3RydWN0ZWQgZnJvbSB0aGUg
QkdQc2VjIHVwZGF0ZSBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBCR1Ag
dXBkYXRlIHdpdGggQVNfUEFUSCBpcyByZWNvbnN0cnVjdGVkIGZyb20gdGhlIEJHUHNlYyB1cGRh
dGUgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGVuIGZvcndhcmRlZCAoc2Vl
IFNlY3Rpb24gNC40KS4gIEluIHBhcnRpY3VsYXIsIHdoZW4gZm9yd2FyZGluZyB0bzwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZW4gZm9yd2FyZGVkIChzZWUgU2VjdGlvbiA0
LjQpLiAgSW4gcGFydGljdWxhciwgd2hlbiBmb3J3YXJkaW5nIHRvPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBhIEJHUHNlYy1jYXBhYmxlIGlCR1AgKG9yIGVCR1ApIHBlZXIsIHRoZSBC
R1BzZWNfUGF0aCBhdHRyaWJ1dGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBh
IEJHUHNlYy1jYXBhYmxlIGlCR1AgKG9yIGVCR1ApIHBlZXIsIHRoZSBCR1BzZWNfUGF0aCBhdHRy
aWJ1dGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFNIT1VMRCBOT1QgYmUgcmVtb3Zl
ZCBldmVuIGluIHRoZSBjYXNlIHdoZXJlIHRoZSBCR1BzZWMgdXBkYXRlPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgU0hPVUxEIE5PVCBiZSByZW1vdmVkIGV2ZW4gaW4gdGhlIGNh
c2Ugd2hlcmUgdGhlIEJHUHNlYyB1cGRhdGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IG1lc3NhZ2UgaGFzIG5vdCBiZWVuIHN1Y2Nlc3NmdWxseSB2YWxpZGF0ZWQuICAoU2VlIFNlY3Rp
b24gNSBmb3IgbW9yZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG1lc3NhZ2Ug
aGFzIG5vdCBiZWVuIHN1Y2Nlc3NmdWxseSB2YWxpZGF0ZWQuICAoU2VlIFNlY3Rpb24gNSBmb3Ig
bW9yZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaW5mb3JtYXRpb24gb24gdmFsaWRh
dGlvbiwgYW5kIFNlY3Rpb24gOCBmb3IgdGhlIHNlY3VyaXR5PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgaW5mb3JtYXRpb24gb24gdmFsaWRhdGlvbiwgYW5kIFNlY3Rpb24gOCBm
b3IgdGhlIHNlY3VyaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICByYW1pZmljYXRp
b25zIG9mIHJlbW92aW5nIEJHUHNlYyBzaWduYXR1cmVzLik8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICByYW1pZmljYXRpb25zIG9mIHJlbW92aW5nIEJHUHNlYyBzaWduYXR1cmVz
Lik8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJk
aWZmMDAwOSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
PHNwYW4gY2xhc3M9Imluc2VydCI+QWxsIEJHUHNlYyB1cGRhdGUgbWVzc2FnZXMgTVVTVCBjb25m
b3JtIHRvIEJHUCdzIG1heGltdW0gbWVzc2FnZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgIHNpemUuICBJZiB0aGUgcmVzdWx0aW5nIG1lc3NhZ2UgZXhjZWVkcyB0aGUgbWF4
aW11bSBtZXNzYWdlIHNpemUsPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAg
dGhlbiB0aGUgZ3VpZGVsaW5lcyBpbiBTZWN0aW9uIDkuMiBvZiBSRkMgNDI3MSBbUkZDNDI3MV0g
TVVTVCBiZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIGZvbGxvd2VkLjwv
c3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjQuMi4gIENvbnN0cnVjdGluZyB0aGUgQkdQc2VjX1BhdGggQXR0cmlidXRlPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+NC4yLiAgQ29uc3RydWN0aW5nIHRoZSBCR1BzZWNfUGF0aCBB
dHRyaWJ1dGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgV2hlbiBhIEJHUHNl
YyBzcGVha2VyIHJlY2VpdmVzIGEgQkdQc2VjIHVwZGF0ZSBtZXNzYWdlIGNvbnRhaW5pbmcgYTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFdoZW4gYSBCR1BzZWMgc3BlYWtlciBy
ZWNlaXZlcyBhIEJHUHNlYyB1cGRhdGUgbWVzc2FnZSBjb250YWluaW5nIGE8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIEJHUHNlY19QYXRoIGF0dHJpYnV0ZSAod2l0aCBvbmUgb3IgbW9y
ZSBzaWduYXR1cmVzKSBmcm9tIGFuIChpbnRlcm5hbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIEJHUHNlY19QYXRoIGF0dHJpYnV0ZSAod2l0aCBvbmUgb3IgbW9yZSBzaWduYXR1
cmVzKSBmcm9tIGFuIChpbnRlcm5hbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb3Ig
ZXh0ZXJuYWwpIHBlZXIsIGl0IG1heSBjaG9vc2UgdG8gcHJvcGFnYXRlIHRoZSByb3V0ZSBhZHZl
cnRpc2VtZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgb3IgZXh0ZXJuYWwp
IHBlZXIsIGl0IG1heSBjaG9vc2UgdG8gcHJvcGFnYXRlIHRoZSByb3V0ZSBhZHZlcnRpc2VtZW50
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBieSBzZW5kaW5nIGl0IHRvIGl0cyBvdGhl
ciAoaW50ZXJuYWwgb3IgZXh0ZXJuYWwpIHBlZXJzLiAgV2hlbjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIGJ5IHNlbmRpbmcgaXQgdG8gaXRzIG90aGVyIChpbnRlcm5hbCBvciBl
eHRlcm5hbCkgcGVlcnMuICBXaGVuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzZW5k
aW5nIHRoZSByb3V0ZSBhZHZlcnRpc2VtZW50IHRvIGFuIGludGVybmFsIEJHUHNlYy1zcGVha2lu
ZyBwZWVyLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHNlbmRpbmcgdGhlIHJv
dXRlIGFkdmVydGlzZW1lbnQgdG8gYW4gaW50ZXJuYWwgQkdQc2VjLXNwZWFraW5nIHBlZXIsPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGUgQkdQc2VjX1BhdGggYXR0cmlidXRlIFNI
QUxMIE5PVCBiZSBtb2RpZmllZC4gIFdoZW4gc2VuZGluZyB0aGU8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICB0aGUgQkdQc2VjX1BhdGggYXR0cmlidXRlIFNIQUxMIE5PVCBiZSBt
b2RpZmllZC4gIFdoZW4gc2VuZGluZyB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IHJvdXRlIGFkdmVydGlzZW1lbnQgdG8gYW4gZXh0ZXJuYWwgQkdQc2VjLXNwZWFraW5nIHBlZXIs
IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHJvdXRlIGFkdmVydGlzZW1l
bnQgdG8gYW4gZXh0ZXJuYWwgQkdQc2VjLXNwZWFraW5nIHBlZXIsIHRoZTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgZm9sbG93aW5nIHByb2NlZHVyZXMgYXJlIHVzZWQgdG8gZm9ybSBv
ciB1cGRhdGUgdGhlIEJHUHNlY19QYXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgZm9sbG93aW5nIHByb2NlZHVyZXMgYXJlIHVzZWQgdG8gZm9ybSBvciB1cGRhdGUgdGhlIEJH
UHNlY19QYXRoPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
ciBpZD0icGFydC02IiBjbGFzcz0iY2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNraXBwaW5n
IHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy90b29s
cy9yZmNkaWZmL3JmY2RpZmYucHlodCNwYXJ0LTYiPjxlbT4gcGFnZSAzMCwgbGluZSAzNjxzcGFu
IGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFs
bD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC02Ij48ZW0+IHBhZ2UgMzAsIGxp
bmUgMzY8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgYW5kIGxhdGVyIHJlY2VpdmVzIGEgc2Vjb25kIEJHUHNlYyB1cGRhdGUgbWVzc2FnZSBmcm9t
IHRoZSBzYW1lIHBlZXI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbmQgbGF0
ZXIgcmVjZWl2ZXMgYSBzZWNvbmQgQkdQc2VjIHVwZGF0ZSBtZXNzYWdlIGZyb20gdGhlIHNhbWUg
cGVlcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZm9yIHRoZSBzYW1lIHByZWZpeCB3
aXRoIHRoZSBzYW1lIFNlY3VyZV9QYXRoIGFuZCBTS0lzLCB0aGUgc2Vjb25kPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZm9yIHRoZSBzYW1lIHByZWZpeCB3aXRoIHRoZSBzYW1l
IFNlY3VyZV9QYXRoIGFuZCBTS0lzLCB0aGUgc2Vjb25kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICB1cGRhdGUgTUFZIGRpZmZlciBmcm9tIHRoZSBmaXJzdCB1cGRhdGUgaW4gdGhlIHNp
Z25hdHVyZSBmaWVsZHMgKGZvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHVw
ZGF0ZSBNQVkgZGlmZmVyIGZyb20gdGhlIGZpcnN0IHVwZGF0ZSBpbiB0aGUgc2lnbmF0dXJlIGZp
ZWxkcyAoZm9yPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhIG5vbi1kZXRlcm1pbmlz
dGljIHNpZ25hdHVyZSBhbGdvcml0aG0pLiAgSG93ZXZlciwgdGhlIHR3byBzZXRzIG9mPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYSBub24tZGV0ZXJtaW5pc3RpYyBzaWduYXR1
cmUgYWxnb3JpdGhtKS4gIEhvd2V2ZXIsIHRoZSB0d28gc2V0cyBvZjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgc2lnbmF0dXJlIGZpZWxkcyB3aWxsIG5vdCBkaWZmZXIgaWYgdGhlIHNl
bmRlciBjYWNoZXMgYW5kIHJldXNlcyB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBzaWduYXR1cmUgZmllbGRzIHdpbGwgbm90IGRpZmZlciBpZiB0aGUgc2VuZGVyIGNhY2hl
cyBhbmQgcmV1c2VzIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHJldmlvdXMg
c2lnbmF0dXJlLiAgRm9yIGEgZGV0ZXJtaW5pc3RpYyBzaWduYXR1cmUgYWxnb3JpdGhtLCB0aGU8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwcmV2aW91cyBzaWduYXR1cmUuICBG
b3IgYSBkZXRlcm1pbmlzdGljIHNpZ25hdHVyZSBhbGdvcml0aG0sIHRoZTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgc2lnbmF0dXJlIGZpZWxkcyBNVVNUIGJlIGlkZW50aWNhbCBiZXR3
ZWVuIHRoZSB0d28gdXBkYXRlcy4gIE9uIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIHNpZ25hdHVyZSBmaWVsZHMgTVVTVCBiZSBpZGVudGljYWwgYmV0d2VlbiB0aGUgdHdv
IHVwZGF0ZXMuICBPbiB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGJhc2lzIG9m
IHRoZXNlIG9ic2VydmF0aW9ucywgYW4gaW1wbGVtZW50YXRpb24gTUFZIGluY29ycG9yYXRlPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYmFzaXMgb2YgdGhlc2Ugb2JzZXJ2YXRp
b25zLCBhbiBpbXBsZW1lbnRhdGlvbiBNQVkgaW5jb3Jwb3JhdGU8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIG9wdGltaXphdGlvbnMgaW4gdXBkYXRlIHZhbGlkYXRpb24gcHJvY2Vzc2lu
Zy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvcHRpbWl6YXRpb25zIGluIHVw
ZGF0ZSB2YWxpZGF0aW9uIHByb2Nlc3NpbmcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTAiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xh
c3M9ImRlbGV0ZSI+SW4gU2VjdGlvbiAyLjIsIGlzIHdhcyBzdGF0ZWQgdGhhdCBhIEJHUHNlYyBz
cGVha2VyIFNIT1VMRCBhbm5vdW5jZTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUi
PiAgIHN1cHBvcnQgZm9yIHRoZSBjYXBhYmlsaXR5IHRvIHJlY2VpdmUgQkdQIGV4dGVuZGVkIG1l
c3NhZ2VzPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgW0ktRC5pZXRmLWlk
ci1iZ3AtZXh0ZW5kZWQtbWVzc2FnZXNdLiAgTGFjayBvZiBuZWdvdGlhdGlvbiBvZiB0aGlzPC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgY2FwYWJpbGl0eSBpcyBub3QgZXhw
ZWN0ZWQgdG8gcG9zZSBhIHByb2JsZW0gaW4gdGhlIGVhcmx5IHllYXJzIG9mPC9zcGFuPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgQkdQc2VjIGRlcGxveW1lbnQuICBIb3dldmVyLCBh
cyBCR1BzZWMgaXMgZGVwbG95ZWQgbW9yZSBhbmQgbW9yZSwgdGhlPC9zcGFuPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNw
YW4gY2xhc3M9ImRlbGV0ZSI+ICAgQkdQc2VjIHVwZGF0ZSBtZXNzYWdlcyB3b3VsZCBncm93IGlu
IHNpemUgYW5kIHNvbWUgbWVzc2FnZXMgbWF5IGJlPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9
ImRlbGV0ZSI+ICAgZHJvcHBlZCBkdWUgdG8gdGhlaXIgc2l6ZSBleGNlZWRpbmcgdGhlIGN1cnJl
bnQgNEsgYnl0ZXMgbGltaXQuPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAg
VGhlcmVmb3JlLCBpdCBpcyBzdHJvbmdseSBSRUNPTU1FTkRFRCB0aGF0IGFsbCBCR1BzZWMgc3Bl
YWtlcnM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBuZWdvdGlhdGUgdGhl
IGV4dGVuZGVkIG1lc3NhZ2UgY2FwYWJpbGl0eSB3aXRoaW4gYSByZWFzb25hYmxlIHBlcmlvZDwv
c3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIG9mIHRpbWUgYWZ0ZXIgaW5pdGlh
bCBkZXBsb3ltZW50IG9mIEJHUHNlYy48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgSXQgaXMgcG9zc2libGUgdGhhdCBhIHN0dWIgY3VzdG9tZXIgb2YgYW4gSVNQIGVtcGxv
eXMgYSBwcml2YXRlIEFTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSXQgaXMg
cG9zc2libGUgdGhhdCBhIHN0dWIgY3VzdG9tZXIgb2YgYW4gSVNQIGVtcGxveXMgYSBwcml2YXRl
IEFTPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBudW1iZXIuICBTdWNoIGEgc3R1YiBj
dXN0b21lciBjYW5ub3QgcHVibGlzaCBhIFJPQSBpbiB0aGUgZ2xvYmFsIFJQS0k8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBudW1iZXIuICBTdWNoIGEgc3R1YiBjdXN0b21lciBj
YW5ub3QgcHVibGlzaCBhIFJPQSBpbiB0aGUgZ2xvYmFsIFJQS0k8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIGZvciB0aGUgcHJpdmF0ZSBBUyBudW1iZXIgYW5kIHRoZSBwcmVmaXhlcyB0
aGF0IHRoZXkgdXNlLiAgQWxzbywgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgZm9yIHRoZSBwcml2YXRlIEFTIG51bWJlciBhbmQgdGhlIHByZWZpeGVzIHRoYXQgdGhleSB1
c2UuICBBbHNvLCB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGdsb2JhbCBSUEtJ
IGNhbm5vdCBzdXBwb3J0IHByaXZhdGUgQVMgbnVtYmVycyAoaS5lLiAgQkdQc2VjIHNwZWFrZXJz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZ2xvYmFsIFJQS0kgY2Fubm90IHN1
cHBvcnQgcHJpdmF0ZSBBUyBudW1iZXJzIChpLmUuICBCR1BzZWMgc3BlYWtlcnM8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGluIHByaXZhdGUgQVNlcyBjYW5ub3QgYmUgaXNzdWVkIHJv
dXRlciBjZXJ0aWZpY2F0ZXMgaW4gdGhlIGdsb2JhbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIGluIHByaXZhdGUgQVNlcyBjYW5ub3QgYmUgaXNzdWVkIHJvdXRlciBjZXJ0aWZp
Y2F0ZXMgaW4gdGhlIGdsb2JhbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUlBLSSku
ICBGb3IgaW50ZXJhY3Rpb25zIGJldHdlZW4gdGhlIHN0dWIgY3VzdG9tZXIgYW5kIHRoZSBJU1As
IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFJQS0kpLiAgRm9yIGludGVy
YWN0aW9ucyBiZXR3ZWVuIHRoZSBzdHViIGN1c3RvbWVyIGFuZCB0aGUgSVNQLCB0aGU8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGZvbGxvd2luZyB0d28gc2NlbmFyaW9zIGFyZSBwb3Nz
aWJsZTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBmb2xsb3dpbmcgdHdvIHNj
ZW5hcmlvcyBhcmUgcG9zc2libGU6PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IDEuICBUaGUgc3R1YiBjdXN0b21lciBzZW5kcyBhbiB1bnNpZ25lZCBCR1AgdXBkYXRlIGZvciBh
IHByZWZpeCB0bzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDEuICBUaGUgc3R1
YiBjdXN0b21lciBzZW5kcyBhbiB1bnNpZ25lZCBCR1AgdXBkYXRlIGZvciBhIHByZWZpeCB0bzwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgIHRoZSBJU1AncyBBUy4gIEFuIGVkZ2Ug
QkdQc2VjIHNwZWFrZXIgaW4gdGhlIElTUCdzIEFTIG1heSBjaG9vc2U8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgdGhlIElTUCdzIEFTLiAgQW4gZWRnZSBCR1BzZWMgc3Bl
YWtlciBpbiB0aGUgSVNQJ3MgQVMgbWF5IGNob29zZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNyIgY2xhc3M9ImNoYW5nZSI+PHRkPjwv
dGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFydC03Ij48ZW0+
IHBhZ2UgMzgsIGxpbmUgOTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi9yZmNkaWZmLnB5aHQjcGFy
dC03Ij48ZW0+IHBhZ2UgMzgsIGxpbmUgOTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9l
bT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBwcm90b2NvbCkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgcHJvdG9jb2wpLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBJQU5BIGlzIHJlcXVlc3RlZCB0byBkZWZpbmUgdGhlICJCR1BzZWMgQ2FwYWJpbGl0eSIgcmVn
aXN0cnkgaW4gdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSUFOQSBpcyBy
ZXF1ZXN0ZWQgdG8gZGVmaW5lIHRoZSAiQkdQc2VjIENhcGFiaWxpdHkiIHJlZ2lzdHJ5IGluIHRo
ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUmVzb3VyY2UgUHVibGljIEtleSBJbmZy
YXN0cnVjdHVyZSAoUlBLSSkgZ3JvdXAuICBUaGUgcmVnaXN0cnkgaXMgYXM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBSZXNvdXJjZSBQdWJsaWMgS2V5IEluZnJhc3RydWN0dXJl
IChSUEtJKSBncm91cC4gIFRoZSByZWdpc3RyeSBpcyBhczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgc2hvd24gaW4gRmlndXJlIDEwIHdpdGggdmFsdWVzIGFzc2lnbmVkIGZyb20gU2Vj
dGlvbiAyLjE6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc2hvd24gaW4gRmln
dXJlIDEwIHdpdGggdmFsdWVzIGFzc2lnbmVkIGZyb20gU2VjdGlvbiAyLjE6PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgKy0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgKy0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0rLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICB8IEJp
dHMgfCBGaWVsZCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgUmVmZXJlbmNlICB8PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICB8IEJpdHMgfCBGaWVsZCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwgUmVmZXJlbmNlICB8PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tKy0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0t
LS0tLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgfCAwLTMgIHwgVmVyc2lv
biAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgfCAwLTMgIHwgVmVyc2lvbiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgIHwgICAgICA8
c3BhbiBjbGFzcz0iZGVsZXRlIj4rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
Ky0tLS0tLS0tLS0tLSs8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
ICAgICAgfCAgICAgIHwgVmFsdWUgPSAweDAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRl
Ij4gICAgICAgIHw8L3NwYW4+ICAgICAgfCBWYWx1ZSA9IDB4MCAgICAgICAgICAgICAgICAgICAg
ICAgIHwgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+W1RoaXMgUkZDXTwvc3Bhbj4gfDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
ICAgKy0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0t
LS0tKzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgKy0tLS0tLSstLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICB8IDQgICAgfCBEaXJlY3Rpb24gICAgICAgICAgICAg
ICAgICAgICAgICAgIHwgW1RoaXMgUkZDXSB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAgICB8IDQgICAgfCBEaXJlY3Rpb24gICAgICAgICAgICAgICAgICAgICAgICAgIHwg
W1RoaXMgUkZDXSB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIg
aWQ9ImRpZmYwMDEyIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgfCAgICAgIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPistLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwv
c3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICB8ICAgICAgfChC
b3RoIHBvc3NpYmxlIHZhbHVlcyAwIGFuZCAxIGFyZSAgIHwgICAgICAgICAgICB8PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICAgICAgfDwvc3Bh
bj4gICAgICB8KEJvdGggcG9zc2libGUgdmFsdWVzIDAgYW5kIDEgYXJlICAgfCA8c3BhbiBjbGFz
cz0iZGVsZXRlIj5bVGhpcyBSRkNdPC9zcGFuPiB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICB8ICAgICAgfCBmdWxs
eSBzcGVjaWZpZWQgYnkgdGhpcyBSRkMpICAgICAgIHwgICAgICAgICAgICB8PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICB8ICAgICAgfCBmdWxseSBzcGVjaWZpZWQgYnkg
dGhpcyBSRkMpICAgICAgIHwgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0t
LS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICstLS0t
LS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLSs8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgfCA1LTcgIHwgVW5hc3NpZ25lZCAgICAg
ICAgICAgICAgICAgICAgICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgICAgfCA1LTcgIHwgVW5hc3NpZ25lZCAgICAgICAgICAgICAgICAgICAg
ICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyIGlkPSJkaWZmMDAxMyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgIHwgICAgICA8c3BhbiBjbGFz
cz0iZGVsZXRlIj4rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0t
LS0tLSs8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgfCAg
ICAgIHwgVmFsdWUgPSAwMDAgKGluIGJpbmFyeSkgICAgICAgICAgICB8ICAgICAgICAgICAgfDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICAgICAg
IHw8L3NwYW4+ICAgICAgfCBWYWx1ZSA9IDAwMCAoaW4gYmluYXJ5KSAgICAgICAgICAgIHwgPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+W1RoaXMgUkZDXTwvc3Bhbj4gfDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgKy0tLS0t
LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgKy0tLS0tLSstLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIEZpZ3VyZSAxMDogSUFOQSByZWdpc3RyeSBmb3Ig
QkdQc2VjIENhcGFiaWxpdHkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICBGaWd1cmUgMTA6IElBTkEgcmVnaXN0cnkgZm9yIEJHUHNlYyBDYXBhYmlsaXR5Ljwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgRGlyZWN0aW9uIGJpdCAoNHRo
IGJpdCkgaGFzIHZhbHVlIGVpdGhlciAwIG9yIDEsIGFuZCBib3RoIHZhbHVlczwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoZSBEaXJlY3Rpb24gYml0ICg0dGggYml0KSBoYXMg
dmFsdWUgZWl0aGVyIDAgb3IgMSwgYW5kIGJvdGggdmFsdWVzPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBhcmUgZnVsbHkgc3BlY2lmaWVkIGJ5IHRoaXMgZG9jdW1lbnQgKGkuZS4gdGhl
IFJGQyB0aGF0IHJlcGxhY2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYXJl
IGZ1bGx5IHNwZWNpZmllZCBieSB0aGlzIGRvY3VtZW50IChpLmUuIHRoZSBSRkMgdGhhdCByZXBs
YWNlczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZHJhZnQtaWV0Zi1zaWRyLWJncHNl
Yy1wcm90b2NvbCkuICBGdXR1cmUgVmVyc2lvbiB2YWx1ZXMgYW5kIGZ1dHVyZTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtcHJvdG9jb2wp
LiAgRnV0dXJlIFZlcnNpb24gdmFsdWVzIGFuZCBmdXR1cmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHZhbHVlcyBvZiB0aGUgVW5hc3NpZ25lZCBiaXRzIGFyZSBhc3NpZ25lZCB1c2lu
ZyB0aGUgIlN0YW5kYXJkczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHZhbHVl
cyBvZiB0aGUgVW5hc3NpZ25lZCBiaXRzIGFyZSBhc3NpZ25lZCB1c2luZyB0aGUgIlN0YW5kYXJk
czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQWN0aW9uIiByZWdpc3RyYXRpb24gcHJv
Y2VkdXJlcyBkZWZpbmVkIGluIFJGQyA1MjI2IFtSRkM1MjI2XS48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBBY3Rpb24iIHJlZ2lzdHJhdGlvbiBwcm9jZWR1cmVzIGRlZmluZWQg
aW4gUkZDIDUyMjYgW1JGQzUyMjZdLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBJQU5BIGlzIHJlcXVlc3RlZCB0byBkZWZpbmUgdGhlICJCR1BzZWNfUGF0aCBGbGFncyIgcmVn
aXN0cnkgaW4gdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSUFOQSBpcyBy
ZXF1ZXN0ZWQgdG8gZGVmaW5lIHRoZSAiQkdQc2VjX1BhdGggRmxhZ3MiIHJlZ2lzdHJ5IGluIHRo
ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUlBLSSBncm91cC4gIFRoZSByZWdpc3Ry
eSBpcyBhcyBzaG93biBpbiBGaWd1cmUgMTEgd2l0aCBvbmUgdmFsdWU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBSUEtJIGdyb3VwLiAgVGhlIHJlZ2lzdHJ5IGlzIGFzIHNob3du
IGluIEZpZ3VyZSAxMSB3aXRoIG9uZSB2YWx1ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgYXNzaWduZWQgZnJvbSBTZWN0aW9uIDMuMTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBhc3NpZ25lZCBmcm9tIFNlY3Rpb24gMy4xOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICArLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
LS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICB8IEZsYWcgfCBE
ZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFJlZmVyZW5jZSAgfDwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgfCBGbGFnIHwgRGVzY3JpcHRpb24g
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBSZWZlcmVuY2UgIHw8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgKy0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSstLS0tLS0tLS0tLS0rPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIHwgMCAg
ICB8IENvbmZlZF9TZWdtZW50ICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgW1RoaXMgUkZD
XSB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICB8IDAgICAgfCBDb25mZWRf
U2VnbWVudCAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxNCI+PHRkPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj4gICAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPistLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rPC9zcGFuPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIHwgICAgICB8IEJpdCB2YWx1ZSA9IDEgbWVhbnMg
RmxhZyBzZXQgICAgICAgICAgICAgIHwgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgICAgfCAgICAgIHwgQml0IHZhbHVlID0gMSBtZWFucyBGbGFnIHNldCAgICAg
ICAgICAgICAgfCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5bVGhpcyBSRkNdPC9zcGFuPiB8PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICB8ICAgICAgfCAgICAgICAgICAgICAgICAoaW5kaWNhdGVzIENvbmZlZF9TZWdtZW50KSB8
ICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgfCAgICAg
IHwgICAgICAgICAgICAgICAgKGluZGljYXRlcyBDb25mZWRfU2VnbWVudCkgfCAgICAgICAgICAg
IHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgfCAgICAgIHwgQml0IHZhbHVlID0g
MCBpcyBkZWZhdWx0ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIHwgICAgICB8IEJpdCB2YWx1ZSA9IDAgaXMgZGVmYXVs
dCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSstLS0tLS0tLS0tLS0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAr
LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0t
LS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICB8IDEtNyAgfCBVbmFzc2ln
bmVkICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IFtUaGlzIFJGQ10gfDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgfCAxLTcgIHwgVW5hc3NpZ25lZCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgfCBbVGhpcyBSRkNdIHw8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTUiPjx0ZD48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICB8
ICAgICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Ky0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKzwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+ICAgICB8ICAgICAgfCBWYWx1ZTogQWxsIDcgYml0cyBzZXQgdG8gemVybyAg
ICAgICAgICAgICB8ICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
c3BhbiBjbGFzcz0iZGVsZXRlIj4gICAgIHw8L3NwYW4+ICAgICAgfCBWYWx1ZTogQWxsIDcgYml0
cyBzZXQgdG8gemVybyAgICAgICAgICAgICB8IDxzcGFuIGNsYXNzPSJkZWxldGUiPltUaGlzIFJG
Q108L3NwYW4+IHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICstLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICArLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAgICAgIEZpZ3VyZSAxMTogSUFOQSByZWdpc3RyeSBmb3IgQkdQc2VjX1BhdGggRmxhZ3MgZmll
bGQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICBGaWd1cmUgMTE6
IElBTkEgcmVnaXN0cnkgZm9yIEJHUHNlY19QYXRoIEZsYWdzIGZpZWxkLjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBGdXR1cmUgdmFsdWVzIG9mIHRoZSBVbmFzc2lnbmVkIGJp
dHMgYXJlIGFzc2lnbmVkIHVzaW5nIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIEZ1dHVyZSB2YWx1ZXMgb2YgdGhlIFVuYXNzaWduZWQgYml0cyBhcmUgYXNzaWduZWQgdXNp
bmcgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAiU3RhbmRhcmRzIEFjdGlvbiIg
cmVnaXN0cmF0aW9uIHByb2NlZHVyZXMgZGVmaW5lZCBpbiBSRkMgNTIyNjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICJTdGFuZGFyZHMgQWN0aW9uIiByZWdpc3RyYXRpb24gcHJv
Y2VkdXJlcyBkZWZpbmVkIGluIFJGQyA1MjI2PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBbUkZDNTIyNl0uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW1JGQzUyMjZd
LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4xMC4gIENvbnRyaWJ1dG9yczwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjEwLiAgQ29udHJpYnV0b3JzPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTgiIGNs
YXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9z
bWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3Rvb2xzL3JmY2RpZmYvcmZjZGlm
Zi5weWh0I3BhcnQtOCI+PGVtPiBwYWdlIDQwLCBsaW5lIDIyPHNwYW4gY2xhc3M9ImhpZGUiPiDC
tjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNo
YW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy90b29scy9yZmNk
aWZmL3JmY2RpZmYucHlodCNwYXJ0LTgiPjxlbT4gcGFnZSA0MCwgbGluZSAyMjxzcGFuIGNsYXNz
PSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBNYXJrIFJleW5vbGRz
LCBIZWF0aGVyIFNjaGlsbGVyLCBKYXNvbiBTY2hpbGxlciwgUnVlZGlnZXIgVm9saywgYW5kPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgTWFyayBSZXlub2xkcywgSGVhdGhlciBT
Y2hpbGxlciwgSmFzb24gU2NoaWxsZXIsIFJ1ZWRpZ2VyIFZvbGssIGFuZDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgRGF2aWQgV2FyZCBmb3IgdGhlaXIgcmV2aWV3LCBjb21tZW50cywg
YW5kIHN1Z2dlc3Rpb25zIGR1cmluZyB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBEYXZpZCBXYXJkIGZvciB0aGVpciByZXZpZXcsIGNvbW1lbnRzLCBhbmQgc3VnZ2VzdGlv
bnMgZHVyaW5nIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgY291cnNlIG9mIHRo
aXMgd29yay4gIFRoYW5rcyBhcmUgYWxzbyBkdWUgdG8gbWFueSBJRVNHIHJldmlld2VyczwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNvdXJzZSBvZiB0aGlzIHdvcmsuICBUaGFu
a3MgYXJlIGFsc28gZHVlIHRvIG1hbnkgSUVTRyByZXZpZXdlcnM8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIHdob3NlIGNvbW1lbnRzIGdyZWF0bHkgaGVscGVkIGltcHJvdmUgdGhlIGNs
YXJpdHksIGFjY3VyYWN5LCBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB3
aG9zZSBjb21tZW50cyBncmVhdGx5IGhlbHBlZCBpbXByb3ZlIHRoZSBjbGFyaXR5LCBhY2N1cmFj
eSwgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBwcmVzZW50YXRpb24gaW4gdGhl
IGRvY3VtZW50LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHByZXNlbnRhdGlv
biBpbiB0aGUgZG9jdW1lbnQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjExLiAg
UmVmZXJlbmNlczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjExLiAgUmVmZXJlbmNl
czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4xMS4xLiAgTm9ybWF0aXZlIFJlZmVy
ZW5jZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4xMS4xLiAgTm9ybWF0aXZlIFJl
ZmVyZW5jZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
IGlkPSJkaWZmMDAxNiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj5bSS1ELmll
dGYtaWRyLWJncC1leHRlbmRlZC1tZXNzYWdlc108L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0i
ZGVsZXRlIj4gICAgICAgICAgICAgIEJ1c2gsIFIuLCBQYXRlbCwgSy4sIGFuZCBELiBXYXJkLCAi
RXh0ZW5kZWQgTWVzc2FnZTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICAg
ICAgICAgICAgc3VwcG9ydCBmb3IgQkdQIiwgZHJhZnQtaWV0Zi1pZHItYmdwLWV4dGVuZGVkLW1l
c3NhZ2VzLTE0PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgICAgICAgICAg
ICAod29yayBpbiBwcm9ncmVzcyksIERlY2VtYmVyIDIwMTYuPC9zcGFuPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQuaWV0Zi1zaWRyLWJncHNlYy1hbGdzXTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1zaWRyLWJncHNlYy1hbGdzXTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxNyI+PHRk
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj4gICAgICAgICAgICAgIFR1cm5lciwgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Uy4sPC9z
cGFuPiAiQkdQc2VjIEFsZ29yaXRobXMsIEtleSBGb3JtYXRzLCAmYW1wOyBTaWduYXR1cmU8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICBUdXJuZXIsIDxzcGFu
IGNsYXNzPSJpbnNlcnQiPlMuIGFuZCBPLiBCb3JjaGVydCw8L3NwYW4+ICJCR1BzZWMgQWxnb3Jp
dGhtcywgS2V5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgRm9y
bWF0cyIsIDxzcGFuIGNsYXNzPSJkZWxldGUiPmRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtYWxncy0x
Njwvc3Bhbj4gKHdvcmsgaW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAg
ICAgICAgICBGb3JtYXRzLCAmYW1wOyBTaWduYXR1cmUgRm9ybWF0cyIsIDxzcGFuIGNsYXNzPSJp
bnNlcnQiPmRyYWZ0LWlldGYtc2lkci1iZ3BzZWMtPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICAgICAgICAgICAgIHByb2dyZXNzKSwgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
Tm92ZW1iZXIgMjAxNi48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxz
cGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgYWxncy0xODwvc3Bhbj4gKHdvcmsgaW4g
cHJvZ3Jlc3MpLCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5BcHJpbCAyMDE3Ljwvc3Bhbj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXNpZHItYmdwc2VjLXBraS1w
cm9maWxlc108L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtc2lk
ci1iZ3BzZWMtcGtpLXByb2ZpbGVzXTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICBSZXlub2xkcywgTS4sIFR1cm5lciwgUy4sIGFuZCBTLiBLZW50LCAiQSBQcm9maWxl
IGZvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgUmV5bm9s
ZHMsIE0uLCBUdXJuZXIsIFMuLCBhbmQgUy4gS2VudCwgIkEgUHJvZmlsZSBmb3I8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgQkdQc2VjIFJvdXRlciBDZXJ0aWZpY2F0
ZXMsIENlcnRpZmljYXRlIFJldm9jYXRpb24gTGlzdHMsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICBCR1BzZWMgUm91dGVyIENlcnRpZmljYXRlcywgQ2VydGlm
aWNhdGUgUmV2b2NhdGlvbiBMaXN0cyw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
ICAgICAgICAgYW5kIENlcnRpZmljYXRpb24gUmVxdWVzdHMiLCBkcmFmdC1pZXRmLXNpZHItYmdw
c2VjLXBraS08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIGFu
ZCBDZXJ0aWZpY2F0aW9uIFJlcXVlc3RzIiwgZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1wa2ktPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIHByb2ZpbGVzLTIxICh3b3Jr
IGluIHByb2dyZXNzKSwgSmFudWFyeSAyMDE3LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgcHJvZmlsZXMtMjEgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBKYW51YXJ5
IDIwMTcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJQU5BLUFGXSAgIkFk
ZHJlc3MgRmFtaWx5IE51bWJlcnMiLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IFtJQU5BLUFGXSAgIkFkZHJlc3MgRmFtaWx5IE51bWJlcnMiLDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgICAgICAgICAgICAmbHQ7aHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50
cy9hZGRyZXNzLWZhbWlseS1udW1iZXJzLzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgICAgICAgICAgJmx0O2h0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvYWRkcmVz
cy1mYW1pbHktbnVtYmVycy88L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgYWRkcmVzcy1mYW1pbHktbnVtYmVycy54aHRtbCZndDsuPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICBhZGRyZXNzLWZhbWlseS1udW1iZXJzLnhodG1sJmd0
Oy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJw
YXJ0LTkiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hh
bmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3Rvb2xzL3JmY2Rp
ZmYvcmZjZGlmZi5weWh0I3BhcnQtOSI+PGVtPiBwYWdlIDQyLCBsaW5lIDM2PHNwYW4gY2xhc3M9
ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBw
aW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy90
b29scy9yZmNkaWZmL3JmY2RpZmYucHlodCNwYXJ0LTkiPjxlbT4gcGFnZSA0MiwgbGluZSAyNzxz
cGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAg
ICAgICAgIEJ1c2gsIFIuLCAiQkdQc2VjIE9wZXJhdGlvbmFsIENvbnNpZGVyYXRpb25zIiwgZHJh
ZnQtaWV0Zi08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIEJ1
c2gsIFIuLCAiQkdQc2VjIE9wZXJhdGlvbmFsIENvbnNpZGVyYXRpb25zIiwgZHJhZnQtaWV0Zi08
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgc2lkci1iZ3BzZWMtb3Bz
LTE2ICh3b3JrIGluIHByb2dyZXNzKSwgSmFudWFyeSAyMDE3LjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgc2lkci1iZ3BzZWMtb3BzLTE2ICh3b3JrIGluIHBy
b2dyZXNzKSwgSmFudWFyeSAyMDE3LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBbSS1ELmlldGYtc2lkci1iZ3BzZWMtcm9sbG92ZXJdPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgW0ktRC5pZXRmLXNpZHItYmdwc2VjLXJvbGxvdmVyXTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBHYWdsaWFubywgUi4sIFdlaXMsIEIuLCBhbmQg
Sy4gUGF0ZWwsICJCR1BzZWMgUm91dGVyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgICAgICAgICBHYWdsaWFubywgUi4sIFdlaXMsIEIuLCBhbmQgSy4gUGF0ZWwsICJCR1Bz
ZWMgUm91dGVyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIENlcnRp
ZmljYXRlIFJvbGxvdmVyIiwgZHJhZnQtaWV0Zi1zaWRyLWJncHNlYy1yb2xsb3Zlci0wNjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgQ2VydGlmaWNhdGUgUm9s
bG92ZXIiLCBkcmFmdC1pZXRmLXNpZHItYmdwc2VjLXJvbGxvdmVyLTA2PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICh3b3JrIGluIHByb2dyZXNzKSwgT2N0b2JlciAy
MDE2LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgKHdvcmsg
aW4gcHJvZ3Jlc3MpLCBPY3RvYmVyIDIwMTYuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIFtJLUQuaWV0Zi1zaWRyLWRlbHRhLXByb3RvY29sXTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1zaWRyLWRlbHRhLXByb3RvY29sXTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBCcnVpam56ZWVscywgVC4sIE11cmF2c2tp
eSwgTy4sIFdlYmVyLCBCLiwgYW5kIFIuIEF1c3RlaW4sPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICBCcnVpam56ZWVscywgVC4sIE11cmF2c2tpeSwgTy4sIFdl
YmVyLCBCLiwgYW5kIFIuIEF1c3RlaW4sPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHIgaWQ9ImRpZmYwMDE4Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgIlJQS0kg
UmVwb3NpdG9yeSBEZWx0YSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5Qcm90b2NvbCIsIGRyYWZ0LWll
dGYtc2lkci1kZWx0YS08L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
ICAgICAgICAgICAgIlJQS0kgUmVwb3NpdG9yeSBEZWx0YSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5Q
cm90b2NvbCAoUlJEUCkiLCBkcmFmdC1pZXRmLXNpZHItPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICAgICAgICAgICAgIHByb3RvY29s
LTA1PC9zcGFuPiAod29yayBpbiBwcm9ncmVzcyksIDxzcGFuIGNsYXNzPSJkZWxldGUiPkphbnVh
cnk8L3NwYW4+IDIwMTcuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgZGVsdGEtcHJvdG9jb2wtMDg8L3NwYW4+ICh3b3Jr
IGluIHByb2dyZXNzKSwgPHNwYW4gY2xhc3M9Imluc2VydCI+TWFyY2g8L3NwYW4+IDIwMTcuPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQuaWV0Zi1zaWRyLXB1YmxpY2F0
aW9uXTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1zaWRyLXB1
YmxpY2F0aW9uXTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBXZWls
ZXIsIFMuLCBTb25hbGtlciwgQS4sIGFuZCBSLiBBdXN0ZWluLCAiQSBQdWJsaWNhdGlvbjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgV2VpbGVyLCBTLiwgU29u
YWxrZXIsIEEuLCBhbmQgUi4gQXVzdGVpbiwgIkEgUHVibGljYXRpb248L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgUHJvdG9jb2wgZm9yIHRoZSBSZXNvdXJjZSBQdWJs
aWMgS2V5IEluZnJhc3RydWN0dXJlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICAgICAgICAgICBQcm90b2NvbCBmb3IgdGhlIFJlc291cmNlIFB1YmxpYyBLZXkgSW5mcmFzdHJ1
Y3R1cmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMTkiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAoUlBLSSkiLCA8c3BhbiBjbGFzcz0iZGVs
ZXRlIj5kcmFmdC1pZXRmLXNpZHItcHVibGljYXRpb24tMTA8L3NwYW4+ICh3b3JrIGluPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgKFJQS0kpIiwgPHNwYW4g
Y2xhc3M9Imluc2VydCI+ZHJhZnQtaWV0Zi1zaWRyLXB1YmxpY2F0aW9uLTEyPC9zcGFuPiAod29y
ayBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgIHByb2dyZXNz
KSwgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+SmFudWFyeTwvc3Bhbj4gMjAxNy48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICBwcm9ncmVzcyksIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPk1hcmNoPC9zcGFuPiAyMDE3LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBbSS1ELmlldGYtc2lkci1ycGtpLXJ0ci1yZmM2ODEwLWJpc108L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtc2lkci1ycGtpLXJ0ci1yZmM2ODEwLWJp
c108L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgQnVzaCwgUi4gYW5k
IFIuIEF1c3RlaW4sICJUaGUgUmVzb3VyY2UgUHVibGljIEtleTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgQnVzaCwgUi4gYW5kIFIuIEF1c3RlaW4sICJUaGUg
UmVzb3VyY2UgUHVibGljIEtleTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyIGlkPSJkaWZmMDAyMCI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgIEluZnJhc3RydWN0
dXJlIChSUEtJKSB0byBSb3V0ZXIgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+UHJvdG9jb2wiLCBkcmFm
dC1pZXRmLTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAg
ICAgICBJbmZyYXN0cnVjdHVyZSAoUlBLSSkgdG8gUm91dGVyIDxzcGFuIGNsYXNzPSJpbnNlcnQi
PlByb3RvY29sLCBWZXJzaW9uIDEiLDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgICAgICAgICAgICBzaWRyLXJwa2ktcnRyLXJmYzY4
MTAtYmlzLTA4PC9zcGFuPiAod29yayBpbiBwcm9ncmVzcyksIDxzcGFuIGNsYXNzPSJkZWxldGUi
PkphbnVhcnk8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1zaWRyLXJwa2ktcnRyLXJmYzY4
MTAtYmlzLTA5PC9zcGFuPiAod29yayBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICAgICAgICAgICAgIDIwMTcuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAg
ICAgICAgICAgcHJvZ3Jlc3MpLCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5GZWJydWFyeTwvc3Bhbj4g
MjAxNy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXNpZHIt
c2x1cm1dPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0ktRC5pZXRmLXNpZHIt
c2x1cm1dPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRp
ZmYwMDIxIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgTWFuZGVsYmVyZywgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+RC4gYW5kIEQuPC9zcGFuPiBNYSwgIlNpbXBsaWZpZWQgTG9jYWwgaW50ZXJuZXQ8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICBNYW5kZWxiZXJn
LCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5ELiw8L3NwYW4+IE1hLCA8c3BhbiBjbGFzcz0iaW5zZXJ0
Ij5ELiwgYW5kIFQuIEJydWlqbnplZWxzLDwvc3Bhbj4gIlNpbXBsaWZpZWQ8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICBuVW1iZXIgUmVzb3VyY2UgTWFuYWdlbWVu
dCB3aXRoIHRoZSBSUEtJIiwgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+ZHJhZnQtaWV0Zi08L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgTG9jYWwgaW50
ZXJuZXQgblVtYmVyIFJlc291cmNlIE1hbmFnZW1lbnQgd2l0aCB0aGUgUlBLSSIsPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICAgICAgICAgICAg
c2lkci1zbHVybS0wMjwvc3Bhbj4gKHdvcmsgaW4gcHJvZ3Jlc3MpLCA8c3BhbiBjbGFzcz0iZGVs
ZXRlIj5BdWd1c3QgMjAxNi48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9Imluc2VydCI+ZHJhZnQtaWV0Zi1zaWRyLXNsdXJt
LTA0PC9zcGFuPiAod29yayBpbiBwcm9ncmVzcyksIDxzcGFuIGNsYXNzPSJpbnNlcnQiPk1hcmNo
IDIwMTcuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbUkZDNjQ3
Ml0gIEt1bWFyaSwgVy4gYW5kIEsuIFNyaXJhbSwgIlJlY29tbWVuZGF0aW9uIGZvciBOb3QgVXNp
bmc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbUkZDNjQ3Ml0gIEt1bWFyaSwg
Vy4gYW5kIEsuIFNyaXJhbSwgIlJlY29tbWVuZGF0aW9uIGZvciBOb3QgVXNpbmc8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgQVNfU0VUIGFuZCBBU19DT05GRURfU0VU
IGluIEJHUCIsIEJDUCAxNzIsIFJGQyA2NDcyLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgQVNfU0VUIGFuZCBBU19DT05GRURfU0VUIGluIEJHUCIsIEJDUCAx
NzIsIFJGQyA2NDcyLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBE
T0kgMTAuMTc0ODcvUkZDNjQ3MiwgRGVjZW1iZXIgMjAxMSw8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM2NDcyLCBEZWNlbWJlciAy
MDExLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAmbHQ7aHR0cDov
L3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzY0NzImZ3Q7LjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgJmx0O2h0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcv
aW5mby9yZmM2NDcyJmd0Oy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW1JG
QzY0ODBdICBMZXBpbnNraSwgTS4gYW5kIFMuIEtlbnQsICJBbiBJbmZyYXN0cnVjdHVyZSB0byBT
dXBwb3J0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW1JGQzY0ODBdICBMZXBp
bnNraSwgTS4gYW5kIFMuIEtlbnQsICJBbiBJbmZyYXN0cnVjdHVyZSB0byBTdXBwb3J0PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIFNlY3VyZSBJbnRlcm5ldCBSb3V0
aW5nIiwgUkZDIDY0ODAsIERPSSAxMC4xNzQ4Ny9SRkM2NDgwLDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgU2VjdXJlIEludGVybmV0IFJvdXRpbmciLCBSRkMg
NjQ4MCwgRE9JIDEwLjE3NDg3L1JGQzY0ODAsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgICAgIEZlYnJ1YXJ5IDIwMTIsICZsdDtodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3Jn
L2luZm8vcmZjNjQ4MCZndDsuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICBGZWJydWFyeSAyMDEyLCAmbHQ7aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZv
L3JmYzY0ODAmZ3Q7LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgoKICAg
ICA8dHI+PHRkPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZD48L3RkPjwvdHI+CiAgICAgPHRyIGlkPSJlbmQiIGJnY29sb3I9Imdy
YXkiPjx0aCBjb2xzcGFuPSI1IiBhbGlnbj0iY2VudGVyIj4mbmJzcDtFbmQgb2YgY2hhbmdlcy4g
MjEgY2hhbmdlIGJsb2Nrcy4mbmJzcDs8L3RoPjwvdHI+CiAgICAgPHRyIGNsYXNzPSJzdGF0cyI+
PHRkPjwvdGQ+PHRoPjxpPjU0IGxpbmVzIGNoYW5nZWQgb3IgZGVsZXRlZDwvaT48L3RoPjx0aD48
aT4gPC9pPjwvdGg+PHRoPjxpPjMyIGxpbmVzIGNoYW5nZWQgb3IgYWRkZWQ8L2k+PC90aD48dGQ+
PC90ZD48L3RyPgogICAgIDx0cj48dGQgY29sc3Bhbj0iNSIgYWxpZ249ImNlbnRlciIgY2xhc3M9
InNtYWxsIj48YnI+VGhpcyBodG1sIGRpZmYgd2FzIHByb2R1Y2VkIGJ5IHJmY2RpZmYgMS40NS4g
VGhlIGxhdGVzdCB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBmcm9tIDxhIGhyZWY9Imh0dHA6Ly93d3cu
dG9vbHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi8iPmh0dHA6Ly90b29scy5pZXRmLm9yZy90b29s
cy9yZmNkaWZmLzwvYT4gPC90ZD48L3RyPgogICA8L3Rib2R5PjwvdGFibGU+CiAgIAogICAKPC9i
b2R5PjwvaHRtbD4=

--_004_6F27B6F225AB4D8DB6E1866E147B6CAAciscocom_--


From nobody Tue Apr 18 08:26:52 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BBE126C0F; Tue, 18 Apr 2017 08:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 96s72pE_IZqe; Tue, 18 Apr 2017 08:26:48 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47D2126E01; Tue, 18 Apr 2017 08:26:48 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id CC476816B5; Tue, 18 Apr 2017 15:09:29 +0000 (UTC)
Date: Tue, 18 Apr 2017 15:09:29 +0000
From: heasley <heas@shrubbery.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
Message-ID: <20170418150929.GC99602@shrubbery.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nYRoyPOsXIV0tQH3EXZAvLRn2q0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 15:26:50 -0000

Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant:
> 5.  Security Considerations
> 
>    Operators should note the recommendations in Section 11 of BGP
>    Operations and Security [RFC7454].
> 
> SB> You do not address the question of whether there are new
> considerations, or considerations
> SB> that are of increased importance? Is there is text somewhere
> SB> that discusses the integrity and synchronization of the
> parameters
> SB> and any consequences that arise?

I agree that this draft lacks one detail of how RFC7454 applies to it, but
I also note that RFC7454 also does not explain the dangers of ignoring
the recommendations in S11.  I suggest that the subject of removing one's
own communities is subjective and a local issue for which we can only
hypothesize.  I'll try to address the latter, but I do not personally feel
this is necessary.

> ===========
> 
> Minor issues:
> 
> 2.2.  Action Communities
> 
>    Action Communities are added as a label to request that a route be
>    treated in a particular way within an AS.  The operator of the AS
>    defines a routing policy that adjusts path attributes based on the
>    community.  For example, the route's propagation characteristics,
> the
>    LOCAL_PREF (local preference), the next-hop, or the number of
> AS_PATH
>    prepends to be added when it is received or propagated can be
>    changed.
> 
> SB> Although these are well known to the target audience, I think you
> SB> need some references in the above para.

How so?  Do you mean actual community values similar to the example in 3.1.1?
Because these are int 4.x, as 3.x are examples related to 2.1.

> Nits/editorial comments: 
> 
> 6.  IANA Considerations
> 
>    None.
> 
> SB> A little briefer than normal. 

Isn't it elegant. :)

thanks for the review.


From nobody Tue Apr 18 14:10:00 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3843712944A for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:09:58 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 Pg5Y4QYtaB7W for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:09:55 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 874491293EE for <ietf@ietf.org>; Tue, 18 Apr 2017 14:09:55 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 484CA58C4D3; Tue, 18 Apr 2017 23:09:50 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 3527DB0BD3C; Tue, 18 Apr 2017 23:09:50 +0200 (CEST)
Date: Tue, 18 Apr 2017 23:09:50 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Message-ID: <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de>
References: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LQsWzL3qkg5RgyXCqdn5nPG2XLU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 21:09:58 -0000

On Sat, Apr 15, 2017 at 10:54:09PM +0200, JORDI PALET MARTINEZ wrote:
> This shows something that I believe most of the native English IETF participants usually don???t realize when having discussion (I???m referring here in general, also technical discussions) with non-native speakers, and how difficult is for the others. Maybe we should switch to Chinese as the default IETF language, or Spanish, as they have more speakers worldwide than English!

https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers

According to that page, spanish does not have more speakers worldwide than english, but
rather the opposite. And IMHO, the relevant number is really just the number of L2
(second language) speakers, and thats lead by english, followed by malay, french,
mandarin, arabic, hindi, russian, urdu, swahili and then spanish!

> I???m still believe that IAOC attitude is not justified at all, and if we don???t have answers from them by next Monday, we should consider a recall process. Hopefully is not the case.

What do you think is the IAOC attitude ? All i read was very noncommittal and "we
still collect information".

I do not even know what the metric for selection is. I hope it is not to make the
most vocal mailing list participants most happy. I would start with excluding the least
number of candidate participants excluded by travel policies, then the lowest price for
median particiants (flight, hotel, food) and then most convenient. I think
IAOC somehow takes these factors into account, but i can not remember that they did send 
their most concrete data for these factors for various countries to the mailing list.

Cheers
    Toerless


> Regards,
> Jordi
> 
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MARTINEZ <jordi.palet@consulintel.es>;
> Responder a: < jordi.palet@consulintel.es>;
> Fecha: viernes, 14 de abril de 2017, 01:24
> Para: <ietf@ietf.org>;
> Asunto: Re: Update on feedback on US-based meetings, and IETF 102
> 
> Well, for some countries what Trump said, has already been a fact, for example the prohibition to have computers on board. Is not that the case?
> 
> Whatever we want to decide, cancel SF or not, it may highly depend on budget, we like it or not. And that means that we need answers:
> 
>     If we cancel San Francisco, how much that is going to cost to the IETF for each of two planned meetings?
>     
>     Can we cancel the actual hotel contract considering the new US situation? If not, has this been considered for new contracts to avoid this problem?
>     
>     Otherwise there is any reason that can justify the lack of transparency in this?
> 
> The problem is so big for this community that I don???t even agree that the IAOC should take the decision. It must be a collective one, especially when the IAOC is demonstrating thru facts that they don???t care that we are discussing and wasting our time without the minimum relevant data, this is disrespectful and even more, not responding to emails since even since years ago, shows lack of education 
> 
> Regards,
> Jordi
> 
> 
> 
> 
> **********************************************
> 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 use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 

-- 
---
tte@cs.fau.de


From nobody Tue Apr 18 14:23:09 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5970B12785F for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:23:07 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 r1p8-u9aqWpB for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:23:06 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D6AD131479 for <ietf@ietf.org>; Tue, 18 Apr 2017 14:22:58 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2C2B858C4B2; Tue, 18 Apr 2017 23:22:55 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 18DBCB0BD42; Tue, 18 Apr 2017 23:22:54 +0200 (CEST)
Date: Tue, 18 Apr 2017 23:22:54 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Christian Hopps <chopps@chopps.org>, ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
Message-ID: <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6566.1492264901@obiwan.sandelman.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wlAWGhz8FYkzpegDSZ3djILcrvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 21:23:07 -0000

On Sat, Apr 15, 2017 at 10:01:41AM -0400, Michael Richardson wrote:
> My argument is as follows:  if a significant number of people can not attend
> in person due to visa, travel, etc. issues, then the value of the meeting
> declines.   The people that we interact with a high bandwidth become the same
> set of people who can get through.  Our views become myopic.

I will contend that there more easier ways to improve the value of the meeeting
than trying to figure out which city/country might score a bit better on the
visaa-trouble/pricing/convenience scale.

For example, there is a lot of death by powerpoint in meetings that pushes off
high bandwidth discussions ("oh, we're out of time"). AFAIK, most active work
on drafts during IETF meeting week happens outside of the WG meetings. I think that
a) was not the original plan, and b) i have not seen IAOC sending around questionaires
what/how to improve the quality of the meetings in this respect.

Cheers
    toerless

> So in the case where we can not have everyone in the same place, then it
> would be fairer to have "everyone" remote.
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 


From nobody Tue Apr 18 14:34:10 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 926A6127A97 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 ItRoj_5scL3J for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 14:34:05 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85FEE127873 for <ietf@ietf.org>; Tue, 18 Apr 2017 14:34:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6337ABE55; Tue, 18 Apr 2017 22:34:02 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyaNvIgKvJDW; Tue, 18 Apr 2017 22:34:01 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DEF08BE3E; Tue, 18 Apr 2017 22:34:00 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492551241; bh=wYa2MXtMWxZ0k238MPAYzLD/dHxC7oqQnRyP1lk8SoY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=hsiGadLgCux082Fof442GuwIuuya228hF8A0+uXl3b9nvzhzaeQk5cooyoNwXKvlH CfslYYpGYk/q9qR5yPVEQwql7d0XOeBbY2roPvy1lE0lM137rBgedWk5zbfCYXRu4K a2EFJWIOeY8wePDMJYFcrqNGqJu02G54uU7gPJ7o=
Subject: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
To: Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
Cc: ietf@ietf.org
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Date: Tue, 18 Apr 2017 22:34:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GQIWDSwUfcS5408ah2PsPmAVvjGktK7dp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oZOer93eWmmJtOVa0YEOfnmKGNo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 21:34:08 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GQIWDSwUfcS5408ah2PsPmAVvjGktK7dp
Content-Type: multipart/mixed; boundary="OVRstGksd5gKjPj2XnI744sIBC7m2WGnr";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Toerless Eckert <tte@cs.fau.de>,
 Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Message-ID: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Subject: Structure of IETF meeting weeks (was: Re: IAOC requesting input on
 (potential) meeting cities)
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
 <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
 <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
 <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
 <10890.1492007455@obiwan.sandelman.ca>
 <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
 <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
 <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
 <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>

--OVRstGksd5gKjPj2XnI744sIBC7m2WGnr
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 18/04/17 22:22, Toerless Eckert wrote:
> For example, there is a lot of death by powerpoint in meetings that pus=
hes off
> high bandwidth discussions ("oh, we're out of time"). AFAIK, most activ=
e work
> on drafts during IETF meeting week happens outside of the WG meetings. =
I think that
> a) was not the original plan, and b) i have not seen IAOC sending aroun=
d questionaires
> what/how to improve the quality of the meetings in this respect.

I agree with the criticism, but not sure I agree about surveys being
the best next step.

One suggestion I made before I exited the IESG was that we consider
changing (or experimenting with) how the meeting week is structured,
for example, only having formal WG sessions in the afternoons, and
leaving the full mornings free for hackathons or informal meetings.
(Partly, that's because I hate getting out of bed early, which sadly
was not considered sufficient justification:-)

Anyway, I think it'd be good if the IESG/IAOC encouraged experiments
in such ways of organising ourselves when loads of us do end up in
one place for a week or so.

Cheers,
S.


--OVRstGksd5gKjPj2XnI744sIBC7m2WGnr--

--GQIWDSwUfcS5408ah2PsPmAVvjGktK7dp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY9oZIAAoJEC88hzaAX42iL6gH/1TfMNUg+kmj/Vg0k9EKtkKY
JfOLwnMtfgRNxkJtS5K1OT6ppKoRigLqKuUtNyM55F2oCDuYYRW8HxYe6CQQBpA9
eV9+p6W8MDH887lxSWlkpD0u+lt5zhdrc7En2pf7W2tL9uF2kllwVCr5+W0MCLBe
9wjICM8Se/dWl++9A5/JNyosc7GCvVBKfG7ELy0jmPR5/iu7kgWKrYDOE+YuJtQt
YaMk4N2OVwVvWlVXTH9I5fxXanZM8wTh8k5rTyZPEDCnT8edpV0bv+2bzaD10Mww
0J8B5jZCf8Ylhmvj6+c0ZqDv3uX3I437LeAaIiSLNi/CmSItnq/iVyDp2AxAMUE=
=z/UG
-----END PGP SIGNATURE-----

--GQIWDSwUfcS5408ah2PsPmAVvjGktK7dp--


From nobody Tue Apr 18 15:20:12 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54C31314B0 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 rLl8vZKibh5l for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C9961314B2 for <ietf@ietf.org>; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTP id 16F2D20047604; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=s6oZFVLaxO4tlb dhzvOvhYQWynA=; b=jgC0vcfjGO4GdnUzbf7XklH1h+zEXQ7LIzUmp7wqPWWwtm Je5L7BOQjatY2PPAZwflJbZlOEBaT4S0j6RPkOJy60zrzvWSzf9/f9lNd9w6LF0O pzXT5sgGxlmj7YQmrzJB2jaqukeu68sHU5FxquQPLiOspOQH1Dm1cYXW4pk5o=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTPSA id A24E020047603; Tue, 18 Apr 2017 15:20:08 -0700 (PDT)
Date: Tue, 18 Apr 2017 17:20:06 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>
Subject: Re: Predictable Internet Time
Message-ID: <20170418222004.GB2856@localhost>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2R5ab1461YSw0U9LJiXIdT25ySo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 22:20:11 -0000

On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
> As I said, I want 30-100 years lead time so I can bake the schedule into
> devices and remove a trust dependency.

30 years' lead time for leap seconds?  Can't be done.

Leap seconds depend on events such as earthquakes.

You can estimate their frequency, but you can't estimate when they'll be
inserted.

Nico
-- 


From nobody Tue Apr 18 15:43:12 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18B81314D4 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:43: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, 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 UJu9dox70BX7 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:43:09 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (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 D43361314D3 for <ietf@ietf.org>; Tue, 18 Apr 2017 15:43:09 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id 63so3293093pgh.0 for <ietf@ietf.org>; Tue, 18 Apr 2017 15:43:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=F+poz8t1IEV0jR8le7OF7UI+OBBc8CwjdeIEBpaoipA=; b=mF8CZ9OkhAXXr6F0fuBrlluz0aVNmzipioPE8sda02/ecCwlPbkhdpcNFfK4GrMyBM RHQIMbKCIKCF9e4/4E80zaLMvKIICnFDpSoih0KhEnilXudKwF2mB8fAeO/RCW11Qdkg XpCCdNU4+2hvZihaR6SKC90VUvf+lbCRWaSsMU7VJ95SfjnYlPnFmn7qyWmQUDC+ovEa BJwXpSjtmB74tmeZWDm6bmRImqWbexVNXiB15u7i+0BD26RU1iwPlxV+CefeFL6yhh31 IjvtLmifZKu3d/fY6t7BKJfjxqmDCeRwG5aaRgiDtQR9fS+I1TF5/F37zIwGy+hQYqUX B+Nw==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=F+poz8t1IEV0jR8le7OF7UI+OBBc8CwjdeIEBpaoipA=; b=WD3Ubqc8ALciLrJRJoB9r8H/kDDmWXtfE1j1SjQb6O0ehnDnJOjJ98IzxaU3GHxo2Q oupAI6j4Zd8+lxiXRkkMxqRURv5J9rJ9tk6XfIYTE6tAsBg5hpcGvno2EzA22CEpwJUy 5b16Dxsi9eyn9q3DKkv4UlroPb//D+LSJbhFrjxCBf2SyWE/crKjXTosfA2Ne6DZLpJt i+Xdj97B+AJl2Ss4FNaUdX+OXq2rQEWPMGD6Xlbkrlwm8uxLJcxYN3vOWmGroCEtejwv L51Wfp3ZFKzrfhzMXmAjjtcJL7IlXIjVvVBNv3ZgWAoJ6gijwx/5BBU7iC5K0Vl2SO+P RAJA==
X-Gm-Message-State: AN3rC/7h6ssfO9o4VD7GkUEWDgI/INpnRNwgkGALgKV54HA6HI8XmhVd UT1n6iBxJR1z2Q==
X-Received: by 10.99.160.1 with SMTP id r1mr20097993pge.37.1492555389373; Tue, 18 Apr 2017 15:43:09 -0700 (PDT)
Received: from ?IPv6:2406:e001:5724:1:28cc:dc4c:9703:6781? ([2406:e001:5724:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id p11sm463825pfl.4.2017.04.18.15.43.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 15:43:08 -0700 (PDT)
Subject: Re: Structure of IETF meeting weeks
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Cc: ietf@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a2de43e1-62c8-76ed-1b98-023e50be561e@gmail.com>
Date: Wed, 19 Apr 2017 10:43:09 +1200
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: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3JQ3RCgy29JDHRuuK4SBplA-pok>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 22:43:11 -0000

On 19/04/2017 09:34, Stephen Farrell wrote:
> 
> Hiya,
> 
> On 18/04/17 22:22, Toerless Eckert wrote:
>> For example, there is a lot of death by powerpoint in meetings that pushes off
>> high bandwidth discussions ("oh, we're out of time"). AFAIK, most active work
>> on drafts during IETF meeting week happens outside of the WG meetings.

It's true. And that is *exactly* the problem with meetings where a large fraction
or even a majority of attendees are remote. They are automatically excluded from
that informal active work. So, be careful what you wish for.

>> I think that
>> a) was not the original plan, and b) i have not seen IAOC sending around questionaires
>> what/how to improve the quality of the meetings in this respect.
> 
> I agree with the criticism, but not sure I agree about surveys being
> the best next step.
> 
> One suggestion I made before I exited the IESG was that we consider
> changing (or experimenting with) how the meeting week is structured,
> for example, only having formal WG sessions in the afternoons, and
> leaving the full mornings free for hackathons or informal meetings.
> (Partly, that's because I hate getting out of bed early, which sadly
> was not considered sufficient justification:-)

Exactly why it should be the other way round: meetings start at 09:00
sharp, and informal sessions after 14:00.  People are deadline driven...
 
> Anyway, I think it'd be good if the IESG/IAOC encouraged experiments
> in such ways of organising ourselves when loads of us do end up in
> one place for a week or so.

Certainly, nudging everybody away from "I came to the IETF to make my
presentation" would be a Good Thing.

    Brian


From nobody Tue Apr 18 15:52:59 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136D51314DD for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 O3aYLcAbYyt9 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:52:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C90B1314D8 for <ietf@ietf.org>; Tue, 18 Apr 2017 15:52:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9A114BE39; Tue, 18 Apr 2017 23:52:53 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szg2iCHQbHI8; Tue, 18 Apr 2017 23:52:52 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 43BBCBDD8; Tue, 18 Apr 2017 23:52:52 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492555972; bh=fdViv6qQTQOzZVbQyzkRrkgZb9GhOPyIIHeJNEHncqQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=G6FA8eJ51g9VGsSjDjC3TFmR3BBWdynnW9XBBpsu6AZ+bOIc9cJvuPtLT5JeV0hVb pyLUk93fquqiEo/n6VgVMQHkdQEI0AXRBo9S3sPi+9oLqRR1XlaOarvOhfXM1f0IDG 9+KNV2uSRTK6Auj7X+qDV2p3yTWxH2B1vLS2Y5Dc=
Subject: Re: Structure of IETF meeting weeks
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <a2de43e1-62c8-76ed-1b98-023e50be561e@gmail.com>
Cc: ietf@ietf.org
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <bc34534c-88e9-5d15-0272-3e9034a549ae@cs.tcd.ie>
Date: Tue, 18 Apr 2017 23:52:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a2de43e1-62c8-76ed-1b98-023e50be561e@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6IaoxbJQL7c6i9e0evKaRTKuA9uBiRjhp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/smejnWTQy4Nix2qUjRTAAODldnM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 22:52:58 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6IaoxbJQL7c6i9e0evKaRTKuA9uBiRjhp
Content-Type: multipart/mixed; boundary="M7JTM3taFkbMvDnCjOjjiiOcPk4b9lEEQ";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
 Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Message-ID: <bc34534c-88e9-5d15-0272-3e9034a549ae@cs.tcd.ie>
Subject: Re: Structure of IETF meeting weeks
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
 <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
 <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
 <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
 <10890.1492007455@obiwan.sandelman.ca>
 <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
 <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
 <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
 <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
 <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
 <a2de43e1-62c8-76ed-1b98-023e50be561e@gmail.com>
In-Reply-To: <a2de43e1-62c8-76ed-1b98-023e50be561e@gmail.com>

--M7JTM3taFkbMvDnCjOjjiiOcPk4b9lEEQ
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 18/04/17 23:43, Brian E Carpenter wrote:
> Exactly why it should be the other way round: meetings start at 09:00
> sharp, and informal sessions after 14:00.  People are deadline driven..=
=2E

Actually, yes, you're right. Now that I don't need to be at so many
formal meetings, I would happily snooze corrected:-)

S.


--M7JTM3taFkbMvDnCjOjjiiOcPk4b9lEEQ--

--6IaoxbJQL7c6i9e0evKaRTKuA9uBiRjhp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY9pjDAAoJEC88hzaAX42ie5UIAI2LlmGAZn4a8IDPHHTTNL8z
IiplSpfLdR4zXgh2ratMJUNkCTkgEQ2CVA1ylFlegwSmj49vbEOtKCjA4ZuPbJOq
n5qksoQaXQb3k3uX7H2j6NLPicFIzPOKFCixemcuD4laiJuWE+EsctfaRyyjeXcL
EjqY/AKFVa57DqheGhV7Qut0bNQEg3jocLFo2r0YBGqcrkGTuOh/DOBnsqgLLfPj
Ji9trv/pbIhvWpn+mDUW09Cejn+Mtx3XAZLUGMSo1ovQpuA/7nA1PMEF3JwLRgfN
eHotptKRuVFkdQ0VX9Mti4TxrBktN1SSZhoGjwnWZWg84d5zYGvMN/4QRoNW0LM=
=ewfy
-----END PGP SIGNATURE-----

--6IaoxbJQL7c6i9e0evKaRTKuA9uBiRjhp--


From nobody Tue Apr 18 16:08:54 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2216F1314EB for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 NHHGDOyYLzuG for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:08:50 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 2A3D61314D5 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:08:50 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id o22so11474073iod.3 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:08:50 -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=XNarIW8w/LeSBA3Uu1ZPtplIX47eAQw1WEg2Y/6WTEo=; b=eo7uIsFHZ5HOF72+IyOH9STUx4GvhF6/DrCx8mmpSlrnpe+UbobR3suBK+ZI9VT/YP ihemvf1xm5V2+aSMR5NL4ESIuEIAONwAxo5hDXd9wDL0z9s3VTsH9/8XBKJTYPyePx0f y31uFT7OU/9s+bl45XhaCndzA+LRaqxprAAJwZ1Qj1YL4hIselUxt4sKNltToqBwyfPC b6v2SAkyQ4RbVpCtrB3bIaPJa7TClB2i71XF0rYDK6Ui51BY3cmqbVdf1Y70A+cr35FP m/GXhkrnOD6yB4Nkd0MI7K6390TY9RDL44Jjx62SOyXygVM1aTqBaqgHIExAkAS8aDg6 wzzA==
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=XNarIW8w/LeSBA3Uu1ZPtplIX47eAQw1WEg2Y/6WTEo=; b=j6utP0nKJ838YLeFh/twZggSCCHxjrFUjY9Dpe2Spg3HvdGcV6zSW89UP4m3aU4BM0 8hmTe1XB9XQxSPQqXU8WYI1p3XDXO6Y0zT2l2A+RvfkPNyxeH0GOOd4iLwouqKApgQJs esziuTvK2BIaK0L0eDc+9ycXDgcPkYbEZTkW9UI+0e9bxuMIi/xlaA9QlCTuA7xQmqgI pqSrEml7gcEnNm9koJIOkU1pd3oB4ZIv6Znvh8uLlYRGRiYGLrbPNbC+lput9jBXFwUt G+sWS7i+bCjVHtbWjORu/xqLYGlSDVkMWYKrRnUDSAx+p8gHlRmRt2Psj7AGmNg3nXvq rulQ==
X-Gm-Message-State: AN3rC/4c2jnZRVRfwRnNTBJ+R8WLVnaYxwkebqqpbbRJK869eX3ljnsO UrRX/Z9DhtNYdg==
X-Received: by 10.107.22.194 with SMTP id 185mr433071iow.122.1492556929612; Tue, 18 Apr 2017 16:08:49 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id 12sm487748itl.31.2017.04.18.16.08.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 16:08:48 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DB0F78A3-4D17-45C7-8835-774B3E089C1D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
Date: Tue, 18 Apr 2017 16:08:46 -0700
In-Reply-To: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Cc: Bob Hinden <bob.hinden@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF <ietf@ietf.org>
To: Toerless Eckert <tte@cs.fau.de>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TF2wbcrngT8OQ8RMtLH2ZYZcZVE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:08:52 -0000

--Apple-Mail=_DB0F78A3-4D17-45C7-8835-774B3E089C1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Toerless,

Responding with this thread as it=E2=80=99s not about meeting locations.

> On Apr 18, 2017, at 2:34 PM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:
>=20
> Hiya,
>=20
> On 18/04/17 22:22, Toerless Eckert wrote:
>> For example, there is a lot of death by powerpoint in meetings that =
pushes off
>> high bandwidth discussions ("oh, we're out of time"). AFAIK, most =
active work
>> on drafts during IETF meeting week happens outside of the WG =
meetings. I think that
>> a) was not the original plan, and b) i have not seen IAOC sending =
around questionaires
>> what/how to improve the quality of the meetings in this respect.

Regarding powerpoint, the problem isn't the use of slides, it the w.g., =
chairs not dealing with presenters who shows up with 20 slides for a 10 =
minutes slot, and the chairs not allocating enough time for a real =
discussions.

I think the meetings would be a lot more productive if a w.g. could have =
a meeting at the start of the week, work on the the issues during the =
week, send updates to the mailing list, have email and face to face =
discussions, and then have a second session at the end of the week to =
get consensus.  Clearly, impossible to schedule this with our current =
number of working groups, but I think it would make for a more =
productive week.

Bob




--Apple-Mail=_DB0F78A3-4D17-45C7-8835-774B3E089C1D
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-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJY9px/AAoJEK7rdBF357uozGQH/3ZchDdAhM2HQCwcXwj6jdl9
sMCkOCruEYh/maPjqv9x4QsI7TOqoTbvNffXgTJfhTwSHUCW+iwmFtI+rTlMSU1I
AYNXDTTszMEy2/6DFg/Is/nnL5SMmgGnEUqUgtOiqYcebORFczTAnWvfmdFHDemV
JZRBRaGmJLyeGanH5JjpXdFuG9oaLd71jSQC8UaSegs/p/eMyTW900isKL958tU3
BHEFN6sU04yEEG67SZIejOY2p6vx7Q6KhDGG4DDJfTiGlQdj2YpCZsiLdnN3s4sM
q6nefMGqUnD90j6bYfQ1cDIgHBg+L4Xv5SZtQNUR/mL6BKfwQRKFWQXBNWDQfkw=
=PvJf
-----END PGP SIGNATURE-----

--Apple-Mail=_DB0F78A3-4D17-45C7-8835-774B3E089C1D--


From nobody Tue Apr 18 16:21:42 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DF812946E for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:21:39 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 6ZOc2EJlFrbU for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:21:32 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06C421314F7 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:21:30 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2FFF158C4B2; Wed, 19 Apr 2017 01:21:27 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 14EABB0BD47; Wed, 19 Apr 2017 01:21:26 +0200 (CEST)
Date: Wed, 19 Apr 2017 01:21:26 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Nico Williams <nico@cryptonector.com>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, Patrik F?ltstr?m <paf@frobbit.se>
Subject: Re: Predictable Internet Time
Message-ID: <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
References: <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170418222004.GB2856@localhost>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tJV6ih7fhEdt0raqLtbj3hfLfDY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:21:39 -0000

Nice!

Why not start to tackle the problem pragmatically before asking for standards
when its clearly a political issue.

a) RFC describing the problems developers and system deployments can face
  because of leap seconds.
b) And best current practices to get around those issues. Eg: Expect clock
  smear on Jan 1 == reduced accuracy of ~1. Unless OS or other trusted
  info source gives explicit indication: NO leap, no smear.
c) And finally a description of the worst open issues when b) is applied.
   Anything worse than labels on products "reduced functionality on Jan 1
   after a leap second" ?

Cheers
    Toerless

On Tue, Apr 18, 2017 at 05:20:06PM -0500, Nico Williams wrote:
> On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
> > As I said, I want 30-100 years lead time so I can bake the schedule into
> > devices and remove a trust dependency.
> 
> 30 years' lead time for leap seconds?  Can't be done.
> 
> Leap seconds depend on events such as earthquakes.
> 
> You can estimate their frequency, but you can't estimate when they'll be
> inserted.
> 
> Nico
> -- 

-- 
---
tte@cs.fau.de


From nobody Tue Apr 18 16:44:56 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AFC1293EC for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:44:55 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 duJRW4LwuI26 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:44:54 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18803126B6D for <ietf@ietf.org>; Tue, 18 Apr 2017 16:44:54 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id B207A58C4B2; Wed, 19 Apr 2017 01:44:50 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 9AA55B0BD41; Wed, 19 Apr 2017 01:44:50 +0200 (CEST)
Date: Wed, 19 Apr 2017 01:44:50 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
Message-ID: <20170418234450.GE5937@faui40p.informatik.uni-erlangen.de>
References: <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FGISzBp3oaOqlbYoDnWC639BOw8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:44:55 -0000

On Tue, Apr 18, 2017 at 04:08:46PM -0700, Bob Hinden wrote:
> Regarding powerpoint, the problem isn't the use of slides, it the w.g., chairs not dealing with presenters who shows up with 20 slides for a 10 minutes slot, and the chairs not allocating enough time for a real discussions.

Right.

So how about we experiment with allowing recordings of presentations to be added to
the meeting material upfronts. Aka: you can have a long detailled presentation, but not
during the WG time slot, but upload it eg: one week in before. Then during your 10 min slot
you can have only <= 4 slides.

Not sure what our current tooling would say about presentation recording files.
Whats the best current "standard" for that, eg: file format with slides and audio
that can be created by multiple apps...

I know what you're thinking "another idiot that thinks technology can improve the world".
Guilty.

> I think the meetings would be a lot more productive if a w.g. could have a meeting at the start of the week, work on the the issues during the week, send updates to the mailing list, have email and face to face discussions, and then have a second session at the end of the week to get consensus.  Clearly, impossible to schedule this with our current number of working groups, but I think it would make for a more productive week.

Thats what we try to do in anima where we luckily did get two meetings so far.
This is non-applicable to more WGs because the cost for more smaller rooms goes up,
or multitaskers could not multiplex enough work anymore ??

Toerless

> Bob
> 
> 
> 



-- 
---
tte@cs.fau.de


From nobody Tue Apr 18 16:53:48 2017
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF66B1293EC for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.104
X-Spam-Level: 
X-Spam-Status: No, score=-0.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_MIMEOLE=1.899, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
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 2QDVplLCzluO for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:53:45 -0700 (PDT)
Received: from gondrom.org (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DFDC12773A for <ietf@ietf.org>; Tue, 18 Apr 2017 16:53:45 -0700 (PDT)
Received: from seraph (x5ce4409f.dyn.telefonica.de [92.228.64.159]) by gondrom.org (Postfix) with ESMTPSA id A009E649EA; Wed, 19 Apr 2017 01:53:43 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=qodwgRBZTdwDQqFB+oPdW5RIAJq1VWHEeO6aTxxyttEy6gkRKqXxBFugEu8Eqkad3EXQFT37qUh1Nb9nBx27H6cNm5OdKsKCKevJzmAo3dOipsARfcjQwjmgS/WUkucRHXebeFGN5uFihW1w0Das7lUzgNig8kI7ZlCHEQtDqeg=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:Thread-Index:Content-Language:Importance;
From: "Tobias Gondrom" <tobias.gondrom@gondrom.org>
To: "'Bob Hinden'" <bob.hinden@gmail.com>, "'Toerless Eckert'" <tte@cs.fau.de>
Cc: "'Michael Richardson'" <mcr+ietf@sandelman.ca>, "'IETF'" <ietf@ietf.org>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
In-Reply-To: <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
Subject: RE: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
Date: Wed, 19 Apr 2017 01:53:38 +0200
Message-ID: <004a01d2b89f$01469740$03d3c5c0$@gondrom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJFGqovNtf1uRc6szM4m5pwBAJ16gJh8oUHA5KikxgBt38BKAIbp3TrAnzs6jEBSR1mEQFhnYp9AMLftloC4U3kGALuGgGxAqc+CeICO78FPKAT4Lzw
Content-Language: en-us
Importance: Low
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YYQBTiAo1gkama6gYDdHB_3w9jI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:53:47 -0000

<IAOC hat =3D "off">
Ps.: and I would like to add that at least in my personal understanding =
the content and format of the WG meetings is under the mandate of the WG =
chairs, the IESG and IETF chair. Same like the IETF meeting agenda is =
also not set by the IAOC. Of course the IAOC could (and I assume would =
be happy to) include questions from the IESG into the usual meeting =
survey, but I don't think it is the IAOC's place to discuss the content =
or how many Powerpoints are used within the WG meeting. IMHO that is for =
WG chairs and IESG to decide. And with these expectations, it is the =
IAOC task to arrange for an environment that is supporting to fulfill =
the expectations from the WG chairs, IETF and the IESG.=20



-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Bob Hinden
Sent: Wednesday, April 19, 2017 1:09 AM
To: Toerless Eckert <tte@cs.fau.de>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>; Bob Hinden =
<bob.hinden@gmail.com>; IETF <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting =
input on (potential) meeting cities)

Toerless,

Responding with this thread as it=E2=80=99s not about meeting locations.

> On Apr 18, 2017, at 2:34 PM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:
>=20
> Hiya,
>=20
> On 18/04/17 22:22, Toerless Eckert wrote:
>> For example, there is a lot of death by powerpoint in meetings that=20
>> pushes off high bandwidth discussions ("oh, we're out of time").=20
>> AFAIK, most active work on drafts during IETF meeting week happens=20
>> outside of the WG meetings. I think that
>> a) was not the original plan, and b) i have not seen IAOC sending=20
>> around questionaires what/how to improve the quality of the meetings =
in this respect.

Regarding powerpoint, the problem isn't the use of slides, it the w.g., =
chairs not dealing with presenters who shows up with 20 slides for a 10 =
minutes slot, and the chairs not allocating enough time for a real =
discussions.

I think the meetings would be a lot more productive if a w.g. could have =
a meeting at the start of the week, work on the the issues during the =
week, send updates to the mailing list, have email and face to face =
discussions, and then have a second session at the end of the week to =
get consensus.  Clearly, impossible to schedule this with our current =
number of working groups, but I think it would make for a more =
productive week.

Bob





From nobody Tue Apr 18 16:59:12 2017
Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4205A129471 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:06 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.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 su75tacGFwrD for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:05 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 625FC129454 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id r190so9352876wme.1 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=Kh0xYTjmgskNnBOGVDhZn9LtH50yrnyxJ439ZHvMvFTWqUlSZL/m1CA0bl237YHyEL x95F0wCozvcHjVhdjm8sXJGfe8jZuzd6vMfZ/HaKKZX4POnP5AkOvfPybKbgA7wsz0k4 XFJTDeJZSd7LlHbprNN0uoMozZWHcNup8vIS5ZCTL1ZN1AwVTHUMicrqWjQOLUFm/Ma+ G/sOa4Frjm8g8Hqqm2FiPrAixFZ3MPS7EQuzI8As0Vx/n8uSWpaAEpAgCJQPCtxmw+aR PMh7rxRdt/LKtShZ0V/u0arHAJTMcJCSMMgfNOpXjiOXU4SSMIt0H2MLaAy4rjBce/89 59pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=LDm+kETlACpYv2lhptkRLVc9stm5sqfcZK2CpbB10ajtJsr84hF4skocdhXlsMicSd y8KjCHOX54E+SbOvBg3Q1vHHshrACjjVNRknWIsTYL4il0l9IxF0nDvkDKaYRggi/BkZ sW4Lh6BkXYKoj9LRHrixcW9eYoX0h2gZLMFQOMUez6XM8vk2Pb5ieaWhT8pNC3pvgwUQ rlQ/S7dGB4PGziyD2cq3wlk3CHryqUC1VB51CLTIUoMYqmU+Ci3D+tuG49yOav4e7AKJ ialZpO+nKdgEcIAY0om4zAu2ibwc+mI6C+DSgrCcmXHlOVU//6+iyNRSwqe00lpc0J6g cAyA==
X-Gm-Message-State: AN3rC/7UBxzELtDPGdZRqvhJjPrarysuK4SD5NUyLQczE/dNvL+67oCQ dVUsdBrg7sL26A==
X-Received: by 10.28.100.195 with SMTP id y186mr15705406wmb.68.1492559940550;  Tue, 18 Apr 2017 16:59:00 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:b007:e025:f7a1:2601]) by smtp.gmail.com with ESMTPSA id 31sm862871wrt.35.2017.04.18.16.58.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 16:58:59 -0700 (PDT)
Date: Wed, 19 Apr 2017 01:58:58 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
Message-ID: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FfX9kpdNJLNZ4gy4gZNYM-IXFxg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:59:06 -0000

Hi Bryant,

Thank you for taking the time to go through the document.

On Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant wrote:
> Please treat these comments just like any other last call comments.
> 
> SB> Even if you just copy the Introduction, the Abstract should
> SB> really be expanded to help the reader understand whether or not
> SB> they want read the RFC or if they had read it what it was about.

OK, we'll copy some text from the introduction section to the abstract
section to provide a better pitch why one would want to read this
document.

> ============
> 
> 5.  Security Considerations
> 
>    Operators should note the recommendations in Section 11 of BGP
>    Operations and Security [RFC7454].
> 
> SB> You do not address the question of whether there are new
> SB> considerations, or considerations that are of increased importance?

It is my understanding that RFC 8092 "BGP Large Communities" are just
like RFC 1997 "BGP Communities", but ...  larger (for lack of better
words). Referencing RFC 7454 seems plenteous.

So, what if there are not any additional considerations, If there were,
they would've been (or are) covered in RFC 8092's security section,
right?

This is an Internet-Draft targetted for Informational status, I'm not
sure what you expect here.

> SB> Is there is text somewhere that discusses the integrity and
> SB> synchronization of the parameters and any consequences that arise?

the what now? Can you elaborate on the above?

> ===========
> 
> Minor issues:
> 
> 2.2.  Action Communities
> 
>    Action Communities are added as a label to request that a route be
>    treated in a particular way within an AS.  The operator of the AS
>    defines a routing policy that adjusts path attributes based on the
>    community.  For example, the route's propagation characteristics,
>    the LOCAL_PREF (local preference), the next-hop, or the number of
>    AS_PATH prepends to be added when it is received or propagated can
>    be changed.
> 
> SB> Although these are well known to the target audience, I think you
> SB> need some references in the above para.

What reference would you suggest? You feel the section 2.2 text cannot
stand on its own?

Kind regards,

Job


From nobody Tue Apr 18 17:14:56 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE531293FF for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 17:14:54 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 jmR3T0kYudzw for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 17:14:53 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F3AA1200C1 for <ietf@ietf.org>; Tue, 18 Apr 2017 17:14:53 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 16CE258C4B2; Wed, 19 Apr 2017 02:14:49 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id F35FAB0BD4D; Wed, 19 Apr 2017 02:14:48 +0200 (CEST)
Date: Wed, 19 Apr 2017 02:14:48 +0200
From: 'Toerless Eckert' <tte@cs.fau.de>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Cc: 'Bob Hinden' <bob.hinden@gmail.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'IETF' <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
Message-ID: <20170419001448.GF5937@faui40p.informatik.uni-erlangen.de>
References: <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com> <004a01d2b89f$01469740$03d3c5c0$@gondrom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004a01d2b89f$01469740$03d3c5c0$@gondrom.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z3jT0PIsnoMkFJtF2HwX6OrjQzE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 00:14:55 -0000

Which is why BC (thanks!) changed the subject of this sub-thread.

But re. IAOC responsibilities: Q: Is it true that the revenue from IETF
meetings does cross-fund other activities like RFC editor etc.. ?

If the goal is not to create the best meeting for the folks helping in producing documents,
but to attract the maximum number of attendees, then we should be clear about it.

I would guess 50% of participants are consuming only. These folks are certainly
well served through death by powerpoint rich dog & pony shows (just me guessing what
i like myself when i go to a WG where i just want to learn). If we focus on work
instead of education and we loose participants and therefore money... Oh well,
then the optimum IETF meeting structure seems to be difficult to define.

Toerless

On Wed, Apr 19, 2017 at 01:53:38AM +0200, Tobias Gondrom wrote:
> <IAOC hat = "off">
> Ps.: and I would like to add that at least in my personal understanding the content and format of the WG meetings is under the mandate of the WG chairs, the IESG and IETF chair. Same like the IETF meeting agenda is also not set by the IAOC. Of course the IAOC could (and I assume would be happy to) include questions from the IESG into the usual meeting survey, but I don't think it is the IAOC's place to discuss the content or how many Powerpoints are used within the WG meeting. IMHO that is for WG chairs and IESG to decide. And with these expectations, it is the IAOC task to arrange for an environment that is supporting to fulfill the expectations from the WG chairs, IETF and the IESG. 
> 
> 
> 
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Bob Hinden
> Sent: Wednesday, April 19, 2017 1:09 AM
> To: Toerless Eckert <tte@cs.fau.de>
> Cc: Michael Richardson <mcr+ietf@sandelman.ca>; Bob Hinden <bob.hinden@gmail.com>; IETF <ietf@ietf.org>
> Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
> 
> Toerless,
> 
> Responding with this thread as it???s not about meeting locations.
> 
> > On Apr 18, 2017, at 2:34 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> > 
> > Hiya,
> > 
> > On 18/04/17 22:22, Toerless Eckert wrote:
> >> For example, there is a lot of death by powerpoint in meetings that 
> >> pushes off high bandwidth discussions ("oh, we're out of time"). 
> >> AFAIK, most active work on drafts during IETF meeting week happens 
> >> outside of the WG meetings. I think that
> >> a) was not the original plan, and b) i have not seen IAOC sending 
> >> around questionaires what/how to improve the quality of the meetings in this respect.
> 
> Regarding powerpoint, the problem isn't the use of slides, it the w.g., chairs not dealing with presenters who shows up with 20 slides for a 10 minutes slot, and the chairs not allocating enough time for a real discussions.
> 
> I think the meetings would be a lot more productive if a w.g. could have a meeting at the start of the week, work on the the issues during the week, send updates to the mailing list, have email and face to face discussions, and then have a second session at the end of the week to get consensus.  Clearly, impossible to schedule this with our current number of working groups, but I think it would make for a more productive week.
> 
> Bob


From nobody Tue Apr 18 17:33:39 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED0B1293FC for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 17:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 9Nfd4y1Jcw6Z for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 17:33:36 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::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 B1AAC1250B8 for <ietf@ietf.org>; Tue, 18 Apr 2017 17:33:35 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id 88so4364524lfr.0 for <ietf@ietf.org>; Tue, 18 Apr 2017 17:33:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bzIo92MKt1LKMYYXATZMyQo8oTi2KLcXgokHc3VxVtM=; b=PWH9D2AeYNv9fZK+xQLIXC1f+Os+inKdvE8+yM/S5feDxDDjY6SgnR/LVYFwIRBqjI xF924rWAl8VHPWjJO8YDbMzp5ExzLJApXVx0dDBReUYmZwGZp8cG4d8N7liUHfJIee/S wnOA+8Yw8QtZGnbYZT7Eygx1DDL/5cUtvKGKbXWe8U1UQBUu5ZL0aPOb+weJn+dA5k5l eiUdFeevX6MGqcjDz9Ve0jEa1xiD3gO+Tg1jYvF6eFPpM/NHghPt4ad1A9/fV5812l4m PofioHyJMtknHgf2RcpFk1E/I6fXjTKl6OV+NnIwnDO+Rj3vKDtEv7XwPTaFpTAiK0k8 dxSQ==
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=bzIo92MKt1LKMYYXATZMyQo8oTi2KLcXgokHc3VxVtM=; b=YVcyUwtpkGBZXH5PFVtIAYzb6Coyz87LxtFo8goNk01hri4pFEsnTgAy6qOSWN71Cy CMcszKmzc1znk+sDWDF3RIKDEhsMkl24tnlWeueY0eDZ8Y73R6NTOOoS3tQwp0IGeJ7N is7ynYSQGvk5TwVpfDJr1oLZgSMzRNwfliGlqJ5TBnXoUtI2ZofvyFM5zdQrb8wShVZs C/a+u/rtRuBK3FbuFYy4Ms+L8V7/+cg0IP2uGdH/NBPIyga5dVXq1EqIvfS62GKx4hHr RTHi61fhgzwhLHHxWAbikeqKzsVnQ406qvOvOVngLvjavrvO9XENAbEQdrpbkAMI2Hee w21w==
X-Gm-Message-State: AN3rC/4j4YmFAL/mBDbdwaUMh4NTuqk14uVtHmwvcsGo4S8PTSYxAPmg CMIiODnFcafF2uOY/F9flvs6deRHeHCK
X-Received: by 10.46.0.70 with SMTP id 67mr36240lja.113.1492562014098; Tue, 18 Apr 2017 17:33:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.5 with HTTP; Tue, 18 Apr 2017 17:33:33 -0700 (PDT)
In-Reply-To: <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 19 Apr 2017 10:33:33 +1000
Message-ID: <CABkgnnWz-GR5T2KA2i=37=gcbbEj=-RKg_ZRcB+06BFiO8VQ+w@mail.gmail.com>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: mohamed.boucadair@orange.com, "ietf@ietf.org" <ietf@ietf.org>,  "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iGOvBLM1SnzE4qxzwrhnhRdnYIs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 00:33:37 -0000

On 11 April 2017 at 18:51, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>
> (*) That is the argument for draft-mm-effect-encrypt, for which I
> do support publication (apparently in disagreement with Martin in
> that case:-)


Taking a break from email is so refreshing...

I would very much like to see a document like this that captures these
use cases and practices.  The problem I have with it are simple: it
isn't particularly coherent, and it makes statements that I disagree
with.  Those statements are particularly bad because they are also
unnecessary (see Brian Carpenter's comments about facts).


From nobody Tue Apr 18 17:48:30 2017
Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 467AF129416; Tue, 18 Apr 2017 17:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=microsoft.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 EP7w0aeHxg73; Tue, 18 Apr 2017 17:48:20 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0118.outbound.protection.outlook.com [104.47.40.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54E401250B8; Tue, 18 Apr 2017 17:48:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=4B6KXpPBLm61WrTUxH+Ze62Fe+lw3X7Gf/vxddMmao0=; b=aHcF6szGa2jS3Lyzip3UYvE97jcxmmK+5zMScehsSmv0Lmq/SZNQ6YKEdChkc7zQ8D3qUceDwn8dUuQnh1TOcXd5C74xOWlbuiPCP7LYSZic4c6eg8ko593p8dMVeBEc4DcWYhjHxjgzuozctVtl1SilyoeUXcEimwHm6FzsXFM=
Received: from BY2PR21MB0084.namprd21.prod.outlook.com (10.162.78.141) by BY2PR21MB0081.namprd21.prod.outlook.com (10.162.78.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.1; Wed, 19 Apr 2017 00:48:18 +0000
Received: from BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) by BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) with mapi id 15.01.1061.003; Wed, 19 Apr 2017 00:48:18 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Carsten Bormann <cabo@tzi.org>, Mark Nottingham <mnot@mnot.net>
CC: "art@ietf.org" <art@ietf.org>, "draft-ietf-core-coap-tcp-tls.all@ietf.org" <draft-ietf-core-coap-tcp-tls.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>
Subject: RE: Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsa/ruYJAPgRh/k2Aqaxin65fHKG+W1UAgA2IyeA=
Date: Wed, 19 Apr 2017 00:48:17 +0000
Message-ID: <BY2PR21MB008467D682834D2C2826F7F683180@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
In-Reply-To: <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: tzi.org; dkim=none (message not signed) header.d=none;tzi.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR21MB0081; 7:ET2ae8tLyud9HDCn+EOfPnA7KzUPQB31CkIKKmjVaSda6ksrE39XnDmSmLVaKO3WMBCHz/WvrxmDhClNuAuECYCK78HhfbT3AZMqUzTve0ai0FpsOtyPPnW87iRCoMbwqEFHNv6Ig82cJ7RGvkuwBjxiB9UrKo7Yq/6fINVX/xNn5RtUH2YUKDHJhENoyNFaRCtxrn8ZInMdWrGCoyMqViJc8l34NMSJNkbVJPot0ErHWiAtcAedlF4wze6caOH0gFRLcn/v9jrz3cvPTYSo4yGNpCauTSA7kiqUbi2opaKffIvg0z3Fl8hVwYrxaiH87WSssSEmj1/ULSxMcHGWHgVDkZKNAZYGolXBv/eIQ7I=
x-ms-office365-filtering-correlation-id: 38543b9b-667b-4555-10dc-08d486bdc529
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:BY2PR21MB0081; 
x-microsoft-antispam-prvs: <BY2PR21MB0081FB0E63021EF13E0E0ABC83180@BY2PR21MB0081.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406088)(20161123558035)(20161123560025)(6072148); SRVR:BY2PR21MB0081; BCL:0; PCL:0; RULEID:; SRVR:BY2PR21MB0081; 
x-forefront-prvs: 028256169F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39450400003)(39860400002)(39400400002)(52314003)(24454002)(38730400002)(6506006)(54906002)(55016002)(4326008)(66066001)(99286003)(6436002)(9686003)(77096006)(74316002)(76176999)(3846002)(25786009)(6306002)(53936002)(6246003)(54356999)(8936002)(8676002)(102836003)(50986999)(2900100001)(6116002)(7696004)(81166006)(2950100002)(305945005)(7736002)(5660300001)(10290500002)(10090500001)(3660700001)(33656002)(5005710100001)(86612001)(2906002)(3280700002)(189998001)(86362001)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR21MB0081; H:BY2PR21MB0084.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Apr 2017 00:48:17.8034 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR21MB0081
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fLXCcyQaZvWryqAezlFhBBD9lR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 00:48:22 -0000

VGhhbmtzIGZvciB5b3VyIHRob3VnaHRmdWwgZmVlZGJhY2ssIE1hcmsuDQoNCk1hcmsgd3JvdGU6
DQo+PiBTZWN0aW9uIDguMSBtYWtlcyBpdCBNYW5kYXRvcnkgdG8gSW1wbGVtZW50IHRoZSBwcm90
b2NvbCB3aXRob3V0IGFueSANCj4+IHNlY3VyaXR5ICgiTm9TZWMiKS4gVGhpcyBzZWVtcyBjb3Vu
dGVyIHRvIGJlc3QgcHJhY3RpY2UgaW4gdGhlIElFVEYsIA0KPj4gYnV0IEknbGwgZGVmZXIgdG8g
dGhlIFNlY3VyaXR5IEFyZWEgcmV2aWV3Lg0KDQpDYXJzdGVuIHJlc3BvbmRlZDoNCj4gU2luY2Ug
aXQgaXMgdGhlIGltcGxlbWVudGVycyB3aG8gd2lsbCBkZWNpZGUgd2hldGhlciB0aGV5IGltcGxl
bWVudCB0aGlzLCB0aGlzIGNvLWF1dGhvciBjb3VsZCBsaXZlIHdpdGggbWFraW5nIGltcGxlbWVu
dGluZyBOb1NlYw0KPiBjb21wbGV0ZWx5IG9wdGlvbmFsLiAgKEl0IHdpbGwgYmUgYW55d2F5LCBp
biBwcmFjdGljZSwgYXQgdGhlIGxldmVsIG9mIHdoYXQgaXMgYWN0dWFsbHkgY29uZmlndXJlZC4p
ICBUaGUgaW1wb3J0YW50IHBvaW50KCopIGZyb20gdGhlIFdHDQo+IHBlcnNwZWN0aXZlIGhlcmUg
aXMgdGhhdCBUTFMgaXMgbWFuZGF0b3J5IHRvIGltcGxlbWVudCwgd2l0aCB0aGUgc3BlY2lmaWNz
IGRlcGVuZGluZyBvbiB0aGUgc2VjdXJpdHkgbW9kZSBuZWVkZWQgKGNmLiBSRkMgNzkyNSkuIA0K
PiAoTm90ZSBhbHNvIHRoYXQgdGhlcmUgYXJlIG90aGVyIHdheXMgdG8gcHJvdmlkZSBzZWN1cml0
eSB3aXRoIENvQVAuKQ0KDQo+ICgqKSBodHRwczovL2dpdGh1Yi5jb20vY29yZS13Zy9jb2FwLXRj
cC10bHMvY29tbWl0L2ZlMzQ4ZjU0M2ZjNDVlOTgxZTM4ZTkzNTQyNDIwMTJhZmIyOGRjNjANCg0K
U29tZSBjb250ZXh0IC0gZHVyaW5nIHRoZSBzZWN1cml0eSBkaXNjdXNzaW9ucyBpbiB0aGUgV0cs
IHRoZXJlIHdhcyBhIHJlY29tbWVuZGF0aW9uIHRvICJtaXJyb3IiIHRoZSBzaW1pbGFyIHNlY3Rp
b24gaW4gUkZDNzI1Mi4NCg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzcyNTIjc2Vj
dGlvbi05IHN0YXRlczoNCg0KICBUaGUgTm9TZWMgYW5kIFJhd1B1YmxpY0tleSBtb2RlcyBhcmUg
bWFuZGF0b3J5IHRvIGltcGxlbWVudCBmb3IgdGhpcyBzcGVjaWZpY2F0aW9uLg0KDQp3aGljaCBp
cyB3aHkgTm9TZWMgaXMgTVRJLiANCg0KSSBhZ3JlZSB3aXRoIENhcnN0ZW4uIEknZCBiZSBoYXBw
eSB0byBtYWtlIHRoaXMgY29tcGxldGVseSBvcHRpb25hbCBpZiBpdCByZXN1bHRzIGluIGxlc3Mg
ZGlzc29uYW5jZSBmb3IgcmV2aWV3ZXJzIGFuZCB0aGVyZSBhcmUgbm8gb2JqZWN0aW9ucyBpbiB0
aGUgV0cuDQoNCg==


From nobody Tue Apr 18 18:06:23 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E8D124D68; Tue, 18 Apr 2017 18:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 5x8X-9bjccYI; Tue, 18 Apr 2017 18:06:11 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 0E8F31243F3; Tue, 18 Apr 2017 18:06:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d0e4N-0000At-9m; Wed, 19 Apr 2017 01:06:07 +0000
Date: Wed, 19 Apr 2017 10:06:05 +0900
Message-ID: <m2vaq1p5oi.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Job Snijders <job@instituut.net>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
In-Reply-To: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/itW7o3ZdmzwV9wV9I8hjwifNztw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 01:06:12 -0000

>> 5.  Security Considerations
>> 
>>    Operators should note the recommendations in Section 11 of BGP
>>    Operations and Security [RFC7454].
>> 
>> SB> You do not address the question of whether there are new
>> SB> considerations, or considerations that are of increased importance?
> 
> It is my understanding that RFC 8092 "BGP Large Communities" are just
> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
> words). Referencing RFC 7454 seems plenteous.
> 
> So, what if there are not any additional considerations, If there were,
> they would've been (or are) covered in RFC 8092's security section,
> right?
> 
> This is an Internet-Draft targetted for Informational status, I'm not
> sure what you expect here.
> 
>> SB> Is there is text somewhere that discusses the integrity and
>> SB> synchronization of the parameters and any consequences that arise?
> 
> the what now? Can you elaborate on the above?

you're supposed to guess

the normal hack here is

  this document introduces no new security issues beyond those discussed
  in 1997


From nobody Tue Apr 18 18:17:06 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFA5129467 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 18:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=cs.tcd.ie
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 GOXrhCtuj8kS for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 18:17:02 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 093B2129400 for <ietf@ietf.org>; Tue, 18 Apr 2017 18:17:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 830AEBE49; Wed, 19 Apr 2017 02:16:59 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opJ9hdWw4VkN; Wed, 19 Apr 2017 02:16:58 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C9677BE38; Wed, 19 Apr 2017 02:16:57 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1492564618; bh=FD4dCbKz5rn5JKT+x29MRXQwcJd09biL+7JVOmHv/sQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=tUXLANy0KCJcsv+QsjdZHy4fmv3OfajZy3mfqeMnGb2blAKhHwQrmYWCJN25ZNCFr LUh8vkET6yC2HJp5AI+/gskZswj3dpGJQnW8HziF705OiwyTMqSDPbhiY9PikANCGy JwrLXKSVBmOKG0vunm0cJbXCN8H1Fh+E6asBrRVg=
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of draft-mm-wg-effect-encrypt-09)
To: Martin Thomson <martin.thomson@gmail.com>
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie> <CABkgnnWz-GR5T2KA2i=37=gcbbEj=-RKg_ZRcB+06BFiO8VQ+w@mail.gmail.com>
Cc: mohamed.boucadair@orange.com, "ietf@ietf.org" <ietf@ietf.org>, "draft-dolson-plus-middlebox-benefits@tools.ietf.org" <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <1f89f84f-5720-a844-a0b7-581a1a3bf53d@cs.tcd.ie>
Date: Wed, 19 Apr 2017 02:16:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnWz-GR5T2KA2i=37=gcbbEj=-RKg_ZRcB+06BFiO8VQ+w@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MLCp9SSPFTAHDgll70vuDSPAW8GvAr7Pd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W3apuyG8KRc9D6VPD_R7VPycRmM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 01:17:04 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MLCp9SSPFTAHDgll70vuDSPAW8GvAr7Pd
Content-Type: multipart/mixed; boundary="59LHgWdBDOEmP9EB7IHoDEdfBCV3WfoK7";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: mohamed.boucadair@orange.com, "ietf@ietf.org" <ietf@ietf.org>,
 "draft-dolson-plus-middlebox-benefits@tools.ietf.org"
 <draft-dolson-plus-middlebox-benefits@tools.ietf.org>
Message-ID: <1f89f84f-5720-a844-a0b7-581a1a3bf53d@cs.tcd.ie>
Subject: Re: draft-dolson-plus-middlebox-benefits (was RE: Review of
 draft-mm-wg-effect-encrypt-09)
References: <787AE7BB302AE849A7480A190F8B933009E4B818@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
 <11843452-d76d-50e3-c162-155f4d1621e2@cs.tcd.ie>
 <CABkgnnWz-GR5T2KA2i=37=gcbbEj=-RKg_ZRcB+06BFiO8VQ+w@mail.gmail.com>
In-Reply-To: <CABkgnnWz-GR5T2KA2i=37=gcbbEj=-RKg_ZRcB+06BFiO8VQ+w@mail.gmail.com>

--59LHgWdBDOEmP9EB7IHoDEdfBCV3WfoK7
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 19/04/17 01:33, Martin Thomson wrote:
> On 11 April 2017 at 18:51, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>>
>> (*) That is the argument for draft-mm-effect-encrypt, for which I
>> do support publication (apparently in disagreement with Martin in
>> that case:-)
>=20
>=20
> Taking a break from email is so refreshing...
>=20
> I would very much like to see a document like this that captures these
> use cases and practices.  The problem I have with it are simple: it
> isn't particularly coherent,=20

Hmm. Two things to consider there: 1) the editors have AIUI tried
hard to collate offered text from various folks and that's fairly
likely to end up less coherent, so we shouldn't insist on a level
of perfection here that we'd not ask from something with which we
might more "natively" agree.

But possibly more interestingly: 2) I think it's arguable that
coherently arranging the set of descriptions here is hard, and I
think that may tell us something about the underlying logic of
the situation.

For me the lesson of that innate incoherence is that the set of what
are now shown (in 20:20 hindsight) to be somewhat "lazy" practices
are being demonstrated as problematic via the re-assertion of the
e2e argument using confidentiality mechanisms, even where those latter
confidentiality mechanisms aren't in fact deployed "fully" e2e. And
that argument is quite close to the ossification one that transport
folks seem to like. The incoherence of the argument as to why
confidentiality is "problematic" seems to me more a fundamental
weakness in that argument against confidentiality rather than a
failure of exposition in this particular draft.

> and it makes statements that I disagree
> with.  Those statements are particularly bad because they are also
> unnecessary=20

I do agree that the draft ought not be recommending things or to
be saying that such-and-such a practice is "necessary." But I did
think we'd gotten rid of those. Mopping up remaining statements of
that sort would be good, I agree. There were a lot of them in the
contributed text that the editors already excised. (In saying that
I did not go through your detailed review checking stuff - now that
I've escaped the IESG I'm fine that someone else does that:-) And
of course, the fact that you or I only "disagree" isn't really a
good criticism, we need an argument that those statements aren't
well grounded or similar, but I guess that's what you meant.

Cheers,
S.

> (see Brian Carpenter's comments about facts).
>=20


--59LHgWdBDOEmP9EB7IHoDEdfBCV3WfoK7--

--MLCp9SSPFTAHDgll70vuDSPAW8GvAr7Pd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBCAAGBQJY9rqJAAoJEC88hzaAX42ikVIIAIyKspkpq8Ww3pK29CZZoOL8
zB/kmS5wzD0/h5z/MTvK5vYCMdXLlVTl5N2FD0wxz2wARnOL8MWKY5sHWI30qqWx
ccR+1ItvgE6R9lHC6phwdjfp2gTc1TGCeBooS6EE4KlBEKzX/1QvHfPVgiNNwDDr
Egdc3z49zwER9EhBlgIFvXe4xnDHtTmKC1dMMghlJUyLAQJpX7qlnlI5Ufico1GM
VNsjaswQg4WnD5w8Qz/OunJdfHFJBxOzaAPhvhCNMvChneG4HEbyfYPwSv38P2SU
dZqoiboo83OQD08Cmh9K9fei3j9I4kacuwTj0ufULKCzos+Tf+45e3M4QOahfks=
=vYxK
-----END PGP SIGNATURE-----

--MLCp9SSPFTAHDgll70vuDSPAW8GvAr7Pd--


From nobody Tue Apr 18 22:18:35 2017
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA04B126C83 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 22:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 0RfFJcMAN3FV for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 22:18:32 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BF49120724 for <ietf@ietf.org>; Tue, 18 Apr 2017 22:18:32 -0700 (PDT)
Received: from [192.168.55.213] (unknown [31.15.50.66]) by mail.frobbit.se (Postfix) with ESMTPSA id 35E4721D98; Wed, 19 Apr 2017 07:18:30 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Toerless Eckert" <tte@cs.fau.de>
Cc: "Nico Williams" <nico@cryptonector.com>, "Phillip Hallam-Baker" <phill@hallambaker.com>, "IETF Discussion Mailing List" <ietf@ietf.org>, "Paul Eggert" <eggert@cs.ucla.edu>
Subject: Re: Predictable Internet Time
Date: Wed, 19 Apr 2017 07:18:29 +0200
Message-ID: <E030FF20-4EA4-4475-9304-B6F7ADA0B8C2@frobbit.se>
In-Reply-To: <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
References: <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_2CD5272D-254C-4CD3-81A3-52CF5DD099DD_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6082)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p5eeSwN1wyzOEdX8IDZBdRP4118>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 05:18:34 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_2CD5272D-254C-4CD3-81A3-52CF5DD099DD_=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On 19 Apr 2017, at 1:21, Toerless Eckert wrote:

> Nice!
>
> Why not start to tackle the problem pragmatically before asking for sta=
ndards when its clearly a political issue.
>
> a) RFC describing the problems developers and system deployments can fa=
ce  because of leap seconds.
> b) And best current practices to get around those issues. Eg: Expect cl=
ock  smear on Jan 1 =3D=3D reduced accuracy of ~1. Unless OS or other tru=
sted  info source gives explicit indication: NO leap, no smear.
> c) And finally a description of the worst open issues when b) is applie=
d.
>    Anything worse than labels on products "reduced functionality on Jan=
 1   after a leap second" ?

I want as potential fixes which I think are doable:

- an updated POSIX definition where the variable which holds the number o=
f seconds since the epoch when converting back and forth to date actually=
 will hold the number of seconds since the epoch.

- a slot in the NTP protocol not used today include the number of leap se=
conds so people get to know that.

FWIW I am a person that is against smear. I think a clock must be able to=
 give the correct time and that timestamps should be correct. Either in s=
econds (and fractions of seconds) since the epoch or in correct date and =
time UTC. Both are increasing all the time. And because of that smear sho=
uld not have to happen.

That said, I am not against a BCP explaining the issues due to for exampl=
e the broken POSIX specification (which makes it hard to "do the right th=
ing" in software).

   Patrik

--=_MailMate_2CD5272D-254C-4CD3-81A3-52CF5DD099DD_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlj28yUACgkQrMabGguI183CbwCfX0H7lsAon4l5DlK/42RgMXXL
71sAn13CHnNu533Tgm94/HNrexjfyutm
=YBAE
-----END PGP SIGNATURE-----

--=_MailMate_2CD5272D-254C-4CD3-81A3-52CF5DD099DD_=--


From nobody Tue Apr 18 22:26:30 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED46128BB7 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 22:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJbQgmFTD2HY for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 22:26:24 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::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 B1446120724 for <ietf@ietf.org>; Tue, 18 Apr 2017 22:26:23 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id t144so6398022lff.1 for <ietf@ietf.org>; Tue, 18 Apr 2017 22:26:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cwYQmx7ZUQyZcduUEYJW3Td2nLHPoIs4C+/HdXgfm0o=; b=YNj+rBo0+UcLOh+FyIZhRRFnSoLqIFJQwYYhoUf8HbonfKPkt0ovsiVIS4v4DUpT3k tuw6Z8oZA6SmSQtNgxgL/JQ/qAqMtZDQSvZmmJhxCt7Ue4cVJgxT+yLGTiSvdRGrxeo5 ypnZxFQtNpYPNN1IANrnWAyFHP9xMkt7CSQ0XypX8hgs5VgJr/dhkN4hfgjNldI7vJLU lFFHhJJMoQdg+VvEa//CzKkW0zooP2QiDFrqj1n+9cku+l0M6modi1uahj+ptSxygh7o Qr26ZDzftS+OfAznI3m4SKy9heDXJm8RFqii8DXRdDSI+Jl99VLNaE9vOPdRN6c5jBEN FWHw==
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=cwYQmx7ZUQyZcduUEYJW3Td2nLHPoIs4C+/HdXgfm0o=; b=p0VVCRg66nLlZ4Jaa3hnxhu+g6tgnGp+JACbq5NZN3SpPgZmBtznJ7kO7kHUWYfvBQ YIJ7hnII8XHwmr+M0uvNsGCEvOqG+VfPCUlQqKppTkz5B37djJFw3YLLY2c5AbKNkYNe zZa+33cP1XqPTNwxwPrDXK64lexz1xMC3BquLyY/EB1OJ1PtkMj8YG7tDILLKkaOcABT EaJ2yJY5kQC1m3trXTWpPPA6Io7BtupgvPzzIfe+07WD73B9o/HUwRFRfw1oQNCIwh67 /2hWQ9aqqVYgu2Xs3D7cv4Wtlq8RiVPScj2JXSODl53BymwbWRLwsw7O1/74/6SHGjR6 YM4g==
X-Gm-Message-State: AN3rC/7+0EfjX+si2OAR304Uz0uxeRXEKJosuPIHF5zdyiRleIEPjY2P 1Fkd5ikW8j5o7aJXSo2Wq6tqardvmdqgvXA=
X-Received: by 10.25.160.147 with SMTP id j141mr279783lfe.19.1492579581152; Tue, 18 Apr 2017 22:26:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.5.132 with HTTP; Tue, 18 Apr 2017 22:26:20 -0700 (PDT)
In-Reply-To: <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 19 Apr 2017 15:26:20 +1000
Message-ID: <CABkgnnWia41swpiMDahqjRGHShJ3iMXm7xKuroccK3Uec-kHKA@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kUPT8eJwdY2m_PmnShByuUMlkcg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 05:26:29 -0000

Hi Kathleen, (Al,)

First, I think that my comments have been misinterpreted - albeit
understandably - as meaning that I am opposed to the existence of this
document.  That's not the case, I believe that there is valuable
content here and I would like to see this published.  As observed
separately, writing RFC 3234 was difficult, but ultimately valuable.

I think that there are some structural issues and some unnecessary
making-of-statements.  The former needs some fairly major editing
work; the latter: I'd advocate for excision.  I believe that your
assertion is that the latter have been excised; I found several places
where that is clearly not the case.  I'll try to highlight those I
find, but I can't afford the time to do another full review just yet.

It would be a mistake to simply say that because someone requested
publication that this document is ready to publish.  The main cost of
taking another pass at this is the not-inconsiderable time and effort
that requires.  So far the main argument against doing that is that it
is hard, and I can't really disagree with that.  I happen to think
that the extra effort is more likely to produce a more valuable
product.

I've tried to trim this mail; it's long.  I noted quite a few issues
that you didn't address in -11 or respond to in the process, but I'm
just cutting them for the sanity of all involved.

On 11 April 2017 at 13:54, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:
>> Perhaps you have additional language suggestions for context setting?

I have a suggestion, below.

>>> Aside from weakening its utility and/or arguments, the lack of focus will
>>> allow
>>> this document to be abused in various ways.  For instance, it might imply
>>> IETF
>>> endorsement of the practices described in the document.  Given that the
>>> IETF has
>>> published positions that in some cases reject these practices, this
>>> document
>>> needs to be very precise with its claims.  In its current form, it is not
>>> nearly
>>> careful enough.
>
> This paragraph is all speculation about an unfortunate future.
> We could speculate that the operator, security and app communities
> come together to work out solutions after reading this doc,
> which is part of our intent.

I don't think that argument is so easily dismissed.  When we create a
statement, we have to consider how it might be read from multiple
perspectives.  In this case, it's not that much of a stretch to
believe that someone might read some of the statements here as license
to try to undermine TLS (for example, based on a reading of the text
from Section 2.4).

>>> If this document is going to be published as an RFC, then it needs to be
>>> very
>>> clear about its intent and its position - or lack thereof - toward these
>>> practices.  It might be possible to say that these practices were employed
>>> in
>>> networks in the past and that encryption is reducing the viability of
>>> those
>>> practices.  A value-neutral statement like that might be acceptable as
>>> long as
>>> it were framed carefully.
>
> The document conveys that message everywhere. The words contributed were
> changed in many places to remove any implication that the current practices
> are "requirements" or even "needs".

Actually, I don't question the fact that people believe these to be
requirements.  But I see a lot of cases where it's less clear, for
example in Section 2.3.1 (I'm moving to -11 now):

   This [referring to traffic analysis] technique may be
   used with clear text or encrypted sessions.

Thinking about an adversarial reading of this, is that a permissive "may"?

> The abstract and introduction contain value neutral statements like
> what you are suggesting already.  We actually say the practices may be
> eliminated, going further than your request as that may be the case.
>
> The only change I could see in the abstract would be the following:
>
>    Increased use of encryption impacts operations for security and
>    network management causing a shift in how these functions are
>    performed.  In some cases, new methods to both monitor and protect
>    data will evolve.  In other cases, the ability to monitor and
>    troubleshoot could be eliminated.  This draft includes a collection
>    of current security and network management functions that may be
>    impacted by the shift to increased use of encryption and encryption
> that is designed prevent interception.  This draft
>    does not attempt to solve these problems, but rather document the
>    current state to assist in the development of alternate options to
>    achieve the intended purpose of the documented practices when possible.
>
> Do you have additional suggestions?  Or is the phrasing read
> differently than we intended by stating functions may be eliminated?
> We thought that was very clear to your points.

The abstract could be better I think.  How about?

   Pervasive monitoring attacks on the privacy of Internet users is of
serious concern to both the user and operator community.  RFC 7258
established the need to protect user privacy when developing IETF
specifications.  This encourages reducing the information that is made
available to passive observers, which affects some security and
network management practices.  This document describes those practices
and examines the effect of increased use of encryption on those
practices.

On a second read, I think that the bulk of the problem is with 1.1,
section 1 is largely OK.  The second-to-last paragraph of Section 1.1
is critical, but I actually think that the remainder of that section
is more of a liability than an asset.  The discussion of OS is weak,
creating good citations for the statistics is hard, and the discussion
of non-web cases isn't adding much value.  You could simply take it as
read that there will be increased encryption and this document would
work well.  Even if you didn't want to assume that encryption is
increasing in volume, you could have a fine document that explored the
management impacts of encrypted sessions.

Also, it would help if there was a clearer statement regarding lack of
endorsement.  If you are going to say "lawful intercept exists" - a
true statement, almost a truism - it's prudent to also say that this
isn't an endorsement of those practices.  Explicitly.

> The intent of this document is to help operators as these changes
> continue.  It is to make sure we are not ignoring the impact of the
> changes the IETF has with our decision (which are supported in this
> document).  This document is intended to assist operators.  By
> explaining the functions being performed, some have already been
> provided alternate methods to achieve their goals.  We have also
> received quite a bit of positive feedback from operators - that this
> document helped them come back to the discussion and to approach a
> world with more encryption or sessions that can't be intercepted (TLS
> 1.3, TCPinc, QUIC, etc.).

Yep, and that's a valuable goal.  It would be nice to have a document
that allowed someone with a need (or requirement) to be redirected to
an architecturally sound solution.  The challenge is that these
problems don't all have simple solutions.  In its current form, I
don't see this draft as providing that service well because the
goals/use cases aren't particularly well-organized.  Also, it's
probably best to avoid developing solutions as part of this.  A simple
catalogue of needs and practices works.

> Can you give specific sections where it sounds like we are weakening
> RFC 7258 so we can change that specific wording?

See above.

> Version 8 to 9 had some edits to remove statements with used terms
> like 'need'.  We may have missed a couple, we'll check the ones you
> pointed out.  There are also numerous statements that are explicitly
> in support of RFC7258.  These are in the abstract, introduction,
> summary and sprinkled throughout the document.

I don't think that the superficial change really worked.  See above
regarding "may".

> Apparently, RFC 7754 goes further than our scope. We are not describing:
> "... the different practices that might be employed to achieve that goal."

Agreed.  I am more interested in the structure of that document.  How
it breaks down the problem carefully and explores the various options.
You don't have to offer solutions here, but the treatment could be
more methodical (like in RFC 7754).

>>> The Real Purpose of this Document
>>>
>>> I think that this is the real question that this document wants to ask is:
>>>
>>>    In a world where we are forced to defend against pervasive monitoring
>>> by
>>>    motivated and malicious actors, can we find a role for less pervasive
>>>    monitoring by well-intentioned entities?
>
> The document aims to help operators by giving them a chance to discuss
> the impact.  It opens the
> door to conversation so they can find new ways to achieve the same
> goals (better performance for customers for instance or monitoring
> services that have been requested - web content, DLP), which may mean
> endpoint solutions are needed or filtering limited to hostnames for
> now until other mechanisms are developed (likely at the application
> layer).
>
> For enterprises, application and host level solutions are
> fine as many organizations have employees sign away their rights to
> privacy.

I understand that's true.  Though it's also a little sad, I'm speaking
from a position of privilege, so I won't make too much of an issue of
it.  What interests me here is the operational challenges that arise
from this.  The need to modify multiple applications for instance.

> QUESTION: Would it help to add some text like the first paragraph into
> the introduction?  - This document aims to...

If that is actually the aim of the document, sure.  It seemed less
clear to me what the intent was from reading it.


>>> In other words, the right question might be:
>>>
>>>    For each of these practices that we see today, are the use cases that
>>>    motivate them legitimate and how might be implement alternative
>>> techniques
>>>    that properly respect privacy and security?
>>>
>
> Yes, this is the point of the document and it's stated in several places.

I don't think that this is exactly the question you ask, it's a
broader one that you are trying to attack.  You are laying the
groundwork for asking that question: which is, what are those
practices and why do they exist?  The question of legitimacy isn't one
that you want to tackle here (not enough space, too hard, etc...) and
designing solutions is best left to individual protocol designs.

>>> Two- and Three- Party Interactions
>>>
>>> A great many sections of the document are unclear about the relationships
>>> between different actors.  It seems like many of the activities describe,
>>> which
>>> are presented here as being beneficial, are performed by a third party
>>> without
>>> the consent or involvement of the two communicating peers.  After all,
>>> those are
>>> the cases where encryption most often interferes.
>
> As the draft says, some of the methods will be eliminated.

It's very easy to lose track of that 40 pages in when the text that
you are reading says something else.

>>> The assertion that some benefit is accrued to communicating peers as a
>>> result of
>>> these actions is the constant subject of the text.  I observe that in most
>>> of
>>> the cases listed in this document, the benefit is accrued primarily to the
>>> third
>>> party.
>
> Operators by their nature have different privacy concerns than their end
> users. Operators by their nature want to accrue benefits. This document
> doesn't change the balance; instead, it tells them how to deal with privacy
> that has already been applied.  While we agree with your statement and think
> it's important to build privacy and privacy options into IETF protocols,
> operators often don't care, despite the many RFCs we have published
> telling them that they should care. We still need to engage them so we can
> have this discussion.
>
> The "third party" is likely the only one receiving a trouble call,
> and there is benefit for all parties when the trouble is cleared.

I think that you missed my point here.  The point is that the document
declares various outcomes as virtuous, rather than simply describing
the practice.

Section 2.3.2.1:

   The features and efficiency of some Internet services can be
   augmented through analysis of user flows and the applications they
   provide.

That's an statement that ascribes a virtue to a particular practice
without qualification.  The ensuing text only doubles down on that.

> The above is stylistic in nature.  We've already made changes to the
> format to address specific comments in IESG review. A complete
> re-write is not appropriate at this point in the draft lifecycle.
> That's not the point of IESG review.

See above.

>>> The immediate focus on opportunistic security is highly misleading,
>>> especially
>>> in the web case.  The amount of opportunistically secured web traffic is
>>> miniscule by global standards.  Since Firefox is the only browser to
>>> support OS
>>> for the web, so adjust the following by market share:
>>> <https://mzl.la/2oc46ch>.
>
> You'll need to cite text that is leading you to this conclusion as I
> don't read it as being specific to OS, rather that OS is explained so
> operators understand it in the mix of encryption options.

The first two paragraphs of Section 1.1 talk about OS.  In the context
of this document OS is maybe relevant for a few reasons:

1. it can be removed trivially (see the STARTTLS attack by operators)
2. it can be deployed more easily (debatable)
3. it is encryption

Of these, the last is the only thing that is relevant.  For the
reasons I cite above, I would restrict discussion of it to those
sections that talk about stripping opportunistic security (striptls,
the STARTTLS attack).

>> For the Mozilla statistics, Richard Barnes had reviewed the text after
>> providing the statistic as he wanted to make sure it was stated
>> clearly raising the same concerns you do about statistics.  Do you
>> have further text suggestions to clarify this statistic?

Well, my first suggestion is removal.  Failing that, create citations
for the statistics.  If you can't - the Dell EMC stats, for example -
then at least describe what they mean. I don't know if 78% applies to
connections, packets, or requests (probably not requests).

>>> There's an implicit argument here that runs counter to established IETF
>>> consensus.
>>>
>>>    Some methods used by service providers are impacted by the use of
>>> encryption
>>>    where middle boxes were in use to perform functions that range from
>>> load
>>>    balancing techniques to monitoring for attacks or enabling "lawful
>>>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>>>
>>> This fails to remain neutral.
>
> The functions are impacted, so how would you suggest we word this
> text?  It doesn't endorse the functions, just says they are impacted.
> We are open to suggested text.  Similar to how we describe 'attacks'
> by operators to break encryption or use RSA private keys.  We do have
> text in both directions on this and your review is complimentary of
> the ones that fit your dialog, but are also not value neutral.  Mind
> you, I am constantly reviewing RFCs and making sure TLS best practices
> are considered and questioning the use of deprecated crypto or not-yet
> but should be deprecated crypto.

I think that you should include a section on intercept.  It happens;
encryption largely prevents it, though OS doesn't.

> But this is true and we've seen operators do things like prevent
> STARTTLS.  This isn't a good thing and we need to ack that this has
> happened.  We need to help operators figure out how they help users in
> new ways and understand that some of the functions they perform
> currently (TLS 1.2) won't work in the future.
>
> This text got re-worded during AD review, I believe.  The intent is to
> say that this is not good - the practices are called out as
> undesirable.  How would you suggest it be re-phrased and we can check
> back with Stephen to see if he agrees.

I would prefer that the document doesn't mention that at all.  Talk
about disabling OS as a practice that happens.

>>> I
>>> certainly disagree with the IETF making any such statement.  It says that
>>> we are
>>> collectively willing to bow in response to (anticipated) threats of
>>> violence.
>
> Prior to AD review, there was a reference in the text to the practices
> being bad and stating that regulators and the media helped to correct
> this behavior.  The problem here may be the evolution of the
> text and lack of reference now since we couldn't find a stable
> reference.  Do you have a wording suggestion?

See above.  That is, acknowledge that some methods exist for
"breaking" encryption, that those are largely limited to striptls and
its ilk, though attackers with significant resources might be able to
perform other sorts of attacks (cite the attacks on TLS doc here).

> While we read this as  more of a substantive remark, the text on
> load balancers and QUIC were added per Mirja's IESG review.  We would
> need to check with her about making any changes here.  They were
> specific additions that were requested.

I think that Mirja responded here, I'll follow-up there.

> Further, it is only IETF QUIC that is in active development.
> Google QUIC (referred to as GQUIC in IETF discussions) is a more
> stable experiment now.

It's existence seems assured, but not its form.  Google are tracking
the IETF work.

>>> Section 2.2
>>>
>>> I think that this sums the situation up reasonably well.  It fails the
>>> value-neutral test in a few ways though.  As I understand the situation,
>>> surveying operates at many levels.  For accurate planning, models of
>>> endpoint
>>> behaviour are used to determine things like whether loss or congestion is
>>> affecting throughput.  Really good models require knowledge of what users
>>> are
>>> attempting to do and the applications they are using (as mentioned, things
>>> like
>>> browser version matter in these models).  For instance, it isn't enough to
>>> understand that the user is trying to receive 720p video, you also have to
>>> know
>>> that a 4k stream for the same content is available.
>
> Sure, that's why we broke the draft down by operator type.  Some
> functions are shifting and the responsibilities for operators will
> shift with these changes.

Here's a structural suggestion then:

* Use Cases
** Common Use Cases - those for more than one type of network operator
(e.g., troubleshooting)
** Enterprise Use Cases - those unique to enterprise (e.g., DLP)
** Network Operator Use Cases - e.g., capacity modelling
** Hosted Service Use Cases
* Practices
** DPI
** Traffic Analysis
** Removing Encryption
** Repacketization
** TCP Termination
** ...

Description of use cases can list practices used in support of them,
or the practices can list the use cases they support, or both.


>>> Section 2.3.2.2
>>>
>>> Again, it's strange to see differential treatment under DPI.  I was fairly
>>> sure
>>> that fingerprinting was used here as well.
>>>
>>> Section 2.4
>>>
>>> This section doesn't even attempt to recognize that applications are much
>>> better
>>> now at scaling content to suit the device on which that content is
>>> intended to
>>> be consumed.  It should.
>
> The reason for that is that there has been a useful dialog between application
> designers and network providers over time, beginning with app designers
> saying "what do you mean the network has errors and delay? this works
> fine in my lab...".  The contributors viewed that as well understood
> and far back
> in time, so not necessary to mention.
>
> If you think there should be text to this point, please suggest some.

"This has an effect on applications in addition to network operations.
By removing the ability of an intermediary to compress content, the
responsibility for adapting to network conditions moves to the
endpoints.  Applications that are able to compress content, or reduce
bandwidth use to suit network conditions will gain better
performance."


>>> This section should not represent compression as an unmitigated good.  I'm
>>> told
>>> that significant damage can be done to video streams by "well-intentioned"
>>> compression middleboxes.
>
> Please suggest text.

"Compression employed by middleboxes can have an effect on
performance.  In addition to latency costs, compression can require
additional computational resources.  Use of lossy compress degrades
the quality of content."

>>> Yet again I see a call back to the implicit threat of violence in "they
>>> will
>>> adopt undesirable security practices".  Statements in that form have no
>>> place in
>>> IETF RFCs.
>
> This was edited text per review and agreed upon (I think in the AD
> review).  Suggest alternate
> text and we'll go back to the other person.

Ahh, I hate putting you in that position.  I would prefer if this be removed.

>>> Section 2.6.2
>>>
>>> I can't parse this statement:
>>>
>>>    Approved access to a network is a prerequisite to requests for Internet
>>>    traffic - hence network access, including any authentication and
>>>    authorization, is not impacted by encryption.
>>>
>>> And then we get into zero rating, which is a hot-button topic.  No
>>> acknowledgment given to the sensitivities on the subject, or even a
>>> superficial
>>> exploration of the technical options that are available.
>
> Please suggest text.  This was updated in IESG review.

I see a reference to Section 7 here, but no text on zero rating in that section.

Zero rating is a use case in its own right.  I would make a new
section, or simply repurpose Section 2.6.2 for that (remove paragraph
1).

Section 2.6.2. Zero Rating and Preferential Treatment

   Some network operators sell tariffs that allow access to certain
content without cost to users, a practice known as 'zero rating'.

   More generally, users might be charged differently based on the
content they are viewing.  Or, packets related to the access of
certain content might be given different priority.  Identification of
content is critical to providing this differentiation, because web
content is often distributed across multiple servers.

   Use of encryption hides details about content, preventing the use
of those specifics from being used in providing preferential
treatment.

This expands the scope of the section considerably, but I think that
it's what you want to say.  I have restrained myself in not making any
statement about the virtue or otherwise of these practices.  I think
that this is a bad trend, but we don't need to say that in an RFC
(unless we create one with that purpose, that is).

>>> Section 2.7
>>>
>>> This is one of the areas that is most legitimately affected by increased
>>> adoption of encryption.  I have no doubt that having detailed information
>>> about
>>> the application and its use makes the process of troubleshooting easier.
>>>
>>> This is the first mention in the document of network-based optimization.
>>> Was
>>> the section describing that cut from an earlier draft?
>>>
>>> The use of websockets as a primary example is an odd one.  It's just not
>>> that
>>> common.  For reference, we see >20% failure rates on encrypted websockets
>>> and
>>>>50% failures in the clear; no one in their right mind would rely on
>>>> websockets.
>>> If the point is that HTTP is carrying more traffic (see
>>> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
>>> just that
>>> would be more effective.
>
> "in their right mind" . That isn't helpful.  Operators submitted text
> to explain what they are doing and how it's impacted.  How about
> proposing text to help in that vein.

"The widespread use of encrypted HTTP means that TCP port 443 is being
used for a large variety of use cases with sometimes very different
performance requirements.  Some uses are latency-sensitive, others
need to send lots of bytes.  In some cases, mixed uses appear on the
same connection; which is possible with both WebSockets [RFC6455] and
HTTP/2 multiplexing [RFC7540].  A network operator is unable to
provide differential treatment using the information that is available
to them."

Now that I look at this, this is a more general and useful statement.
Hiding it in the bottom of a section about something else doesn't make
a lot of sense.  It's also not general enough to surface in an
introduction, so I recognize the difficulty in finding it a home.

>>> Section 3.3
>>>
>>> There's certainly a lot of detail here, but I had a really hard time
>>> extracting
>>> value from this section.  I can't see how data storage is fundamentally
>>> different to the general case of an application provider.
>
> They figured out how to increase encryption and manage their hosted
> environments.  There were adjustments made and they've been
> successful.

This short explanation is much easier to digest.  Is there any way
that might be said up front? Though even with that, I would still find
this section very difficult to read.

>>> Section 4.1.2
>>>
>>> I'm confused about the purpose of this section.  This seems to be talking
>>> about
>>> the sort of network-based methodologies an application provider might
>>> employ to
>>> ensure that their application is working as intended.  Why would the
>>> application
>>> provider not have access to detailed logging and usage metrics?
>
> The problem cited to us is that logging is sorely lacking.  This needs
> to be pointed out and fixed as it is too much for the operator to deal
> with given the large number of applications running in their
> environments.

If that is indeed an issue (I've heard the same asserted, it's
probably true), then it needs to be said.

>>> Section 4.2
>>>
>>> If the inclusion of a reference to RFC 7457 is to support a claim that TLS
>>> is
>>> attacked, that's sailing far too close to an endorsement of attacks than I
>>> am
>>> comfortable with.  However, I don't believe that any of the listed attacks
>>> remain viable in modern applications.  What is most often the case is that
>>> a
>>> trust anchor is installed on enterprise users' machines and new
>>> certificates are
>>> minted as needed.  In other words, the host that is accessing the HTTPS
>>> site is
>>> owned by the enterprise and modified so that it can comply with its
>>> policies.
>>>
>>> When you recommend attack like this (to be clear, I would oppose
>>> publication of
>>> text that does this), you need to acknowledge the downsides.  For example,
>>> MitM
>>> devices routinely break connections, they hide the true security status of
>>> communications from endpoints and users, they frequently implement weaker
>>> versions of protocols, they often don't include the same degree of rigor
>>> in
>>> things like certificate validation, and probably many more things that I
>>> can't
>>> casually list off the cuff.
>
> Please suggest text.

Well, to preface this, I don't think that this is the right section to
put text like this.  It's more appropriate in a section that talks
about the specific techniques (Section 4.2 is another grab bag of
practices duplicating text from other sections).

I think that it is entirely appropriate to say:

```
Encryption can be disadvantageous to the goals of the operator of a
middlebox.  Removal of encryption without the consent of endpoints is
an attack.  Attackers can and have removed attempts by endpoints to
use opportunistic security (see [SSLSTRIP --
https://www.blackhat.com/presentations/bh-dc-09/Marlinspike/BlackHat-DC-09-Marlinspike-Defeating-SSL.pdf],
[STARTTLS -- Section 5.1 of DOI.10.1145/2815675.2815695]).  More
resourceful attackers might use attacks or weaknesses in deployed
protocols (see [RFC7457]) or flaws in implementations to remove or
attack uses of encryption.
```

That's a stronger statement than I think you are looking to make
though.  It doesn't invalidate the cases where endpoints are owned and
trust anchors are installed.  I would put that down in a different
section.

```One method for intermediating encrypted sessions is to install a
trust anchor on an endpoint and then use the associated keys to create
authentication credentials that will be accepted by the endpoint.  In
this way, a middlebox can terminate a session in a way that the
endpoint will accept as legitimate, thereby impersonating the intended
peer.

This technique rarely works for mutually authenticated communications,
because the middlebox is usually unable to exert control over both
intended endpoints in a way that would allow it to impersonate both
peers to each other.  It also causes the modified endpoint to become
entirely reliant on the methods the middlebox uses for correctly
authenticating the intended peer.

For example, a web client typically implements authentication checks
that exceed those listed in RFC 5280 [cite]. This might include key
pinning [RFC7469], OCSP stapling
[https://www.iab.org/documents/correspondence-reports-documents/2017-2/iab-statement-on-ocsp-stapling/],
and other checks. A middlebox that impersonates a web server that does
not perform the same checks could be vulnerable to the attacks that
these additional checks are intended to protect against.
Impersonation of a web server also hides the true status of the
connection from the web client.
```

>>> Section 6.1
...
> Please suggest text if this should be included.

Here's a rewrite...

```
A TLS client that initiates a connection to a server can provide a
server_name extension (server name indication, or SNI) [RFC6066] which
indicates the name of the server to which it is attempting to connect.
SNI allows servers to select between multiple certificates when
handling a TLS handshake.  This enables the use of multiple domain
names at the same IP address, also known as virtual hosting.

Although SNI is an optional extension, it is today supported by all
modern browsers, web servers and developer libraries.  Akamai [Nygren]
report that many of their customers see client TLS SNI usage over 99%.
HTTP/2 [RFC7540] mandates the use of SNI.

When present, the server_name extension that is included in the TLS
handshake is not encrypted.  This allows a passive observer to
identify the domain name to which a connection SNI is being made.
Other information about the application, such as the URL of an HTTP
request or the type of content being requested, is not visible, only
the domain name of the server.

Relying on SNI to identify a host has several limitations.  It is not
present in a small number of cases where clients do not support the
feature, or where protocols that don't mandate or rely on its use.  In
addition, HTTP/2 connection coalescing (see Section 9.1.1 of
[RFC7540]) can mean that a connection originally established for one
name is used for requests to other names.
```

I've dropped Alt-Svc mentions (they aren't relevant in this context -
even with HTTP OS, SNI is still shown in the clear).  I tried to keep
the text about the type of content

>>> Section 6.2
>>>
>>> ALPN will be encrypted in TLS 1.3.
>
> Noted.  Thanks.

Hmm, I should have been clearer, the server's choice of application
protocol will be encrypted.  The client's set of options will not be.

>>> Section 6.3
>>>
>>> This reads as a invitation to perform traffic analysis (a statement that I
>>> oppose).  Note that we have added padding to most recent protocols (HTTP/2
>>> and
>>> TLS 1.3 in particular) to give endpoints the ability to resist this sort
>>> of
>>> attack.
>>>
>>> Note that block ciphers can add ~240 octets of discretionary padding per
>>> record.
>>> That can be pretty effective if you are careful.
>
> I believe this text was added through the IESG review.  I don't see
> the problem with the text you are citing, so could you suggest
> alternate text?

```
Information about the content of encrypted communications is often
available through traffic analysis.  For instance, the size and timing
of packets can reveal considerable information about the contents of
data [NETFLIX][CLINIC].

Applications can implement traffic analysis strategies, usually by
padding content to obscure its true length.  This can be achieved in a
limited fashion in block ciphers in TLS, and various features of other
protocols can be exploited to add padding.  Explicit support for
padding is included in HTTP/2, TLS 1.3, and some other protocols.

Use of multiplexed protocols can confound traffic analysis by
combining data from multiple discrete events.  However, multiplexed
protocols depend on flow control, which can be exploited to reveal
information (see [HEIST]).
```

Citations for the above (sorry, rough):

  NETFLIX=DOI.10.1145/3029806.3029821
  CLINIC:
    title: "I Know Why You Went to the Clinic: Risks and Realization
of HTTPS Traffic Analysis"
    author:
      - ins: B. Miller
      - ins: L. Huang
      - ins: A. D. Joseph
      - ins: J. D. Tygar
    date: 2014-03-03
    target: "https://arxiv.org/abs/1403.0297"
  HEIST: https://www.blackhat.com/docs/us-16/materials/us-16-VanGoethem-HEIST-HTTP-Encrypted-Information-Can-Be-Stolen-Through-TCP-Windows-wp.pdf


>>> Section 7
>>>
>>> This section is duplicative of much of the rest of the document.  I
>>> realize that
>>> editing is hard, but see my earlier comments about structure.
>
> This text was the appendix, but moved to section 7 per IESG review and
> discuss.  It was the mobile operator view.

It's valuable information, sure, but hard to use.  I can see why the
IESG thought that it needed to be in the body, as there are quite a
few new use cases.

>>> Section 8
>>>
>>> I generally agree with the first statement here, but after having read the
>>> document, I could take away some very different views on what the
>>> "problems at
>>> hand" actually are.  I suspect that different people will have very
>>> different
>>> takeaways.
>>>
>>> The conclusion section of a document is not the right place to start
>>> introducing
>>> new information, particularly information relevant to RFC 2804.
>
> Should we move this to the introduction perhaps to help with context setting?

The bit about surveillance programs and lawful intercept really need
to be in the relevant sections of the body (that was the "new
information" I referred to).  I agree that it would be good to promote
the first statement to the introductory material.

>>> Not sure where this is going:
>>>
>>>    Terrorists and criminals have been using encryption for many years.
>>>
>>> Because it's disconnected from the remainder of the paragraph.  If you are
>>> going
>>> to invoke the T-word, you had better have a strong argument to make.  On
>>> the
>>> final sentence of that paragraph, the subject ("This") is unclear.
>>>
>
> Sure, the point was that their use of encryption is not a
> justification argue any of the improvements to crypto for the general
> population.  Incident handlers know full well that encryption has been
> in place for a long time by these users.  Essentially, it's not an argument that
> hold muster.

Yeah, as before, when it comes to discussion of lawful intercept, I
would prefer to have that in the body of the document.  Preferably
without mentioning why it happens, because that avoids the emotive
topics.


From nobody Wed Apr 19 01:46:59 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C16213157F; Wed, 19 Apr 2017 01:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 jfQ1uRl2DjPz; Wed, 19 Apr 2017 01:46:57 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 DF713131576; Wed, 19 Apr 2017 01:46:56 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id o81so74223789wmb.1; Wed, 19 Apr 2017 01:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Ougxf9uJ25t+oNOaLThwQnfKjE44NoNBJsTUmD9K0i4=; b=bUpgBR07/A2qO3WX3zR+Z1rvZ/ajfcZUeL3Vr5dHQUCS1yc/OmAdcoD+Yi/ljXLOe9 iYSz1f8wxAuujq/pXBM8eZLenaCPzi08RWXHYRohd09oHqOPVgwXcUZrq/Eg7PTeCRC5 Ibr5ZFwvvZbp/k9+eM9CR220zBmhNhwDp0XDzlTIkzZk2d8s/hur4Rt+d/vxx0rJfcyw KYPs+LVyrLaopLXiNFjDNO6xlOtPWe0/MytWFFvr+YP6UySLrdfD8K0tw28Sm0C/Hotb QEUDAmhU7HTnHQ0kVaJ87XfTWJ+o5Ed74nFOIzmzxQdCHtCP6lggpmK9/77oy28iVj/1 iSjg==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ougxf9uJ25t+oNOaLThwQnfKjE44NoNBJsTUmD9K0i4=; b=cOh4MxD/NFa1mrwuzc87qNjP7xvcpMz9u6OUkT74aji1SveD9sxA8NhMG6TRel6mGW wh0CH/X1rD5frnIvLjN8lA1UJfjKc5IiSPD8e6dAR+kd9Bp78k1WhK46cyLnqXCKhWQl wsn/h7ylIiopOquneAhtMOTrAmk4IBdNUKb7ycE3BlJZCD73iNiwXacHLSGJIRFbl1iY 3jI90OpninU4LQIxqjJXf4mzDgkerHFhUef/RsKo03aR+WMONuzmbMkWqTzHyr9Wod60 uXs6DxwjIcbnBUr+mgkbMQiFf7ynD9XNwLpgb2X0zB5oOnnn2ysd7oYtnBxmUe6DFCkK t/XA==
X-Gm-Message-State: AN3rC/5Z7UYN8Akrscu8iuQuP4x/Q85IRjcvromNAfR7B7JV646TKQZE TjbLG+fjJ6zMQFyIHSs=
X-Received: by 10.28.165.13 with SMTP id o13mr1909942wme.139.1492591615207; Wed, 19 Apr 2017 01:46:55 -0700 (PDT)
Received: from [10.66.4.239] ([131.227.23.37]) by smtp.gmail.com with ESMTPSA id e21sm2859828wma.5.2017.04.19.01.46.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 01:46:54 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
To: Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
Date: Wed, 19 Apr 2017 09:46:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U7XKIdMoUDidkbLo_XdCz0bdIjQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:46:58 -0000

On 19/04/2017 00:58, Job Snijders wrote:
>
>> ============
>>
>> 5.  Security Considerations
>>
>>     Operators should note the recommendations in Section 11 of BGP
>>     Operations and Security [RFC7454].
>>
>> SB> You do not address the question of whether there are new
>> SB> considerations, or considerations that are of increased importance?
> It is my understanding that RFC 8092 "BGP Large Communities" are just
> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
> words). Referencing RFC 7454 seems plenteous.
>
> So, what if there are not any additional considerations, If there were,
> they would've been (or are) covered in RFC 8092's security section,
> right?
>
> This is an Internet-Draft targetted for Informational status, I'm not
> sure what you expect here.
I was wondering if there was more scope to make mischief at a distance 
in a less
less obvious way than before.

If everyone is happy that there is no additional risk then I am fine, 
but seems to
me the more knobs you give the mischeif maker to turn the more security 
risks
you have.

>> SB> Is there is text somewhere that discusses the integrity and
>> SB> synchronization of the parameters and any consequences that arise?
> the what now? Can you elaborate on the above?
So you rely on the nodes that receive these community strings to 
interpret them in
a common way. Maybe this is an already solved problem, or an known risk, 
but what
if the dictionaries get out of sync?

>> ===========
>>
>> Minor issues:
>>
>> 2.2.  Action Communities
>>
>>     Action Communities are added as a label to request that a route be
>>     treated in a particular way within an AS.  The operator of the AS
>>     defines a routing policy that adjusts path attributes based on the
>>     community.  For example, the route's propagation characteristics,
>>     the LOCAL_PREF (local preference), the next-hop, or the number of
>>     AS_PATH prepends to be added when it is received or propagated can
>>     be changed.
>>
>> SB> Although these are well known to the target audience, I think you
>> SB> need some references in the above para.
> What reference would you suggest? You feel the section 2.2 text cannot
> stand on its own?
As I said I imagine that all readers will know the definition of 
LOCAL_PREF and
AS_PATH, but normally we give a reference in a documnet like this.

- Stewart


From nobody Wed Apr 19 01:52:17 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61DA131585; Wed, 19 Apr 2017 01:52:15 -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 k91G6eHyPaqD; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (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 6E69213158E; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
Received: by mail-wr0-x243.google.com with SMTP id l44so2264420wrc.2; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=SFAYnSLEx54i0XkbEkVy9DdmlNHF7h2XeHEkNh/A5Nw=; b=vMLw/BTfm9G+enfXJDe+pOEOSyiZeSvtslYVR68V9FiVzKvQ9WsOxnzTPkzPNdfCTl +bRTS9wr42JFuY4oNcz7d/RQwDFs7UsTJDB6EnTXk1biEx6AgjIodvb0A+5ExfeiD9eX L+NdBgR5C66MxeOxfwDje3tblEONa8s1nEVpLmjQ65NUzQCuL/FM6GuUVgH5xnEU4L44 3cKdsSaYB9ogE/p3dCnw+8/nOHVRSCXGYC2eJ9qLiD2JzuHrUqJOTlHLk33zoWPZq+An 0WBDHo2Jy6HzWzH/PO7iTVsKHLf+MRIBKD4ojUTVKPCbdsoNA1Haa3t9ZBx+hoUwC1DG goRg==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=SFAYnSLEx54i0XkbEkVy9DdmlNHF7h2XeHEkNh/A5Nw=; b=kPSC8DOI3Hd6I9us+uR3VvSFcPt69CcfVpMAoD4ea0sUAL9Ysm6+MgFITDVdKet26w YP5iFUTNdI5cPr8WSHrXYC2Bv3He0dfb9Fe/vE54zXPZUYt4P6iNFt2st6erVr/481DW /mNaRiPToYDhABWymzuoMB+3Pjxgmr4nKKKbCpwS2CLexaJM7BCGKSW3cIfqATS6PetO OOJLQu/wc1RQsLRzzMpuNSdQkC2U2GVU/rfyevaaOYO6c+4DUQTY8+5IuXgKqAccJcHu hyRAyjZzXUBx/i977xHFhsXBBOtwUJa+7NU3YYC3I89i149+OJLCYllKLRIKEGMMaWuD AVdw==
X-Gm-Message-State: AN3rC/4PURalyj1gZODNHTrgjxOYAyQwm9S3D8CIpvenoDpOfH56s09C kBt0qr9fa1lYuLZ7rKs=
X-Received: by 10.223.162.152 with SMTP id s24mr1901087wra.27.1492591931635; Wed, 19 Apr 2017 01:52:11 -0700 (PDT)
Received: from [10.66.4.239] ([131.227.23.37]) by smtp.gmail.com with ESMTPSA id w16sm1486809wmd.0.2017.04.19.01.52.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 01:52:11 -0700 (PDT)
Subject: Re: [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
To: Randy Bush <randy@psg.com>, Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com>
Cc: gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
Date: Wed, 19 Apr 2017 09:52:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m2vaq1p5oi.wl-randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mDnU6hWw8NNFs34bvYakMzUpw1I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:52:16 -0000

On 19/04/2017 02:06, Randy Bush wrote:
>>> 5.  Security Considerations
>>>
>>>     Operators should note the recommendations in Section 11 of BGP
>>>     Operations and Security [RFC7454].
>>>
>>> SB> You do not address the question of whether there are new
>>> SB> considerations, or considerations that are of increased importance?
>> It is my understanding that RFC 8092 "BGP Large Communities" are just
>> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
>> words). Referencing RFC 7454 seems plenteous.
>>
>> So, what if there are not any additional considerations, If there were,
>> they would've been (or are) covered in RFC 8092's security section,
>> right?
>>
>> This is an Internet-Draft targetted for Informational status, I'm not
>> sure what you expect here.
>>
>>> SB> Is there is text somewhere that discusses the integrity and
>>> SB> synchronization of the parameters and any consequences that arise?
>> the what now? Can you elaborate on the above?
> you're supposed to guess
>
> the normal hack here is
>
>    this document introduces no new security issues beyond those discussed
>    in 1997

Guessing is horrible, but if that is what you do, that is what you do, 
and if the risks are the accepted norm in the BGP
community I am fine.

Is corruption (deliberate or otherwise) of the community strings 
something that BGPsec will address?

- Stewart


From nobody Wed Apr 19 01:55:26 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDA7131585; Wed, 19 Apr 2017 01:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 lXUOhXgiH8BY; Wed, 19 Apr 2017 01:55:13 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 6103813158F; Wed, 19 Apr 2017 01:55:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d0lOI-0002pN-OT; Wed, 19 Apr 2017 08:55:11 +0000
Date: Wed, 19 Apr 2017 17:55:07 +0900
Message-ID: <m237d493pw.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com> <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o24BKYaHF-MbosHw99HZ3fCoPTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:55:14 -0000

>> you're supposed to guess
>> 
>> the normal hack here is
>> 
>>    this document introduces no new security issues beyond those discussed
>>    in 1997
> 
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP community I am fine.

i meant that, instead of being specific, you left it to the authors to
guess what you wanted.

> Is corruption (deliberate or otherwise) of the community strings
> something that BGPsec will address?

no.  bgpsec does not sign over communities.  this is because hops may
validly remove them, thus invalidating signatures.

randy


From nobody Wed Apr 19 02:01:49 2017
Return-Path: <prvs=1282ce1966=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E49213159A for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 02:01: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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4kglTsPY9Cu for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 02:01:45 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A29E131583 for <ietf@ietf.org>; Wed, 19 Apr 2017 02:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492592504; x=1493197304; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=2JTTuxbTRB9y1RSB/8+p+zfE4 ouEhimPvF3r96LJCvI=; b=Bk9f0WX70P8O7KTWU8mQnWGV9KFxdaKg7iTcYnm9T ZN7w5hE+axjQ5yAHqpx1tWp/TOhVTEs4yUGQWXTWDOUdc1YJrPt+a/Nn8C2+cFhI WEN40Q63UctsWBzu7cZuw8221OmEgF+6C0r14HgYR3SCr6Chbh54CtAmyp0b562X d8=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=IudwYlx2U2WwXq/49inj2g2wheJs0gOxgZ8SFnitJcvDwdP2Z36/RMZqegYb cLvmlB0utuBAVhjvcLR7BXTpfB6ejC0qX+0/4PZ5OCPE4yScTTWbdPAaf jRy+SL7HnBqYHl7ll/c5ZuieW7Vo9hYCFUAY4ZHfAY4SZaH0iUWdOc=;
X-MDAV-Processed: mail.consulintel.es, Wed, 19 Apr 2017 11:01:43 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 19 Apr 2017 11:01:43 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005410879.msg for <ietf@ietf.org>; Wed, 19 Apr 2017 11:01:41 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170419:md50005410879::2alVxCSHAmf1rZts:0000Aeiu
X-Return-Path: prvs=1282ce1966=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 19 Apr 2017 11:01:37 +0200
Subject: Re: Update on feedback on US-based meetings, and IETF 102
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es>
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
References: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es> <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KiFDwxJV0wQRlQA7iAheIJhItmA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 09:01:48 -0000

The problem comes from non-being a native speaker, as definitively that mea=
ns that many times you =E2=80=9Ctranslate=E2=80=9D from your mother tongue.=
 And in this case, it seems, according to many sources, English and Chinese=
 is declining across the time vs Spanish. Most of the sources state that Sp=
anish is the 2nd one right now, some indicate it is Hindi, but English is a=
lways after Spanish (again, native speakers):

https://www.tomedes.com/top-10-languages-natively-spoken.php

http://www.vistawide.com/languages/top_30_languages.htm

https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speaker=
s

https://en.wikipedia.org/wiki/Linguistic_demography

https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers

The latest info from 2016, which I=E2=80=99ve found only in spanish, seems =
to confirm the trend and in 2016 the censed number of native spanish speake=
rs raised to 472 millions, 567 as second language, which agains confirms Ch=
inesse being the first, Spanish the second (7,8% of total population).

http://www.cervantes.es/imagenes/File/prensa/EspanolLenguaViva16.pdf

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Toerless Eckert <tte@cs.fau.d=
e>
Responder a: <tte@cs.fau.de>
Fecha: martes, 18 de abril de 2017, 23:09
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: Re: Update on feedback on US-based meetings, and IETF 102

    On Sat, Apr 15, 2017 at 10:54:09PM +0200, JORDI PALET MARTINEZ wrote:
    > This shows something that I believe most of the native English IETF p=
articipants usually don???t realize when having discussion (I???m referring=
 here in general, also technical discussions) with non-native speakers, and=
 how difficult is for the others. Maybe we should switch to Chinese as the =
default IETF language, or Spanish, as they have more speakers worldwide tha=
n English!
   =20
    https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_spea=
kers
   =20
    According to that page, spanish does not have more speakers worldwide t=
han english, but
    rather the opposite. And IMHO, the relevant number is really just the n=
umber of L2
    (second language) speakers, and thats lead by english, followed by mala=
y, french,
    mandarin, arabic, hindi, russian, urdu, swahili and then spanish!
   =20
    > I???m still believe that IAOC attitude is not justified at all, and i=
f we don???t have answers from them by next Monday, we should consider a re=
call process. Hopefully is not the case.
   =20
    What do you think is the IAOC attitude ? All i read was very noncommitt=
al and "we
    still collect information".
   =20
    I do not even know what the metric for selection is. I hope it is not t=
o make the
    most vocal mailing list participants most happy. I would start with exc=
luding the least
    number of candidate participants excluded by travel policies, then the =
lowest price for
    median particiants (flight, hotel, food) and then most convenient. I th=
ink
    IAOC somehow takes these factors into account, but i can not remember t=
hat they did send=20
    their most concrete data for these factors for various countries to the=
 mailing list.
   =20
    Cheers
        Toerless
   =20
   =20
    > Regards,
    > Jordi
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MARTINEZ <=
jordi.palet@consulintel.es>;
    > Responder a: < jordi.palet@consulintel.es>;
    > Fecha: viernes, 14 de abril de 2017, 01:24
    > Para: <ietf@ietf.org>;
    > Asunto: Re: Update on feedback on US-based meetings, and IETF 102
    >=20
    > Well, for some countries what Trump said, has already been a fact, fo=
r example the prohibition to have computers on board. Is not that the case?
    >=20
    > Whatever we want to decide, cancel SF or not, it may highly depend on=
 budget, we like it or not. And that means that we need answers:
    >=20
    >     If we cancel San Francisco, how much that is going to cost to the=
 IETF for each of two planned meetings?
    >    =20
    >     Can we cancel the actual hotel contract considering the new US si=
tuation? If not, has this been considered for new contracts to avoid this p=
roblem?
    >    =20
    >     Otherwise there is any reason that can justify the lack of transp=
arency in this?
    >=20
    > The problem is so big for this community that I don???t even agree th=
at the IAOC should take the decision. It must be a collective one, especial=
ly when the IAOC is demonstrating thru facts that they don???t care that we=
 are discussing and wasting our time without the minimum relevant data, thi=
s is disrespectful and even more, not responding to emails since even since=
 years ago, shows lack of education=20
    >=20
    > Regards,
    > Jordi
    >=20
    >=20
    >=20
    >=20
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >=20
    > This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that a=
ny disclosure, copying, distribution or use of the contents of this informa=
tion, including attached files, is prohibited.
    >=20
    >=20
   =20
    --=20
    ---
    tte@cs.fau.de
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Apr 19 02:28:11 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA0A71315B5 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 02:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 MhDOUfJmbqrC for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 02:28:02 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAD7B1315A7 for <ietf@ietf.org>; Wed, 19 Apr 2017 02:28:01 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.local ([194.88.241.232]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v3J9RpJO048586 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Apr 2017 10:27:52 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [194.88.241.232] claimed to be cupcake.local
Message-ID: <58F72D8F.6020106@foobar.org>
Date: Wed, 19 Apr 2017 12:27:43 +0300
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.12 (Macintosh/20170323)
MIME-Version: 1.0
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: Randy Bush <randy@psg.com>, Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com> <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2FigQrOvEUiayH2MgQswCVmb0wE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 09:28:03 -0000

Stewart Bryant wrote:
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP
> community I am fine.

there's a general understanding out there that if you're directly
connect to $asn, you can somewhat believe $asn:* or $asn:*:*
communities, assuming you trust the remote ASN. Otherwise all bets are off.

Nick


From nobody Wed Apr 19 05:01:20 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF861294E8 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 05:01: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 MrXxkdDnJyFo for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 05:01:15 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 68E211294EE for <ietf@ietf.org>; Wed, 19 Apr 2017 05:01:15 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id l28so13931863wre.0 for <ietf@ietf.org>; Wed, 19 Apr 2017 05:01:15 -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=SuX3GZZs2LsaFJ2mb6elvi8vfdyNKxtkcVteVx116cA=; b=GG+r+UuNbp5neiLftsjlwXpQ7qnGHk4aOVqhkf/1H/CNsQbLRQRQUREYKKSYW66p0q w/FjEnHaEmmBb9rdhq/J+VvKg/yaGwW+g5lue0B9KkJ9BzZ5kETCzoAD13DzwZvFcgHO ZcTHALgfhSXwYgK6AinGCzthcEA67EZpeBnOlk0MwtJ114hjIUq2YOeJZIAXUrO3v83C xFgCup86jNSokeGPTH2tjI97wX/eimyLnLv80fZS4f0RW1VPfmFHXTugUr+R6iyJtq0C lHaFguiBRLRxAhoRB93sil2R3Yy41wOQEzfrDQUcah/gBek6V7AM4+ArHJFtI1EHxs3a aCmQ==
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=SuX3GZZs2LsaFJ2mb6elvi8vfdyNKxtkcVteVx116cA=; b=ua5enE12WYxdEN0P/zDJbBz5laQUbhegvk/3WJlnd9GuEuMUvZhiIYaaR4eKIKSZm4 DjpiIFfV4I8BrJkWg8EZT4XRQ6lb9/GN7N6afNLsxbl6cVCohLldHMYJId/CDN8THIkP 3SIIY4HfN2SkE6Eumr/Hyce1fklaUaT+/em+k2NaS2d35ccYuNPDENbfmgNOs37+ox7L l7NeExUjNXWloy128q2/XEYA0GGSGb9wUuRxqI0T7noNPVM3ZenV95n1gQFf0UL3Tngi G7vutxFIEW0e39bd1+WzzXc03cEl+qxDie8yQjt8aohvOetmS3nNF70PkO4LU4YWbATL a1NQ==
X-Gm-Message-State: AN3rC/5IF+Lj57n1/rzgoXeNgjkHckjpyExToGH7EIFvK0nSng1O2SUg QxRgI1Pu/77sCw==
X-Received: by 10.223.174.130 with SMTP id y2mr2776975wrc.79.1492603273773; Wed, 19 Apr 2017 05:01:13 -0700 (PDT)
Received: from [172.24.251.229] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id z84sm19076563wmh.27.2017.04.19.05.01.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 05:01:13 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <5010F48B-D95E-46F4-AB78-E2214652A57C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F52DB594-C473-4D8B-847C-7ECA2246E88B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Date: Wed, 19 Apr 2017 15:01:10 +0300
In-Reply-To: <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: jordi.palet@consulintel.es
References: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es> <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de> <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E8_jCi14DivrUTHmwrib1Wxg70s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 12:01:18 -0000

--Apple-Mail=_F52DB594-C473-4D8B-847C-7ECA2246E88B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Jordi.

I think a more pertinent question is how may of us can carry on a =
technical conversation in Spanish vs English vs Chinese.

It=E2=80=99s not enough to be able to order at a restaurant or tell a =
taxi driver where you want to go. I can do that and it=E2=80=99s =
probably true for many of our attendees from the US.  But I don=E2=80=99t =
speak it well enough to carry on a technical conversation. I would =
probably need Google translate if I wanted to write this message is =
Spanish.

I think on this criterion English wins out. Even if you count potential =
rather than current participants.

Yoav

> On 19 Apr 2017, at 12:01, JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es> wrote:
>=20
> The problem comes from non-being a native speaker, as definitively =
that means that many times you =E2=80=9Ctranslate=E2=80=9D from your =
mother tongue. And in this case, it seems, according to many sources, =
English and Chinese is declining across the time vs Spanish. Most of the =
sources state that Spanish is the 2nd one right now, some indicate it is =
Hindi, but English is always after Spanish (again, native speakers):
>=20
> https://www.tomedes.com/top-10-languages-natively-spoken.php
>=20
> http://www.vistawide.com/languages/top_30_languages.htm
>=20
> =
https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speake=
rs
>=20
> https://en.wikipedia.org/wiki/Linguistic_demography
>=20
> =
https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speaker=
s
>=20
> The latest info from 2016, which I=E2=80=99ve found only in spanish, =
seems to confirm the trend and in 2016 the censed number of native =
spanish speakers raised to 472 millions, 567 as second language, which =
agains confirms Chinesse being the first, Spanish the second (7,8% of =
total population).
>=20
> http://www.cervantes.es/imagenes/File/prensa/EspanolLenguaViva16.pdf
>=20
> Regards,
> Jordi
>=20
>=20
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Toerless Eckert =
<tte@cs.fau.de>
> Responder a: <tte@cs.fau.de>
> Fecha: martes, 18 de abril de 2017, 23:09
> Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
> CC: "ietf@ietf.org" <ietf@ietf.org>
> Asunto: Re: Update on feedback on US-based meetings, and IETF 102
>=20
>    On Sat, Apr 15, 2017 at 10:54:09PM +0200, JORDI PALET MARTINEZ =
wrote:
>> This shows something that I believe most of the native English IETF =
participants usually don???t realize when having discussion (I???m =
referring here in general, also technical discussions) with non-native =
speakers, and how difficult is for the others. Maybe we should switch to =
Chinese as the default IETF language, or Spanish, as they have more =
speakers worldwide than English!
>=20
>    =
https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speaker=
s
>=20
>    According to that page, spanish does not have more speakers =
worldwide than english, but
>    rather the opposite. And IMHO, the relevant number is really just =
the number of L2
>    (second language) speakers, and thats lead by english, followed by =
malay, french,
>    mandarin, arabic, hindi, russian, urdu, swahili and then spanish!
>=20
>> I???m still believe that IAOC attitude is not justified at all, and =
if we don???t have answers from them by next Monday, we should consider =
a recall process. Hopefully is not the case.
>=20
>    What do you think is the IAOC attitude ? All i read was very =
noncommittal and "we
>    still collect information".
>=20
>    I do not even know what the metric for selection is. I hope it is =
not to make the
>    most vocal mailing list participants most happy. I would start with =
excluding the least
>    number of candidate participants excluded by travel policies, then =
the lowest price for
>    median particiants (flight, hotel, food) and then most convenient. =
I think
>    IAOC somehow takes these factors into account, but i can not =
remember that they did send
>    their most concrete data for these factors for various countries to =
the mailing list.
>=20
>    Cheers
>        Toerless
>=20
>=20
>> Regards,
>> Jordi
>>=20
>> -----Mensaje original-----
>> De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es>;
>> Responder a: < jordi.palet@consulintel.es>;
>> Fecha: viernes, 14 de abril de 2017, 01:24
>> Para: <ietf@ietf.org>;
>> Asunto: Re: Update on feedback on US-based meetings, and IETF 102
>>=20
>> Well, for some countries what Trump said, has already been a fact, =
for example the prohibition to have computers on board. Is not that the =
case?
>>=20
>> Whatever we want to decide, cancel SF or not, it may highly depend on =
budget, we like it or not. And that means that we need answers:
>>=20
>>    If we cancel San Francisco, how much that is going to cost to the =
IETF for each of two planned meetings?
>>=20
>>    Can we cancel the actual hotel contract considering the new US =
situation? If not, has this been considered for new contracts to avoid =
this problem?
>>=20
>>    Otherwise there is any reason that can justify the lack of =
transparency in this?
>>=20
>> The problem is so big for this community that I don???t even agree =
that the IAOC should take the decision. It must be a collective one, =
especially when the IAOC is demonstrating thru facts that they don???t =
care that we are discussing and wasting our time without the minimum =
relevant data, this is disrespectful and even more, not responding to =
emails since even since years ago, shows lack of education
>>=20
>> Regards,
>> Jordi
>>=20
>>=20
>>=20
>>=20
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.consulintel.es
>> The IPv6 Company
>>=20
>> This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the =
individual(s) named above. If you are not the intended recipient be =
aware that any disclosure, copying, distribution or use of the contents =
of this information, including attached files, is prohibited.
>>=20
>>=20
>=20
>    --
>    ---
>    tte@cs.fau.de
>=20
>=20
>=20
>=20
>=20
>=20
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>=20
> This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the =
individual(s) named above. If you are not the intended recipient be =
aware that any disclosure, copying, distribution or use of the contents =
of this information, including attached files, is prohibited.
>=20
>=20
>=20


--Apple-Mail=_F52DB594-C473-4D8B-847C-7ECA2246E88B
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-----

iQEcBAEBCgAGBQJY91GGAAoJELhJCxUKWMyZkPoIAL0kuVKujSJ/imr2Rc3p5yqB
JqJAgMt16FoRwbTuS62W0wQkB1S2l+GUiO4OHwnYGxZZqR56qMQZvhLjzMGBJ8k5
cUfqT41o/98CM9PvI6zTWhVO0/LAQMwT1NByJ2LucddG7rzLBwIJR2OMQnmiSH/r
XFtnV/WxYo6cp3gzlLA6wi9Oj+jKKJYnu7UVdePf3PQ1NiGYWK3KzR2CAq0cKRzZ
WmpzpGoTgnnjP2bug/kIc2sNcKDvCJFIAYmOFLkMdXxzDrjcbkU35W0yERnYV7CG
SBS72j+8/dT6RhTm+Vnzskc2m17Are+tk9QoTgKDQHhuo8CdPVE3iR3e7p344mQ=
=VzRW
-----END PGP SIGNATURE-----

--Apple-Mail=_F52DB594-C473-4D8B-847C-7ECA2246E88B--


From nobody Wed Apr 19 06:20:20 2017
Return-Path: <klensin@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15DF129562; Wed, 19 Apr 2017 06:20:12 -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, RP_MATCHES_RCVD=-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 BMQcko1-gYsg; Wed, 19 Apr 2017 06:20:10 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494E8129543; Wed, 19 Apr 2017 06:20:07 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1d0pWa-000EiU-5F; Wed, 19 Apr 2017 09:20:00 -0400
Date: Wed, 19 Apr 2017 09:19:52 -0400
From: John C Klensin <klensin@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Vint Cerf <vint@google.com>, alexey.melnikov@isode.com, draft-freytag-lager-variant-rules@ietf.org, shollenbeck@verisign.com, ietf@ietf.org
cc: idna-update@ietf.org
Subject: Re:Last Call: <draft-freytag-lager-variant-rules-05.txt> (Variant Rules) to Informational RFC
Message-ID: <C0533444B8C1E349F970D950@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: klensin@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N6tLszUf8RGkkjop22PT4o8neF8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 13:20:13 -0000

Paul and IESG,

While I think the clarifications in this draft are a
considerable improvement, your response to Vint captures the
concern about this document all along.  To explain, I'm going to
need to review some history, so apologies for probable length.

The whole topic of DNS "variant rules" has been controversial
among those who know about them and care from the beginning.
They are much less so in the context of the root zone for which,
the special names issues aside, ICANN has clear responsibility
(and can make whatever rules they like, including the one to
allow thousands of names, as long as IETF Standards are not
violated -- and even the latter seems to be under threat), than
for zones deeper in the tree and whether such rules are used
there in a voluntary or involuntary.  

I note that, at the time ICANN first started allowing and
encouraging IANA publication/ registrations of the characters
that particular TLDs would allow in their zones, the ICANN Board
(with support from me and the IAB), created that registry
directly rather than requiring that the IETF establish the
registry and rules for its maintenance.  The idea was to try to
help preserve and reinforce the separation implied by the above. 

We've also seen some history of documents being adopted (a
deliberately vague term) in the IETF then being used to argue in
ICANN processes that the IETF action means that ICANN has to
implement then.  That approach goes back to at least the CRISP
effort (RFC 3707).   That it has been unsuccessful in many cases
is beside the point.  That some of the efforts in the IETF have
been strongly influenced by ICANN staff members who might (or
might not) have planned to influence ICANN policy development
processes in ways that they could not do directly may or may not
also be an issue (and you, and other ICANN staff, may reasonably
interpret all of those data differently than I do).

So the IETF created a WG, LAGER, to do the core work on which
this I-D was based, ultimately cumulating in RFC 7940.  I note
that, in recent years, we've had trouble getting enough traction
to do meaningful work on any internationalization (i18n) issues
-- IMO, EAI and PRECIS barely had enough active participation to
justify a claim of meaningful WG consensus by the time their
work wound down and other than a BOF (LUCID) that, IMO, never
engaged with the key topics, the IETF has not been able to
engage on the "non-decomposable character" issue despite a
request from the IAB that it do so.   I imagine that many
people, even some of the i18n experts looked at the lAGER
charter and said "if people want to get together and write some
data representation rules around something that is basically an
ICANN problem, I don't need to worry about it".   I also
imagine, reinforced by the few comments during IETF Last Call on
what became 7940, that the Last Call reaction was similar.
However, in that case, there _was_ a WG, the IESG reached the
conclusion that the WG had sufficient membership and
participation to be meaningful, and the community generally
assumes that WG conclusions should stand as IETF ones if there
is no meaningful and substantive dissent during Last Call.

Then the IESG, in its wisdom and for reasons not announced to
the IETF other than "concluded work" (such announcements are
rarely made and I wouldn't propose to change it) closed down the
WG.  

Then this document appears as an individual submission.   There
has been little evidence of wide review, especially by those
with significant history of IDN involvement in the IETF.
Perhaps that is in part because it shares the limited scope
issues with LAGER and RFC 7940, requires a thorough
understanding of that document and what it does and does not do,
and, noting that the IAB just shut down its I19n Program after a
long period of inactivity, there seems to be even less ability
to get IETF traction on i18n issues than there was a few years
ago.   

As I understand it, this document provides and explains a system
to assist in developing and describing rules that might then be
documented according to 7940.  Even with the latest revision, it
makes some assumptions that some of us (including, given his
comment, I assume Vint) question in an IETF context (even if
they represent ICANN consensus and are reasonable there because
the scope, conditions, and support arrangements are different).
At least in principle, the IESG could have reopened LAGER,
gotten review there, and then pushed this through as a document
from the same WG that was responsible for 7940.  They didn't. 

But your conclusion was (out of context, but complete below)

> There is no IDNA Working Group any more, so there is no way to
> say that it was not endorsed by this WG. The document is,
> however, intending to be an IETF consensus document.

Right.  There is no way to say that LAGER did not endorse it (or
would not have endorsed it had it still existed).   Likewise for
IDNABIS.  AFAIK, DNSOP and for that matter and, despite it (and
7940 (to pick a random example) LISP didn't consider it either.
Since 7940 (last paragraph of introduction) and this document
even more strongly claim that their data structures, mechanisms,
and principles can be used for non-DNS identifier labels,
perhaps the latter should have looked at it.  But none of them
did although, by your logic as I read it, there is no way to
assume that they would not have endorsed it had they looked and
therefore their assent must be assumed.

For a claim of IETF consensus on an individual submission,
especially one that is the slightest bit controversial (as this
clearly is, even if one believes the controversy is about
process, not substantive content), I think there has to be clear
evidence of adequate and competent review of document content
and relationship to other work to make that consensus claim
meaningful.  I don't think that has been demonstrated; YMMD.

I also think that, if a document comes out of a WG and then one
of its authors produces a individual document that suggests an
extension, interpretation, or supplemental tools, we need to be
extra-careful about that document and IETF consensus claims.
YMMD about that too.

Your response to Vint about what can be done about this was:

> It says "Informational" right at the top of the document, and
> that's the best we can do for the RFC Series.

But that is not "the best we can do".   The IESG can say
"insufficient evidence of IETF consensus" and drop the document.
I don't recommend that, but it is possible that others would
disagree.  The document can be handed off to the Independent
Submission Editor with recommendation for publication with the
usual clear statement from that Stream about there being no
consensus assessment.   Noting that all of the documents that
started the "variant" epidemic (RFCs 3743, 4290, and, as a key
example at least, 4713) were published in the Independent Stream
and that didn't prevent them from getting community attention,
there is probably little argument for the IETF Stream unless
there is either clear evidence of consensus or if this document
is really expected to be treated as a Standards Track supplement
to 7940 independent of its official status.   Or, in principle,
the IESG could attach a note indicating that the document is
published as a convenience and there is little or no evidence of
informed IETF consensus about it.  

For me, it is precisely the claim that the document represents
IETF consensus, or the now-demonstrated high likelihood that
claim will be made, that is the problem here.   That claim is,
at best, not demonstrated to be true and, for a document that I
believe lies very close to the boundaries of IETF scope and
relationship to ICANN, I think we need to be extra careful about
it when it is not demonstrably true (and not just because a
series of current and closed WGs haven't commented on, much less
endorsed, it).

   best,
     john


  ---------------------------

For the information of the IESG and community, Paul forwarded
the Last Call announcement to the idna-update mailing list.
Vint responded there (but not to the IETF list or, AFAIK, to the
IESG) and Paul responded to him (but, again, not to the IETF
list or AFAIK, the IESG).  Paul's response to Vint and, IIR, the
substantive part of Vint's message appear below.


--On Tuesday, April 18, 2017 09:38 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> On 18 Apr 2017, at 7:04, Vint Cerf wrote:
> 
>> if this is published, I hope it is made clear that this is
>> not a  standards
>> recommendation endorsed by the IDNA working group.
> 
> It says "Informational" right at the top of the document, and
> that's the best we can do for the RFC Series.
> 
> There is no IDNA Working Group any more, so there is no way to
> say that it was not endorsed by this WG. The document is,
> however, intending to be an IETF consensus document.
> 
> --Paul Hoffman


From nobody Wed Apr 19 06:38:00 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A2F1293F4; Wed, 19 Apr 2017 06:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 Gl1jzugwCKd0; Wed, 19 Apr 2017 06:37:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 68249127275; Wed, 19 Apr 2017 06:37:50 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d0pnn-0004HA-RV; Wed, 19 Apr 2017 13:37:48 +0000
Date: Wed, 19 Apr 2017 22:37:45 +0900
Message-ID: <m2bmrs7c2e.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
In-Reply-To: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eAc_bFG5YGG_q2L-j6YFEbauc3g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 13:37:52 -0000

> I was wondering if there was more scope to make mischief at a distance
> in a less less obvious way than before.

there isn't

but where were you when the blackhole community was passed?

> So you rely on the nodes that receive these community strings to
> interpret them in a common way.

no.  as with bgp communities since they were handed down to us by our
mothers, unless specified in some other document, there is no assumption
that all apply the same semantic to the same syntax.

randy


From nobody Wed Apr 19 07:18:56 2017
Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776C4129649 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:18:48 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.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 SU1Y82Lhv-pn for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:18:47 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 48262129AAD for <ietf@ietf.org>; Wed, 19 Apr 2017 07:18:45 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id l28so16625883wre.0 for <ietf@ietf.org>; Wed, 19 Apr 2017 07:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6f/MLbmZcIGt0635Dmfko5kO55hiUY0E1UeOldlQ1Gc=; b=VIhUD1GBPSI1iKiZ2vM0X2jhTeS3O3vKWSVhTQXGZUB8XTh9G8p/FUOyIMlagSN/3P PCbJxePkEzigdXhFn70Z/m2pL4ZCtibfNXK6Iar3DMedwFDOMCYzBS9gYa/bPNSF1vTw jBe+ryP/ujtppIGcuwOBjUuQDp+QfJgc/9iu7CrlqZ2UCPc7Gj1oWwVTn4SqN3IVE82x IP8NtOubJ6S7DB9wBXLyz5W1XkQs7n92eVJiJq8DWp32vfvVO7WrIaRTTNEiWLxO+q3J NlI98im97rAYrlzk6UhSgceOE1ECSVoPBEIY2YmFJBYhapGp87VDLv3EJJurgUUjuMSL +WPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=6f/MLbmZcIGt0635Dmfko5kO55hiUY0E1UeOldlQ1Gc=; b=VAwKIyxEFGbFaIJ2v46cbXM5YmHDYUZ4rjLVpu9eulNZKY800D2sONfe+9OclPoh9h v5Iz3eRPHyn8awMqQHye+oXedvU0C7n/RCcR/6tCbQCUslcAWka9I712C5CIPsRRnutA eVzzB1tOT3Ia7ZLWPvarQ9Ck3t7szjQZX2TWZ6Z6df7OzNJDc8KYWE/axShPJifwAaEV RQExH67AUFVFklfVkO6WHxsubxsw/CJHyLR/cC3vK/nR7xjxfyVx/MJrFMdBZlHhuxar KRRGc0cssO2YCg/wdcTWrVqTeLzs+yS4EtKEGfHZF8JthWWlpX3hHJen+P9kAfjJQSdR P1wA==
X-Gm-Message-State: AN3rC/55tLaMW4jItpQf5mZL8u3EJx8Hpkz46LsAzLT0SqG0uwIIFhiY Wnug2e6ZxXAKbQ==
X-Received: by 10.223.130.212 with SMTP id 78mr2970192wrc.106.1492611523758; Wed, 19 Apr 2017 07:18:43 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:1558:83a0:4ae5:75f7]) by smtp.gmail.com with ESMTPSA id d10sm3498962wrd.54.2017.04.19.07.18.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:18:42 -0700 (PDT)
Date: Wed, 19 Apr 2017 16:18:41 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
Message-ID: <20170419141841.5agsblcuiqvyxek4@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z6dmgVe_FkOawrtgK0irNO8J8H4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:18:48 -0000

On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
> > >     Operations and Security [RFC7454].
> > > 
> > > SB> You do not address the question of whether there are new
> > > SB> considerations, or considerations that are of increased importance?
> > 
> > It is my understanding that RFC 8092 "BGP Large Communities" are
> > just like RFC 1997 "BGP Communities", but ...  larger (for lack of
> > better words). Referencing RFC 7454 seems plenteous.
> > 
> > So, what if there are not any additional considerations, If there
> > were, they would've been (or are) covered in RFC 8092's security
> > section, right?
> > 
> > This is an Internet-Draft targetted for Informational status, I'm
> > not sure what you expect here.
>
> I was wondering if there was more scope to make mischief at a distance
> in a less less obvious way than before.
> 
> If everyone is happy that there is no additional risk then I am fine,
> but seems to me the more knobs you give the mischeif maker to turn the
> more security risks you have.

Ah, I see now. This document does not create new knobs. RFC 8092
definded the BGP Large Community attribute, and this internet-draft
reflects on possible use cases, much like RFC 1998 was a companion for
RFC 1997.

> > > SB> Is there is text somewhere that discusses the integrity and
> > > SB> synchronization of the parameters and any consequences that arise?
> >
> > the what now? Can you elaborate on the above?
>
> So you rely on the nodes that receive these community strings to
> interpret them in a common way. Maybe this is an already solved
> problem, or an known risk, but what if the dictionaries get out of
> sync?

Yes, there is not anything novel here. How to keep a list of integers
like UN M.49 up to date (or how to write bug-free software) is out of
scope for this internet draft. ;-)

Deploy coherent routing policy configurations on an autonomous
system-wide level is not for this document to cover.

Kind regards,

Job


From nobody Wed Apr 19 07:52:35 2017
Return-Path: <vint@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621B5128799 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, RP_MATCHES_RCVD=-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=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 6wOoH6qp9IsD for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:52:31 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::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 43658129ACD for <ietf@ietf.org>; Wed, 19 Apr 2017 07:52:30 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id j201so30308281oih.2 for <ietf@ietf.org>; Wed, 19 Apr 2017 07:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F43vrZAi+b5LFudxLdsSJEDrhLxyoGOM5b7wNfJNfPE=; b=HPJ9KMvSvH02NgzNsbvbtMixjdqFe2synAF84vIhXN0ybg1OTooEbgNW7uwqFD22Ke nkUqkevP1PZHLOutTXeYEYLOSuTxqhPg+g4DOsp+QRLstXIQmLhD2W7mG8K+Vc9DURKT Z6qGLQxkHe+SRvd21QqJdNf6sErBc7TBMsLCrhdw/zrr0qmJBUr0EM3MKvCUmxYGMMfW 15Ml8OI3maMP1wU85QV3BOKfY23KsKL/TUCqHMPSpbN+seUGsnnY5t3VoGDUAXpdnW3V HHrFYHGmll1NvqrkxmAJyl87PBCNrHXvSSkJnfAl6jhsbQOm7Mp7cLNizx+Xj2MqvD2C I2fQ==
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=F43vrZAi+b5LFudxLdsSJEDrhLxyoGOM5b7wNfJNfPE=; b=Rk8o1ka2Z6Zmq/fzNV3oFr68x6WCCu9FikaeNjr6Vm01a9U2vSZ+pTqGHzumV803JV uYKouDlwO09c89Yuxq7MJ3vw45rByyBOPMqqwCLfSGL+Jec7fQOhVViLBOlnfOed6wYe ReZYf9RPpCNGGuACYx02Ot4pACh9pQs866FDSIytcaiSPEXAB27MsNEqXBo4Ba91CHy6 7t1g4WEn6po/MkVbu6jdlfwrzadSvUsABmeGuq6iywMVtEqSq/HHxnvVTyvYuzVe2I9N FBprUOknKYabzpfGh5zCynlEDiAGLt1v8K7Ga523nUqYxSDCgENy/kttFv2QSu+yjs54 LTHQ==
X-Gm-Message-State: AN3rC/7En6atEwWf1nIrVZxaE3zBvOCSVxOP3/vVXKBMdgoJ+NH+abNe waBnRNybR/pAjtSCXC86KpE9uRUO/Ieb
X-Received: by 10.157.54.147 with SMTP id h19mr1540423otc.156.1492613549477; Wed, 19 Apr 2017 07:52:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.18.208 with HTTP; Wed, 19 Apr 2017 07:52:28 -0700 (PDT)
In-Reply-To: <C0533444B8C1E349F970D950@PSB>
References: <C0533444B8C1E349F970D950@PSB>
From: Vint Cerf <vint@google.com>
Date: Wed, 19 Apr 2017 10:52:28 -0400
Message-ID: <CAHxHggff1dQg9=Y36YoMDx+PVOf6gPJEYcXJv_U-2Yf_MxPH5g@mail.gmail.com>
Subject: Re: Last Call: <draft-freytag-lager-variant-rules-05.txt> (Variant Rules) to Informational RFC
To: John C Klensin <klensin@jck.com>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Alexey Melnikov <alexey.melnikov@isode.com>,  draft-freytag-lager-variant-rules@ietf.org, shollenbeck@verisign.com,  IETF-Discussion list <ietf@ietf.org>, idna-update@ietf.org
Content-Type: multipart/alternative; boundary=001a11c16cc667b0c6054d862c57
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CcIkoY5ZcdruWXYAt9xIltLLXrw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:52:34 -0000

--001a11c16cc667b0c6054d862c57
Content-Type: text/plain; charset=UTF-8

+1
v


On Wed, Apr 19, 2017 at 9:19 AM, John C Klensin <klensin@jck.com> wrote:

> Paul and IESG,
>
> While I think the clarifications in this draft are a
> considerable improvement, your response to Vint captures the
> concern about this document all along.  To explain, I'm going to
> need to review some history, so apologies for probable length.
>
> The whole topic of DNS "variant rules" has been controversial
> among those who know about them and care from the beginning.
> They are much less so in the context of the root zone for which,
> the special names issues aside, ICANN has clear responsibility
> (and can make whatever rules they like, including the one to
> allow thousands of names, as long as IETF Standards are not
> violated -- and even the latter seems to be under threat), than
> for zones deeper in the tree and whether such rules are used
> there in a voluntary or involuntary.
>
> I note that, at the time ICANN first started allowing and
> encouraging IANA publication/ registrations of the characters
> that particular TLDs would allow in their zones, the ICANN Board
> (with support from me and the IAB), created that registry
> directly rather than requiring that the IETF establish the
> registry and rules for its maintenance.  The idea was to try to
> help preserve and reinforce the separation implied by the above.
>
> We've also seen some history of documents being adopted (a
> deliberately vague term) in the IETF then being used to argue in
> ICANN processes that the IETF action means that ICANN has to
> implement then.  That approach goes back to at least the CRISP
> effort (RFC 3707).   That it has been unsuccessful in many cases
> is beside the point.  That some of the efforts in the IETF have
> been strongly influenced by ICANN staff members who might (or
> might not) have planned to influence ICANN policy development
> processes in ways that they could not do directly may or may not
> also be an issue (and you, and other ICANN staff, may reasonably
> interpret all of those data differently than I do).
>
> So the IETF created a WG, LAGER, to do the core work on which
> this I-D was based, ultimately cumulating in RFC 7940.  I note
> that, in recent years, we've had trouble getting enough traction
> to do meaningful work on any internationalization (i18n) issues
> -- IMO, EAI and PRECIS barely had enough active participation to
> justify a claim of meaningful WG consensus by the time their
> work wound down and other than a BOF (LUCID) that, IMO, never
> engaged with the key topics, the IETF has not been able to
> engage on the "non-decomposable character" issue despite a
> request from the IAB that it do so.   I imagine that many
> people, even some of the i18n experts looked at the lAGER
> charter and said "if people want to get together and write some
> data representation rules around something that is basically an
> ICANN problem, I don't need to worry about it".   I also
> imagine, reinforced by the few comments during IETF Last Call on
> what became 7940, that the Last Call reaction was similar.
> However, in that case, there _was_ a WG, the IESG reached the
> conclusion that the WG had sufficient membership and
> participation to be meaningful, and the community generally
> assumes that WG conclusions should stand as IETF ones if there
> is no meaningful and substantive dissent during Last Call.
>
> Then the IESG, in its wisdom and for reasons not announced to
> the IETF other than "concluded work" (such announcements are
> rarely made and I wouldn't propose to change it) closed down the
> WG.
>
> Then this document appears as an individual submission.   There
> has been little evidence of wide review, especially by those
> with significant history of IDN involvement in the IETF.
> Perhaps that is in part because it shares the limited scope
> issues with LAGER and RFC 7940, requires a thorough
> understanding of that document and what it does and does not do,
> and, noting that the IAB just shut down its I19n Program after a
> long period of inactivity, there seems to be even less ability
> to get IETF traction on i18n issues than there was a few years
> ago.
>
> As I understand it, this document provides and explains a system
> to assist in developing and describing rules that might then be
> documented according to 7940.  Even with the latest revision, it
> makes some assumptions that some of us (including, given his
> comment, I assume Vint) question in an IETF context (even if
> they represent ICANN consensus and are reasonable there because
> the scope, conditions, and support arrangements are different).
> At least in principle, the IESG could have reopened LAGER,
> gotten review there, and then pushed this through as a document
> from the same WG that was responsible for 7940.  They didn't.
>
> But your conclusion was (out of context, but complete below)
>
> > There is no IDNA Working Group any more, so there is no way to
> > say that it was not endorsed by this WG. The document is,
> > however, intending to be an IETF consensus document.
>
> Right.  There is no way to say that LAGER did not endorse it (or
> would not have endorsed it had it still existed).   Likewise for
> IDNABIS.  AFAIK, DNSOP and for that matter and, despite it (and
> 7940 (to pick a random example) LISP didn't consider it either.
> Since 7940 (last paragraph of introduction) and this document
> even more strongly claim that their data structures, mechanisms,
> and principles can be used for non-DNS identifier labels,
> perhaps the latter should have looked at it.  But none of them
> did although, by your logic as I read it, there is no way to
> assume that they would not have endorsed it had they looked and
> therefore their assent must be assumed.
>
> For a claim of IETF consensus on an individual submission,
> especially one that is the slightest bit controversial (as this
> clearly is, even if one believes the controversy is about
> process, not substantive content), I think there has to be clear
> evidence of adequate and competent review of document content
> and relationship to other work to make that consensus claim
> meaningful.  I don't think that has been demonstrated; YMMD.
>
> I also think that, if a document comes out of a WG and then one
> of its authors produces a individual document that suggests an
> extension, interpretation, or supplemental tools, we need to be
> extra-careful about that document and IETF consensus claims.
> YMMD about that too.
>
> Your response to Vint about what can be done about this was:
>
> > It says "Informational" right at the top of the document, and
> > that's the best we can do for the RFC Series.
>
> But that is not "the best we can do".   The IESG can say
> "insufficient evidence of IETF consensus" and drop the document.
> I don't recommend that, but it is possible that others would
> disagree.  The document can be handed off to the Independent
> Submission Editor with recommendation for publication with the
> usual clear statement from that Stream about there being no
> consensus assessment.   Noting that all of the documents that
> started the "variant" epidemic (RFCs 3743, 4290, and, as a key
> example at least, 4713) were published in the Independent Stream
> and that didn't prevent them from getting community attention,
> there is probably little argument for the IETF Stream unless
> there is either clear evidence of consensus or if this document
> is really expected to be treated as a Standards Track supplement
> to 7940 independent of its official status.   Or, in principle,
> the IESG could attach a note indicating that the document is
> published as a convenience and there is little or no evidence of
> informed IETF consensus about it.
>
> For me, it is precisely the claim that the document represents
> IETF consensus, or the now-demonstrated high likelihood that
> claim will be made, that is the problem here.   That claim is,
> at best, not demonstrated to be true and, for a document that I
> believe lies very close to the boundaries of IETF scope and
> relationship to ICANN, I think we need to be extra careful about
> it when it is not demonstrably true (and not just because a
> series of current and closed WGs haven't commented on, much less
> endorsed, it).
>
>    best,
>      john
>
>
>   ---------------------------
>
> For the information of the IESG and community, Paul forwarded
> the Last Call announcement to the idna-update mailing list.
> Vint responded there (but not to the IETF list or, AFAIK, to the
> IESG) and Paul responded to him (but, again, not to the IETF
> list or AFAIK, the IESG).  Paul's response to Vint and, IIR, the
> substantive part of Vint's message appear below.
>
>
> --On Tuesday, April 18, 2017 09:38 -0700 Paul Hoffman
> <paul.hoffman@vpnc.org> wrote:
>
> > On 18 Apr 2017, at 7:04, Vint Cerf wrote:
> >
> >> if this is published, I hope it is made clear that this is
> >> not a  standards
> >> recommendation endorsed by the IDNA working group.
> >
> > It says "Informational" right at the top of the document, and
> > that's the best we can do for the RFC Series.
> >
> > There is no IDNA Working Group any more, so there is no way to
> > say that it was not endorsed by this WG. The document is,
> > however, intending to be an IETF consensus document.
> >
> > --Paul Hoffman
>
>


-- 
New postal address:
Google
1875 Explorer Street, 10th Floor
Reston, VA 20190

--001a11c16cc667b0c6054d862c57
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1=C2=A0<div>v</div><div><br></div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Wed, Apr 19, 2017 at 9:19 AM, J=
ohn C Klensin <span dir=3D"ltr">&lt;<a href=3D"mailto:klensin@jck.com" targ=
et=3D"_blank">klensin@jck.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Paul and IESG,<br>
<br>
While I think the clarifications in this draft are a<br>
considerable improvement, your response to Vint captures the<br>
concern about this document all along.=C2=A0 To explain, I&#39;m going to<b=
r>
need to review some history, so apologies for probable length.<br>
<br>
The whole topic of DNS &quot;variant rules&quot; has been controversial<br>
among those who know about them and care from the beginning.<br>
They are much less so in the context of the root zone for which,<br>
the special names issues aside, ICANN has clear responsibility<br>
(and can make whatever rules they like, including the one to<br>
allow thousands of names, as long as IETF Standards are not<br>
violated -- and even the latter seems to be under threat), than<br>
for zones deeper in the tree and whether such rules are used<br>
there in a voluntary or involuntary.<br>
<br>
I note that, at the time ICANN first started allowing and<br>
encouraging IANA publication/ registrations of the characters<br>
that particular TLDs would allow in their zones, the ICANN Board<br>
(with support from me and the IAB), created that registry<br>
directly rather than requiring that the IETF establish the<br>
registry and rules for its maintenance.=C2=A0 The idea was to try to<br>
help preserve and reinforce the separation implied by the above.<br>
<br>
We&#39;ve also seen some history of documents being adopted (a<br>
deliberately vague term) in the IETF then being used to argue in<br>
ICANN processes that the IETF action means that ICANN has to<br>
implement then.=C2=A0 That approach goes back to at least the CRISP<br>
effort (RFC 3707).=C2=A0 =C2=A0That it has been unsuccessful in many cases<=
br>
is beside the point.=C2=A0 That some of the efforts in the IETF have<br>
been strongly influenced by ICANN staff members who might (or<br>
might not) have planned to influence ICANN policy development<br>
processes in ways that they could not do directly may or may not<br>
also be an issue (and you, and other ICANN staff, may reasonably<br>
interpret all of those data differently than I do).<br>
<br>
So the IETF created a WG, LAGER, to do the core work on which<br>
this I-D was based, ultimately cumulating in RFC 7940.=C2=A0 I note<br>
that, in recent years, we&#39;ve had trouble getting enough traction<br>
to do meaningful work on any internationalization (i18n) issues<br>
-- IMO, EAI and PRECIS barely had enough active participation to<br>
justify a claim of meaningful WG consensus by the time their<br>
work wound down and other than a BOF (LUCID) that, IMO, never<br>
engaged with the key topics, the IETF has not been able to<br>
engage on the &quot;non-decomposable character&quot; issue despite a<br>
request from the IAB that it do so.=C2=A0 =C2=A0I imagine that many<br>
people, even some of the i18n experts looked at the lAGER<br>
charter and said &quot;if people want to get together and write some<br>
data representation rules around something that is basically an<br>
ICANN problem, I don&#39;t need to worry about it&quot;.=C2=A0 =C2=A0I also=
<br>
imagine, reinforced by the few comments during IETF Last Call on<br>
what became 7940, that the Last Call reaction was similar.<br>
However, in that case, there _was_ a WG, the IESG reached the<br>
conclusion that the WG had sufficient membership and<br>
participation to be meaningful, and the community generally<br>
assumes that WG conclusions should stand as IETF ones if there<br>
is no meaningful and substantive dissent during Last Call.<br>
<br>
Then the IESG, in its wisdom and for reasons not announced to<br>
the IETF other than &quot;concluded work&quot; (such announcements are<br>
rarely made and I wouldn&#39;t propose to change it) closed down the<br>
WG.<br>
<br>
Then this document appears as an individual submission.=C2=A0 =C2=A0There<b=
r>
has been little evidence of wide review, especially by those<br>
with significant history of IDN involvement in the IETF.<br>
Perhaps that is in part because it shares the limited scope<br>
issues with LAGER and RFC 7940, requires a thorough<br>
understanding of that document and what it does and does not do,<br>
and, noting that the IAB just shut down its I19n Program after a<br>
long period of inactivity, there seems to be even less ability<br>
to get IETF traction on i18n issues than there was a few years<br>
ago.<br>
<br>
As I understand it, this document provides and explains a system<br>
to assist in developing and describing rules that might then be<br>
documented according to 7940.=C2=A0 Even with the latest revision, it<br>
makes some assumptions that some of us (including, given his<br>
comment, I assume Vint) question in an IETF context (even if<br>
they represent ICANN consensus and are reasonable there because<br>
the scope, conditions, and support arrangements are different).<br>
At least in principle, the IESG could have reopened LAGER,<br>
gotten review there, and then pushed this through as a document<br>
from the same WG that was responsible for 7940.=C2=A0 They didn&#39;t.<br>
<br>
But your conclusion was (out of context, but complete below)<br>
<span class=3D""><br>
&gt; There is no IDNA Working Group any more, so there is no way to<br>
&gt; say that it was not endorsed by this WG. The document is,<br>
&gt; however, intending to be an IETF consensus document.<br>
<br>
</span>Right.=C2=A0 There is no way to say that LAGER did not endorse it (o=
r<br>
would not have endorsed it had it still existed).=C2=A0 =C2=A0Likewise for<=
br>
IDNABIS.=C2=A0 AFAIK, DNSOP and for that matter and, despite it (and<br>
7940 (to pick a random example) LISP didn&#39;t consider it either.<br>
Since 7940 (last paragraph of introduction) and this document<br>
even more strongly claim that their data structures, mechanisms,<br>
and principles can be used for non-DNS identifier labels,<br>
perhaps the latter should have looked at it.=C2=A0 But none of them<br>
did although, by your logic as I read it, there is no way to<br>
assume that they would not have endorsed it had they looked and<br>
therefore their assent must be assumed.<br>
<br>
For a claim of IETF consensus on an individual submission,<br>
especially one that is the slightest bit controversial (as this<br>
clearly is, even if one believes the controversy is about<br>
process, not substantive content), I think there has to be clear<br>
evidence of adequate and competent review of document content<br>
and relationship to other work to make that consensus claim<br>
meaningful.=C2=A0 I don&#39;t think that has been demonstrated; YMMD.<br>
<br>
I also think that, if a document comes out of a WG and then one<br>
of its authors produces a individual document that suggests an<br>
extension, interpretation, or supplemental tools, we need to be<br>
extra-careful about that document and IETF consensus claims.<br>
YMMD about that too.<br>
<br>
Your response to Vint about what can be done about this was:<br>
<span class=3D""><br>
&gt; It says &quot;Informational&quot; right at the top of the document, an=
d<br>
&gt; that&#39;s the best we can do for the RFC Series.<br>
<br>
</span>But that is not &quot;the best we can do&quot;.=C2=A0 =C2=A0The IESG=
 can say<br>
&quot;insufficient evidence of IETF consensus&quot; and drop the document.<=
br>
I don&#39;t recommend that, but it is possible that others would<br>
disagree.=C2=A0 The document can be handed off to the Independent<br>
Submission Editor with recommendation for publication with the<br>
usual clear statement from that Stream about there being no<br>
consensus assessment.=C2=A0 =C2=A0Noting that all of the documents that<br>
started the &quot;variant&quot; epidemic (RFCs 3743, 4290, and, as a key<br=
>
example at least, 4713) were published in the Independent Stream<br>
and that didn&#39;t prevent them from getting community attention,<br>
there is probably little argument for the IETF Stream unless<br>
there is either clear evidence of consensus or if this document<br>
is really expected to be treated as a Standards Track supplement<br>
to 7940 independent of its official status.=C2=A0 =C2=A0Or, in principle,<b=
r>
the IESG could attach a note indicating that the document is<br>
published as a convenience and there is little or no evidence of<br>
informed IETF consensus about it.<br>
<br>
For me, it is precisely the claim that the document represents<br>
IETF consensus, or the now-demonstrated high likelihood that<br>
claim will be made, that is the problem here.=C2=A0 =C2=A0That claim is,<br=
>
at best, not demonstrated to be true and, for a document that I<br>
believe lies very close to the boundaries of IETF scope and<br>
relationship to ICANN, I think we need to be extra careful about<br>
it when it is not demonstrably true (and not just because a<br>
series of current and closed WGs haven&#39;t commented on, much less<br>
endorsed, it).<br>
<br>
=C2=A0 =C2=A0best,<br>
=C2=A0 =C2=A0 =C2=A0john<br>
<br>
<br>
=C2=A0 ---------------------------<br>
<br>
For the information of the IESG and community, Paul forwarded<br>
the Last Call announcement to the idna-update mailing list.<br>
Vint responded there (but not to the IETF list or, AFAIK, to the<br>
IESG) and Paul responded to him (but, again, not to the IETF<br>
list or AFAIK, the IESG).=C2=A0 Paul&#39;s response to Vint and, IIR, the<b=
r>
substantive part of Vint&#39;s message appear below.<br>
<br>
<br>
--On Tuesday, April 18, 2017 09:38 -0700 Paul Hoffman<br>
<span class=3D"">&lt;<a href=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@=
vpnc.org</a>&gt; wrote:<br>
<br>
&gt; On 18 Apr 2017, at 7:04, Vint Cerf wrote:<br>
&gt;<br>
&gt;&gt; if this is published, I hope it is made clear that this is<br>
&gt;&gt; not a=C2=A0 standards<br>
&gt;&gt; recommendation endorsed by the IDNA working group.<br>
&gt;<br>
&gt; It says &quot;Informational&quot; right at the top of the document, an=
d<br>
&gt; that&#39;s the best we can do for the RFC Series.<br>
&gt;<br>
&gt; There is no IDNA Working Group any more, so there is no way to<br>
&gt; say that it was not endorsed by this WG. The document is,<br>
&gt; however, intending to be an IETF consensus document.<br>
&gt;<br>
</span>&gt; --Paul Hoffman<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Ne=
w postal address:<div>Google<br><div>1875 Explorer Street, 10th Floor</div>=
<div>Reston, VA 20190</div></div></div></div>
</div>

--001a11c16cc667b0c6054d862c57--


From nobody Wed Apr 19 07:54:14 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3F129AC9; Wed, 19 Apr 2017 07:54:12 -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 JyL6cKcLQggt; Wed, 19 Apr 2017 07:54:11 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 A07FE129AC4; Wed, 19 Apr 2017 07:54:10 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id z109so17367484wrb.1; Wed, 19 Apr 2017 07:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=g5s24NlMTYgrKxKepXovDtryOUxF0WN0Cpl3Vv+C0Sk=; b=r9QUxQk52Eqp05KuZRWFW21MNJtK4PEpzAvg/ArI1OTEbC0aUYKFeLGOsF0PFcoYfB MPcIsqcm/v56uCUJTrMyxo7wg6FN4ocBMxndhqaJZaZRwogEB8KH/39ZQwBy1OmFKYSK sg972JWRhfC4pA/sAYduXa8OUjNGZpRxp4lDn4Wjq7FtVWTeFUBB0Bz6T8XLmpFfkg3L E4HdZPfvCx0mJgpCj55s67jFSAYDd2jZ5os9nigY9H+e09fvoRCj6y22JQMEPAdIrp0r cs1XVbxIRo2uV19oL3Q8MRKTH3WgFYdqqOfxgezBehcLcbh2iuvl+ySspTzQaiidzanz sCsQ==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=g5s24NlMTYgrKxKepXovDtryOUxF0WN0Cpl3Vv+C0Sk=; b=HqnWalPjklSm2N64pttEmnOqj41GnpNBTZKY+yBo3D6EqfgjTQg8lvrhhNKWNVLSlk G+vdI2KfoJKmgPfJu9iyMXFKbbSGb16kb9dfmq0SaafQI58S4P7PVXEfFZee+FGZOKnq JF/JImIhTnsl/ponNpC2fduGPlnXj0FjijxMYtJob9U6Rb9Wx+QQT+xWqkdfaOOaXN4v dQwupIkXg9DqKMdTOcxWByWAdyf9Q0NltEvM1R6C58YnPuthEktFKkO3XyKx1zWbt38K ymUdvlnvzcxbqMVN88pP7WJxXjeVmAsuc2eL/acsREABJkA//xRyMU0JbCjdT/jXOBNE 0WfQ==
X-Gm-Message-State: AN3rC/5iva/42V8/2qKWusQcmHpqjq0ZyDqAQvt8tnOp6Klp9hEhRTcs YmVByHaHU7zMLA==
X-Received: by 10.223.150.121 with SMTP id c54mr3130046wra.202.1492613649035;  Wed, 19 Apr 2017 07:54:09 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id h199sm13062217wme.4.2017.04.19.07.54.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:54:08 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
To: Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com> <20170419141841.5agsblcuiqvyxek4@Vurt.local>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
Date: Wed, 19 Apr 2017 15:54:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170419141841.5agsblcuiqvyxek4@Vurt.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S7FSrNR8PX7dI68Fz81-AQdXjtY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:54:12 -0000

Thanks

I think I have done the required Genart level of due diligence on Security.

Stewart

On 19/04/2017 15:18, Job Snijders wrote:
> On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
>>>>      Operations and Security [RFC7454].
>>>>
>>>> SB> You do not address the question of whether there are new
>>>> SB> considerations, or considerations that are of increased importance?
>>> It is my understanding that RFC 8092 "BGP Large Communities" are
>>> just like RFC 1997 "BGP Communities", but ...  larger (for lack of
>>> better words). Referencing RFC 7454 seems plenteous.
>>>
>>> So, what if there are not any additional considerations, If there
>>> were, they would've been (or are) covered in RFC 8092's security
>>> section, right?
>>>
>>> This is an Internet-Draft targetted for Informational status, I'm
>>> not sure what you expect here.
>> I was wondering if there was more scope to make mischief at a distance
>> in a less less obvious way than before.
>>
>> If everyone is happy that there is no additional risk then I am fine,
>> but seems to me the more knobs you give the mischeif maker to turn the
>> more security risks you have.
> Ah, I see now. This document does not create new knobs. RFC 8092
> definded the BGP Large Community attribute, and this internet-draft
> reflects on possible use cases, much like RFC 1998 was a companion for
> RFC 1997.
>
>>>> SB> Is there is text somewhere that discusses the integrity and
>>>> SB> synchronization of the parameters and any consequences that arise?
>>> the what now? Can you elaborate on the above?
>> So you rely on the nodes that receive these community strings to
>> interpret them in a common way. Maybe this is an already solved
>> problem, or an known risk, but what if the dictionaries get out of
>> sync?
> Yes, there is not anything novel here. How to keep a list of integers
> like UN M.49 up to date (or how to write bug-free software) is out of
> scope for this internet draft. ;-)
>
> Deploy coherent routing policy configurations on an autonomous
> system-wide level is not for this document to cover.
>
> Kind regards,
>
> Job


From nobody Wed Apr 19 07:54:45 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445C1129AD3 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:54:37 -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, RP_MATCHES_RCVD=-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 XDyY81IngU7f for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:54:24 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 F180A129AE9 for <ietf@ietf.org>; Wed, 19 Apr 2017 07:54:20 -0700 (PDT)
Received: from mbp-4.local ([IPv6:2607:fb90:2764:6f7d:802c:ffd5:77cc:b109]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v3JErtIm087632 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 19 Apr 2017 14:54:04 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2607:fb90:2764:6f7d:802c:ffd5:77cc:b109] claimed to be mbp-4.local
Subject: Re: Structure of IETF meeting weeks
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Cc: ietf@ietf.org
From: joel jaeggli <joelja@bogus.com>
Message-ID: <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
Date: Wed, 19 Apr 2017 07:53:56 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lGebj7xwOop52DPuJCim80MjecTPj0Mmq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IV6K2NXZLc1JGEvcPExtRF4i-VE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:54:37 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--lGebj7xwOop52DPuJCim80MjecTPj0Mmq
Content-Type: multipart/mixed; boundary="2B7aKejaQLKR9mcl661VOSuP5d3h9GiB1";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>,
 Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Message-ID: <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
Subject: Re: Structure of IETF meeting weeks
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
 <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
 <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
 <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
 <10890.1492007455@obiwan.sandelman.ca>
 <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
 <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
 <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
 <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
 <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
In-Reply-To: <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>

--2B7aKejaQLKR9mcl661VOSuP5d3h9GiB1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/18/17 14:34, Stephen Farrell wrote:
> Hiya,
>
> On 18/04/17 22:22, Toerless Eckert wrote:
>> For example, there is a lot of death by powerpoint in meetings that pu=
shes off
>> high bandwidth discussions ("oh, we're out of time"). AFAIK, most acti=
ve work
>> on drafts during IETF meeting week happens outside of the WG meetings.=
 I think that
>> a) was not the original plan, and b) i have not seen IAOC sending arou=
nd questionaires
>> what/how to improve the quality of the meetings in this respect.
> I agree with the criticism, but not sure I agree about surveys being
> the best next step.
>
> One suggestion I made before I exited the IESG was that we consider
> changing (or experimenting with) how the meeting week is structured,
> for example, only having formal WG sessions in the afternoons, and
> leaving the full mornings free for hackathons or informal meetings.
> (Partly, that's because I hate getting out of bed early, which sadly
> was not considered sufficient justification:-)
In my time I had tended to view the increased structural demands of side
meetings, bar bofs and what have you (isoc briefings, lunch trainings
and so on) that infill all the available time as detrimental to the
available supply of unstrctured time.

Time to meet and space work with your co-authors and collaborators is a
pretty important part of why IETF meetings have any value at all to me
as an individual contributor. You are at a rather signficant
disadvantage if you're remote, given that for me at least this is why
you come together.
> Anyway, I think it'd be good if the IESG/IAOC encouraged experiments
> in such ways of organising ourselves when loads of us do end up in
> one place for a week or so.
>
> Cheers,
> S.
>



--2B7aKejaQLKR9mcl661VOSuP5d3h9GiB1--

--lGebj7xwOop52DPuJCim80MjecTPj0Mmq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlj3egUACgkQ8AA1q7Z/VrLI9ACeI8V0SC0MF6UQKGORjztG9pck
a38Aniw/YlS7l6JwAeR/JgdAlXRHmjaB
=0N3T
-----END PGP SIGNATURE-----

--lGebj7xwOop52DPuJCim80MjecTPj0Mmq--


From nobody Wed Apr 19 07:58:14 2017
Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E60129AE3 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:58:06 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.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 hs56tM-Q35nK for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 07:58:04 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 C489C129ADE for <ietf@ietf.org>; Wed, 19 Apr 2017 07:58:03 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id r190so15345053wme.1 for <ietf@ietf.org>; Wed, 19 Apr 2017 07:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sc4106xRtU0hgDKmgSRewO1J4wd551XL6qIrTHHTK/s=; b=U1PZy+mlmDILpYfo/sB2grp+xs5NWIl9X2KV6Fv3KPus+bmjndOZwFIPrib4M2rHfU OaZOpAGNHoOVzxPJnntzJ1N+rAJ7Qov7NU9JUcKdvZ1dLLPMtErYb3VtTkWL9FyJvR6J KmoDA26/BN3Ya1oI1LfMJEzE6zbERiex2glzze8V+tXvZupUAi4h6alnGyBS2iKhxAgU xjFiffkcPmlGD8bfzcsEN+xGesahqzVgCLazf3IqdzY5oJ06RHqoh4GBAj9AkjAzaqMB Ds+oSLNCP36ENhujua9Yw4DmFM54cPT+yrS2oNk6Z7jocYHciZrA/oFVv5kzctHFI1Qq p2aQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=sc4106xRtU0hgDKmgSRewO1J4wd551XL6qIrTHHTK/s=; b=h2BQifeJeJ4oAjkpETqQQlwxU1MqTVIs29lQtw4JlfGQA+8ISBuBABvUwXAK459Rwq IviKlMrFvNYv6C2IyDSXVh7JdhfLcO6lXJdJFyXp/ZJHojgESF8o9dRJhFehaKgRlRXY bPqS2hscoTV7l92yeqtSegzkWuEwbJFlyYn5dFQYu6vR/x5/E9qovBzRS0SLtH2zeSYr TfsDRfq5lwb5+4BGYMhiFT1ydKq7plViN3k6XFq0EJEoX0yUBJZwXM2C/tMxcivjmhKU gB6szg/C88OsFSSI/nJ/DMY50Xj8qrGsr94+BYEr8r18cytmnpmY7H5XVf2V6kdxMw7h MMEg==
X-Gm-Message-State: AN3rC/5kcp6Oa5q8nVHs6eTH2iQfU8ARmVUdj4tO+U/dU7kbT7dNsnCo HI0X2mqrH1ciWw==
X-Received: by 10.28.128.197 with SMTP id b188mr17478718wmd.115.1492613882182;  Wed, 19 Apr 2017 07:58:02 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:1558:83a0:4ae5:75f7]) by smtp.gmail.com with ESMTPSA id 3sm3650231wrv.33.2017.04.19.07.58.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:58:01 -0700 (PDT)
Date: Wed, 19 Apr 2017 16:58:00 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
Message-ID: <20170419145800.nwczhjy5lzygpaqp@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com> <20170419141841.5agsblcuiqvyxek4@Vurt.local> <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MiNmL2fcT-K7W7BjpWmk8IlX8NA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:58:06 -0000

On Wed, Apr 19, 2017 at 03:54:06PM +0100, Stewart Bryant wrote:
> Thanks
> 
> I think I have done the required Genart level of due diligence on
> Security.

Much appreciated, stay tuned for an updated version which incorporates
your feedback.

Kind regards,

Job


From nobody Wed Apr 19 08:03:01 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA31129AC9 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.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 NmJtcWu4M4pz for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:02:58 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 698EA129513 for <ietf@ietf.org>; Wed, 19 Apr 2017 08:02:58 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3JF4v0G013039 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 08:04:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492614298; bh=pbfOpzCMUwZZLMTDF7IQvi8Cb4i7yEGkXwqXwKiQN2Q=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=LHb/cygL+Dw6NgLT0o5s4raCjYqDxrT8jhUPB4G4ubwnEBGaEF4+TIKVaqz2W2sD4 YGsnKXXmztt4vA12/F6hrHqXpbPLTE1dFybJ8rJXVs6tXWgzSuhV1H+8GKFg8GdU/C Qdg9QNKVvB/IyhKhRTgHC314DKpjaaht8Z5K/I5U=
Subject: Re: Structure of IETF meeting weeks
To: joel jaeggli <joelja@bogus.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
Date: Wed, 19 Apr 2017 08:02:31 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kQ9UZZbtQsE3M_Ts4kCwfmiFsBI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:02:59 -0000

On 4/19/2017 7:53 AM, joel jaeggli wrote:
> Time to meet and space work with your co-authors and collaborators is a
> pretty important part of why IETF meetings have any value at all to me
> as an individual contributor.

If there is serious interest in having more unstructured time available, 
remove less-productive wg sessions and reconsider carefully each of the 
ewstablished 'extra-curricular' time slots that are scheduled -- my own 
favorite target is Bits-n-Bites -- for possible elimination.

There is relatively little filtering on working group slot requests, and 
worse there's no real aid for working group chairs, to help them plan 
and manage sessions more effectively.

We periodically have public discussions about this latter issue and 
there are documents that say the right things. However chairs often have 
little experience with such 'project' management and few have -- or 
should be expected to have -- natural talents in that arena.

Professional project planning and management assistance for chairs, and 
careful vetting of wg progress as a filter for wg time requests, would 
produce fewer and shorter sessions and better use of time.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 19 08:03:49 2017
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8EE129AE5; Wed, 19 Apr 2017 08:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_50=0.8] 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 N60Jm7-BVOHW; Wed, 19 Apr 2017 08:03:45 -0700 (PDT)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:1200:706b:158a:682d:9e9b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 65273129AE8; Wed, 19 Apr 2017 08:03:45 -0700 (PDT)
To: ietf@ietf.org, ietf-announce@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: Appointment to the Internet Society Board of Trustees
Message-ID: <0af97746-4b9f-5454-bba9-ee565eb31ab2@iab.org>
Date: Wed, 19 Apr 2017 08:03:45 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
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/ietf/UlR-bBlCrnP7poWWspwN-6Q81BQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:03:47 -0000

As set out in RFC 3677, the IAB is responsible for selecting a certain 
number of the Trustees who serve on the Board of the Internet Society.

In fulfillment of that responsibility, we are happy to announce that 
Sean Turner has been selected for a second three year term, to begin at 
ISOC’s annual general meeting in June.

The IAB had a very strong set of candidates this year, and we would like 
to express our appreciation to each of them for their willingness to 
serve.  We look forward to their continued engagement with the Internet 
Society and the IETF.

Best regards,

Ted Hardie
On behalf of the IAB


From nobody Wed Apr 19 08:06:40 2017
Return-Path: <buhrmi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB997129ADD for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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=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 bmL0AR5aTtBH for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:06:36 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 0CCCE129AD7 for <ietf@ietf.org>; Wed, 19 Apr 2017 08:06:36 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id r190so25192775wme.1 for <ietf@ietf.org>; Wed, 19 Apr 2017 08:06:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QtJTpCuBvETqQXF+KecDKp7tMCDldgb2QW9gHIKH1VM=; b=IKIBt5KQYIGkuQ+FW4V2zkz0Tf3VOLZdjb8vufPwmIaIN4NA9OifOPLMm8AscNxtVS 8YblSOzSSYFYn9gFQXzBEGrWiIXmGZvPfAXv6zVWfN/KyVbMYoPtdQ4yYioxsDHd1WgN UAZTVO0JItMv7JbLz4MmnAGOq5qPCFYikftOW6Qt91auJ/PBkx3xHGSkl0/Hkkz15CVW glHk1mAoNRB+01HXwXvgmxulxK71mzINL5Dd/gHy9oUyw1jo9+R+ynlrzhOh7dkkQMOK sGCRbNDmE5yh405Jztm3srj7FtoETR+qR/XltoJKtb48Wlf9ETwVwKrcEwWTju60ojw6 Mhmw==
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=QtJTpCuBvETqQXF+KecDKp7tMCDldgb2QW9gHIKH1VM=; b=XaFfeYB2q+uHJ8rFaY7yUoXJ5heepzG7d7F3eTsS4Y3eLT8fQRhUVWos31F1A1F4Uc d2IG1I49ifFcXlEjkWWXAniBDQHkjTszfLJk3l78kpH9TIPT08Mn+eiKLhz6hbcMldfY e2d17eqjuaEYXt2PvNvPMD8ErDf5A/mQKUp44efP0c7Z12pcUE2sBBLT4b7zAoYwYFzN ScKPXR4mIPcXIgYKjlI6SNns//9JsddNOdH0zmjzBZhRFh6JOqA3C3jvLSaeOJ/jIrqm 9cSL/xRrISZdfozjcHKi/ZlgIsY6/d6XaPK1TXgR3I8XWFAoEME19Y0cLb+AHktN/SdF mZhQ==
X-Gm-Message-State: AN3rC/53j5/qdxlqfuDTnniMS0HsUW6JNaoJQN9heZSCssJXGfdPrL4d PmR++Ti1UzwnzuqSujVHAdDX5RNV3Q==
X-Received: by 10.28.133.70 with SMTP id h67mr2684147wmd.136.1492614394592; Wed, 19 Apr 2017 08:06:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.176.4 with HTTP; Wed, 19 Apr 2017 08:06:33 -0700 (PDT)
Received: by 10.28.176.4 with HTTP; Wed, 19 Apr 2017 08:06:33 -0700 (PDT)
In-Reply-To: <CANhkrbTHiXs9TsU3wkcsmjHErB2CYgKK6uhh3gdeyqX8tjzw9g@mail.gmail.com>
References: <0af97746-4b9f-5454-bba9-ee565eb31ab2@iab.org> <CANhkrbTHiXs9TsU3wkcsmjHErB2CYgKK6uhh3gdeyqX8tjzw9g@mail.gmail.com>
From: Stefan Buhrmester <buhrmi@gmail.com>
Date: Thu, 20 Apr 2017 00:06:33 +0900
Message-ID: <CANhkrbS0gtbsoDrLG6AvLg7+8Ze9VzDUGRpm4=mSEGj7mYbp0g@mail.gmail.com>
Subject: Re: Appointment to the Internet Society Board of Trustees
To: IAB Chair <iab-chair@iab.org>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114431f8c6c4f6054d865e88
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZSujTYBxvIBT9fMnz492Bd47wfM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:06:39 -0000

--001a114431f8c6c4f6054d865e88
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Congratulations

On Apr 20, 2017 12:04 AM, "IAB Chair" <iab-chair@iab.org> wrote:

As set out in RFC 3677, the IAB is responsible for selecting a certain
number of the Trustees who serve on the Board of the Internet Society.

In fulfillment of that responsibility, we are happy to announce that Sean
Turner has been selected for a second three year term, to begin at ISOC=E2=
=80=99s
annual general meeting in June.

The IAB had a very strong set of candidates this year, and we would like to
express our appreciation to each of them for their willingness to serve.
We look forward to their continued engagement with the Internet Society and
the IETF.

Best regards,

Ted Hardie
On behalf of the IAB

--001a114431f8c6c4f6054d865e88
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Congratulations</div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Apr 20, 2017 12:04 AM, &quot;IAB Chair&quot; &lt;<=
a href=3D"mailto:iab-chair@iab.org">iab-chair@iab.org</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">As set out in RFC 3677, the IAB =
is responsible for selecting a certain number of the Trustees who serve on =
the Board of the Internet Society.<br>
<br>
In fulfillment of that responsibility, we are happy to announce that Sean T=
urner has been selected for a second three year term, to begin at ISOC=E2=
=80=99s annual general meeting in June.<br>
<br>
The IAB had a very strong set of candidates this year, and we would like to=
 express our appreciation to each of them for their willingness to serve.=
=C2=A0 We look forward to their continued engagement with the Internet Soci=
ety and the IETF.<br>
<br>
Best regards,<br>
<br>
Ted Hardie<br>
On behalf of the IAB<br>
<br>
</blockquote></div><br></div>

--001a114431f8c6c4f6054d865e88--


From nobody Wed Apr 19 08:10:37 2017
Return-Path: <kaliloudama@yahoo.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEB9A129B04 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.085
X-Spam-Level: 
X-Spam-Status: No, score=-1.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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=yahoo.fr
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 XYLxgXoF6_BA for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:10:31 -0700 (PDT)
Received: from nm29-vm3.bullet.mail.ir2.yahoo.com (nm29-vm3.bullet.mail.ir2.yahoo.com [212.82.97.72]) (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 34E24129AFE for <ietf@ietf.org>; Wed, 19 Apr 2017 08:10:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s2048; t=1492614628; bh=9HTuBKbK05uB5njNO4wnP5wdxFYTZuwx1/p2bkdXSKE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=fhS6FwABOTQG+oL5jm+J5rBpgicE5TDAB5V7/akZApajBMOEFVW8fwo/K+CC4OjJ1qEcsV6AnTCjl61qPxPOOKLa150lPWsSbI5nG3HsTN5ZHidHuxdp1LjO/ECMs5kw+mXKyFXbaTDHDsdHRz9yBLbADvHqB1nj0jrFBtECMUbU9AH50fTGo5VgKmAynJd7nk0t69XoQP93x3V2egwkogvgqwAJz+ZGFDFZmKSLAkF7pBe11qdxgjH9AZBYcnwQ07JpwvJiHuLPbAAud/JnweUsKJi0SFmW7wRLjLJ6i87lbOlTt4+uvSQ+K2tY1wEvJ4+EI4Ba+ipD48Z1OatSpg==
Received: from [212.82.98.60] by nm29.bullet.mail.ir2.yahoo.com with NNFMP; 19 Apr 2017 15:10:28 -0000
Received: from [212.82.98.110] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 19 Apr 2017 15:10:28 -0000
Received: from [127.0.0.1] by omp1047.mail.ir2.yahoo.com with NNFMP; 19 Apr 2017 15:10:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 138328.84307.bm@omp1047.mail.ir2.yahoo.com
X-YMail-OSG: .A46TRcVM1mLBlMzioaHL2ruTp0fxwi4IdsKw7xdmyUlo6jQqhruovhFHL5AGqQ Nl.KuU8mRxEiW4rt.qCSLm8U1I0rqXFJ4ePEiv5hd3L3NDWffcwkQlhbtKEE__X6Qm7NyQtUeSe8 ykfrEfL_87lKFg43qECMraJj2hh04eBZvx3EYBMWkwEvnbXGgzrdb_aZs0MNPB5QdecqYKaxILZL NH69SaXRT5ivNQUclqzW950NlxyE.dTvbhNwNsWYa6eiTaGkh.mHvMwJJ9nRezNRuY4XheYmn1KE CcNXFCa0jihgj3.HaH_pQXIC7R.VdXdEQkuCE_AIj0wiF4GiqRQBcFx1_JTmZMA3.FlGGSC1OFWi 5J9CEpRLTYHZ2jJIUFRCPeHB0obZJqIAxjQ2pvzUoTNlrBhzbcHxkD4rwifiheWR22sMrykuaT13 tHJs3utLle6IyDJFE2KtJ4LI2owT3R9CBtrZ2SFBYcPJhnPgPo8GYPGXUo_jtKJA15tP6d.guwwH aehBnrwdIhmIF4IAf6hNBiU4HqxbNiS9EEJI.4KoDvJw8pN9uFYhxRy5SQ9B7H8SF8Gc1zIomZTI XhRiX_33KjGV.TiYzgY52fty_9gGVkqP8lvLpd00xD0rT772KS.FQDXrSwMBz.bajC3ydpwcEhwQ atShCdYue1Q3KGaJARMDinVw3B3dQvYP2298Ifh_enynJkPmMU1SY6rhHD_Ysv3w4htQsSrKi8mT l7lqlJk6ToRcUgCpY0_EX01kMrZWvKWhXR7FN590yVgo_rSV_.9Q-
Received: from jws700040.mail.ir2.yahoo.com by sendmailws103.mail.ir2.yahoo.com; Wed, 19 Apr 2017 15:10:27 +0000; 1492614627.716
Date: Wed, 19 Apr 2017 15:10:27 +0000 (UTC)
From: Kalilou Dama <kaliloudama@yahoo.fr>
Reply-To: Kalilou Dama <kaliloudama@yahoo.fr>
To: Stefan Buhrmester <buhrmi@gmail.com>, IAB Chair <iab-chair@iab.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <3266635.5243721.1492614627463@mail.yahoo.com>
In-Reply-To: <CANhkrbS0gtbsoDrLG6AvLg7+8Ze9VzDUGRpm4=mSEGj7mYbp0g@mail.gmail.com>
References: <0af97746-4b9f-5454-bba9-ee565eb31ab2@iab.org> <CANhkrbTHiXs9TsU3wkcsmjHErB2CYgKK6uhh3gdeyqX8tjzw9g@mail.gmail.com> <CANhkrbS0gtbsoDrLG6AvLg7+8Ze9VzDUGRpm4=mSEGj7mYbp0g@mail.gmail.com>
Subject: Re: Appointment to the Internet Society Board of Trustees
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_5243720_914198106.1492614627463"
X-Mailer: WebService/1.1.9408 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kf504LHV5StobCfJDfk21qlsy3Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:10:33 -0000

------=_Part_5243720_914198106.1492614627463
Content-Type: multipart/alternative; 
	boundary="----=_Part_5243719_1645556588.1492614627462"

------=_Part_5243719_1645556588.1492614627462
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Congrats Sean Turner.All the best
=C2=A0kalilou DAMA
Consultant
Lawyer & Business Advisor


phone +223 66 74 88 07
03 BP 237 Bamako - MALI=20

    Le Mercredi 19 avril 2017 16h07, Stefan Buhrmester <buhrmi@gmail.com> a=
 =C3=A9crit :
=20

 Congratulations
On Apr 20, 2017 12:04 AM, "IAB Chair" <iab-chair@iab.org> wrote:

As set out in RFC 3677, the IAB is responsible for selecting a certain numb=
er of the Trustees who serve on the Board of the Internet Society.

In fulfillment of that responsibility, we are happy to announce that Sean T=
urner has been selected for a second three year term, to begin at ISOC=E2=
=80=99s annual general meeting in June.

The IAB had a very strong set of candidates this year, and we would like to=
 express our appreciation to each of them for their willingness to serve.=
=C2=A0 We look forward to their continued engagement with the Internet Soci=
ety and the IETF.

Best regards,

Ted Hardie
On behalf of the IAB





  =20
------=_Part_5243719_1645556588.1492614627462
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font=
-size:16px"><div>Congrats Sean Turner.</div><div>All the best<br></div><div=
><span></span></div><div>&nbsp;</div><div class=3D"signature" id=3D"yui_3_1=
6_0_ym19_1_1492614155029_11414">kalilou DAMA<br>Consultant<br>Lawyer &amp; =
Business Advisor<br><img class=3D"ymail-preserve-class inline-image-guid-53=
65bcaa-51fe-96de-8969-89f973704881 rte-inline-saved-image" src=3D"cid:cc011=
d15-4009-1bd0-c955-2fa14738b463@yahoo.com" data-id=3D"inline-image-guid-536=
5bcaa-51fe-96de-8969-89f973704881" alt=3D"Image en ligne" style=3D"width:10=
0%;max-width:85px;max-height:65px;"><br><br>phone +223 66 74 88 07<br>03 BP=
 237 Bamako - MALI</div> <div class=3D"qtdSeparateBR"><br><br></div><div cl=
ass=3D"yahoo_quoted" style=3D"display: block;"> <div style=3D"font-family: =
Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16p=
x;"> <div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, A=
rial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir=3D"ltr"><font =
size=3D"2" face=3D"Arial"> Le Mercredi 19 avril 2017 16h07, Stefan Buhrmest=
er &lt;buhrmi@gmail.com&gt; a =C3=A9crit :<br></font></div>  <br><br> <div =
class=3D"y_msg_container"><div id=3D"yiv0918621271"><div>Congratulations</d=
iv><div class=3D"yiv0918621271gmail_extra"><br><div class=3D"yiv0918621271g=
mail_quote">On Apr 20, 2017 12:04 AM, "IAB Chair" &lt;<a rel=3D"nofollow" y=
mailto=3D"mailto:iab-chair@iab.org" target=3D"_blank" href=3D"mailto:iab-ch=
air@iab.org">iab-chair@iab.org</a>&gt; wrote:<br><blockquote class=3D"yiv09=
18621271quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;paddin=
g-left:1ex;">As set out in RFC 3677, the IAB is responsible for selecting a=
 certain number of the Trustees who serve on the Board of the Internet Soci=
ety.<br>
<br>
In fulfillment of that responsibility, we are happy to announce that Sean T=
urner has been selected for a second three year term, to begin at ISOC=E2=
=80=99s annual general meeting in June.<br>
<br>
The IAB had a very strong set of candidates this year, and we would like to=
 express our appreciation to each of them for their willingness to serve.&n=
bsp; We look forward to their continued engagement with the Internet Societ=
y and the IETF.<br>
<br>
Best regards,<br>
<br>
Ted Hardie<br>
On behalf of the IAB<br>
<br>
</blockquote></div><br></div></div><br><br></div>  </div> </div>  </div></d=
iv></body></html>
------=_Part_5243719_1645556588.1492614627462--

------=_Part_5243720_914198106.1492614627463
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="datauri-file.png"
Content-ID: <cc011d15-4009-1bd0-c955-2fa14738b463@yahoo.com>

iVBORw0KGgoAAAANSUhEUgAAAFUAAABBCAYAAACgsujXAAAgAElEQVR4nOzb1Y9lZ5b3+fc/as07
1d1V5aTAw8zMzHHOiRPMHCeYmZkyIjKSycl22plmSJeZIU1pu+zqqvrORXXPTfpypJFGs6R9v/XR
b+1naenZ/4v/v/4fr//1//YL/H+x/m9UUcVJSuInKYmcQhAqoMR3imJPAYWuk5T6ilCkJIhipQjC
JRhaFGi6hKg7Rdj65biGdBg6lWgaJEjLipBlClFXFGFrlWBrFaGpL0TXKsY6YiO+miGxFCK2bKJs
Q0toqYTel8M8+fE7Hj95h/6X/OTOuag/n2HoQTPDX4bJfxxm4I0YDedjRCfiJMcjRAa9RPoDhCZs
hGbMtB0mePuL5/nhpx+59unzNJ9pIDsXIjxnJTqnIrWqIbymJLGmJrUpJnEkoueVAHc+36P+bIDE
uoLMjo7Ujo7MaSs9t8ppfTZIfF9K/KyW8ls2ctftpE4H6bie5fyX25z+aIpXn7zJua9Pc+W707+D
2vxnNIMnUOaPU5o8QbG3iGJvASW+Qoo8/wKWREpRZEvRtclQd8nRd8txD2txDekwdivR1AlRpAtQ
lhegry3C1F6ArqkYQ0sxxjYhtg4N0SkvoTUv6XUniVUjoQ0xRx8P8Pgfz3P9iyGyZzQk1+3kr/ex
8cZFJl8eoP6Sg6oDJ55RM4EhH4kxP75uJ6FBD7ElI4EFDX33kyw+auXWVzeZffGQis1G4nMewlNq
YlMy4ksaIst64ssqyvfkpM8o6H05RP65IJFVLeVnTGTPqMnsG0gfGEmcNlJ2qCFzRk3dbS/V97xU
33VTdS3C8PONfPXkc97+5nW+/OFTXvvqERt/WX8atTh0HGn9MeTNxylNn6I4UIzAX4AgUIgwVESJ
p4AS7wlk5YWIawtRtkmx9KrxjRjwDBuw9GjQ1ZVgqixGmT2BtqYQbdMpTPki7H0C/P0qAtMa3JNS
PNM6Uis2kmsmQpsl3Phkitf+ukjNZR3BBTmhCQ2BcSfR8SCZ2QjZeQv+QSPWJguuZge+ZhfWahue
Zj/eDg+BITNli24qN2L0n+2m70wvXacryE5ZqJ43UjavoGzdQPmKndSckcodM4kNLdkzBiouukht
GKi5rCd5KCexo6ThvJfa/QC5fQsNF6N03U/T/mKcjgcJOl9KM/pGPZ99/x7fffUdf/vhN/7ru79z
8NrR06il0QJKoscQJE4gSpxCECpEGCz61xMqRhwqoTRwEkHyBKKaU2g7xLgGtbgHdfhHbbiH7KjL
S1HFChBFCyiNnKA0cZLwnIyyFSNli2bOvbbK0I1qfHOlhOd0JNeNhNekbL7SzeKL9SS39FRsWohO
6AgNmPF3mfC12bBVWjGWOdCFHeh8DjQuN2qXC7XTg87pxRRwY4q78dWHyI1GqJgJUr0apGzGSuWq
mcSagqoNK/XLHsomHETHrcSXHGR3HVQceqnaj5LY0hNdVxDdlFJ5xkD2tIWyHQN159y0X69h6Pk8
vddq6blWzfg7Lbz047M8/vZb/vHdP/jk2y+5/9GDp1EFkZOIY4WIogUIIycQRgsQR4uRhEqQhIVI
QkLE4QLE6eMoGoqw5GW4B1XYBhR4Rq24+2zI48WIgoUIo8XI4wJUlSKCA3Kq5uzU7Dh5/PN73P5s
k9hhMcFZFclVC4k1GbkNI7klLRULOpJDWjyNWmzlBgxRC1q/HZXLidJhRWWzoTI7UBldqIwOlCYn
aosDjc2JzunE6HXjSHnxNfgJdNuIjRlJLBnJbGhJz9qIj9jJzfhIjTsIj1iJLGmoOYzSer6O5IaD
4JyaxKqOxLaSxKaW2KKBzKGR5itpzjy6wd4bF+g+28Tg/Wb2P1vkix++4u/f/ZM3v36P97/98mnU
E7rjaOIC1IkixOETlIZOIowUIo2WIo8KUMVE6LIStLUCjG0SPP1qXAMyzL1CbH0KjI1SZKlSZMkS
VIlS9FVyyoY91M/5yE04SMxqGLyQYuBSjMpDNTWbLmo3XeRWdaRmVCRGlfhblOhicpQuAwqbBYXF
jNJsRWWyojJaUBksKPRWVHoHKq0DjcGJxuhEbbKjtTgwWJ0YnE50Xgf2tJ3EsI3EkoGKNQ+ZKSfl
MxGa16oon/JQueQiu2Kkdi9E07ks2V0nwQUVvkkp8Q0lqU01mSUvlQc+Gi+EWbp7hgdfP2bvxStM
3Bhl8YUJHn3yiL9/+09+/uFX/vbDP59GVbok2DIyTGkBqtgpxKECSgKnEEUKUSUFaFNCjFUKLG1q
PP0GAiN6bH1iNB1FmNuFmKqEKNMlyMuK0NWI8I/raJyP0DDtIzluombLwtztWtr3bTRvm2ndtVA9
r6VsUE28W481p0ThliMza5AZ9MgMWhR6Iwq9EZXOiE5nQa8zYzLYsVr8eFxJQr4sAXcKryuGwxbA
bvditjnQ250Y3E5cVQ4SEwZy8w6yo0F27hyydecMtStxylfMJOcNpBfsNBzGyB04iO0ZcM9I8S2I
iG5JaTxIsHB/nPzFJsauznLznZe4/ehtjl69xfaDffZe2uH9Lz7ii6+/5I0PXn8aVeUXIfcUIfMU
IPGcQuQ9iSBwkuLQcSTxArQZIcY6Jc5+M+4hI74hDea8GHlTIbo6Ia4GFa3zTbSvN5I8raDqip7a
WQ+5ITOZOSNdV+1svtLC/J0sjQcGslMyHDVCzHE5Wo8UqUmBSKdCqlUi1yhRatTodQbMRgM2gxGP
yUbY6SPpj1Eeq6C5qpuuxnHa64Zore6mLl1HLlpGPOjH7/fg9Dpx+JxEmjyUj7vIjoa58OKznH94
ldatJOk5O4FRI6FRI9XbfqqP3CQPrATm9DhHxISWlIQXrHSea6blXAX1Z3K0n66j/6ibxesTvPH5
a7z08V3+8tlbvPrhy4xdG3oatdDxB4otf6LA8EdOqP+TQssxpIEiJJEihLECpGVF6Juk2Po0WHsV
eAYVmLskqBtLUVeW4GhXMX6jjZHLzcRmlERGVZQP28kM2UiOGggOCylbFtF71kXnjoNwnwhTVoLK
oUCskyJUSxApZUiVctQqJSatCrdBi9+sJ2g2ErVaSXl8ZPwxKmPldNUNMdS9xkDHEr2NI+Sr2mnN
VFCfjFGdDFGeDpHNpAjnklROJ6iaDVO/WEv9RjW5VR9lMw6S0xYqFz3Ub3moOXSTWHPiG9XjzMuI
TduILvkJTFpI77moOReiaStF124NsxeH+fDTD/ntyW/c/sst1p9bYvJW/mlUefQZjun/jT+p/o0/
Kf+dAv0xlP5S5KFiZJEC5KkidPVijJ1STN1S3ANKTD0i9E1SrDV6HG1KjG0CXK0Kkp1m0t0uUnk7
kU4j/nYFrjYRNUsa2jZMVC3pSC0oMWdEiPRCSlViBHIxEoUMtUqBVaPErVPgMygIGFUEDWrCJh0J
q5W0M0BFKEtX7SizI5eYn7jGUMcy+ZpeOrM1tJWV0ZwO05CL0tbeSP/ULt0b07Ts1FExl2TrhXnW
7/dTs+Gn5byftt0ymtaD5LateMa0BCaUuHvkxMfsVG2kCYwa6L1cT9vpCpqWk3TvNNC+18jU5XGu
vHyJ7RcW2Xxhit1XZ59G/U/5/+YPkv+D/5D+gWdU/4HEcQqlt5hCwzOUWI4j9RWhzpWgbRZg6pLh
GdBg6ZJibtTQOt+Ao16FLifCUaPA36rC06jC36wl2KbG2yaiaspAy6oFR18hmTU587cbMcWUCFRC
BHIRYqkYuUyKQSXDrZUR1MsJGhSEDEpCeiURg5qk0UjW5qE2lKW3doy54YusTt9hduiIoaZxussb
6Exl6cikaKtM0tFUzZlz93jp7R8Z399m4lwPN946w+K1PpoPymm5mKBlP0PlqoPKXTPhKS2OQQn+
KQmpJRP1+xmCEwbGLnWS32xgYLeJ8w8OGTjqpXmvjpbtesaudLDz3CQ7D6efRi1QPcO/C/83f5T8
OwXaYwjNBRxT/JETymMU6U4gtJ1AkynG0CTA3qvCM6zHkldibBXj6JRjbJVialFhrFPgbtOTGPSR
G4sS7NLj75IR7JPhGymh4bSd5LQUd4MSsVmIUCFGIBUgk4rQKsSYVSJcGgkBrZywTklYryKiUxPT
aUgZ9WQtdur9Mboz7Yy1LTI3sM9c7w5jjSP0VbbSV15HX0UNPTU1dDfUsri4zndf/Z3DK3donK1j
bHeQzaurnL63z8zVEZp3klRtquk9F2TlxiD+QR2eSQmhRQ2Vh27KNp0kx+1UTYW49uA8/BXO3D2i
ej1L3UqO/LkW5m8Ns3p/5PdQ/8Qfiv+NPwn/wAnZnzkuP8YJ9TGKLScROk4hcp1EkxVibJHgGzYQ
mrTiGtDj6JZjzYvxT2tIzDlw5W14ux0Eeu24OsxY6uR425Qkx53UbQWpWrHiaClF4itGqBUhlIsQ
S0UopSIMMhF2lRifRkJAIyWkVRDRq4nptSQMOjImI5U2G/UeP62hMvoyLUw0DjLZOMRYbZ7h6jaG
a9oYbehkpCXPQHMnIyNTvPPml7z56HNqRhqoGozTNVPDzM4QMwf9NM7HqF91U73goG+vnmCvnuCo
FveQgsSqiYp9F/EpB/ULSd55/w2++OJbZq6sULVaQd1qFZPX55i+s8Ds3d85qP5d8H/yh6I/cFxy
DKNPgSetxZKQoQwWo4icQho5jqZagKVbRnjcSGLWga/fgLPVgKvTiKtHQ6jHQmooRGTUjTuvwd6q
xNulJjpiYO/2Mi+/9yxVcyYsdUKkdjFClQiBVIBULEIlEWGQCHEqRPjV/4MqJ6pXkzTqyVrN5Gw2
al1emr0h2gNxeuM5RsobGK1qZbiqlYmaViYbO5lu72e6c4DJ7j7Gxsa49uwD3v/0J9pmuqgZCVMz
EqBy2Ed2yEHdopP200GSkyZ8PRqCfVriI0aSYzZCIwZCUxpC404q5xOMnx9l5OIEtWt11K3W07mV
5+jNF3nhk3dYf3HzadQS5x85pv8Pjmn/A6mjAKWrkCLDM5zQHkfoKkARL0JTJ8DWJyc0biK16CM1
6yfU7yEy4CUx6qNqNkrjWoiqTQ81GxFa9lN071eydHOAL77+kNXLecJDYkxVQmTGEoQKAWJJKQqx
ALWwFJO4BLdcgE8pxKcSE1BJiWgVJPU6shYzNW4fzaE0nbEq8vEKBlJVjOUamaxpY6K2jZn6Vmaa
2plpyzPT0ctMTz9TEwPsHh5y77X3aJ/PE+9xEeu3Ee03EezVkJo10HIUIjnnwdtvI9hnJtCtItqv
JTJsIjHtJjLhJzrlpXKlgpqVamqWczRutTB4YYnPH/8GT+DeB689jWpsfAZ17Z+QZf9IkeOPnNA8
w5+Vz/CM6jgntScRuotRV0uw96kJjNvouFzP+MMOWs7naNlvpGu/m679OoafzXHu3TFe++Q6X3/1
CR98+xo3Pl9l41YnmRklgWEh3tYSpOYiRIpSpNJSVOJi9KJC7NISPLJS/PJSfEoRAYWEsFpOXKuh
zGSkzhOis6yZ/up+hqrzjFZ2M1mTZ7Yhz1xDB3MNrcw1tTHb1slsZ565vl7mJ3vZ2Jnj9NV9uuZb
ifW7CA1Y8PVp8fQocA9Iqdj0Epww4R4y4es3EejVU7saIzbpITrhJzEdIrPkp3w+SdVylqq1cpp2
Oxm9vs9fv/0nfAs///C3p1E19SdQ1P4Hyqr/RBE9ToH+GU6ZjiOPlCKLFiGKFOJo1OAeMpCey/DS
p6/ywo9XOfhiiec/f8Dzf3mV3Rf3WHt9hM9+u88///o5/PpX3v72Lt1XoiQWFYTHJIRHxKSG1Ugt
xUjlJSglRWglhZglhTikpbhlpfjlQgIKESGFhJBaTlinIWEyUedP0FPRxXDjOOOtM0w0TTDVNMRs
Yx+zDW3MNbQw19jKXFsHC93dzPd2szg1wOrmFNtHC/QvtZEY9hEcNhAY0OIbVBGeUVGx5SQ4riM8
7SCzECc7EyY9E8U34ME/5CY27aHpdIbGnToq1nJUbuRoPp2n9+ISn3/zLT989xt33n74NKqppgBj
VQGaspMUGv/ISeVxiizH0VQU4emX4OqXEh03kN12MHQ3z8PPX+Gdx+/y/c9fwZN/whP45McvuPjN
Fp/99ib/+PFXHn3+AkvPdVKx5SI0o8DTL8LRIUCTOoVEW4xMXoJaUoRRWoRZWoRdUoxLWopPLiQg
FxFUiAmqZEQ0StImPc2BKH25Dsbqx5htGme+ZYSF5l4W6jpZrG9huaGZpaYWVjo6We7uYbmvm4WJ
Hla3Z9m/eMTEzgTZGR+5RT+VCz5SU2bSiwaq1uyUTVuoXo3Qd7GexKQP94ATd7+TwFCQ2FSMitU0
Ddu11G430XmujZ5z/dRsdHPjw1tceecqh29vPY2qDhdhTSkwxuSU2E4gi5WgqilG01SEtUNC5ayH
ujUv7WcjXPpylVd/eZGPf/2B354A3wE/wqufvcraGwMsvN7M/CttVF224V+V4Z8WERqR4O8T4OkU
YUwKkKlLkMuK0UiKMIoLMYkKsYn/heqVC/HLRfiVEsIqKUmNgpxJR7XDQV0gRXuynqFMHXMVNazV
1rBV18huQwM7zQ1stjSx2dHGRncHW4MdbEy0srI0zOGlq6xf3KVu3k/too/qeTeJUR3JSS3ZKT25
WTuLt0YZPOzF22PBM2AjOV1B08YQzZv9VK3laN5voO9GL6999hyvvvcG+cNRJm8P8OyHK7z5eP93
kppQ4krZcKXsyCISLO1KvBNK7KNS7D1yfHkNiSkH9ZsxNl+b5PnH9/ngxy9476fPeevrj7n5+n06
D7rILcaIbRgJb8mJr0qJzcmJTokJjYvwDwrwdAnQxYTIlMUoZUXopIX/jVqETVKCWyrAKxPhl4kI
KSXEVHLiGhVRrYaY3kDGZKXCaqfa7qDD52EwHmAqk2StPsduay27bXXsttex11XHXl8dp0cb2Jzq
YHdnmTNXj2iZTVM5aaR8xkRySkvZnJbMpInUuJOWzTpq5isJjzhJTPpp3xtg/fnzrN7doXGrip5L
jdz+4IDffv6Gz376hPkXR5m50s7qg05m7zU+jWpPaDGHtOjDenRZJ+mxOnqPhsjMl2Hv0WDrlGNp
V+MesjD+fDdLr00z9fwUSy/OM3xxgpa1PMmpONEJG5E5DbElJbFlOfFlMdEFEeEZCdERJeleE464
GoWyFJWsBI24CL2oCLO4GLu0BJdUgEcmxCcTEVJICavkBJUyomoV5SYTzU4HXV4nXV4n7W4nHV47
nX4n/XE/K7VZ9loqOWjLcaargsN8joP+ak6PNbC91MnRuWUmt/PUz7mpWXJRteqics1KZt5Gdj5A
ei5Eas5Lat5N2VyAyuUU3Qe19J0pp30nRMteiPGrjSzc7mPl1VGmXmxh+nIj7/64z41Pxp5GtZXp
cZfZsCRsVA3lOXzhBsP7YyT7I1ia5bj7VbgG9HjHrVTvJ6g7SlF9VEbVYZLqnXIqVytILXhIzjtJ
LOiJLygoW1HTcRBk8dl2li52UtFppaLSRdhvQacUopIUoxYXoReXYBGX/OubKivFLRPilYsJKqQE
5BKCSillOjX1VhOdPheDsQCTZRGmEkEGfVb6PSbGwk5WK+LsN2W51F3NpZ4ajrqr2WyrYLm9gql8
BYsznUyvd5JfTTB2WE3XdpCm9QBVax6yC27KF73kFiKkZwNkF1zUrXhoXk8xciHN9VenOXi+l/7z
GVr3o7Tt5GjYTNJ3lOPWp9Nc/rLvaVRP2ki4yoMz58DXHiE7UY6zzYCjXYu9W4lzWItr3IRrzEZg
yk1sPkTlZpKa3RgVW1HKliIkllwkVgJE1yyU75nYf62Pbx5/yK/f/cTB2V4yZUriDjUhuwGzWohG
UohWVIhRXIxVKsAhE+CSCXHLxPgVMoIKKT65BK9cik8uIyhXktTrqXTYaPS76Yn46PTYabVo6XOa
mAzb2atPcnOohftTPTw/3cfVsW4ujuY5PdLBXF8tgwMZrt1c4ptv3mX3Xgf5oyjNu0Ey03ayMy4q
Ft3kFsxk5w1ULbtoW0uxdLaK9z+5xlffn+ONT88ydKGJxu0Ezetheo4ybL6Sp+G8/2lUR5kGdUCE
NFSKpl6GJa/E3qfEM6jCOaDEPqjFNWTEN2oiMm0jteQjveCjYi1A54UU7ZfiVOz6qTxw0nwhRstV
P2Ovp3npyS7f/fyImekciVAJCWsxfl0xdlUpOkkBWlEBJkkxFknpf6OKcMsk+OQyAjI5dokUQ6kQ
bbEAfYkYj1pNbdhHfdRDymIkbTSQ0Sip1qnIOwysVEW5PtrO+4crPNqZ47nFEe7MD/Hcxjg3N8fY
XWrhozdfgJ/hvY9fZP5KLTUrLsomLZRN6UjPaCmbVpKe0VK77KdnM8KF2x189OEdHr1/hk+/eZkz
D9dp2UrSvhGnaStM/kya2KL1d+bUtABVeQHGRgGOXjmuAQX+YQWBYQW+IQXeMRWuYQUVWy4aLvqo
ve6k64UoQ3dTrH5Rx9Ufe5l/sZaO227e/PYGH339HLt/6WD0/RCbn2SobNNRFhCTcQjwKQuwSksw
SoswioswSUqwSUpxyUrxykX45VJCKiUxnZ6w1oBTpsUuUxBQqslYzMy31rDaUUXOYiSuUZNQKanQ
qel22ViqznLY18DVyR5Wm6vpz0YYqYqzPVjHnb0x7l6d5tdvPodv4a9fP2bpXC2183bK561ERxT4
uyR4O6VkJyz0roW599okV+718dmXz/LlFw9468N7DJ5upXzRS/16gPxBGY3bYSo3vE+jurqLCY+J
iE6KiU1KiE3K8Y+KcOTFeAa1xJeMOMdLqD1yUHvFSvaKkr43/Bw+Gmfx0yrOf93D6ksN1F3Xsf9h
L/ztCW89PmDwmpORc25qamVk/HJC2kLsouNYpcWYpUWYxEVYJCXYpQI88lL8CiFBuYSoSkFcpyNn
cVBl95MyWcgYLFTaXDT6vLSGvNS5XaSMRhIaNRV6Hb2BCMt1TSw2lNMT95K2mcn53XSUx5jpruDq
7jAfvnWT3775jN9+/JGbLy/Tux+mYctOctyAs02Bt0lOvFtHw4yfnpUAr3+yzq03Vnnh7TXuvnxE
12aO5LSP+Iyf1HSQ7Kyb1IKdpt3E06iRHhGuFiHOFgnBHjV1ay5yKzpMPUWYB0qIrSuJrUuJrAqI
rAsIrwmIrshIremIrSqILCoJzMuJrynIXlSx/HwdXWd81K/omL8UoSVvpcyjJKQqIqouxa8uxSIr
xiIpxiYtwSEV4JULCSjEhOQSoko5KY2WBoeL/liOdn+MSouTcrODcruLrMNNzuoiZ3JSZXTQaHUy
lKhisSHPZG0FHTEPWaeNmpCX09P97M92szxVyw+fv8HPX37Cy18sMXY9RPOWlfIFPf4uDe42Gd4m
Fc1jIboWk5RPWxm6E2XkYYLJ63XMXeqjcj5IcsZDw1YTidEyfAMmKtYiTF37nc1/dEBH9ZSPxrkY
PdsVzF1pYvX5eso2VUS3VGQOjWT2dZTtykisi4ktiwkvS4gtiQjOluKZFOObkOGdVBCZVROcLsY/
LqFmxcjC1ShNgwaSXhUxvYSkTkJAXYpNVoJNWoJNWopTKsQvFxOQiwnLJSTVCir1BjrcfuYqu5it
ydMTTtLm8tPq9NHujZIPVtAXqmUgWktfOMdgqobp2i5mmuoZrErSEvLRkQqymK9hZbiOw71uvvz4
Nr99+yUXXhkifz5C96GDmnUdyUkNZeM6ykbMLJxupnshTXrCTe+zMbquJGnZylK3FKZyIURywk9y
LETdSoaqrSRVB0l6L1c+jdqw6mXhahNLV5sYP5dj8CBB66aX9KqO7L6N3Bk35Qcm0ntKyjalJFel
JBaFBBdK8E4V4RgrpGbdz+7LneSPvIRnRETGlWRmdJSNyfFWioh4ZGTtSuIaCR6lELuiFLu8FLus
FKdMiE8uIiATEVNKyOqU1Bv05N0+5svb2G4bZ7W2i7l0LbNl1cxnG5ipbGeqooOJ8jZ6YxV0BpP0
JTOMVqeZai6nvyLOQHUZWyOdXNoe4dHLF+HJX/nlu8/ZeW6MxgMXlfNGKpbVVG9oqVoxUrtqYWy/
gqbRBLWzISZvtdB+lKFy1UfZjI3yWS/hIQf+ASNNBzEq9mPkzqSoPko+jdq8FKF1IUnVmI9gvxrf
iBxdWwGJBT0NZ53E15REtxREtyXEtkRE1gRElooIzRfgnSrCNVpAcErB2N0QrUdGAiMi6pc1dKxb
8PUVEOuQUFlmoClio9ymw6MWY1cKsMpLscsFOOQCXHIhAbmYhFJCTiOn0aiiz21lLhFno6aWnYZm
dhubWKupY7IsS184SU84RU8oS7MrQrM7wGAqy0RNJQvddcx2ZRhvK2Out5q1qVbeeP4s73xwj9Ub
bXTshWnYCBDt0RPsVpIcV1GzaKZxzUn1nIPe9Ry9RwkGr6UYupph8kILbUs5MpM+wqN2gmMmctt+
qg7ilO+GyB2En0ZVZQTIEyWo0qVYmqTYO6UYO4uJLitJbitwzRThnC3GPV+Cb6kU30oJkRURkSUR
vtkC3KPHsA7+GfPACTzDhURHhHRvm2lcVdO55eTFNzdYXKikPmGl3GXApxNiVZRilZdgkwuwyQQ4
5BL8SikJlZRyjYw6vZJuu46poJ2lsiAbuRTrFRmGQkHqLVZqDWZanR76o1n6Y1kGE2mWG9pZaetk
bbCD9dEmlkaqmR+sYmW2h/Wtbvp2EtRvOxm6XMXYUTvpHjeRbgORHjUjm2n2bw4wvl/B7LkaBq+n
GTpfycaVIZbO99MynyU56iQx5yC94aZqP0D5rp/0tofUtvP3RioxwnABwsgpDJUibA0S7F0ibCNF
GEdOoM2fQNd2DEt3Eb4xKb4ZCYlVA9nTJtLnZZQfqanaVxFfEBMaLyY+LqR9w0jHrp3Zqxmu3Ztk
eD5AeZmMmE2CWyPCKi/F8j+ociF2hRiPQkxEIaFMI6dSp6bFpKXfaWIi5GY6EWbA76PJ5iCt1VOp
1dPisNIXDDKWSDIWj7FcUc7pjmZ2BzrYGhlh050AAB3NSURBVO1kZ6abzakW1uZamVmqpmM1RMtO
nLadMtoWstQOB0kOGIgPaJjdbWT1dDerl5pZv9pBxYSf1KCH9IiPeI+LSN5Kas5K2Zad7Gkf5Xs+
yrY8JDfsxDZ+Z07VVosRRo4hiDyDqrwUbX0plj4B9rFi3JNCTO1FmFtO4e2TEhkzElswUL7rpOaC
k5rnVHS+bqL3oZXkipTgeCGJqWJaVlX07hioXhYTnyjAP1CIp7kIk/cUBp0Aq1qARVGKVSHAoRTi
UorwyMUE5FIiShllGhnVegXNJg15r52ugIs2t5MOf5Bqq5OsRkuFXkeFXkdOp6feamEo6GCvMcW1
sW5urI5zfqGPvclm1qerWV6ooHMtQMd2lOGtCqpHvGSGbKRG1TQsuFm+1MvM2TamLlcyc76FSI8N
V5sGW4sKW6uS4IiG8tMO0ocu0gc+cqeDZLf8JLYdpPYcv5PU2hI0VacwtwjwjSgxdhVgGxLgnhYS
XpNjHyxB33UC62AJiQUnlbsB0rtOUvsmcjdk1N5W4V8sxDpYSGhCQvmckq4tA8MXjXReUlO1IyY6
U4SntwB94DgGfTFmTSlmlQCrUohLKcanlOCXS/HKpXgVUmJKGRmNghqjhja3gxafm86An/5Ymq5A
GZVGC2mtlrReR0qvI6XX0xf2cNRZx1unV3lxd4l7m9PsjTayMV7F2kKOgcUUa2d7mD/TTmbUQGJM
R3pey9DNaqYfdtF3q4yBS1Eal4MEB/X4h9UkZ43U7jlouRqk4ryX8nN+Ko6CVB5EiG66yOwFqb74
O+2vrjyFsb0Qx6iI1Laa0KwIU1cx4Xkd2QMzxqFnMAyexDWhIbuSoOmgivJdN6kjGcHdQsyDx9Hn
T+KZlBOdN5Kc19K8baDjjIH6s0pSG0WE5k7g6z+J3nsSvb4Yk7YUk1qARSnErRITUkoJKWR45VI8
CikhhYKUSkmlQUerx0Or30eL20urN0JXOEuTO0yl0UaF0Ui900JLwEV/MshcQ5btwTZ2R1s5PdzK
RncN5+e7ubg7yPhGjuHTWZqX/OQm7TSu2pm/Wcv5b3pZereMkVth6vatZNdNNB/46LsZZ/3FBi5+
NkLbnSSV54NUXQhTcy5CxWGE6v0Yp19aoOt+/GlURe4UyqpjKOr+jH24GMegAEubgPCEGte4EGPf
CfxzMkLLNqIrbpouxag6ayOwJkQ/+gzG/lN4pqQE5rUEZg3EFxQ0bprIzikJzhQTnCkgPHcKb88x
9K5TGPTF6HUlmNRCLP/d+gHV/6z65PgUUoJKJQm1ipxRT4PLRZXdQc5kptbmpM0fpSuYpsOfoMUX
oSUQojMWorssTGcuRG9jlLm+LCt9VWwPt/La1T0uXJ6gZdNOdlNO9aKepjUvo7dS3P54ild+mWXj
3RyTzydYfdjA5vtNrH5Uw+p7NZx+p4+FB53Uno9QfTFK7cUYVecjZM6GWXm+nwffXKTz+czvtH+V
CH1tCZq6AlQtJ1E1FSOvPIGtrQT/qArHsBTnqBzjSCm2hVLip2Ukt2X4FkuxT5fiX1QRWNHgnlBg
6RXjnyqlfFGBo60IW88pwvOn8E8dx9n2DDp7ATpdMTptCUa1AJtSiFspwqeUEFTICCuVBJVKAioV
Ma2KjEFHhdVCVGcgolaT1uupMJtpcPpoD8bpTmboTefoz1UyVFfDYGsFg/k0Y/kylgZruLw2zgv3
NhnYj1O+KSW7qqJyzUTbjpeWIz/n3xzgjV/WefjDKo8fv8mPP7/Ne79d4bkn61z7doyhhxly5zzU
X4pRfylO3aU4leci5M6G6bhSRfPZOIM3fmf4FyeLUdUUoWo5hbz9z8gbC5FVFmJqFOEakhNclVFz
Jkh0xox1WEp4SUl6x0hkU0NoTUt4XU9wWYl7WISx8xS+GSHhGTHa6gJc+RLK90pwjT+Do/k4Ousp
dNoidBoBJrUAu0qEWy3Bq5ASkEsJK5WE1Gr8KjVRjYaUTkeZyYxfrcUpkRNUqkjodGQMJnImK7V2
F12RCMNV5cx3tbA22sHeQjeb0y1sTDZx4/Qca2dbqN8x0nLWwtSFKvr3U7TuBui5FODMO3m232nn
8odj/PTzB/zj+yf848dv+eK/bvLhP88w92YT9deDtF5N0Hw1+a+knotSfTZGzZk4qy/2cv+zw9+Z
U3MF6GqK0DQUoG0pwN4qwdIgxdNlwdIpJ76kpetClqoVN6FZI+k9F9kzXhKnLQTWVASXZMTm5Tj7
ijD1HsM3X4x7pAhl+hTKzEkSi2JCS8ewdzyD1lGATlOCXi3ApBFh10hxaeR4lHJ8CjlBhYKAUolP
pSKiUZPQaSkzmkkarcT1ZhJ6M2VGCzUWF22OAD1OP8OeAFPxCMvNtdzaXeYv965x63CZ86sjnNsb
Ib8WpuZAx+SNNJdfmmbsUo6WowBjD2LcfTzPtY8m2X6jhe+/+4j/+v4XHnx9xOE3nWx80UTv/TRt
N9K03Sij6WqCmgtRKs+Fqb8QYfx+I0dvLLJ993cuqBnri9BWFqOpLMFYJ8bfqsXWKMHbbSMx5CM9
6KR9OUP+cozMGSvxPTOJfSvhbS2eJQHhpVI8Q0UYOo5jGXoGx9RJrB2lKBKFqNIFVK8bqNyV4Oo6
idpWjE4tQq8WY9ZIsWnkODRKnCoFbrkcn1yOVynHo1QRVCuJ67SkzRZyNgdlJgtlJgspk5ms1Uln
MMl8upb9mhYu17VxoaGZSwN5rqxMsjTawd7iMKvb7VQuWCjf0tBzzsvSczWsvlrN7MMKRl8N89K3
C3z8ww0ufjTGez8+xw9PPuPcR9PsfN3O6FvVtNzO0nIjQ9uNNA2XE1Sfi1B1IUj+hXK6HkSYvtfP
/Lm5p1GFZc8gLjuJOHMSRUUhuloRukYJ9ryS3FSItvkUjYtJ2i6VEd5S418VEd8xE97QEVmVEZ4R
Ysmfwpg/iWn4GayDxzHWFaOOlWDKifB0CnG1FuKtEaM3lqJXCDCoxJjUUixqORalAqtCjkMuxy2X
4VEo8CgU+JUKolo1aYuFnNVKzmohazaRs1kot1moc7vIxxMsNDVwfmiAG5PDHI11sjhWR3drkvXF
TgbWyqhYM1B/aKHvepCbH47x6PsjFl8pp+ehlalXYky/HOH8V3289dtZvvvlM1786QL3fthk9vV2
Wm+U0XmjnNZny2m8nKTybJDG6yGG3sjR+tDHwHM1rN79nVt/wuQxJOUnEGaOIa8SoKmXo+0oIbXk
om2rlo7TlcRnzPhnlNimi/EuCyjbNhJckxNbk+AfEmHtLsTUdwLD4J+xdhVgyokwxKRE6/Qk2/R4
ahRY/FJ0WhF6hQi9XIReJsEgk2KQyjBIpJhlMuwyGU6pDI9cjk+hIKRRkzQaKDebqbCaqbAYqLQa
qXdaafLa6Yr4ma4p56C/gwuTfdzcWeTi4SzLM50cHg7SvOuh8cBG3xU/O68O8Lcn3/L5N28zejtC
/q6VoReirH/czJ1ft7j+ywLv//1Zrn2zweIrnfTcztF+O0PX7Wo6n62h8VKKmutJxl5so/9uC803
YzTeCNF0NfA0qihzClHmBIKyY4jLi5BVlRJcVZE4bSa2riewqMY9KsQ7LcQyVoB/WUp0Q41nUYBt
7CSu/lIs+SKMfScwD54gPqwh0+rCmzOTaXLS0humvNWL2a5Fr1ZhUkoxyKXopBLUQglqgRi1UIxe
JMEskWKTyHBI5XjkCnxKBSGNkpRBR7nZSJXNRLXNRL3TSkfYw2h5lKWmHIeD7bywNc+XD29z9+Iq
Z46GOPf2JM3nbfRcD5G/EWD/9Tx/f/I1H3x7mTNvDrD7sJ35t6rZ+q6FF37d5dkf1rj0yxhjr1TR
fSNB560c3feqyd+po/tWPYsPp7j60RHvfvU2r3z8iJE7PdRdDVF9xf40qry6AFn1KWRVJ5FVnkLf
KSC+pSe8oyS8rSa6bCQ0pyW+qsY8WoBtuhT/ipTwuhzXhATXoBxLTwmGnhNYBk5RMWmntjuKN2cj
0egjP1pLz3At/qALo1aDWa3AqJShl0lRC8UoioTIi4Qoi0VoBWKMYilmsRS7TIZHIcevkhPVqii3
GKh1WGhwWWn1O+lJBJiqzbDV08KzK5N8dOsSn750kwtnJ7j06jhjb5TTfzvI3P1yem66mXyY5Pa7
Szz8dJs7n2xx/cM1zn++xLnvNrjz0yav/rTCzMcZul+I0H2vivzdKvrv1tN/p5Hdl2f46fsf4Me/
8V/f/5N3PviCowdXmH04xOTrvU+japuE6BoFGFvEmNpkxMdddF2ooPUwTctWLclFN4F5OZFFFa5p
EeF1NU3Peui4F8Y/q8XRJ8XUVYQpX4hnTEBoUIM5q8VX6aJ1uI7RuT5mFsZobq3HZjZj1Roxq5UY
5FL0YgmqUjHyIiHSAgHyIgFqgRS9UIZZIsMpk+FTyYholaRNOuqcVtoCbrrjfgbKY4zX59gcznNv
b42P79/g0f1LXLg5xcabTfTdC3H6UTdv/bDH658eMv1SGQN3Quy80snFD0dZer2OK1/scPvJTfYe
d/Eac8x+kCb/QpzOezl67jbQd6eB6XudvPvZy/A98P0v/PXb37j/9l+4+fJDrr36kJmbK0+jSqsK
UFWWYKiXYO1QExxxk5z14RtxEJw1EZxREJnWk10zU3WgouVikO5LObyLKrQ9QvT5Uux5Ke5eFcll
LZl5Cw39GSbmBpjdmGNiYZyl9QUWlmfJlqWxG2zYNAYsCiUWiRy9SIaqVIysUID0lABZoQh1iRiD
UIpNKsWtlBFQK0jqVVTZTLSFPPRn4wzXpBlvqWJxqJXDtXGunlvm4uUZ9t/oZuzVGMvvVfD+zze4
82SOh0+O2P6sk4GXXEy9mOHmd+PMvF3JwAsZOp6P0vGCn7FHCfpeDtN9O0nvrRy9t6uZud/B2x/e
h8f/hMfAN/Dr439w55XXOXv3JguX90gup59GldUUIc0K0FQrsHRqsPbKsPVLMXSLCc5oCc/p8Yyp
SK8q6b7ppOV6kOy+C8NwEfquYkzdpdjyUkxNYiJTBspnPBxdW+HSpUPW9w+YX99gaXOFzZ1NpiYn
CftD2HRWbCoDNrkas1SOUSxHI5CgKBIiKyj9V2JLhehFIqwyGV6lgqhGRcaoo95tJZ+MMFyTYaqj
hrWxDjZXetg57OH5Bxt89N1zvPfteV78eYbVr3KMfxZm6JMIA38J0PO2jf33u3j/55ssftZE160Y
mSMr0bNaIkdycheMdN5Ikb9TSd/tal764Ab8BPwAv333K//47lf+/gO88tZ7bN25Qt1uOYnf26e6
hswYW1Ro6iQ4etW4RmTYR2VkD0z45mXYRsTYRgQMnKvn9MMN1l4bJ7Fuw9AvxNBbjGGgCFuPAHOD
BHuHGm/eyuB6J/vnD9g+d4Xl3TPMr6+zubfHzt42g4O9+FxeHDozDpUeu0KFXa7ALJGhF0pQl4pQ
FAlQlQjRCEUYpTKccgU+tZq4SUeFw0RTyMNAdRkLA61c2JrhwY1D3n50k8ffvcs3v7zNL7++yS8/
vc7mZ7X0f+Cm/90g+beddD/ycOvxBO/+/JC5T3Pk74YpP2sndaQidaii/rKdnucydNzJ0njNz+TN
Om4/OuTFTy9z/fMNLn+xzAuPr3P33TtM3lig+kyA8jO/c1A5hs3YetXY8wq8g2oCE3pCi1Za7vkJ
bSowjwpxTunovNBB16VWpt9oJ7VlQtNVgmVAgGVUiL1PirVJhatLgytvJDuUZnF7lTOXn2Xr8AIT
i8tsnj7k8OgMp/e3yHe2EbC7cOvMuNRa3EoVToUSm0yBSSLDIJShF0jQCyWYpQqcag1evY6wRU/W
Y6Ux7qW/PsPCSDtXzy7zw+fvwQ/wtx9/5v5vO5z7pZcPnzzHR7/eZO2jGrpf95B/zUP+dS/nf2pn
/9t2pj4so+tBlPR5I9GzapLnNbTcctFy00/dVTd1l81UX7dQf8VL360yjj4d4f53Wxx9Mc7Cez20
XkvScClE3eXI7yR10omhS429R4e9XYuzW09o0k5s1Y1/WYdlQoh9TkJ4z0jkQE/60IJ7XIWuW4h1
SIh9TIprWIu9XYu/x0FuPEvP8jBbR2e5eO1Zzl25xczKBgtrWxydu8i5c+c5vbNJR0MTQasDr96M
T6PDr9biU2twq1Q45P8CtsrkOJQq/CYDKbeDukSY7rocvU05OhrLGByq5O6Dbf763381f/rkE174
7Tzbv3az+EUNlx9P8c6P11l8VE3Hy3baX3Yw92Gaw1/aGH83S+tdJ43XrdRcsVN9xUzLDTv11/8b
87qdxptumm55ab7ho+dOmrsfHfDVX9/l4L0F2u8m6H++iqlbw0+jRoc9xHqceDpsaOt1+AfsxGcD
JOZDhJbN2GZkuBeUpA5shNbNaLrFaNqlGPtE6PtFOCY0hKasZMcS9K0PM3/mNNNbu2wdXuLStTtc
un6Hrf3zTMwusrd/lkuXrnLu7Fl2NhZpqc4RsjiJGCxEdEYiegNhvZ6gTotPo8KnUePXa4lZjdSE
PIw017A41MXscDtt7SlaRxJcfHme3374gb9+/4RPfvmAD375hCtPttn+qI2xv0Q59/EEHz9+wMqj
LnpfCdLziofJ99L0PReh9YaPsefirLxRy9BLFUw+aOXgzQm23u5i6IX/qx07fWZD0f84/g/+Htz5
3ZlzT/U41FLaFK21BLEVta9BlEhIhMgiq2yySCRIKKL2LlrVKpHSVlvkfR+cmd+Tnoe/++x+/oTX
zHfmO+8imgIC6gPZ1AXvUu3PojFYiObjM4xHcjSf+jGePEO9pP0VNbcvm+zOdDLbs3ggKaR0qpRH
yhzKjA8o0KWROfI7hbo0cidTSOr9B/9s+h9utf6DpPZ/ktL7G42uAnocT5DoFUzYnGjtXuRaC+0D
I4xrbVhdc1gcPobl48iVk9idHpyuWSxmPZPjMkRFRQhup5Bz6w/ybiXxMOkWubd+J+f3f5GbdIu8
P25TmPoHVYK79NYIkTRVIW6qpLzsHhVP79OrEhLdDXD+9YjTL8ecfblA834Iw6GY8MkkhoNOgodq
9k4XmNhtoH4pA1m0Eu1mE5WOuyjXm5l7J+epJ5/mgIjBZTH6txJWLw1sHwWwb48hiZbSvVxKS7iE
js0yZOdNGOLDWN5PYjuc+RU1/dkd7o3m02UbYvPwDcqwmq6FJ/RtlVPtyKPZVoPleIKnvlqSun7j
9/b/5c/e38gUp1ChqqBrphu5TYvG7kM/60fn9KKxzTKgUNEiljJhsGF2zDGhMSEZkmO02PH6g9js
LsyGaZSyIUrzHpKbnEJ+cjLFfyZT9GcyBcm3yU++TVFqCo/T06gSZNFcVkBbVTGNlYXk5qTyuFJA
S08ZCkMX80cG9i8PeP9tm+njXqwfZPy8uODtyRpDW0LGdqroiRah2Wtm99yLbKWdansWwyv1KKMd
PHHfo84roHu5nmfbbQQ/aeECvlycMnPWgyneT/R0CePBBIrzRia+NTO6rUS3ZP0VNVWejMjShmNz
Bb7DSnwJQ6yPzrCILmc3E2EzkvAQuepcbrXfJk2cSpGskLrxJvr1ChRWG9PeBeyhVWYCEYzueaYd
cxjsXnqHlHRKFGitHrRmN4MyFYoJLbO+ID7/AiaTGaNBy+iwBGFuDgWpd3icdofSjFRK0/+kJC2Z
kvRUSu+mUX4/g6pH2dQWCxAWZJOZkUR+qYCWLhHdw/VMBYbZu3zL9tUSvm8aDCejvD3bJRG/xHEo
Q7xViPJ1DTs/Hdj2h2iZL6XBn033YgFTL7rQ7LXTOH+X3udFyHYamD4Y5HPsBOI3hL9a0F92EP0R
YvaLhtkfMsYTdaiv+tDvWn5FFegzKJ1pYizs5Ogkjv3IRoO/hGpTLWP+aTYP36NfmiGj7z5ZfXlU
jzXTp1UiNRpQzXgxza3gXt7Fv/YS3/Im9kAYqy+E0eVHZXDQ0PUMsVSN3upDoTYwIJUzbXbhDy7j
9gbQG3SYTXpkg4MIc/N4nJlJZVYmoqwMKrLuUJZ1h7K7dxDeS6MiJwNhXjoFD+6QkZFETv5d2npr
ae+rQ6oW41zX4r/Q8/bnAReXF3y4/MCrs200bwZQ7jfjOJaxEDcgXa+je6Wc7mgRkzsNbBzNsv0p
RHekgMH9xyhe16I77mEnHoYYxM4/Yr8aQH/ZjPZbO+6rcTQ3Xai+NzD2pflvULUpiMLl1IXbEAek
tPobaQqJaPS20eZ6hio0y3jQSZm0mSZFPxKtlhGTjVGLkwmnH/tilPn114Q2Dgit7TEXXsc+F8bq
C2PxRXimMlJe30nfiJopo4OhURVypQ6He4H5xVVsLg86/TQWqw3Z8DCignwqBAKqBdlUCzKoEmRQ
eS+N8vtpCB+kUfIghdysZAT30sm6f4fWnnraBp7SPdKJwilB93oE/QcZs59mMX7SMbLbQv9WE0Nb
3YztDiDd7KJ3tYaO5QJGNhvwHSk5Ptnly+kZUzvdyA9FqD+1onjXROjcSCL2E2Lw+nIF140Ew3UH
nutJnDcaxr82Ij9p+JvzVyVR7alA8nyE6U0TlZ4yHtqzydXf54mrhip1E/UTEnq0k0iNFuQzHsZs
bsZn3Ey757EFV/AsbxJcf4V/ZRfPQhRP6AX2+Q1mAlF0jiDNvVKKRU/pG1ah0lkYkk+g1tvxLawT
WIpitjjRGi043LOoxpXUlwupyc+h7mE2tTmZ1DzIQPQgjbIHqRQLUsnJSqGkKJdsQTp1LVX0y7po
7a9HqpFgDKswvpUw+XGAkZct9G3WIN3pon+zm95oJ+2RGpoWC2kK5qGI1uM9UPHt7AzOEgSODYy/
b8D8ox97bIyFuJ2f8e/cxBJcxX7y6scqnmslth+jBOJBpuKDjIXH/uZPVaWQMSagSNtIr09KsSef
XNM9BPJcnuja6NANM6DTI5txMeEOMuVZYGo2wLR3AfPcEtbAMvalDWYje/hWXuFffYP/+RscoS1m
5tex+p+j0NkRPmmnqKKenkE5o2odUpUak8vP0vpL5oKraI1WTDYH3vlFdEYD7Y211BbmIMrLpion
E1FOGsLcNIrzMsm9n07j0woKSnIor33M4Gg/beKniGUdTDlVONftzGybMO5Notl7hmq/h75oNa1r
5YhXq+gJC2mZf8Twi3L8b8e5jn8ncXbF4rkZfawD580AR5ebvD97xdf4BTdnwAkkYgmOLvdZuwqz
cRJjZn8B3eLCr6j3dGnkTRdTpK+jWFNHla0Gke4p1eO9dE5NMmiwILf5mPKEMQSeYw6uYp5fQe+L
MB1YZXb1JZ61N3jXDvBH3+OPHuJbO8AV2cMajGKdX8foCdM1NE5RZT3FFTV0Dw4zqtYyrrcwF95k
KfoKmyeIetqMxe7GGwpjc7uQDPZQU5ZP+aNsKh7ep7xAQEnhXWrr8lFrB6ltEFIszEc81I14uIuu
oTZGtDLMASfWJS+GJTvGZSuGDT1j0X6kG9VEPpp4ebyEdrcD00EvGx9cXMbO+fn5O4s3GqzXbfiv
R/hy/hFicHN6TSKWIBFLwAlwCpcX16x8imNbeYnC5f0VVTiXxxNvK61+KbqtEINOHa1aOWKDkWGT
gzG7H7VvBdPCJtbwJtbFKMb5NaZ8z9EvbuHd+Uhw7xjvi3e41w7wrL/DG32H+/lrrKEXWOajWIJR
VGYPta09FAhFFFWI6JQMIlNrMLh8zK/tEFjZwOj0oLXYmPEE8ESW8YVDTOnGaWupoqlBSEe7CKms
BYdHRWDRTLe4maLSPFo7nzCkkCCWiRlQSph0aLFGvJjDHkwRN5ZFF6awG9uLGd592uTb5w/EPu/z
5ewT5/FDvsUviH/5iOdGijnRxuJPDT/PP/+FGPurUCViCW7Obv6qVTEIvDrDvrKPbv75r6ieDwH0
0SCtDjX9jmkGZ2wMWGwM2XyMugNoQhGmw1FMkW3MkS0skW2M4W00oXXMq3uE3sSIHF4QfPkR98Yb
XOtvcEcP8ay/xRHexRKMYl3YwOyPMKhUU17fyKNSISXVlbQNdCNRyJkwW7AFQjhCi+ics5jcHmye
OdzBINN2M0b7FL6QhkjUyPqOm/U9P0trs8gVz6isKuZpSwVDin4Gx4cYGBtArlMyNWvBsRpCF3Ri
XfZjXw1ieR7Cu7XA2+MoifhHiH/l5uwDN/Erjr5Gsd8MYKafzR9z3JxdkTi9+b/sd3MGiVPgNMH1
5wQL+6cYIluM2oO/ov53/3/7L+p/YP8GpEG9l0Ol6/sAAAAASUVORK5CYII=

------=_Part_5243720_914198106.1492614627463--


From nobody Wed Apr 19 08:44:15 2017
Return-Path: <aafalk@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C25EF129B04 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:44:13 -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, 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=akamai.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 jkDK342XaTia for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:44:12 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 318E8128BBB for <ietf@ietf.org>; Wed, 19 Apr 2017 08:44:12 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v3JFbRsu006119; Wed, 19 Apr 2017 16:43:49 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type : content-transfer-encoding; s=jan2016.eng; bh=MKC5mNgzfn+39KPVuDv8XYLllD1LPpCX906bOTFWDKs=; b=OAVe13lriLv3xYuAVCHnKO7HeUXlPzkR3+uTVI+3uFpU2e1BMfczXHpkY5zhttxRViDM tNKSovh7DQYTi/j0BV6RaGUl4EN/IrW+0hLcZE0yLdxR/cIfIpkFgvHaW7mBAY0w4t7K Cb6HbZ2L2W0z94jGnLUpGJTVn36nGT9kxf456Id69Ws2yIoa6ILQMfhTaXzvzEVtSID6 d0zRRjZ6IsKmOik31uIPhakOXnq9QOgJYPrH3JFsZcqvI63jDVG+rtjjlo0Ft9xO/TdF GFREED3NpuWN1rDm8m981jG53GZt2jBqBBtDfNd7qGg72O2y6KljouCocZo3EC3gOnZd sQ== 
Received: from prod-mail-ppoint2 (a184-51-33-19.deploy.static.akamaitechnologies.com [184.51.33.19] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 29x9x10c0k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 16:43:49 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v3JFa7N6029214; Wed, 19 Apr 2017 11:43:48 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 29wqn5gg78-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 11:43:48 -0400
Received: from USMA1EX-CAS1.msg.corp.akamai.com (172.27.123.30) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 19 Apr 2017 11:43:47 -0400
Received: from [172.19.35.43] (172.19.35.43) by USMA1EX-CAS1.msg.corp.akamai.com (172.27.123.30) with Microsoft SMTP Server id 15.0.1178.4 via Frontend Transport; Wed, 19 Apr 2017 11:43:47 -0400
From: Aaron Falk <aafalk@akamai.com>
To: <dcrocker@bbiw.net>
CC: joel jaeggli <joelja@bogus.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>, <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks
Date: Wed, 19 Apr 2017 11:43:47 -0400
Message-ID: <51792EE1-6B14-45C5-A744-A8B41D67E137@akamai.com>
In-Reply-To: <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_B7A2B3F6-FD2E-4874-9052-D881EBE79E7C_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5356)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704190131
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704190131
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/563dPu3QsFgpEBs0RECV08SYNgQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:44:14 -0000

--=_MailMate_B7A2B3F6-FD2E-4874-9052-D881EBE79E7C_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit



On 19 Apr 2017, at 11:02, Dave Crocker wrote:

> On 4/19/2017 7:53 AM, joel jaeggli wrote:
>> Time to meet and space work with your co-authors and collaborators is 
>> a
>> pretty important part of why IETF meetings have any value at all to 
>> me
>> as an individual contributor.
>
> If there is serious interest in having more unstructured time 
> available, remove less-productive wg sessions and reconsider carefully 
> each of the ewstablished 'extra-curricular' time slots that are 
> scheduled -- my own favorite target is Bits-n-Bites -- for possible 
> elimination.
>

Not this is a significant problem.  I manage this by not going to 
meetings that have uninteresting agendas.  Same for Bits-n-Bytes.  C.f.  
George Michaelson’s 
[talk](http://snaggletooth.akam.ai/Chicago-videos/05-george-michaelson-8.mp4) 
about having IETF meetings in the hallways…

—aaron
--=_MailMate_B7A2B3F6-FD2E-4874-9052-D881EBE79E7C_=
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 http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 19 Apr 2017, at 11:02, Dave Crocker wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">On 4/19/2017 7:53 AM, joel jaeggli wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">Time to meet and space work with your co-authors and coll=
aborators is a<br>
pretty important part of why IETF meetings have any value at all to me<br=
>
as an individual contributor.</p>
</blockquote>

<p dir=3D"auto">If there is serious interest in having more unstructured =
time available, remove less-productive wg sessions and reconsider careful=
ly each of the ewstablished 'extra-curricular' time slots that are schedu=
led -- my own favorite target is Bits-n-Bites -- for possible elimination=
=2E</p>
</blockquote>

<p dir=3D"auto">Not this is a significant problem.  I manage this by not =
going to meetings that have uninteresting agendas.  Same for Bits-n-Bytes=
=2E  C.f.  George Michaelson=E2=80=99s <a href=3D"http://snaggletooth.aka=
m.ai/Chicago-videos/05-george-michaelson-8.mp4" style=3D"color:#3983C4">t=
alk</a> about having IETF meetings in the hallways=E2=80=A6</p>

<p dir=3D"auto">=E2=80=94aaron</p>
</div>
</div>
</body>
</html>

--=_MailMate_B7A2B3F6-FD2E-4874-9052-D881EBE79E7C_=--


From nobody Wed Apr 19 08:47:20 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F604127333 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:47:18 -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, DKIM_SIGNED=0.1, DKIM_VALID=-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 (2048-bit key) header.d=fugue-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 rubq0v36PPxT for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:47:16 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::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 56E3412422F for <ietf@ietf.org>; Wed, 19 Apr 2017 08:47:16 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id y33so22442907qta.2 for <ietf@ietf.org>; Wed, 19 Apr 2017 08:47:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=GzXm5Vi3jT36tEsdtxj0CN+V8qjaZQdb00GjdYlR+W8=; b=dVlB9Os3elwH5pUTydXy2eI9etfR+ojpM28EJ6dK39haxmAdu8sSk2A75biuuHf2tv 9S13/Z2kJGFXIt1+XhDKEefheoFJ38Re7Q2UxT/Q8WWeLCD5l/y0mK1K3aWIoNnp1tVd JhkZ4DzGV4jncZU6kEaQoSN71Q5mJ9scJAxXCSckaWXSuTWiN+rpLLZ0+iEAVkN5PuCP e/BUwjWYsbtSrXztOUZCxKCND6wLzCC6Yaf1LB/7Umhtn6f8zNf8YFzG7TuIDwzUyJ+F z+hi+Oc9SKTZASOQXgJJX/+wEIhFtOJ39uXG3UczU0uJehbmDZPEHZYvERwuh0ErrD1X 2vmQ==
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=GzXm5Vi3jT36tEsdtxj0CN+V8qjaZQdb00GjdYlR+W8=; b=nnwb2+rsJ2r9GKhtlcL0t1kf1bFX+TMjHbe8p+ewct17gpUpvCUis8pgXCw7tJoRBS 4VnupG1vM7nb8MC+uyQ/5ycpRQgNYpKATsfVT+t9XwhTwGefq7pL0naNlhkuIM7/3ZJr /TW1jkTBh71vCeErxz70vYonqnD9DPPOPsL1KWhDPn1COOs0EE4Jeh6bnDZ7sRcI9Bvr r2p2oIxA7AuCiQfKPe/p6HjLmnbLZDvURP+ej/l5HVhrOmKfYQwP/SZnixr8b9lRNHD/ Y8VRSfEhDqnG47NPTrHrGfbKdM66GX5zi/IrmsUI4nZDZtkCpELdASPiL3mXWECWt2L1 UWOw==
X-Gm-Message-State: AN3rC/6SJAKEO3S5Az5C0CIwhuY8acgwQtWbO9g4LN6Kzi8W4uJHUyjU poSGjCamcYhyy3aqFHA=
X-Received: by 10.200.3.216 with SMTP id z24mr3626544qtg.124.1492616835517; Wed, 19 Apr 2017 08:47:15 -0700 (PDT)
Received: from [10.0.20.202] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id z188sm2104659qka.59.2017.04.19.08.47.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 08:47:14 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <DEEBB209-2CB7-46F2-BE98-C563A422181E@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FCA8D0C0-C068-45BF-AFE0-2F0B9DA79039"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Structure of IETF meeting weeks
Date: Wed, 19 Apr 2017 11:47:13 -0400
In-Reply-To: <51792EE1-6B14-45C5-A744-A8B41D67E137@akamai.com>
Cc: Dave CROCKER <dcrocker@bbiw.net>, Michael Richardson <mcr+ietf@sandelman.ca>, Toerless Eckert <tte@cs.fau.de>, ietf@ietf.org
To: Aaron Falk <aafalk@akamai.com>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net> <51792EE1-6B14-45C5-A744-A8B41D67E137@akamai.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mJoBK5mrX_MflR7i4dgehJw9eg0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:47:18 -0000

--Apple-Mail=_FCA8D0C0-C068-45BF-AFE0-2F0B9DA79039
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Apr 19, 2017, at 11:43 AM, Aaron Falk <aafalk@akamai.com> wrote:
> Not this is a significant problem. I manage this by not going to =
meetings that have uninteresting agendas. Same for Bits-n-Bytes. C.f. =
George Michaelson=E2=80=99s talk =
<http://snaggletooth.akam.ai/Chicago-videos/05-george-michaelson-8.mp4> =
about having IETF meetings in the hallways=E2=80=A6
>=20
I don't think it's possible for us to say on behalf of the IETF which =
meetings are more and which are less beneficial, because that will be =
different for different people.   However, a structure that allows for =
collaborative work to be done when there are no meetings happening would =
have the benefit that not only you, but also the people you want to talk =
to, would potentially not be in meetings for extended periods of time.

Of course, the risk is that people will take these time periods for =
sightseeing rather than gathering.


--Apple-Mail=_FCA8D0C0-C068-45BF-AFE0-2F0B9DA79039
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; -webkit-line-break: after-white-space;" =
class=3D"">On Apr 19, 2017, at 11:43 AM, Aaron Falk &lt;<a =
href=3D"mailto:aafalk@akamai.com" class=3D"">aafalk@akamai.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><p =
dir=3D"auto" style=3D"font-family: sans-serif; font-size: 18px; =
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;" class=3D"">Not this is a significant =
problem. I manage this by not going to meetings that have uninteresting =
agendas. Same for Bits-n-Bytes. C.f. George Michaelson=E2=80=99s<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://snaggletooth.akam.ai/Chicago-videos/05-george-michaelson-8.=
mp4" style=3D"color: rgb(57, 131, 196);" class=3D"">talk</a><span =
class=3D"Apple-converted-space">&nbsp;</span>about having IETF meetings =
in the hallways=E2=80=A6</p></div></blockquote>I don't think it's =
possible for us to say on behalf of the IETF which meetings are more and =
which are less beneficial, because that will be different for different =
people. &nbsp; However, a structure that allows for collaborative work =
to be done when there are no meetings happening would have the benefit =
that not only you, but also the people you want to talk to, would =
potentially not be in meetings for extended periods of =
time.</div><div><br class=3D""></div><div>Of course, the risk is that =
people will take these time periods for sightseeing rather than =
gathering.</div><div><br class=3D""></div></body></html>=

--Apple-Mail=_FCA8D0C0-C068-45BF-AFE0-2F0B9DA79039--


From nobody Wed Apr 19 08:50:13 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB2E129B0D for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.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 95Djc5SPyYNC for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 08:50:10 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 D4A8D129AD4 for <ietf@ietf.org>; Wed, 19 Apr 2017 08:50:10 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3JFqJDN014877 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 08:52:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492617140; bh=SpnONFxPfp8bc4nt4OpU9KkQ5/5PiRR+pAiw50vhn0w=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=FnxB++J/Mpe7qqzxHzPt5Ch++kDtlS5UvCkn9jM9HcwZ73XCh5sDb6hBR7GZPsZSp i1luWIv5oJbxOBUkQwdyzxPEvzH249rsA6OA3780mWM5NrQ6aPzk2BGkAKeb5P1ciI BVU0mfHD5/d7m2MAKVQYx54AX/H16BYIRm+n0yTg=
Subject: Re: Structure of IETF meeting weeks
To: Aaron Falk <aafalk@akamai.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Toerless Eckert <tte@cs.fau.de>, ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net> <51792EE1-6B14-45C5-A744-A8B41D67E137@akamai.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <a238b879-7edd-8265-caa9-adc5250ef451@dcrocker.net>
Date: Wed, 19 Apr 2017 08:49:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <51792EE1-6B14-45C5-A744-A8B41D67E137@akamai.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EmEy3WUSav9EV-neOk2jUaUqI2s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 15:50:12 -0000

On 4/19/2017 8:43 AM, Aaron Falk wrote:
> Not this is a significant problem. I manage this by not going to 
> meetings that have uninteresting agendas. Same for Bits-n-Bytes. C.f. 
> George Michaelson’s talk 
> <http://snaggletooth.akam.ai/Chicago-videos/05-george-michaelson-8.mp4> 
> about having IETF meetings in the hallways…


The general form of this philosophy if full-blown libertarianism, 
placing all the responsibility for time management on the individual and 
no filters on scheduling any of the events.

Among other things, this model ignores the group effects of scheduling 
without regard for importance or utility.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 19 09:14:57 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E34129AF2 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 fAhp1GAvL3YL for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:14:54 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08D71129AD4 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:14:54 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id 61691A003A1E; Wed, 19 Apr 2017 09:14:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=Sm4XnZuO5MefcXRmFjXTTojmaX8=; b=BXJ0H6/djY/ skd3isoRqMJU0QQ7glvZ45lga6dg5np3vOw6/pf8+NtHUirdH01B8J50NcKtMQ4W MUquQu5I5jauYYWlZinrANUADt2ysEM8D4Hn/IxbFxSOebNESgdYaIbrhvgQnCyO ew3ZgXQpcZXsxPTBS1QbamQgVG9JHSpg=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTPSA id A1C83A003A1D; Wed, 19 Apr 2017 09:14:52 -0700 (PDT)
Date: Wed, 19 Apr 2017 11:14:49 -0500
From: Nico Williams <nico@cryptonector.com>
To: Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>
Cc: Toerless Eckert <tte@cs.fau.de>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Predictable Internet Time
Message-ID: <20170419161448.GC2856@localhost>
References: <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de> <E030FF20-4EA4-4475-9304-B6F7ADA0B8C2@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <E030FF20-4EA4-4475-9304-B6F7ADA0B8C2@frobbit.se>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W9F8EtowzLs66wxbZ_fIknw25gc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 16:14:55 -0000

On Wed, Apr 19, 2017 at 07:18:29AM +0200, Patrik F=E4ltstr=F6m wrote:
> I want as potential fixes which I think are doable:
>=20
> - an updated POSIX definition where the variable which holds the
> number of seconds since the epoch when converting back and forth to
> date actually will hold the number of seconds since the epoch.

So we should... brigade the Open Group?

> - a slot in the NTP protocol not used today include the number of leap
> seconds so people get to know that.
>=20
> FWIW I am a person that is against smear. I think a clock must be able
> to give the correct time and that timestamps should be correct. Either
> in seconds (and fractions of seconds) since the epoch or in correct
> date and time UTC. Both are increasing all the time. And because of
> that smear should not have to happen.

+1

> That said, I am not against a BCP explaining the issues due to for
> example the broken POSIX specification (which makes it hard to "do the
> right thing" in software).

Sure.

Nico
--=20


From nobody Wed Apr 19 09:16:37 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F6AA128DE5 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:16:34 -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, RP_MATCHES_RCVD=-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 mja6TeOE2Ia1 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:16:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 296E7129B0A for <ietf@ietf.org>; Wed, 19 Apr 2017 09:16:23 -0700 (PDT)
Received: from mbp-4.local ([IPv6:2620:11a:c081:20:31e2:14a0:117e:fa59]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v3JGG9VS088538 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 19 Apr 2017 16:16:09 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:31e2:14a0:117e:fa59] claimed to be mbp-4.local
Subject: Re: Structure of IETF meeting weeks
To: Dave Crocker <dhc@dcrocker.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
Cc: ietf@ietf.org
From: joel jaeggli <joelja@bogus.com>
Message-ID: <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
Date: Wed, 19 Apr 2017 09:16:03 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OCohRblMMwCE9jwumT7XoQ3bShv4DertP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-pk1efMRTKGHPv5xuS27laGDAlU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 16:16:34 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--OCohRblMMwCE9jwumT7XoQ3bShv4DertP
Content-Type: multipart/mixed; boundary="dFRAfvoKpR8jvIKSVgSiwuwnl3c3oJiNb";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Dave Crocker <dhc@dcrocker.net>,
 Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert
 <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Message-ID: <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
Subject: Re: Structure of IETF meeting weeks
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
 <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
 <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
 <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
 <10890.1492007455@obiwan.sandelman.ca>
 <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
 <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
 <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
 <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
 <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
 <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
 <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
In-Reply-To: <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>

--dFRAfvoKpR8jvIKSVgSiwuwnl3c3oJiNb
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/19/17 08:02, Dave Crocker wrote:
> On 4/19/2017 7:53 AM, joel jaeggli wrote:
>> Time to meet and space work with your co-authors and collaborators is =
a
>> pretty important part of why IETF meetings have any value at all to me=

>> as an individual contributor.
>
> If there is serious interest in having more unstructured time
> available, remove less-productive wg sessions and reconsider carefully
> each of the ewstablished 'extra-curricular' time slots that are
> scheduled -- my own favorite target is Bits-n-Bites -- for possible
> elimination.
>
> There is relatively little filtering on working group slot requests,
> and worse there's no real aid for working group chairs, to help them
> plan and manage sessions more effectively.
fwiw, slot requests are considerably earlier in the pipeline then agenda
formation.

As an AD I was relatively assiduous at working with my chairs to cancel
working group slots where the agenda/acitivity didn't justify meeting
(beyond the case of the empty agenda that's probably somewhat subjective)=
=2E
> We periodically have public discussions about this latter issue and
> there are documents that say the right things. However chairs often
> have little experience with such 'project' management and few have --
> or should be expected to have -- natural talents in that arena.
>
> Professional project planning and management assistance for chairs,
> and careful vetting of wg progress as a filter for wg time requests,
> would produce fewer and shorter sessions and better use of time.
>
>
> d/




--dFRAfvoKpR8jvIKSVgSiwuwnl3c3oJiNb--

--OCohRblMMwCE9jwumT7XoQ3bShv4DertP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlj3jUQACgkQ8AA1q7Z/VrJqUQCfbQl5qe4DAwvNXvqsBPIDUTU4
w40AniJniJhSSRpjV4Z92h6u3FUUd7HK
=VaLl
-----END PGP SIGNATURE-----

--OCohRblMMwCE9jwumT7XoQ3bShv4DertP--


From nobody Wed Apr 19 09:23:07 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852601293E9 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.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 SyFG7wM5OJhJ for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:23:04 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 C8B5C128CB9 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:23:04 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3JGPD4k017170 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 09:25:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492619114; bh=5OJDfNo6rzCVm+jD5wCojMCLe3VNsbyc4Yxe+xBGPuo=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From; b=mGyey36Y8Tr9BvE+r7Bg/WBSlxfdEj0W11OCh5NDEIJi3W9EYG/odM0mNsT1OOS1D DM6OHNNtGA2KLsktbpomFwT8rVzkcbhZOJwO00kDD9koUr4yP0hSFU07cpI87wGTRs 8GxVhv01ai9ra/lnwzwAc+GHUxHVnef6HCXdTpWo=
Reply-To: dcrocker@bbiw.net
Subject: Re: Structure of IETF meeting weeks
To: joel jaeggli <joelja@bogus.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net> <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>
Date: Wed, 19 Apr 2017 09:22:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tOvEF0wjovtU_ZUte5QEY-elHF4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 16:23:05 -0000

On 4/19/2017 9:16 AM, joel jaeggli wrote:
> As an AD I was relatively assiduous at working with my chairs to cancel
> working group slots where the agenda/acitivity didn't justify meeting
> (beyond the case of the empty agenda that's probably somewhat subjective).


Thanks for checking off that script requirement in this sequence.  When 
discussing such management issues on the we always get one or more 
postings following the template "my management oversight did/does what 
you are suggesting".

As always, individual anecdotes have nothing to do with patterns of 
concern.  It's not that they are untrue, it's that they are a single 
datum, which never explains or resolves a pattern.

Note, for example Ted Lemon's view that meaningful filtering isn't 
possible due to individual differences in defining an applying criteria.

All of this, of course, provides continuing comfort in taking no action 
to manage the week's time better.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 19 09:28:24 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DAF5129AD4 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.503
X-Spam-Level: 
X-Spam-Status: No, score=-14.503 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 D5X8pG0APYhz for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:28:22 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB4D127B57 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:28:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2787; q=dns/txt; s=iport; t=1492619302; x=1493828902; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=iA0W3VIAmMT1prRSp8BhggJyvc6LjWkIBILsWa4Fq3A=; b=DDXtGNMaw3k/Q6pkK5CHd0mahthUDOZPMGjHEMLQeQJRuQ7Qkh1CpEuG ip2mIBWNpBc/OwLgOC2r+udajttZDIrCa2G1s+rzKARHevqrmc3OOnc7Q wxay3bihCoSaKm5otnYBdEmPhlf7IctgJrCfCHLuy6EkmWPlooUMZINWo Q=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AgBej/dY/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhGaEQYoVc5BPIZVigg8Hhh0ChEIYAQIBAQEBAQEBayiFFgEFI1Y?= =?us-ascii?q?QCxgqAgJXBgEMCAEBihWqHYImiy4BAQEBAQEBAQEBAQEBAQEBAQERD4hbC4Jjh?= =?us-ascii?q?12CXwEEnS+ECIIRjGOBaIkHhl2UER84gQUmHQgYFYcrPolKAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,222,1488844800";  d="asc'?scan'208";a="654103264"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2017 16:28:20 +0000
Received: from [10.61.105.160] (dhcp-10-61-105-160.cisco.com [10.61.105.160]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v3JGSJXV014051;  Wed, 19 Apr 2017 16:28:19 GMT
Subject: Re: Structure of IETF meeting weeks
To: dcrocker@bbiw.net, joel jaeggli <joelja@bogus.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net> <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com> <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>
Cc: ietf@ietf.org
From: Eliot Lear <lear@cisco.com>
Message-ID: <971179aa-4a9b-3626-8d35-c214f558da9f@cisco.com>
Date: Wed, 19 Apr 2017 18:28:18 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jIpNaDGOa5gngIWmFCCBebfdvOQWVgPUW"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B3moFzBgMuAN7xnTFK5mSxSGFtQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 16:28:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--jIpNaDGOa5gngIWmFCCBebfdvOQWVgPUW
Content-Type: multipart/mixed; boundary="3wqSHv8sQAD8V6A7vlE6n1B9I0cqwkFbA";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: dcrocker@bbiw.net, joel jaeggli <joelja@bogus.com>,
 Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert
 <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Message-ID: <971179aa-4a9b-3626-8d35-c214f558da9f@cisco.com>
Subject: Re: Structure of IETF meeting weeks
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org>
 <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net>
 <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca>
 <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu>
 <10890.1492007455@obiwan.sandelman.ca>
 <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com>
 <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com>
 <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca>
 <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
 <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie>
 <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com>
 <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net>
 <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
 <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>
In-Reply-To: <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>

--3wqSHv8sQAD8V6A7vlE6n1B9I0cqwkFbA
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Dave,


On 4/19/17 6:22 PM, Dave Crocker wrote:
>
> As always, individual anecdotes have nothing to do with patterns of
> concern.  It's not that they are untrue, it's that they are a single
> datum, which never explains or resolves a pattern.

The converse is also true: are we quite certain that meeting time isn't
being used effectively, and how do we know? (I'm sure this is part of
the script as well, mind you.  I just don't recall what the next line is =
;-)

Eliot


--3wqSHv8sQAD8V6A7vlE6n1B9I0cqwkFbA--

--jIpNaDGOa5gngIWmFCCBebfdvOQWVgPUW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJY95AiAAoJEIe2a0bZ0nozjCMH/3g6l838rdbv7NC+yyrZy66x
DwaayZpYPIqgFPQxmzX1osxYC7t5z0pl/cb1p52dHWJLhLcy5fYuEX17YJCCOWXz
zUbf9wzSYk7IKvDuDf2UNDjzP2TCI69U9ibRe5AVhTjk+ybNiMUmOzg8rSQQ3lk+
CnTB9cXSW8X58s+t/od7vzVAjkOQ590s6VAvz60/VFNFT9qMMxFxTi/l7ICidV2n
Q7iGHWg3gN6FUr18vJtBgCQJxtxLxQUb3xEIdXepNUL3P48SzAAW7mk5OT7OdjaX
/JBZ4XftkvJNT8CGlmi7oBXu5GpM7zGlZ7pz3JqumdCt+BlfDadQjH3lEzEty1I=
=T+m3
-----END PGP SIGNATURE-----

--jIpNaDGOa5gngIWmFCCBebfdvOQWVgPUW--


From nobody Wed Apr 19 09:52:59 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E13F129B2A for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:52:58 -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 hc_IpuRs6Neq for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:52:52 -0700 (PDT)
Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002:c09::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 2A995129B36 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:52:52 -0700 (PDT)
Received: by mail-yb0-x232.google.com with SMTP id 6so7160260ybq.2 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:52:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7PfWB8ARZZ/DL6rkSwirENjUatSZsmYyTkiBQ3OGiaY=; b=o292ZBCipnzdnS8pNA1zms5ELk0CVq6vvqB2+ZPo0vT0iSy9ChomQCuCy4sSK9hZFf wqd7XdfDP9i/UGGUC9kkWtfvBAtdiR8S/bAefQlMkAX0uUf+4QpphFIWtuB+T7fqugNs qsCGsnoLcD4AkK0VrO2LuWU3frW+ZB7rfsnn4WwfTVZSP7zxpmu7m166ZXbs0vh6WHII 7nj+3nzIgxrZh+oVsJ8HnZQJ02nxlHU+mvkIhf8FF1cvNzp2sujeZQIR609D8FKRNLI1 7x/u++aIVXwgAWdZTk7ZnaKBb8iG8jca1xGYNoGDBHPBvPUy+FTXI9ZEy0yHWC0s04vq 6TTw==
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=7PfWB8ARZZ/DL6rkSwirENjUatSZsmYyTkiBQ3OGiaY=; b=KjU0xIU/pfESOUzDYmkKkOoOcdyek5TRJf/1Z/vSQ/ejbWQj8DUpeCCVNCxiIqedlA Xqk61qNIwLzBz/vZDvJoXVDre+nAagzFatCK+e7DePbDUzPgYVabulkOoBizk+d8YmnE qjmYDoNU3S+Ocbgirt4FMZeHD2Qs9R2l+tBoXbnR+8KidfO5GJMXW4kBTqL5z38s4VsZ AWy+tvbS5w1FNJYQGwOJlW/l4b2m6NpfnsO1Z0q226GlAUtZ1pGecJVAN3AG6e03VMNU A4DwEekXS3ERo6Bwd05D1Ty93AjbzmnjSAY6tCn0xHXZvnl7UG99RZfcyAH8Y/AffbnO Fy/A==
X-Gm-Message-State: AN3rC/5jBR03cvGGJslaE5MUhOJRpOcagjtylxb6rrFwL30iPpCF1qXa WF2+sbYy2QVaO7NWd28V7hHAlV7+PA==
X-Received: by 10.99.62.68 with SMTP id l65mr3817996pga.172.1492620769757; Wed, 19 Apr 2017 09:52:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.162.41 with HTTP; Wed, 19 Apr 2017 09:52:09 -0700 (PDT)
In-Reply-To: <CABkgnnWia41swpiMDahqjRGHShJ3iMXm7xKuroccK3Uec-kHKA@mail.gmail.com>
References: <CABkgnnU-rFL6sPTx=Y2rh6vzf9NSiLmMTQPMFNgrV+-Fq29+dA@mail.gmail.com> <CAHbuEH7CeZ-3D8bqDzhUTTGSkLJ2k69cw3vAM8xid1_=UvGiyQ@mail.gmail.com> <CABkgnnXv4RkwGKW42O_0=6FgQHgFjOGVxoHvxUdY=vhAJPWi7A@mail.gmail.com> <CABkgnnWrufep_hQTVqbZ6cn9kDZRkc_B4ExWOV_5d3bK_H_-zw@mail.gmail.com> <CAHbuEH6KGgqa7F59PcWO+U3i1e-YtaMOtPZQfXo4uE2x5jf2+Q@mail.gmail.com> <CABkgnnWia41swpiMDahqjRGHShJ3iMXm7xKuroccK3Uec-kHKA@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 19 Apr 2017 12:52:09 -0400
Message-ID: <CAHbuEH6+Fm-9EdBsZX5SEne_qygBUWR_WuFxWKQ5Z5hEdNGZCg@mail.gmail.com>
Subject: Re: Review of draft-mm-wg-effect-encrypt-09
To: Martin Thomson <martin.thomson@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X36BMcW9C1QJgCbwtT05Zx8IisA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 16:52:58 -0000

Hello Martin,


Thanks for your review and clarification.

On Wed, Apr 19, 2017 at 1:26 AM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> Hi Kathleen, (Al,)
>
> First, I think that my comments have been misinterpreted - albeit
> understandably - as meaning that I am opposed to the existence of this
> document.  That's not the case, I believe that there is valuable
> content here and I would like to see this published.  As observed
> separately, writing RFC 3234 was difficult, but ultimately valuable.

Thanks, this is very helpful.
>
> I think that there are some structural issues and some unnecessary
> making-of-statements.  The former needs some fairly major editing
> work; the latter: I'd advocate for excision.  I believe that your
> assertion is that the latter have been excised; I found several places
> where that is clearly not the case.  I'll try to highlight those I
> find, but I can't afford the time to do another full review just yet.

That's good that you haven't had time for a full review yet as we are
working on a revision. Alissa . Cooper has been providing extensive
input on the latter.  We are waiting on some comments from her and I
will be taking a couple of days off, so there may be a slight delay in
posting the next version.

As for structural issues, it is tough with this document as there are
many opinions on what the layout should be, having said that, we are
looking at that as well.  We'll likely figure out what to do with
section 7 as a first step.

>
> It would be a mistake to simply say that because someone requested
> publication that this document is ready to publish.  The main cost of
> taking another pass at this is the not-inconsiderable time and effort
> that requires.  So far the main argument against doing that is that it
> is hard, and I can't really disagree with that.  I happen to think
> that the extra effort is more likely to produce a more valuable
> product.

We are working on it already.

>
> I've tried to trim this mail; it's long.  I noted quite a few issues
> that you didn't address in -11 or respond to in the process, but I'm
> just cutting them for the sanity of all involved.
>
> On 11 April 2017 at 13:54, Kathleen Moriarty
> <kathleen.moriarty.ietf@gmail.com> wrote:
>>> Perhaps you have additional language suggestions for context setting?
>
> I have a suggestion, below.
>
>>>> Aside from weakening its utility and/or arguments, the lack of focus will
>>>> allow
>>>> this document to be abused in various ways.  For instance, it might imply
>>>> IETF
>>>> endorsement of the practices described in the document.  Given that the
>>>> IETF has
>>>> published positions that in some cases reject these practices, this
>>>> document
>>>> needs to be very precise with its claims.  In its current form, it is not
>>>> nearly
>>>> careful enough.
>>
>> This paragraph is all speculation about an unfortunate future.
>> We could speculate that the operator, security and app communities
>> come together to work out solutions after reading this doc,
>> which is part of our intent.

We've worked on the context setting more since this last message with
input from the IESG reviews.  I'll just put a bit of the text here and
the rest will be in version 12.  We can let you know when the updated
version gets posted.



1.  Introduction

   In response to pervasive monitoring revelations and the IETF
   consensus that Pervasive Monitoring is an Attack [RFC7258], efforts
   are underway to improve and increase encryption of Internet traffic.
   Pervasive Monitoring (PM) is of serious concern to users, operators,
   and application providers.  RFC7258 discussed the critical need to
   protect users' privacy when developing IETF specifications and also
   recognized that making networks unmanageable to mitigate PM is not an
   acceptable outcome, but rather an appropriate balance would emerge
   over time.

...

Seeing the rest in the next version and getting your comments would be helpful.


>
> I don't think that argument is so easily dismissed.  When we create a
> statement, we have to consider how it might be read from multiple
> perspectives.  In this case, it's not that much of a stretch to
> believe that someone might read some of the statements here as license
> to try to undermine TLS (for example, based on a reading of the text
> from Section 2.4).
>
>>>> If this document is going to be published as an RFC, then it needs to be
>>>> very
>>>> clear about its intent and its position - or lack thereof - toward these
>>>> practices.  It might be possible to say that these practices were employed
>>>> in
>>>> networks in the past and that encryption is reducing the viability of
>>>> those
>>>> practices.  A value-neutral statement like that might be acceptable as
>>>> long as
>>>> it were framed carefully.
>>
>> The document conveys that message everywhere. The words contributed were
>> changed in many places to remove any implication that the current practices
>> are "requirements" or even "needs".
>
> Actually, I don't question the fact that people believe these to be
> requirements.  But I see a lot of cases where it's less clear, for
> example in Section 2.3.1 (I'm moving to -11 now):
>
>    This [referring to traffic analysis] technique may be
>    used with clear text or encrypted sessions.

Good then I'll update that to, more of a statement that this occurs:

This technique is sometimes used with clear text or encrypted sessions.

>
> Thinking about an adversarial reading of this, is that a permissive "may"?
>
>> The abstract and introduction contain value neutral statements like
>> what you are suggesting already.  We actually say the practices may be
>> eliminated, going further than your request as that may be the case.
>>
>> The only change I could see in the abstract would be the following:
>>
>>    Increased use of encryption impacts operations for security and
>>    network management causing a shift in how these functions are
>>    performed.  In some cases, new methods to both monitor and protect
>>    data will evolve.  In other cases, the ability to monitor and
>>    troubleshoot could be eliminated.  This draft includes a collection
>>    of current security and network management functions that may be
>>    impacted by the shift to increased use of encryption and encryption
>> that is designed prevent interception.  This draft
>>    does not attempt to solve these problems, but rather document the
>>    current state to assist in the development of alternate options to
>>    achieve the intended purpose of the documented practices when possible.
>>
>> Do you have additional suggestions?  Or is the phrasing read
>> differently than we intended by stating functions may be eliminated?
>> We thought that was very clear to your points.
>
> The abstract could be better I think.  How about?
>
>    Pervasive monitoring attacks on the privacy of Internet users is of
> serious concern to both the user and operator community.  RFC 7258
> established the need to protect user privacy when developing IETF
> specifications.  This encourages reducing the information that is made
> available to passive observers, which affects some security and
> network management practices.  This document describes those practices
> and examines the effect of increased use of encryption on those
> practices.

We've updated the abstract in IESG review and have the text as follows
in the running version.  The full scope of RFC7258 is important for
this draft as it discuses finding a balance with network management
and the importance of user privacy.  The following is similar to your
proposed text, but includes that as well.  We want to make sure the
document is helpful to operators and keeps the conversation open for
each side of the discussion - so it happens.

Abstract

   Pervasive Monitoring (PM) attacks on the privacy of Internet users is
   of serious concern to both the user and operator community.  RFC7258
   discussed the critical need to protect users' privacy when developing
   IETF specifications and also recognized making networks unmanageable
   to mitigate PM is not an acceptable outcome, an appropriate balance
   is needed.  This document discusses current security and network
   management practices that may be impacted by the shift to increased
   use of encryption to help guide protocol development in support of
   manageable, secure networks.

>
> On a second read, I think that the bulk of the problem is with 1.1,
> section 1 is largely OK.  The second-to-last paragraph of Section 1.1
> is critical, but I actually think that the remainder of that section
> is more of a liability than an asset.  The discussion of OS is weak,
> creating good citations for the statistics is hard, and the discussion
> of non-web cases isn't adding much value.  You could simply take it as
> read that there will be increased encryption and this document would
> work well.  Even if you didn't want to assume that encryption is
> increasing in volume, you could have a fine document that explored the
> management impacts of encrypted sessions.

In reviewing this text again, I see we jumped right into TLS and DTLS
with no discussion of OS used in IPsec.  I'll think about this a bit
more.  IPsec has had OS in place for a while and we have a few
documents published showing implementation work: RFC4322 - Linux
FreeS/WAN project and RFC7619 -specifying IPsec without
authentication.  The latter was implemented by RedHat.  RedHat put it
in the OS and had intended to have it enabled by default, that hasn't
happened yet.  There are many uses for OS between servers or Linux
systems, where you can't authenticate the other party in advance.  I
actually posted a review to the DHCPv6 mailing list yesterday pointing
to these RFCs to consider including int heir work to make it easier to
implement end-to-end encryption for DHCP for the coffee shop use case.
Storage uses IPsec and I'm sure there are other use cases where OS
is/will be very helpful. We'll play with the text a bit to make this
clear.

>
> Also, it would help if there was a clearer statement regarding lack of
> endorsement.  If you are going to say "lawful intercept exists" - a
> true statement, almost a truism - it's prudent to also say that this
> isn't an endorsement of those practices.  Explicitly.

OK, some of this text got cut, but we'll look through it again.  We've
also gotten comments to not have text throughout that restates such
things as the context setting is enough.  I think considering this
with the full updates is needed and we'll look at that.

>
>> The intent of this document is to help operators as these changes
>> continue.  It is to make sure we are not ignoring the impact of the
>> changes the IETF has with our decision (which are supported in this
>> document).  This document is intended to assist operators.  By
>> explaining the functions being performed, some have already been
>> provided alternate methods to achieve their goals.  We have also
>> received quite a bit of positive feedback from operators - that this
>> document helped them come back to the discussion and to approach a
>> world with more encryption or sessions that can't be intercepted (TLS
>> 1.3, TCPinc, QUIC, etc.).
>
> Yep, and that's a valuable goal.  It would be nice to have a document
> that allowed someone with a need (or requirement) to be redirected to
> an architecturally sound solution.  The challenge is that these
> problems don't all have simple solutions.  In its current form, I
> don't see this draft as providing that service well because the
> goals/use cases aren't particularly well-organized.  Also, it's
> probably best to avoid developing solutions as part of this.  A simple
> catalogue of needs and practices works.


Agreed.
>
>> Can you give specific sections where it sounds like we are weakening
>> RFC 7258 so we can change that specific wording?
>
> See above.
>
>> Version 8 to 9 had some edits to remove statements with used terms
>> like 'need'.  We may have missed a couple, we'll check the ones you
>> pointed out.  There are also numerous statements that are explicitly
>> in support of RFC7258.  These are in the abstract, introduction,
>> summary and sprinkled throughout the document.
>
> I don't think that the superficial change really worked.  See above
> regarding "may".

Yes, we are working on this and if you find any problems in a later
version, that would be helpful.  We are trying to catch all of them.

>
>> Apparently, RFC 7754 goes further than our scope. We are not describing:
>> "... the different practices that might be employed to achieve that goal."
>
> Agreed.  I am more interested in the structure of that document.  How
> it breaks down the problem carefully and explores the various options.
> You don't have to offer solutions here, but the treatment could be
> more methodical (like in RFC 7754).
>
>>>> The Real Purpose of this Document
>>>>
>>>> I think that this is the real question that this document wants to ask is:
>>>>
>>>>    In a world where we are forced to defend against pervasive monitoring
>>>> by
>>>>    motivated and malicious actors, can we find a role for less pervasive
>>>>    monitoring by well-intentioned entities?
>>
>> The document aims to help operators by giving them a chance to discuss
>> the impact.  It opens the
>> door to conversation so they can find new ways to achieve the same
>> goals (better performance for customers for instance or monitoring
>> services that have been requested - web content, DLP), which may mean
>> endpoint solutions are needed or filtering limited to hostnames for
>> now until other mechanisms are developed (likely at the application
>> layer).
>>
>> For enterprises, application and host level solutions are
>> fine as many organizations have employees sign away their rights to
>> privacy.
>
> I understand that's true.  Though it's also a little sad, I'm speaking
> from a position of privilege, so I won't make too much of an issue of
> it.  What interests me here is the operational challenges that arise
> from this.  The need to modify multiple applications for instance.
>
>> QUESTION: Would it help to add some text like the first paragraph into
>> the introduction?  - This document aims to...
>
> If that is actually the aim of the document, sure.  It seemed less
> clear to me what the intent was from reading it.

OK, hopefully much of what you are looking to see will be in one of
the next versions.  We may need to do a couple as we work through the
rest of the comments.

>
>
>>>> In other words, the right question might be:
>>>>
>>>>    For each of these practices that we see today, are the use cases that
>>>>    motivate them legitimate and how might be implement alternative
>>>> techniques
>>>>    that properly respect privacy and security?
>>>>
>>
>> Yes, this is the point of the document and it's stated in several places.
>
> I don't think that this is exactly the question you ask, it's a
> broader one that you are trying to attack.  You are laying the
> groundwork for asking that question: which is, what are those
> practices and why do they exist?  The question of legitimacy isn't one
> that you want to tackle here (not enough space, too hard, etc...) and
> designing solutions is best left to individual protocol designs.

Agreed and yes, this might be input to include in conversations on
individual protocol design.  At that point interested parties should
dig deeper and determine what make sense and what is possible
considering the balance that is desired for that protocol.

>
>>>> Two- and Three- Party Interactions
>>>>
>>>> A great many sections of the document are unclear about the relationships
>>>> between different actors.  It seems like many of the activities describe,
>>>> which
>>>> are presented here as being beneficial, are performed by a third party
>>>> without
>>>> the consent or involvement of the two communicating peers.  After all,
>>>> those are
>>>> the cases where encryption most often interferes.
>>
>> As the draft says, some of the methods will be eliminated.
>
> It's very easy to lose track of that 40 pages in when the text that
> you are reading says something else.

Fair enough.

>
>>>> The assertion that some benefit is accrued to communicating peers as a
>>>> result of
>>>> these actions is the constant subject of the text.  I observe that in most
>>>> of
>>>> the cases listed in this document, the benefit is accrued primarily to the
>>>> third
>>>> party.
>>
>> Operators by their nature have different privacy concerns than their end
>> users. Operators by their nature want to accrue benefits. This document
>> doesn't change the balance; instead, it tells them how to deal with privacy
>> that has already been applied.  While we agree with your statement and think
>> it's important to build privacy and privacy options into IETF protocols,
>> operators often don't care, despite the many RFCs we have published
>> telling them that they should care. We still need to engage them so we can
>> have this discussion.
>>
>> The "third party" is likely the only one receiving a trouble call,
>> and there is benefit for all parties when the trouble is cleared.
>
> I think that you missed my point here.  The point is that the document
> declares various outcomes as virtuous, rather than simply describing
> the practice.
>
> Section 2.3.2.1:
>
>    The features and efficiency of some Internet services can be
>    augmented through analysis of user flows and the applications they
>    provide.
>
> That's an statement that ascribes a virtue to a particular practice
> without qualification.  The ensuing text only doubles down on that.
>
>> The above is stylistic in nature.  We've already made changes to the
>> format to address specific comments in IESG review. A complete
>> re-write is not appropriate at this point in the draft lifecycle.
>> That's not the point of IESG review.
>
> See above.
>
>>>> The immediate focus on opportunistic security is highly misleading,
>>>> especially
>>>> in the web case.  The amount of opportunistically secured web traffic is
>>>> miniscule by global standards.  Since Firefox is the only browser to
>>>> support OS
>>>> for the web, so adjust the following by market share:
>>>> <https://mzl.la/2oc46ch>.
>>
>> You'll need to cite text that is leading you to this conclusion as I
>> don't read it as being specific to OS, rather that OS is explained so
>> operators understand it in the mix of encryption options.
>
> The first two paragraphs of Section 1.1 talk about OS.  In the context
> of this document OS is maybe relevant for a few reasons:
>
> 1. it can be removed trivially (see the STARTTLS attack by operators)
> 2. it can be deployed more easily (debatable)
I think the IPsec uses of this may change the argument (meaning the
deployment ease improves for that), think DHCP or connections between
servers.  In the RedHat case, their plan was to implement tunnel mode
IPsec and have it enabled by default for use between other systems on
the same operating system.

> 3. it is encryption
>
> Of these, the last is the only thing that is relevant.  For the
> reasons I cite above, I would restrict discussion of it to those
> sections that talk about stripping opportunistic security (striptls,
> the STARTTLS attack).
I'm going to think about your points more, but just an initial thought...
For follow on work, wouldn't individual protocol designs consider OS
in the balance between management and privacy?  I would think the
conversation would be part of the discussion and wouldn't go as far as
saying (for the purpose of this thread, not the draft) that management
would tip a balance to OS

>
>>> For the Mozilla statistics, Richard Barnes had reviewed the text after
>>> providing the statistic as he wanted to make sure it was stated
>>> clearly raising the same concerns you do about statistics.  Do you
>>> have further text suggestions to clarify this statistic?
>
> Well, my first suggestion is removal.  Failing that, create citations
> for the statistics.  If you can't - the Dell EMC stats, for example -
> then at least describe what they mean. I don't know if 78% applies to
> connections, packets, or requests (probably not requests).

For Dell EMC, it was firewall logs.  This would be URL accessed (many
for single pages) I suspect.  We'll think more about this and possible
removal.

>
>>>> There's an implicit argument here that runs counter to established IETF
>>>> consensus.
>>>>
>>>>    Some methods used by service providers are impacted by the use of
>>>> encryption
>>>>    where middle boxes were in use to perform functions that range from
>>>> load
>>>>    balancing techniques to monitoring for attacks or enabling "lawful
>>>>    intercept", such that described in [ETSI101331] and [CALEA] in the US.
>>>>
>>>> This fails to remain neutral.
>>
>> The functions are impacted, so how would you suggest we word this
>> text?  It doesn't endorse the functions, just says they are impacted.
>> We are open to suggested text.  Similar to how we describe 'attacks'
>> by operators to break encryption or use RSA private keys.  We do have
>> text in both directions on this and your review is complimentary of
>> the ones that fit your dialog, but are also not value neutral.  Mind
>> you, I am constantly reviewing RFCs and making sure TLS best practices
>> are considered and questioning the use of deprecated crypto or not-yet
>> but should be deprecated crypto.
>
> I think that you should include a section on intercept.  It happens;
> encryption largely prevents it, though OS doesn't.

OK, we'll consider doing that.  I think some of this text has been
removed in the current version and I don't want to see a head in sand
approach, so maybe a section on interception is the best way forward.

>
>> But this is true and we've seen operators do things like prevent
>> STARTTLS.  This isn't a good thing and we need to ack that this has
>> happened.  We need to help operators figure out how they help users in
>> new ways and understand that some of the functions they perform
>> currently (TLS 1.2) won't work in the future.
>>
>> This text got re-worded during AD review, I believe.  The intent is to
>> say that this is not good - the practices are called out as
>> undesirable.  How would you suggest it be re-phrased and we can check
>> back with Stephen to see if he agrees.
>
> I would prefer that the document doesn't mention that at all.  Talk
> about disabling OS as a practice that happens.

We'll think about this more in an intercept section.  There are steps
to this, TLS 1.2 to TLS 1.3, use of OS in TLS and IPsec, known attacks
possible in TLS 1.2, things you can do if you own the server and keys
for TLS, as well as ACME work - setup easier, but not quite as secure
since we are accepting tradeoffs to increase the use of encryption.

>
>>>> I
>>>> certainly disagree with the IETF making any such statement.  It says that
>>>> we are
>>>> collectively willing to bow in response to (anticipated) threats of
>>>> violence.
>>
>> Prior to AD review, there was a reference in the text to the practices
>> being bad and stating that regulators and the media helped to correct
>> this behavior.  The problem here may be the evolution of the
>> text and lack of reference now since we couldn't find a stable
>> reference.  Do you have a wording suggestion?
>
> See above.  That is, acknowledge that some methods exist for
> "breaking" encryption, that those are largely limited to striptls and
> its ilk, though attackers with significant resources might be able to
> perform other sorts of attacks (cite the attacks on TLS doc here).

Noted, thanks.
>
>> While we read this as  more of a substantive remark, the text on
>> load balancers and QUIC were added per Mirja's IESG review.  We would
>> need to check with her about making any changes here.  They were
>> specific additions that were requested.
>
> I think that Mirja responded here, I'll follow-up there.

Great and her suggestions have been taken into account in the working
copy of the draft.
>
>> Further, it is only IETF QUIC that is in active development.
>> Google QUIC (referred to as GQUIC in IETF discussions) is a more
>> stable experiment now.
>
> It's existence seems assured, but not its form.  Google are tracking
> the IETF work.

This was removed, per Mirja.

>
>>>> Section 2.2
>>>>
>>>> I think that this sums the situation up reasonably well.  It fails the
>>>> value-neutral test in a few ways though.  As I understand the situation,
>>>> surveying operates at many levels.  For accurate planning, models of
>>>> endpoint
>>>> behaviour are used to determine things like whether loss or congestion is
>>>> affecting throughput.  Really good models require knowledge of what users
>>>> are
>>>> attempting to do and the applications they are using (as mentioned, things
>>>> like
>>>> browser version matter in these models).  For instance, it isn't enough to
>>>> understand that the user is trying to receive 720p video, you also have to
>>>> know
>>>> that a 4k stream for the same content is available.
>>
>> Sure, that's why we broke the draft down by operator type.  Some
>> functions are shifting and the responsibilities for operators will
>> shift with these changes.
>
> Here's a structural suggestion then:
>
> * Use Cases
> ** Common Use Cases - those for more than one type of network operator
> (e.g., troubleshooting)
> ** Enterprise Use Cases - those unique to enterprise (e.g., DLP)
> ** Network Operator Use Cases - e.g., capacity modelling
> ** Hosted Service Use Cases
> * Practices
> ** DPI
> ** Traffic Analysis
> ** Removing Encryption
> ** Repacketization
> ** TCP Termination
> ** ...
>
> Description of use cases can list practices used in support of them,
> or the practices can list the use cases they support, or both.

Thanks, we'll consider this structure.
>
>
>>>> Section 2.3.2.2
>>>>
>>>> Again, it's strange to see differential treatment under DPI.  I was fairly
>>>> sure
>>>> that fingerprinting was used here as well.
>>>>
>>>> Section 2.4
>>>>
>>>> This section doesn't even attempt to recognize that applications are much
>>>> better
>>>> now at scaling content to suit the device on which that content is
>>>> intended to
>>>> be consumed.  It should.
>>
>> The reason for that is that there has been a useful dialog between application
>> designers and network providers over time, beginning with app designers
>> saying "what do you mean the network has errors and delay? this works
>> fine in my lab...".  The contributors viewed that as well understood
>> and far back
>> in time, so not necessary to mention.
>>
>> If you think there should be text to this point, please suggest some.
>
> "This has an effect on applications in addition to network operations.
> By removing the ability of an intermediary to compress content, the
> responsibility for adapting to network conditions moves to the
> endpoints.  Applications that are able to compress content, or reduce
> bandwidth use to suit network conditions will gain better
> performance."
>

Thanks for the text to add.

>
>>>> This section should not represent compression as an unmitigated good.  I'm
>>>> told
>>>> that significant damage can be done to video streams by "well-intentioned"
>>>> compression middleboxes.
>>
>> Please suggest text.
>
> "Compression employed by middleboxes can have an effect on
> performance.  In addition to latency costs, compression can require
> additional computational resources.  Use of lossy compress degrades
> the quality of content."

Thanks for the suggested text.

>
>>>> Yet again I see a call back to the implicit threat of violence in "they
>>>> will
>>>> adopt undesirable security practices".  Statements in that form have no
>>>> place in
>>>> IETF RFCs.
>>
>> This was edited text per review and agreed upon (I think in the AD
>> review).  Suggest alternate
>> text and we'll go back to the other person.
>
> Ahh, I hate putting you in that position.  I would prefer if this be removed.

It was edited again in the meantime.  One instance seems to be removed
(there were 2) and we have:

      In response to increased encryption of these fields, some network
      service providers may be inspired to undertake undesirable security
      practices in order to gain access to the fields in unencrypted data flows.
>
>>>> Section 2.6.2
>>>>
>>>> I can't parse this statement:
>>>>
>>>>    Approved access to a network is a prerequisite to requests for Internet
>>>>    traffic - hence network access, including any authentication and
>>>>    authorization, is not impacted by encryption.
>>>>
>>>> And then we get into zero rating, which is a hot-button topic.  No
>>>> acknowledgment given to the sensitivities on the subject, or even a
>>>> superficial
>>>> exploration of the technical options that are available.
>>
>> Please suggest text.  This was updated in IESG review.
>
> I see a reference to Section 7 here, but no text on zero rating in that section.
>
> Zero rating is a use case in its own right.  I would make a new
> section, or simply repurpose Section 2.6.2 for that (remove paragraph
> 1).
>
> Section 2.6.2. Zero Rating and Preferential Treatment
>
>    Some network operators sell tariffs that allow access to certain
> content without cost to users, a practice known as 'zero rating'.
>
>    More generally, users might be charged differently based on the
> content they are viewing.  Or, packets related to the access of
> certain content might be given different priority.  Identification of
> content is critical to providing this differentiation, because web
> content is often distributed across multiple servers.
>
>    Use of encryption hides details about content, preventing the use
> of those specifics from being used in providing preferential
> treatment.
>
> This expands the scope of the section considerably, but I think that
> it's what you want to say.  I have restrained myself in not making any
> statement about the virtue or otherwise of these practices.  I think
> that this is a bad trend, but we don't need to say that in an RFC
> (unless we create one with that purpose, that is).

Thanks, this is helpful. Al will need to take a look at this as well
and then we can integrate it.

>
>>>> Section 2.7
>>>>
>>>> This is one of the areas that is most legitimately affected by increased
>>>> adoption of encryption.  I have no doubt that having detailed information
>>>> about
>>>> the application and its use makes the process of troubleshooting easier.
>>>>
>>>> This is the first mention in the document of network-based optimization.
>>>> Was
>>>>the section describing that cut from an earlier draft?
>>>>
>>>> The use of websockets as a primary example is an odd one.  It's just not
>>>> that
>>>> common.  For reference, we see >20% failure rates on encrypted websockets
>>>> and
>>>>>50% failures in the clear; no one in their right mind would rely on
>>>>> websockets.
>>>> If the point is that HTTP is carrying more traffic (see
>>>> http://conferences.sigcomm.org/hotnets/2010/papers/a6-popa.pdf) saying
>>>> just that
>>>> would be more effective.
>>
>> "in their right mind" . That isn't helpful.  Operators submitted text
>> to explain what they are doing and how it's impacted.  How about
>> proposing text to help in that vein.
>
> "The widespread use of encrypted HTTP means that TCP port 443 is being
> used for a large variety of use cases with sometimes very different
> performance requirements.  Some uses are latency-sensitive, others
> need to send lots of bytes.  In some cases, mixed uses appear on the
> same connection; which is possible with both WebSockets [RFC6455] and
> HTTP/2 multiplexing [RFC7540].  A network operator is unable to
> provide differential treatment using the information that is available
> to them."
>
> Now that I look at this, this is a more general and useful statement.
> Hiding it in the bottom of a section about something else doesn't make
> a lot of sense.  It's also not general enough to surface in an
> introduction, so I recognize the difficulty in finding it a home.

Thanks for the text, we'll figure out what to do with it then.
Structure isn't easy in this draft.

>
>>>> Section 3.3
>>>>
>>>> There's certainly a lot of detail here, but I had a really hard time
>>>> extracting
>>>> value from this section.  I can't see how data storage is fundamentally
>>>> different to the general case of an application provider.
>>
>> They figured out how to increase encryption and manage their hosted
>> environments.  There were adjustments made and they've been
>> successful.
>
> This short explanation is much easier to digest.  Is there any way
> that might be said up front? Though even with that, I would still find
> this section very difficult to read.

OK, We'll think about this more.
>
>>>> Section 4.1.2
>>>>
>>>> I'm confused about the purpose of this section.  This seems to be talking
>>>> about
>>>> the sort of network-based methodologies an application provider might
>>>> employ to
>>>> ensure that their application is working as intended.  Why would the
>>>> application
>>>> provider not have access to detailed logging and usage metrics?
>>
>> The problem cited to us is that logging is sorely lacking.  This needs
>> to be pointed out and fixed as it is too much for the operator to deal
>> with given the large number of applications running in their
>> environments.
>
> If that is indeed an issue (I've heard the same asserted, it's
> probably true), then it needs to be said.

I'm pretty sure we've inserted more text on logging, but will make
sure with a sweep of the full draft to make sure it was put in
appropriately.  This might not be perfect in -12.

>
>>>> Section 4.2
>>>>
>>>> If the inclusion of a reference to RFC 7457 is to support a claim that TLS
>>>> is
>>>> attacked, that's sailing far too close to an endorsement of attacks than I
>>>> am
>>>> comfortable with.  However, I don't believe that any of the listed attacks
>>>> remain viable in modern applications.  What is most often the case is that
>>>> a
>>>> trust anchor is installed on enterprise users' machines and new
>>>> certificates are
>>>> minted as needed.  In other words, the host that is accessing the HTTPS
>>>> site is
>>>> owned by the enterprise and modified so that it can comply with its
>>>> policies.
>>>>
>>>> When you recommend attack like this (to be clear, I would oppose
>>>> publication of
>>>> text that does this), you need to acknowledge the downsides.  For example,
>>>> MitM
>>>> devices routinely break connections, they hide the true security status of
>>>> communications from endpoints and users, they frequently implement weaker
>>>> versions of protocols, they often don't include the same degree of rigor
>>>> in
>>>> things like certificate validation, and probably many more things that I
>>>> can't
>>>> casually list off the cuff.
>>
>> Please suggest text.
>
> Well, to preface this, I don't think that this is the right section to
> put text like this.  It's more appropriate in a section that talks
> about the specific techniques (Section 4.2 is another grab bag of
> practices duplicating text from other sections).
>
> I think that it is entirely appropriate to say:
>
> ```
> Encryption can be disadvantageous to the goals of the operator of a
> middlebox.  Removal of encryption without the consent of endpoints is
> an attack.  Attackers can and have removed attempts by endpoints to
> use opportunistic security (see [SSLSTRIP --
> https://www.blackhat.com/presentations/bh-dc-09/Marlinspike/BlackHat-DC-09-Marlinspike-Defeating-SSL.pdf],
> [STARTTLS -- Section 5.1 of DOI.10.1145/2815675.2815695]).  More
> resourceful attackers might use attacks or weaknesses in deployed
> protocols (see [RFC7457]) or flaws in implementations to remove or
> attack uses of encryption.
> ```


We'll think about this more as section 4 is part of the enterprise
text with the disclaimer at the start of the section that provides the
caveat that users have signed away their privacy rights (essentially).

>
> That's a stronger statement than I think you are looking to make
> though.  It doesn't invalidate the cases where endpoints are owned and
> trust anchors are installed.  I would put that down in a different
> section.

This goes to our current division of sections for text and what's okay
in an enterprise is by no means okay anywhere else.

>
> ```One method for intermediating encrypted sessions is to install a
> trust anchor on an endpoint and then use the associated keys to create
> authentication credentials that will be accepted by the endpoint.  In
> this way, a middlebox can terminate a session in a way that the
> endpoint will accept as legitimate, thereby impersonating the intended
> peer.
>
> This technique rarely works for mutually authenticated communications,
> because the middlebox is usually unable to exert control over both
> intended endpoints in a way that would allow it to impersonate both
> peers to each other.  It also causes the modified endpoint to become
> entirely reliant on the methods the middlebox uses for correctly
> authenticating the intended peer.
>
> For example, a web client typically implements authentication checks
> that exceed those listed in RFC 5280 [cite]. This might include key
> pinning [RFC7469], OCSP stapling
> [https://www.iab.org/documents/correspondence-reports-documents/2017-2/iab-statement-on-ocsp-stapling/],
> and other checks. A middlebox that impersonates a web server that does
> not perform the same checks could be vulnerable to the attacks that
> these additional checks are intended to protect against.
> Impersonation of a web server also hides the true status of the
> connection from the web client.
> ```

Thanks for the text, it's helpful and we'll also consider placement.
I'm not sure of the extent of structural changes for the document, but
this is text that we'd have to consider where it makes the most sense.
>
>>>> Section 6.1
> ...
>> Please suggest text if this should be included.
>
> Here's a rewrite...
>
> ```
> A TLS client that initiates a connection to a server can provide a
> server_name extension (server name indication, or SNI) [RFC6066] which
> indicates the name of the server to which it is attempting to connect.
> SNI allows servers to select between multiple certificates when
> handling a TLS handshake.  This enables the use of multiple domain
> names at the same IP address, also known as virtual hosting.
>
> Although SNI is an optional extension, it is today supported by all
> modern browsers, web servers and developer libraries.  Akamai [Nygren]
> report that many of their customers see client TLS SNI usage over 99%.
> HTTP/2 [RFC7540] mandates the use of SNI.
>
> When present, the server_name extension that is included in the TLS
> handshake is not encrypted.  This allows a passive observer to
> identify the domain name to which a connection SNI is being made.
> Other information about the application, such as the URL of an HTTP
> request or the type of content being requested, is not visible, only
> the domain name of the server.
>
> Relying on SNI to identify a host has several limitations.  It is not
> present in a small number of cases where clients do not support the
> feature, or where protocols that don't mandate or rely on its use.  In
> addition, HTTP/2 connection coalescing (see Section 9.1.1 of
> [RFC7540]) can mean that a connection originally established for one
> name is used for requests to other names.
> ```

Thanks for the text.  This is good, but we also have to include the
point that this is a change for operators and an impact as they were
using more information than just the server/hostname in the past and
we need to make that change clear in
the text for operator impact.

>
> I've dropped Alt-Svc mentions (they aren't relevant in this context -
> even with HTTP OS, SNI is still shown in the clear).  I tried to keep
> the text about the type of content

OK, thank you.

>
>>>> Section 6.2
>>>>
>>>> ALPN will be encrypted in TLS 1.3.
>>
>> Noted.  Thanks.
>
> Hmm, I should have been clearer, the server's choice of application
> protocol will be encrypted.  The client's set of options will not be.

Thanks that's helpful.

>
>>>> Section 6.3
>>>>
>>>> This reads as a invitation to perform traffic analysis (a statement that I
>>>> oppose).  Note that we have added padding to most recent protocols (HTTP/2
>>>> and
>>>> TLS 1.3 in particular) to give endpoints the ability to resist this sort
>>>> of
>>>> attack.
>>>>
>>>> Note that block ciphers can add ~240 octets of discretionary padding per
>>>> record.
>>>> That can be pretty effective if you are careful.
>>
>> I believe this text was added through the IESG review.  I don't see
>> the problem with the text you are citing, so could you suggest
>> alternate text?
>
> ```
> Information about the content of encrypted communications is often
> available through traffic analysis.  For instance, the size and timing
> of packets can reveal considerable information about the contents of
> data [NETFLIX][CLINIC].
>
> Applications can implement traffic analysis strategies, usually by
> padding content to obscure its true length.  This can be achieved in a
> limited fashion in block ciphers in TLS, and various features of other
> protocols can be exploited to add padding.  Explicit support for
> padding is included in HTTP/2, TLS 1.3, and some other protocols.
>
> Use of multiplexed protocols can confound traffic analysis by
> combining data from multiple discrete events.  However, multiplexed
> protocols depend on flow control, which can be exploited to reveal
> information (see [HEIST]).

Thanks is good text to have as part of the changes and problem statement.

> ```
>
> Citations for the above (sorry, rough):
>
>   NETFLIX=DOI.10.1145/3029806.3029821
>   CLINIC:
>     title: "I Know Why You Went to the Clinic: Risks and Realization
> of HTTPS Traffic Analysis"
>     author:
>       - ins: B. Miller
>       - ins: L. Huang
>       - ins: A. D. Joseph
>       - ins: J. D. Tygar
>     date: 2014-03-03
>     target: "https://arxiv.org/abs/1403.0297"
>   HEIST: https://www.blackhat.com/docs/us-16/materials/us-16-VanGoethem-HEIST-HTTP-Encrypted-Information-Can-Be-Stolen-Through-TCP-Windows-wp.pdf
>

Thanks.

>
>>>> Section 7
>>>>
>>>> This section is duplicative of much of the rest of the document.  I
>>>> realize that
>>>> editing is hard, but see my earlier comments about structure.
>>
>> This text was the appendix, but moved to section 7 per IESG review and
>> discuss.  It was the mobile operator view.
>
> It's valuable information, sure, but hard to use.  I can see why the
> IESG thought that it needed to be in the body, as there are quite a
> few new use cases.

We'll be working on this soon, maybe in -13, maybe -12, not sure yet.
>
>>>> Section 8
>>>>
>>>> I generally agree with the first statement here, but after having read the
>>>> document, I could take away some very different views on what the
>>>> "problems at
>>>> hand" actually are.  I suspect that different people will have very
>>>> different
>>>> takeaways.
>>>>
>>>> The conclusion section of a document is not the right place to start
>>>> introducing
>>>> new information, particularly information relevant to RFC 2804.
>>
>> Should we move this to the introduction perhaps to help with context setting?
>
> The bit about surveillance programs and lawful intercept really need
> to be in the relevant sections of the body (that was the "new
> information" I referred to).  I agree that it would be good to promote
> the first statement to the introductory material.

Noted, thanks.

>
>>>> Not sure where this is going:
>>>>
>>>>    Terrorists and criminals have been using encryption for many years.
>>>>
>>>> Because it's disconnected from the remainder of the paragraph.  If you are
>>>> going
>>>> to invoke the T-word, you had better have a strong argument to make.  On
>>>> the
>>>> final sentence of that paragraph, the subject ("This") is unclear.
>>>>
>>
>> Sure, the point was that their use of encryption is not a
>> justification argue any of the improvements to crypto for the general
>> population.  Incident handlers know full well that encryption has been
>> in place for a long time by these users.  Essentially, it's not an argument that
>> hold muster.
>
> Yeah, as before, when it comes to discussion of lawful intercept, I
> would prefer to have that in the body of the document.  Preferably
> without mentioning why it happens, because that avoids the emotive
> topics.

OK, l think about this more.  Thanks for your review and proposed text.



-- 

Best regards,
Kathleen


From nobody Wed Apr 19 11:35:44 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3FAB129BF0 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 11:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 Wr3C8ubvxXJG for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 11:35:40 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A483129BE6 for <ietf@ietf.org>; Wed, 19 Apr 2017 11:35:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=126; q=dns/txt; s=iport; t=1492626940; x=1493836540; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=71wASYSOI7l+CNN+X+CD7kTv/S9hZFOninKkhh/jLKo=; b=AGa4kaOeG2txrIspd97RaAAvrkazVuCm2N29w0vBt/6PavAFuM3/CVZx gJ6Vyp7YK/FSlZ30t8Ghf0+g0WV+J2A9/PabXGs631+qSICJX1V0pq2z8 QLY965W8KULpvzhk3oDVJxLBUE98mTFk9c8tXuoDBvArNUcOyctHGZ+Rx g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CHAgAgrPdY/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDWEcosIplKCDy6KPBcBAgEBAQEBAQFrKIU/FXYCJgJfDQgBAYo?= =?us-ascii?q?VDpozkAiCJosjAQEIAQEBAR8FgQuFSIIIikuCXwEEizmRdpJ8gWgBiQaGXYtzi?= =?us-ascii?q?B4gATaBBSYdCBgVhys+iUoBAQE?=
X-IronPort-AV: E=Sophos;i="5.37,222,1488844800"; d="scan'208";a="651262479"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2017 18:35:36 +0000
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v3JIZZlN027450 for <ietf@ietf.org>; Wed, 19 Apr 2017 18:35:36 GMT
To: IETF-Discussion list <ietf@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Subject: Blog: YANG Catalog Latest Development (IETF 98 Hackathon)
Message-ID: <ca48b109-bc29-771f-40ed-5174f051ed55@cisco.com>
Date: Wed, 19 Apr 2017 20:35: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
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/brpl9etI1TlElE3g5gMRIPGrGvQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 18:35:43 -0000

Dear all,

https://www.ietf.org/blog/2017/04/yang-catalog-latest-development-ietf-98-hackathon/
Enjoy.

Regards, Benoit


From nobody Wed Apr 19 12:22:18 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 591A4129C1A; Wed, 19 Apr 2017 12:22:11 -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, RCVD_IN_DNSWL_MED=-2.3, 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 IFzqeXD2KAZL; Wed, 19 Apr 2017 12:22:10 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 DB24D129557; Wed, 19 Apr 2017 12:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3JJM6VE017168; Wed, 19 Apr 2017 21:22:06 +0200 (CEST)
Received: from [192.168.217.113] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w7X1p4yfgzDH3W; Wed, 19 Apr 2017 21:22:06 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149179722452.3118.982908107963516290@ietfa.amsl.com>
Date: Wed, 19 Apr 2017 21:22:05 +0200
X-Mao-Original-Outgoing-Id: 514322525.709632-e6c608bc5c2ecfb6a3a2b1b6084beadb
Content-Transfer-Encoding: quoted-printable
Message-Id: <C011A48B-7865-4557-A9EA-7CE79C790762@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com>
To: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, hybi@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d9RldKpO4wmHz7nCoYzk5-PPVxY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 19:22:11 -0000

On Apr 10, 2017, at 06:07, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
> URI, using a well-known URI in the "wss" scheme. However, "wss" is not
> defined to use well-known URIs, so this is an invalid use.

Clearly, this is a bug in draft-ietf-core-coap-tcp-tls-07.

I have argued that underlying this is an omission in RFC 6455:

ws:/wss: URIs are translated into http:/https: URIs, and the well-known =
space is already reserved in the latter, so it would be nonsensical to =
try to use RFC 5785 /.well-known for something else in the ws:/wss: URI =
schemes.

Maybe there wasn=E2=80=99t a use case for well-known URIs in WebSockets =
before, but there is one now, and we would like to remedy this omission =
in the procedurally simplest possibly way.

So I am proposing to add RFC 5785=E2=80=99s well-known URI mechanism to =
these URI schemes in the document that needs it, =
draft-ietf-core-coap-tcp-tls, which by that updates RFC 6455.

Are there any objections to this procedure?

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr 19 12:32:46 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9170129B0D; Wed, 19 Apr 2017 12:32:43 -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, RCVD_IN_DNSWL_MED=-2.3, 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 L2t_a9dboMM0; Wed, 19 Apr 2017 12:32:42 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 49DCE128C83; Wed, 19 Apr 2017 12:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3JJWb0V025914; Wed, 19 Apr 2017 21:32:38 +0200 (CEST)
Received: from [192.168.217.113] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w7XFx5FkyzDH3d; Wed, 19 Apr 2017 21:32:37 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C011A48B-7865-4557-A9EA-7CE79C790762@tzi.org>
Date: Wed, 19 Apr 2017 21:32:37 +0200
X-Mao-Original-Outgoing-Id: 514323157.104291-7d2be15871210d08ee22cfcf0d7a07e1
Content-Transfer-Encoding: quoted-printable
Message-Id: <289231B4-3335-4CC1-A285-68E1F301360C@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <C011A48B-7865-4557-A9EA-7CE79C790762@tzi.org>
To: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, hybi@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q85pS-1-AHkK2cwop56YbM63T20>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 19:32:44 -0000

On Apr 19, 2017, at 21:22, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> So I am proposing to add RFC 5785=E2=80=99s well-known URI mechanism =
to these URI schemes in the document that needs it, =
draft-ietf-core-coap-tcp-tls, which by that updates RFC 6455.

Forgot to add the pointer to the simple fix text:

https://github.com/core-wg/coap-tcp-tls/pull/128/files

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr 19 15:50:02 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5991273E2 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 15:50:00 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 Hl8cUdsEyt-J for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 15:49:58 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E44C41293D9 for <ietf@ietf.org>; Wed, 19 Apr 2017 15:49:57 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id BE35C58C594; Thu, 20 Apr 2017 00:49:51 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id A6744B0BD4F; Thu, 20 Apr 2017 00:49:51 +0200 (CEST)
Date: Thu, 20 Apr 2017 00:49:51 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
Message-ID: <20170419224951.GG5937@faui40p.informatik.uni-erlangen.de>
References: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es> <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de> <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SaRMNJ7oLnQyaYhqv07dSSDfsvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 22:50:00 -0000

Jordi,

None of the URLs seems to contradict that english is the most widely spoken second language.
And you also did not make an argument why it would make more sense to select the language
based on first language vs. second language speakers.

Also note that "second language" is just a good starting point. More importantly,
you want to have some common language in a professional area. And try to change that slower
than average human lifetime, so that professional experts are not rendered useless because
they can not learn another language at higher age.

In computer/networking etc. this is english. That has mostly historical reasons,
but IMHO its quite a good choice: It is easier to learn, and there is a high tolerance
for even mediocre language proficiencies in countries that commonly use it. To put it
into the original context of this thread: Only in the USA can you be interrogated and
potentially thrown out of the country by an immigrations officer that speaks the native
language worse than you!

Or you can just count the languages used in open source code comments on the Internet ;-)

Cheers
    Toerless

On Wed, Apr 19, 2017 at 11:01:37AM +0200, JORDI PALET MARTINEZ wrote:
> The problem comes from non-being a native speaker, as definitively that means that many times you ???translate??? from your mother tongue. And in this case, it seems, according to many sources, English and Chinese is declining across the time vs Spanish. Most of the sources state that Spanish is the 2nd one right now, some indicate it is Hindi, but English is always after Spanish (again, native speakers):
> 
> https://www.tomedes.com/top-10-languages-natively-spoken.php
> 
> http://www.vistawide.com/languages/top_30_languages.htm
> 
> https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers
> 
> https://en.wikipedia.org/wiki/Linguistic_demography
> 
> https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers
> 
> The latest info from 2016, which I???ve found only in spanish, seems to confirm the trend and in 2016 the censed number of native spanish speakers raised to 472 millions, 567 as second language, which agains confirms Chinesse being the first, Spanish the second (7,8% of total population).
> 
> http://www.cervantes.es/imagenes/File/prensa/EspanolLenguaViva16.pdf
> 
> Regards,
> Jordi
>  
> 
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Toerless Eckert <tte@cs.fau.de>
> Responder a: <tte@cs.fau.de>
> Fecha: martes, 18 de abril de 2017, 23:09
> Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
> CC: "ietf@ietf.org" <ietf@ietf.org>
> Asunto: Re: Update on feedback on US-based meetings, and IETF 102
> 
>     On Sat, Apr 15, 2017 at 10:54:09PM +0200, JORDI PALET MARTINEZ wrote:
>     > This shows something that I believe most of the native English IETF participants usually don???t realize when having discussion (I???m referring here in general, also technical discussions) with non-native speakers, and how difficult is for the others. Maybe we should switch to Chinese as the default IETF language, or Spanish, as they have more speakers worldwide than English!
>     
>     https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers
>     
>     According to that page, spanish does not have more speakers worldwide than english, but
>     rather the opposite. And IMHO, the relevant number is really just the number of L2
>     (second language) speakers, and thats lead by english, followed by malay, french,
>     mandarin, arabic, hindi, russian, urdu, swahili and then spanish!
>     
>     > I???m still believe that IAOC attitude is not justified at all, and if we don???t have answers from them by next Monday, we should consider a recall process. Hopefully is not the case.
>     
>     What do you think is the IAOC attitude ? All i read was very noncommittal and "we
>     still collect information".
>     
>     I do not even know what the metric for selection is. I hope it is not to make the
>     most vocal mailing list participants most happy. I would start with excluding the least
>     number of candidate participants excluded by travel policies, then the lowest price for
>     median particiants (flight, hotel, food) and then most convenient. I think
>     IAOC somehow takes these factors into account, but i can not remember that they did send 
>     their most concrete data for these factors for various countries to the mailing list.
>     
>     Cheers
>         Toerless
>     
>     
>     > Regards,
>     > Jordi
>     > 
>     > -----Mensaje original-----
>     > De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MARTINEZ <jordi.palet@consulintel.es>;
>     > Responder a: < jordi.palet@consulintel.es>;
>     > Fecha: viernes, 14 de abril de 2017, 01:24
>     > Para: <ietf@ietf.org>;
>     > Asunto: Re: Update on feedback on US-based meetings, and IETF 102
>     > 
>     > Well, for some countries what Trump said, has already been a fact, for example the prohibition to have computers on board. Is not that the case?
>     > 
>     > Whatever we want to decide, cancel SF or not, it may highly depend on budget, we like it or not. And that means that we need answers:
>     > 
>     >     If we cancel San Francisco, how much that is going to cost to the IETF for each of two planned meetings?
>     >     
>     >     Can we cancel the actual hotel contract considering the new US situation? If not, has this been considered for new contracts to avoid this problem?
>     >     
>     >     Otherwise there is any reason that can justify the lack of transparency in this?
>     > 
>     > The problem is so big for this community that I don???t even agree that the IAOC should take the decision. It must be a collective one, especially when the IAOC is demonstrating thru facts that they don???t care that we are discussing and wasting our time without the minimum relevant data, this is disrespectful and even more, not responding to emails since even since years ago, shows lack of education 
>     > 
>     > Regards,
>     > Jordi
>     > 
>     > 
>     > 
>     > 
>     > **********************************************
>     > 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 use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
>     > 
>     > 
>     
>     -- 
>     ---
>     tte@cs.fau.de
>     
>     
>     
> 
> 
> 
> **********************************************
> 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 use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 

-- 
---
tte@cs.fau.de


From nobody Thu Apr 20 02:57:37 2017
Return-Path: <prvs=12830127ab=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6A4012EC4E for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 02:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySls4PktYOZk for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 02:57:33 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F9112EC51 for <ietf@ietf.org>; Thu, 20 Apr 2017 02:57:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492682251; x=1493287051; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=+vd4qC7kZad1j6pYJgtKuutPQ /lfs1KkPrRoiEbp9r0=; b=IIGDZp/5uBWf6GcAKgflV/6DhTxExldUYirjFJoBo poGoBfHuHm6ea3UOzqhuaXyOiT+K2bvtwMDUfxNrCu7GrM1kUeEYkKozgKm93FH2 kZGWDruTjpsrQqdrFGVUR3fllH2YmxCcIqhUAaoQz8vKVdbNXVk3j1dyJA1Z3kLq ag=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=mBJIB/7DIFgHTt4VBcynErKJdkh3oJsYB6/ZJOpAF0W1vGfC2Qv/jKWDdhXS sObeS1NfGf9CEgZ3yNoAyG1cKi/7lhRIMja7FSQIBLZr9TLhQZByfesxS pChjH+v39Qr1g9d1A8qrl2PV7pm5t7GKicDF1kdNgnMKF2YGcNPs3U=;
X-MDAV-Processed: mail.consulintel.es, Thu, 20 Apr 2017 11:57:31 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 20 Apr 2017 11:57:29 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005411580.msg for <ietf@ietf.org>; Thu, 20 Apr 2017 11:57:29 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170420:md50005411580::ajECgwYIdFAcVMlw:00001ccX
X-Return-Path: prvs=12830127ab=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Thu, 20 Apr 2017 11:57:28 +0200
Subject: Re: Update on feedback on US-based meetings, and IETF 102
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <407F1142-3EE1-49EB-A331-3A02F0FED6B7@consulintel.es>
Thread-Topic: Update on feedback on US-based meetings, and IETF 102
References: <E22598F5-BA60-43E2-BBB3-9333F573D3E1@consulintel.es> <20170418210950.GA5937@faui40p.informatik.uni-erlangen.de> <5D2AE320-7824-4AE1-94B1-526650F0F48C@consulintel.es> <20170419224951.GG5937@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20170419224951.GG5937@faui40p.informatik.uni-erlangen.de>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MO2PBLa6if3zfR7S12CfNtOAYac>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 09:57:36 -0000

I guess you=E2=80=99re not reading the =E2=80=9CNATIVE=E2=80=9D (as I indic=
ated in all my messages on this) speaker=E2=80=99s column, which is the peo=
ple that is closer to the 100% comprehension of a given language.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Toerless Eckert <tte@cs.fau.d=
e>
Responder a: <tte@cs.fau.de>
Fecha: jueves, 20 de abril de 2017, 0:49
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: Re: Update on feedback on US-based meetings, and IETF 102

    Jordi,
   =20
    None of the URLs seems to contradict that english is the most widely sp=
oken second language.
    And you also did not make an argument why it would make more sense to s=
elect the language
    based on first language vs. second language speakers.
   =20
    Also note that "second language" is just a good starting point. More im=
portantly,
    you want to have some common language in a professional area. And try t=
o change that slower
    than average human lifetime, so that professional experts are not rende=
red useless because
    they can not learn another language at higher age.
   =20
    In computer/networking etc. this is english. That has mostly historical=
 reasons,
    but IMHO its quite a good choice: It is easier to learn, and there is a=
 high tolerance
    for even mediocre language proficiencies in countries that commonly use=
 it. To put it
    into the original context of this thread: Only in the USA can you be in=
terrogated and
    potentially thrown out of the country by an immigrations officer that s=
peaks the native
    language worse than you!
   =20
    Or you can just count the languages used in open source code comments o=
n the Internet ;-)
   =20
    Cheers
        Toerless
   =20
    On Wed, Apr 19, 2017 at 11:01:37AM +0200, JORDI PALET MARTINEZ wrote:
    > The problem comes from non-being a native speaker, as definitively th=
at means that many times you ???translate??? from your mother tongue. And i=
n this case, it seems, according to many sources, English and Chinese is de=
clining across the time vs Spanish. Most of the sources state that Spanish =
is the 2nd one right now, some indicate it is Hindi, but English is always =
after Spanish (again, native speakers):
    >=20
    > https://www.tomedes.com/top-10-languages-natively-spoken.php
    >=20
    > http://www.vistawide.com/languages/top_30_languages.htm
    >=20
    > https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_s=
peakers
    >=20
    > https://en.wikipedia.org/wiki/Linguistic_demography
    >=20
    > https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_sp=
eakers
    >=20
    > The latest info from 2016, which I???ve found only in spanish, seems =
to confirm the trend and in 2016 the censed number of native spanish speake=
rs raised to 472 millions, 567 as second language, which agains confirms Ch=
inesse being the first, Spanish the second (7,8% of total population).
    >=20
    > http://www.cervantes.es/imagenes/File/prensa/EspanolLenguaViva16.pdf
    >=20
    > Regards,
    > Jordi
    > =20
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Toerless Eckert <tte@cs=
.fau.de>
    > Responder a: <tte@cs.fau.de>
    > Fecha: martes, 18 de abril de 2017, 23:09
    > Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
    > CC: "ietf@ietf.org" <ietf@ietf.org>
    > Asunto: Re: Update on feedback on US-based meetings, and IETF 102
    >=20
    >     On Sat, Apr 15, 2017 at 10:54:09PM +0200, JORDI PALET MARTINEZ wr=
ote:
    >     > This shows something that I believe most of the native English =
IETF participants usually don???t realize when having discussion (I???m ref=
erring here in general, also technical discussions) with non-native speaker=
s, and how difficult is for the others. Maybe we should switch to Chinese a=
s the default IETF language, or Spanish, as they have more speakers worldwi=
de than English!
    >    =20
    >     https://en.wikipedia.org/wiki/List_of_languages_by_total_number_o=
f_speakers
    >    =20
    >     According to that page, spanish does not have more speakers world=
wide than english, but
    >     rather the opposite. And IMHO, the relevant number is really just=
 the number of L2
    >     (second language) speakers, and thats lead by english, followed b=
y malay, french,
    >     mandarin, arabic, hindi, russian, urdu, swahili and then spanish!
    >    =20
    >     > I???m still believe that IAOC attitude is not justified at all,=
 and if we don???t have answers from them by next Monday, we should conside=
r a recall process. Hopefully is not the case.
    >    =20
    >     What do you think is the IAOC attitude ? All i read was very nonc=
ommittal and "we
    >     still collect information".
    >    =20
    >     I do not even know what the metric for selection is. I hope it is=
 not to make the
    >     most vocal mailing list participants most happy. I would start wi=
th excluding the least
    >     number of candidate participants excluded by travel policies, the=
n the lowest price for
    >     median particiants (flight, hotel, food) and then most convenient=
. I think
    >     IAOC somehow takes these factors into account, but i can not reme=
mber that they did send=20
    >     their most concrete data for these factors for various countries =
to the mailing list.
    >    =20
    >     Cheers
    >         Toerless
    >    =20
    >    =20
    >     > Regards,
    >     > Jordi
    >     >=20
    >     > -----Mensaje original-----
    >     > De: ietf <ietf-bounces@ietf.org>; en nombre de JORDI PALET MART=
INEZ <jordi.palet@consulintel.es>;
    >     > Responder a: < jordi.palet@consulintel.es>;
    >     > Fecha: viernes, 14 de abril de 2017, 01:24
    >     > Para: <ietf@ietf.org>;
    >     > Asunto: Re: Update on feedback on US-based meetings, and IETF 1=
02
    >     >=20
    >     > Well, for some countries what Trump said, has already been a fa=
ct, for example the prohibition to have computers on board. Is not that the=
 case?
    >     >=20
    >     > Whatever we want to decide, cancel SF or not, it may highly dep=
end on budget, we like it or not. And that means that we need answers:
    >     >=20
    >     >     If we cancel San Francisco, how much that is going to cost =
to the IETF for each of two planned meetings?
    >     >    =20
    >     >     Can we cancel the actual hotel contract considering the new=
 US situation? If not, has this been considered for new contracts to avoid =
this problem?
    >     >    =20
    >     >     Otherwise there is any reason that can justify the lack of =
transparency in this?
    >     >=20
    >     > The problem is so big for this community that I don???t even ag=
ree that the IAOC should take the decision. It must be a collective one, es=
pecially when the IAOC is demonstrating thru facts that they don???t care t=
hat we are discussing and wasting our time without the minimum relevant dat=
a, this is disrespectful and even more, not responding to emails since even=
 since years ago, shows lack of education=20
    >     >=20
    >     > Regards,
    >     > Jordi
    >     >=20
    >     >=20
    >     >=20
    >     >=20
    >     > **********************************************
    >     > IPv4 is over
    >     > Are you ready for the new Internet ?
    >     > http://www.consulintel.es
    >     > The IPv6 Company
    >     >=20
    >     > This electronic message contains information which may be privi=
leged or confidential. The information is intended to be for the use of the=
 individual(s) named above. If you are not the intended recipient be aware =
that any disclosure, copying, distribution or use of the contents of this i=
nformation, including attached files, is prohibited.
    >     >=20
    >     >=20
    >    =20
    >     --=20
    >     ---
    >     tte@cs.fau.de
    >    =20
    >    =20
    >    =20
    >=20
    >=20
    >=20
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >=20
    > This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the indiv=
idual(s) named above. If you are not the intended recipient be aware that a=
ny disclosure, copying, distribution or use of the contents of this informa=
tion, including attached files, is prohibited.
    >=20
    >=20
   =20
    --=20
    ---
    tte@cs.fau.de
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From jmoroney@hawaii.edu  Thu Apr 20 06:20:12 2017
Return-Path: <jmoroney@hawaii.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C05C127444 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 06:20:12 -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, 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=hawaii-edu.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 Lj0HQg-IbuKI for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 06:20:10 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::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 D9CD8128656 for <ietf@ietf.org>; Thu, 20 Apr 2017 06:20:09 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id c55so35475276wrc.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 06:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hawaii-edu.20150623.gappssmtp.com; s=20150623; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=inzN+FZT3yPofCgaKloioZ43+4vuUfhxlZhhBmp534A=; b=A/JFx2TYu34oegS4iu4T14wvc5oeAtYWcUJXGzd+txFqkcpgF2X+vMKGevEIHfj2zh 3b7eCUcbGnmt+2BY15f8+Q/WxB15O0XCOPe6rF9UvXfksJ209Z0a5B18C3iQwZ9odIxI 20BY3Be2fGAAnqXZp0WudA+IfXA71BWXApG3ZE3Bo7eaYimAtBDyM5g5yYn3mWUh4yqo BqcNEBjiKXPEW6YJudfPLf/7L02+gt3/83S/Xwy6faQ5qNVrtojaaZE6lmhURkzFUgzP npLR8Le3YKyftjTQ3SEJK5lEVgu8QutpPbIw4lYvh4a+vDNpPC2zy6QJhiZJcFfqqGYw zgZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=inzN+FZT3yPofCgaKloioZ43+4vuUfhxlZhhBmp534A=; b=gXHfm483ZO1zktU92kSQHdDUNgnzXfpQHKEkaVCrJJr3g7tY0VFe5Vywm+ISYuw7Cw p0piktXJQ9J8v8jOm+aQGuc1E7SjF3EqdwClmxUNMka+c76AGbLDCYl6BVNi+rIXP7OB 8gH+EU18bQU/NRmLOG/IUtqwJRVpLQ1+8/57R2ldOfbqwQf2Aiv6KvQ6xdEHSaBo06PS I0dHpJ7Bg/Gih5JT4x1HLbB1nM3IG+zJN5Hi7JkwgVBJFwCygwe9qrxeWRBGG9VvDviG lzCo0BOMKXPiajPhZ51XFNDOPba47M5d1CPdlDBB22jZ6ZZpJvW4QcEgpl1xku9y1UvJ p+YA==
X-Gm-Message-State: AN3rC/71KuW7NKhinNGOTrtcLs9GSoApxLx4v6dYcmcVuXjQ/eJZYUyq DAkSv21J0uukU8cHj2WfXIhv7FPyp3e70PgaLHw+en4IrsOBJsvOTZMApHpbdrND42EDBrjLBJp vp406ua4cFiBCSZGrdYXjxp5/xJKOn0PXKxq5rdC/BYm8
X-Received: by 10.223.172.165 with SMTP id o34mr8600553wrc.4.1492694407054; Thu, 20 Apr 2017 06:20:07 -0700 (PDT)
Received: from n142188.science.ru.nl (n142188.science.ru.nl. [131.174.142.188]) by smtp.gmail.com with ESMTPSA id v8sm7540613wrd.42.2017.04.20.06.20.05 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 06:20:06 -0700 (PDT)
From: Jon <jmoroney@hawaii.edu>
Subject: Why are mail servers not also key servers?
To: ietf@ietf.org
Message-ID: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Date: Thu, 20 Apr 2017 15:20:05 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JOg9VeOWlUSh-rs78sMvOk6y9jI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 13:21:15 -0000

Hi All,

I'm not sure if this is a topic which has already come up or not (I did
a simple search brought nothing up).

Anyway, the state of email security is still pretty poor despite much
low hanging fruit. PGP is great for those that use
it, but they are a small group. TLS seems to be the only wide spread
security implementation and I suspect that it has worked because it's
transparent to the end users. So, why hasn't key exchange been made to
be transparent? Why are (E)SMTP servers not also key servers? Have users
generate a key pair on registration, store those keys on the server (in
an encrypted archive), and make the public key available. A little
coding later and we've got key exchange and message confidentiality.

Some extra security can be had by giving mail servers their own keys
with which they can sign exchanges (and remember each other). TLS can be
used to as part of an initial key exchange if that is desired. Can
we not extend smtp again to include the necessary key exchange commands?
Is there any movement on this?

Jon



From nobody Thu Apr 20 07:22:42 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5D2413146A for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:22:40 -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, RP_MATCHES_RCVD=-0.001] 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 6fUGXTvAhsY5 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:22:25 -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 E72041296CF for <ietf@ietf.org>; Thu, 20 Apr 2017 07:22:24 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w81KT3kJPzD49; Thu, 20 Apr 2017 16:22:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492698141; bh=d8NRKWOMwQjidxEDAS/E5CaX8ewH78+E2NkqrOSoANc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=heU3/qTRHtYpd34YXpe3MAjq4WYIpqSlM73VSwFoEvPHc7CCx1fGm6GEugmVpEDGk lW8UDi1IQKDJhXR4U08zQjsibZrwIE9DlZJlG5xPeUqX8SwaxAKsX6aC1WmYZJR7my MLJOYpEsxFAqYd3+GPCPP03FP92WCkcMl9ft6KPo=
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 8RcRlpervUQK; Thu, 20 Apr 2017 16:22:19 +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; Thu, 20 Apr 2017 16:22:19 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C8C3F353643; Thu, 20 Apr 2017 10:22:17 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca C8C3F353643
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C2A5840D811F; Thu, 20 Apr 2017 10:22:17 -0400 (EDT)
Date: Thu, 20 Apr 2017 10:22:17 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Jon <jmoroney@hawaii.edu>
cc: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Message-ID: <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SOgKu17cTRbpYG4ul6x7b9r4hYU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 14:22:41 -0000

On Thu, 20 Apr 2017, Jon wrote:

> Why are (E)SMTP servers not also key servers?

You will find a history of that discussion in the dane archives.

Basically, it is the equivalent to the domain's DNS servers acting as
key servers, except that:

- SMTP is often blocked cross-domain, eg by ISPs, hotspot operators, etc
- SMTP failure cannot be distinguished from SMTP attacks, whereas DNSSEC
   based published keys (eg OPENPGPKEY and SMIMEA) can be detected when
   blocked (DNSSEC returns bogus or indeterminate results)
- Using public DNS to publish keys allows for a level of indirection,
   making targeted attacks much harder to do.

> generate a key pair on registration, store those keys on the server (in
> an encrypted archive), and make the public key available. A little
> coding later and we've got key exchange and message confidentiality.

SMTP servers could be key servers without having the private key of
individuals?

> Some extra security can be had by giving mail servers their own keys
> with which they can sign exchanges (and remember each other). TLS can be
> used to as part of an initial key exchange if that is desired. Can
> we not extend smtp again to include the necessary key exchange commands?

I believe there was a draft that tried to do something like this.

Paul


From nobody Thu Apr 20 07:29:56 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16A9713147C for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:29: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 Mob5OK3-9rR0 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:29:53 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::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 1344E13146A for <ietf@ietf.org>; Thu, 20 Apr 2017 07:29:52 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id o21so7808356wrb.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 07:29:52 -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=uLGWiuqn+B9qYAhhZjlyNV2izu/2cmFKnGqICCJzg4U=; b=VJHyCFhA4sC2iJeiz8yZzUuT1ZiC+FU1+KN+wQNY51YAbPiVehmngm5IbDOaSOkAtF HtBFPL4uk8zBm4WCnhdXZr1V4Sbvyy7HOMKPVb0yWNUbedRDTaNuj86DZRAt5VDmpWoi 0Ak8/uUZOLlKVgtEcldg02q9RlOtvi/7k2GrKvtJQXJgK6O0r+DmheneySZdn1vyrrTE jpnE8wEtIyKxAfxxhMMV5ZuzeBlCcStS1f03Ugm5DL52y4foee1F+G+nimYSTa9stq7t 00EPN+ygx2ieVKFTaCBTKYXOVlxmbAdbXhkkdQ4BcPLPwK/4Skeql3DgFhs78xhNrguI 4GFw==
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=uLGWiuqn+B9qYAhhZjlyNV2izu/2cmFKnGqICCJzg4U=; b=nErmY7XPthzJwh83u8ShQMD9QXp4Dk1BJX+BDMZv9S0nPGvs3MPIoheV4Q7DqT7scc BjbE4/Bu/ndJbercUZm7g8xu8TFo1PvkdLQKnOXByu5I74u65xJlVzvBjd9nWdfkGifB KfhfQQqxIhvXVOwPjkZouIZwHLsqbZu01ePOILbk1+VqeADiQXv7XqMg83Ny9xkDaQ2f 6XQDNAs5zd/yCL4z+DcwWjgPOfPV/no50nTUmIhwR2Ttu32acAnnTsFjWPworWKXBsqH V8/t6s3SBQW+sJbeGTWjRJjcfs5CkP1zbCj2woptOhjevJp7Aa2YXCteewWZoSi1j8q8 Dlqw==
X-Gm-Message-State: AN3rC/4F6QbJAvzx/vQ9BjkWO2RCXmso8YJ8c7avoLIYE04WhO1WXk1l 0WTNE+41R8k/JzcSJJM=
X-Received: by 10.223.150.121 with SMTP id c54mr7840698wra.202.1492698591467;  Thu, 20 Apr 2017 07:29:51 -0700 (PDT)
Received: from [172.24.251.229] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id o9sm8318612wmd.4.2017.04.20.07.29.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 07:29:50 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5196DFAF-D6CF-4F51-A3C6-6CF3A29C157E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Why are mail servers not also key servers?
Date: Thu, 20 Apr 2017 17:29:46 +0300
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Cc: ietf@ietf.org
To: Jon <jmoroney@hawaii.edu>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tvvhS99tYRiOFXWP7-OM7TRczfg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 14:29:55 -0000

--Apple-Mail=_5196DFAF-D6CF-4F51-A3C6-6CF3A29C157E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_50F60B20-F488-4B69-BA9F-85908602389C"


--Apple-Mail=_50F60B20-F488-4B69-BA9F-85908602389C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 20 Apr 2017, at 16:20, Jon <jmoroney@hawaii.edu> wrote:

> Hi All,
>=20
> I'm not sure if this is a topic which has already come up or not (I =
did
> a simple search brought nothing up).
>=20
> Anyway, the state of email security is still pretty poor despite much
> low hanging fruit. PGP is great for those that use
> it, but they are a small group. TLS seems to be the only wide spread
> security implementation and I suspect that it has worked because it's
> transparent to the end users. So, why hasn't key exchange been made to
> be transparent? Why are (E)SMTP servers not also key servers? Have =
users
> generate a key pair on registration, store those keys on the server =
(in
> an encrypted archive), and make the public key available. A little
> coding later and we've got key exchange and message confidentiality.
>=20
> Some extra security can be had by giving mail servers their own keys
> with which they can sign exchanges (and remember each other). TLS can =
be
> used to as part of an initial key exchange if that is desired. Can
> we not extend smtp again to include the necessary key exchange =
commands?
> Is there any movement on this?
>=20

Hi, Jon

I=E2=80=99m sure such things have been considered in the past, and for =
certain SMTP could be extended. I can think of a few complications right =
of the top of my head. There are undoubtedly others:

1. People use multiple MUAs. For this account I use this Mac MUA, a =
phone MUA, and occasionally the web-based MUA. I=E2=80=99d need to share =
the private key to receive encrypted mail on all three. Doing it in the =
browser is a hard problem.

2. There=E2=80=99s the administrative problem of tying the SMTP server =
to whatever server is serving the public keys. HTTPS from the same IP =
address? New special DNS SRV record somehow tied to the gmail.com =
<http://gmail.com/> MX record?

3. How much to you trust your email provider? Because they could =
trivially serve the wrong public key and intercept your traffic.

Yoav



--Apple-Mail=_50F60B20-F488-4B69-BA9F-85908602389C
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; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><div class=3D"">On 20 Apr 2017, at 16:20, =
Jon &lt;<a href=3D"mailto:jmoroney@hawaii.edu" =
class=3D"">jmoroney@hawaii.edu</a>&gt; wrote:</div><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D"">Hi All,<br class=3D""><br class=3D"">I'm not sure if this is =
a topic which has already come up or not (I did<br class=3D"">a simple =
search brought nothing up).<br class=3D""><br class=3D"">Anyway, the =
state of email security is still pretty poor despite much<br =
class=3D"">low hanging fruit. PGP is great for those that use<br =
class=3D"">it, but they are a small group. TLS seems to be the only wide =
spread<br class=3D"">security implementation and I suspect that it has =
worked because it's<br class=3D"">transparent to the end users. So, why =
hasn't key exchange been made to<br class=3D"">be transparent? Why are =
(E)SMTP servers not also key servers? Have users<br class=3D"">generate =
a key pair on registration, store those keys on the server (in<br =
class=3D"">an encrypted archive), and make the public key available. A =
little<br class=3D"">coding later and we've got key exchange and message =
confidentiality.<br class=3D""><br class=3D"">Some extra security can be =
had by giving mail servers their own keys<br class=3D"">with which they =
can sign exchanges (and remember each other). TLS can be<br =
class=3D"">used to as part of an initial key exchange if that is =
desired. Can<br class=3D"">we not extend smtp again to include the =
necessary key exchange commands?<br class=3D"">Is there any movement on =
this?<br class=3D""><br class=3D""></div></div></blockquote><br =
class=3D""></div><div>Hi, Jon</div><div><br class=3D""></div><div>I=E2=80=99=
m sure such things have been considered in the past, and for certain =
SMTP could be extended. I can think of a few complications right of the =
top of my head. There are undoubtedly others:</div><div><br =
class=3D""></div><div>1. People use multiple MUAs. For this account I =
use this Mac MUA, a phone MUA, and occasionally the web-based MUA. I=E2=80=
=99d need to share the private key to receive encrypted mail on all =
three. Doing it in the browser is a hard problem.</div><div><br =
class=3D""></div><div>2. There=E2=80=99s the administrative problem of =
tying the SMTP server to whatever server is serving the public keys. =
HTTPS from the same IP address? New special DNS SRV record somehow tied =
to the <a href=3D"http://gmail.com" class=3D"">gmail.com</a>&nbsp;MX =
record?</div><div><br class=3D""></div><div>3. How much to you trust =
your email provider? Because they could trivially serve the wrong public =
key and intercept your traffic.</div><div><br =
class=3D""></div><div>Yoav</div><div><br class=3D""></div><br =
class=3D""></body></html>=

--Apple-Mail=_50F60B20-F488-4B69-BA9F-85908602389C--

--Apple-Mail=_5196DFAF-D6CF-4F51-A3C6-6CF3A29C157E
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-----

iQEcBAEBCgAGBQJY+MXbAAoJELhJCxUKWMyZnOIH/jVdN0eIZS70DKJswdzqPMHT
6r8QLq6/V86fjM005qT297GEpwCcn8k1waV+hytaTU6z4x4O5Pxu6CRSGIJJs9eg
vlWzfFYSQZj5gOVY99EQmc5McksxCAXEUCLEih/yx6xwTXtbgr3919v/nrep8OkJ
HgbQ7fJ+5SR8hYAjPBM1DQKAsjRfkKgOX7mR5Zg0iVlz0esInKiVb+Xkar9Pxs33
TR6cMSxCQ2Ib4J9EqCM0NZr0QnvvJugmvkRIwgJdLtEdTkN3X0VG73HF3FpA7+fG
jRcUWXd2z+LFUT40KZb79RlviXl3sOjVYMU4P+kmo+fTnmaWf8XjeIPCm+zDQyA=
=vXwL
-----END PGP SIGNATURE-----

--Apple-Mail=_5196DFAF-D6CF-4F51-A3C6-6CF3A29C157E--


From nobody Thu Apr 20 07:36:12 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB023127B60 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:36:10 -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 yiXVFOXLefPl for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:36:08 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 8B24D129543 for <ietf@ietf.org>; Thu, 20 Apr 2017 07:36:07 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id z109so37070699wrb.1 for <ietf@ietf.org>; Thu, 20 Apr 2017 07:36:07 -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=/Ao1SJBElU7GJykXu3E8EOxuUzss4/3zdADxGdAUYYo=; b=OvNACYQ9QfAvhY6YaFQMAX8MXK2FvFJGNR5tIg82VRjuXQCnsQaLiMMujIGNnQqcTt bg5TqRb1MAYRMGmvZPC4alONBi+cV0GeFUZsTroMfS40ZdtrvuKjqi0/DKEkKBS8B3OK nC8wnDwjZ9JJRyMZ2sebxnveicQrD6YFtcMzge/I4wJs1ajEhFtDzrEwp3Agjr4XeLuI g7/7fYIJdCYuYGWHnKUbHJdjT/NDUMEERn7ftGc8shLMtv0q5YLqzybeunvNdNjXEx2J VDRl1LpADjUJXwDCH1Z1jQre0EzeiSL8k6XqTkxckNwEmatabquRgGB5Kh7h8RjuRLUj Hceg==
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=/Ao1SJBElU7GJykXu3E8EOxuUzss4/3zdADxGdAUYYo=; b=rMTnhSLzyvw9sZij3cBnRFEynMoklMzlBw8AqglRQPBj3pqZdQnVKC4+qURYGQ20s+ 7NFu8oA0raYek9IJPQr4oUCrCKhY5BVIQJZgzh/ViV+9VJCDwb6OFFPrV7JVUtUSfqjJ M+sNVvTggmD9KgRfiQMnemPB37ut/CAz6Xv/8bbqOJ3GJZpQHq6TuVYdsS6afYSKiP/S wGIFsth9eiWxJ9g61p9ouPmvUmWWsxkkqdigGc1wPk0SrEl00VfaUMAZZybI5U3abEd6 alkOuA4+u2fqU6yasmNQU4tW74nDAmWkoXBxJxpQ13V0mcLiQiwJNsG3tuSToicr6EJS 6jFA==
X-Gm-Message-State: AN3rC/633WGvA4hiy2mtuJVZOaArZaSdkWBHYkWCujOcgHQ/Wed3K2yI LRH9rl5iSR8MUQ==
X-Received: by 10.223.150.179 with SMTP id u48mr2186741wrb.195.1492698966117;  Thu, 20 Apr 2017 07:36:06 -0700 (PDT)
Received: from [172.24.251.229] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id w10sm23784677wmw.14.2017.04.20.07.36.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 07:36:05 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DBD20EB7-086A-442F-A1AE-431628FC611E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Why are mail servers not also key servers?
Date: Thu, 20 Apr 2017 17:36:03 +0300
In-Reply-To: <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca>
Cc: Jon <jmoroney@hawaii.edu>, ietf@ietf.org
To: Paul Wouters <paul@nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/It16xwwaFZ9xfg8Ylq3Cu62Q0vo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 14:36:11 -0000

--Apple-Mail=_DBD20EB7-086A-442F-A1AE-431628FC611E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7013EDDB-DA26-4332-8E8E-24E7621F1A29"


--Apple-Mail=_7013EDDB-DA26-4332-8E8E-24E7621F1A29
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 20 Apr 2017, at 17:22, Paul Wouters <paul@nohats.ca> wrote:

>=20
>> generate a key pair on registration, store those keys on the server =
(in
>> an encrypted archive), and make the public key available. A little
>> coding later and we've got key exchange and message confidentiality.
>=20
> SMTP servers could be key servers without having the private key of
> individuals?

Sure. If they double as HTTPS servers.

I want to send you an email, so I type =E2=80=9Cpaul@nohats.ca =
<mailto:paul@nohats.ca>=E2=80=9D in the To: field, and my MUA goes to =
https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/paul =
<https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/paul> and =
that gets your public key.

And now my MUA can encrypt.  And it all works, as long as we trust =
nohats.ca <http://nohats.ca/> (and conversely gmail.com =
<http://gmail.com/>) and as long as you have a copy of your private key =
on every single MUA that you use.

Small assumptions, no?

Yoav


--Apple-Mail=_7013EDDB-DA26-4332-8E8E-24E7621F1A29
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; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><div class=3D"">On 20 Apr 2017, at 17:22, =
Paul Wouters &lt;<a href=3D"mailto:paul@nohats.ca" =
class=3D"">paul@nohats.ca</a>&gt; wrote:</div><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">generate =
a key pair on registration, store those keys on the server (in<br =
class=3D"">an encrypted archive), and make the public key available. A =
little<br class=3D"">coding later and we've got key exchange and message =
confidentiality.<br class=3D""></blockquote><br class=3D"">SMTP servers =
could be key servers without having the private key of<br =
class=3D"">individuals?<br class=3D""></div></div></blockquote></div><br =
class=3D""><div class=3D"">Sure. If they double as HTTPS =
servers.</div><div class=3D""><br class=3D""></div><div class=3D"">I =
want to send you an email, so I type =E2=80=9C<a =
href=3D"mailto:paul@nohats.ca" class=3D"">paul@nohats.ca</a>=E2=80=9D in =
the To: field, and my MUA goes to <a =
href=3D"https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/paul" =
class=3D"">https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/pau=
l</a>&nbsp;and that gets your public key.</div><div class=3D""><br =
class=3D""></div><div class=3D"">And now my MUA can encrypt. &nbsp;And =
it all works, as long as we trust <a href=3D"http://nohats.ca" =
class=3D"">nohats.ca</a>&nbsp;(and conversely <a href=3D"http://gmail.com"=
 class=3D"">gmail.com</a>) and as long as you have a copy of your =
private key on every single MUA that you use.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Small assumptions, no?</div><div =
class=3D""><br class=3D""></div><div class=3D"">Yoav</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_7013EDDB-DA26-4332-8E8E-24E7621F1A29--

--Apple-Mail=_DBD20EB7-086A-442F-A1AE-431628FC611E
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-----

iQEcBAEBCgAGBQJY+MdTAAoJELhJCxUKWMyZkYsH/33R/sOj5vSb8NfB4OgfVPmX
prAJQCylrWeOZ7lbj68HL5TKpLBwl+NHqMWCxKV6qK8FVN0ADR/ZCJVAfstUYvAw
8IsNcQ6BZQaW+iYHdJqV8DFKxrNXFrdmKvRpqGSrkpMgLpl0EC72ZeIorj8UEpTG
6K1urbmvz7T7AA/dCMHGgrn4YXS0JKwtYNkoqd2nSu81+dzxVUl/qvDv7PVSCD1l
ICyP4qkD+qsW1qUdBtEYIrPKYBBWLxiTGqRl/c1JGW8mro1MrBYdU7YfS2QWi8lA
yy+200r4YoV6LFKvqLnLkGBp/zvgOPGkP7neB/4EcA7W3B3PxZ1UgVdvtz55hCA=
=Tc+A
-----END PGP SIGNATURE-----

--Apple-Mail=_DBD20EB7-086A-442F-A1AE-431628FC611E--


From nobody Thu Apr 20 07:58:28 2017
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71112129AAA; Thu, 20 Apr 2017 07:58:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Martinez <carlosm3011@gmail.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-avtcore-rfc5285-bis.all@ietf.org, ietf@ietf.org, avt@ietf.org
Subject: Opsdir last call review of draft-ietf-avtcore-rfc5285-bis-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149270030040.22369.16996023581425987557@ietfa.amsl.com>
Date: Thu, 20 Apr 2017 07:58:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZzrUELSdcY13K7bVm4dtfavHSzw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 14:58:20 -0000

Reviewer: Carlos Martinez
Review result: Ready

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

With the caveat that I'm not fully familiar with the topic, I have not
found any serious issues with the document and I believe the document
to be ready.

I found the document well-written and providing adequate references
along the text. Being a -bis document I believe this is particularly
important.

Thanks,

-Carlos


From nobody Thu Apr 20 08:08:32 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA97F129A97 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 08:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.759
X-Spam-Level: 
X-Spam-Status: No, score=-0.759 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NUMERIC_HTTP_ADDR=1.242, RP_MATCHES_RCVD=-0.001] 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 LD6bszptEsdD for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 08:08:29 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.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 D7A461293E0 for <ietf@ietf.org>; Thu, 20 Apr 2017 08:08:28 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w82Lb42WPzD23; Thu, 20 Apr 2017 17:08:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492700903; bh=P6Xr48yMPXIzZutVizOE7mXEvLlCqdmxhNU30a6tTbg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=kfa0jhTAABgCgJFyzGCbdlAed7E72V7EikKujKjF3F9WxEiLoOAQmgIZ2OxTvZkbt i+9Vue0RUeiGBRQs4WRiyM2brCC8KpxO5S5JcD+vB05BR4i7U7JQVpg/zn1fkVZCR3 eXn+47lClc45X4R3McxMJmNGEA6acxrJY/dr/XuM=
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 L8vIsLwQQXPj; Thu, 20 Apr 2017 17:08:21 +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; Thu, 20 Apr 2017 17:08:21 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 8F06A353643; Thu, 20 Apr 2017 11:08:20 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 8F06A353643
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 73C3940D811F; Thu, 20 Apr 2017 11:08:20 -0400 (EDT)
Date: Thu, 20 Apr 2017 11:08:20 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Yoav Nir <ynir.ietf@gmail.com>
cc: Jon <jmoroney@hawaii.edu>, ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
Message-ID: <alpine.LRH.2.20.999.1704201055590.1457@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca> <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
User-Agent: Alpine 2.20.999 (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/ietf/J5kpn4DJgqwUp2akJRdiI3B06qw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 15:08:31 -0000

On Thu, 20 Apr 2017, Yoav Nir wrote:

> On 20 Apr 2017, at 17:22, Paul Wouters <paul@nohats.ca> wrote:
>
>             generate a key pair on registration, store those keys on the server (in
>             an encrypted archive), and make the public key available. A little
>             coding later and we've got key exchange and message confidentiality.
>
>       SMTP servers could be key servers without having the private key of
>       individuals?
> 
> Sure. If they double as HTTPS servers.

I should drink coffee before posting... What I meant to say was the
model where the mail server generates and/or has a copy of the private
key seems dangerous. And I tried to say SMTP servers could be key
servers with only having public keys, not private keys. Still, using
(E)SMTP has all the problems I described earlier.

> I want to send you an email, so I type “paul@nohats.ca” in the To: field, and my MUA goes to
> https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/paul and that gets your public key.

But any MUA can already get my key using RFC-7929 at sha256("paul")[1:28]._openpgpkey.nohats.ca

eg:

dig openpgpkey 0357513deb903a056e74a7e475247fc1ffe31d8be4c1d4a31f58dd47._openpgpkey.nohats.ca.

So using another HTTP(S) server that is not the SMTP server itself does
not seem to make much sense to me? An SMTP server relaying the
OPENPGPKEY or SMIMEA or other source of pubkey could be useful,
if we think DNS transport is bigger problem than ESMTP transport.
But I think it is harder for people to contact mx.nohats.ca on port
25 from a random ISP compared to use DNS against 8.8.8.8 on an ISP
network.

Paul


From nobody Thu Apr 20 08:23:48 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF7E126E3A for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 08:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.658
X-Spam-Level: 
X-Spam-Status: No, score=-0.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NUMERIC_HTTP_ADDR=1.242] 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 1VXj8qHNEDPX for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 08:23:45 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC73129AAC for <ietf@ietf.org>; Thu, 20 Apr 2017 08:23:43 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 00A0E7A3309; Thu, 20 Apr 2017 15:23:42 +0000 (UTC)
Date: Thu, 20 Apr 2017 15:23:42 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <20170420152342.GM25754@mournblade.imrryr.org>
Reply-To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca> <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> <alpine.LRH.2.20.999.1704201055590.1457@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.LRH.2.20.999.1704201055590.1457@bofh.nohats.ca>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BJ_D_XFBVZcy-fdFtrWjzx2JLyM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 15:23:47 -0000

On Thu, Apr 20, 2017 at 11:08:20AM -0400, Paul Wouters wrote:

> > I want to send you an email, so I type “paul@nohats.ca” in the To: field, and my MUA goes to
> > https://mail-public-keys.nohats.ca/.well-known/mail-pubkeys/paul and that gets your public key.
> 
> But any MUA can already get my key using RFC-7929 at sha256("paul")[1:28]._openpgpkey.nohats.ca
> 
> eg:
> 
> dig openpgpkey 0357513deb903a056e74a7e475247fc1ffe31d8be4c1d4a31f58dd47._openpgpkey.nohats.ca.
> 
> So using another HTTP(S) server that is not the SMTP server itself does
> not seem to make much sense to me? An SMTP server relaying the
> OPENPGPKEY or SMIMEA or other source of pubkey could be useful,
> if we think DNS transport is bigger problem than ESMTP transport.
> But I think it is harder for people to contact mx.nohats.ca on port
> 25 from a random ISP compared to use DNS against 8.8.8.8 on an ISP
> network.

This was all covered in the discussion of draft-moore-email-addrquery.
(Perhaps on the UTA rather than DANE list? I don't recall)

My take at the time was (and remains) that queries for the recipient's
public key can be tunneled through the user's MSA, thereby avoiding
the issue of inability to reach port 25 from consumer end-device
IP space.  That discussion unfortunately appears to have worn-out
the draft author.  

I still think that draft is worth pursuing, if one is willing to
not set the bar too high.  The reason we have so little security
is sometimes (often?) because we're unwilling to accept less than
"perfect" security.  It is not unreasonable to trust the MSA to be
a trusted proxy for remote keys.  After all, in that model the same
MSA/MTA operator is trusted to vend your keys to others.

-- 
	Viktor.


From nobody Thu Apr 20 09:19:13 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DADF61294E1 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 09:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 wHtKxDp9ZNmJ for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 09:19:09 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A88B5128D3E for <ietf@ietf.org>; Thu, 20 Apr 2017 09:19:09 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTP id 0F80C30002B26; Thu, 20 Apr 2017 09:19:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=cryptonector.com; bh=LAM8q5c4wRF/0AIuQiApQvlOVkc =; b=j+F+4JY4wx4l17bbA0VjuQMu75kdM5YkDtcELZpXzxQa44rQSRlsI35EV9R 3yiT4sBhx6D5vnT/utjyEPht5+9JV/NLWT1EdFpPAoQwGLnbJn/WCgyUUsW8KdA4 VrqF+cgw2eejM13Xgq0QQrW6pNozuxWMuvEyMEo91OmxcA+k=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTPSA id B480B30002B25; Thu, 20 Apr 2017 09:19:08 -0700 (PDT)
Date: Thu, 20 Apr 2017 11:19:05 -0500
From: Nico Williams <nico@cryptonector.com>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <20170420161904.GE2856@localhost>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca> <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> <alpine.LRH.2.20.999.1704201055590.1457@bofh.nohats.ca> <20170420152342.GM25754@mournblade.imrryr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170420152342.GM25754@mournblade.imrryr.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ab1VnijtUapqr9YeSyf24uImt2A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 16:19:11 -0000

On Thu, Apr 20, 2017 at 03:23:42PM +0000, Viktor Dukhovni wrote:
> This was all covered in the discussion of draft-moore-email-addrquery.
> (Perhaps on the UTA rather than DANE list? I don't recall)
> 
> My take at the time was (and remains) that queries for the recipient's
> public key can be tunneled through the user's MSA, thereby avoiding
> the issue of inability to reach port 25 from consumer end-device
> IP space.  That discussion unfortunately appears to have worn-out
> the draft author.  
> 
> I still think that draft is worth pursuing, if one is willing to
> not set the bar too high.  The reason we have so little security
> is sometimes (often?) because we're unwilling to accept less than
> "perfect" security.  It is not unreasonable to trust the MSA to be
> a trusted proxy for remote keys.  After all, in that model the same
> MSA/MTA operator is trusted to vend your keys to others.

+1

The link to DNSSEC could be this:

 - the client should learn via DNSSEC that the user's MSA supports this
   feature, 

and

 - the user's MSA should learn via DNSSEC that the target domain (and
   any MTAs on the way there) supports this feature.

Nico
-- 


From nobody Thu Apr 20 10:01:24 2017
Return-Path: <jmoroney@hawaii.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA51131499 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:01:20 -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, 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=hawaii-edu.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 JyMEUNk0aY30 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:01:17 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 8C687129ADC for <ietf@ietf.org>; Thu, 20 Apr 2017 10:01:16 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id w50so16450912wrc.0 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:01:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hawaii-edu.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=8XGY3y/szkeekvj3Jh35sqJqaIPy8ejgGrIe8+fvsMQ=; b=UpN9NeK/VkT7pOpfc40ceKT9cuGD2F98LZ/zwJ7U4lvkvxhG2mgbyhJZXo25/2JExD EgKUJYS+4E+NqXdf8V7LzkItboQ0yrp89RMhC8u3/7WJjVWDb8qlGBHD+hWoqIqkjMyY jIo3EY6wRC9S/O3XZx6d28l+DLr3Pgmes9ZwiMz7+QGzZIa0gKEyQCr/pVLxTYjOLIFn TNQNyYACs4xxNFAqyiNz7DNd4cmzzF11+uGhNj/WXJzvJg2eJ0QdAm0ajZ9glUk8yLuW CPxm7eRjJqmFXYU8kxJ9D3FqFMaErWYzpjykdvEEf1lt5AMap/aNgnIe7A6eB++9OM2z 87iA==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=8XGY3y/szkeekvj3Jh35sqJqaIPy8ejgGrIe8+fvsMQ=; b=bESSyOpeJP2ZGWRycnNSloqwnh/Z8fqppAD85RNoS75CBCzoCmMHyOXMjbt/fQ1ASH 0n0HQ09tza4yfYJcKQzFIjooMsNDXhh+b3e4MdkA/i3dAmumCk61/u0jC/W3DRHN2TeU znfwIiskDALp5z0OiAKahZQ684uNz2F9GJsZEiD9I1wSnIO88MWAl4nzjzwcEBxFWw3Y iHUJ/EpP6Fh9q1bYMP+Zy6zK/O+0oOh4YIcVG3XL5yZWnRlBT7ol+RmdK/c74o31+3ih 5NKnUE6J8jKxFi0xUTyTyRKorxECWTvgONcu5I602IRV7zQzH3wYfKTnKnLv720jW0Pd F5ig==
X-Gm-Message-State: AN3rC/4hlE3A13B9Ga5zUG4WfNYvowqq/IUkS7g+QUfdqpdlcG4jP+3P UjWVk7I4ulxgBljk4PIo+rbHeLdz04N/s6+b3uJlcJsWCOdUOnf3lLpLAllx6p+3x8FQ4HguDg6 Ez7PdiUntbg+WXBCZHVGV8GkOTr50SYhCVtvZgNE=
X-Received: by 10.223.131.226 with SMTP id 89mr9372130wre.111.1492707675043; Thu, 20 Apr 2017 10:01:15 -0700 (PDT)
Received: from [192.168.1.213] (4daeb4bb.ftth.telfortglasvezel.nl. [77.174.180.187]) by smtp.gmail.com with ESMTPSA id p197sm8733268wmb.34.2017.04.20.10.01.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 10:01:14 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: Yoav Nir <ynir.ietf@gmail.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com>
Cc: ietf@ietf.org
From: Jon <jmoroney@hawaii.edu>
Message-ID: <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
Date: Thu, 20 Apr 2017 19:01:05 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PHlwTFVOwAS71OJ4BaMN9e04CNIf61J2P"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zM77VG1dPgIWSj5PePz5UYoeX8Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 17:01:20 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PHlwTFVOwAS71OJ4BaMN9e04CNIf61J2P
Content-Type: multipart/mixed; boundary="qoEGlKo3wNEQxiMVUMPomWdqXbmTFtwC6";
 protected-headers="v1"
From: Jon <jmoroney@hawaii.edu>
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: ietf@ietf.org
Message-ID: <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
Subject: Re: Why are mail servers not also key servers?
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
 <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com>
In-Reply-To: <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com>

--qoEGlKo3wNEQxiMVUMPomWdqXbmTFtwC6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 20/04/2017 16:29, Yoav Nir wrote:
>> *SNIP*
> I=E2=80=99m sure such things have been considered in the past, and for =
certain
> SMTP could be extended. I can think of a few complications right of the=

> top of my head. There are undoubtedly others:
>=20
> 1. People use multiple MUAs. For this account I use this Mac MUA, a
> phone MUA, and occasionally the web-based MUA. I=E2=80=99d need to shar=
e the
> private key to receive encrypted mail on all three. Doing it in the
> browser is a hard problem.
>=20
This is why I think smtp should be extended. All your mail agents
support (E)SMTP and presumably they would all support an extension to
smtp. The private keys will need to be stored some how to allow for
multiple clients, but a key generated from user input could be used to
decrypt a stored copy of the private key.

> 2. There=E2=80=99s the administrative problem of tying the SMTP server =
to
> whatever server is serving the public keys. HTTPS from the same IP
> address? New special DNS SRV record somehow tied to the gmail.com
> <http://gmail.com> MX record?
>=20
Indeed there is an administrative problem. I've done a project I call
CMTP that takes a very federated, hand off stance on this to keep
administration down.
https://github.com/darakian/cmtp
tl;dr servers have keys and sign transactions. The server key is simply
requested and is trusted on first use.

> 3. How much to you trust your email provider? Because they could
> trivially serve the wrong public key and intercept your traffic.
>=20
I really dislike this argument. You, me, and many others already trust
our mail servers in the same capacity. Sure a mail server could serve
the wrong key and then my mail ends up in a nefarious villains hands,
but that is already the case today. If there's some degree of
confidentiality we at least have traffic interception as a possible case
rather than the default.


Jon


--qoEGlKo3wNEQxiMVUMPomWdqXbmTFtwC6--

--PHlwTFVOwAS71OJ4BaMN9e04CNIf61J2P
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQIcBAEBCgAGBQJY+OlYAAoJEHCjQxAh73EjXRAP/1jBQAN96h8ll3ntAO6K2eTg
Ja9y67sQccdK9wf2Gw3QBHrhBjz2UPDAcLjW+b9Lc4/LJyomttK8q8v3+iYGlaEA
yvepNwFZ0UB0U9rwH+NZXHAtnM/RkXtjE+5lmR1Gv5hWXFItou6009xFaCwoLX3l
uSa/N3pjmCjT58SFvUUsg9X+57IOU+5arMa9tdKOuxk+2JlPPRrj48n4gJVp1oUk
7ILm8uH56NhC+wf7whC2dU1f4c4T2UY0v/BcwVLLhWFnXFC3Xczp9HDTgXXLHvx0
048j1OUz2baIgwq6+17EQDAUETu2KotynEfruPCU5dOiJzgN+ZuOUmywLOWa8XHC
4/Zpgp5HPfNGWzIjgkMHTt170B0WddLbjaWhf82tIA/evbi5tNTroe7AVCfyXcWA
z1e42OrAZuW2oizrRPA8kJURpwBXm4DnkFf7tQKGcw2k7MR/yMMk3etwAIL0zcIL
oDdS3sk2DcirpaDGgu/moqBbbJvPTnoInUr8Sqt0V9gn1T4HpJCNIy5tlYnSK+o6
xK7yXssKxb9lOwNMIqjijUUcFoCsMrITgQrT8ZvNaYUf2o3gJbEG22IpJYIl7I+d
Ov8wmMaxEZjqznHhj9YHQjSAllC4CtszYgfYDFicPReQ0Go3O52LEQKFCFC2GFte
HutZH6P1kM755/FdbegV
=R0Ty
-----END PGP SIGNATURE-----

--PHlwTFVOwAS71OJ4BaMN9e04CNIf61J2P--


From nobody Thu Apr 20 10:35:55 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6DD21314A3 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:35:53 -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 GjrntDlLxORS for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:35:52 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 948FB1314A5 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:35:52 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id E7CF57A3309; Thu, 20 Apr 2017 17:35:51 +0000 (UTC)
Date: Thu, 20 Apr 2017 17:35:51 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <20170420173551.GN25754@mournblade.imrryr.org>
Reply-To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Sv4fXeYfD8n5rt808edA2eUEjO4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 17:35:54 -0000

On Thu, Apr 20, 2017 at 07:01:05PM +0200, Jon wrote:

> This is why I think smtp should be extended. All your mail agents
> support (E)SMTP and presumably they would all support an extension to
> smtp. The private keys will need to be stored some how to allow for
> multiple clients, but a key generated from user input could be used to
> decrypt a stored copy of the private key.

A major problems with all E2E email encryption proposals is unrelated
to key distribution, none of the extant MUAs provide an adequate
interface for E2E encrypted email.

      + Encrypted email is not searchable.

      + Encrypted email is difficult to scan for spam and malware

      + Changing the private key can mean loss of access to email
	encrypted under the old key.

      + Signatures stop verifying when the signature key expires,
	even though they were valid at the the email was received.

In addition, nobody is investing any effort into major improvements
in standalone MUAs.  Free webmail has gotten rather fancy, but
content security is not in the provider's interest.  Will users
want to pay for security that reduces usability?

Therefore, for the foreseable future, hop-by-hop TLS is the best
security you're likely to get, and is most appropriate for the
vast majority of email.

It is not enough to invest effort in better key distribution,
the effort will be wasted unless the right incentives are in
place to induce a similar effort in usability of E2E encrypted
email after it arrives.

> > 3. How much to you trust your email provider? Because they could
> > trivially serve the wrong public key and intercept your traffic.
>
> I really dislike this argument. You, me, and many others already trust
> our mail servers in the same capacity. Sure a mail server could serve
> the wrong key and then my mail ends up in a nefarious villains hands,
> but that is already the case today. If there's some degree of
> confidentiality we at least have traffic interception as a possible case
> rather than the default.

TLS is quite sufficient to guard against passive monitoring, and
the final message stored unencrypted in the user's mailbox is much
more usable.

Make (stored) E2E email usable, and then there'll may be real
incentives to address key distribution.  Otherwise, any effort
to address key distribution will be largely wasted.

Do you have a design for an efficiently searchable and yet secure,
encrypted content index that supports concurrent updates from
multiple clients without losing data integrity?

How do you propose to handle spam and malware?

-- 
	Viktor.


From nobody Thu Apr 20 10:48:13 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1737F129431 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:48:11 -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 I_UQ0b8B-1bM for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:48:09 -0700 (PDT)
Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (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 8A239126B6E for <ietf@ietf.org>; Thu, 20 Apr 2017 10:48:09 -0700 (PDT)
Received: by mail-oi0-x243.google.com with SMTP id y11so9717013oie.1 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:48:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=dkfyrvaAysbUVc/cQOh1fX2foJ2Bj7uU91M8DoFq7Ps=; b=dFFlCiP+Ic8ew9vkNHUZVSZ1OvFgk7KEzxsgIf3dHTkLX4yaxFHSGx5B4xSum1jGnv qwmS3jAuBmRguiUQqCEOO7NOs+hYYzRfdoNKe/Eqe8IYMgwK35HLNvdgBVrEOggDSJvZ YMrmlpdEzrpt897ysqVKs4SOanhSby1SpVifRE6hJqB/IEhyfc8Svo1xI3eU9Km5Xg+D BViDB/6RuT8o9V0Tj5o5mTmoPBxxMpKkhAjCt0coLm4bTqS9yxFGG9RVjdY5Irl8RM2H TFyTEzQiD7I9ggb2sdzCNmNzJAEhIeBqtlZvzZUU2ZVdnDSgj3MZz0kySj+Kl00qW5qU 8ybQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=dkfyrvaAysbUVc/cQOh1fX2foJ2Bj7uU91M8DoFq7Ps=; b=K6hVSsW1KwPaMFCeWRCw1s0MhGwQYzz3ZqWk2KOwIlTQT/YY7+m2K+FcqUunMNRhYv KAd8HLxGntkN/layh66JfRqWfwxbQ/D8CYDDCUa5UpZ6giRSmVtynxtL/WsSKqbuvaXX iQg6KPP7f/nCnAz1KYOJh/VLx8fFxB1XI7oexaTHUxw6e9K31YD15V7fQcAvKZsxTM7P jp3sDjV6Emnl27SbAxo5HLSxQfaeyAvMJhX2qZk06vwddsz1hVoTu7oh7AFRi1KGFV+f 8PT38oPy/vPzmEVW7PQH83DRtq01RCNmOfL5w2KrKiO3UM2hjrqf1/29JI5hnMbmcl1w 3liA==
X-Gm-Message-State: AN3rC/7sU6RebBJo90RIRPBnlBrMZP6qz1xJkyFU2hEZeb5rP2CueIYS nhsYyVKkGVXKvTGy7uw=
X-Received: by 10.157.63.243 with SMTP id i48mr2334255ote.231.1492710488481; Thu, 20 Apr 2017 10:48:08 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id s193sm2822761oie.21.2017.04.20.10.48.05 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 10:48:07 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com>
Date: Thu, 20 Apr 2017 11:48:04 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010501010803000506090705"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P0Zif6X9asqQ2MROu7QG_on1zCU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 17:48:11 -0000

This is a cryptographically signed message in MIME format.

--------------ms010501010803000506090705
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/20/2017 11:01 AM, Jon wrote:
> On 20/04/2017 16:29, Yoav Nir wrote:
> (lots snip)
> This is why I think smtp should be extended. All your mail agents
> support (E)SMTP and presumably they would all support an extension to
> smtp. The private keys will need to be stored some how to allow for
> multiple clients, but a key generated from user input could be used to
> decrypt a stored copy of the private key.


You seem to be describing a configuration server.  (I forget the RFC#, I =

think it was a Chris Newman one). A configuration server could store a=20
BLOB of data that could be decrypted by a client that had the key.

I would like to see an extension so that the MUA could contact the=20
destination server (perhaps their MX record host) and get a users PUBLIC =

key. Perhaps (just an idea - no screaming please) a new TXT record type=20
that points to the domains PubKey server.

I think it is undisputed that the MX server would know which email=20
recipients are valid for itself. Or if a proxy SMTP server, could relay=20
the request to the real hidden SMTP server.

As someone else pointed out, draft-moore-email-addrquery is a great start=
=2E



--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIwMTc0ODA0WjAvBgkqhkiG9w0BCQQxIgQgaOZdXfr0l7G54EcpXk5hha/WL/M0JPAb
8asaN4GmFy8wbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEATbquoWkPZMhm
zzZZEtwC7nCxl2TwEp9jvWX8lKnXIV/sRZ3UaHPPVKt4JDsHg90eYgiCm9doPq0H+59pLtXa
6InBevl3Xulc4r3XUSuyBDNe0z6Q7cZF/jNNcz+YZ9fhKh3SSLaexzfhEOvEIgS0uQVe9jIj
bz7pUkQ1VdOyz7jUYk+NbSlP3u3BWshcgObMqJIbyzbFcScW6im8V7oI05kRw1ofz5P5swZL
wh++q4Qn1Hlx7PMCqCHCzwwPYAF54kqON/kvjzE/aI8MXHhG0QwDuMDIux+7LKri3fvo+gdH
JuTRYVFPBwvzwX3mBjfsGlTR+Sdphj2LKLEBw9EkHwAAAAAAAA==
--------------ms010501010803000506090705--


From nobody Thu Apr 20 10:56:15 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1DB131493 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:56: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, 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 HiMy9lTaCrCw for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:56:12 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::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 68494129B74 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:56:12 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id y11so9783806oie.1 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=itdhqU8BuFAmDrRWf9VPp9H3igimZLlyBSmB8Q7VR0M=; b=V52YFuvpZCDb9Yhs9AFPLu0K1mWVCyTqlVXTLNEcU9N9vo1KlmVnOFdK8Wyz+BExir xeplvxhTPMAtiknB2dTC1Ql91d6GHJJiECxuFxgooGBshjWAX5bra6EralA/SdlFHz/m UuUngr8eThkMrEyfUezygo4nlgNNOdOTD7nxZ42DtQWmEjT6Wn3nex63MNwcpZ68RYns P2GgQtdHW0eCMgrFz8hrHzrkx74aAsCQKcw3eAGvPR53Nvb/ZBL1/7RcoQ0ujjctXEjK wiDx2x1kglQ5PfAPsdWzRO9VCi1vpj7c7NoTZABJjTVrWgq+ZBpPaCyLVf3xH7ZSSFMb 1ivw==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=itdhqU8BuFAmDrRWf9VPp9H3igimZLlyBSmB8Q7VR0M=; b=eoMh/5WUJk7wnUKxcUYz+IG3vGSgOOW++c0kISh4cnB0xR+YRusY1dQOdDZ08xZ/rv 41U4DFXUu081jamb1guFKkyKBFVXoDhLYSDK2QhZ5b21Lh6FZ2qJiDa28Om9L+bp62qC T1nIHKincVVRGn8LjlJpRiZJBGjqV6SGLvqmIpZLvFUYRf76yjKc4gMxUoImxamCm6QS ep6iGvVyxS7rbMFsg+wqxt5q2NGUyVqzx/doW4TqjlfazBY3Q+Fq7Kl4JHEfDTygp8ra 0zbUjHF5CjzrsYBYnRp7a027y1Sewx/mFIzvzeUZPK+/wXy8YKx7JJx2mWrxvNRZLEa6 5D8g==
X-Gm-Message-State: AN3rC/7LF5QsxOwVHysjcIT4iJOKM5YU8z5NR2nczm0t6zLCmrYMtXjQ 7b+TrxoqizqI+KrXv0U=
X-Received: by 10.202.50.131 with SMTP id y125mr5147844oiy.105.1492710971433;  Thu, 20 Apr 2017 10:56:11 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id j17sm2826222ota.24.2017.04.20.10.56.09 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 10:56:10 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
Date: Thu, 20 Apr 2017 11:56:08 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <20170420173551.GN25754@mournblade.imrryr.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms060905080803040705000203"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/en1FftYSAS6qmSvnB4NBa-WjlkI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 17:56:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms060905080803040705000203
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/20/2017 11:35 AM, Viktor Dukhovni wrote:
> On Thu, Apr 20, 2017 at 07:01:05PM +0200, Jon wrote:
>=20
>> This is why I think smtp should be extended. All your mail agents
>> support (E)SMTP and presumably they would all support an extension to
>> smtp. The private keys will need to be stored some how to allow for
>> multiple clients, but a key generated from user input could be used to=

>> decrypt a stored copy of the private key.
>=20
> A major problems with all E2E email encryption proposals is unrelated
> to key distribution, none of the extant MUAs provide an adequate
> interface for E2E encrypted email.
>=20
>        + Encrypted email is not searchable.

Sure it is, by the recipient MUA, else the user could not read their=20
email. It would not be searchable by a 3rd party - which is the point of =

encryption.

>        + Encrypted email is difficult to scan for spam and malware

The scan would have to take place in the MUA. Firewall scanners would=20
fail, as they do now with S/MIME or encrypted PGP.

>        + Changing the private key can mean loss of access to email
> 	encrypted under the old key.

Only if you throw away old keys. Doctor, Doctor, it hurts when I do=20
this. - So Do not do that :-)

>        + Signatures stop verifying when the signature key expires,
> 	even though they were valid at the the email was received.

Again, do not throw away the old keys. An MUA should not allow a user to =

throw away any key needed for any message still in the store. Yep - compl=
ex.

> ....

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIwMTc1NjA4WjAvBgkqhkiG9w0BCQQxIgQgItUxvlztFiCX6EshsVWoMTu55ftWyIUh
nuosdQGfvl8wbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEASJ/35uImP889
kNa74Hw6MfPIZKVHS+oDu9cuy3Q/RKMbAkpVJ32tvDFegIOY8SZ7ypTMr58LQ8UmlQYXM2Mm
9KjWnb5o+LslQnMD8odYPVYrW2eRJKv50ZNe8CXIoIc+bXCpJy+65kkK5SI/ba3fqfNmufLm
56euzjk0P8IaEpyWRvFPa/5xVu0NwKpulJQ+VGIY18yTOeZBXyW9ShtlI+ANsYhydyVIuMgo
Kyg0JkWP0+8ujBIUyB2kXNoPry+2CrGZxeqAagrbxPgdeurEOpkpye7I+8UiTXOV9CwzVDwf
itth/2q/xoax14zMIM3L48BhimguEz+dmi3pseIUQgAAAAAAAA==
--------------ms060905080803040705000203--


From nobody Thu Apr 20 11:53:38 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 857071292FC for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 11:53:31 -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 FJOKA577d-7o for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 11:53:30 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86513129BA2 for <ietf@ietf.org>; Thu, 20 Apr 2017 11:53:28 -0700 (PDT)
Received: from [172.31.31.193] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 3839F7A32F1 for <ietf@ietf.org>; Thu, 20 Apr 2017 18:53:27 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Why are mail servers not also key servers?
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
Date: Thu, 20 Apr 2017 14:53:27 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: IETF general list <ietf@ietf.org>
Message-Id: <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dkuHrCYotWlRpq76fhgQpVA8TmY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 18:53:31 -0000

>> A major problems with all E2E email encryption proposals is unrelated
>> to key distribution, none of the extant MUAs provide an adequate
>> interface for E2E encrypted email.
>>       + Encrypted email is not searchable.
>=20
> Sure it is, by the recipient MUA, else the user could not read their =
email.
> It would not be searchable by a 3rd party - which is the point of =
encryption.

Which MUAs index content of encrypted messages?  How does this work for =
clients
that store only a cache of recent messages, or webmail?

>>       + Encrypted email is difficult to scan for spam and malware
>=20
> The scan would have to take place in the MUA. Firewall scanners would =
fail,
> as they do now with S/MIME or encrypted PGP.

Endpoint scans are often not nearly as effective.

>>       + Changing the private key can mean loss of access to email
>> 	encrypted under the old key.
>=20
> Only if you throw away old keys. Doctor, Doctor, it hurts when I do =
this.
> - So Do not do that :-)

The mocking tone is entirely out of place.  Not all MUAs support =
multiple recipient
keys.

>>       + Signatures stop verifying when the signature key expires,
>> 	even though they were valid at the the email was received.
>=20
> Again, do not throw away the old keys. An MUA should not allow a user =
to throw away
> any key needed for any message still in the store. Yep - complex.

Should not is not the same as do not.  My point is and remains that E2E =
encryption
of email is not usable with today's MUAs, progress on some of the issues =
is both
difficult and unlikely.

--=20
	Viktor.


From nobody Thu Apr 20 12:10:46 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B023513158F for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:10: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, 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 X-S6aXIF5f4W for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:10:42 -0700 (PDT)
Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003:c06::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 B27F9131585 for <ietf@ietf.org>; Thu, 20 Apr 2017 12:10:42 -0700 (PDT)
Received: by mail-oi0-x244.google.com with SMTP id a3so7399094oii.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 12:10:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=U4vaGMDg566+UOPg78yXNL0W19NLDmgdar9OstHaNms=; b=DQB1Dk5ILoXPAu72w4spfxtqiPqsrjgeJLDgznh8Qly3b5kt5ZzZttMDAoxfM4vx3f 8s4CTQ/utbCqbJNhgARseWyXRYv1VpqitDIiqvAEFSy41tcJBq6YfXMKTGljnEsSb97z HUIzUztqH4IFL8l7vt3saQT8OYnLePU2GifufyWdI8dZbZX11RxbGAxhM1SnTdUcgH6E j/b7GzpWbXVU8RJ66JHO2BGN3323CSkIxYzuUklN+P4WDIORroNhgZdiwfwiGlJ0uSyH 8QcQ7/YN3hY/GndUSCs9auB8B65nphtdO5IjWXxEY6TLTdtq9wneFsdoDWFqpJA0ikIE xLCg==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=U4vaGMDg566+UOPg78yXNL0W19NLDmgdar9OstHaNms=; b=HvCfeMcC198eATVXxjzFcar6VOAc0GHMxrUGSCTKVNBS0/pyH7p2hL0ICJcdGkXudQ 16jSv2mnQAEo7YLAqdHogU/Y3jNUBheiIUYiPV/+M5F6bUg3xkZFIWxls6IQoT+G6GCQ 3FKej12Zj2UbyZqdpaqKwhY66o9P1eHU5DE7UHbWV/Cmp5T4uXUoZm6/yyKpZFuK4quH z3MHWJ10OFcTG4PjUHSv6G0BwtLJwqNTUZ16wyX7tTbVbzS5ej1/fDtYzJ8HwnWtT3aj Pb61lGcVBAL+KHYoeuubBMWp6pRvidKl1NJP2jKLNFfHmU94XjhxutW5rJ7QbuA+DThA dwPQ==
X-Gm-Message-State: AN3rC/7unOqilsQTW3r7tv/G3ec52RAb4zl4wHkeSeUKYXoaqNYQIhn+ FRSqPo5bIyN6fy2whsk=
X-Received: by 10.202.49.12 with SMTP id x12mr5491529oix.18.1492715441564; Thu, 20 Apr 2017 12:10:41 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id y67sm2910224ota.25.2017.04.20.12.10.39 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 12:10:40 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com>
Date: Thu, 20 Apr 2017 13:10:38 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090300040102080609020208"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kbDAjWSIBIT1PxG4x7wlQlLK7tc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 19:10:45 -0000

This is a cryptographically signed message in MIME format.

--------------ms090300040102080609020208
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/20/2017 12:53 PM, Viktor Dukhovni wrote:
 >
 >>> A major problems with all E2E email encryption proposals is unrelate=
d
 >>> to key distribution, none of the extant MUAs provide an adequate
 >>> interface for E2E encrypted email.
 >>>        + Encrypted email is not searchable.
 >>
 >> Sure it is, by the recipient MUA, else the user could not read their =

email.
 >> It would not be searchable by a 3rd party - which is the point of=20
encryption.
 >
 > Which MUAs index content of encrypted messages?  How does this work=20
for clients
 > that store only a cache of recent messages, or webmail?

That is an implementation detail. If the MUA wants to see the message,=20
it can, if it can't, its not an MUA.

Storing the message in a cache is orthogonal to if it is encrypted. I=20
can cache the encrypted message, cache it after its decrypted, or not=20
cache it at all.

Webmail does not work with encrypted email. Never will until you give=20
your private key to some unknown email-web-server implementation and=20
that systems unknown administrator. Not something the IETF should be=20
recommending.

 >>>        + Encrypted email is difficult to scan for spam and malware
 >>
 >> The scan would have to take place in the MUA. Firewall scanners=20
would fail,
 >> as they do now with S/MIME or encrypted PGP.
 >
 > Endpoint scans are often not nearly as effective.

No change to the current operation of encrypted email. The entire point=20
of encrypted email is so that no one (including the server) can see the=20
contents of encrypted email.

If your ISP holds your private key, then you have no privacy in your emai=
l.

 >>>        + Changing the private key can mean loss of access to email
 >>> 	encrypted under the old key.
 >>
 >> Only if you throw away old keys. Doctor, Doctor, it hurts when I do=20
this.
 >> - So Do not do that :-)
 >
 > The mocking tone is entirely out of place.  Not all MUAs support=20
multiple recipient
 > keys.

That is an implementation detail, not a protocol detail. If you want to=20
see old email, don't throw away the key to that email.

 >>>        + Signatures stop verifying when the signature key expires,
 >>> 	even though they were valid at the the email was received.
 >>
 >> Again, do not throw away the old keys. An MUA should not allow a=20
user to throw away
 >> any key needed for any message still in the store. Yep - complex.
 >
 > Should not is not the same as do not.  My point is and remains that=20
E2E encryption
 > of email is not usable with today's MUAs, progress on some of the=20
issues is both
 > difficult and unlikely.

I use E2E almost every day. Works fine. Update the MUA your using. If=20
you do not want to update your MUA, then, your making the decision for=20
things to not work. Its not a protocol issue.

A Web-clients MUA have a problem, because you would have to store the=20
private key in the email-web-server. I would not do that, so I will not=20
use an MUA that allows my private key to be given to another server,=20
managed by some unknown person. They have that problem now - no change.
Not fixable, unless you give away your private key. And again, not=20
something the IETF should be recommending.


--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIwMTkxMDM4WjAvBgkqhkiG9w0BCQQxIgQg9Ru06swwwVNmGJSVwQ1iFANOQZiiAIxt
GSvPxPmFm9YwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEApkm1wzAKE6UT
5zkjwf+Xzj51w0ljVKa84KusUoXau6z87RGJtLu/l2ma2g9RJwx//Ta2Q4ZXGGioeFj7lQeS
5dcbkztCvIR5V4F+NbALs1eUceYAadSL1a2HMOPpk5vs4vjd0z2vyXA0vzhJ8Jf8ZQtrGMni
NGapcqKJ5RnvfjpVlWrHmHIhwrjD3zWi8Bs7fidmF5qrdv0MRM4tOsTGDVA1QfuUwRLC9t/Q
zDB4NY0qTi36RoxEMs2mz/nFRE7DfTayeifNXDVelrks4+J3rMmQLvmtHCAEqYMD/55y68WJ
7sJrq1gXg2ilLU8EcpJxL5Jy8+rog6Y9duR1yPWGbAAAAAAAAA==
--------------ms090300040102080609020208--


From nobody Thu Apr 20 12:26:14 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2068131555 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 TsH0ueT9qecs for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:26:11 -0700 (PDT)
Received: from homiemail-a87.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3473129B51 for <ietf@ietf.org>; Thu, 20 Apr 2017 12:26:10 -0700 (PDT)
Received: from homiemail-a87.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTP id 3A347C009F49; Thu, 20 Apr 2017 12:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=q/zihS5bHLX6si 8vQlwZmmMFUZs=; b=Jf8mZRNpXIjKhMO7zGWjqLuCT83486PAEK7Y92PrEjeJbw VZcpElc4x68MnzVWOTvLEJgTfAsgFKZh4pXBm6jV2E5irjqvZ94pbmvlghMxIjYr 9LnSILpC+MghWbiLo5GVxMq5KqROTnBixqeEZo3QeEtAkGV5mgfjmwM/44lsM=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTPSA id 1EA86C009F47; Thu, 20 Apr 2017 12:26:09 -0700 (PDT)
Date: Thu, 20 Apr 2017 14:26:05 -0500
From: Nico Williams <nico@cryptonector.com>
To: Doug Royer <douglasroyer@gmail.com>
Cc: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <20170420192604.GF2856@localhost>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bWXZ9_DAwNUHnlN21G_n4Fa2l4Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 19:26:13 -0000

On Thu, Apr 20, 2017 at 01:10:38PM -0600, Doug Royer wrote:
> On 04/20/2017 12:53 PM, Viktor Dukhovni wrote:
> >
> >>> A major problems with all E2E email encryption proposals is unrelated
> >>> to key distribution, none of the extant MUAs provide an adequate
> >>> interface for E2E encrypted email.
> >>>        + Encrypted email is not searchable.
> >>
> >> Sure it is, by the recipient MUA, else the user could not read their
> email.
> >> It would not be searchable by a 3rd party - which is the point of
> encryption.
> >
> > Which MUAs index content of encrypted messages?  How does this work for
> clients
> > that store only a cache of recent messages, or webmail?
> 
> That is an implementation detail. If the MUA wants to see the message, it
> can, if it can't, its not an MUA.

Sure.

> Storing the message in a cache is orthogonal to if it is encrypted. I can
> cache the encrypted message, cache it after its decrypted, or not cache it
> at all.

If you want to use IMAP and leave the mail on a server (which does not
have your private keys thus can't decrypt the e-mails) then the server
can't index your email.  Your client could build and keep an index
(presumably stored encrypted) to search email with.

No MUA does that.  Maybe they should, and it'd be nice.  But since they
don't, E2E encrypted email is just too difficult to use.

Now, indexing encrypted email on the MUA side is clearly an
implementation detail, but it is a detail which (along with many other
UI details) is critical to adoption.

Part of the problem is that there is very little work being done on
MUAs.  We can tell people what to do, but they're not doing it, so we're
stuck.

> I use E2E almost every day. Works fine. Update the MUA your using. If you do
> not want to update your MUA, then, your making the decision for things to
> not work. Its not a protocol issue.

And what MUA is that?

> A Web-clients MUA have a problem, because you would have to store the
> private key in the email-web-server. I would not do that, so I will not use
> an MUA that allows my private key to be given to another server, managed by
> some unknown person. They have that problem now - no change.
> Not fixable, unless you give away your private key. And again, not something
> the IETF should be recommending.

I'm not so sure.  A client could use JS crypto APIs to locally decrypt
(and hopefully not send the cleartext back to the server! but you have
to trust the MUA software...), and it could even build an index in local
storage.

But still, without anyone actually implementing such a thing...

Nico
-- 


From nobody Thu Apr 20 12:31:59 2017
Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D4E1315BF; Thu, 20 Apr 2017 12:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 qfttccClCqb1; Thu, 20 Apr 2017 12:31:41 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0129.outbound.protection.outlook.com [104.47.41.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19EF21315FD; Thu, 20 Apr 2017 12:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gZQXEn5AMfW0SBRFJEmxpLjuTJxdKqTjytB5LVLRDiE=; b=SD6+8mXBtOaz/KX0yX0mbAUC9HcBxzUb79V7N2m707E74qAOVlsuq7DBrL1jOL8I9REXm2RL6FEOK54Zf8HrooN6eU5JPr5FrcdX8dokihbG9dxGXYBC/YRn9OsGvTTSFCOtmb19HV1a27pZnX+DOXMkzWT5yF1s1uTZR9GojiU=
Received: from BY2PR21MB0084.namprd21.prod.outlook.com (10.162.78.141) by BY2PR21MB0083.namprd21.prod.outlook.com (10.162.78.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.1; Thu, 20 Apr 2017 19:31:38 +0000
Received: from BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) by BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) with mapi id 15.01.1061.003; Thu, 20 Apr 2017 19:31:38 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsOTWicthTbHq+0Cl6wEpb6SnVKHOtjQA
Date: Thu, 20 Apr 2017 19:31:38 +0000
Message-ID: <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
In-Reply-To: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sfc.wide.ad.jp; dkim=none (message not signed) header.d=none;sfc.wide.ad.jp; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR21MB0083; 7:rWzV/MddUNs53nBT3v6eGgbIIJPr5ZooUjY/MeGMkEDdnhAHkAeKvWBaM3vIv0cezKcqstjTqSUfN0du9Mtvhk3B7rx2cl0LMo3CuYX9Dh8odSWtHv72Ve0ATl7skOsq+VHXhvN+SyASxUOHRTTVizyjjPirFFmU+3K3yItnGeIGYgfy4cJ9KhFxNpHvrwj54fQrUwzGEhwoA98fjMp8DPeMx7lv+9xyr3ORNkWWW40gojujKt4mBaIMMMOVdvcg9S9TA4kbXt3Im1issFqb3scQlYbhcfL9X6LzqMwQsyCzf0qwZ2WmvGeZMNtKCvlqSgmNdJSZhv0ooxyns9/GFn5J4mNizUL6gaS0Zpzy9oo=
x-ms-office365-filtering-correlation-id: de05cb43-ed75-4b8d-6352-08d48823dd64
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:BY2PR21MB0083; 
x-microsoft-antispam-prvs: <BY2PR21MB00831A56E423A03E46C59804831B0@BY2PR21MB0083.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123558043)(201703131423075)(201702281528075)(201703061421075)(201703061406096)(20161123564025)(20161123560025)(6072148); SRVR:BY2PR21MB0083; BCL:0; PCL:0; RULEID:; SRVR:BY2PR21MB0083; 
x-forefront-prvs: 02830F0362
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39850400002)(39860400002)(39450400003)(39400400002)(39840400002)(6436002)(6116002)(50986999)(55016002)(54906002)(74316002)(99286003)(38730400002)(6506006)(66066001)(4326008)(6246003)(2900100001)(53936002)(76176999)(9686003)(8676002)(6306002)(8936002)(81166006)(54356999)(3846002)(7736002)(7696004)(5660300001)(305945005)(25786009)(102836003)(2950100002)(77096006)(10090500001)(5005710100001)(33656002)(86362001)(3660700001)(2906002)(3280700002)(2501003)(122556002)(189998001)(10290500002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR21MB0083; H:BY2PR21MB0084.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2017 19:31:38.2636 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR21MB0083
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_56XKwqL-TUYou0KNZs_-MD9UbU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 19:31:44 -0000

DQpUaGFua3MgZm9yIHlvdXIgZmVlZGJhY2suDQoNCj4gMTogSXQgaXMgbm90IGNsZWFyIGhvdyB0
aGUgcHJvdG9jb2wgcmVhY3RzIHRoZSBlcnJvcnMgZnJvbSB0cmFuc3BvcnQgbGF5ZXJzIChlLmcu
IGNvbm5lY3Rpb24gZmFpbHVyZSkuDQo+ICAgIFRoZSBwcm90b2NvbCB3aWxsIGp1c3QgaW5mb3Jt
IGFwcHMgb2YgdGhlIGV2ZW50cyBhbmQgdGhlIGFwcCB3aWxsIGRlY2lkZSB3aGF0IHRvIGRvIG9y
IHRoZSBwcm90b2NvbCBpdHNlbGYgd2lsbCBkbyBzb21ldGhpbmc/DQoNClRoZSBXZWJTb2NrZXRz
IGNhc2UgaXMgYWRkcmVzc2VkIGJ5IFJGQzY0NTU6DQoNCiAgIFdoZW4gdGhlIHVuZGVybHlpbmcg
VENQIGNvbm5lY3Rpb24gaXMgY2xvc2VkLCBpdCBpcyBzYWlkIHRoYXQgX1RoZQ0KICAgV2ViU29j
a2V0IENvbm5lY3Rpb24gaXMgQ2xvc2VkXyBhbmQgdGhhdCB0aGUgV2ViU29ja2V0IGNvbm5lY3Rp
b24gaXMNCiAgIGluIHRoZSBDTE9TRUQgc3RhdGUuICBJZiB0aGUgVENQIGNvbm5lY3Rpb24gd2Fz
IGNsb3NlZCBhZnRlciB0aGUNCiAgIFdlYlNvY2tldCBjbG9zaW5nIGhhbmRzaGFrZSB3YXMgY29t
cGxldGVkLCB0aGUgV2ViU29ja2V0IGNvbm5lY3Rpb24NCiAgIGlzIHNhaWQgdG8gaGF2ZSBiZWVu
IGNsb3NlZCBfY2xlYW5seV8uDQoNCi1hbmQtDQoNCiAgIElmIGF0IGFueSBwb2ludCB0aGUgdW5k
ZXJseWluZyB0cmFuc3BvcnQgbGF5ZXIgY29ubmVjdGlvbiBpcw0KICAgdW5leHBlY3RlZGx5IGxv
c3QsIHRoZSBjbGllbnQgTVVTVCBfRmFpbCB0aGUgV2ViU29ja2V0IENvbm5lY3Rpb25fLg0KDQpJ
dCdzIHBvc3NpYmxlIHRvIGFkZCBsYW5ndWFnZSBzaW1pbGFyIHRvIHRoZSBhYm9ydCBjYXNlLCBh
bG9uZyB0aGUgbGluZXMgb2YgIldoZW4gdGhlIHVuZGVybHlpbmcgVENQIGNvbm5lY3Rpb24gaXMg
Y2xvc2VkIG9yIHJlc2V0LCB0aGUgQ29BUCBjb25uZWN0aW9uIGlzIGNsb3NlZCBhbmQgaW4gZmxp
Z2h0IG1lc3NhZ2VzIG1heSBiZSBsb3N0Ii4NCg0KPiAyOiBUaGVyZSB3aWxsIGJlIHNpdHVhdGlv
bnMgd2hlcmUgdGhlIGFwcCBsYXllciBpcyBmcmVlemluZyB3aGlsZSB0aGUgDQo+IHRyYW5zcG9y
dCBsYXllciBpcyBzdGlsbCB3b3JraW5nLiBTaW5jZSB0cmFuc3BvcnQgbGF5ZXJzIGNhbm5vdCBk
ZXRlY3QgDQo+IHRoaXMgdHlwZSBvZiBmYWlsdXJlcywgdGhlcmUgc2hvdWxkIGJlIHNvbWUgbWVj
aGFuaXNtcyBmb3IgaXQgc29tZXdoZXJlIGluIHRoZSBwcm90b2NvbCBvciBpbiB0aGUgYXBwIGxh
eWVyLiAgVGhlIGRvYyBuZWVkcyB0byBhZGRyZXNzDQo+IHRoaXMgcG9pbnQuIEZvciBleGFtcGxl
LCB3aGF0IHdpbGwgaGFwcGVuIHdoZW4gYSBQT05HIG1lc3NhZ2UgaXMgbm90IHJldHVybmVkIGZv
ciBhIGNlcnRhaW4gYW1vdW50IG9mIHRpbWU/DQoNClBPTkcgaXMgbW9kZWxlZCBvbiBzaW1pbGFy
IG1lY2hhbmlzbXMgaW4gUkZDNjQ1NSBhbmQgUkZDNzU0MC4gTmVpdGhlciBwcm92aWRlcyBhbnkg
Z3VpZGFuY2UgZm9yIHRoaXMgY2FzZS4gSXQncyBleHBlY3RlZCB0aGF0IGFuIGFwcGxpY2F0aW9u
IGZyYW1ld29yayB3b3VsZCBkZWZpbmUgYW5kIGVuZm9yY2UgdGhlIGFwcHJvcHJpYXRlIHBvbGlj
eSBmb3IgdGltZW91dHMgb3IgcmV0cmllcy4NCiANCj4gMzogU2luY2UgdGhpcyBkcmFmdCBkZWZp
bmVzIG5ldyBTWlggdmFsdWUsIEkgdGhpbmsgdGhlIGRvYyBuZWVkcyB0byB1cGRhdGUgUkZDNzk1
OS4gVGhpcyBwb2ludCBzaG91bGQgYmUgY2xhcmlmaWVkIG1vcmUgaW4gdGhlIGRvYy4NCg0KQ2Fy
c3RlbiByZXNwb25kZWQgdG8gdGhpcyBpc3N1ZSBhbmQgdGhlIGZpbmFsIGV4Y2hhbmdlIGlzIGhl
cmUgLSBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9t
c2cwODU2Mi5odG1sIA0KDQpNeSBzZW5zZSBpcyB0aGF0IHdlIHNob3VsZCB0cmVhdCB0aGlzIGFz
IGFuIHVwZGF0ZSB0byBSRkM3OTU5IGJhc2VkIG9uIHRoZSBvcmlnaW5hbCBsYW5ndWFnZToNCg0K
ICAgICBUaGUgdmFsdWUgNyBmb3IgU1pYICh3aGljaCB3b3VsZA0KICAgICAgaW5kaWNhdGUgYSBi
bG9jayBzaXplIG9mIDIwNDgpIGlzIHJlc2VydmVkLCBpLmUuLCBNVVNUIE5PVCBiZSBzZW50DQog
ICAgICBhbmQgTVVTVCBsZWFkIHRvIGEgNC4wMCBCYWQgUmVxdWVzdCByZXNwb25zZSBjb2RlIHVw
b24gcmVjZXB0aW9uDQogICAgICBpbiBhIHJlcXVlc3QuDQoNCmFuZCB0aGUgdXNlIG9mICJleHRl
bnNpb24iIGluIGNvYXAtdGNwLXRsczoNCg0KICAgIFRoZSDigJlCbG9jay13aXNlIEV4dGVuc2lv
biBmb3IgUmVsaWFibGUgVHJhbnNwb3J0IChCRVJUKeKAmSBleHRlbmRzIHRoZSBCbG9jayBwcm90
b2NvbA0KICAgIHRvIGVuYWJsZSB0aGUgdXNlIG9mIGxhcmdlciBtZXNzYWdlcyBvdmVyIGEgcmVs
aWFibGUgdHJhbnNwb3J0Lg0KDQpUaGUgZXhpc3RpbmcgSUFOQSBlbnRyaWVzIGZvciBCbG9jazEg
YW5kIEJsb2NrMiB3aWxsIGFsc28gbmVlZCB0byByZWZlcmVuY2UgY29hcC10Y3AtdGxzIGluIGFk
ZGl0aW9uIHRvIFJGQzc5NTkuDQoNClRyYWNraW5nIGluIGh0dHBzOi8vZ2l0aHViLmNvbS9jb3Jl
LXdnL2NvYXAtdGNwLXRscy9pc3N1ZXMvMTI5DQoNCg0K


From nobody Thu Apr 20 12:50:52 2017
Return-Path: <phluid61@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A82E1315C2 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 K2GCLFUf8avQ for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 12:50:49 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::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 0505113160B for <ietf@ietf.org>; Thu, 20 Apr 2017 12:50:48 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id o22so92438539iod.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 12:50:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=IdQJJsP8aiBNKus2bOg80hRquq5Fx3w/HV7rWQ5jOqo=; b=LA3eiinty7Wr1l07WhoJDcSKZ/lw1xsj/RQPjor1dA60P8C8OqsDvQQrjlQIJayva3 TKwgpxhdTlqMR1ezQfsA6O0ynymgubEbMgB9qH5e//UJHrBdCwa7MrWXXDJhvhTM3RcM SyNA2fL1G9wwvDTLMJ5ChdQV5GfdsdkbMarqECSnZ4ONOhRtzK5JLwJmDj+ANQaLgI83 XHhKtAXLmUUsdatdarVqWlr5OOFYThlBej8iHaa4HVloOr2kA7nqiAslrHFONhC8Veko tfGLZb/DLXe7//pM2ea8/mxodWkT0Kv9S5z6+kc5h/PfgINKFTIjrkPOaE0dTN2OWWJm SLaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=IdQJJsP8aiBNKus2bOg80hRquq5Fx3w/HV7rWQ5jOqo=; b=kEjw+IWH/rs2xxzNbQzYUItGC6YKaNUldaLWB3Zi7ZxXc6e7jlGduW5jUlDXOHKJra DmDLjYpEHACmVqRuH4HwwrH0TmHtnPX2hWzEDl4feNtRgI+/RB6Tueoormz5W+/A9ap7 db11+sveBZA5MtVvzy9OXLs+bu4b9R8VRgsHcyfh2+p8q+jiSsgO8Jd6F5wghb8Lppht gh064IbyVFK5uoNH3UfTKGR6MfRpnTSJ8dlIbxE1xvCEkGasH80xZJa6LUISSU5Ao1NF JnkrxUduvaetyoQIdrIRiwmtQBSPil3VXgg49j1BSfaxIbIM07p4XSoMWpWklFXVKkG3 TzaA==
X-Gm-Message-State: AN3rC/6QdTuNdUxS7YDcoWJ9MXuRiG53M5n9AtY5qwCgfDRth1DPKMgO abk2nJLIewRdnq0SsWUZRuOodEqAsQ==
X-Received: by 10.107.187.199 with SMTP id l190mr11197970iof.86.1492717848416;  Thu, 20 Apr 2017 12:50:48 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.169.206 with HTTP; Thu, 20 Apr 2017 12:50:47 -0700 (PDT)
Received: by 10.107.169.206 with HTTP; Thu, 20 Apr 2017 12:50:47 -0700 (PDT)
In-Reply-To: <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Fri, 21 Apr 2017 05:50:47 +1000
X-Google-Sender-Auth: Qi-6VcVHkOYlIfe8mOybYrKbiH4
Message-ID: <CACweHNDjM5B_R5n2dqDF0Qeqn7yHAGq722OD+cCELej2KN2HRw@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: Doug Royer <douglasroyer@gmail.com>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c0766bc1adb66054d9e7584
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ixVXRFaoDHi49wDkB-JalrB1ios>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 19:50:50 -0000

--94eb2c0766bc1adb66054d9e7584
Content-Type: text/plain; charset=UTF-8

On 21 Apr. 2017 3:57 am, "Doug Royer" <douglasroyer@gmail.com> wrote:

On 04/20/2017 11:35 AM, Viktor Dukhovni wrote:

> On Thu, Apr 20, 2017 at 07:01:05PM +0200, Jon wrote:


       + Changing the private key can mean loss of access to email
>         encrypted under the old key.
>

Only if you throw away old keys. Doctor, Doctor, it hurts when I do this. -
So Do not do that :-)


       + Signatures stop verifying when the signature key expires,
>         even though they were valid at the the email was received.
>

Again, do not throw away the old keys. An MUA should not allow a user to
throw away any key needed for any message still in the store. Yep - complex.



... And re-import every old key when you switch to a new MUA. Sounds like
fun to enforce.

Cheers
-- 
Matthew Kerwin

--94eb2c0766bc1adb66054d9e7584
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 21 Apr. 2017 3:57 am, &quot;Doug Royer&quot; &lt;<a href=3D"ma=
ilto:douglasroyer@gmail.com">douglasroyer@gmail.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">On 04/=
20/2017 11:35 AM, Viktor Dukhovni wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Thu, Apr 20, 2017 at 07:01:05PM +0200, Jon wrote:</blockquote></div><div=
 class=3D"quoted-text">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 =C2=A0 =C2=A0+ Changing the private key can mean loss of acce=
ss to email<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 encrypted under the old key.<br>
</blockquote>
<br></div>
Only if you throw away old keys. Doctor, Doctor, it hurts when I do this. -=
 So Do not do that :-)<div class=3D"quoted-text"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 =C2=A0 =C2=A0+ Signatures stop verifying when the signature k=
ey expires,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 even though they were valid at the the email wa=
s received.<br>
</blockquote>
<br></div>
Again, do not throw away the old keys. An MUA should not allow a user to th=
row away any key needed for any message still in the store. Yep - complex.<=
br><div class=3D"elided-text"><br>
<br>
</div></blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D"=
auto">... And re-import every old key when you switch to a new MUA. Sounds =
like fun to enforce.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div=
><div class=3D"gmail_extra" dir=3D"auto">Cheers</div><div class=3D"gmail_ex=
tra" dir=3D"auto">--=C2=A0</div><div class=3D"gmail_extra" dir=3D"auto">Mat=
thew Kerwin</div><div class=3D"gmail_extra" dir=3D"auto"><br></div></div>

--94eb2c0766bc1adb66054d9e7584--


From nobody Thu Apr 20 13:11:05 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667B2131666 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 KmWD7Kghj733 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:01 -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 60FC113163C for <ietf@ietf.org>; Thu, 20 Apr 2017 13:11:01 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id j201so66151798oih.2 for <ietf@ietf.org>; Thu, 20 Apr 2017 13:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=7MXTheIWgh11iojvV/v7AKFWZwO8AoTKtRQES5BIN/w=; b=WFbIrwBNBUlJnpEGF8GcGDHT1GeuPq9gViWhbic1IVKbq2mdzE9yKpTIPtFA0dQ3Pa 7/VK0Je9BMF06cR6VDYPhe52OmZ/+1YPcQrNwn9D0WsydzMX78c4Kvkh5OCjr04RmYi9 2xww7fh1TNZbBOnLGSAYS+nkAOZFQhxozHVVrvMQA9s/ukiM8B9/dtsNUXA2Kn2bAB8z FpJAs9qMCrrHDX/3xOPNcjkoiqE276tZC4VTPh8Po9096jDayQck7k0A83OWwLCYvq4U BhPtDVTpFoEWqB9RJA3ryKfVFJO9rr/sBV1OhV+VszuH5yNgDJYQyAs/ty7sd8u5STSD PEEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=7MXTheIWgh11iojvV/v7AKFWZwO8AoTKtRQES5BIN/w=; b=qhz2I5LW6BonPLMlThn2ebTNmOqtCghyfT3JlrQUmD73hwcO3/Vaw3gUNTzvoqemWW An7txZb75RoNLFAEIexe2cAPrdcPePgVBOWHDY19g64PACyPfcTzx+IgtvaqThDCSP99 CMDLLm0+z7AYoW1QXim0ceI6x+nJD+llEIlskggehc14/Bl7rHp2vuu/3LepdjRDOj6A PNLCIrE5zvrvedrN/ARxKAcKUAPkXSM4aaOFC3MFJ3bIeTkaw72ai5Qwqy43t4Dqf3mW J1jTSuW9R4UgWDdH0kzj+cZeXHoAOIrwXFkkWTd+tWriEZJJIt/JCVNRBcLUCTjtBHGs 2hVQ==
X-Gm-Message-State: AN3rC/4Xs1h0skQY63RHH4UgSBAyVdwwYy7f8QwVT60m3qJaS6/u7+hK NCdOBiwkziQKdTFwXrRyR/e21XA1sg==
X-Received: by 10.157.42.132 with SMTP id e4mr6072671otb.86.1492719060713; Thu, 20 Apr 2017 13:11:00 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Thu, 20 Apr 2017 13:10:59 -0700 (PDT)
In-Reply-To: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca> <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 20 Apr 2017 16:10:59 -0400
X-Google-Sender-Auth: sAbGFukgz678TIuJUU9G1AySLtM
Message-ID: <CAMm+LwhpcmfOWdLFHyA-NP__5_a8=W67CAfxJDjf-pAZMUGZrA@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, Jon <jmoroney@hawaii.edu>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1103d25d0502054d9ebd99
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qk-OfpRTaPwTSvsQCS-EDZCLMe8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 20:11:03 -0000

--94eb2c1103d25d0502054d9ebd99
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sharon Boyen and I wrote this up as an RFC a while back:

https://tools.ietf.org/html/rfc4386


The weakness as I see it is that it still lacks the data necessary to make
the decision whether to use the key or not. In particular:

Alice@example.com sends a message to Bob@example.net

Forget the issue of trust for a moment, the infrastructure should deliver
all the information that Alice's email client needs:

* Is encryption refused, optional or required?
* Which encryption protocols are supported (OpenPGP, S/MIME)?
* Which key(s) should be used?

Note that this is only the raw information, a client would also have to
decide whether the information was trustworthy or not. Though if the email
would be sent en-clair otherwise, that does not matter much.


For ubiquitous use of message level encryption, it is essential to take
into account the fact that spam and malware filtering is actually a bigger
concern than confidentiality:

END TO END ENCRYPTION IS NOT A PRIVILEGE I WILL EXTEND TO ANONYMOUS SENDERS

So encrypted mail is going to have to be signed by an authorized sender for
end to end encryption to be permitted. Everything else goes through the
filters as usual.

I am working on code right now: Prismproof.org


On Thu, Apr 20, 2017 at 10:36 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

>
> On 20 Apr 2017, at 17:22, Paul Wouters <paul@nohats.ca> wrote:
>
>
> generate a key pair on registration, store those keys on the server (in
> an encrypted archive), and make the public key available. A little
> coding later and we've got key exchange and message confidentiality.
>
>
> SMTP servers could be key servers without having the private key of
> individuals?
>
>
> Sure. If they double as HTTPS servers.
>
> I want to send you an email, so I type =E2=80=9Cpaul@nohats.ca=E2=80=9D i=
n the To: field,
> and my MUA goes to https://mail-public-keys.nohats.ca/.well-known/mail-
> pubkeys/paul and that gets your public key.
>
> And now my MUA can encrypt.  And it all works, as long as we trust
> nohats.ca (and conversely gmail.com) and as long as you have a copy of
> your private key on every single MUA that you use.
>
> Small assumptions, no?
>
> Yoav
>
>

--94eb2c1103d25d0502054d9ebd99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default">Sharon Boyen and I wrote this=
 up as an RFC a while back:</div><div class=3D"gmail_default"><br></div><di=
v class=3D"gmail_default"><a href=3D"https://tools.ietf.org/html/rfc4386">h=
ttps://tools.ietf.org/html/rfc4386</a><br></div><div class=3D"gmail_default=
"><br></div><div class=3D"gmail_default"><br></div><div class=3D"gmail_defa=
ult">The weakness as I see it is that it still lacks the data necessary to =
make the decision whether to use the key or not. In particular:</div><div c=
lass=3D"gmail_default"><br></div><div class=3D"gmail_default"><a href=3D"ma=
ilto:Alice@example.com">Alice@example.com</a> sends a message to <a href=3D=
"mailto:Bob@example.net">Bob@example.net</a></div><div class=3D"gmail_defau=
lt"><br></div><div class=3D"gmail_default">Forget the issue of trust for a =
moment, the infrastructure should deliver all the information that Alice&#3=
9;s email client needs:</div><div class=3D"gmail_default"><br></div><div cl=
ass=3D"gmail_default">* Is encryption refused, optional or required?</div><=
div class=3D"gmail_default">* Which encryption protocols are supported (Ope=
nPGP, S/MIME)?</div><div class=3D"gmail_default">* Which key(s) should be u=
sed?</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_defaul=
t">Note that this is only the raw information, a client would also have to =
decide whether the information was trustworthy or not. Though if the email =
would be sent en-clair otherwise, that does not matter much.</div><div clas=
s=3D"gmail_default"><br></div><div class=3D"gmail_default"><br></div><div c=
lass=3D"gmail_default">For ubiquitous use of message level encryption, it i=
s essential to take into account the fact that spam and malware filtering i=
s actually a bigger concern than confidentiality:</div><div class=3D"gmail_=
default"><br></div><div class=3D"gmail_default">END TO END ENCRYPTION IS NO=
T A PRIVILEGE I WILL EXTEND TO ANONYMOUS SENDERS</div><div class=3D"gmail_d=
efault"><br></div><div class=3D"gmail_default">So encrypted mail is going t=
o have to be signed by an authorized sender for end to end encryption to be=
 permitted. Everything else goes through the filters as usual.</div><div cl=
ass=3D"gmail_default"><br></div><div class=3D"gmail_default">I am working o=
n code right now: Prismproof.org</div><div class=3D"gmail_default"><br></di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, A=
pr 20, 2017 at 10:36 AM, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:y=
nir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">=
<span class=3D""><br><div><div>On 20 Apr 2017, at 17:22, Paul Wouters &lt;<=
a href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</a>&gt; w=
rote:</div><div><br></div><blockquote type=3D"cite"><div><div><br><blockquo=
te type=3D"cite">generate a key pair on registration, store those keys on t=
he server (in<br>an encrypted archive), and make the public key available. =
A little<br>coding later and we&#39;ve got key exchange and message confide=
ntiality.<br></blockquote><br>SMTP servers could be key servers without hav=
ing the private key of<br>individuals?<br></div></div></blockquote></div><b=
r></span><div>Sure. If they double as HTTPS servers.</div><div><br></div><d=
iv>I want to send you an email, so I type =E2=80=9C<a href=3D"mailto:paul@n=
ohats.ca" target=3D"_blank">paul@nohats.ca</a>=E2=80=9D in the To: field, a=
nd my MUA goes to <a href=3D"https://mail-public-keys.nohats.ca/.well-known=
/mail-pubkeys/paul" target=3D"_blank">https://mail-public-keys.<wbr>nohats.=
ca/.well-known/mail-<wbr>pubkeys/paul</a>=C2=A0and that gets your public ke=
y.</div><div><br></div><div>And now my MUA can encrypt.=C2=A0 And it all wo=
rks, as long as we trust <a href=3D"http://nohats.ca" target=3D"_blank">noh=
ats.ca</a>=C2=A0(and conversely <a href=3D"http://gmail.com" target=3D"_bla=
nk">gmail.com</a>) and as long as you have a copy of your private key on ev=
ery single MUA that you use.</div><div><br></div><div>Small assumptions, no=
?</div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Y=
oav</div><div><br></div></font></span></div></blockquote></div><br></div>

--94eb2c1103d25d0502054d9ebd99--


From nobody Thu Apr 20 13:11:33 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4AE129C1A for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:32 -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, RP_MATCHES_RCVD=-0.001] 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 1LTnaHdX7HXG for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:30 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.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 693681293F2 for <ietf@ietf.org>; Thu, 20 Apr 2017 13:11:30 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w894J54ldzDH9; Thu, 20 Apr 2017 22:11:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492719088; bh=bsHQ17iuNKR22a5bOYBuSEMB6TmwCEIWWJisKIHWzNY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=IdHGbr7Lat+QVxLWTQugl0e2xYISLdDhwzVYMMNAD3swvpikf7VNC6Ca8SLjVfb3v 8OWYLrgleG8SJijVqH1BXTxTpXZAv3z3TgLtaw8eiafrv2ZEC4I1uBphtHE+ofhkqS UY/mV4e0l9NTaCcStfUxSAOGOf2I02thLGf3fi+0=
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 ZiVKbep4seoD; Thu, 20 Apr 2017 22:11:27 +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; Thu, 20 Apr 2017 22:11:27 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id EF405418565; Thu, 20 Apr 2017 16:11:26 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca EF405418565
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EA27B40B7F47; Thu, 20 Apr 2017 16:11:26 -0400 (EDT)
Date: Thu, 20 Apr 2017 16:11:26 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Nico Williams <nico@cryptonector.com>
cc: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <20170420192604.GF2856@localhost>
Message-ID: <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o6At8IFtjti1mWhPbdJvuErf9L8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 20:11:32 -0000

On Thu, 20 Apr 2017, Nico Williams wrote:

> Part of the problem is that there is very little work being done on
> MUAs.

I think there is just no work to be done. Decrypt the email on the MUA
and store/use it as any uncrypted email now and run the OS or at least
the user's directory using a disk encryption system.

Paul


From nobody Thu Apr 20 13:55:01 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0E3C1316B1 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 pv3xArWHpBVd for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:54:58 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3605F1316A8 for <ietf@ietf.org>; Thu, 20 Apr 2017 13:54:58 -0700 (PDT)
Received: (qmail 42035 invoked from network); 20 Apr 2017 20:54:56 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2017 20:54:56 -0000
Date: 20 Apr 2017 20:54:34 -0000
Message-ID: <20170420205434.24400.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s3vcCY_q5teXofd9rZSh7rE_v8I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 20:55:00 -0000

In article <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> you write:
>> SMTP servers could be key servers without having the private key of
>> individuals?
>
>Sure. If they double as HTTPS servers.

As others have noted, this topic has come up more than a few times before.

Here's a recent draft we wrote for a simple per domain https key
server, based almost entirely on existing standards.  It distributes
public keys.  Managing your private keys on all of your MUAs remains
as intractable a problem as it's always been.

https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/

R's,
John


From nobody Thu Apr 20 15:37:34 2017
Return-Path: <RCosta@alticelabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF43129BAA for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 15:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 2vayRiSVQcG0 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 15:37:30 -0700 (PDT)
Received: from smtp2.telecom.pt (smtp2.telecom.pt [83.240.175.146]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E93B129431 for <ietf@ietf.org>; Thu, 20 Apr 2017 15:37:29 -0700 (PDT)
From: Rui Costa <RCosta@alticelabs.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 20 Apr 2017 23:37:24 +0100
Subject: RE: Why are mail servers not also key servers?
Thread-Topic: Why are mail servers not also key servers?
Thread-Index: AdK6Emay6zlYaFQkRdWPkn/07evviAAA7Atg
Message-ID: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
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/ietf/cuek9LCFB2k0JA-hCBhkhtfCqJo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 22:37:32 -0000

Although having read some of the DANE discussions that took place ~1 year a=
go, being PGP illiterate, a little less about SMTP, certificates, ... i don=
't understand this:=09

Cryptography (at least "in the beginning") was created for E2E communicatio=
n, independently of your network's layers or the hops/people it goes throug=
h.=09
PK allowed something Caeser (or D=F6nitz, or other Enigma's users, or...) h=
adn't: the ability to avoid the 2 E2Es having to meet in order to set new k=
eys.=09

I guess (maybe wrongly) certificates handle something the internet brought,=
 formerly inexistent: the answer to "is this person that sent me her/his pu=
blic key REALLY the person she/he says to be, with whom i want to talk to?"=
 In other words, some means of trust/signature, once "we can't see" with wh=
om we speak/write.=09



So, can someone point me to some URL/documentation/https://mailarchive.ietf=
.org/arch/msg/ietf/xyz explaining the point on having keys/cryptography som=
ewhere in between these 2 end points? (And thus i guess i'm saying i don't =
understand cryptography's point on scenarios other than what i think people=
 have called on these threads "E2E".)=09


Some time ago a friend of mine told me her company changed the old firewall=
/proxy into zscaler. When the browser presented her new certificates asking=
 her trust, she asked network support why didn't they explain people the im=
plications: often on lunch breaks people use the network for private purpos=
es like going to the bank, f.i. Network support pointed her to corporation =
network support which said it was that corporation's company own decision. =
She asked her director, that told her "we'll talk about it in the afternoon=
", an afternoon ~2 years ago. This makes me wonder whether people that have=
 to take these decisions understand the implications.=09

Most people think "https" means they're talking directly to the other end v=
ia a secure channel, know nothing about "man in the middle" or similar conc=
epts. Why give them false confidence on scenarios other than E2E?=09

King Regards,=09
Rui=09


From nobody Thu Apr 20 16:41:11 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A592A128792 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 16:41:10 -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, RP_MATCHES_RCVD=-0.001] 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 kjGR8bmkrsNb for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 16:41:08 -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 6234C128DE5 for <ietf@ietf.org>; Thu, 20 Apr 2017 16:41:08 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w8Fk8045cz3F8; Fri, 21 Apr 2017 01:41:04 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492731664; bh=dKmdLFgjlaDlUuXazwtjd1LUeF8iSsx4lYI6FLqAXbI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=aOFQJF11CTzYv1M6IB/MzRS123noLLZHBsFfuiD6ITl2Q6yKkQK1L0yhCVnCxlvdS pnEvFCv+RTEhli2PwA7FBWv7kRxtVy6IdXukYBhpxfyJ5pryek6EJASUDF5E6OvzdI EOY1+jsALW3zrBpk+sOYh3kLMEW3tKaVlpxDRtyI=
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 Jy2GpNy1safK; Fri, 21 Apr 2017 01:41:00 +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; Fri, 21 Apr 2017 01:41:00 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 4D865418565; Thu, 20 Apr 2017 19:40:59 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 4D865418565
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 30A7F40D811F; Thu, 20 Apr 2017 19:40:59 -0400 (EDT)
Date: Thu, 20 Apr 2017 19:40:59 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Rui Costa <RCosta@alticelabs.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Why are mail servers not also key servers?
In-Reply-To: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
Message-ID: <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca> <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kn9Zv-6EByURXkaZ5wLc3c6m53s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 23:41:11 -0000

On Thu, 20 Apr 2017, Rui Costa wrote:

> So, can someone point me to some URL/documentation/https://mailarchive.ietf.org/arch/msg/ietf/xyz explaining the point on having keys/cryptography somewhere in between these 2 end points? (And thus i guess i'm saying i don't understand cryptography's point on scenarios other than what i think people have called on these threads "E2E".)

I want to send you an encrypted email. I need your key. I can send a
plaintext email asking you for the key. I have to hope that it really
reached you and that it is you who gave me the key and that the key
was not modified in transport.

versus:

You publish your key somewhere with a verifiable link of key to your
email address. Now your first contact with me will be encrypted and
secured.

People have different ideas of what minimums and maximums to use
for "verifiable link of key to email" (or even key to human)

Paul


From nobody Thu Apr 20 17:26:21 2017
Return-Path: <RCosta@alticelabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24618129BE8 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 17:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 G6AYRGKIIA8b for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 17:26:17 -0700 (PDT)
Received: from smtp2.telecom.pt (smtp2.telecom.pt [83.240.175.146]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F18261293E9 for <ietf@ietf.org>; Thu, 20 Apr 2017 17:26:16 -0700 (PDT)
From: Rui Costa <RCosta@alticelabs.com>
To: Paul Wouters <paul@nohats.ca>
CC: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 21 Apr 2017 01:26:10 +0100
Subject: RE: Why are mail servers not also key servers?
Thread-Topic: Why are mail servers not also key servers?
Thread-Index: AdK6Emay6zlYaFQkRdWPkn/07evviAAA7AtgAAaDhYA=
Message-ID: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D6@PTPTVDEX02.PTPortugal.corpPT.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca> <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
In-Reply-To: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
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/ietf/lT8eCwnRfRGDPYjY89agx9_ofKo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 00:26:20 -0000

Thanks Paul. We're considering untrustable email/DNS/... servers. OK.=09

This particular email hasn't any jurisprudence value. However, it could hav=
e the same value as a registered letter, couldn't it? (Can't layers' emails=
?) I suppose the difference is some digital signature, which i guess will m=
ean some certificate issued by some trusted entity. (Which means, at least =
once, the 2 ends can't avoid "having to meet" (not to set new keys but) to =
know each other's signature. (I actually don't know which entity grants the=
m.))=09

Why doesn't that solve the doubt about "who gave [...] the key"? And again,=
 what have the networks in between to do with it?=09

In traditional mail, the only thing one needs is the delivery registry and =
signatures. (Perhaps wrongly, i'm extrapolating Portuguese law to other cou=
ntries'.) From that, you're sure you're writing who you want to write to. I=
f on top of that you want, both of you can exchange keys and encrypt. Howev=
er, that's inside the envelope. The mail service doesn't really care or kno=
w what's in there and wouldn't understand the message if the envelope was v=
iolated. Its role is simply...=09
-transport=09
-providing you the proof you sent the letter=09
-providing you the proof the other end sent you the receipt (with its own s=
ignature)=09

(But i fear you'll point out why this won't work with email, if you carry o=
n the babysitting :-) Kind Regards=09

-----Original Message-----
From: Paul Wouters [mailto:paul@nohats.ca]=20
Sent: 21 de abril de 2017 00:41
To: Rui Costa
Cc: ietf@ietf.org
Subject: RE: Why are mail servers not also key servers?

On Thu, 20 Apr 2017, Rui Costa wrote:

> So, can someone point me to some=20
> URL/documentation/https://mailarchive.ietf.org/arch/msg/ietf/xyz=20
> explaining the point on having keys/cryptography somewhere in between=20
> these 2 end points? (And thus i guess i'm saying i don't understand=20
> cryptography's point on scenarios other than what i think people have=20
> called on these threads "E2E".)

I want to send you an encrypted email. I need your key. I can send a plaint=
ext email asking you for the key. I have to hope that it really reached you=
 and that it is you who gave me the key and that the key was not modified i=
n transport.

versus:

You publish your key somewhere with a verifiable link of key to your email =
address. Now your first contact with me will be encrypted and secured.

People have different ideas of what minimums and maximums to use for "verif=
iable link of key to email" (or even key to human)

Paul




-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Rui Costa
Sent: 20 de abril de 2017 23:37
To: ietf@ietf.org
Subject: RE: Why are mail servers not also key servers?

Although having read some of the DANE discussions that took place ~1 year a=
go, being PGP illiterate, a little less about SMTP, certificates, ... i don=
't understand this:=09

Cryptography (at least "in the beginning") was created for E2E communicatio=
n, independently of your network's layers or the hops/people it goes throug=
h.=09
PK allowed something Caeser (or D=F6nitz, or other Enigma's users, or...) h=
adn't: the ability to avoid the 2 E2Es having to meet in order to set new k=
eys.=09

I guess (maybe wrongly) certificates handle something the internet brought,=
 formerly inexistent: the answer to "is this person that sent me her/his pu=
blic key REALLY the person she/he says to be, with whom i want to talk to?"=
 In other words, some means of trust/signature, once "we can't see" with wh=
om we speak/write.=09



So, can someone point me to some URL/documentation/https://mailarchive.ietf=
.org/arch/msg/ietf/xyz explaining the point on having keys/cryptography som=
ewhere in between these 2 end points? (And thus i guess i'm saying i don't =
understand cryptography's point on scenarios other than what i think people=
 have called on these threads "E2E".)=09


Some time ago a friend of mine told me her company changed the old firewall=
/proxy into zscaler. When the browser presented her new certificates asking=
 her trust, she asked network support why didn't they explain people the im=
plications: often on lunch breaks people use the network for private purpos=
es like going to the bank, f.i. Network support pointed her to corporation =
network support which said it was that corporation's company own decision. =
She asked her director, that told her "we'll talk about it in the afternoon=
", an afternoon ~2 years ago. This makes me wonder whether people that have=
 to take these decisions understand the implications.=09

Most people think "https" means they're talking directly to the other end v=
ia a secure channel, know nothing about "man in the middle" or similar conc=
epts. Why give them false confidence on scenarios other than E2E?=09

King Regards,=09
Rui=09


From nobody Thu Apr 20 17:43:44 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF7312EA8C; Thu, 20 Apr 2017 17:43:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-isis-l2bundles.all@ietf.org, ietf@ietf.org, isis-wg@ietf.org
Subject: Opsdir telechat review of draft-ietf-isis-l2bundles-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149273541553.22376.11208485483295858450@ietfa.amsl.com>
Date: Thu, 20 Apr 2017 17:43:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gdiZaBo89seJLnYf_k1SbvaBGfk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 00:43:36 -0000

Reviewer: Mahesh Jethanandani
Review result: Has Issues

I have reviewed this document as part of the Operational
directorate’s ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be
included in AD reviews during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last
call comments.

Document reviewed:  draft-ietf-isis-l2bundles-04

Summary: 

There are deployments where the Layer 3 interface on which IS-IS
operates is a Layer 2 interface bundle.  Existing IS-IS advertisements
only support advertising link attributes of the Layer 3 interface. If
entities external to IS-IS wish to control traffic flows on the
individual physical links which comprise the Layer 2 interface bundle
link attribute information about the bundle members is required.

Document Status:

Has Issues

Comments:

The following comments look at the document both from an operational
perspective as well as a management perspective. 

Operational Considerations:

Operational considerations include installation and initial setup,
migration path, requirements on other protocols, impact on network
operations and verification of correct operation.

Advertisement of these link attributes needs to be configured,
including which attributes will be advertised. While there are some
attributes, e.g. max link bandwidth, which can be learnt and
advertised, there are others that need configuration. What is not
clear from the draft is which of the attributes should be configured
as  a minimum, and if they can have default values that they can
carry.

Since these are TLVs, it is assumed that the controller that does not
understand the advertisement will ignore the TLV. From a network
operations perspective, there will be more of these advertisements
that need to be sent, and will have to tracked and maintained by the
controller.

Whether these advertisements result in a correct operation is not
obvious, because there is no feedback mechanism on how these
advertisements are being used, other than watching the changes that
happen from a TE perspective.

Management Considerations:

Management considerations include interoperability, fault management,
configuration management, accounting, performance and security.

The attributes being advertised are additional to existing link
attributes. In that sense, it is new and additional information, as
does not impact existing operations. Controllers that understand the
new advertisements will use them, and those that do not, will ignore
them. Interoperability therefore, should not be impacted.

However, there is no discussion of fault management. For example, if
one of the links in the bundle goes down, are the attribute values
updated to reflect the new state of the bundle. There is also no
definition of how these attributes are configured on the box. Ideally,
we should see a YANG model defining the new attributes that can be
configured for advertisement.

As discussed above, there is no accounting for how these new
advertisements are being used, or whether they are being used by the
controller at all. Updates to TE as a result of these advertisements
should be accounted to indicate the effectiveness of the new
advertisements.

Performance should not be an issue, as these are advertisements, even
if they take up a small amount of additional bandwidth for
advertisement.

Finally, and importantly, the draft needs to address the question of
security, even if it means pointing to a boiler plate set of drafts
that deal with similar issues. It would be hard to believe that there
are no security considerations to be had.

A run of idnits revealed no errors, flaws, or warnings. There were 3
comments though

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Possible downref: Non-RFC (?) normative reference: ref.
'IEEE802.1AX'

  -- Possible downref: Non-RFC (?) normative reference: ref.
'ISO10589'


     Summary: 0 errors (**), 0 flaws (~~), 0 warnings (==), 3 comments
(--).



From nobody Thu Apr 20 18:44:52 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753C9129B28; Thu, 20 Apr 2017 18:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.022
X-Spam-Level: 
X-Spam-Status: No, score=-14.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 q75m-19qnvda; Thu, 20 Apr 2017 18:44:43 -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 CEA85129AC1; Thu, 20 Apr 2017 18:44:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9074; q=dns/txt; s=iport; t=1492739082; x=1493948682; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FQcOFq7EubK/EGRY6DMUEMuHhJDmnwdDEnfPSlBeYZM=; b=KQbhO289IKBZ0mqkf7YCdEkVOSvHpD1W2rUfeywmLeDrlazGOReT2l/B keswfXjOwICEglrEy4IABW1gwGZPyGigU4/Zk+zWf8ubjiY4fiptwzlMO sFlSPffQD5ZCNy/OHUQ+oOt4MnyTZw5AUmne2gUBieHz3Y2VMgO3njpfj A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BTAQDmYvlY/49dJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1SBbQeDYIoVkWiIHo1Fgg+GJAIag2Q/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAgEMFxFFBQcEAgEGAg4DBAEBAwIjAwICAh8RFAEICAIEAQ0FCIl8Aw0Ij?= =?us-ascii?q?E6dXYImhy4Ng2YBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQuFSIFcAYMZglGCLIJ?= =?us-ascii?q?ggl8FnHk7AY45hECRXosQiQMBHziBBWMVhyl1iCGBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,227,1488844800"; d="scan'208";a="17574349"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Apr 2017 01:44:41 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3L1ifjd019429 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 21 Apr 2017 01:44:41 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Apr 2017 20:44:40 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Thu, 20 Apr 2017 20:44:40 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-isis-l2bundles.all@ietf.org" <draft-ietf-isis-l2bundles.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Opsdir telechat review of draft-ietf-isis-l2bundles-04
Thread-Topic: Opsdir telechat review of draft-ietf-isis-l2bundles-04
Thread-Index: AQHSujhRu8Bbwjbrzkiw0v6PO9WOMqHPCMzA
Date: Fri, 21 Apr 2017 01:44:40 +0000
Message-ID: <6a2db34731a3402ba7112bcb611e760b@XCH-ALN-001.cisco.com>
References: <149273541553.22376.11208485483295858450@ietfa.amsl.com>
In-Reply-To: <149273541553.22376.11208485483295858450@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.152.147]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EAqrLHzbBwVRkpH4UqYyAAjqn4s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 01:44:44 -0000

TWFoZXNoIC0NCg0KVGhhbnggZm9yIHRoZSByZXZpZXcuDQpSZXNwb25zZXMgaW5saW5lLiBMZXQg
bWUga25vdyBpZiB0aGVzZSBhZGVxdWF0ZWx5IGFkZHJlc3MgeW91ciBjb21tZW50cy4NCg0KDQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE1haGVzaCBKZXRoYW5hbmRhbmkg
W21haWx0bzptamV0aGFuYW5kYW5pQGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEFwcmls
IDIwLCAyMDE3IDU6NDQgUE0NCj4gVG86IG9wcy1kaXJAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWll
dGYtaXNpcy1sMmJ1bmRsZXMuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGll
dGYub3JnDQo+IFN1YmplY3Q6IE9wc2RpciB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1p
c2lzLWwyYnVuZGxlcy0wNA0KPiANCj4gUmV2aWV3ZXI6IE1haGVzaCBKZXRoYW5hbmRhbmkNCj4g
UmV2aWV3IHJlc3VsdDogSGFzIElzc3Vlcw0KPiANCj4gSSBoYXZlIHJldmlld2VkIHRoaXMgZG9j
dW1lbnQgYXMgcGFydCBvZiB0aGUgT3BlcmF0aW9uYWwNCj4gZGlyZWN0b3JhdGXigJlzwqBvbmdv
aW5nIGVmZm9ydCB0byByZXZpZXcgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBi
eQ0KPiB0aGUgSUVTRy4gwqBUaGVzZcKgY29tbWVudHMgd2VyZSB3cml0dGVuIHdpdGggdGhlIGlu
dGVudCBvZiBpbXByb3ZpbmcgdGhlDQo+IG9wZXJhdGlvbmFswqBhc3BlY3RzIG9mIHRoZSBJRVRG
IGRyYWZ0cy4gQ29tbWVudHMgdGhhdCBhcmUgbm90IGFkZHJlc3NlZCBpbg0KPiBsYXN0IGNhbGwg
bWF5IGJlIGluY2x1ZGVkIGluIEFEIHJldmlld3MgZHVyaW5nIHRoZSBJRVNHIHJldmlldy4gwqBE
b2N1bWVudA0KPiBlZGl0b3JzIGFuZMKgV0cgY2hhaXJzIHNob3VsZCB0cmVhdCB0aGVzZSBjb21t
ZW50cyBqdXN0IGxpa2UgYW55IG90aGVyIGxhc3QNCj4gY2FsbMKgY29tbWVudHMuDQo+IA0KPiBE
b2N1bWVudCByZXZpZXdlZDogwqBkcmFmdC1pZXRmLWlzaXMtbDJidW5kbGVzLTA0DQo+IA0KPiBT
dW1tYXJ5Og0KPiANCj4gVGhlcmUgYXJlIGRlcGxveW1lbnRzIHdoZXJlIHRoZSBMYXllciAzIGlu
dGVyZmFjZSBvbiB3aGljaCBJUy1JUyBvcGVyYXRlcw0KPiBpcyBhIExheWVyIDIgaW50ZXJmYWNl
IGJ1bmRsZS4gIEV4aXN0aW5nIElTLUlTIGFkdmVydGlzZW1lbnRzIG9ubHkgc3VwcG9ydA0KPiBh
ZHZlcnRpc2luZyBsaW5rIGF0dHJpYnV0ZXMgb2YgdGhlIExheWVyIDMgaW50ZXJmYWNlLiBJZiBl
bnRpdGllcyBleHRlcm5hbCB0byBJUy1JUw0KPiB3aXNoIHRvIGNvbnRyb2wgdHJhZmZpYyBmbG93
cyBvbiB0aGUgaW5kaXZpZHVhbCBwaHlzaWNhbCBsaW5rcyB3aGljaCBjb21wcmlzZQ0KPiB0aGUg
TGF5ZXIgMiBpbnRlcmZhY2UgYnVuZGxlIGxpbmsgYXR0cmlidXRlIGluZm9ybWF0aW9uIGFib3V0
IHRoZSBidW5kbGUNCj4gbWVtYmVycyBpcyByZXF1aXJlZC4NCj4gDQo+IERvY3VtZW50IFN0YXR1
czoNCj4gDQo+IEhhcyBJc3N1ZXMNCj4gDQo+IENvbW1lbnRzOg0KPiANCj4gVGhlIGZvbGxvd2lu
ZyBjb21tZW50cyBsb29rIGF0IHRoZSBkb2N1bWVudCBib3RoIGZyb20gYW4gb3BlcmF0aW9uYWwN
Cj4gcGVyc3BlY3RpdmUgYXMgd2VsbCBhcyBhIG1hbmFnZW1lbnQgcGVyc3BlY3RpdmUuDQo+IA0K
PiBPcGVyYXRpb25hbCBDb25zaWRlcmF0aW9uczoNCj4gDQo+IE9wZXJhdGlvbmFsIGNvbnNpZGVy
YXRpb25zIGluY2x1ZGUgaW5zdGFsbGF0aW9uIGFuZCBpbml0aWFsIHNldHVwLCBtaWdyYXRpb24N
Cj4gcGF0aCwgcmVxdWlyZW1lbnRzIG9uIG90aGVyIHByb3RvY29scywgaW1wYWN0IG9uIG5ldHdv
cmsgb3BlcmF0aW9ucyBhbmQNCj4gdmVyaWZpY2F0aW9uIG9mIGNvcnJlY3Qgb3BlcmF0aW9uLg0K
PiANCj4gQWR2ZXJ0aXNlbWVudCBvZiB0aGVzZSBsaW5rIGF0dHJpYnV0ZXMgbmVlZHMgdG8gYmUg
Y29uZmlndXJlZCwgaW5jbHVkaW5nDQo+IHdoaWNoIGF0dHJpYnV0ZXMgd2lsbCBiZSBhZHZlcnRp
c2VkLiBXaGlsZSB0aGVyZSBhcmUgc29tZSBhdHRyaWJ1dGVzLCBlLmcuIG1heA0KPiBsaW5rIGJh
bmR3aWR0aCwgd2hpY2ggY2FuIGJlIGxlYXJudCBhbmQgYWR2ZXJ0aXNlZCwgdGhlcmUgYXJlIG90
aGVycyB0aGF0DQo+IG5lZWQgY29uZmlndXJhdGlvbi4gV2hhdCBpcyBub3QgY2xlYXIgZnJvbSB0
aGUgZHJhZnQgaXMgd2hpY2ggb2YgdGhlIGF0dHJpYnV0ZXMNCj4gc2hvdWxkIGJlIGNvbmZpZ3Vy
ZWQgYXMgIGEgbWluaW11bSwgYW5kIGlmIHRoZXkgY2FuIGhhdmUgZGVmYXVsdCB2YWx1ZXMgdGhh
dA0KPiB0aGV5IGNhbiBjYXJyeS4NCj4gDQoNCltMZXM6XSBUaGVyZSBpcyBubyBkZWZhdWx0L21p
bmltdW0gc2V0IG9mIGF0dHJpYnV0ZXMuIFdoYXQgYXR0cmlidXRlcyB3aWxsIGJlIGFkdmVydGlz
ZWQgYXJlIGRldGVybWluZWQgYnkgdGhlIHVzZSBjYXNlLiBXaGF0IHRoaXMgZHJhZnQgaXMgZGVm
aW5pbmcgaXMgdGhlIHRyYW5zcG9ydCBpLmUuLCB3aGF0IGF0dHJpYnV0ZSBhZHZlcnRpc2VtZW50
cyB0aGUgcHJvdG9jb2wgaXMgY2FwYWJsZSBvZiBhZHZlcnRpc2luZy4gQXMgd2l0aCB0cmFkaXRp
b25hbCBURSB3aGF0IGF0dHJpYnV0ZXMgYXJlIGFjdHVhbGx5IGFkdmVydGlzZWQgaXMgZGV0ZXJt
aW5lZCBieSB0aGUgYXBwbGljYXRpb24uDQoNCj4gU2luY2UgdGhlc2UgYXJlIFRMVnMsIGl0IGlz
IGFzc3VtZWQgdGhhdCB0aGUgY29udHJvbGxlciB0aGF0IGRvZXMgbm90DQo+IHVuZGVyc3RhbmQg
dGhlIGFkdmVydGlzZW1lbnQgd2lsbCBpZ25vcmUgdGhlIFRMVi4gRnJvbSBhIG5ldHdvcmsNCj4g
b3BlcmF0aW9ucyBwZXJzcGVjdGl2ZSwgdGhlcmUgd2lsbCBiZSBtb3JlIG9mIHRoZXNlIGFkdmVy
dGlzZW1lbnRzIHRoYXQNCj4gbmVlZCB0byBiZSBzZW50LCBhbmQgd2lsbCBoYXZlIHRvIHRyYWNr
ZWQgYW5kIG1haW50YWluZWQgYnkgdGhlIGNvbnRyb2xsZXIuDQo+IA0KPiBXaGV0aGVyIHRoZXNl
IGFkdmVydGlzZW1lbnRzIHJlc3VsdCBpbiBhIGNvcnJlY3Qgb3BlcmF0aW9uIGlzIG5vdCBvYnZp
b3VzLA0KPiBiZWNhdXNlIHRoZXJlIGlzIG5vIGZlZWRiYWNrIG1lY2hhbmlzbSBvbiBob3cgdGhl
c2UgYWR2ZXJ0aXNlbWVudHMgYXJlDQo+IGJlaW5nIHVzZWQsIG90aGVyIHRoYW4gd2F0Y2hpbmcg
dGhlIGNoYW5nZXMgdGhhdCBoYXBwZW4gZnJvbSBhIFRFDQo+IHBlcnNwZWN0aXZlLg0KPiANCg0K
W0xlczpdIFRoZSBkZWZpbml0aW9uIG9mICJjb3JyZWN0IG9wZXJhdGlvbiIgZGVwZW5kcyB1cG9u
IHRoZSB1c2UgY2FzZS4gSVMtSVMgaXMgc2ltcGx5IHRyYW5zcG9ydGluZyB0aGUgYXR0cmlidXRl
cyBhZHZlcnRpc2VtZW50cy4gSXQgaXMgdW5hd2FyZSBvZiBob3cgdGhlc2UgYWR2ZXJ0aXNlbWVu
dHMgYXJlIGJlaW5nIHVzZWQgYW5kIGhvdyB0cmFmZmljIG1heSBiZSBhZmZlY3RlZCBieSB0aGUg
dXNlIG9mIHRoZXNlIGFkdmVydGlzZW1lbnRzLiBTbyBpdCBpcyB0aGUgYXBwbGljYXRpb24ocykg
d2hpY2ggdXNlIHRoaXMgaW5mb3JtYXRpb24gd2hpY2ggbmVlZCB0byBkZWZpbmUgd2hhdCBiZWhh
dmlvciBpcyBleHBlY3RlZC4NCg0KPiBNYW5hZ2VtZW50IENvbnNpZGVyYXRpb25zOg0KPiANCj4g
TWFuYWdlbWVudCBjb25zaWRlcmF0aW9ucyBpbmNsdWRlIGludGVyb3BlcmFiaWxpdHksIGZhdWx0
IG1hbmFnZW1lbnQsDQo+IGNvbmZpZ3VyYXRpb24gbWFuYWdlbWVudCwgYWNjb3VudGluZywgcGVy
Zm9ybWFuY2UgYW5kIHNlY3VyaXR5Lg0KPiANCj4gVGhlIGF0dHJpYnV0ZXMgYmVpbmcgYWR2ZXJ0
aXNlZCBhcmUgYWRkaXRpb25hbCB0byBleGlzdGluZyBsaW5rIGF0dHJpYnV0ZXMuIEluDQo+IHRo
YXQgc2Vuc2UsIGl0IGlzIG5ldyBhbmQgYWRkaXRpb25hbCBpbmZvcm1hdGlvbiwgYXMgZG9lcyBu
b3QgaW1wYWN0IGV4aXN0aW5nDQo+IG9wZXJhdGlvbnMuIENvbnRyb2xsZXJzIHRoYXQgdW5kZXJz
dGFuZCB0aGUgbmV3IGFkdmVydGlzZW1lbnRzIHdpbGwgdXNlDQo+IHRoZW0sIGFuZCB0aG9zZSB0
aGF0IGRvIG5vdCwgd2lsbCBpZ25vcmUgdGhlbS4gSW50ZXJvcGVyYWJpbGl0eSB0aGVyZWZvcmUs
DQo+IHNob3VsZCBub3QgYmUgaW1wYWN0ZWQuDQo+IA0KPiBIb3dldmVyLCB0aGVyZSBpcyBubyBk
aXNjdXNzaW9uIG9mIGZhdWx0IG1hbmFnZW1lbnQuIEZvciBleGFtcGxlLCBpZiBvbmUgb2YNCj4g
dGhlIGxpbmtzIGluIHRoZSBidW5kbGUgZ29lcyBkb3duLCBhcmUgdGhlIGF0dHJpYnV0ZSB2YWx1
ZXMgdXBkYXRlZCB0byByZWZsZWN0DQo+IHRoZSBuZXcgc3RhdGUgb2YgdGhlIGJ1bmRsZS4gVGhl
cmUgaXMgYWxzbyBubyBkZWZpbml0aW9uIG9mIGhvdyB0aGVzZQ0KPiBhdHRyaWJ1dGVzIGFyZSBj
b25maWd1cmVkIG9uIHRoZSBib3guIElkZWFsbHksIHdlIHNob3VsZCBzZWUgYSBZQU5HIG1vZGVs
DQo+IGRlZmluaW5nIHRoZSBuZXcgYXR0cmlidXRlcyB0aGF0IGNhbiBiZSBjb25maWd1cmVkIGZv
ciBhZHZlcnRpc2VtZW50Lg0KPiANCg0KW0xlczpdIENlcnRhaW5seSBpZiB0aGUgYnVuZGxlIG1l
bWJlcnNoaXAgY2hhbmdlcyB0aGVzZSBjaGFuZ2UgTVVTVCBiZSByZWZsZWN0ZWQgaW4gdGhlIGFk
dmVydGlzZW1lbnRzIGkuZS4sIHJlbW92YWwvYWRkaXRpb24gb2YgYSBidW5kbGUgbWVtYmVyIE1V
U1QgcmVzdWx0IGluIHJlbW92YWwvYWRkaXRpb24gb2YgYWR2ZXJ0aXNlbWVudHMgYXNzb2NpYXRl
ZCB3aXRoIHRoYXQgYnVuZGxlIG1lbWJlci4NCklmIGEgYnVuZGxlIG1lbWJlciBpcyBkb3duIHRo
aXMgc2hvdWxkIGJlIHJlZmxlY3RlZCBpbiB0aGUgc2FtZSB3YXkgdGhhdCBMMyBhZHZlcnRpc2Vt
ZW50cyBhcmUgd2l0aGRyYXduIHdoZW4gYSBnaXZlbiBMMyBsaW5rIGdvZXMgZG93bi4NCg0KTWVh
bnMgb2YgY29uZmlndXJhdGlvbiBvZiBsaW5rIGF0dHJpYnV0ZXMgaXMgb3V0IG9mIHNjb3BlIGZv
ciB0aGlzIGRyYWZ0LiBJIHdvdWxkIGV4cGVjdCBzdWNoIGNvbmZpZ3VyYXRpb24gdG8gYmUgYXBw
bGllZCBpbiB0aGUgY29udGV4dCBvZiB0aGUgYnVuZGxlIG1lbWJlciBpbnRlcmZhY2VzLg0KDQo+
IEFzIGRpc2N1c3NlZCBhYm92ZSwgdGhlcmUgaXMgbm8gYWNjb3VudGluZyBmb3IgaG93IHRoZXNl
IG5ldw0KPiBhZHZlcnRpc2VtZW50cyBhcmUgYmVpbmcgdXNlZCwgb3Igd2hldGhlciB0aGV5IGFy
ZSBiZWluZyB1c2VkIGJ5IHRoZQ0KPiBjb250cm9sbGVyIGF0IGFsbC4gVXBkYXRlcyB0byBURSBh
cyBhIHJlc3VsdCBvZiB0aGVzZSBhZHZlcnRpc2VtZW50cyBzaG91bGQgYmUNCj4gYWNjb3VudGVk
IHRvIGluZGljYXRlIHRoZSBlZmZlY3RpdmVuZXNzIG9mIHRoZSBuZXcgYWR2ZXJ0aXNlbWVudHMu
DQo+IA0KDQpbTGVzOl0gVGhpcyBhbHNvIGZhbGxzIGluIHRoZSBzY29wZSBvZiB0aGUgYXBwbGlj
YXRpb24uIElTLUlTIGRvZXMgbm90IGtub3cgaG93IG9yIGlmIGxpbmsgYXR0cmlidXRlcyBhcmUg
dXNlZC4NCg0KPiBQZXJmb3JtYW5jZSBzaG91bGQgbm90IGJlIGFuIGlzc3VlLCBhcyB0aGVzZSBh
cmUgYWR2ZXJ0aXNlbWVudHMsIGV2ZW4gaWYNCj4gdGhleSB0YWtlIHVwIGEgc21hbGwgYW1vdW50
IG9mIGFkZGl0aW9uYWwgYmFuZHdpZHRoIGZvciBhZHZlcnRpc2VtZW50Lg0KPiANCj4gRmluYWxs
eSwgYW5kIGltcG9ydGFudGx5LCB0aGUgZHJhZnQgbmVlZHMgdG8gYWRkcmVzcyB0aGUgcXVlc3Rp
b24gb2Ygc2VjdXJpdHksDQo+IGV2ZW4gaWYgaXQgbWVhbnMgcG9pbnRpbmcgdG8gYSBib2lsZXIg
cGxhdGUgc2V0IG9mIGRyYWZ0cyB0aGF0IGRlYWwgd2l0aCBzaW1pbGFyDQo+IGlzc3Vlcy4gSXQg
d291bGQgYmUgaGFyZCB0byBiZWxpZXZlIHRoYXQgdGhlcmUgYXJlIG5vIHNlY3VyaXR5IGNvbnNp
ZGVyYXRpb25zDQo+IHRvIGJlIGhhZC4NCj4gDQoNCltMZXM6XSBBZ3JlZWQuIFNlY3VyaXR5IHNl
Y3Rpb24gc2hvdWxkIHJlZmVyZW5jZSB0aGUgc3RhbmRhcmQgc2VjdXJpdHkgc3BlY2lmaWNhdGlv
bnMgZm9yIHRoZSBwcm90b2NvbCAoUkZDIDUzMDQvUkZDIDUzMTApLg0KDQo+IEEgcnVuIG9mIGlk
bml0cyByZXZlYWxlZCBubyBlcnJvcnMsIGZsYXdzLCBvciB3YXJuaW5ncy4gVGhlcmUgd2VyZSAz
DQo+IGNvbW1lbnRzIHRob3VnaA0KPiANCj4gICAgICAoU2VlIFJGQ3MgMzk2NyBhbmQgNDg5NyBm
b3IgaW5mb3JtYXRpb24gYWJvdXQgdXNpbmcgbm9ybWF0aXZlIHJlZmVyZW5jZXMNCj4gICAgICB0
byBsb3dlci1tYXR1cml0eSBkb2N1bWVudHMgaW4gUkZDcykNCj4gDQo+ICAgLS0gUG9zc2libGUg
ZG93bnJlZjogTm9uLVJGQyAoPykgbm9ybWF0aXZlIHJlZmVyZW5jZTogcmVmLg0KPiAnSUVFRTgw
Mi4xQVgnDQo+IA0KPiAgIC0tIFBvc3NpYmxlIGRvd25yZWY6IE5vbi1SRkMgKD8pIG5vcm1hdGl2
ZSByZWZlcmVuY2U6IHJlZi4NCj4gJ0lTTzEwNTg5Jw0KPg0KW0xlczpdIFRoZXNlIHdhcm5pbmdz
IGFyZSBzZWVuIHdoZW4gcmVmZXJlbmNpbmcgbm9uLVJGQyBkb2N1bWVudHMuIFRoZSByZWZlcmVu
Y2VkIGRvY3VtZW50cyBhcmUgc3RhbmRhcmRzIGFuZCBhcmUgY29ycmVjdGx5IGlkZW50aWZpZWQg
YXMgbm9ybWF0aXZlIHJlZmVyZW5jZXMuDQoNCiAgICBMZXMNCiANCj4gDQo+ICAgICAgU3VtbWFy
eTogMCBlcnJvcnMgKCoqKSwgMCBmbGF3cyAofn4pLCAwIHdhcm5pbmdzICg9PSksIDMgY29tbWVu
dHMgKC0tKS4NCj4gDQoNCg==


From nobody Thu Apr 20 19:12:23 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9003B128796 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 19:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, 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 Lr_ogpfWRuUM for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 19:12:20 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6496D126D85 for <ietf@ietf.org>; Thu, 20 Apr 2017 19:12:20 -0700 (PDT)
Received: (qmail 87968 invoked from network); 21 Apr 2017 02:12:18 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2017 02:12:18 -0000
Date: 21 Apr 2017 02:11:56 -0000
Message-ID: <20170421021156.25637.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D6@PTPTVDEX02.PTPortugal.corpPT.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uWvHoP2uHNKhiw0G_MsNem2Q7IM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 02:12:22 -0000

In article <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D6@PTPTVDEX02.PTPortugal.corpPT.com> you write:
>Thanks Paul. We're considering untrustable email/DNS/... servers. OK.	
>
>This particular email hasn't any jurisprudence value. However, it could have the same value as a registered letter, couldn't it?

Postal mail isn't a very good analogy here.  Registered postal mail
depends on a trusted third party, the government post office, to make
assertions about the mail it handles.  It typically provides two
services.  One is reliable delivery of valuable physical objects like
jewelry which doesn't apply to e-mail.  The other is to prove that one
party sent a message to a second, even if the second party doesn't
want it and won't sign for it.  (The usual example is a letter from
your insurance company saying they've canceled your policy.)  In the
US they're separate services Registered and Certified mail, elsewhere
they're usually combined.

E-mail crypto doesn't do either of those things.  A digital signature
says that this message really came from whoever, with the physical
analogy being a notary stamp.  Encrypted e-mail doesn't promise that
the mail will be delivered, but makes a negative promise that it will
not be delivered to (or at least read by) anyone but the person with
the key.

If a recipient is cooperative, and sends you back a message signed
with the same key to which you encrypted the message, that tells you
he got it, but that's not a very interesting case.

In the real world we have centuries of law and practice that tell
notaries how to verify someone's identity, and tell recipients what
the value of a notary stamp is.  In e-mail, we have the web of trust
for PGP and for S/MIME third party CAs (or DANE domain assertions)
none of which map very well into the way we manage identities in the
normal world.

R's,
John


From nobody Thu Apr 20 20:35:43 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0FC129533 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 20:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqDhqayLISmV for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 20:35:39 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 CA87012EAA5 for <ietf@ietf.org>; Thu, 20 Apr 2017 20:35:37 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id j201so76932312oih.2 for <ietf@ietf.org>; Thu, 20 Apr 2017 20:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=wuzTclmvFyP+0VRPCv6hGo/RBwTPclCi47QVXQ3uzM4=; b=fCPUhcSJfbjEQcnZXH6e/fDrryU+5VTwZnjE2WwOUn4gX2dcTFOvKEsyjrRYNx9l8q RZxqtCvZ895OA+AajkBNFDwzYPD1NdBTlNAq0kUUM7vjS9tTockB3ZzbNabRh6V0NMh4 3Q8vykLTX0pw4GhiSG9fWarUoKMt4BrOU5pO6FXSz4i9YGm2wPODJfoE0qT5SMXCmzVb KA3lQfWv1GhJGyAnqaSg6prn96oS7fAS1GCbdVjkqunJRk8KKpvDpkzBbmNcco9inkAJ ggB5EQwrt/F9oXB+4dl7ZQsvH6FAIECVcDbe80olHXSSWKE9viYKkDjXWhCwNZCBgaGc R5CQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=wuzTclmvFyP+0VRPCv6hGo/RBwTPclCi47QVXQ3uzM4=; b=FbdxZxVAMz32wTpcysIJv684FwQtWvn2P4APrxdcZOUh0ypRkStsRTSSbH2bBPkmqm wQv5vsBRQgdiqeXzgDCHHn/7OoHpsPvQ1jPdf7I7iR55Kk85K6XQXKp4BMYIpXvnouDO z+UU1CLNYrBucsT0FepC9nFKxOydbRrPosqybvgy2qyROlB7B6dIvvKh+f21642tT3px FCL+507AczCwbHm4XlUo7EHDTsebNnB6IX/m21HqxSNXN5o0gJp/xiBlyHUN4z1FJlN7 Sz3AcAMVbP6+yi3kU/sZ3N+It5ofM8p4PlugOFHCuhleI26uitFIdhuTBezCKJDR8uqL wjYQ==
X-Gm-Message-State: AN3rC/6wNBZikhSC0r7bfEd1Q6nPNxQqOfXCMS/Ei2Q8FBMsDT2LT8+Z rG28Lb59ptJ1kARj/iw=
X-Received: by 10.157.22.161 with SMTP id c30mr6233516ote.247.1492745736686; Thu, 20 Apr 2017 20:35:36 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id n64sm3540561oif.22.2017.04.20.20.35.34 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 20:35:35 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca> <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com> <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <c4b3cfbe-9420-e171-8d0f-18d21b6e451d@gmail.com>
Date: Thu, 20 Apr 2017 21:35:33 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070000080306040105040208"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7JlZQ79KAfRmyj9RcOUE4ADd9Mg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 03:35:42 -0000

This is a cryptographically signed message in MIME format.

--------------ms070000080306040105040208
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/20/2017 05:40 PM, Paul Wouters wrote:
> On Thu, 20 Apr 2017, Rui Costa wrote:
>=20
>> So, can someone point me to some=20
>> URL/documentation/https://mailarchive.ietf.org/arch/msg/ietf/xyz=20
>> explaining the point on having keys/cryptography somewhere in between =

>> these 2 end points? (And thus i guess i'm saying i don't understand=20
>> cryptography's point on scenarios other than what i think people have =

>> called on these threads "E2E".)
>=20
> I want to send you an encrypted email. I need your key. I can send a
> plaintext email asking you for the key. I have to hope that it really
> reached you and that it is you who gave me the key and that the key
> was not modified in transport.
>

You send me a signed email from a mutually trusted source. I now have=20
your public key, because you can extract it from the signed S/MIME=20
email. (I am guessing you can do this with PGP.)

I can now send you an encrypted email, and it includes my public key, so =

you can decrypt it.

There are free email cert companies. This email is signed by one (unless =

the list server strips them out like it used to). Your MUA now knows my=20
public key.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMDMzNTMzWjAvBgkqhkiG9w0BCQQxIgQgRBPXmns7HRsxK/FrH5zeivYUQNze7xUz
ZUy57QuZ9OEwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAg7gaCdmU9Xi4
8PlsluMcBpD+WfWe6JgEC3X/Ba410rZ0TMAMLqGJCLBAN9tUlTLRVEmtDT4dYykzVL0+VPZ2
ZHRgxn3nQDqpW/CZvf6Ujh5xQYy5cQgHbGP4dVNXZQaPAuZp1BmYE5hsQT2+AWw7Z+ZT/gJ5
JAU/qtGNnS6odS7LK85WfoLnv56Ina2B3gUfOmo1f/X2eH/qe+97TOCKwvQZQgtPrEgh+04T
vlCOJxH9sF3GQt9ec2/u1JnDjnfhHXBsUDCDcWbKs15rrH89JssL1j12nMYMj83TwgvmlgVP
pzB8yYktP/hzSfPuBAjZoTCe7DU/9xIOvb2ivaYnnQAAAAAAAA==
--------------ms070000080306040105040208--


From nobody Thu Apr 20 21:03:57 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F224129470 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mj3MbB-LQP6Y for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:03:54 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 6D314128D69 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:03:54 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id r203so76843185oib.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:03:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=uOolkFaWj1hxEF2us8yXKze4AQrSoae19QzOJLTybA4=; b=HVQx0ZlBvaxdKIHOIpQTYhTns1l60HNSmeSG+LTcrS59iK+FTm6HRN+dRnuTyMKXOJ XJUVlAkXL3Jxga1T25pMabboyzNlY7xUh5IZSIOPiwyn6vC5sBNyoq3kKZJcHnkiyd0V 9pbS9XEb6OVduyiAnhaL4oLwJISaKfSWO2XKS5Lp1sLWgmqzx4v3knVce8rdoX/cO0tk SVerjAmRqEHDMqq/GPZV+HfIY1KOcRI0Am1Y9C838s7CxCKRLD6FYSpugk3c50fc+Anq 9pHpIlm/KD7Dci7Kwlw71MCVx2Bz8hq9c1z95cLFp9uQoB5oNiLj8V445K/vp7MYby7e eTTA==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=uOolkFaWj1hxEF2us8yXKze4AQrSoae19QzOJLTybA4=; b=KHV3pkILRmKT5Q4kFRvuIQVG1w68JPj9a5v2GZL9m/XYey8IGr7qKslZpHmAoHw474 nNOEQhGQjDGdwKmRyleI/GgT0l+cth6Imf4wM6rnK5i49aIOqGlgh/VzZgoytNPqtz60 JUEPB8jzKw4O8N6lldWEJo8a67KAIUhbQYg0qvk0dNeUOWbiShdcpWDS5NoEC7vh8id9 YO+FNpqqzM3DTsfb9ro8gojK8Tv+7OQCl1j1Ou31jnAW5FEIzOldigkTyU8uyVcmOmpp bkxBvWwLqveKit1fkh25tNtSMgBugzJX5o57kGnW4XJIfkn5wg26nEGA/oaIgV3UOugx ALBg==
X-Gm-Message-State: AN3rC/5MBRCAQ4jkFFTncIyWf+tHYAlNGxglbv4chPMI9HK2D8u0qMWE LOvQ2oGYpk5OqCp1PjI=
X-Received: by 10.157.80.142 with SMTP id b14mr6292117oth.151.1492747433221; Thu, 20 Apr 2017 21:03:53 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id e204sm3545429oia.35.2017.04.20.21.03.50 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 21:03:51 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: IETF Discussion Mailing List <ietf@ietf.org>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca> <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com> <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <9d66d8d2-6c75-31c2-6364-e7becd2b81ea@gmail.com>
Date: Thu, 20 Apr 2017 22:03:49 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080602000408000607020905"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ShU_N2M3gmnPJp1oIAXLPhv9DBo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 04:03:56 -0000

This is a cryptographically signed message in MIME format.

--------------ms080602000408000607020905
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/20/2017 05:40 PM, Paul Wouters wrote:
> On Thu, 20 Apr 2017, Rui Costa wrote:
>=20
> I want to send you an encrypted email. I need your key. I can send a
> plaintext email asking you for the key. I have to hope that it really
> reached you and that it is you who gave me the key and that the key
> was not modified in transport.
>

There are free email cert companies. This email is signed by one (unless =

the list server strips them out like it used to). Your MUA now knows my=20
public key.

This is how it is done. I know it works with Thunderbird and Outlook.

To send a signed email, I only had to configure my MUA once. Thunderbird =

and Outlook always S/MIME signs all of my email with the free cert I use.=


You send me a signed (not encrypted) email from a *mutually trusted*=20
cert source. Your MUA signed it with your private key, because that's=20
how its done. Only your public key can verify it.

My MUA examines the email, extracts your public key that is included in=20
an S/MIME signed email, verifies it was signed by the mutually trusted=20
cert source. I now know the 'From' email address matches the signature,=20
the content, and the only way your MUA could have generated those=20
sequence of bits, is that it was signed by your matching private key.

I now have your public key. Verified by a email message signature that=20
could have only been signed by the matching private key, which validate=20
against the trusted cert source. Who cares if the world sees your public =

key - that the point of a public key.

If someone were to modify the message in transit (only some of the=20
headers are used in the signature verification), the signature will fail =

to validate. Then my MUA would tag it as bad signature and should be=20
un-trusted.

Thunderbird signifies a good signature with an image of a letter, with a =

red seal.

When my MUA validates that the signature matches the email content, then =

the recipient MUA knows nothing was altered, including the public key,=20
which it keeps.

Thunderbird and Outlook collect these certs by default. I do not have to =

do anything. I can even export them to a file, and import them into=20
another MUA.

I can now send you an encrypted email, encrypted with my private key and =

your public key. Only your MUA can open it with your private key and my=20
public key, and in that process, also validates it.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMDQwMzQ5WjAvBgkqhkiG9w0BCQQxIgQghdh19C5zBlk74skwwaBXmxuOG0FZyLb1
d1yQv2DLTnQwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAuNqW6dnGUmtS
Nqaro3infB56V78nwzW9Cm8wa52Uz6YaaIO8Y40vuY9acOMuyczmIpfbpan12YkAEHVpGUZk
NTfwhSnURUQiIBMHqlIhnsqvhmR9pYt1yM9amvCRDAb3mnvCqYyINOtWfjAO/NDgiLVQxEZ2
JDspUCIPOOjcHKrUcfNnioAMj8fgCxB+bs6JPTEpjz6LgJ+zjSPqnHcYNJGfdA/HWqy4pQDN
CVqC95dFyT9ntFH0onoA4n5752bXX1YTCKKjw5j+KDBJXskknz1tCspSPprYE3lnshIeKJD8
y0rpmxmtZ98Kbmrx5llbeWf5vxWamOyboMKL9qijIQAAAAAAAA==
--------------ms080602000408000607020905--


From nobody Thu Apr 20 21:52:42 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE49129470 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5geKuEXrtxnw for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:52:40 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::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 291A1129462 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:52:40 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id c80so38918190lfh.3 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:52:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5rJihUgtz5CUBixMvJQ2pTgKV64Axb40BQ8gDfehHeY=; b=imdlvmdtP/pWVy0F65Q9wTkXx2FvwYl5RlbIfDq4x1kGVUcfprjRvaocEWqeQV8rKs HnFalkvJ7USTkOqs8lZLBh0X6Qcb7tCikJ/QD3nbfZ9+dalsbNOleAwQQdPgunBYUeSQ oWCVO9wZrw9zaLOULNO9EZMzlvUPXQsGg0hy2b1s31/UimgdrTHAsTldRXa6qNrP/yqp hEXiPckfyqTB5Hy/attn5z3XneDqTTEK8RzgarT6+sCkrKRe8wL2zoldufFJP+rOOiqr kDARw0wyfWRC7a0sflWk8DJR+en80G5iH8aEgRZljcVS3O6AIIhZmzNrqxFcIBl6oKEt 8ZbA==
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=5rJihUgtz5CUBixMvJQ2pTgKV64Axb40BQ8gDfehHeY=; b=ikh6+E0x9XIsjfxvhsGpxK9+yvakBWyB/Tl3oUVnQ/uJwVzT0j8pq6BmT/KYki7lpU korrDZREl+BAemnwCS86NaNdlfmQlDvPS3b8JeF+0aPB3wz6Xd8xLRV7glETI2Y70G/m 8cWZX5yHMW0OQLWLABwXTrBrQQW3XdGjJ2U48m4oE7mEtnM/wzy6MW4jJDzaVXn8CVEw 7VoexnpP8961YpHPllkLokj2sByiYr0GGEfZPbdZBruDdUgEmZzHymoLfoiNsY4ImWpb OUzVapdLYCec7DLJiaBmOItvvjYaQj47vmRZX3UNhFRMt6kMJdiazE3aZ/knLhPGhQyi /yxg==
X-Gm-Message-State: AN3rC/5FDAmRCXn4siaFBvLq6mFiPCf0SGHo20qZakCSmpZCJipwn04Q ADMYlt4tS/GWUwusoL1uvwDZjZJb/6Rd
X-Received: by 10.46.14.10 with SMTP id 10mr4033570ljo.22.1492750358382; Thu, 20 Apr 2017 21:52:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.2 with HTTP; Thu, 20 Apr 2017 21:52:37 -0700 (PDT)
In-Reply-To: <20170421021156.25637.qmail@ary.lan>
References: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D6@PTPTVDEX02.PTPortugal.corpPT.com> <20170421021156.25637.qmail@ary.lan>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 21 Apr 2017 14:52:37 +1000
Message-ID: <CABkgnnVmJf66ZJLToFm9_o34P3FswezVRFguuFrgMJeQv_TMgg@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: John Levine <johnl@taugh.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bMy8BgOy0FFfnnJrar5nD-uELPM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 04:52:42 -0000

On 21 April 2017 at 12:11, John Levine <johnl@taugh.com> wrote:
>
> If a recipient is cooperative, and sends you back a message signed
> with the same key to which you encrypted the message, that tells you
> he got it, but that's not a very interesting case.

It's also abuse of the cryptographic primitives, I hope that this
isn't really how it works and you are eliding certain key details.


From nobody Thu Apr 20 21:53:32 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9528A129457 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 C29o4rgOVPV6 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 21:53:27 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 965C1129458 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:53:27 -0700 (PDT)
Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v3L4mrDp104189 for <ietf@ietf.org>; Fri, 21 Apr 2017 00:53:22 -0400
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0b-001b2d01.pphosted.com with ESMTP id 29y02dsfff-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Apr 2017 00:53:22 -0400
Received: from localhost by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 20 Apr 2017 22:53:21 -0600
Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 20 Apr 2017 22:53:20 -0600
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v3L4rKpb7995900 for <ietf@ietf.org>; Thu, 20 Apr 2017 21:53:20 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 12B6CC604A for <ietf@ietf.org>; Thu, 20 Apr 2017 22:53:20 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id E343BC603C for <ietf@ietf.org>; Thu, 20 Apr 2017 22:53:19 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v3L4rI4f017126 for <ietf@ietf.org>; Fri, 21 Apr 2017 00:53:19 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v3L4rHmN017109 for ietf@ietf.org; Fri, 21 Apr 2017 00:53:17 -0400
From: narten@us.ibm.com
Date: Fri, 21 Apr 2017 00:53:17 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17042104-0020-0000-0000-00000BCB9085
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006947; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000208; SDB=6.00850310; UDB=6.00420015; IPR=6.00629030;  BA=6.00005305; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015117; XFM=3.00000013; UTC=2017-04-21 04:53:21
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17042104-0021-0000-0000-00005BD707E0
Message-Id: <201704210453.v3L4rHmN017109@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-21_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704210090
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ksLiWi8VkivPSpP5Tnow_QNxirI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 04:53:31 -0000

Total of 118 messages in the last 7 days.
 
script run at: Fri Apr 21 00:53:12 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.24% |    5 | 17.84% |   298173 | eng.khaled.omar@hotmail.com
  5.93% |    7 |  5.20% |    86884 | jordi.palet@consulintel.es
  0.85% |    1 |  7.87% |   131517 | aretana@cisco.com
  5.08% |    6 |  3.39% |    56622 | tte@cs.fau.de
  3.39% |    4 |  3.66% |    61237 | douglasroyer@gmail.com
  4.24% |    5 |  2.66% |    44532 | stewart.bryant@gmail.com
  4.24% |    5 |  2.47% |    41272 | dhc@dcrocker.net
  2.54% |    3 |  3.56% |    59463 | martin.thomson@gmail.com
  3.39% |    4 |  2.01% |    33558 | nico@cryptonector.com
  3.39% |    4 |  1.98% |    33065 | paul@nohats.ca
  2.54% |    3 |  2.46% |    41184 | ynir.ietf@gmail.com
  3.39% |    4 |  1.57% |    26246 | randy@psg.com
  2.54% |    3 |  1.91% |    31861 | stephen.farrell@cs.tcd.ie
  2.54% |    3 |  1.67% |    27890 | job@instituut.net
  0.85% |    1 |  3.14% |    52535 | kathleen.moriarty.ietf@gmail.com
  2.54% |    3 |  1.43% |    23932 | mcr+ietf@sandelman.ca
  2.54% |    3 |  1.42% |    23743 | ietf-dane@dukhovni.org
  1.69% |    2 |  1.53% |    25624 | lear@cisco.com
  1.69% |    2 |  1.39% |    23276 | brian.raymor@microsoft.com
  1.69% |    2 |  1.30% |    21711 | nalini.elkins@insidethestack.com
  1.69% |    2 |  1.22% |    20451 | joelja@bogus.com
  1.69% |    2 |  1.20% |    20092 | jmoroney@hawaii.edu
  0.85% |    1 |  2.03% |    33883 | kaliloudama@yahoo.fr
  1.69% |    2 |  1.17% |    19534 | rcosta@alticelabs.com
  1.69% |    2 |  1.08% |    17977 | michal@krsek.cz
  1.69% |    2 |  1.06% |    17727 | brian.e.carpenter@gmail.com
  1.69% |    2 |  0.96% |    15990 | fgont@si6networks.com
  1.69% |    2 |  0.86% |    14352 | cabo@tzi.org
  0.85% |    1 |  1.68% |    28123 | vint@google.com
  1.69% |    2 |  0.82% |    13659 | johnl@taugh.com
  0.85% |    1 |  1.64% |    27332 | oritl@microsoft.com
  0.85% |    1 |  1.26% |    21029 | hvdsomp@gmail.com
  0.85% |    1 |  0.98% |    16305 | jared@puck.nether.net
  0.85% |    1 |  0.89% |    14825 | klensin@jck.com
  0.85% |    1 |  0.87% |    14559 | ginsberg@cisco.com
  0.85% |    1 |  0.87% |    14473 | phill@hallambaker.com
  0.85% |    1 |  0.76% |    12633 | narten@us.ibm.com
  0.85% |    1 |  0.71% |    11931 | aafalk@akamai.com
  0.85% |    1 |  0.69% |    11457 | mellon@fugue.com
  0.85% |    1 |  0.65% |    10922 | steve@shinkuro.com
  0.85% |    1 |  0.64% |    10769 | matthew@kerwin.net.au
  0.85% |    1 |  0.62% |    10442 | bob.hinden@gmail.com
  0.85% |    1 |  0.60% |    10043 | vinayakh@gmail.com
  0.85% |    1 |  0.60% |    10009 | otroan@employees.org
  0.85% |    1 |  0.58% |     9666 | john-ietf@jck.com
  0.85% |    1 |  0.58% |     9655 | tobias.gondrom@gondrom.org
  0.85% |    1 |  0.58% |     9636 | ldaigle@thinkingcat.com
  0.85% |    1 |  0.57% |     9572 | buhrmi@gmail.com
  0.85% |    1 |  0.56% |     9345 | morrowc.lists@gmail.com
  0.85% |    1 |  0.54% |     8967 | mjethanandani@gmail.com
  0.85% |    1 |  0.52% |     8708 | paf@frobbit.se
  0.85% |    1 |  0.51% |     8476 | chopps@chopps.org
  0.85% |    1 |  0.48% |     8073 | jmh@joelhalpern.com
  0.85% |    1 |  0.46% |     7755 | heas@shrubbery.net
  0.85% |    1 |  0.44% |     7415 | dmznr@icloud.com
  0.85% |    1 |  0.42% |     7045 | bclaise@cisco.com
  0.85% |    1 |  0.40% |     6716 | nick@foobar.org
  0.85% |    1 |  0.36% |     6032 | iab-chair@iab.org
  0.85% |    1 |  0.33% |     5585 | carlosm3011@gmail.com
  0.85% |    1 |  0.33% |     5537 | francis.dupont@fdupont.fr
--------+------+--------+----------+------------------------
100.00% |  118 |100.00% |  1671025 | Total


From nobody Thu Apr 20 22:08:51 2017
Return-Path: <weigengyu@bupt.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60D3112940F for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 22:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.462
X-Spam-Level: 
X-Spam-Status: No, score=-1.462 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439, 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 z8ZncMYqoIOa for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 22:08:47 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 25A291293F5 for <ietf@ietf.org>; Thu, 20 Apr 2017 22:08:47 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.255.40.36]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 37D7919F36D; Fri, 21 Apr 2017 13:08:43 +0800 (HKT)
Message-ID: <A3E5E7239DC042BD8206DB35CD1A305F@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Brian Raymor" <Brian.Raymor@microsoft.com>, "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, <tsv-art@ietf.org>
Cc: <draft-ietf-core-coap-tcp-tls@ietf.org>, <core@ietf.org>, <ietf@ietf.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
In-Reply-To: <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Date: Fri, 21 Apr 2017 13:08:43 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tF_S7DTcj_fw90-xgDcLXN2wOuY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 05:08:49 -0000

Hi，

> It's possible to add language similar to the abort case, along the lines 
> of "When the underlying TCP connection is closed or reset,
> the CoAP connection is closed and in flight messages may be lost".

It is not necessary when CoAP over WEBSocket is concerned, I think.
By the API or the interface, CoAP only interacts with WEB socket, does not 
need to touch issues of TCP.
CoAP would react to the events of WebSokcet.

But, issues on TCP should be concerned if it is CoAP over TCP.

Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Brian Raymor
Sent: Friday, April 21, 2017 3:31 AM
To: Yoshifumi Nishida ; tsv-art@ietf.org
Cc: draft-ietf-core-coap-tcp-tls@ietf.org ; core@ietf.org ; ietf@ietf.org
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07


Thanks for your feedback.

> 1: It is not clear how the protocol reacts the errors from transport 
> layers (e.g. connection failure).
>    The protocol will just inform apps of the events and the app will 
> decide what to do or the protocol itself will do something?

The WebSockets case is addressed by RFC6455:

   When the underlying TCP connection is closed, it is said that _The
   WebSocket Connection is Closed_ and that the WebSocket connection is
   in the CLOSED state.  If the TCP connection was closed after the
   WebSocket closing handshake was completed, the WebSocket connection
   is said to have been closed _cleanly_.

-and-

   If at any point the underlying transport layer connection is
   unexpectedly lost, the client MUST _Fail the WebSocket Connection_.

It's possible to add language similar to the abort case, along the lines of 
"When the underlying TCP connection is closed or reset, the CoAP connection 
is closed and in flight messages may be lost".

> 2: There will be situations where the app layer is freezing while the
> transport layer is still working. Since transport layers cannot detect
> this type of failures, there should be some mechanisms for it somewhere in 
> the protocol or in the app layer.  The doc needs to address
> this point. For example, what will happen when a PONG message is not 
> returned for a certain amount of time?

PONG is modeled on similar mechanisms in RFC6455 and RFC7540. Neither 
provides any guidance for this case. It's expected that an application 
framework would define and enforce the appropriate policy for timeouts or 
retries.

> 3: Since this draft defines new SZX value, I think the doc needs to update 
> RFC7959. This point should be clarified more in the doc.

Carsten responded to this issue and the final exchange is here - 
https://www.ietf.org/mail-archive/web/core/current/msg08562.html

My sense is that we should treat this as an update to RFC7959 based on the 
original language:

     The value 7 for SZX (which would
      indicate a block size of 2048) is reserved, i.e., MUST NOT be sent
      and MUST lead to a 4.00 Bad Request response code upon reception
      in a request.

and the use of "extension" in coap-tcp-tls:

    The ’Block-wise Extension for Reliable Transport (BERT)’ extends the 
Block protocol
    to enable the use of larger messages over a reliable transport.

The existing IANA entries for Block1 and Block2 will also need to reference 
coap-tcp-tls in addition to RFC7959.

Tracking in https://github.com/core-wg/coap-tcp-tls/issues/129


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


From nobody Fri Apr 21 01:26:04 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBB71288B8; Fri, 21 Apr 2017 01:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, 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 8gs9nIIjJ9cq; Fri, 21 Apr 2017 01:25:46 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCDF4126CC7; Fri, 21 Apr 2017 01:25:45 -0700 (PDT)
Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A4B8A279C66; Fri, 21 Apr 2017 17:25:43 +0900 (JST)
Received: by mail-oi0-f49.google.com with SMTP id y11so52400910oie.0; Fri, 21 Apr 2017 01:25:43 -0700 (PDT)
X-Gm-Message-State: AN3rC/6396mJRhNyNXJaX0mk76s/nsdo1daScsz1xO/XHW7B959kPIE/ 4EtjqIYIFCOwOKqN5eujEl5/h8Txbw==
X-Received: by 10.202.97.85 with SMTP id v82mr7096714oib.214.1492763139122; Fri, 21 Apr 2017 01:25:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Fri, 21 Apr 2017 01:25:38 -0700 (PDT)
In-Reply-To: <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Fri, 21 Apr 2017 01:25:38 -0700
X-Gmail-Original-Message-ID: <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com>
Message-ID: <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com>
Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Brian Raymor <Brian.Raymor@microsoft.com>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113d45f4a42cd6054da900d7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i1wBp82Rf4jmHDd5QGP6RiJCuXc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 08:25:48 -0000

--001a113d45f4a42cd6054da900d7
Content-Type: text/plain; charset=UTF-8

Hi Brian,

On Thu, Apr 20, 2017 at 12:31 PM, Brian Raymor <Brian.Raymor@microsoft.com>
wrote:

>
> Thanks for your feedback.
>
> > 1: It is not clear how the protocol reacts the errors from transport
> layers (e.g. connection failure).
> >    The protocol will just inform apps of the events and the app will
> decide what to do or the protocol itself will do something?
>
> The WebSockets case is addressed by RFC6455:
>
>    When the underlying TCP connection is closed, it is said that _The
>    WebSocket Connection is Closed_ and that the WebSocket connection is
>    in the CLOSED state.  If the TCP connection was closed after the
>    WebSocket closing handshake was completed, the WebSocket connection
>    is said to have been closed _cleanly_.
>
> -and-
>
>    If at any point the underlying transport layer connection is
>    unexpectedly lost, the client MUST _Fail the WebSocket Connection_.
>
> It's possible to add language similar to the abort case, along the lines
> of "When the underlying TCP connection is closed or reset, the CoAP
> connection is closed and in flight messages may be lost".
>

OK. I also think we should state that the protocol should notify the
failure events to applications.
Since errors can happen not only in TCP, but also TLS and websocket level,
mentioning only TCP close or reset might not be enough.


>
> > 2: There will be situations where the app layer is freezing while the
> > transport layer is still working. Since transport layers cannot detect
> > this type of failures, there should be some mechanisms for it somewhere
> in the protocol or in the app layer.  The doc needs to address
> > this point. For example, what will happen when a PONG message is not
> returned for a certain amount of time?
>
> PONG is modeled on similar mechanisms in RFC6455 and RFC7540. Neither
> provides any guidance for this case. It's expected that an application
> framework would define and enforce the appropriate policy for timeouts or
> retries.
>

The figure 1 in the draft indicates that this draft and RFC7252 are in the
same level.
So, I am looking at this draft and 7252.
When we use 7252, I think applications basically don't need to implement
timeouts or retry mechanisms as the protocol provides such things.
However, when we use this one, it seems applications will need to have such
mechanisms. Isn't it a bit confusing? I am thinking that there need to be
some guidance here.
BTW, PONG is one example.


> > 3: Since this draft defines new SZX value, I think the doc needs to
> update RFC7959. This point should be clarified more in the doc.
>
> Carsten responded to this issue and the final exchange is here -
> https://www.ietf.org/mail-archive/web/core/current/msg08562.html
>
> My sense is that we should treat this as an update to RFC7959 based on the
> original language:
>
> I don't have a strong opinion here. Updating 7959 is fine for me if it's
clearer to CoAP people.

Thanks,
--
Yoshi

--001a113d45f4a42cd6054da900d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Brian,<div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Thu, Apr 20, 2017 at 12:31 PM, Brian Raymor <span dir=3D"l=
tr">&lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Bri=
an.Raymor@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><br>
Thanks for your feedback.<br>
<span class=3D""><br>
&gt; 1: It is not clear how the protocol reacts the errors from transport l=
ayers (e.g. connection failure).<br>
&gt;=C2=A0 =C2=A0 The protocol will just inform apps of the events and the =
app will decide what to do or the protocol itself will do something?<br>
<br>
</span>The WebSockets case is addressed by RFC6455:<br>
<br>
=C2=A0 =C2=A0When the underlying TCP connection is closed, it is said that =
_The<br>
=C2=A0 =C2=A0WebSocket Connection is Closed_ and that the WebSocket connect=
ion is<br>
=C2=A0 =C2=A0in the CLOSED state.=C2=A0 If the TCP connection was closed af=
ter the<br>
=C2=A0 =C2=A0WebSocket closing handshake was completed, the WebSocket conne=
ction<br>
=C2=A0 =C2=A0is said to have been closed _cleanly_.<br>
<br>
-and-<br>
<br>
=C2=A0 =C2=A0If at any point the underlying transport layer connection is<b=
r>
=C2=A0 =C2=A0unexpectedly lost, the client MUST _Fail the WebSocket Connect=
ion_.<br>
<br>
It&#39;s possible to add language similar to the abort case, along the line=
s of &quot;When the underlying TCP connection is closed or reset, the CoAP =
connection is closed and in flight messages may be lost&quot;.<br></blockqu=
ote><div><br></div><div>OK. I also think we should state that the protocol =
should notify the failure events to applications.=C2=A0</div><div>Since err=
ors can happen not only in TCP, but also TLS and websocket level, mentionin=
g only TCP close or reset might not be enough.</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<span class=3D""><br>
&gt; 2: There will be situations where the app layer is freezing while the<=
br>
&gt; transport layer is still working. Since transport layers cannot detect=
<br>
&gt; this type of failures, there should be some mechanisms for it somewher=
e in the protocol or in the app layer.=C2=A0 The doc needs to address<br>
&gt; this point. For example, what will happen when a PONG message is not r=
eturned for a certain amount of time?<br>
<br>
</span>PONG is modeled on similar mechanisms in RFC6455 and RFC7540. Neithe=
r provides any guidance for this case. It&#39;s expected that an applicatio=
n framework would define and enforce the appropriate policy for timeouts or=
 retries.<br></blockquote><div><br></div><div>The figure 1 in the draft ind=
icates that this draft and RFC7252 are in the same level.</div><div>So, I a=
m looking at this draft and 7252.=C2=A0</div><div>When we use 7252, I think=
 applications basically don&#39;t need to implement timeouts or retry mecha=
nisms as the protocol provides such things.=C2=A0</div><div>However, when w=
e use this one, it seems applications will need to have such mechanisms. Is=
n&#39;t it a bit confusing? I am thinking that there need to be some guidan=
ce here.</div><div>BTW, PONG is one example.=C2=A0</div><div><br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<span class=3D""><br>
&gt; 3: Since this draft defines new SZX value, I think the doc needs to up=
date RFC7959. This point should be clarified more in the doc.<br>
<br>
</span>Carsten responded to this issue and the final exchange is here - <a =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08562.html" r=
el=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mail-<wbr>archive/=
web/core/current/<wbr>msg08562.html</a><br>
<br>
My sense is that we should treat this as an update to RFC7959 based on the =
original language:<br><br></blockquote><div>I don&#39;t have a strong opini=
on here. Updating 7959 is fine for me if it&#39;s clearer to CoAP people.</=
div><div><br></div><div>Thanks,</div><div>--</div><div>Yoshi=C2=A0</div></d=
iv><br></div></div><div class=3D"gmail_extra"><br></div></div>

--001a113d45f4a42cd6054da900d7--


From nobody Fri Apr 21 05:06:22 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98833126B72 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 05:06:20 -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 r003ag_kBTcI for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 05:06:18 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 89E62120454 for <ietf@ietf.org>; Fri, 21 Apr 2017 05:06:18 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1d1XKL-0000DoC; Fri, 21 Apr 2017 14:06:17 +0200
Message-Id: <m1d1XKL-0000DoC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers? 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "Thu, 20 Apr 2017 21:35:33 -0600 ." <c4b3cfbe-9420-e171-8d0f-18d21b6e451d@gmail.com> 
Date: Fri, 21 Apr 2017 14:06:16 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/23cLJKD_omcebKOgHOooLzpSLRI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 12:06:20 -0000

>You send me a signed email from a mutually trusted source. I now have 
>your public key, because you can extract it from the signed S/MIME 
>email. (I am guessing you can do this with PGP.)

Just replying to a random part of the discussion.

Is there any kind of description and any kind of agreement of what attacks
secure mail is supposed to defend against?

Without a clear statement of what it is supposed to do, it is not possible
to figure out whether a proposal actually meets that goal. And without a
clear goal it is also not possible to figure out if the system is going to 
useful or not.

People have wildly different ideas of what e-mail security means. 

In the context of this discussion, one thing I'm curious about, and something
that should be clear from the description of the attack vectors, is who
controls a key.

To put it in terms of TLS certificates, is an e-mail key 'DV' or 'EV'?

It is easy to come up with lots of ways in which a domain holder can provide
a public key for a mailbox at that domain. But is that what we want?
In some cases, like corporate mailboxes, probably yes. In other cases,
journalists or activists with an e-mail account at a big e-mail provider,
probably not.



From nobody Fri Apr 21 06:35:40 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A29D81270A3 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 BP2TFBHgAwiQ for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:35:37 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 4328C1205F1 for <ietf@ietf.org>; Fri, 21 Apr 2017 06:35:37 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v3LDZZHW014918 for <ietf@ietf.org>; Fri, 21 Apr 2017 09:35:35 -0400 (EDT)
Date: Fri, 21 Apr 2017 09:35:35 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <20170421133535.GA21229@gsp.org>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wNdBtyWF3Jv6Eg6SIKVPybMY2js>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 13:35:39 -0000

On Thu, Apr 20, 2017 at 11:48:04AM -0600, Doug Royer wrote:
> I would like to see an extension so that the MUA could contact the
> destination server (perhaps their MX record host) and get a users PUBLIC
> key. Perhaps (just an idea - no screaming please) a new TXT record type that
> points to the domains PubKey server.

How's this going to work when the MUA is:

	- running on a host that's not connected to the 'net
	- running on a host that can't connect to MX's (because
		of local firewall rules)
	- running on a host that can't connect to MX's (because
		they're unreachable or down)
	- running on a host that can't connect to MX's (because
		they no longer exist)
	- running on a host that can connect to the MX's but can't
		get the user's public key because the user is no
		longer valid
	- and so on

There are way too many failure modes here that will render messages that
have already been received either temporarily or permanently unreadable.

---rsk


From nobody Fri Apr 21 06:53:19 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52D35120227 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZB99B0ZmOHF for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:53:15 -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 61D2D127444 for <ietf@ietf.org>; Fri, 21 Apr 2017 06:53:15 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id y11so63877683oie.0 for <ietf@ietf.org>; Fri, 21 Apr 2017 06:53:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=awFhWEsQd5uRobC2/+qzE/F/RH/t/ApxWlHoXxnDLac=; b=YLQvlOylv4Gti5XrCjpFkJ3yno+4+TMK0UuE6G2BSCcuoCKYIzTFR26WuOEvXQifKy VyzEqrtCBqEAy+dqwOqGUwpBdT9jNWDn4UtxEG0qJDLX1KXeEMHBPkLhzQOOfXvaHe9v Kor+r+UmdX3H6sELYzXzG4YRGoGZ659zsrOsmJePD2bsAcqFwDuhngNBhnGGnDTaOg0h Kh88U0xnJ4hoR2QdjrXDL65MtPZG97FQzJyq702mMRbwPaLlwzHdGo/5E/X/d7RQYiLm GQOv7yQN8WgZjVZbJMUncZ0Upm/sbZclkIa/+OUG0jwAJiNBHr5wkYMUJUT3SzQd8J+X 7hpw==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=awFhWEsQd5uRobC2/+qzE/F/RH/t/ApxWlHoXxnDLac=; b=tnOXQlhNkDwSpDQhjSi4hN3KrNXJT/6q8MFle2digywXa26FjOCDmZNkNZI47ltz27 dlejlz31WKwZx/bdHQlTznNbk06ln2MXBcc4Pwn3acXpB7V9xC49i5IUmdEoo6RxkmWy fNydxN0Tfo0XKEgrdNwiR4PoIOKKtUS/KPaTPSHiqsC5I1XqtMK/h9q/fwfXawCBxnZY uluEd+KmW/ZY+gdt45dpwX+9U0m+3PuUzf5L8TJltuCTzmviNcvnJTcFJy54Now5SWhS y6zy47582Qsv0DhZMosMRvOyyhGTtDgdKXmztMr3dz4onOI2s7VWo0ymsf93nhOcOI9+ o9yg==
X-Gm-Message-State: AN3rC/4CZBLdRCMi9Tsq78thcGmsQOQlpL7z3fSrqVfOVgdPc/PqXJXj 0nUKHfwIhDtwiZ5tDV4=
X-Received: by 10.157.51.87 with SMTP id u23mr7528629otd.191.1492782794378; Fri, 21 Apr 2017 06:53:14 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id c5sm4034917otb.40.2017.04.21.06.53.12 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 06:53:13 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <9440cd43-d8d9-8950-cdc7-bbf9fd2d7a91@gmail.com>
Date: Fri, 21 Apr 2017 07:53:11 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <20170421133535.GA21229@gsp.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms060504050000080608010500"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4rJwLW37h3KCCChhPHk2pixQKAM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 13:53:17 -0000

This is a cryptographically signed message in MIME format.

--------------ms060504050000080608010500
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/21/2017 07:35 AM, Rich Kulawiec wrote:
> On Thu, Apr 20, 2017 at 11:48:04AM -0600, Doug Royer wrote:
>> I would like to see an extension so that the MUA could contact the
>> destination server (perhaps their MX record host) and get a users PUBL=
IC
>> key. Perhaps (just an idea - no screaming please) a new TXT record typ=
e that
>> points to the domains PubKey server.
>=20
> How's this going to work when the MUA is:
>=20
> 	- running on a host that's not connected to the 'net
> 	- running on a host that can't connect to MX's (because
> 		of local firewall rules)
> 	- running on a host that can't connect to MX's (because
> 		they're unreachable or down)
> 	- running on a host that can't connect to MX's (because
> 		they no longer exist)
> 	- running on a host that can connect to the MX's but can't
> 		get the user's public key because the user is no
> 		longer valid
> 	- and so on
>=20
> There are way too many failure modes here that will render messages tha=
t
> have already been received either temporarily or permanently unreadable=
=2E

Currently, if you need to send an encrypted email to someone, and you=20
can not get their public key - same results. No change. It does not=20
break anything that is not already broken.

You only need their public key when you want to send them encrypted=20
email first, If your happy with first a signed one, then encrypted one,=20
then you do not need to look one up.

Automated email might have a hard time performing the signed email=20
exchange first, followed by the encrypted email. Humans could do it=20
manually and only be slightly annoyed at the extra step.

No matter what kind of public key lookup service is designed, if you can =

not reach it, it is not going to work.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMTM1MzExWjAvBgkqhkiG9w0BCQQxIgQgFUHMNtc8UfEEsH6BFkcfmLid8eUL54UE
ljqDXwA0TCYwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAbGlkQGO3PyJE
Cn3w9BPvrKC4uULxiomfwxCDgUWzXDdqU0UXOwUyg4nHbVaHTpO5rphEz/IiToxarCQIJfml
pRY1Mbv4qfIfSqSTrIr+OB37xcKL2oatnV7Nuan25eCnWp81lTRV+v3l5MHwVXNI9L2sommF
i1CfJjMmOqViJcxz5sI4fgkE9qZZnZjAWB7BzixOqEOrLVuJOoLZ9MAa7JuF8M7zvQRHCS3r
1uAKgxnCzEFNgmDZWFjgO56gIUMR3CoAWliEJreesw1NX1PPTAhh7LRMHYUpnbfy4JFPDjTI
luUOjkPUjTwfIvB/sMsJHW5Ec2efKAsdqU+WpMNlvwAAAAAAAA==
--------------ms060504050000080608010500--


From nobody Fri Apr 21 06:59:44 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C1C126DC2 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:59:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nT9Avc18DIx for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 06:59:39 -0700 (PDT)
Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::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 B4EDE124BE8 for <ietf@ietf.org>; Fri, 21 Apr 2017 06:59:39 -0700 (PDT)
Received: by mail-oi0-x241.google.com with SMTP id a3so15153473oii.3 for <ietf@ietf.org>; Fri, 21 Apr 2017 06:59:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=AqjDHo0evQFWh03yOB8A3Ofzn7n3XVc0k8sVC9tWKpg=; b=eRFWpZ6sv5UQDG25jW/CHJbFWVU/s9c6RRng13C8xq4F3ZLFQ5KAjFcpDbaCI2JuOZ 8twvBJy4qvLRwuXPFa0hxBE5GEnQK6Uzoy5DEwoCxhyjBbVVUhZ3XPW3ghg2H6mRwETO W8HI2fL0STiNFyLUwFM8k4F0AlryFJU7XELDidMGS72zs9r4/JIf+78sKoTZAip+Cvuk 8WYeBeHuCyZyIKnRsMArhtzfZVt4+MilcmlEC7SWCwK2sXenjX8plZUV2qSDlshJqVQ1 T76Mmt4tkFKnEzqkfOL4KQ5y4fVOOsjmWSaX98bm5yJyZPmuVNqBAOufDiEFFLB47mCg eMaA==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=AqjDHo0evQFWh03yOB8A3Ofzn7n3XVc0k8sVC9tWKpg=; b=c+W62c8xCmitk+yXuqxf11mMhviEHjKVA2GD8xQJFzlKp8iYW1AsHFFic0WAOSApxD 6VpFEzIyyuUoKfyjrt8bwATR6kil7mQBisaquWoBGe7Wpgs1s5BqzVOzabojXCt9dtNI R0qmCYo0Vh9+6M3twCyDBw7i1TWhGdH3GGf3IYWKj6DHAVvU3hVrTkgmjHKyxytEvXW1 73rLnPV1/QG3hOjR+IXuiDTBD1Uw9xv5+Dm79mC02GkH1YU5+Ou2SJroQdbGqEx40Uip +uncotv94/2b+y22OPdMP3LU1T/yqeMGrk4wHoLZ8r0qP14Ew1VXoIYUCeQecYPtJCOb uEfg==
X-Gm-Message-State: AN3rC/5B+FE3lCB7erbpcPs/HcJg1VqPl+BAO0wViQcxDbGE84dhy8St DUE5myZajIfpMTLuZN4=
X-Received: by 10.157.50.165 with SMTP id u34mr7451262otb.26.1492783178720; Fri, 21 Apr 2017 06:59:38 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id h189sm4077447oic.37.2017.04.21.06.59.36 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 06:59:37 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <m1d1XKL-0000DoC@stereo.hq.phicoh.net>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <c4492e1e-aa10-b163-6525-7420ef5e4ffd@gmail.com>
Date: Fri, 21 Apr 2017 07:59:35 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <m1d1XKL-0000DoC@stereo.hq.phicoh.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms060201000000090305040102"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vizSBqX55gN-qGbPMWzOdJ-Jz7o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 13:59:41 -0000

This is a cryptographically signed message in MIME format.

--------------ms060201000000090305040102
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/21/2017 06:06 AM, Philip Homburg wrote:
>> You send me a signed email from a mutually trusted source. I now have
>> your public key, because you can extract it from the signed S/MIME
>> email. (I am guessing you can do this with PGP.)
>=20
> Just replying to a random part of the discussion.
>=20
> Is there any kind of description and any kind of agreement of what atta=
cks
> secure mail is supposed to defend against?

I am not a security expert, I did however buy a couple of them lunch at=20
an IETF meeting years ago and I am sure that the experts will correct=20
any misstatements I have made here. S/MIME has been working for years.

> Without a clear statement of what it is supposed to do, it is not possi=
ble
> to figure out whether a proposal actually meets that goal. And without =
a
> clear goal it is also not possible to figure out if the system is going=
 to
> useful or not.

To be clear, this is not a goal or proposal. This is how S/MIME works=20
now. This is how it was designed to work.

> People have wildly different ideas of what e-mail security means.
>=20
> In the context of this discussion, one thing I'm curious about, and som=
ething
> that should be clear from the description of the attack vectors, is who=

> controls a key.

You should be in control of your private keys. You private key is as=20
secure as you make it. The average non-technical user will just send=20
email, get email, and might make sure that the signed, or encrypted=20
email checkbox is checked in their MUA.

> To put it in terms of TLS certificates, is an e-mail key 'DV' or 'EV'?

> It is easy to come up with lots of ways in which a domain holder can pr=
ovide
> a public key for a mailbox at that domain. But is that what we want?
> In some cases, like corporate mailboxes, probably yes. In other cases,
> journalists or activists with an e-mail account at a big e-mail provide=
r,
> probably not.

The only reason you need to fetch a persons private key first, is so=20
that you do not have to exchange the signed and not encrypted key first.

And I would imagine that a journalist and activists would most=20
definitely want people to send them encrypted email.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMTM1OTM1WjAvBgkqhkiG9w0BCQQxIgQgeIMSUaH4rJqVlfgq0aWWOyG6Nnbc/oK6
ZiYfD+2kcaowbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAj0w2c2nFL+is
DVBMC9oS79cd8Tt1IJSurLxpqX9VRKGw+WZQVRicEvDlYoV0QmRJOLQjToYYG5Nzu6tr7yxQ
yqXMkCab8OvozJhDfQTVIdRJU8zrgQsaenAlqwcgNXk9D9W6dhFGYk/NyTvj1Vgg0eAQW0ZC
855R7uiqbWjl9dTJk44RYgi2JIF4LY5PVborUcfhq/s6wNxQNJxRXIYMiCkWI4lEZOCe9bpJ
WXl2R57jwVPu+9S8233pZW+75+1TpOImd6PpSe1kMpga+heeE40yIkdbEad9RXr0KDYrjpYp
mKDz1zkCeiv1WRQezqs8pAMVT1Lq5TabwTwka/Gt9gAAAAAAAA==
--------------ms060201000000090305040102--


From nobody Fri Apr 21 07:24:14 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BC412944C for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 gCyNYUTIWeCm for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:24:11 -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 3A4421241FC for <ietf@ietf.org>; Fri, 21 Apr 2017 07:24:11 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id x184so97868742oia.1 for <ietf@ietf.org>; Fri, 21 Apr 2017 07:24:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=4a/GZ3fnU6lkatMMXxL+Od/ZVuPH2S4ekRzqXUUzc+g=; b=raLcP6PTf2wRbxSzRgfpPlVLJ5BoJ8m8v5lDNmK/MXRKWpo4rusRtnW55XwJa4Sa+B YbnP8Z0QBJu95wf75kPo50q+wFsn9zlhxbgJl98AGC2f7Xsm2mbVfUQlN0HYfhdIBVUt cxGQ1Uql0AafD6Mmkz0PVta5NpCRQU9UNN9Dli60ulzuYc5iRcbNIn3+ISCOJP0E60ur HccmvOWQmroloJmZyYhQOv3wlXmLoj5rtArcWyUw9Z+u0CNYY7v5Mob4bRo3NKiCZfJY EtPzOsyFJy+Mal0UUGMAySEo+VwF8VLF+qBBGGjAsQPp847qE2tBW8gwEpTa8SGEnFUC tRtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=4a/GZ3fnU6lkatMMXxL+Od/ZVuPH2S4ekRzqXUUzc+g=; b=Lo9YOrK4MB4gIVZ4sgkyKlvotUxnrmrsROxBiKrs69Vlu68ItUN/pMAmI2jax1CBjG 2kAjVG/bmXcLRNay6ARkZYmqW036TOL8qYvOug2zA5SxDKFLC7SA8iBopFLElsWSdDhT b3ueW0r5KiIGXVPMpNNnEIZQ51SH/hTr9DbRM8sjDgg+LvtSY6F/D3qSSaXfI4Wxu64P wm6Gj7b8amRqxkyeCbz8mBM3RqM40AxmkPv/d+A38c61JXg96BWmLQdD7u+A0aYz203B yl5WZXZDrdkAbS9cHF8teJrQeFiinCiNwMqlgrY6Vk37h/15SwvCXlIjMigvkaXOn9gb F02A==
X-Gm-Message-State: AN3rC/5KPN8t7Zwjv8Hrgz83aDtpuFvOSwuBvYyC65pTx14LEIJCRZCv +1JgJmtxOLcu9v2q91P8jOYerf71cg==
X-Received: by 10.157.46.9 with SMTP id q9mr4534586otb.102.1492784650305; Fri, 21 Apr 2017 07:24:10 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 07:24:09 -0700 (PDT)
In-Reply-To: <9440cd43-d8d9-8950-cdc7-bbf9fd2d7a91@gmail.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org> <9440cd43-d8d9-8950-cdc7-bbf9fd2d7a91@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 10:24:09 -0400
X-Google-Sender-Auth: ec7DrZhPArgyyMlnr5f6XIBT2eA
Message-ID: <CAMm+LwgboKwXs+uEUCDA=KMbWHgFU6iVOvQZPMOvS0S4Omu8ew@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a114639dccec603054dae0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JRe0OpHXREx9VFwid9CnjVmz45Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 14:24:13 -0000

--001a114639dccec603054dae0200
Content-Type: text/plain; charset=UTF-8

The problem I keep seeing is that whenever we start talking about problem
X, people immediately start throwing in problem Y, Z... Often prefixed with
the words, 'but you obviously haven't thought about...'

I have identified at least a dozen problems with mail security, all of
which need to be fixed in order to deploy something better. And I think I
have a pretty good solution to all of them. I am not saying I have the best
solution or a perfect solution but I have *A* solution.


Tweaking the SMTP mail infrastructure doesn't help because the sending and
receiving device do not interact with either server directly under the
current model. SMTP email has grown to meet a lot of important requirements
in ways that make repurposing SMTP mail servers a non starter.

Talking about 'end to end' is also unhelpful because the only ends that
matter are the sender and receiver brains and you are not going to have
true end-to-end in out lifetime. The last and the first meter is always
going to be a weak link. As I showed in another post, there are good
reasons to only accept encrypted messages end-to-end after the sender has
been deemed trustworthy.

Also, Dave Crocker will soon chime in to point out the deployment problem.
And he is completely right. You are not going to replace SMTP with a new
email system. The only way that a system as pervasive as SMTP has ever been
replaced is by a new system that offers a superset of its functions.

I watched Tim B-L very carefully at CERN and I think I learned how the
deployment strategy of the Web worked. The key was to find one feature that
the Web offered to a distinct community that nothing else provided. In this
case the feature was to allow people to read the CERN phone book without
using CERN-VM, a mainframe whose operating system was the most unpleasant
in history.


So the first step towards sanity is to talk about data level security, not
just message. Right now, there is no standards based approach to encrypting
business documents, Word, Excel, program code, etc. in ways that support
business processes. Yes, you can buy and configure a Microsoft CRM system
but it only works for Microsoft products and not even the CIA and NSA
bother with it, hence Snowden, Manning and the two as yet unknown GRU moles
in NSA and CIA who supplied the Shadowbroker and Vault7 data.

The principle obstacle to deployment of such a system has been a set of
patents on the core technology. Patents which expire this year.

A secondary obstacle has been the insistence on perfect security so that if
Alice sends a document to Bob, Bob can only use it for purposes Bob
approves of. That might sound good till you realize it makes the document
next to useless to Bob. He can't edit, can't steal slides from a Powerpoint
Deck, he can't even show it without permission. Oh and he can only use
particular hardware configurations.

The biggest pratfall for traditional CRM schemes is that most of the most
important documents in any corporation have to be sent outside the company.
We are required to open our accounts to our auditors, we are required to
share trade secrets with our external counsel to apply for patents and of
course we have to share price information with customers to make a sale.


So what I suggest we do is that we start a Working Group to develop a
Confidential Document Control protocol, that is CRM minus the secure
hardware requirement.

Proxy Re-Encryption provides the technical capabilities we need to meet the
requirements of CDC. We would of course need to also solve the key
distribution problem. I have running code which addresses both.


Note however that once you solve the key distribution problem for CDC, you
can apply that solution to SSH, Web password management, second factor
authentication/confirmation and yes, messaging.

--001a114639dccec603054dae0200
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
 problem I keep seeing is that whenever we start talking about problem X, p=
eople immediately start throwing in problem Y, Z... Often prefixed with the=
 words, &#39;but you obviously haven&#39;t thought about...&#39;</div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small">I have identified at least a dozen =
problems with mail security, all of which need to be fixed in order to depl=
oy something better. And I think I have a pretty good solution to all of th=
em. I am not saying I have the best solution or a perfect solution but I ha=
ve *A* solution.</div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><br></di=
v><div class=3D"gmail_default" style=3D"font-size:small">Tweaking the SMTP =
mail infrastructure doesn&#39;t help because the sending and receiving devi=
ce do not interact with either server directly under the current model. SMT=
P email has grown to meet a lot of important requirements in ways that make=
 repurposing SMTP mail servers a non starter.</div><div class=3D"gmail_defa=
ult" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">Talking about &#39;end to end&#39; is also unhelpful b=
ecause the only ends that matter are the sender and receiver brains and you=
 are not going to have true end-to-end in out lifetime. The last and the fi=
rst meter is always going to be a weak link. As I showed in another post, t=
here are good reasons to only accept encrypted messages end-to-end after th=
e sender has been deemed trustworthy.</div><div class=3D"gmail_default" sty=
le=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-size:small">Also, Dave Crocker will soon chime in to point out the deploym=
ent problem. And he is completely right. You are not going to replace SMTP =
with a new email system. The only way that a system as pervasive as SMTP ha=
s ever been replaced is by a new system that offers a superset of its funct=
ions.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-size:small">I watched Tim B-L v=
ery carefully at CERN and I think I learned how the deployment strategy of =
the Web worked. The key was to find one feature that the Web offered to a d=
istinct community that nothing else provided. In this case the feature was =
to allow people to read the CERN phone book without using CERN-VM, a mainfr=
ame whose operating system was the most unpleasant in history.</div><div cl=
ass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">So the first step towards sanity is to talk abo=
ut data level security, not just message. Right now, there is no standards =
based approach to encrypting business documents, Word, Excel, program code,=
 etc. in ways that support business processes. Yes, you can buy and configu=
re a Microsoft CRM system but it only works for Microsoft products and not =
even the CIA and NSA bother with it, hence Snowden, Manning and the two as =
yet unknown GRU moles in NSA and CIA who supplied the Shadowbroker and Vaul=
t7 data.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-size:small">The principle ob=
stacle to deployment of such a system has been a set of patents on the core=
 technology. Patents which expire this year.=C2=A0</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">A secondary obstacle has been the insistence on p=
erfect security so that if Alice sends a document to Bob, Bob can only use =
it for purposes Bob approves of. That might sound good till you realize it =
makes the document next to useless to Bob. He can&#39;t edit, can&#39;t ste=
al slides from a Powerpoint Deck, he can&#39;t even show it without permiss=
ion. Oh and he can only use particular hardware configurations.=C2=A0</div>=
<div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">The biggest pratfall for tradi=
tional CRM schemes is that most of the most important documents in any corp=
oration have to be sent outside the company. We are required to open our ac=
counts to our auditors, we are required to share trade secrets with our ext=
ernal counsel to apply for patents and of course we have to share price inf=
ormation with customers to make a sale.</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sm=
all">So what I suggest we do is that we start a Working Group to develop a =
Confidential Document Control protocol, that is CRM minus the secure hardwa=
re requirement.=C2=A0</div><div class=3D"gmail_default" style=3D"font-size:=
small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">Pro=
xy Re-Encryption provides the technical capabilities we need to meet the re=
quirements of CDC. We would of course need to also solve the key distributi=
on problem. I have running code which addresses both.=C2=A0</div><div class=
=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">Note however that once you solve the key distribut=
ion problem for CDC, you can apply that solution to SSH, Web password manag=
ement, second factor authentication/confirmation and yes, messaging.</div><=
div class=3D"gmail_default" style=3D"font-size:small"><br></div></div>

--001a114639dccec603054dae0200--


From nobody Fri Apr 21 07:31:39 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2451294C8 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, 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 Zs3UwpEfZx4r for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:31:36 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2001294A8 for <ietf@ietf.org>; Fri, 21 Apr 2017 07:31:35 -0700 (PDT)
Received: (qmail 10835 invoked from network); 21 Apr 2017 14:31:34 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2017 14:31:34 -0000
Date: 21 Apr 2017 14:31:12 -0000
Message-ID: <20170421143112.28055.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <CABkgnnVmJf66ZJLToFm9_o34P3FswezVRFguuFrgMJeQv_TMgg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/16O0YZfmlgQs9HYpTEbeAo_y7Iw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 14:31:37 -0000

In article <CABkgnnVmJf66ZJLToFm9_o34P3FswezVRFguuFrgMJeQv_TMgg@mail.gmail.com> you write:
>On 21 April 2017 at 12:11, John Levine <johnl@taugh.com> wrote:
>>
>> If a recipient is cooperative, and sends you back a message signed
>> with the same key to which you encrypted the message, that tells you
>> he got it, but that's not a very interesting case.
>
>It's also abuse of the cryptographic primitives, I hope that this
>isn't really how it works and you are eliding certain key details.

It doesn't use the same session key, it uses the same public key.  It's
not obvious to me why that would be wrong.

R's,
John



From nobody Fri Apr 21 07:46:27 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B38128C84 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:46:25 -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 RdW6Nv8sIQzw for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 07:46:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3B01204DA for <ietf@ietf.org>; Fri, 21 Apr 2017 07:46:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1d1ZpH-0000HJC; Fri, 21 Apr 2017 16:46:23 +0200
Message-Id: <m1d1ZpH-0000HJC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Cc: Doug Royer <douglasroyer@gmail.com>
Subject: Re: Why are mail servers not also key servers? 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "Fri, 21 Apr 2017 07:59:35 -0600 ." <c4492e1e-aa10-b163-6525-7420ef5e4ffd@gmail.com> 
Date: Fri, 21 Apr 2017 16:46:22 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FlcOpsMDemA0ykhoBpPMHX_XWQQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 14:46:26 -0000

>> Is there any kind of description and any kind of agreement of what attacks
>> secure mail is supposed to defend against?
>
>I am not a security expert, I did however buy a couple of them lunch at 
>an IETF meeting years ago and I am sure that the experts will correct 
>any misstatements I have made here. S/MIME has been working for years.

At a technical level, yes. S/MIME does stuff. Whether it does the right thing?
Who knows.

>> People have wildly different ideas of what e-mail security means.
>> 
>> In the context of this discussion, one thing I'm curious about, and somethin
>g
>> that should be clear from the description of the attack vectors, is who
>> controls a key.
>
>You should be in control of your private keys. You private key is as 
>secure as you make it. The average non-technical user will just send 
>email, get email, and might make sure that the signed, or encrypted 
>email checkbox is checked in their MUA.

By and large, private keys are the boring part. Yes, private keys will leak
every now and then. But overall that's not a big issue.

The big issue is how do you make sure that a public key actually belongs to
the party you want to communicate with and is not a key inserted by an
attacker.

It is easy to say 'trusted third party' without actually defining what such
a third party will look like. That gives the mess that is the current CA
system.

It is also easy to say, just use DNSSEC. Disregarding the trust issues
with that model.

>> It is easy to come up with lots of ways in which a domain holder can provide
>> a public key for a mailbox at that domain. But is that what we want?
>> In some cases, like corporate mailboxes, probably yes. In other cases,
>> journalists or activists with an e-mail account at a big e-mail provider,
>> probably not.
>
>The only reason you need to fetch a persons private key first, is so 
>that you do not have to exchange the signed and not encrypted key first.

You never 'fetch' a private key. 

>And I would imagine that a journalist and activists would most 
>definitely want people to send them encrypted email.

Only if governments or other large parties cannot mount a man in the middle
attack. Which they can, if they can control the distribution of public keys.


From nobody Fri Apr 21 08:29:10 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48055129532 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNu1R9dmOVe1 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:29:06 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 9BAB1127B60 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:29:06 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id x184so100422884oia.1 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vCuQIchAjl8+Ei2V3hqEW7Dd/tblaw7vBA1mWBd6SAs=; b=kCd01HBEXmAizAzXISKaaUnRV0+2WndUB/SFsB5QzK2uQkNrRKW9+zmkCkR+9oKZoy Wn0wnbK/dtzwzB+CHjRoBNu9InsBdzUjRP5WCMV90Nm8LHyn4Wbn02J8HAO0wd02hIPX 25CznFWlHHk/2VFpXoQIlK2wZ+xtUEnOf1m7K8mkVFJcdznAI/Vf+OTaQ51vT9zA47LS 3HUmA6nSd9fQe5VS6J39DOqlYLTf8gQvm3BReelpySewydIDZhevyeXMEx9aGX8p2wGF uXvf6Wg+37Pe8tLiBFzBRz7c7dZmQZtEYdSopJ9f1ZQq7VB5Bi+0FbDc6ZktY9HYKv1B bkdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vCuQIchAjl8+Ei2V3hqEW7Dd/tblaw7vBA1mWBd6SAs=; b=mdMaL4NA0q6Er0aAClEGCKmiFhAGp0q4ClwopQqd+eXFkjkY8cqK2yfINQVhKoS4jC zVAtbVskMAo9BU/BLk4Zb7EGMjDgldqtDgaXaeC3kCm3chuWPL0495CvOM5OLYNcNTcK roVuzKrdEGkXR9hhozcl8tjkokwqphGeW6ocdjo0CScEuXa5HgViLNQ5mYaFf86SXAXQ /ajuVE2eTbYAIN2YXSfgqEnndxog440yzTgT/9TX3V9l/SuAimeYqN2ktMXy6FZDFxcF 9/jSJ5EILE/8Z/oLyCUDdz7smiyHa0Cd4IaP/n+821fMrdOf5jkUx+u49o1J4o3AytF0 LY4g==
X-Gm-Message-State: AN3rC/50GUjHRfKaU8L64ibJ0vktJTxbHkIi3FJo2fYGLHZhMA/6lVEd d545pa7VRDgUSWUTX4kOGIJSPF6/Zw==
X-Received: by 10.157.46.9 with SMTP id q9mr4832425otb.102.1492788545895; Fri, 21 Apr 2017 08:29:05 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 08:29:05 -0700 (PDT)
In-Reply-To: <m1d1ZpH-0000HJC@stereo.hq.phicoh.net>
References: <c4492e1e-aa10-b163-6525-7420ef5e4ffd@gmail.com> <m1d1ZpH-0000HJC@stereo.hq.phicoh.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 11:29:05 -0400
X-Google-Sender-Auth: R73e_mYljnt2NyKA5-j9eOoH9k4
Message-ID: <CAMm+LwjMt07p_Oz3KxvE5EY=ydsFZ1HCOj9ZK15vo=x4vPfYfg@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Doug Royer <douglasroyer@gmail.com>
Content-Type: multipart/alternative; boundary=001a114639dc00c09c054daeeba9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ktl2xEej2pQrQTYqYTbeVs5jc3k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 15:29:09 -0000

--001a114639dc00c09c054daeeba9
Content-Type: text/plain; charset=UTF-8

On the trust issue, one of the problems I have identified with existing
message level security schemes is the lack of an infrastructure to
adequately manage user private keys. This is in part a result of the
constraints of 1990s technology which took seconds to perform RSA
operations. Today, those constraints are no longer relevant.

If we are going to have a useful discussion about Trust, we have to talk
metrics. Otherwise we end up with handwavy arguments like'nobody can trust
a CA'. Oh really, you think that email about Johnny making the school choir
that you currently send en-clair can't be trusted to CA issued trust?

When I worked on the design of what is now the WebPKI in the early 1990s at
CERN, I used a Work Factor analysis that is denominated in dollars. In the
wake of BlockChain, I realized that the model had to be extended to take
account of time because the wonderful thing about BlockChain and any
Lamport hash chain is that the Work Factor of an attack goes to essentially
infinity as soon as a data item is enrolled.

https://datatracker.ietf.org/doc/draft-hallambaker-prismproof-trust/


The big problem with private keys is that people have multiple devices and
they HAVE to be able to read email on more than one. Which means that
either you have to re-engineer the mail crypto to use proxy re-encryption
or you have to be able to move private keys about. I am currently
completing the code for the second approach.

My scheme in a nutshell is to establish a personal PKI for each user and
give them the tools to manage it transparently. OpenPGP offers something
similar but it isn't designed to allow a user to keep a personal
fingerprint for their whole life. Mine is and making that possible requires
the same offline/intermediate/online approach we use to manage WebPKI keys.
Each key in my scheme has a very narrow purpose. That means more public key
operations but greatly simplifies the code.


So let us say that the fingerprint for Alice's personal Mesh
is MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ.

We can use this to create a strong DNS address so:

example.com.mm--MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ

which allows us to construct a strong email address:

alice@example.com.mm--MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ

mm-- is a DNS label prefix following the practice established for 118N
domains. It is the top level because it is the root of this particular
naming scheme and we do not want anyone to be able to resolve this name
unless they understand the mm-- prefix.

Try to send a mail with that address using a regular email client and it
will fail. Which is exactly what I want. This allows me to support the use
case 'only send if it can be encrypted'.


In this case, the fingerprint is of a personal signing key which signs
Alice's Mesh profile which in turn signs Alice's Mail profile which
describes how to send email to Alice. So if a mail is sent to that address,
following the specified profile, it has been sent securely (for Alice's
definition of secure). There is no opportunity for a third party to
compromise the communication. You are not relying on any CA or TTP for
trust.

What you probably will end up doing if you are an Enterprise customer is
paying some party some money to run the infrastructure that
maps MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ to the necessary resources and also
helps you address the first contact and promiscuous encryption use cases.

There is a business model for existing CAs here but the services are rather
more than signing a certificate.


The concept of strong addresses can be applied to any IETF protocol and is
wonderfully back compatible because every strong DNS address is a valid DNS
address but one that has no chance of accidentally being confused with an
ICANN issued address. It would take an act of intentional malice for
confusion to arise.

So how to apply these to the use case raised by John Levine?


We could configure a mail client to add a header that includes strong email
address as a header:

From: alice@example.com
Strong-Address: alice@example.com.mm--MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ


This gives us Trust After First Use (TAFU) which is a great way to build a
Web of Trust. It does work for SSH. It is fine for interpersonal messages.

If you combine Web of Trust and Trusted Third Party models, you can achieve
a higher work factor than is possible with either alone.

--001a114639dc00c09c054daeeba9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
the trust issue, one of the problems I have identified with existing messag=
e level security schemes is the lack of an infrastructure to adequately man=
age user private keys. This is in part a result of the constraints of 1990s=
 technology which took seconds to perform RSA operations. Today, those cons=
traints are no longer relevant.</div><div class=3D"gmail_default" style=3D"=
font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:=
small">If we are going to have a useful discussion about Trust, we have to =
talk metrics. Otherwise we end up with handwavy arguments like&#39;nobody c=
an trust a CA&#39;. Oh really, you think that email about Johnny making the=
 school choir that you currently send en-clair can&#39;t be trusted to CA i=
ssued trust?</div><div class=3D"gmail_default" style=3D"font-size:small"><b=
r></div><div class=3D"gmail_default" style=3D"font-size:small">When I worke=
d on the design of what is now the WebPKI in the early 1990s at CERN, I use=
d a Work Factor analysis that is denominated in dollars. In the wake of Blo=
ckChain, I realized that the model had to be extended to take account of ti=
me because the wonderful thing about BlockChain and any Lamport hash chain =
is that the Work Factor of an attack goes to essentially infinity as soon a=
s a data item is enrolled.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default"><a href=3D"https://datat=
racker.ietf.org/doc/draft-hallambaker-prismproof-trust/">https://datatracke=
r.ietf.org/doc/draft-hallambaker-prismproof-trust/</a><br></div><div class=
=3D"gmail_default"><br></div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">T=
he big problem with private keys is that people have multiple devices and t=
hey HAVE to be able to read email on more than one. Which means that either=
 you have to re-engineer the mail crypto to use proxy re-encryption or you =
have to be able to move private keys about. I am currently completing the c=
ode for the second approach.</div><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">My scheme in a nutshell is to establish a personal PKI for each user an=
d give them the tools to manage it transparently. OpenPGP offers something =
similar but it isn&#39;t designed to allow a user to keep a personal finger=
print for their whole life. Mine is and making that possible requires the s=
ame offline/intermediate/online approach we use to manage WebPKI keys. Each=
 key in my scheme has a very narrow purpose. That means more public key ope=
rations but greatly simplifies the code.</div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:s=
mall">So let us say that the fingerprint for Alice&#39;s personal Mesh is=
=C2=A0MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ.</div><div class=3D"gmail_default" styl=
e=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-=
size:small">We can use this to create a strong DNS address so:</div><div cl=
ass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gma=
il_default" style=3D"font-size:small">example.com.mm--MB2GK-6DUF5-YGYYL-JNY=
5E-RWSHZ<br></div><div class=3D"gmail_default" style=3D"font-size:small"><b=
r></div><div class=3D"gmail_default" style=3D"font-size:small">which allows=
 us to construct a strong email address:</div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-size:small">alice@example.com.mm--MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ</div><d=
iv class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">mm-- is a DNS label prefix fol=
lowing the practice established for 118N domains. It is the top level becau=
se it is the root of this particular naming scheme and we do not want anyon=
e to be able to resolve this name unless they understand the mm-- prefix.</=
div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div c=
lass=3D"gmail_default" style=3D"font-size:small">Try to send a mail with th=
at address using a regular email client and it will fail. Which is exactly =
what I want. This allows me to support the use case &#39;only send if it ca=
n be encrypted&#39;.</div><div class=3D"gmail_default" style=3D"font-size:s=
mall"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><br>=
</div><div class=3D"gmail_default" style=3D"font-size:small">In this case, =
the fingerprint is of a personal signing key which signs Alice&#39;s Mesh p=
rofile which in turn signs Alice&#39;s Mail profile which describes how to =
send email to Alice. So if a mail is sent to that address, following the sp=
ecified profile, it has been sent securely (for Alice&#39;s definition of s=
ecure). There is no opportunity for a third party to compromise the communi=
cation. You are not relying on any CA or TTP for trust.</div><div class=3D"=
gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">What you probably will end up doing if you a=
re an Enterprise customer is paying some party some money to run the infras=
tructure that maps=C2=A0MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ to the necessary reso=
urces and also helps you address the first contact and promiscuous encrypti=
on use cases.</div><div class=3D"gmail_default" style=3D"font-size:small"><=
br></div><div class=3D"gmail_default" style=3D"font-size:small">There is a =
business model for existing CAs here but the services are rather more than =
signing a certificate.</div><div class=3D"gmail_default" style=3D"font-size=
:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><b=
r></div><div class=3D"gmail_default" style=3D"font-size:small">The concept =
of strong addresses can be applied to any IETF protocol and is wonderfully =
back compatible because every strong DNS address is a valid DNS address but=
 one that has no chance of accidentally being confused with an ICANN issued=
 address. It would take an act of intentional malice for confusion to arise=
.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><di=
v class=3D"gmail_default" style=3D"font-size:small">So how to apply these t=
o the use case raised by John Levine?</div><div class=3D"gmail_default" sty=
le=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l">We could configure a mail client to add a header that includes strong em=
ail address as a header:</div><div class=3D"gmail_default" style=3D"font-si=
ze:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">=
From: <a href=3D"mailto:alice@example.com">alice@example.com</a></div><div =
class=3D"gmail_default" style=3D"font-size:small">Strong-Address: alice@exa=
mple.com.mm--MB2GK-6DUF5-YGYYL-JNY5E-RWSHZ</div><div class=3D"gmail_default=
" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size=
:small">This gives us Trust After First Use (TAFU) which is a great way to =
build a Web of Trust. It does work for SSH. It is fine for interpersonal me=
ssages.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-size:small">If you combine We=
b of Trust and Trusted Third Party models, you can achieve a higher work fa=
ctor than is possible with either alone.</div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div></div>

--001a114639dc00c09c054daeeba9--


From nobody Fri Apr 21 08:39:32 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387D012954C for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:39:29 -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 eBO5KleKYPms for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:39:27 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::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 53426129535 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:39:27 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id j201so100186944oih.2 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=+HXAQ5qRlmRHHPwBxEWmWiiOf75u6CHv+Vb3wW2UKuE=; b=s5Y9E2PNi3FT+RGy3gR7VbjOkxHiYsyqBK8irTEUoZII94uotkm2F1BrxbxuX3d36U 7bJglYfj4WQKOGbCkj2+MTSwfQP+VX47pMH9X0J0CQp0xjz1DyzFeKm+DFak6dQZI7bL /bgjgoPRrLZYzSqPwxxnjBTpimYZ3aF15+lgsT5mUqRCSSFTRqXMOkzYeujH+nTWQOOq kEr1Sr4agMA/JQMGpHBiwDNQvALuWh6SqdsN0yrGM9chZ7iHKAfKJnfsA3AtsefsqdCG 6/ddvSBOK19c5WSuIkeyo00Ofrbwg1wG9RCjI/GOeEhsqhjRRvgZs+IChRfVWMlUpH8v /tFA==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=+HXAQ5qRlmRHHPwBxEWmWiiOf75u6CHv+Vb3wW2UKuE=; b=tBYhf1joGIc2iV0SOt37CcF9Ejbve/5tCPiQ94Cy38D3Uo+0zLql6MO6z7bk3LEJ68 Oc4QdpaKxM2Xar+IAbB00eJjE4LjGKYktcl9ANOooanzjKAA/utIZ9ha7LJNL0mcE4bm Uk1OYsB6AKVx2DU7cL87n0yErHriEVfpLZfDL5TY70A1SDkaAtNy91z3KVrKBaHDmsqY iXhXSjQKSK6OiEZylZHeI+WklZFGYeBNFAjUUJhyuypc00FX5iSLSgfMy6Sb3PXZeIXd GbYmIEgB3tnLNjJYbZBa7UruZH9rHgTJSwrqFvHEw+CjUpRk6SI68Hgs0vB1fysuM3p3 ldYw==
X-Gm-Message-State: AN3rC/5QVdr/vuMXwrxZTS3Mk5KOlKpQA5g4lHd4aMzlKVuHyvZWsfZu ml+aqrBN2Jlbd0bKFHY=
X-Received: by 10.202.177.131 with SMTP id a125mr7280252oif.2.1492789166239; Fri, 21 Apr 2017 08:39:26 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id 63sm4153874otw.57.2017.04.21.08.39.24 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 08:39:24 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org> <9440cd43-d8d9-8950-cdc7-bbf9fd2d7a91@gmail.com> <CAMm+LwgboKwXs+uEUCDA=KMbWHgFU6iVOvQZPMOvS0S4Omu8ew@mail.gmail.com>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <3f0ebabd-1eb9-d81b-7cda-47d7ace3f57b@gmail.com>
Date: Fri, 21 Apr 2017 09:39:23 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwgboKwXs+uEUCDA=KMbWHgFU6iVOvQZPMOvS0S4Omu8ew@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030301070006030200080107"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ER6nvyxIO_zF5tElr8FU00ZDzAs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 15:39:29 -0000

This is a cryptographically signed message in MIME format.

--------------ms030301070006030200080107
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/21/2017 08:24 AM, Phillip Hallam-Baker wrote:
> ...
>=20
> Tweaking the SMTP mail infrastructure doesn't help because the sending =

> and receiving device do not interact with either server directly under =

> the current model. SMTP email has grown to meet a lot of important=20
> requirements in ways that make repurposing SMTP mail servers a non star=
ter.
>=20

They do not, does not mean they can not. So, maybe SMTP server is not=20
the correct place. But MX host might be, with a public key server on a=20
different port. Because the MX host is currently the authority for an=20
email addresses validity checking (well it bounces it if its not valid - =

but it knows if its valid).

Is it repurposing? Is this really different?

   RCPT TO user@domain
   250 OK
   550 No such user here

   PEMCERT user@domain
   250 OK ...PEM-encoded-cert..
   550 No such user here

   PGPCERT user@domain
   250 OK ...PGP-encoded-cert..
   550 No such user here

Thoughts below on this. And I am thinking of how the code would be=20
written ...

I was leaning towards the SMTP/MX server because its currently the only=20
place of authority where you can find out if user@host is valid. If you=20
send a RCPT TO and it says, NO, then your done.


I have no problem with another solution. I just think you would have to=20
replicate the email address validity check problem as part of that other =

implementation. 'User' is not always the same as email address. So any=20
new service would have to know about email proxy rewrite rules=20
(Doug.Royer@gateway -> dougr@his-site-server),  mailing/distribution=20
lists, ... and the mess goes on.

I am not saying a public key server would need to understand those=20
rules. I am saying that Doug.Royer@gateway would be the public key you=20
might need. I am saying a public key server would need to parallel the=20
knowledge of what the SMTP server already knows is a valid email address =

for its site. Currently Doug.Royer@gateway is in some file/database as=20
valid in a way that is currently unique the SMTP server implementation.

And, who is the local authority for the public cert of=20
Doug.Royer@gateway? The SMTP server already knows it goes to=20
dougr@his-site-server.

So, maybe the SMTP server is not the place. I think it would make for a=20
simpler implementation. Or maybe an entirely news service, that the SMTP =

server would use, to make sure they are in sync.

It seems to me that a completely new approach is not going to be adopted =

as quickly as extending SMTP.

Or I could see the SMTP server implementation also opening up a new=20
public key service port that is only used for fetching public keys. And=20
that port could use a non-SMTP protocol. However the MX host is the=20
authority.

Lets not make two authorities.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMTUzOTIzWjAvBgkqhkiG9w0BCQQxIgQgD4g5bLwIwRz6Jge4XPNhGX6dNeMzIS6w
zutU0RoU/FYwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAnqYUapNCvR9G
p73Hs2afW8I5IlYdxBjwX5kWdS1ylHMV4F/CdBec+mpXIHJUDuJgOukR1+4CsoqF69YrG3Vh
qmExh6sobB/UCLfn+v/auzhIyvcMnGbOhfkyDhgeqzl44wzY5RGvZ8bU0xNkhMtDsJwutNdq
NUaXWWAXNYqd5Xc6/v0J3iGmT9N6IakE8i8KEGbQ+y7u6CJAY0h9PVw4Ru5fXZaazQ6MuZqH
yMoQQcNmeEBTINk10LcJNkGSTV7Cf7fV7GxexTGuZo5YSB2/kn1Gcn29C3GdemAT+FwGk3Fd
0ISpyF4W2XsO1u5GXN4dB51v7YRlVyEBLebSVkHrRAAAAAAAAA==
--------------ms030301070006030200080107--


From nobody Fri Apr 21 08:48:24 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719A612953F for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:48:22 -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, RP_MATCHES_RCVD=-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 L4URMOA1ARxi for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:48:20 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5B3D129528 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:48:20 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1d1anD-000LUj-NC; Fri, 21 Apr 2017 11:48:19 -0400
Date: Fri, 21 Apr 2017 11:48:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Rich Kulawiec <rsk@gsp.org>, ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <E690BED1BD448540F502C8DD@PSB>
In-Reply-To: <20170421133535.GA21229@gsp.org>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YelkpXiUHR2XrpAWhgq50cx5yWo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 15:48:22 -0000

--On Friday, April 21, 2017 09:35 -0400 Rich Kulawiec
<rsk@gsp.org> wrote:

> On Thu, Apr 20, 2017 at 11:48:04AM -0600, Doug Royer wrote:
>> I would like to see an extension so that the MUA could
>> contact the destination server (perhaps their MX record host)
>> and get a users PUBLIC key. Perhaps (just an idea - no
>> screaming please) a new TXT record type that points to the
>> domains PubKey server.
> 
> How's this going to work when the MUA is:
> 
> 	- running on a host that's not connected to the 'net
> 	- running on a host that can't connect to MX's (because
> 		of local firewall rules)
> 	- running on a host that can't connect to MX's (because
> 		they're unreachable or down)
> 	- running on a host that can't connect to MX's (because
> 		they no longer exist)
> 	- running on a host that can connect to the MX's but can't
> 		get the user's public key because the user is no
> 		longer valid
> 	- and so on
> 
> There are way too many failure modes here that will render
> messages that have already been received either temporarily or
> permanently unreadable.

An idea was kicked around some years ago (can't remember if
there was ever an I-D) to create an SMTP extensions that would
work more or less like VRFY to return either the public key of
the server, that of a user associated with an address, or both.
IIR it never got any traction, partially because of the issues
Rich identified about and partially because of the issues others
have mentioned about being sure one reaches the right server
and/or can trust the keys received.

In addition, as others have pointed out, if you can't trust your
email (server) provider, then expecting others to trust keys on
the basis that they are obtained from that server may not make a
lot of sense.

   john



From nobody Fri Apr 21 08:52:21 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710B2129528 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcKHPv8gPOIJ for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 08:52:18 -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 CB09B129789 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:52:17 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id y11so68514725oie.0 for <ietf@ietf.org>; Fri, 21 Apr 2017 08:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=LoskcclDhSvOrcZEMUHW2BS6/DbKRqQKv9+6W+52rGI=; b=fiGsChUNSqVY5Bye9WQb9LLJNQRR55321TZ/oeUtThyOmWxlWYGMXqgsZ/ST+cEkk/ c2rtR1XWx5qqr9tzNuNov3iN18kDpW2X0UZGCQ7VMOi8wOPu/YaPqNNfgjKv9a3+0EQV HNwN7+qiFtzyNLkMnR0PKuS5DWLuxnZZDITvEfaw9PskazaCIQWkqqNZsX6+Y/bkaaYJ QUuip2CT32OuGGSMkocUJApVKkoR7z1TidN95YZwBsu8+Lf+8uxNRjgQNLDgBV2gv34E /ermddxpRfXFBjFNdBCaV5c+38jV5k/kAqQqxYw3ukGPqL35oYdd97z+h1K9du4pV3b0 GpQQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=LoskcclDhSvOrcZEMUHW2BS6/DbKRqQKv9+6W+52rGI=; b=dgtRPO69OeQzD1DxddVDZ9WawBD/2D/9Gi8CVrU3144fHWJzPF0b3IdMkQN/VivPdW qqiNOiNXSt60h3ciBndqLTpKpHJCQiRZ0gHKrcTAqGZi5co8s/cGUYIRe5VWSnpHOuMJ erTl7fL87vrfmv2S/3IW1l+6brdNe911uDA5pcBX3tH4ywsuifuuyYdYi4Gu5wUdl0lV fWh8+FocrfHi/JXx8MH+szZoNYvxRvJB67hMFcLYA3yUiuTjqaCMHBv8+Q2e3goSkSLU zhOF0Tb0+ooJ7ijWF4XZlJXbRKXfScpYcZuDcpKnRJx+NtJLnfvKDO6c/PXXsQYXSy4d LIBA==
X-Gm-Message-State: AN3rC/5yjg4drO+TecxD7cI3TDo2VfEn1Fp/0mox7MkuDlHC7fq60LKc kN7BRc6phIFBqbX37J0=
X-Received: by 10.157.9.41 with SMTP id 38mr8030741otp.256.1492789936811; Fri, 21 Apr 2017 08:52:16 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id p27sm4224487otd.26.2017.04.21.08.52.14 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 08:52:15 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org> <E690BED1BD448540F502C8DD@PSB>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <4e394b3d-0f12-ef16-65b6-a2b712e98da5@gmail.com>
Date: Fri, 21 Apr 2017 09:52:13 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <E690BED1BD448540F502C8DD@PSB>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040505090501050006040704"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ww1C_iUeLJtXtzai-zR2GO44GaE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 15:52:19 -0000

This is a cryptographically signed message in MIME format.

--------------ms040505090501050006040704
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/21/2017 09:48 AM, John C Klensin wrote:

>=20
> In addition, as others have pointed out, if you can't trust your
> email (server) provider, then expecting others to trust keys on
> the basis that they are obtained from that server may not make a
> lot of sense.

You do not have to trust your or their email server. If you trust the=20
cert issuer. Then use the result.

If you do not trust the cert issuer, then do not use the results.

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMTU1MjEzWjAvBgkqhkiG9w0BCQQxIgQg7cDXR6LKa+PVlZLQrmRy6F+Mdpk92BRu
2BksEyUQEQUwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEATGxhfFBaFOkD
ARlse0Ef6VRiK7heiWw8dSeNcLVsQae2YXt4BdPNwzDm1GjCY1VuNOH8ftZ1n6gGFxSANFAN
tTKxV6WzHsDjtetGHMLb13OVP3VjP58IK/llWGIo/NxM+KNdYhJ/ksKraOSMDgZVnfE+FkVf
qJ6bMnyHav6Eo+y+sQtrtLGI4C1uK0EQJchcPgiec9qMW7rLHwnRbLkeHE8dxI8why/J8TKQ
wPPKCLirikzrc6AE8Ebg9NXmkWUtyo7IkSix1Ps4G26NfroI9bfbeWK1f5P+opLaou6bsTmN
2expSVmwf5j3ayZkcfbBamGfuVyjdYVPEUC2wGxs8AAAAAAAAA==
--------------ms040505090501050006040704--


From nobody Fri Apr 21 09:11:26 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB7DE129481 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:11: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, RP_MATCHES_RCVD=-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 Jj9ftNgLeC7r for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:11:22 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 782B512960D for <ietf@ietf.org>; Fri, 21 Apr 2017 09:11:22 -0700 (PDT)
Received: from [128.9.184.96] ([128.9.184.96]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v3LGA4Ho017648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Apr 2017 09:10:05 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Toerless Eckert <tte@cs.fau.de>, Nico Williams <nico@cryptonector.com>
Cc: Patrik F?ltstr?m <paf@frobbit.se>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, Paul Eggert <eggert@cs.ucla.edu>
References: <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
From: Joe Touch <touch@isi.edu>
Message-ID: <1bd9112d-091b-7889-633a-69e2137b8ca0@isi.edu>
Date: Fri, 21 Apr 2017 09:10:02 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/18sAG48Vt2NrUw7qO2BXFdzjwls>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 16:11:24 -0000

Hi, all,

Again, this discussion is continuing over in ART at the advice of the IESG.

I'll post followups there.

Joe


On 4/18/2017 4:21 PM, Toerless Eckert wrote:
> Nice!
>
> Why not start to tackle the problem pragmatically before asking for standards
> when its clearly a political issue.
>
> a) RFC describing the problems developers and system deployments can face
>   because of leap seconds.
> b) And best current practices to get around those issues. Eg: Expect clock
>   smear on Jan 1 == reduced accuracy of ~1. Unless OS or other trusted
>   info source gives explicit indication: NO leap, no smear.
> c) And finally a description of the worst open issues when b) is applied.
>    Anything worse than labels on products "reduced functionality on Jan 1
>    after a leap second" ?
>
> Cheers
>     Toerless
>
> On Tue, Apr 18, 2017 at 05:20:06PM -0500, Nico Williams wrote:
>> On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
>>> As I said, I want 30-100 years lead time so I can bake the schedule into
>>> devices and remove a trust dependency.
>> 30 years' lead time for leap seconds?  Can't be done.
>>
>> Leap seconds depend on events such as earthquakes.
>>
>> You can estimate their frequency, but you can't estimate when they'll be
>> inserted.
>>
>> Nico
>> -- 


From nobody Fri Apr 21 09:28:56 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD770129A91 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:28:54 -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, RP_MATCHES_RCVD=-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 ec8R7YjeRlri for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:28:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E80212778D for <ietf@ietf.org>; Fri, 21 Apr 2017 09:28:53 -0700 (PDT)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1d1bQR-000LYV-T8; Fri, 21 Apr 2017 12:28:51 -0400
Date: Fri, 21 Apr 2017 12:28:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: Doug Royer <douglasroyer@gmail.com>, ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
Message-ID: <DC47E6048E80CB088257D00D@PSB>
In-Reply-To: <4e394b3d-0f12-ef16-65b6-a2b712e98da5@gmail.com>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org> <E690BED1BD448540F502C8DD@PSB> <4e394b3d-0f12-ef16-65b6-a2b712e98da5@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W1tB3JFCrnctsRPGHa-9cpBO80M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 16:28:55 -0000

--On Friday, April 21, 2017 09:52 -0600 Doug Royer
<douglasroyer@gmail.com> wrote:

> On 04/21/2017 09:48 AM, John C Klensin wrote:
> 
>> 
>> In addition, as others have pointed out, if you can't trust
>> your email (server) provider, then expecting others to trust
>> keys on the basis that they are obtained from that server may
>> not make a lot of sense.
> 
> You do not have to trust your or their email server. If you
> trust the cert issuer. Then use the result.
> 
> If you do not trust the cert issuer, then do not use the
> results.

Doug,

Sorry... should have been more explicit (or just stayed out of
this).  While I agree with you, given the current state of
certification quality readily available to most of us and the
process needed, in the general case, to verify a cert, I have a
lot of trouble figuring out what this thread is about if getting
the cert from the mail server doesn't add value.

There are, as Rich points out, too many cases (perhaps a large
number every year) where a direct connection cannot be made from
the MUA to the remote server (final delivery MTA or something
verifiably under its control).  For almost any case involving
relaying rather than that sort of direct connection (and some
that don't), cert requests risk being used to propel a DoS or
blowback attack unless the server can verify the identity of the
MUA or at least the submission server, creating a chicken and
egg problem at best. 

The one advantage the (final delivery) mail server has is that
is is able to know --and, in general, is the only system that
knows -- which email addresses in its systems are aliases for
which other one, including such things as whether case-folding
works (and, for non-ASCII local parts, what it even means).
However, some of the discussions now going on in LAMPS
notwithstanding, the certificate issuer generally doesn't have
access to that information so the cert one gets back may not
match the address you asked about closely enough that, in the
general case, you can make a competent decision as to whether or
not to trust it.

Each one of those complications, including any returned
certificates that can't be trusted without further verification
(that might be all of them), makes the value proposition for
fixing a mail server to return certificate over something
mail-related less attractive... and the answer to the original
question in the subject line closer to "why bother?".   And, if
the plan is to connect to that server over something other than
email protocols, then it seems to me there is relatively little
advantage of trying to tie the discovery and retrieval
mechanisms to the email infrastructure rather than treating its
as a service we already know how to find with the DNS (even
though that doesn't solve all of the problems.  So that answer
is, again, "why bother?" except for a very selected set of cases.

Back to trying to get useful work done.

    john







From nobody Fri Apr 21 09:32:16 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97342127342 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ffT7wGoLdOa for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:32:13 -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 E14371293DF for <ietf@ietf.org>; Fri, 21 Apr 2017 09:32:12 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id x184so102905468oia.1 for <ietf@ietf.org>; Fri, 21 Apr 2017 09:32:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=kOGTb3un282MrbZ6cnokzjfxkbVXV69OrJF1dM0Bpns=; b=oaB3KJUN3QF9hV7ynxucLEktxQNSBawaORfP6FuVQ4u6vGy7L9qzNgK7zrSP/JqEsm 2tctOYzxCgK25SXURL3LD8PmgXRQGmv18e7IgifurkJepLvLUFDKk33UtXCpuEKqttRd Ohl+18Ybv2/7ZvBAF6Op7Jdwf2A0rC65OakaAJZNQ4SgUFvnOGRXLYHszhOgPp69iUS6 87dKWmeyeNH6KAUFkIOPn5RVGIXaiY46ibj32qLcj2H3YtZH2SPfkwq3SO7/CKMBJtyU PHlz/UiO5u7GnPiPHkRCP5jd6HCQPP/tMnEFlQhXkMbCS2sjC2c58etoXZPdAU+LHgzL gHLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=kOGTb3un282MrbZ6cnokzjfxkbVXV69OrJF1dM0Bpns=; b=m7m6bW+pal2Nl0TbhOg0mnLJ4tiuZInelgWaogbnCbHYi4cbhYVwGCg55r6AFhiPLf pGD4As4mvgqtDAb9nrNy0lqs7ftqUlYeWFmenlGQVD2yToQV2kuq3OqBQACTOtJQ0MRy WVuGDpaZBZL57B7VqWR+Y0CuOJpvZWJsWHbfcKm2EW9MFP9xxbrRtWcS4iNvmWUNwMO7 n2TjBLCnXVqoSGffCoEtFLhSmW+VdtOAj8hmWpa+xq3hu3f4EWtzucqThS1jDeYMlO2i 8RnO8BVr5XmN5wLMwZrQScecJfTy464um+y2RkUOVTwn/qAabu4oML8+O2bTzXvzlOTC MyMQ==
X-Gm-Message-State: AN3rC/547OmtQr3m8CnDQFQdV82yqojPCnjnHSYnWOkOl37c+/KJ0X4U 3KJZcCZ+R0olDV1skZ/UGwBSWR+JSA==
X-Received: by 10.157.34.21 with SMTP id o21mr8092643ota.201.1492792332274; Fri, 21 Apr 2017 09:32:12 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 09:32:11 -0700 (PDT)
In-Reply-To: <20170418222004.GB2856@localhost>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 12:32:11 -0400
X-Google-Sender-Auth: 7Qy6_4k-CSybAYc7EjjU72Ib6uo
Message-ID: <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com>
Subject: Re: Predictable Internet Time
To: Nico Williams <nico@cryptonector.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>,  =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=001a113d6f5cb05341054dafccbe
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Bwx84f2CbFUDiM2UvoF8yaaDPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 16:32:15 -0000

--001a113d6f5cb05341054dafccbe
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 18, 2017 at 6:20 PM, Nico Williams <nico@cryptonector.com>
wrote:

> On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
> > As I said, I want 30-100 years lead time so I can bake the schedule int=
o
> > devices and remove a trust dependency.
>
> 30 years' lead time for leap seconds?  Can't be done.
>
> Leap seconds depend on events such as earthquakes.
>
> You can estimate their frequency, but you can't estimate when they'll be
> inserted.
>

=E2=80=8BOf course it can be done. I can show you one very simple algorithm=
 that
allows every leap second to the end of time to be known right now:

"All leap seconds are abolished. UTC =3D TAI +37 for all future dates."


We do not need to let the astronomers mess around with time according to
their calendars. What I proposed was to define PIT in such a way that the
difference between PIT and UTC is highly unlikely to be more than 5 seconds
but the table of leap seconds is set 30 years ahead of time.

The basic scheme is to observe the current frequency of leap seconds (8 in
 the past 30 years) and use a simple linear extrapolation to approximate
that for the next 30 years. For dates after 2047, the leap second table and
approximation function will be updated so as to minimize the divergence
between PIT and UTC. If UTC is ahead of PIT in 2018, then an additional
leap second will be scheduled for 30 years in the future, unless a leap
second would have been scheduled for that date anyway in which it will
carry over to the next year.


=E2=80=8BThe scheme proposed guarantees complete predictability over a 30 y=
ear
timespan while ensuring that the deviation between PIT and solar time is
never more than a few seconds. If the frequency of leap seconds becomes too
high, the extrapolation function can be changed. At the end of the day, the
earth is only going to speed up its rotation for very brief intervals, the
long term trend is always downwards.=E2=80=8B

--001a113d6f5cb05341054dafccbe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ap=
r 18, 2017 at 6:20 PM, Nico Williams <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:nico@cryptonector.com" target=3D"_blank">nico@cryptonector.com</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 03, 2017 at 05:34=
:11PM -0500, Phillip Hallam-Baker wrote:<br>
&gt; As I said, I want 30-100 years lead time so I can bake the schedule in=
to<br>
&gt; devices and remove a trust dependency.<br>
<br>
30 years&#39; lead time for leap seconds?=C2=A0 Can&#39;t be done.<br>
<br>
Leap seconds depend on events such as earthquakes.<br>
<br>
You can estimate their frequency, but you can&#39;t estimate when they&#39;=
ll be<br>
inserted.<br></blockquote><div><br></div><div><div class=3D"gmail_default" =
style=3D"font-size:small">=E2=80=8BOf course it can be done. I can show you=
 one very simple algorithm that allows every leap second to the end of time=
 to be known right now:</div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">&=
quot;All leap seconds are abolished. UTC =3D TAI +37 for all future dates.&=
quot;</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">We do not need to let the ast=
ronomers mess around with time according to their calendars. What I propose=
d was to define PIT in such a way that the difference between PIT and UTC i=
s highly unlikely to be more than 5 seconds but the table of leap seconds i=
s set 30 years ahead of time.<br></div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">The basic scheme is to observe the current frequency of leap sec=
onds (8 in =C2=A0the past 30 years) and use a simple linear extrapolation t=
o approximate that for the next 30 years. For dates after 2047, the leap se=
cond table and approximation function will be updated so as to minimize the=
 divergence between PIT and UTC. If UTC is ahead of PIT in 2018, then an ad=
ditional leap second will be scheduled for 30 years in the future, unless a=
 leap second would have been scheduled for that date anyway in which it wil=
l carry over to the next year.</div><br></div><div><br></div><div><div clas=
s=3D"gmail_default" style=3D"font-size:small">=E2=80=8BThe scheme proposed =
guarantees complete predictability over a 30 year timespan while ensuring t=
hat the deviation between PIT and solar time is never more than a few secon=
ds. If the frequency of leap seconds becomes too high, the extrapolation fu=
nction can be changed. At the end of the day, the earth is only going to sp=
eed up its rotation for very brief intervals, the long term trend is always=
 downwards.=E2=80=8B</div><br></div></div></div></div>

--001a113d6f5cb05341054dafccbe--


From nobody Fri Apr 21 09:56:32 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48990129A8F for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level: 
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkXT5WaKNlF2 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:56:29 -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 D47A3127871 for <ietf@ietf.org>; Fri, 21 Apr 2017 09:56:28 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id y11so70998940oie.0 for <ietf@ietf.org>; Fri, 21 Apr 2017 09:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=gqzuRARF6Aqv1qLNiLNU/OLF/eWyXQKIMGK6c+wKbAA=; b=OPupVy6rhCjZhOOk4mSuMGFN92Dtou3Vif656Tb9jZXUSbeCWQF6qLmk6yJH0Xxyz9 2YBL/+uiPmDetZqOY4AvjIPd7oDEzYiEkYMsstYSOsym2jD2qP8Mmmm7RwC7SO+qzoVo 8hFleawDzk+Mr133dwDvYSUXrLfQ02vvzvPQaRkMcQK5bJclJ2MUYVgZIedYHnhcTu7z Wm42YN2DoMNR7xNKNTwwXDkz014BL0OUSrTylv8SzebJ9TR0NzeTjfqOpPJOxJzbf10s QTuTFkN1dxWiZKzRwgwEE+E3NWz6ePBCzUmCK2Puutmzdul8TN7opeFE8rcUuvIZV6yG xoqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=gqzuRARF6Aqv1qLNiLNU/OLF/eWyXQKIMGK6c+wKbAA=; b=BILQaUO7Xhw97iMTyQRVUMRwqLAUNWgfF1/EP+JuLFd9CrL6ImJLZjl9VctKlc4v98 9VfO2KNxJ2QJ3z84pWi75FeP5t2vCYyeI8A6aFAjr4uYz5YrI0jEpE102sDT9LPPybWQ ZJJw+9uSoHA0vxyOYDuQQfalxTJ0Y5PiXk8UJ2488Lq2qzyic2lfdKOUz4GrBW4VQPAv W6g04cblBDYtttmr6gh7ncOc7DWyANADh6smry+HuRVrXEBnlIirafZPbKa5lR9lvBSE kCqxM4SkXzyFIkrGb6fmZIIoymVwwjgadPLm5FInP6s2XuX8CJAIMIpuh5DzGMb0N96K 2IBg==
X-Gm-Message-State: AN3rC/7owR3YlQRC9GCdNUu8piToS+2MEdhUTpDbsHNKQCKC51wpEcQf mDfjFqaHCqwJfaKnE/1bYVoT1ItkaQ==
X-Received: by 10.157.47.69 with SMTP id h63mr9016570otb.89.1492793788185; Fri, 21 Apr 2017 09:56:28 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 09:56:27 -0700 (PDT)
In-Reply-To: <DC47E6048E80CB088257D00D@PSB>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <32b6bba4-cd4b-167f-b3d1-36733d1504c2@gmail.com> <20170421133535.GA21229@gsp.org> <E690BED1BD448540F502C8DD@PSB> <4e394b3d-0f12-ef16-65b6-a2b712e98da5@gmail.com> <DC47E6048E80CB088257D00D@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 12:56:27 -0400
X-Google-Sender-Auth: OCm50nF4M1aunuBwjDzQq1t_4og
Message-ID: <CAMm+LwhwMwWoXf48dudE_zu=S8xkNOj_cbCRDhwFjipZQEecUQ@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: John C Klensin <john-ietf@jck.com>
Cc: Doug Royer <douglasroyer@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c030bf677c2c0054db023f1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rPv1nkpSlCF5A36slaS9cWRzQA0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 16:56:31 -0000

--94eb2c030bf677c2c0054db023f1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 21, 2017 at 12:28 PM, John C Klensin <john-ietf@jck.com> wrote:

> --On Friday, April 21, 2017 09:52 -0600 Doug Royer
> <douglasroyer@gmail.com> wrote:
>
> > On 04/21/2017 09:48 AM, John C Klensin wrote:
> >
> >>
> >> In addition, as others have pointed out, if you can't trust
> >> your email (server) provider, then expecting others to trust
> >> keys on the basis that they are obtained from that server may
> >> not make a lot of sense.
> >
> > You do not have to trust your or their email server. If you
> > trust the cert issuer. Then use the result.
> >
> > If you do not trust the cert issuer, then do not use the
> > results.
>
> Doug,
>
> Sorry... should have been more explicit (or just stayed out of
> this).  While I agree with you, given the current state of
> certification quality readily available to most of us and the
> process needed, in the general case, to verify a cert, I have a
> lot of trouble figuring out what this thread is about if getting
> the cert from the mail server doesn't add value.
>
=E2=80=8B...

The big flaw I see in the current S/MIME PKI is that the WebPKI is only
really designed to support validation of organizations and there is no
comparable infrastructure for individuals. Nor is it possible to extend the
WebPKI approach usefully.

The total market for TLS certs is over $1 billion a year. The market for
S/MIME certs to be used across organizations is less than $10 million. Yes,
there is a market to support Intranet S/MIME but the internet market is
tiny.


One change I would like to see is to make enterprise level S/MIME certs the
norm. So instead of the CA issuing certificates for Alice@example.com, it
issues an example.com certificate that can then be combined with some other
credential issued by example.com that is specific to Alice.

We could use PKIX pathmath and issuer constraints for this of course. But
they are kinda screwed up by existing deployment.
=E2=80=8B

=E2=80=8BMy problem with my code right now is that my original demo was des=
igned to
deep integrate with Outlook Express which became Windows Essentials and is
now unavailable. The new Windows 10 mail client looks like it should be a
lot better and a lot easier to integrate to. However, the client only
became viable a few months ago, with the Anniversary update and the =E2=80=
=8BAPI
documentation is almost non existent.

What I need for my demo is the ability to

1) Read the mail client configuration to enumerate accounts and determine
the outbound mail server, etc, etc. for each

2) Create a mail account via an API.

3) Bind the S/MIME credentials.

At present, it seems like the last might need no more than just inserting
the correct cert into the correct cert store and watching it get picked up
automatically.

I would do this for Thunderbird only the code is really impenetrable and
the developers are planning to declare that code base EOL and move to a
scratch rewrite.


=E2=80=8BFor encryption, an outbound SUBMIT proxy running on the same machi=
ne as
the mail client is going to be essential in the short run as strong
addresses and policy driven opportunistic email encryption requires a plug
in approach and plug ins are disappearing from the infrastructure.

--94eb2c030bf677c2c0054db023f1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Ap=
r 21, 2017 at 12:28 PM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">--On Friday, April 21, 2017 09:52 -=
0600 Doug Royer<br>
<span class=3D"">&lt;<a href=3D"mailto:douglasroyer@gmail.com">douglasroyer=
@gmail.com</a>&gt; wrote:<br>
<br>
&gt; On 04/21/2017 09:48 AM, John C Klensin wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; In addition, as others have pointed out, if you can&#39;t trust<br=
>
&gt;&gt; your email (server) provider, then expecting others to trust<br>
&gt;&gt; keys on the basis that they are obtained from that server may<br>
&gt;&gt; not make a lot of sense.<br>
&gt;<br>
&gt; You do not have to trust your or their email server. If you<br>
&gt; trust the cert issuer. Then use the result.<br>
&gt;<br>
&gt; If you do not trust the cert issuer, then do not use the<br>
&gt; results.<br>
<br>
</span>Doug,<br>
<br>
Sorry... should have been more explicit (or just stayed out of<br>
this).=C2=A0 While I agree with you, given the current state of<br>
certification quality readily available to most of us and the<br>
process needed, in the general case, to verify a cert, I have a<br>
lot of trouble figuring out what this thread is about if getting<br>
the cert from the mail server doesn&#39;t add value.<br></blockquote><div><=
div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B...</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small">The big flaw I see in the current=
 S/MIME PKI is that the WebPKI is only really designed to support validatio=
n of organizations and there is no comparable infrastructure for individual=
s. Nor is it possible to extend the WebPKI approach usefully.</div><div cla=
ss=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmai=
l_default" style=3D"font-size:small">The total market for TLS certs is over=
 $1 billion a year. The market for S/MIME certs to be used across organizat=
ions is less than $10 million. Yes, there is a market to support Intranet S=
/MIME but the internet market is tiny.</div><div class=3D"gmail_default" st=
yle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">One change I would like to see is to make enterprise level S/MIME certs=
 the norm. So instead of the CA issuing certificates for <a href=3D"mailto:=
Alice@example.com">Alice@example.com</a>, it issues an <a href=3D"http://ex=
ample.com">example.com</a> certificate that can then be combined with some =
other credential issued by <a href=3D"http://example.com">example.com</a> t=
hat is specific to Alice.</div><div class=3D"gmail_default" style=3D"font-s=
ize:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small"=
>We could use PKIX pathmath and issuer constraints for this of course. But =
they are kinda screwed up by existing deployment.=C2=A0</div><div class=3D"=
gmail_default" style=3D"font-size:small">=E2=80=8B</div><br></div><div><div=
 class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BMy problem with=
 my code right now is that my original demo was designed to deep integrate =
with Outlook Express which became Windows Essentials and is now unavailable=
. The new Windows 10 mail client looks like it should be a lot better and a=
 lot easier to integrate to. However, the client only became viable a few m=
onths ago, with the Anniversary update and the =E2=80=8BAPI documentation i=
s almost non existent.</div><div class=3D"gmail_default" style=3D"font-size=
:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">Wh=
at I need for my demo is the ability to</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">1) Read the mail client configuration to enumerate accounts =
and determine the outbound mail server, etc, etc. for each</div><div class=
=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_=
default" style=3D"font-size:small">2) Create a mail account via an API.</di=
v><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cla=
ss=3D"gmail_default" style=3D"font-size:small">3) Bind the S/MIME credentia=
ls.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-size:small">At present, it seems =
like the last might need no more than just inserting the correct cert into =
the correct cert store and watching it get picked up automatically.</div><d=
iv class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">I would do this for Thunderbir=
d only the code is really impenetrable and the developers are planning to d=
eclare that code base EOL and move to a scratch rewrite.</div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">=E2=80=8BFor encryption, an outbound SUBMIT proxy run=
ning on the same machine as the mail client is going to be essential in the=
 short run as strong addresses and policy driven opportunistic email encryp=
tion requires a plug in approach and plug ins are disappearing from the inf=
rastructure.</div><br></div><div><br></div><div>=C2=A0</div></div></div></d=
iv>

--94eb2c030bf677c2c0054db023f1--


From nobody Fri Apr 21 10:00:30 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0733129577 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, RP_MATCHES_RCVD=-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=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 rh6TWbqeecmD for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:00:26 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::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 7683B127871 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:00:26 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id q78so14083071vke.3 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:00:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TPd9Tx9lMtkEnwC18CaqBm7+Tq1NpWD3vPo/4YXNqp4=; b=hAbYfbu4kbhlW1BiluK6kujcuScTYQAx5gDs1iLfzO3sizmV4dpmkSvTQtRxyEZWe6 v9katWhGEOoa4tnAZsrgtgn2HwuHqLyB4b9BUZM3UZHjpuRBRTR5YpeoZQdax9y5Cqdx yf9WE68SoyN7oqi6QhWdHZJg+4RNqMtBoPhthXmvg+LefLPRcds+Te5HLVBIqqWuEKsY V85J8C1XpefMLxkVxxRb1TITOsxjidBksXr3LnV2py5DdGEjFBaq34FIXnaxDuUFBC/J EMKRHfYZdDL6iILh64WwQCnzzaDVI8br6JypOn3Jg8RghqB/f0FmEX7vMJV9sM/TTE7M sugw==
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=TPd9Tx9lMtkEnwC18CaqBm7+Tq1NpWD3vPo/4YXNqp4=; b=tMWUNorDBBZ3hMwismbl8d3GZz52OTSz/U2uz8fPa8Q6chntjkyH0jCXqaYONxNXlW 9cMJdu7UKMxmHotpxpFO2dm6u4TB0QKA5gdCNTb2w6WjcLgGEcCWHe9LB030ZSgjSFhw li0Y09Cs4ZmC5RmtFk2GRA8Dg/UEjrXMz9PMlbf2X5eBG4tP3sL4/rXiBQQPrRgBapo2 u+vpnfaO+bFWcMSjgSsGvbNNBl9jkWNXYbaFG9bP7TUbN2JCgT5ByafEBqbLMOR3RfEv 1zh50S7sowuwPDtALDqosdv3mwKJaHWJ2rnFsIionOi28SHJwyIUdpO5NRX7DINmeTGV uweQ==
X-Gm-Message-State: AN3rC/7jh+zSF4wRpfqZXDAXwd65fcvCCp2cEq0c6Jh7aPBsisnPD+gv 1/a1of9oTDYYCFluqxIBYM8ekD/lqUOgwnOKBg==
X-Received: by 10.31.156.212 with SMTP id f203mr6040947vke.163.1492794025305;  Fri, 21 Apr 2017 10:00:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.51.200 with HTTP; Fri, 21 Apr 2017 10:00:22 -0700 (PDT)
In-Reply-To: <20170420205434.24400.qmail@ary.lan>
References: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> <20170420205434.24400.qmail@ary.lan>
From: Wei Chuang <weihaw@google.com>
Date: Fri, 21 Apr 2017 10:00:22 -0700
Message-ID: <CAAFsWK1FtqM2GqTkCWzgm-L87KoXGFW+yorRF-t===MycjR1Ow@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: John Levine <johnl@taugh.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a1142677ea04782054db031de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C38qFRG_dAg4RUMEqSQPxsbTRkw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 17:00:29 -0000

--001a1142677ea04782054db031de
Content-Type: multipart/alternative; boundary=001a1142677e9a5cb6054db0313a

--001a1142677e9a5cb6054db0313a
Content-Type: text/plain; charset=UTF-8

I just wanted to second the draft-bhjl-x509-srv approach as preferable as
opposed to a new SMTP extension.  That draft calls for transport of the
certificate request and response to be over HTTPS.  As HTTPS is based on
Web PKI and generally has more up-to-date crypto (due to the ecosystem)
that traffic will stay private.  SMTP uses STARTTLS which has stripping
problems, and its PKI is worse off.  There's a lot of self signed certs
there making certificate path validation problematic.  Just my two cents.

-Wei

On Thu, Apr 20, 2017 at 1:54 PM, John Levine <johnl@taugh.com> wrote:

> In article <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> you write:
> >> SMTP servers could be key servers without having the private key of
> >> individuals?
> >
> >Sure. If they double as HTTPS servers.
>
> As others have noted, this topic has come up more than a few times before.
>
> Here's a recent draft we wrote for a simple per domain https key
> server, based almost entirely on existing standards.  It distributes
> public keys.  Managing your private keys on all of your MUAs remains
> as intractable a problem as it's always been.
>
> https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/
>
> R's,
> John
>
>

--001a1142677e9a5cb6054db0313a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I just wanted to second the draft-bhjl-x509-srv=C2=A0appro=
ach as preferable as opposed to a new SMTP extension.=C2=A0 That draft call=
s for transport of the certificate request and response to be over HTTPS.=
=C2=A0 As HTTPS is based on Web PKI and generally has more up-to-date crypt=
o (due to the ecosystem) that traffic will stay private.=C2=A0 SMTP uses ST=
ARTTLS which has stripping problems, and its PKI is worse off.=C2=A0 There&=
#39;s a lot of self signed certs there making certificate path validation p=
roblematic.=C2=A0 Just my two cents.<div><br></div><div>-Wei</div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Apr 20, 2017=
 at 1:54 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:johnl@taug=
h.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><span class=3D"">In article &lt;<a href=3D"mailto:FC8=
31208-97A3-4F1B-A37C-F8646C3FB208@gmail.com">FC831208-97A3-4F1B-A37C-<wbr>F=
8646C3FB208@gmail.com</a>&gt; you write:<br>
&gt;&gt; SMTP servers could be key servers without having the private key o=
f<br>
&gt;&gt; individuals?<br>
&gt;<br>
&gt;Sure. If they double as HTTPS servers.<br>
<br>
</span>As others have noted, this topic has come up more than a few times b=
efore.<br>
<br>
Here&#39;s a recent draft we wrote for a simple per domain https key<br>
server, based almost entirely on existing standards.=C2=A0 It distributes<b=
r>
public keys.=C2=A0 Managing your private keys on all of your MUAs remains<b=
r>
as intractable a problem as it&#39;s always been.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/" rel=3D"no=
referrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-bhj=
l-x509-srv/</a><br>
<br>
R&#39;s,<br>
John<br>
<br>
</blockquote></div><br></div>

--001a1142677e9a5cb6054db0313a--

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

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/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
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMAQEwAHyjxWs8sJNjMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE3MDMyNTE4NDI0N1oXDTE3MDky
MTE4NDI0N1owIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDf/V6s9+sy7fHvy6Z2bKp63d5w85JpcZW9SebsKdycSAUATqgb
Gvo6SYD4qMWY3mR+O3LHmJ6WoHqr9xEd7uZ5JxxpfjGhe3MqgS5JaXuKn34q4li1EdMk8F7MB0FD
6VFzmd2OYPpKF8f3d8oyqQUHPnZvoOqCVlO4+fHapq+Rz9++cSI1UbK7KX/kOsi1q+tNEVGP1oVC
Cmy/1WK7EEGMOLo2K48AS9T3IP15I1hn/Sj4vVJrpW0rzvRpahOxWKo7SqLcwSRvDvKNue5di7iQ
eVceAPcahROEy4P20dimQXpxTVyjQG8wz75b4hwykEgPruaXn1J1usP830/0Tet5AgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFF4Fc4YKhOL19j17oEbz6tlaKO/DMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCPihhAVF7RDXtgpruF
0d7ukFX3Ki/I7JD6lTgEGdekylp4bPtLcnIZKM5+JhwalsTbInvGVI6e3VlIyVIOonCf+lIxwC0A
enfp52lsFIy12dunCtSJckTlT9LYuxSK5sA4krofdq0ZtSxJ3y8CYHzzolTGaEPqf2BhIpboO4QI
zEaRD8w652Rjfo/zP+yI+qYXzACs8erQN0B+8+hT/7Ir8NQcOztDBlNey/ynwE+p1/85y8IHPR8Y
Ssm0jF6cpyP/WDat2BbKzT0O1XuZF24UCNxasGcYjYuz3a2+JwQEfSFyFVu/lslEsd8Ehcd9siGL
t+pE4LJq0i8cDdnBhWcIMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMAQEwAHyj
xWs8sJNjMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCAK6FzUmaXesv7QQhnl9NuV
kQiEDjmL2Kgx6EhNwiJI5jAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzA0MjExNzAwMjVaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAV58IQA+W+m4c7iyHJC0A7J7wvb13oWhqodcHetLf
GYh1bC1NDRQgMy9BOuYCbu9VxGkCaP4ugo85nNoHomM+XnxAZ6CBVU3I6+FskmyQQAliFMtOQklR
Eb06i2CeJMHobAEDIm1fTjgezIm3QWdkYLgAOKygy83NfVeWF/uhJmg/Uu5vZPU1vJiXlaYzi69a
YsUmN92JF3+xX4+JvkkDZUivbhYpnUgTqeqPJFgT4kwz9gwjMxL8Coz0u1gjyGSdBMFPAedJyGEv
ouzA+9l6HfkC105U5iyaIZjJISsmPtWR+p1vQ/fHdexMhTjzKEnmX/T70s5LKhP180J7EMYivg==
--001a1142677ea04782054db031de--


From nobody Fri Apr 21 10:26:35 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C330D12957A for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level: 
X-Spam-Status: No, score=-4.799 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, RCVD_IN_MSPIKE_H2=-2.8, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 se1AgQuaCjMo for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:26:32 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0071294A3 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:26:32 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id AC329A00CEC1; Fri, 21 Apr 2017 10:26:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=LDk0x/5S0Gbv4t m/7GwSok+6/UE=; b=fczKDuEzfNjI1iG/NhE4TNKyqm4DkfAeRD3eVLeXXwhmHi E2p5aBLjzOBax2qnsHOGRB0oWe3FVly42sMYiB2iGyD7P43Yb5O8QM/mnOSIVnGs BtX8Hmp/yxRwaZdPXQCUmkqNBusTKPRvnuSyO7OkiudZ6x9VGHv5bdIv3Kp7Q=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id 3CC7DA000B32; Fri, 21 Apr 2017 10:26:31 -0700 (PDT)
Date: Fri, 21 Apr 2017 12:26:27 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>
Subject: Re: Predictable Internet Time
Message-ID: <20170421172626.GG2856@localhost>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qjoddn9RHEMOUQIQRc_LaK8Vd-4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 17:26:34 -0000

On Fri, Apr 21, 2017 at 12:32:11PM -0400, Phillip Hallam-Baker wrote:
> On Tue, Apr 18, 2017 at 6:20 PM, Nico Williams <nico@cryptonector.com>
> wrote:
> > On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
> > > As I said, I want 30-100 years lead time so I can bake the schedule into
> > > devices and remove a trust dependency.
> >
> > 30 years' lead time for leap seconds?  Can't be done.
> >
> > Leap seconds depend on events such as earthquakes.
> >
> > You can estimate their frequency, but you can't estimate when they'll be
> > inserted.
> >
> 
> Of course it can be done. I can show you one very simple algorithm that
> allows every leap second to the end of time to be known right now:
> 
> "All leap seconds are abolished. UTC = TAI +37 for all future dates."

That's moving the goal posts, and it's not your smeared time proposal.

Good, because smeared time is a terrible idea.  We don't need more time
standards to convert between.  Smearing time does not make UTC go away,
nor conversions to/from UTC.  Systems will always need to know about
leap seconds in order to convert to/from UTC because there will always
be parts of the system (or apps) that need TAI or something close to
TAI.  Smearing does not make that go away -- it solves nothing.

"Internet time" (that which we use in [new] Internet protocols) should
just be TAI.  And every existing Internet protocol should be updated to
indicate which time is used in practice, UTC or TAI, regardless of what
was originally specified.

Nico
-- 


From nobody Fri Apr 21 10:31:34 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1999129B08 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLxzFKEOZDv4 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:31: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 97989129A98 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:31:27 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id s131so18106511oia.3 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=dplpMo1xoN8nEAn3iaP+gHYImJYqr+IJ46f7ke9AX+0=; b=ShywB9k5otQr9ZT67222NIUzVeN2x2QH4kBJtvkT/BQMhE7jN561poa6hcdPAikCML MOMiTVXz1VvR7e7O5rA7XoX4eU16SsJPFiZDNSScbzv1NPcNS3ki1T3b86gYgTwhUrq0 aWzvKmrKQR1dOwFrjI/8bcMOMNgr9iRaif1LP7pcDgIb1cDKaCZI1tYtR7MdXCX8r180 2Y/CI+yxs7wblMt4Z+rbFibmFJPStJ/2/7U3TvZMDFWjab7mPLs90PV3MT8YqozLrGr3 KPCaxQFteVzRsIwDuITIbhVXIA1rOw6muN4+NapT0KWcKNJgrHFm3lVU1+7qOKUIJn73 yvPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=dplpMo1xoN8nEAn3iaP+gHYImJYqr+IJ46f7ke9AX+0=; b=hQWNTbnNqFPzCqeZOQ9BYYI5vUZ/cBilzsKLv6JPbqzC5PX1VXfsIeE7VKfH6cVO9c hzl7F253lTnE1igPpOLjDLWoOuvnZ8xDbZ/wJKyMpjrOcoFYFaynAwVZRB64giWWIUWC RVkK0P+cDxSfmKC3hcagdWoPG6I1PIImy7TM4CABDv0G5zVTIq5l+3L0H3Qr7yCQVZb7 GALQIAfA5hXgKNhke8E94t1Vz+Z8L8CyyfhJIA64qv9OW+XMLG+Kr23/zlMW12zGQ2wR BwqgcOuG6jblzTdZBpUr1PtfG+w15mxY8aMEHc01XUyxeh9B1nDAYqmQYXjAb1DGsXVX nZsw==
X-Gm-Message-State: AN3rC/4r+9hM4tm6CTHhmqFrwOwpR/Kw7/8Mq615IkTA4qwGdrJ6xVdK hUYOCY3a4qJrH535gHCvV1kQr4zQMA==
X-Received: by 10.202.81.83 with SMTP id f80mr8719392oib.9.1492795887047; Fri, 21 Apr 2017 10:31:27 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 10:31:26 -0700 (PDT)
In-Reply-To: <CAAFsWK1FtqM2GqTkCWzgm-L87KoXGFW+yorRF-t===MycjR1Ow@mail.gmail.com>
References: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> <20170420205434.24400.qmail@ary.lan> <CAAFsWK1FtqM2GqTkCWzgm-L87KoXGFW+yorRF-t===MycjR1Ow@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 13:31:26 -0400
X-Google-Sender-Auth: uKsfUv3dNjDTtFs8X6P33wTAqW0
Message-ID: <CAMm+LwivmUDD8Fjihiw7moFFphfL6RcT_7EFOPh7gDhvgT7M6A@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: Wei Chuang <weihaw@google.com>
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113b06c491daf7054db0a0cf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QWKnHe0qxyuNROaILAK15bubyx0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 17:31:30 -0000

--001a113b06c491daf7054db0a0cf
Content-Type: text/plain; charset=UTF-8

Again, how does the draft advance on the existing RFC?

https://tools.ietf.org/html/rfc4386

On Fri, Apr 21, 2017 at 1:00 PM, Wei Chuang <weihaw@google.com> wrote:

> I just wanted to second the draft-bhjl-x509-srv approach as preferable as
> opposed to a new SMTP extension.  That draft calls for transport of the
> certificate request and response to be over HTTPS.  As HTTPS is based on
> Web PKI and generally has more up-to-date crypto (due to the ecosystem)
> that traffic will stay private.  SMTP uses STARTTLS which has stripping
> problems, and its PKI is worse off.  There's a lot of self signed certs
> there making certificate path validation problematic.  Just my two cents.
>
> -Wei
>
> On Thu, Apr 20, 2017 at 1:54 PM, John Levine <johnl@taugh.com> wrote:
>
>> In article <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> you write:
>> >> SMTP servers could be key servers without having the private key of
>> >> individuals?
>> >
>> >Sure. If they double as HTTPS servers.
>>
>> As others have noted, this topic has come up more than a few times before.
>>
>> Here's a recent draft we wrote for a simple per domain https key
>> server, based almost entirely on existing standards.  It distributes
>> public keys.  Managing your private keys on all of your MUAs remains
>> as intractable a problem as it's always been.
>>
>> https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/
>>
>> R's,
>> John
>>
>>
>

--001a113b06c491daf7054db0a0cf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Aga=
in, how does the draft advance on the existing RFC?</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small"><a href=3D"https://tools.ietf.org/html/rfc4386" =
target=3D"_blank" style=3D"font-size:12.8px">https://tools.ietf.org/html/<w=
br>rfc4386</a><br></div></div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Fri, Apr 21, 2017 at 1:00 PM, Wei Chuang <span dir=3D"ltr">=
&lt;<a href=3D"mailto:weihaw@google.com" target=3D"_blank">weihaw@google.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">=
I just wanted to second the draft-bhjl-x509-srv=C2=A0approach as preferable=
 as opposed to a new SMTP extension.=C2=A0 That draft calls for transport o=
f the certificate request and response to be over HTTPS.=C2=A0 As HTTPS is =
based on Web PKI and generally has more up-to-date crypto (due to the ecosy=
stem) that traffic will stay private.=C2=A0 SMTP uses STARTTLS which has st=
ripping problems, and its PKI is worse off.=C2=A0 There&#39;s a lot of self=
 signed certs there making certificate path validation problematic.=C2=A0 J=
ust my two cents.<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></=
div><div>-Wei</div></font></span></div><div class=3D"HOEnZb"><div class=3D"=
h5"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Apr 2=
0, 2017 at 1:54 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:joh=
nl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><span>In article &lt;<a href=3D"mailto:FC83120=
8-97A3-4F1B-A37C-F8646C3FB208@gmail.com" target=3D"_blank">FC831208-97A3-4F=
1B-A37C-F8646<wbr>C3FB208@gmail.com</a>&gt; you write:<br>
&gt;&gt; SMTP servers could be key servers without having the private key o=
f<br>
&gt;&gt; individuals?<br>
&gt;<br>
&gt;Sure. If they double as HTTPS servers.<br>
<br>
</span>As others have noted, this topic has come up more than a few times b=
efore.<br>
<br>
Here&#39;s a recent draft we wrote for a simple per domain https key<br>
server, based almost entirely on existing standards.=C2=A0 It distributes<b=
r>
public keys.=C2=A0 Managing your private keys on all of your MUAs remains<b=
r>
as intractable a problem as it&#39;s always been.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/" rel=3D"no=
referrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr>oc/draft-bhj=
l-x509-srv/</a><br>
<br>
R&#39;s,<br>
John<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a113b06c491daf7054db0a0cf--


From nobody Fri Apr 21 10:58:05 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1637912EAAF for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:58:04 -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, RP_MATCHES_RCVD=-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 IFFWah2gV54x for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:58:03 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 0DE5812EAAE for <ietf@ietf.org>; Fri, 21 Apr 2017 10:58:03 -0700 (PDT)
Received: from [128.9.184.96] ([128.9.184.96]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v3LHvFSU019146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Apr 2017 10:57:15 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Nico Williams <nico@cryptonector.com>, Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com> <20170421172626.GG2856@localhost>
From: Joe Touch <touch@isi.edu>
Message-ID: <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu>
Date: Fri, 21 Apr 2017 10:57:13 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <20170421172626.GG2856@localhost>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X1Rd2a0BK_ZkSBga2ltVTuvYru0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 17:58:04 -0000

On 4/21/2017 10:26 AM, Nico Williams wrote:
> "Internet time" (that which we use in [new] Internet protocols) should
> just be TAI.  And every existing Internet protocol should be updated to
> indicate which time is used in practice, UTC or TAI, regardless of what
> was originally specified.
I would be very glad of we defined Internet Time as TAI, but also expect
all protocols to understand both TAI and UTC if possible.

Joe


From nobody Fri Apr 21 10:59:50 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4118F129B38 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IULwwWqQdFZs for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 10:59:43 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 CBFF1129B22 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:59:42 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id s131so19194431oia.3 for <ietf@ietf.org>; Fri, 21 Apr 2017 10:59:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=TM2Ou0kD6dFFGlDlB65y5MKdngv/Mdfgas9AIxjSspo=; b=JHNx+KELrLIwPEU5YPJZp6Fsyro1wQiReomiGXQ1gq7IUotH0V9nim8fp5yemScmcf ZjCQhGmkrqKlxNEnHa8dUrTU0lityVwPRVOMie0NV7CyXZ0nOTaDgxgbT6KS2oNaolji bw6islWcVnJcfvi5ciszPe0jYaHiIu/OU3kF+8jIgJKck610iUSRyMAVyaLgq6AVkYan 0AF0y7hPsUUyjUPz6qRFxh+nSiCHzEvYfYjWNOeYY6V5RfsxgWumh9zhRmmGViWbti5Z Fcp1OQgn36IHZRHm1d2Kbm/bB1ggbic6Mv+EzZ4XjMfEDzWBGLPvlHO9A5Qa3eUITMPd oigw==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=TM2Ou0kD6dFFGlDlB65y5MKdngv/Mdfgas9AIxjSspo=; b=ZxyTHB1olJqGnTLUh7WWwlvWSMwN414G0wHvs3hG75z766E0hxMCDjoyU/qFl1lz4e 4fL9oX9Di88fIz6vrmvTiBRaEjJZ2vUBWS7Dkdg3QlmCNkaaSdwXSV3exOrqX0B0OEQV OZhS5OlpniV4WKa1t0GBCK/lkibSzw7Bq38uIffQdB6YGnXxUQVMCUDDguhKjN+ZmyU5 PLL5e4dJLv8dWG9Xrvom26tEfZOk7KtdP5k183YeJ20FKEdngRuy1/s2ApKj6sab0Y9K tdHrgEnZOynRvxgbPMvxzPiNlxgw4m3YmphuXONGdY6ygk0OgXc4YfpFG1Nc9J+hw/7C ekqw==
X-Gm-Message-State: AN3rC/40pC/JdfHzjBPIfjRyWm+adE3BSryb3ghVgJh4TQaSyLg6wpLs PxQXEkiLIFX2GGvbkmk=
X-Received: by 10.202.179.5 with SMTP id c5mr8365456oif.64.1492797581412; Fri, 21 Apr 2017 10:59:41 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id l140sm4386320oib.14.2017.04.21.10.59.39 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 10:59:40 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <c0ecde08-ce70-5e20-2126-b7624ce23997@gmail.com>
Date: Fri, 21 Apr 2017 11:59:38 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000108080606090504090500"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xVHUjRrxoroFPwERpLLYF5ZEbNk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 17:59:44 -0000

This is a cryptographically signed message in MIME format.

--------------ms000108080606090504090500
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable


I have learned much in this thread!

--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDIxMTc1OTM4WjAvBgkqhkiG9w0BCQQxIgQguwOY4GxlUOYfWHS0veW4arp0osXeNr0h
6ZlFYaWF1+UwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAH55VHaFSTmn1
15rzsunK74cfBglB+XGXrKlYjcqdSgPMtYYLgZxeoyeGf4kDYQXmZepAtHiM+nddGHIa3oJX
5GX7J/66hD5lYvCVwtfm/oa81vJdJDJ/VmP2sGzpaJxYABaJzUnhkR8tdGSd7LzJIp2RL42e
Sw6paYTA38134/tNyEYdylmVkzNsTtSc+rcdX4ShpbOeQGpu3URZJYDiM8WpOlSfNvNfwKf/
OF/MRWpz6qH1wMDcDz48KSnZ1aQMAalq1xUsgzI8jVjFetdV8FQmA58bNeABHGmTN+zXQC4L
GnZerOl2B6cpfDJwuHTDaZ8GvzC78x2mtVlanRSVjQAAAAAAAA==
--------------ms000108080606090504090500--


From nobody Fri Apr 21 11:15:47 2017
Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB1512EAAF; Fri, 21 Apr 2017 11:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=microsoft.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 GVp5ZPV_J0TA; Fri, 21 Apr 2017 11:15:44 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0104.outbound.protection.outlook.com [104.47.33.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A386B129B31; Fri, 21 Apr 2017 11:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=/VZ5UsaK7vLD4NN+KKgNG84lH2X7MR+V4XHDq6pQ1Z8=; b=dqtqqR4Vy/z2qdG9Thi8Dy2l+mCZxv5hnL/it86gAxt74iuS/iMlmAcO3bpPVkzMQY2ivOOtHafnacfeU0q1udO6fSOlA3IM3wjhnYeXL4jLB16WmZ7W6/zFbGa7SJN/axuy+R1S4cphDFcqmLy0SwH+QyKmMCEBUqrJYoj71qo=
Received: from BY2PR21MB0084.namprd21.prod.outlook.com (10.162.78.141) by BY2PR21MB0081.namprd21.prod.outlook.com (10.162.78.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.1; Fri, 21 Apr 2017 18:15:41 +0000
Received: from BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) by BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) with mapi id 15.01.1061.003; Fri, 21 Apr 2017 18:15:41 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
CC: "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsOTWicthTbHq+0Cl6wEpb6SnVKHOtjQAgADZuACAAKJUUA==
Date: Fri, 21 Apr 2017 18:15:41 +0000
Message-ID: <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com>
In-Reply-To: <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sfc.wide.ad.jp; dkim=none (message not signed) header.d=none;sfc.wide.ad.jp; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR21MB0081; 7:qfCLDnaB8/U9ttbrq86XBAMJRHA+UXepMmUysJRHVSqaxY9gk7mTbF8siP2YSAMCgyUr8Fba8vb9ATo4JDGeqamPlbQZjBCPGeK0l5bhoBx+gPeW3YzLYVfzwgq6e2oHbNNaJFUiX8csdV4IRo5vvmgoAMzNFSXtoTsw6c/+2xhP1DqfVhHmuQPV3GcUR4LJVNKt/tQZtU7TRgoybyRE2daHmpn4GcnPC/Br857L++1KRFez+7/n5YZfUFuzAbe1FY06W9sacWAGeLze29gcEMMfuQLKs59numfvJTM2NM2h7s0fRqXQNvOwlhBd51cgMLIFKJ78pH4qCZKyvIS2A1BV1l5yilEb3SDVs9SItPI=
x-ms-office365-filtering-correlation-id: eaef3a27-4556-4407-68e1-08d488e26bb7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR21MB0081; 
x-microsoft-antispam-prvs: <BY2PR21MB008172EA596A87501DC81E57831A0@BY2PR21MB0081.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(166708455590820)(21748063052155); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123558055)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406108)(20161123555025)(20161123560025)(6072148); SRVR:BY2PR21MB0081; BCL:0; PCL:0; RULEID:; SRVR:BY2PR21MB0081; 
x-forefront-prvs: 02843AA9E0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400002)(39840400002)(39860400002)(39450400003)(39410400002)(39400400002)(43784003)(86362001)(2950100002)(102836003)(6916009)(6246003)(4326008)(7696004)(74316002)(38730400002)(110136004)(7906003)(230783001)(229853002)(33656002)(7736002)(122556002)(54356999)(5660300001)(790700001)(6116002)(76176999)(3846002)(189998001)(50986999)(9686003)(10090500001)(55016002)(66066001)(6306002)(54896002)(99286003)(54906002)(53936002)(2906002)(3280700002)(25786009)(236005)(606005)(8936002)(8676002)(81166006)(9326002)(3660700001)(6506006)(77096006)(6436002)(10290500002)(5005710100001)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR21MB0081; H:BY2PR21MB0084.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR21MB00849DB795086F08F6D7A98A831A0BY2PR21MB0084namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2017 18:15:41.3988 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR21MB0081
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NNCoLKc5hXZMz_Z76VzKUTTkbG0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 18:15:46 -0000

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

SGkgWW9zaGksDQoNCg0KDQo+IE9LLiBJIGFsc28gdGhpbmsgd2Ugc2hvdWxkIHN0YXRlIHRoYXQg
dGhlIHByb3RvY29sIHNob3VsZCBub3RpZnkgdGhlIGZhaWx1cmUgZXZlbnRzIHRvIGFwcGxpY2F0
aW9ucy4NCg0KPiBTaW5jZSBlcnJvcnMgY2FuIGhhcHBlbiBub3Qgb25seSBpbiBUQ1AsIGJ1dCBh
bHNvIFRMUyBhbmQgd2Vic29ja2V0IGxldmVsLCBtZW50aW9uaW5nIG9ubHkgVENQIGNsb3NlIG9y
IHJlc2V0IG1pZ2h0IG5vdA0KDQo+IGJlIGVub3VnaC4NCg0KDQoNCkFmdGVyIHJldmlld2luZyB3
aXRoIHRoZSBhdXRob3JzLCBhbiBhZGRpdGlvbmFsIGNsYXJpZmljYXRpb24gd2FzIGFwcGVuZGVk
IHRvIDMuNCBDb25uZWN0aW9uIEhlYWx0aCAtIGh0dHBzOi8vZ2l0aHViLmNvbS9jb3JlLXdnL2Nv
YXAtdGNwLXRscy9wdWxsLzE0MC9maWxlcw0KDQoNCg0KVGhlIG9waW5pb24gb2YgdGhlIGF1dGhv
cnMgKGFuZCBHZW5neXUgV0VJ4oCZcyByZWNlbnQgcmVzcG9uc2UgLSBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cwODYyMi5odG1sKSBpcyB0aGF0
IFJGQzY0NTUgY292ZXJzIHRoZSBXZWJTb2NrZXQgY2FzZSBhbmQgZG9lcyBub3QgbmVlZCB0byBi
ZSByZXBlYXRlZCBoZXJlLg0KDQoNCg0KPiBXaGVuIHdlIHVzZSA3MjUyLCBJIHRoaW5rIGFwcGxp
Y2F0aW9ucyBiYXNpY2FsbHkgZG9uJ3QgbmVlZCB0byBpbXBsZW1lbnQgdGltZW91dHMgb3IgcmV0
cnkgbWVjaGFuaXNtcyBhcyB0aGUgcHJvdG9jb2wNCg0KPiBwcm92aWRlcyBzdWNoIHRoaW5ncy4N
Cg0KDQoNClJGQzcyNTIgcHJvdmlkZXMgdGltZW91dHMgYW5kIHJldHJpZXMgYmVjYXVzZSBpdCdz
IGltcGxlbWVudGluZyBhIFRDUC1saWtlIHJlbGlhYmlsaXR5IG1lY2hhbmlzbSBvdmVyIFVEUCAt
IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM3MjUyI3NlY3Rpb24tMi4xDQoNCg0KDQo+
IEhvd2V2ZXIsIHdoZW4gd2UgdXNlIHRoaXMgb25lLCBpdCBzZWVtcyBhcHBsaWNhdGlvbnMgd2ls
bCBuZWVkIHRvIGhhdmUgc3VjaCBtZWNoYW5pc21zLiBJc24ndCBpdCBhIGJpdCBjb25mdXNpbmc/
IEkgYW0gdGhpbmtpbmcgdGhhdA0KDQo+IHRoZXJlIG5lZWQgdG8gYmUgc29tZSBndWlkYW5jZSBo
ZXJlLg0KDQo+IEJUVywgUE9ORyBpcyBvbmUgZXhhbXBsZS4NCg0KDQoNCkZvciBjb2FwLXRjcC10
bHMsIHRoZXJlIGFyZSBtdWx0aXBsZSBlYXJseSBpbXBsZW1lbnRhdGlvbnMuIFRoaXMgaGFzIG5l
dmVyIGJlZW4gcmVwb3J0ZWQgYXMgYSBzb3VyY2Ugb2YgY29uZnVzaW9uLg0KDQoNCg0KPj4gTXkg
c2Vuc2UgaXMgdGhhdCB3ZSBzaG91bGQgdHJlYXQgdGhpcyBhcyBhbiB1cGRhdGUgdG8gUkZDNzk1
OSBiYXNlZCBvbiB0aGUgb3JpZ2luYWwgbGFuZ3VhZ2U6DQoNCj4gSSBkb24ndCBoYXZlIGEgc3Ry
b25nIG9waW5pb24gaGVyZS4gVXBkYXRpbmcgNzk1OSBpcyBmaW5lIGZvciBtZSBpZiBpdCdzIGNs
ZWFyZXIgdG8gQ29BUCBwZW9wbGUuDQoNCg0KDQpJJ3ZlIG1lcmdlZCB0aGUgY2hhbmdlIC0gaHR0
cHM6Ly9naXRodWIuY29tL2NvcmUtd2cvY29hcC10Y3AtdGxzL3B1bGwvMTM4L2ZpbGVzDQoNCg0K
VGhhbmtzIGFnYWluIGZvciBoZWxwaW5nIHVzIHRvIGltcHJvdmUgdGhlIHF1YWxpdHkgb2YgdGhl
IGRyYWZ0LA0KDQrigKZCcmlhbg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGku
TXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25v
cm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDph
dXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJ
bWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVz
IE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29s
b3I6d2luZG93dGV4dDt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBs
YWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5r
OiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQouTXNv
Q2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToi
Q2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAx
MS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlv
bjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8
L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0
IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNo
YXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMi
IGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+SGkgWW9zaGksPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgT0suIEkgYWxzbyB0aGluayB3ZSBzaG91bGQgc3Rh
dGUgdGhhdCB0aGUgcHJvdG9jb2wgc2hvdWxkIG5vdGlmeSB0aGUgZmFpbHVyZSBldmVudHMgdG8g
YXBwbGljYXRpb25zLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+Jmd0OyBTaW5jZSBlcnJvcnMgY2FuIGhhcHBlbiBub3Qgb25seSBpbiBUQ1AsIGJ1dCBhbHNv
IFRMUyBhbmQgd2Vic29ja2V0IGxldmVsLCBtZW50aW9uaW5nIG9ubHkgVENQIGNsb3NlIG9yIHJl
c2V0IG1pZ2h0IG5vdA0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4m
Z3Q7IGJlIGVub3VnaC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QWZ0ZXIgcmV2aWV3
aW5nIHdpdGggdGhlIGF1dGhvcnMsIGFuIGFkZGl0aW9uYWwgY2xhcmlmaWNhdGlvbiB3YXMgYXBw
ZW5kZWQgdG8gMy40IENvbm5lY3Rpb24gSGVhbHRoIC0NCjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHVi
LmNvbS9jb3JlLXdnL2NvYXAtdGNwLXRscy9wdWxsLzE0MC9maWxlcyI+aHR0cHM6Ly9naXRodWIu
Y29tL2NvcmUtd2cvY29hcC10Y3AtdGxzL3B1bGwvMTQwL2ZpbGVzPC9hPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5UaGUgb3BpbmlvbiBvZiB0aGUgYXV0aG9ycyAoYW5kIEdlbmd5dSBX
RUnigJlzIHJlY2VudCByZXNwb25zZSAtDQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cwODYyMi5odG1sIj5odHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cwODYyMi5odG1sPC9hPikg
aXMgdGhhdCBSRkM2NDU1IGNvdmVycyB0aGUgV2ViU29ja2V0IGNhc2UgYW5kIGRvZXMgbm90IG5l
ZWQgdG8gYmUgcmVwZWF0ZWQgaGVyZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0
OyBXaGVuIHdlIHVzZSA3MjUyLCBJIHRoaW5rIGFwcGxpY2F0aW9ucyBiYXNpY2FsbHkgZG9uJ3Qg
bmVlZCB0byBpbXBsZW1lbnQgdGltZW91dHMgb3IgcmV0cnkgbWVjaGFuaXNtcyBhcyB0aGUgcHJv
dG9jb2w8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgcHJvdmlk
ZXMgc3VjaCB0aGluZ3MuIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5SRkM3MjUyIHBy
b3ZpZGVzIHRpbWVvdXRzIGFuZCByZXRyaWVzIGJlY2F1c2UgaXQncyBpbXBsZW1lbnRpbmcgYSBU
Q1AtbGlrZSByZWxpYWJpbGl0eSBtZWNoYW5pc20gb3ZlciBVRFAgLQ0KPGEgaHJlZj0iaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzcyNTIjc2VjdGlvbi0yLjEiPmh0dHBzOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9yZmM3MjUyI3NlY3Rpb24tMi4xPC9hPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mZ3Q7IEhvd2V2ZXIsIHdoZW4gd2UgdXNlIHRoaXMgb25lLCBpdCBzZWVtcyBh
cHBsaWNhdGlvbnMgd2lsbCBuZWVkIHRvIGhhdmUgc3VjaCBtZWNoYW5pc21zLiBJc24ndCBpdCBh
IGJpdCBjb25mdXNpbmc/IEkgYW0gdGhpbmtpbmcgdGhhdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyB0aGVyZSBuZWVkIHRvIGJlIHNvbWUgZ3VpZGFuY2UgaGVy
ZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgQlRXLCBQT05H
IGlzIG9uZSBleGFtcGxlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5Gb3IgY29hcC10
Y3AtdGxzLCB0aGVyZSBhcmUgbXVsdGlwbGUgZWFybHkgaW1wbGVtZW50YXRpb25zLiBUaGlzIGhh
cyBuZXZlciBiZWVuIHJlcG9ydGVkIGFzIGEgc291cmNlIG9mIGNvbmZ1c2lvbi4NCjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7Jmd0OyBNeSBzZW5zZSBpcyB0aGF0IHdlIHNob3Vs
ZCB0cmVhdCB0aGlzIGFzIGFuIHVwZGF0ZSB0byBSRkM3OTU5IGJhc2VkIG9uIHRoZSBvcmlnaW5h
bCBsYW5ndWFnZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsg
SSBkb24ndCBoYXZlIGEgc3Ryb25nIG9waW5pb24gaGVyZS4gVXBkYXRpbmcgNzk1OSBpcyBmaW5l
IGZvciBtZSBpZiBpdCdzIGNsZWFyZXIgdG8gQ29BUCBwZW9wbGUuPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPkkndmUgbWVyZ2VkIHRoZSBjaGFuZ2UgLSA8YSBocmVmPSJodHRwczovL2dp
dGh1Yi5jb20vY29yZS13Zy9jb2FwLXRjcC10bHMvcHVsbC8xMzgvZmlsZXMiPg0KaHR0cHM6Ly9n
aXRodWIuY29tL2NvcmUtd2cvY29hcC10Y3AtdGxzL3B1bGwvMTM4L2ZpbGVzPC9hPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlRoYW5rcyBhZ2FpbiBmb3IgaGVs
cGluZyB1cyB0byBpbXByb3ZlIHRoZSBxdWFsaXR5IG9mIHRoZSBkcmFmdCw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+4oCmQnJpYW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BY2PR21MB00849DB795086F08F6D7A98A831A0BY2PR21MB0084namp_--


From nobody Fri Apr 21 11:35:35 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB7E512EACD for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 11:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, 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 QSJZI6CH9KNN for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 11:35:31 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::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 7EC4F12EACC for <ietf@ietf.org>; Fri, 21 Apr 2017 11:35:31 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id j201so107005795oih.2 for <ietf@ietf.org>; Fri, 21 Apr 2017 11:35:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=H0rDGralMqHwCrucQz8AKdT1i4nL09X4E+WvfRAMP64=; b=Z+rFd3Ui3QYWSot+zSB6Ow4tJlVO5UbklPyqlnkkgL079zpoFA3yEnejCs5fSan0ET dOkuA7KVh3p5vjkanbk/RShz28W2OIqFulNTnkpmJ7Gv2aXjCTy33+ZRWA6slOIwOhSf L+gx1OCINYCp9pUc5pvC+YHWT4PSYOfQIL4pqWPwzU5zLfAKolOyRQaQnAfOaT36PZal C72X+GEKM0vGdOsySqxO9tmOEpsxPs+95ke2RtFHIlNUhgG+czgyEIJ0FvP8g9wr+5I9 TnbLKdBK+kvCbawLW1k2TOJmoVbmfFyHQi6W6ee29AKwmg2CaHSqReSZOp2L9Ck8rkUV ezFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=H0rDGralMqHwCrucQz8AKdT1i4nL09X4E+WvfRAMP64=; b=o9yJXpHIofRPgPH9kGvO0MGTcse+3OMIWcDV7pjOr/xqCzd+PRGz/fVlYYNglqykx2 kiVyKJAgZhycTDIbKuWxcKae8G+BYH32hySOTwWk4gPeWv3xLmjkfw/IEcu4Fifm9p9r Rp7k6+vgXI9xUIdYJBj71C88/XIKWIeJZJE4SJeIIBEJ5uRNTP5a/rWfObiMSQU+phe9 Si3pg4eAvY755UD4UekqHxsOWQpcMrsyn6HsOu8g2X941Gmb38BglwAgtg+T8OVw8OuR hGNg1173KBWJWnsyc0vd7vKXxrdU/FPt8sNqYps3DPeAZrw2vDlhl4FcxxdIXx/JJdQx Xw6g==
X-Gm-Message-State: AN3rC/4UMv/dFGASEKZSmSEF1wee66w+M9nsyCGQNxOR5jYj8mZ4pMKC 0K1dLT0Dy6IPntWBHvhjypLp5zN3+w==
X-Received: by 10.202.178.85 with SMTP id b82mr8617364oif.151.1492799730929; Fri, 21 Apr 2017 11:35:30 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 11:35:30 -0700 (PDT)
In-Reply-To: <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com> <20170421172626.GG2856@localhost> <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 14:35:30 -0400
X-Google-Sender-Auth: 6iRIKfQ1BZ7exaSMRsAdcGhGk6M
Message-ID: <CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com>
Subject: Re: Predictable Internet Time
To: Joe Touch <touch@isi.edu>
Cc: Nico Williams <nico@cryptonector.com>, Paul Eggert <eggert@cs.ucla.edu>,  IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=001a1146ac5eaed445054db185ab
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PrZTMnGhEmhGrAwM5hZaX4jBIs0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 18:35:33 -0000

--001a1146ac5eaed445054db185ab
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 21, 2017 at 1:57 PM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 4/21/2017 10:26 AM, Nico Williams wrote:
> > "Internet time" (that which we use in [new] Internet protocols) should
> > just be TAI.  And every existing Internet protocol should be updated to
> > indicate which time is used in practice, UTC or TAI, regardless of what
> > was originally specified.
> I would be very glad of we defined Internet Time as TAI, but also expect
> all protocols to understand both TAI and UTC if possible.
>
> Joe
>

=E2=80=8BTo answer the issues raised:

1) POSIX already has this pretty much covered

http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html=
=E2=80=8B

=E2=80=8Bint clock_gettime(clockid_t *clock_id*, struct timespec **tp*);=E2=
=80=8B

=E2=80=8BSo all that is required is to define clock identifiers for:

TAI (The total number of seconds elapsed since the start of the epoch)
UTC (The TAI value adjusted for UTC leap seconds, i.e. number of non leap
second seconds since the start of the epoch)
PIT (The TAI value adjusted for PIT leap seconds)

POSIX already defines constants for CLOCK_PROCESS_CPUTIME_ID, CLOCK_REALTIM=
E


All that is needed is to define the additional ones.


=E2=80=8B2) No I did not move the goalposts. My original proposal was to so=
lve the
needless chaos caused be the idiotic notion of changing the definition of
time at six months notice. The stupidity of that notion should be apparent
to all.

3) Screw the astronomers. Pluto is to a planet.=E2=80=8B

--001a1146ac5eaed445054db185ab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default"><br></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Fri, Apr 21, 2017 at 1:57 PM, Joe=
 Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_bl=
ank">touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-"><br>
<br>
On 4/21/2017 10:26 AM, Nico Williams wrote:<br>
&gt; &quot;Internet time&quot; (that which we use in [new] Internet protoco=
ls) should<br>
&gt; just be TAI.=C2=A0 And every existing Internet protocol should be upda=
ted to<br>
&gt; indicate which time is used in practice, UTC or TAI, regardless of wha=
t<br>
&gt; was originally specified.<br>
</span>I would be very glad of we defined Internet Time as TAI, but also ex=
pect<br>
all protocols to understand both TAI and UTC if possible.<br>
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
Joe<br></font></span></blockquote><div><br></div><div><div class=3D"gmail_d=
efault">=E2=80=8BTo answer the issues raised:</div><div class=3D"gmail_defa=
ult"><br></div><div class=3D"gmail_default">1) POSIX already has this prett=
y much covered</div><div class=3D"gmail_default"><br></div><div class=3D"gm=
ail_default"><a href=3D"http://pubs.opengroup.org/onlinepubs/009695399/func=
tions/clock_getres.html">http://pubs.opengroup.org/onlinepubs/009695399/fun=
ctions/clock_getres.html</a>=E2=80=8B</div></div><div><br></div><div><div c=
lass=3D"gmail_default">=E2=80=8B<tt style=3D"color:rgb(0,0,0);background-co=
lor:rgb(204,204,255)">int clock_gettime(clockid_t</tt><span style=3D"color:=
rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)">=C2=A0<=
/span><i style=3D"color:rgb(0,0,0);font-family:monospace;background-color:r=
gb(204,204,255)">clock_id</i><tt style=3D"color:rgb(0,0,0);background-color=
:rgb(204,204,255)">, struct timespec *</tt><i style=3D"color:rgb(0,0,0);fon=
t-family:monospace;background-color:rgb(204,204,255)">tp</i><tt style=3D"co=
lor:rgb(0,0,0);background-color:rgb(204,204,255)">);</tt>=E2=80=8B</div></d=
iv><div>=C2=A0</div></div><div class=3D"gmail_default">=E2=80=8BSo all that=
 is required is to define clock identifiers for:</div><div class=3D"gmail_d=
efault"><br></div><div class=3D"gmail_default">TAI (The total number of sec=
onds elapsed since the start of the epoch)</div><div class=3D"gmail_default=
">UTC (The TAI value adjusted for UTC leap seconds, i.e. number of non leap=
 second seconds since the start of the epoch)</div><div class=3D"gmail_defa=
ult">PIT (The TAI value adjusted for PIT leap seconds)</div><div class=3D"g=
mail_default"><br></div><div class=3D"gmail_default">POSIX already defines =
constants for=C2=A0<span style=3D"color:rgb(0,0,0);font-family:verdana,aria=
l,helvetica,sans-serif">CLOCK_PROCESS_CPUTIME_ID,=C2=A0</span><span style=
=3D"color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif">CLOCK_=
REALTIME</span><span style=3D"color:rgb(0,0,0);font-family:verdana,arial,he=
lvetica,sans-serif">=C2=A0</span></div><div class=3D"gmail_default"><br></d=
iv><div class=3D"gmail_default">All that is needed is to define the additio=
nal ones.=C2=A0</div><br></div><div class=3D"gmail_extra"><br></div><div cl=
ass=3D"gmail_extra"><div class=3D"gmail_default" style=3D"font-size:small">=
=E2=80=8B2) No I did not move the goalposts. My original proposal was to so=
lve the needless chaos caused be the idiotic notion of changing the definit=
ion of time at six months notice. The stupidity of that notion should be ap=
parent to all.</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">3) Screw t=
he astronomers. Pluto is to a planet.=E2=80=8B</div><br></div></div>

--001a1146ac5eaed445054db185ab--


From nobody Fri Apr 21 11:42:42 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3BA129AFF for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 11:42:41 -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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 hO_pPSHAMFYC for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 11:42:39 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 C282D128854 for <ietf@ietf.org>; Fri, 21 Apr 2017 11:42:39 -0700 (PDT)
Received: from [128.9.184.96] ([128.9.184.96]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3LIfj2e014779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Apr 2017 11:41:47 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Nico Williams <nico@cryptonector.com>, Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com> <20170421172626.GG2856@localhost> <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu> <CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <ad341d37-6256-fe0b-4f01-aa349a04ef36@isi.edu>
Date: Fri, 21 Apr 2017 11:41:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8431CAD1AC57A3D9BFD16F51"
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Apco3aexzG0erLHyOPxlvAguwLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 18:42:42 -0000

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



On 4/21/2017 11:35 AM, Phillip Hallam-Baker wrote:
>
>
> On Fri, Apr 21, 2017 at 1:57 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>
>
>     On 4/21/2017 10:26 AM, Nico Williams wrote:
>     > "Internet time" (that which we use in [new] Internet protocols)
>     should
>     > just be TAI.  And every existing Internet protocol should be
>     updated to
>     > indicate which time is used in practice, UTC or TAI, regardless
>     of what
>     > was originally specified.
>     I would be very glad of we defined Internet Time as TAI, but also
>     expect
>     all protocols to understand both TAI and UTC if possible.
>
>     Joe
>
>
> ​To answer the issues raised:
>
> 1) POSIX already has this pretty much covered
>
> http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html​
>
> ​int clock_gettime(clockid_t /clock_id/, struct timespec */tp/);​
>  
> ​So all that is required is to define clock identifiers for:
>
> TAI (The total number of seconds elapsed since the start of the epoch)
> UTC (The TAI value adjusted for UTC leap seconds, i.e. number of non
> leap second seconds since the start of the epoch)
If these aren't already included, I'm surprised (at least UTC).

> PIT (The TAI value adjusted for PIT leap seconds)

We don't need PIT.

> POSIX already defines constants
> for CLOCK_PROCESS_CPUTIME_ID, CLOCK_REALTIME 
>
> All that is needed is to define the additional ones. 
>
>
> ​2) No I did not move the goalposts. My original proposal was to solve
> the needless chaos caused be the idiotic notion of changing the
> definition of time at six months notice. The stupidity of that notion
> should be apparent to all.

There is no getting around the fact that the rest of the planet accepts
leap seconds. If that's not something you want to track, then use TAI
and be off-sync with the rest of the world when they use UTC.

PIT does nothing helpful except add yet another level of indirection and
confusion here.

> 3) Screw the astronomers. Pluto is to a planet.​

IMO, this issue is sufficently driven by "rough consensus and running
code" of the entire planet right now - where all governments already use
UTC.

Joe


--------------8431CAD1AC57A3D9BFD16F51
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 4/21/2017 11:35 AM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_default"><br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Apr 21, 2017 at 1:57 PM, Joe
            Touch <span dir="ltr">&lt;<a href="mailto:touch@isi.edu"
                target="_blank" moz-do-not-send="true">touch@isi.edu</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
                <br>
                On 4/21/2017 10:26 AM, Nico Williams wrote:<br>
                &gt; "Internet time" (that which we use in [new]
                Internet protocols) should<br>
                &gt; just be TAI.  And every existing Internet protocol
                should be updated to<br>
                &gt; indicate which time is used in practice, UTC or
                TAI, regardless of what<br>
                &gt; was originally specified.<br>
              </span>I would be very glad of we defined Internet Time as
              TAI, but also expect<br>
              all protocols to understand both TAI and UTC if possible.<br>
              <span class="gmail-HOEnZb"><font color="#888888"><br>
                  Joe<br>
                </font></span></blockquote>
            <div><br>
            </div>
            <div>
              <div class="gmail_default">​To answer the issues raised:</div>
              <div class="gmail_default"><br>
              </div>
              <div class="gmail_default">1) POSIX already has this
                pretty much covered</div>
              <div class="gmail_default"><br>
              </div>
              <div class="gmail_default"><a
href="http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html"
                  moz-do-not-send="true">http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html</a>​</div>
            </div>
            <div><br>
            </div>
            <div>
              <div class="gmail_default">​<tt
                  style="color:rgb(0,0,0);background-color:rgb(204,204,255)">int
                  clock_gettime(clockid_t</tt><span
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)"> </span><i
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)">clock_id</i><tt
style="color:rgb(0,0,0);background-color:rgb(204,204,255)">, struct
                  timespec *</tt><i
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)">tp</i><tt
style="color:rgb(0,0,0);background-color:rgb(204,204,255)">);</tt>​</div>
            </div>
            <div> </div>
          </div>
          <div class="gmail_default">​So all that is required is to
            define clock identifiers for:</div>
          <div class="gmail_default"><br>
          </div>
          <div class="gmail_default">TAI (The total number of seconds
            elapsed since the start of the epoch)</div>
          <div class="gmail_default">UTC (The TAI value adjusted for UTC
            leap seconds, i.e. number of non leap second seconds since
            the start of the epoch)</div>
        </div>
      </div>
    </blockquote>
    If these aren't already included, I'm surprised (at least UTC).<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_default">PIT (The TAI value adjusted for PIT
            leap seconds)</div>
        </div>
      </div>
    </blockquote>
    <br>
    We don't need PIT.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_default">POSIX already defines constants
            for <span
              style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif">CLOCK_PROCESS_CPUTIME_ID, </span><span
style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif">CLOCK_REALTIME</span><span
style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif"> </span></div>
          <div class="gmail_default"><br>
          </div>
          <div class="gmail_default">All that is needed is to define the
            additional ones. </div>
          <br>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">
          <div class="gmail_default" style="font-size:small">​2) No I
            did not move the goalposts. My original proposal was to
            solve the needless chaos caused be the idiotic notion of
            changing the definition of time at six months notice. The
            stupidity of that notion should be apparent to all.</div>
        </div>
      </div>
    </blockquote>
    <br>
    There is no getting around the fact that the rest of the planet
    accepts leap seconds. If that's not something you want to track,
    then use TAI and be off-sync with the rest of the world when they
    use UTC.<br>
    <br>
    PIT does nothing helpful except add yet another level of indirection
    and confusion here.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_default" style="font-size:small">3) Screw
            the astronomers. Pluto is to a planet.​</div>
        </div>
      </div>
    </blockquote>
    <br>
    IMO, this issue is sufficently driven by "rough consensus and
    running code" of the entire planet right now - where all governments
    already use UTC.<br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------8431CAD1AC57A3D9BFD16F51--


From nobody Fri Apr 21 13:29:29 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBDE129B8C for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g9QseNuf43-u for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:29:26 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::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 E8CF8127B57 for <ietf@ietf.org>; Fri, 21 Apr 2017 13:29:25 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id x184so111932877oia.1 for <ietf@ietf.org>; Fri, 21 Apr 2017 13:29:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6Iq74/u51xOgBPRrxsBlybcuIJOLuf8t8H/qWA45lq0=; b=rt/ywZumMzKYgkT4onRQ4zAoAqyjWlzNOYF/jG//JvW+QO3gR2wkXrVV5+NbLKzcXR rqr1YR6RJOR4TtWQU2hfN4qDHcVGKvS+vEEjQJ3cgloABDJk3adVCXJwDsS1QDbwp2NG xQl4BBDRjnRx/l6fp4RTWL/kD3GXEDECmvcB8cjIN8Oj81cKIK/ATV4GJ5zE/OhGWKNg Vo6ZRVO8Rg2q75O+Ut1trFPxa7uJZFkLXXp+T3ZJQmMz3RzObo+zE0+HLU26MzqT00/0 XUaz/pGj6eVlrIyNzwB5DW2hke4C4BnJez6v87aS5jLowuwWHqwu5CgSSDXZ/ylYhWXd YjdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6Iq74/u51xOgBPRrxsBlybcuIJOLuf8t8H/qWA45lq0=; b=GBM5f4kBJlyy8+yqOhg/xRmXDF/kpAzFkHEnrlKcSXzGy8DBm6BjmjtgN6WjushvCd U28kZRoEtPsSUVnhgti7zov5XIQwPyMKj7JDAGDlIg8xTuAg+N3YEzUU91hhv2DreuxT 6cbsdV4Lm0iH6QK/Ct2dty+toDvWERAgblzFffQEuI1I65Pog+g49TrTVMkt6W22KS2t yZfHp+Zq2wEN+/F4+WwwmeLiO7v59/IQC0KER1SDavldvB4a8/TZIws/TFn3ydYig85E /yQAvTDUnNA7rPTtk2PS9Qg+/bri1SOPGGtlHd9LsqBvGCE6ceoAVMkfheR5tJtRwkC2 fl5Q==
X-Gm-Message-State: AN3rC/5gQn3JI5RjMuFkvhNw7jp1hnrYdG1T5ID7hx0snIimSKR6kfEy 5U7MJXWWYCE3CxfnViCzUynLTKOt7w==
X-Received: by 10.202.45.206 with SMTP id t197mr9071983oit.104.1492806565342;  Fri, 21 Apr 2017 13:29:25 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Fri, 21 Apr 2017 13:29:24 -0700 (PDT)
In-Reply-To: <ad341d37-6256-fe0b-4f01-aa349a04ef36@isi.edu>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com> <20170421172626.GG2856@localhost> <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu> <CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com> <ad341d37-6256-fe0b-4f01-aa349a04ef36@isi.edu>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Apr 2017 16:29:24 -0400
X-Google-Sender-Auth: SGffTjJ738bDI_FQwOurBjM0BLc
Message-ID: <CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com>
Subject: Re: Predictable Internet Time
To: Joe Touch <touch@isi.edu>
Cc: Nico Williams <nico@cryptonector.com>, Paul Eggert <eggert@cs.ucla.edu>,  IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=001a1137b4f80bb38f054db31d17
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aEPgs1DP9l2ZeV9kBUN62xr3R9A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 20:29:28 -0000

--001a1137b4f80bb38f054db31d17
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 21, 2017 at 2:41 PM, Joe Touch <touch@isi.edu> wrot
=E2=80=8Be=E2=80=8B

> On 4/21/2017 11:35 AM, Phillip Hallam-Baker wrote:
>
> =E2=80=8BTo answer the issues raised:
>
> 1) POSIX already has this pretty much covered
>
> http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.htm=
l
> =E2=80=8B
>
> =E2=80=8Bint clock_gettime(clockid_t *clock_id*, struct timespec **tp*);=
=E2=80=8B
>
> =E2=80=8BSo all that is required is to define clock identifiers for:
>
> TAI (The total number of seconds elapsed since the start of the epoch)
> UTC (The TAI value adjusted for UTC leap seconds, i.e. number of non leap
> second seconds since the start of the epoch)
>
> If these aren't already included, I'm surprised (at least UTC).
>

=E2=80=8BWell I linked to the spec so you could have looked and checked. Yo=
u are
wrong. The spec is ambiguous as to whether the value is UTC or not, hence
the need to be explicit. =E2=80=8B



>
> PIT (The TAI value adjusted for PIT leap seconds)
>
>
> We don't need PIT.
>
> =E2=80=8BThat is your opinion, like the astronomers, you might just be wr=
ong about
the requirements.

I can see the benefit of an IoT where time is absolutely predictable even
if it may be out of sync with UT by a few seconds.=E2=80=8B You might not b=
ut I
doubt you have the range of experience in realtime and process control that
I have.

=E2=80=8BUnless a device actually deals in time, PIT is going to be just fi=
ne for
status messages and logs. The advantage over UTC being that you know
exactly what the device is trying to do which you don't have with UTC. You
don't know whether the device is keeping UTC or some heuristic.

TAI would be a possibility if we counted in seconds which we don't. We
track time by date and need to compare. The difference between UTC and TAI
is half a minute which is just too much to be viable.=E2=80=8B


POSIX already defines constants for CLOCK_PROCESS_CPUTIME_ID, CLOCK_REALTIM=
E
>
>
> All that is needed is to define the additional ones.
>
>
> =E2=80=8B2) No I did not move the goalposts. My original proposal was to =
solve the
> needless chaos caused be the idiotic notion of changing the definition of
> time at six months notice. The stupidity of that notion should be apparen=
t
> to all.
>
>
> There is no getting around the fact that the rest of the planet accepts
> leap seconds. If that's not something you want to track, then use TAI and
> be off-sync with the rest of the world when they use UTC.
>

=E2=80=8BSince the standard was only created in our lifetimes, it is hardly
immutable and fixed for all eternity.

The reason UTC is the standard is because it is what the ITU decided to use
and the broadcasters synchronize everything. That can change.

--001a1137b4f80bb38f054db31d17
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Ap=
r 21, 2017 at 2:41 PM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:to=
uch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> wrot<div class=
=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8Be=E2=
=80=8B</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D=
"#FFFFFF"><span class=3D"">
    <div class=3D"m_-6334995718116752182moz-cite-prefix">On 4/21/2017 11:35=
 AM, Phillip
      Hallam-Baker wrote:</div><blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra"><div class=3D"gmail_quote">
            <div>
              <div>=E2=80=8BTo answer the issues raised:</div>
              <div><br>
              </div>
              <div>1) POSIX already has this
                pretty much covered</div>
              <div><br>
              </div>
              <div><a href=3D"http://pubs.opengroup.org/onlinepubs/00969539=
9/functions/clock_getres.html" target=3D"_blank">http://pubs.opengroup.org/=
<wbr>onlinepubs/009695399/<wbr>functions/clock_getres.html</a>=E2=80=8B</di=
v>
            </div>
            <div><br>
            </div>
            <div>
              <div>=E2=80=8B<tt style=3D"color:rgb(0,0,0);background-color:=
rgb(204,204,255)">int
                  clock_gettime(clockid_t</tt><span style=3D"color:rgb(0,0,=
0);font-family:monospace;background-color:rgb(204,204,255)">=C2=A0</span><i=
 style=3D"color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,2=
04,255)">clock_<wbr>id</i><tt style=3D"color:rgb(0,0,0);background-color:rg=
b(204,204,255)">, struct
                  timespec *</tt><i style=3D"color:rgb(0,0,0);font-family:m=
onospace;background-color:rgb(204,204,255)">tp</i><tt style=3D"color:rgb(0,=
0,0);background-color:rgb(204,204,255)">);</tt>=E2=80=8B</div>
            </div>
            <div>=C2=A0</div>
          </div>
          <div>=E2=80=8BSo all that is required is to
            define clock identifiers for:</div>
          <div><br>
          </div>
          <div>TAI (The total number of seconds
            elapsed since the start of the epoch)</div>
          <div>UTC (The TAI value adjusted for UTC
            leap seconds, i.e. number of non leap second seconds since
            the start of the epoch)</div>
        </div>
      </div>
    </blockquote></span>
    If these aren&#39;t already included, I&#39;m surprised (at least UTC).=
</div></blockquote><div><br></div><div><div class=3D"gmail_default" style=
=3D"font-size:small">=E2=80=8BWell I linked to the spec so you could have l=
ooked and checked. You are wrong. The spec is ambiguous as to whether the v=
alue is UTC or not, hence the need to be explicit. =E2=80=8B</div></div><di=
v><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#0=
00000" bgcolor=3D"#FFFFFF"><span class=3D""><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div>PIT (The TAI value adjusted for PIT
            leap seconds)</div>
        </div>
      </div>
    </blockquote>
    <br></span>
    We don&#39;t need PIT.<span class=3D""><br><blockquote type=3D"cite"><d=
iv dir=3D"ltr"><div class=3D"gmail_extra"><div></div></div></div></blockquo=
te></span></div></blockquote><div><div class=3D"gmail_default" style=3D"fon=
t-size:small">=E2=80=8BThat is your opinion, like the astronomers, you migh=
t just be wrong about the requirements.</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">I can see the benefit of an IoT where time is absolutely pre=
dictable even if it may be out of sync with UT by a few seconds.=E2=80=8B Y=
ou might not but I doubt you have the range of experience in realtime and p=
rocess control that I have.</div></div><div><br></div><div><div class=3D"gm=
ail_default" style=3D"font-size:small">=E2=80=8BUnless a device actually de=
als in time, PIT is going to be just fine for status messages and logs. The=
 advantage over UTC being that you know exactly what the device is trying t=
o do which you don&#39;t have with UTC. You don&#39;t know whether the devi=
ce is keeping UTC or some heuristic.</div><div class=3D"gmail_default" styl=
e=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-=
size:small">TAI would be a possibility if we counted in seconds which we do=
n&#39;t. We track time by date and need to compare. The difference between =
UTC and TAI is half a minute which is just too much to be viable.=E2=80=8B<=
/div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#=
000000" bgcolor=3D"#FFFFFF"><span class=3D""><blockquote type=3D"cite"><div=
 dir=3D"ltr"><div class=3D"gmail_extra"><div>POSIX already defines constant=
s
            for=C2=A0<span style=3D"color:rgb(0,0,0);font-family:verdana,ar=
ial,helvetica,sans-serif">CLOCK_PROCESS_CPUTIME_ID,=C2=A0</span><span style=
=3D"color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif"><wbr>C=
LOCK_REALTIME</span><span style=3D"color:rgb(0,0,0);font-family:verdana,ari=
al,helvetica,sans-serif">=C2=A0</span></div>
          <div><br>
          </div>
          <div>All that is needed is to define the
            additional ones.=C2=A0</div>
          <br>
        </div>
        <div class=3D"gmail_extra"><br>
        </div>
        <div class=3D"gmail_extra">
          <div style=3D"font-size:small">=E2=80=8B2) No I
            did not move the goalposts. My original proposal was to
            solve the needless chaos caused be the idiotic notion of
            changing the definition of time at six months notice. The
            stupidity of that notion should be apparent to all.</div>
        </div>
      </div>
    </blockquote>
    <br></span>
    There is no getting around the fact that the rest of the planet
    accepts leap seconds. If that&#39;s not something you want to track,
    then use TAI and be off-sync with the rest of the world when they
    use UTC.<br></div></blockquote><div><br></div><div><div class=3D"gmail_=
default" style=3D"font-size:small">=E2=80=8BSince the standard was only cre=
ated in our lifetimes, it is hardly immutable and fixed for all eternity.</=
div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div c=
lass=3D"gmail_default" style=3D"font-size:small">The reason UTC is the stan=
dard is because it is what the ITU decided to use and the broadcasters sync=
hronize everything. That can change.</div></div></div></div></div>

--001a1137b4f80bb38f054db31d17--


From nobody Fri Apr 21 13:31:25 2017
Return-Path: <tobias@inet.tu-berlin.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9ECE128768; Fri, 21 Apr 2017 13:31:24 -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, RP_MATCHES_RCVD=-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 FG2U8aVOZ5ni; Fri, 21 Apr 2017 13:31:22 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail1.net.t-labs.tu-berlin.de [IPv6:2001:638:809:ff11:130:149:220:242]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0B3127B57; Fri, 21 Apr 2017 13:31:22 -0700 (PDT)
Received: from mail.inet.tu-berlin.de (firewall.seclab.cs.ucsb.edu [128.111.48.252]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 4568873; Fri, 21 Apr 2017 22:31:18 +0200 (CEST)
Date: Fri, 21 Apr 2017 13:31:15 -0700
From: Tobias Fiebig <tobias@inet.tu-berlin.de>
To: Jared Mauch <jared@puck.nether.net>
Cc: Khaled Omar <eng.khaled.omar@hotmail.com>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Subject: Re: Google Statistics for IPv6 adoption.
Message-ID: <20170421203114.GA19501@mail.inet.tu-berlin.de>
References: <AM4PR0401MB22419992B651EBBA3FC9B6FEBD040@AM4PR0401MB2241.eurprd04.prod.outlook.com> <CAL9jLaa+zTSj9g1QMQAEPDiVqEmGG3OtChuu5NvA3feTX2mrjw@mail.gmail.com> <AM4PR0401MB2241F94B536F114D83190A14BD040@AM4PR0401MB2241.eurprd04.prod.outlook.com> <40315FF7-DD5D-4A3D-BCA5-C6D4C17CE8A9@puck.nether.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <40315FF7-DD5D-4A3D-BCA5-C6D4C17CE8A9@puck.nether.net>
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IM_cmmIyC6mdafv2ztrva3lT4Q8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 20:31:25 -0000

Heho, On Sat, Apr 15, 2017 at 02:47:20PM -0400, Jared Mauch wrote:
> ... 
>
> Using one datapoint, an ad network (google) is helpful to
> understand what browser users might look like but a set top box
> without a browser may move significantly more bits and not be
> apparent at all in the IPv6 stats at google. 

I would like to chim in on that point. Actually google has a strong
bias for IPv6 adoption in devices speaking to google. While natural,
this really skews the numbers: The BigN (Google (YouTube), Facebook,
Akamai, Cloudflare, Netflix etc.) account for a major part of
overall traffic, especially in access networks. 

Incidentily, most of these orgs have deployed v6 on the server side.
Hence, as soon as an access network rolls out v6, the traffic share
of v6 skyrockets, as a major portion of the remotes causing most
traffic well... support v6.

However, this observation does not hold for the heavy tail of the
Internet. Actually, I am currently investigating other datasources,
that are not biased towards end-users and "BigN" content providers;
There, v6 adoption for the heavy tail actually ranges more in the
field of 1%...

With best Regards,
Tobias Fiebig

-- 
Tobias Fiebig                      building MAR, 4th floor, room 4.003
Fachgebiet INET - Sekr. MAR 4-4        phone: +49 162 243 205 2
Technische Universität Berlin         gpg-fp: 21A9 91EB 4971 ED48 001E
Marchstrasse 23 - 10587 Berlin                FBBC B6AF 3CD8 59A2 795B


From nobody Fri Apr 21 13:45:18 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF371129AE9 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:45:15 -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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 INSduUDvyoXf for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:45:13 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 E88CA129557 for <ietf@ietf.org>; Fri, 21 Apr 2017 13:45:13 -0700 (PDT)
Received: from [128.9.184.96] ([128.9.184.96]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3LKiIXD009298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Apr 2017 13:44:20 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Nico Williams <nico@cryptonector.com>, Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
References: <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com> <20170421172626.GG2856@localhost> <b0f0362a-cb46-79b6-b22b-ab2baaa69327@isi.edu> <CAMm+Lwjnrj43sN6rU-6Zf_PJAfyobeLHUtsh63G7sW0-5LH3tQ@mail.gmail.com> <ad341d37-6256-fe0b-4f01-aa349a04ef36@isi.edu> <CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <2de9d2d3-7c8a-a3e9-8d24-d0336262c8d5@isi.edu>
Date: Fri, 21 Apr 2017 13:44:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1A907F02F2FD8BF8CC829696"
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tb11y3X3Ni92XcD0C6nCEyFUqDE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 20:45:16 -0000

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



On 4/21/2017 1:29 PM, Phillip Hallam-Baker wrote:
>
>
> On Fri, Apr 21, 2017 at 2:41 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrot
> ​e​
>
>     On 4/21/2017 11:35 AM, Phillip Hallam-Baker wrote:
>>     ​To answer the issues raised:
>>
>>     1) POSIX already has this pretty much covered
>>
>>     http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html
>>     <http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html>​
>>
>>     ​int clock_gettime(clockid_t /clock_id/, struct timespec */tp/);​
>>      
>>     ​So all that is required is to define clock identifiers for:
>>
>>     TAI (The total number of seconds elapsed since the start of the
>>     epoch)
>>     UTC (The TAI value adjusted for UTC leap seconds, i.e. number of
>>     non leap second seconds since the start of the epoch)
>     If these aren't already included, I'm surprised (at least UTC).
>
>
> ​Well I linked to the spec so you could have looked and checked.
You linked to an outdated 2004 spec.
The current spec is here: http://pubs.opengroup.org/onlinepubs/9699919799/

> You are wrong.
I can't be wrong. I said "IF", and you can't claim I'm not surprised
that these aren't already included.

> The spec is ambiguous as to whether the value is UTC or not, hence the
> need to be explicit. ​
While I agree, that is an issue for POSIX.

>  
>
>
>>     PIT (The TAI value adjusted for PIT leap seconds)
>
>     We don't need PIT.
>
> ​That is your opinion, like the astronomers, you might just be wrong
> about the requirements.
>
> I can see the benefit of an IoT where time is absolutely predictable
> even if it may be out of sync with UT by a few seconds.​
For every reason you want PIT, we can already use TAI.

> You might not but I doubt you have the range of experience in realtime
> and process control that I have.
>
> ​Unless a device actually deals in time, PIT is going to be just fine
> for status messages and logs. The advantage over UTC being that you
> know exactly what the device is trying to do which you don't have with
> UTC. You don't know whether the device is keeping UTC or some heuristic.
>
> TAI would be a possibility if we counted in seconds which we don't. We
> track time by date and need to compare. The difference between UTC and
> TAI is half a minute which is just too much to be viable.​

Any difference between the current date and UTC renders everything that
interacts with the real world incorrect.

>
>>     POSIX already defines constants
>>     for CLOCK_PROCESS_CPUTIME_ID, CLOCK_REALTIME 
>>
>>     All that is needed is to define the additional ones. 
>>
>>
>>     ​2) No I did not move the goalposts. My original proposal was to
>>     solve the needless chaos caused be the idiotic notion of changing
>>     the definition of time at six months notice. The stupidity of
>>     that notion should be apparent to all.
>
>     There is no getting around the fact that the rest of the planet
>     accepts leap seconds. If that's not something you want to track,
>     then use TAI and be off-sync with the rest of the world when they
>     use UTC.
>
>
> ​Since the standard was only created in our lifetimes, it is hardly
> immutable and fixed for all eternity.
That's true, but the organizations that pick times scales are not the
IETF. We use standards others manage in that regard, exactly because
we're not special - either time is largely local (in which case it
doesn't matter) or you need to interact with the rest of the world,
which agreed on UTC.

> The reason UTC is the standard is because it is what the ITU decided
> to use and the broadcasters synchronize everything. That can change.

OK, then let us know when any government picks PIT.

Until then, though, the Internet should not be picking something
different when there are already current standards that are sufficient.

Joe


--------------1A907F02F2FD8BF8CC829696
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 4/21/2017 1:29 PM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_default" style="font-size:small"><br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Apr 21, 2017 at 2:41 PM, Joe
            Touch <span dir="ltr">&lt;<a href="mailto:touch@isi.edu"
                target="_blank" moz-do-not-send="true">touch@isi.edu</a>&gt;</span>
            wrot
            <div class="gmail_default"
              style="font-size:small;display:inline">​e​</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"><span class="">
                  <div class="m_-6334995718116752182moz-cite-prefix">On
                    4/21/2017 11:35 AM, Phillip Hallam-Baker wrote:</div>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div>
                            <div>​To answer the issues raised:</div>
                            <div><br>
                            </div>
                            <div>1) POSIX already has this pretty much
                              covered</div>
                            <div><br>
                            </div>
                            <div><a
href="http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_getres.html"
                                target="_blank" moz-do-not-send="true">http://pubs.opengroup.org/<wbr>onlinepubs/009695399/<wbr>functions/clock_getres.html</a>​</div>
                          </div>
                          <div><br>
                          </div>
                          <div>
                            <div>​<tt
                                style="color:rgb(0,0,0);background-color:rgb(204,204,255)">int
                                clock_gettime(clockid_t</tt><span
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)"> </span><i
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)">clock_<wbr>id</i><tt
style="color:rgb(0,0,0);background-color:rgb(204,204,255)">, struct
                                timespec *</tt><i
style="color:rgb(0,0,0);font-family:monospace;background-color:rgb(204,204,255)">tp</i><tt
style="color:rgb(0,0,0);background-color:rgb(204,204,255)">);</tt>​</div>
                          </div>
                          <div> </div>
                        </div>
                        <div>​So all that is required is to define clock
                          identifiers for:</div>
                        <div><br>
                        </div>
                        <div>TAI (The total number of seconds elapsed
                          since the start of the epoch)</div>
                        <div>UTC (The TAI value adjusted for UTC leap
                          seconds, i.e. number of non leap second
                          seconds since the start of the epoch)</div>
                      </div>
                    </div>
                  </blockquote>
                </span> If these aren't already included, I'm surprised
                (at least UTC).</div>
            </blockquote>
            <div><br>
            </div>
            <div>
              <div class="gmail_default" style="font-size:small">​Well I
                linked to the spec so you could have looked and checked.
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    You linked to an outdated 2004 spec.<br>
    The current spec is here:
    <a class="moz-txt-link-freetext" href="http://pubs.opengroup.org/onlinepubs/9699919799/">http://pubs.opengroup.org/onlinepubs/9699919799/</a><br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>
              <div class="gmail_default" style="font-size:small">You are
                wrong. </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    I can't be wrong. I said "IF", and you can't claim I'm not surprised
    that these aren't already included.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>
              <div class="gmail_default" style="font-size:small">The
                spec is ambiguous as to whether the value is UTC or not,
                hence the need to be explicit. ​</div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    While I agree, that is an issue for POSIX.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"><span class=""><br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div>PIT (The TAI value adjusted for PIT leap
                          seconds)</div>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </span> We don't need PIT.<span class=""><br>
                </span></div>
            </blockquote>
            <div>
              <div class="gmail_default" style="font-size:small">​That
                is your opinion, like the astronomers, you might just be
                wrong about the requirements.</div>
              <div class="gmail_default" style="font-size:small"><br>
              </div>
              <div class="gmail_default" style="font-size:small">I can
                see the benefit of an IoT where time is absolutely
                predictable even if it may be out of sync with UT by a
                few seconds.​ </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    For every reason you want PIT, we can already use TAI.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>
              <div class="gmail_default" style="font-size:small">You
                might not but I doubt you have the range of experience
                in realtime and process control that I have.</div>
            </div>
            <div><br>
            </div>
            <div>
              <div class="gmail_default" style="font-size:small">​Unless
                a device actually deals in time, PIT is going to be just
                fine for status messages and logs. The advantage over
                UTC being that you know exactly what the device is
                trying to do which you don't have with UTC. You don't
                know whether the device is keeping UTC or some
                heuristic.</div>
              <div class="gmail_default" style="font-size:small"><br>
              </div>
              <div class="gmail_default" style="font-size:small">TAI
                would be a possibility if we counted in seconds which we
                don't. We track time by date and need to compare. The
                difference between UTC and TAI is half a minute which is
                just too much to be viable.​</div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Any difference between the current date and UTC renders everything
    that interacts with the real world incorrect.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"><span class="">
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div>POSIX already defines constants for <span
                            style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif">CLOCK_PROCESS_CPUTIME_ID, </span><span
style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif"><wbr>CLOCK_REALTIME</span><span
style="color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif"> </span></div>
                        <div><br>
                        </div>
                        <div>All that is needed is to define the
                          additional ones. </div>
                        <br>
                      </div>
                      <div class="gmail_extra"><br>
                      </div>
                      <div class="gmail_extra">
                        <div style="font-size:small">​2) No I did not
                          move the goalposts. My original proposal was
                          to solve the needless chaos caused be the
                          idiotic notion of changing the definition of
                          time at six months notice. The stupidity of
                          that notion should be apparent to all.</div>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </span> There is no getting around the fact that the
                rest of the planet accepts leap seconds. If that's not
                something you want to track, then use TAI and be
                off-sync with the rest of the world when they use UTC.<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>
              <div class="gmail_default" style="font-size:small">​Since
                the standard was only created in our lifetimes, it is
                hardly immutable and fixed for all eternity.</div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    That's true, but the organizations that pick times scales are not
    the IETF. We use standards others manage in that regard, exactly
    because we're not special - either time is largely local (in which
    case it doesn't matter) or you need to interact with the rest of the
    world, which agreed on UTC.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAMm+Lwg+Q3eKpHNnfCaff1entXwYCNLjk-OR4LfQ3DFY4Fdywg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>
              <div class="gmail_default" style="font-size:small">The
                reason UTC is the standard is because it is what the ITU
                decided to use and the broadcasters synchronize
                everything. That can change.</div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    OK, then let us know when any government picks PIT.<br>
    <br>
    Until then, though, the Internet should not be picking something
    different when there are already current standards that are
    sufficient.<br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------1A907F02F2FD8BF8CC829696--


From nobody Fri Apr 21 13:50:04 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A750129557 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level: 
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=abh9MUxl; dkim=pass (1536-bit key) header.d=taugh.com header.b=NneWgz6Y
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 AI8oluwz7JnI for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 13:50:00 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BBA2129463 for <ietf@ietf.org>; Fri, 21 Apr 2017 13:50:00 -0700 (PDT)
Received: (qmail 58209 invoked from network); 21 Apr 2017 20:49:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e35f.58fa7076.k1704; bh=Dp9/VD/g5LzB8fjxp2vrKWQToUivHZwiDkrQKLYq9IE=; b=abh9MUxlTliNldZ8Z2hg3ad2oaqHhCNWbf/Vplr7vinCR1UKRqUOEXmznyGaxHSAlRojUbTnaD7rqf1hV/buV2Emn8+0XP/yvWoKsTimOPg1hjweYhWele7YjKlBrRZfjfLiF6KrVJEHY2Fgvv4Q9ucPoiDm1zJq91ZcjiQhLYWBq7+NgyACrB6xQK78tYQD+Ie5FSza4kzkfP6EbxtgUALagDTBQc057npuYWGCN5geXor/SAe4SC10rIMyIVYy
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e35f.58fa7076.k1704; bh=Dp9/VD/g5LzB8fjxp2vrKWQToUivHZwiDkrQKLYq9IE=; b=NneWgz6YC+u9pM4UflmvNeetQpihUUpskkqhtKVAwS2EBle5Ept7Wr46KSn/gIsyTTQFDLSFUQzVGBKwDC4AOQAQp5bzi82Sf2U9oJYs9kSZ61ENE92NBTC/ex+xLpkvFI6yAHejB/1eK5TMuiD/W8dFlFiuCKDO9gLhQl6vw/wGlZGs0kAOqeuE940/Z/FNPk6uUemXGXYCIN9xM1sxZkpUyff3tYdxLItyXXkQ3P6OnD0bruJTx0cEE4W4Jokr
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 21 Apr 2017 20:49:58 -0000
Date: 21 Apr 2017 16:49:58 -0400
Message-ID: <alpine.OSX.2.20.1704211647470.55442@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <CAMm+LwivmUDD8Fjihiw7moFFphfL6RcT_7EFOPh7gDhvgT7M6A@mail.gmail.com>
References: <FC831208-97A3-4F1B-A37C-F8646C3FB208@gmail.com> <20170420205434.24400.qmail@ary.lan> <CAAFsWK1FtqM2GqTkCWzgm-L87KoXGFW+yorRF-t===MycjR1Ow@mail.gmail.com> <CAMm+LwivmUDD8Fjihiw7moFFphfL6RcT_7EFOPh7gDhvgT7M6A@mail.gmail.com>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2BNC4N3IHv4TpYl0hbioLQQkbTg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 20:50:02 -0000

> On Fri, Apr 21, 2017 at 1:00 PM, Wei Chuang <weihaw@google.com> wrote:
>
>> I just wanted to second the draft-bhjl-x509-srv approach as preferable as

On Fri, 21 Apr 2017, Phillip Hallam-Baker wrote:
> Again, how does the draft advance on the existing RFC?
> https://tools.ietf.org/html/rfc4386

I don't see what the connection is.  RFC 4386 tells you how to find an 
LDAP or OCSP server.  This is a profile of RFC 4387, which tells you how 
to find a key server for S/MIME and PGP keys, how to retrieve keys by 
e-mail address from it, and optionally how to check whether a domain has 
signed the keys it returns.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Fri Apr 21 14:08:00 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6F1129479; Fri, 21 Apr 2017 14:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, 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 ahQJJ6NZu6_S; Fri, 21 Apr 2017 14:07:57 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8C25128B44; Fri, 21 Apr 2017 14:07:56 -0700 (PDT)
Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 30195279D8E; Sat, 22 Apr 2017 06:07:54 +0900 (JST)
Received: by mail-oi0-f48.google.com with SMTP id x184so112867488oia.1; Fri, 21 Apr 2017 14:07:54 -0700 (PDT)
X-Gm-Message-State: AN3rC/6vOngQAXDkGNCJhPiowtR0CAmuNZcCGZ/dXd6RBnVt/7rUy+YN DHiFeUG4clDLVb8RwnaykgToU2grPw==
X-Received: by 10.157.40.87 with SMTP id h23mr9949234otd.274.1492808872850; Fri, 21 Apr 2017 14:07:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Fri, 21 Apr 2017 14:07:52 -0700 (PDT)
In-Reply-To: <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Fri, 21 Apr 2017 14:07:52 -0700
X-Gmail-Original-Message-ID: <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com>
Message-ID: <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com>
Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Brian Raymor <Brian.Raymor@microsoft.com>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11396afc957e3a054db3a6cc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DwTQYlYyexE-on3lCaGgTdnoYwQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 21:07:59 -0000

--001a11396afc957e3a054db3a6cc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Brian,

Just in case,
Reliable transports only provide reliability at transport level. It doesn't
provide reliability in application protocol level.

RFC7252 has reliability mechanisms in it since it uses UDP. This means it
has abilities to check both transport and app level reliability.
This draft only provides transport level reliability and apps will need to
detect app protocol failure by themselves.
This means 7252 and this draft are not totally equivalent from the
viewpoint of applications.

I am not saying this is wrong or bad, but I believe app developer should
aware this point.
--
Yoshi

On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <Brian.Raymor@microsoft.com>
wrote:

> Hi Yoshi,
>
>
>
> > OK. I also think we should state that the protocol should notify the
> failure events to applications.
>
> > Since errors can happen not only in TCP, but also TLS and websocket
> level, mentioning only TCP close or reset might not
>
> > be enough.
>
>
>
> After reviewing with the authors, an additional clarification was appende=
d
> to 3.4 Connection Health - https://github.com/core-wg/
> coap-tcp-tls/pull/140/files
>
>
>
> The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -
> https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is that
> RFC6455 covers the WebSocket case and does not need to be repeated here.
>
>
>
> > When we use 7252, I think applications basically don't need to implemen=
t
> timeouts or retry mechanisms as the protocol
>
> > provides such things.
>
>
>
> RFC7252 provides timeouts and retries because it's implementing a TCP-lik=
e
> reliability mechanism over UDP - https://tools.ietf.org/html/
> rfc7252#section-2.1
>
>
>
> > However, when we use this one, it seems applications will need to have
> such mechanisms. Isn't it a bit confusing? I am thinking that
>
> > there need to be some guidance here.
>
> > BTW, PONG is one example.
>
>
>
> For coap-tcp-tls, there are multiple early implementations. This has neve=
r
> been reported as a source of confusion.
>
>
>
> >> My sense is that we should treat this as an update to RFC7959 based on
> the original language:
>
> > I don't have a strong opinion here. Updating 7959 is fine for me if it'=
s
> clearer to CoAP people.
>
>
>
> I've merged the change - https://github.com/core-wg/
> coap-tcp-tls/pull/138/files
>
>
>
> Thanks again for helping us to improve the quality of the draft,
>
>
>
> =E2=80=A6Brian
>

--001a11396afc957e3a054db3a6cc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Brian,<div><br></div><div>Just in case,</div><div>Relia=
ble transports only provide reliability at transport level. It doesn&#39;t =
provide reliability in application protocol level.=C2=A0</div><div><br></di=
v><div>RFC7252 has reliability mechanisms in it since it uses UDP. This mea=
ns it has abilities to check both transport and app level reliability.</div=
><div>This draft only provides transport level reliability and apps will ne=
ed to detect app protocol failure by themselves.=C2=A0</div><div>This means=
 7252 and this draft are not totally equivalent from the viewpoint of appli=
cations.=C2=A0</div><div><br></div><div>I am not saying this is wrong or ba=
d, but I believe app developer should aware this point.</div><div>--<br></d=
iv><div>Yoshi</div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <span dir=3D"ltr">&lt=
;<a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian.Raym=
or@microsoft.com</a>&gt;</span> wrote:<br><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 lang=3D"EN-US">
<div class=3D"gmail-m_-3058448815637676647WordSection1">
<div>
<div>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">Hi Yoshi,<u></u><u></=
u></p><span class=3D"gmail-">
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; OK. I also think=
 we should state that the protocol should notify the failure events to appl=
ications.=C2=A0<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; Since errors can=
 happen not only in TCP, but also TLS and websocket level, mentioning only =
TCP close or reset might not
<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; be enough.<u></u=
><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">=C2=A0<u></u><u></u><=
/p>
</span><p class=3D"gmail-m_-3058448815637676647MsoPlainText">After reviewin=
g with the authors, an additional clarification was appended to 3.4 Connect=
ion Health -
<a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files" target=
=3D"_blank">https://github.com/core-wg/<wbr>coap-tcp-tls/pull/140/files</a>=
<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">The opinion of the au=
thors (and Gengyu WEI=E2=80=99s recent response -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html=
" target=3D"_blank">https://www.ietf.org/mail-<wbr>archive/web/core/current=
/<wbr>msg08622.html</a>) is that RFC6455 covers the WebSocket case and does=
 not need to be repeated here.<u></u><u></u></p><span class=3D"gmail-">
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; When we use 7252=
, I think applications basically don&#39;t need to implement timeouts or re=
try mechanisms as the protocol<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; provides such th=
ings. <u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
</span><p class=3D"gmail-m_-3058448815637676647MsoPlainText">RFC7252 provid=
es timeouts and retries because it&#39;s implementing a TCP-like reliabilit=
y mechanism over UDP -
<a href=3D"https://tools.ietf.org/html/rfc7252#section-2.1" target=3D"_blan=
k">https://tools.ietf.org/html/<wbr>rfc7252#section-2.1</a><u></u><u></u></=
p><span class=3D"gmail-">
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; However, when we=
 use this one, it seems applications will need to have such mechanisms. Isn=
&#39;t it a bit confusing? I am thinking that<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; there need to be=
 some guidance here.<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; BTW, PONG is one=
 example.<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
</span><p class=3D"gmail-m_-3058448815637676647MsoPlainText">For coap-tcp-t=
ls, there are multiple early implementations. This has never been reported =
as a source of confusion.
<u></u><u></u></p><span class=3D"gmail-">
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt;&gt; My sense is =
that we should treat this as an update to RFC7959 based on the original lan=
guage:<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText">&gt; I don&#39;t have=
 a strong opinion here. Updating 7959 is fine for me if it&#39;s clearer to=
 CoAP people.<u></u><u></u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
</span><p class=3D"gmail-m_-3058448815637676647MsoPlainText">I&#39;ve merge=
d the change - <a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/138/=
files" target=3D"_blank">
https://github.com/core-wg/<wbr>coap-tcp-tls/pull/138/files</a><u></u><u></=
u></p>
<p class=3D"gmail-m_-3058448815637676647MsoPlainText"><u></u>=C2=A0<u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif">Thanks again for helping us to improve the quality of the draft,<=
span class=3D"gmail-HOEnZb"><font color=3D"#888888"><u></u><u></u></font></=
span></span></p><span class=3D"gmail-HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif">=E2=80=A6Brian<u></u><u></u></span></p>
</font></span></div>
</div>
</div>
</div>

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

--001a11396afc957e3a054db3a6cc--


From nobody Fri Apr 21 14:58:36 2017
Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3AC0128896; Fri, 21 Apr 2017 14:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=microsoft.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 v8M7J2GgLu_N; Fri, 21 Apr 2017 14:58:23 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0137.outbound.protection.outlook.com [104.47.38.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 786AC127419; Fri, 21 Apr 2017 14:58:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RCNcGBcpFMFACwUzgRWino9j/YiAC0OIqEzpt7Mk0q8=; b=QlBZJCF597JET/z8/JXFo4r92pAerWliExHW561i1rm6G+hOZCSJeB/ltKB8tpykewXM1KZUiwJjh+oiv273hnehCpsQUPnfPAPzFR3sPW+7Acr7fKqyXwh40MOBm3HiCuxU6OPWyTmVrPXk5C/a0mP0ZZvL01xwApOvKnkv/CA=
Received: from BY2PR21MB0084.namprd21.prod.outlook.com (10.162.78.141) by BY2PR21MB0083.namprd21.prod.outlook.com (10.162.78.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.1; Fri, 21 Apr 2017 21:57:39 +0000
Received: from BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) by BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) with mapi id 15.01.1061.003; Fri, 21 Apr 2017 21:57:39 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
CC: "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Topic: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsOTWicthTbHq+0Cl6wEpb6SnVKHOtjQAgADZuACAAKJUUIAAMqMAgAADmmA=
Date: Fri, 21 Apr 2017 21:57:38 +0000
Message-ID: <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com>
In-Reply-To: <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.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=Brian.Raymor@microsoft.com; 
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR21MB0083; 7:SUyyCBTp6tIPDmMkBxW3jAig8ww5pYu2G79NPVVNK1yBkyOowbioy+N+Xf618XodNeWh5DuwyqEAztWNW+TqU+98EWQvilEXXUskZdQych/mntocKRsqi/3jbXi/mYQAYub6rUWyAtmwS2i2vwle8KVWu9rdph0gGWD1tfYyqYTYtggO4NtncBGx5YX0YQECDeeSNIuKHg8zQ0Q/uMvZBjF+uKg6/kDbWzM4I02co41tq9pgyVRf+pDoKw672+xVXFf2MyGqpnpcEP+EXTYeR2LYZTJQEKwMM1EWsj+hCgw1dIF2+pSoIpjGy+zraJSF/FPaho6wFZ+uO4NgyDdmmCFAg4Cts9m1WFVqqi8tUUs=
x-ms-office365-filtering-correlation-id: 76a0f5b2-64ee-453c-8300-08d489016d76
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR21MB0083; 
x-forefront-prvs: 02843AA9E0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(43784003)(51444003)(377454003)(199003)(189002)(24454002)(3660700001)(230783001)(10290500002)(6436002)(189998001)(86612001)(5005710100001)(7696004)(105586002)(6506006)(6246003)(77096006)(4326008)(74316002)(86362001)(3280700002)(5660300001)(110136004)(7736002)(76176999)(54356999)(236005)(50986999)(101416001)(33656002)(7906003)(8990500004)(2900100001)(9686003)(97736004)(229853002)(606005)(55016002)(19609705001)(54906002)(99286003)(8676002)(6916009)(25786009)(68736007)(93886004)(790700001)(10090500001)(6116002)(102836003)(3846002)(81156014)(8936002)(54896002)(6306002)(2950100002)(66066001)(53546009)(122556002)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR21MB0083; H:BY2PR21MB0084.namprd21.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR21MB008453149ADC1A998FEA56D3831A0BY2PR21MB0084namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2017 21:57:38.8246 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR21MB0083
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1_OnnbVSg_JQUFlLyIye72m6OB0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 21:58:27 -0000

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

SSB0aGluayB0aGF0IEkgdW5kZXJzdGFuZCB5b3VyIHBlcmNlcHRpb25zIGJldHRlci4gUHJpb3Ig
dG8gYWRvcHRpb24gb2YgY29hcC10Y3AtdGxzIGFuZCBiZWZvcmUgSSB3YXMgYWN0aXZlIGluIHRo
ZSBXRywgSSByZWNhbGwgZGlzY3Vzc2lvbnMgcmVsYXRlZCB0byB0aGUgY29uZnVzaW9uIG92ZXIg
YXBwbGljYXRpb24gdnMgdHJhbnNwb3J0IHJlbGlhYmlsaXR5IGluIENvQVAgZXNwZWNpYWxseSBh
cyByZWxhdGVkIHRvIENPTiBhbmQgTk9OLiBXaGF0IHdhcyBpbnRlbmRlZD8NCg0KVGltIENhcmV5
IG91dGxpbmVkIHNvbWUgY29uY2VybnMgaW46DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtY2FyZXktY29yZS1zdGQtbXNnLXZzLXRyYW5zLWFkYXB0LTAwI3NlY3Rpb24tMg0KDQpU
aGlzIHRvcGljIHdhcyBwcmVzZW50ZWQgaW4gZGV0YWlsIGF0IElFVEYgOTMgLSBodHRwczovL3d3
dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy85My9zbGlkZXMvc2xpZGVzLTkzLWNvcmUtMC5wZGYgLSBz
dGFydGluZyBvbiBzbGlkZSAyMy4NCg0KQW5kIGluIGEgcmVsYXRlZCB0aHJlYWQgb24gdGhlIG1h
aWxpbmcgbGlzdCBiYWNrIGluIDIwMTUgLSBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hp
dmUvd2ViL2NvcmUvY3VycmVudC9tc2cwNjI4MC5odG1sIC0gQ2Fyc3RlbiByZXNwb25kZWQ6DQoN
Cj4gSW4gYW55IGNhc2UsIENPTiBhbmQgTk9OIGFyZSBhYm91dCBtZXNzYWdlIGxheWVyIHNlbWFu
dGljcywgbm90IGFib3V0IGFwcGxpY2F0aW9uIHNlbWFudGljcw0KPiAtLSB5b3UgZ2F2ZSB0aGVt
IGEgbWVhbmluZyB0aGV5IGRvbid0IGhhdmUuDQoNCkJ5IElFVEYgOTQsIHRoZSBhdXRob3JzIHdl
cmUgcmVwb3J0aW5nIOKAkyDigJxNb3N0IG9mIHRoZSBDb25mdXNpb24gYXJvdW5kICAgICAgICAg
ICAgICBDT04vTk9OIHdhcyByZXNvbHZlZOKAnS4NCg0KV2hlcmUgcmVsZXZhbnQsIEnigJl2ZSBh
ZGRlZCBjbGFyaWZpY2F0aW9ucyAtIHN1Y2ggYXMgdGhlIEFwcGVuZGl4IHJlbGF0ZWQgdG8gZGlm
ZmVyZW5jZXMgaW4gT2JzZXJ2ZSBmb3IgcmVsaWFibGUgdHJhbnNwb3J0cy4NCg0KQm90aCBDYXJz
dGVuIGFuZCBIYW5uZXMgY291bGQgcHJvYmFibHkgb2ZmZXIgbW9yZSBjb250ZXh0IGlmIG5lZWRl
ZC4NCg0KRnJvbTogWW9zaGlmdW1pIE5pc2hpZGEgW21haWx0bzpuaXNoaWRhQHNmYy53aWRlLmFk
LmpwXQ0KU2VudDogRnJpZGF5LCBBcHJpbCAyMSwgMjAxNyAyOjA4IFBNDQpUbzogQnJpYW4gUmF5
bW9yIDxCcmlhbi5SYXltb3JAbWljcm9zb2Z0LmNvbT4NCkNjOiBZb3NoaWZ1bWkgTmlzaGlkYSA8
bmlzaGlkYUBzZmMud2lkZS5hZC5qcD47IHRzdi1hcnRAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtY29y
ZS1jb2FwLXRjcC10bHNAaWV0Zi5vcmc7IGNvcmVAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNClN1
YmplY3Q6IFJlOiBUU1YtQVJUIHJldmlldyBvZiBkcmFmdC1pZXRmLWNvcmUtY29hcC10Y3AtdGxz
LTA3DQoNCkhpIEJyaWFuLA0KDQpKdXN0IGluIGNhc2UsDQpSZWxpYWJsZSB0cmFuc3BvcnRzIG9u
bHkgcHJvdmlkZSByZWxpYWJpbGl0eSBhdCB0cmFuc3BvcnQgbGV2ZWwuIEl0IGRvZXNuJ3QgcHJv
dmlkZSByZWxpYWJpbGl0eSBpbiBhcHBsaWNhdGlvbiBwcm90b2NvbCBsZXZlbC4NCg0KUkZDNzI1
MiBoYXMgcmVsaWFiaWxpdHkgbWVjaGFuaXNtcyBpbiBpdCBzaW5jZSBpdCB1c2VzIFVEUC4gVGhp
cyBtZWFucyBpdCBoYXMgYWJpbGl0aWVzIHRvIGNoZWNrIGJvdGggdHJhbnNwb3J0IGFuZCBhcHAg
bGV2ZWwgcmVsaWFiaWxpdHkuDQpUaGlzIGRyYWZ0IG9ubHkgcHJvdmlkZXMgdHJhbnNwb3J0IGxl
dmVsIHJlbGlhYmlsaXR5IGFuZCBhcHBzIHdpbGwgbmVlZCB0byBkZXRlY3QgYXBwIHByb3RvY29s
IGZhaWx1cmUgYnkgdGhlbXNlbHZlcy4NClRoaXMgbWVhbnMgNzI1MiBhbmQgdGhpcyBkcmFmdCBh
cmUgbm90IHRvdGFsbHkgZXF1aXZhbGVudCBmcm9tIHRoZSB2aWV3cG9pbnQgb2YgYXBwbGljYXRp
b25zLg0KDQpJIGFtIG5vdCBzYXlpbmcgdGhpcyBpcyB3cm9uZyBvciBiYWQsIGJ1dCBJIGJlbGll
dmUgYXBwIGRldmVsb3BlciBzaG91bGQgYXdhcmUgdGhpcyBwb2ludC4NCi0tDQpZb3NoaQ0KDQpP
biBGcmksIEFwciAyMSwgMjAxNyBhdCAxMToxNSBBTSwgQnJpYW4gUmF5bW9yIDxCcmlhbi5SYXlt
b3JAbWljcm9zb2Z0LmNvbTxtYWlsdG86QnJpYW4uUmF5bW9yQG1pY3Jvc29mdC5jb20+PiB3cm90
ZToNCg0KSGkgWW9zaGksDQoNCg0KDQo+IE9LLiBJIGFsc28gdGhpbmsgd2Ugc2hvdWxkIHN0YXRl
IHRoYXQgdGhlIHByb3RvY29sIHNob3VsZCBub3RpZnkgdGhlIGZhaWx1cmUgZXZlbnRzIHRvIGFw
cGxpY2F0aW9ucy4NCg0KPiBTaW5jZSBlcnJvcnMgY2FuIGhhcHBlbiBub3Qgb25seSBpbiBUQ1As
IGJ1dCBhbHNvIFRMUyBhbmQgd2Vic29ja2V0IGxldmVsLCBtZW50aW9uaW5nIG9ubHkgVENQIGNs
b3NlIG9yIHJlc2V0IG1pZ2h0IG5vdA0KDQo+IGJlIGVub3VnaC4NCg0KDQoNCkFmdGVyIHJldmll
d2luZyB3aXRoIHRoZSBhdXRob3JzLCBhbiBhZGRpdGlvbmFsIGNsYXJpZmljYXRpb24gd2FzIGFw
cGVuZGVkIHRvIDMuNCBDb25uZWN0aW9uIEhlYWx0aCAtIGh0dHBzOi8vZ2l0aHViLmNvbS9jb3Jl
LXdnL2NvYXAtdGNwLXRscy9wdWxsLzE0MC9maWxlcw0KDQoNCg0KVGhlIG9waW5pb24gb2YgdGhl
IGF1dGhvcnMgKGFuZCBHZW5neXUgV0VJ4oCZcyByZWNlbnQgcmVzcG9uc2UgLSBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cwODYyMi5odG1sKSBp
cyB0aGF0IFJGQzY0NTUgY292ZXJzIHRoZSBXZWJTb2NrZXQgY2FzZSBhbmQgZG9lcyBub3QgbmVl
ZCB0byBiZSByZXBlYXRlZCBoZXJlLg0KDQoNCg0KPiBXaGVuIHdlIHVzZSA3MjUyLCBJIHRoaW5r
IGFwcGxpY2F0aW9ucyBiYXNpY2FsbHkgZG9uJ3QgbmVlZCB0byBpbXBsZW1lbnQgdGltZW91dHMg
b3IgcmV0cnkgbWVjaGFuaXNtcyBhcyB0aGUgcHJvdG9jb2wNCg0KPiBwcm92aWRlcyBzdWNoIHRo
aW5ncy4NCg0KDQoNClJGQzcyNTIgcHJvdmlkZXMgdGltZW91dHMgYW5kIHJldHJpZXMgYmVjYXVz
ZSBpdCdzIGltcGxlbWVudGluZyBhIFRDUC1saWtlIHJlbGlhYmlsaXR5IG1lY2hhbmlzbSBvdmVy
IFVEUCAtIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM3MjUyI3NlY3Rpb24tMi4xDQoN
Cg0KDQo+IEhvd2V2ZXIsIHdoZW4gd2UgdXNlIHRoaXMgb25lLCBpdCBzZWVtcyBhcHBsaWNhdGlv
bnMgd2lsbCBuZWVkIHRvIGhhdmUgc3VjaCBtZWNoYW5pc21zLiBJc24ndCBpdCBhIGJpdCBjb25m
dXNpbmc/IEkgYW0gdGhpbmtpbmcgdGhhdA0KDQo+IHRoZXJlIG5lZWQgdG8gYmUgc29tZSBndWlk
YW5jZSBoZXJlLg0KDQo+IEJUVywgUE9ORyBpcyBvbmUgZXhhbXBsZS4NCg0KDQoNCkZvciBjb2Fw
LXRjcC10bHMsIHRoZXJlIGFyZSBtdWx0aXBsZSBlYXJseSBpbXBsZW1lbnRhdGlvbnMuIFRoaXMg
aGFzIG5ldmVyIGJlZW4gcmVwb3J0ZWQgYXMgYSBzb3VyY2Ugb2YgY29uZnVzaW9uLg0KDQoNCg0K
Pj4gTXkgc2Vuc2UgaXMgdGhhdCB3ZSBzaG91bGQgdHJlYXQgdGhpcyBhcyBhbiB1cGRhdGUgdG8g
UkZDNzk1OSBiYXNlZCBvbiB0aGUgb3JpZ2luYWwgbGFuZ3VhZ2U6DQoNCj4gSSBkb24ndCBoYXZl
IGEgc3Ryb25nIG9waW5pb24gaGVyZS4gVXBkYXRpbmcgNzk1OSBpcyBmaW5lIGZvciBtZSBpZiBp
dCdzIGNsZWFyZXIgdG8gQ29BUCBwZW9wbGUuDQoNCg0KDQpJJ3ZlIG1lcmdlZCB0aGUgY2hhbmdl
IC0gaHR0cHM6Ly9naXRodWIuY29tL2NvcmUtd2cvY29hcC10Y3AtdGxzL3B1bGwvMTM4L2ZpbGVz
DQoNCg0KVGhhbmtzIGFnYWluIGZvciBoZWxwaW5nIHVzIHRvIGltcHJvdmUgdGhlIHF1YWxpdHkg
b2YgdGhlIGRyYWZ0LA0KDQrigKZCcmlhbg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1z
b25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCglt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAuZ21haWwtbS0zMDU4NDQ4
ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0LCBsaS5nbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdt
c29wbGFpbnRleHQsIGRpdi5nbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQN
Cgl7bXNvLXN0eWxlLW5hbWU6Z21haWwtbV8tMzA1ODQ0ODgxNTYzNzY3NjY0N21zb3BsYWludGV4
dDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIu
MHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uZ21haWwt
DQoJe21zby1zdHlsZS1uYW1lOmdtYWlsLTt9DQpzcGFuLmdtYWlsLWhvZW56Yg0KCXttc28tc3R5
bGUtbmFtZTpnbWFpbC1ob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJ
Y29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBv
cnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFy
Z2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+SSB0aGluayB0aGF0IEkgdW5kZXJzdGFuZCB5b3Vy
IHBlcmNlcHRpb25zIGJldHRlci4gUHJpb3IgdG8gYWRvcHRpb24gb2YgY29hcC10Y3AtdGxzIGFu
ZCBiZWZvcmUgSSB3YXMgYWN0aXZlIGluIHRoZSBXRywgSSByZWNhbGwgZGlzY3Vzc2lvbnMgcmVs
YXRlZCB0byB0aGUgY29uZnVzaW9uIG92ZXIgYXBwbGljYXRpb24NCiB2cyB0cmFuc3BvcnQgcmVs
aWFiaWxpdHkgaW4gQ29BUCBlc3BlY2lhbGx5IGFzIHJlbGF0ZWQgdG8gQ09OIGFuZCBOT04uIFdo
YXQgd2FzIGludGVuZGVkPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5UaW0gQ2FyZXkgb3V0bGluZWQgc29tZSBj
b25jZXJucyBpbjo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1jYXJleS1jb3JlLXN0ZC1tc2ctdnMtdHJhbnMtYWRhcHQtMDAjc2VjdGlvbi0yIj5odHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2FyZXktY29yZS1zdGQtbXNnLXZzLXRyYW5zLWFk
YXB0LTAwI3NlY3Rpb24tMjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+VGhpcyB0b3BpYyB3YXMgcHJlc2Vu
dGVkIGluIGRldGFpbCBhdCBJRVRGIDkzIC0NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L3Byb2NlZWRpbmdzLzkzL3NsaWRlcy9zbGlkZXMtOTMtY29yZS0wLnBkZiI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvcHJvY2VlZGluZ3MvOTMvc2xpZGVzL3NsaWRlcy05My1jb3JlLTAucGRmPC9hPiAt
IHN0YXJ0aW5nIG9uIHNsaWRlIDIzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5BbmQgaW4gYSByZWxhdGVkIHRo
cmVhZCBvbiB0aGUgbWFpbGluZyBsaXN0IGJhY2sgaW4gMjAxNSAtDQo8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cwNjI4MC5odG1s
Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2NvcmUvY3VycmVudC9tc2cw
NjI4MC5odG1sPC9hPiAtIENhcnN0ZW4gcmVzcG9uZGVkOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7IElu
IGFueSBjYXNlLCBDT04gYW5kIE5PTiBhcmUgYWJvdXQgbWVzc2FnZSBsYXllciBzZW1hbnRpY3Ms
IG5vdCBhYm91dCBhcHBsaWNhdGlvbiBzZW1hbnRpY3M8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZndDsgLS0geW91IGdhdmUgdGhl
bSBhIG1lYW5pbmcgdGhleSBkb24ndCBoYXZlLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkJ5IElFVEYgOTQs
IHRoZSBhdXRob3JzIHdlcmUgcmVwb3J0aW5nIOKAkyDigJxNb3N0IG9mIHRoZSBDb25mdXNpb24g
YXJvdW5kJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IENPTi9OT04gd2FzIHJlc29sdmVk4oCdLg0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPldoZXJlIHJlbGV2YW50LCBJ4oCZdmUgYWRkZWQgY2xhcmlmaWNhdGlvbnMg
LSBzdWNoIGFzIHRoZSBBcHBlbmRpeCByZWxhdGVkIHRvIGRpZmZlcmVuY2VzIGluIE9ic2VydmUg
Zm9yIHJlbGlhYmxlIHRyYW5zcG9ydHMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkJvdGggQ2Fyc3RlbiBhbmQg
SGFubmVzIGNvdWxkIHByb2JhYmx5IG9mZmVyIG1vcmUgY29udGV4dCBpZiBuZWVkZWQuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRD
b21wb3NlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48L3A+
DQo8c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsRW5kQ29tcG9zZSI+PC9zcGFuPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj4gWW9zaGlmdW1pIE5pc2hpZGEgW21haWx0bzpuaXNoaWRhQHNmYy53aWRl
LmFkLmpwXQ0KPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgQXByaWwgMjEsIDIwMTcgMjowOCBQ
TTxicj4NCjxiPlRvOjwvYj4gQnJpYW4gUmF5bW9yICZsdDtCcmlhbi5SYXltb3JAbWljcm9zb2Z0
LmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IFlvc2hpZnVtaSBOaXNoaWRhICZsdDtuaXNoaWRhQHNm
Yy53aWRlLmFkLmpwJmd0OzsgdHN2LWFydEBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1jb3JlLWNvYXAt
dGNwLXRsc0BpZXRmLm9yZzsgY29yZUBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4NCjxiPlN1
YmplY3Q6PC9iPiBSZTogVFNWLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jb3JlLWNvYXAtdGNw
LXRscy0wNzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgQnJpYW4sPG86cD48L286
cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5KdXN0IGluIGNhc2UsPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZWxpYWJsZSB0
cmFuc3BvcnRzIG9ubHkgcHJvdmlkZSByZWxpYWJpbGl0eSBhdCB0cmFuc3BvcnQgbGV2ZWwuIEl0
IGRvZXNuJ3QgcHJvdmlkZSByZWxpYWJpbGl0eSBpbiBhcHBsaWNhdGlvbiBwcm90b2NvbCBsZXZl
bC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+UkZDNzI1MiBoYXMgcmVsaWFiaWxpdHkgbWVjaGFuaXNtcyBpbiBpdCBzaW5jZSBpdCB1
c2VzIFVEUC4gVGhpcyBtZWFucyBpdCBoYXMgYWJpbGl0aWVzIHRvIGNoZWNrIGJvdGggdHJhbnNw
b3J0IGFuZCBhcHAgbGV2ZWwgcmVsaWFiaWxpdHkuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGRyYWZ0IG9ubHkgcHJvdmlkZXMgdHJhbnNw
b3J0IGxldmVsIHJlbGlhYmlsaXR5IGFuZCBhcHBzIHdpbGwgbmVlZCB0byBkZXRlY3QgYXBwIHBy
b3RvY29sIGZhaWx1cmUgYnkgdGhlbXNlbHZlcy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMgbWVhbnMgNzI1MiBhbmQgdGhpcyBk
cmFmdCBhcmUgbm90IHRvdGFsbHkgZXF1aXZhbGVudCBmcm9tIHRoZSB2aWV3cG9pbnQgb2YgYXBw
bGljYXRpb25zLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5JIGFtIG5vdCBzYXlpbmcgdGhpcyBpcyB3cm9uZyBvciBiYWQsIGJ1dCBJ
IGJlbGlldmUgYXBwIGRldmVsb3BlciBzaG91bGQgYXdhcmUgdGhpcyBwb2ludC48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Zb3NoaTxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBGcmksIEFwciAyMSwgMjAxNyBhdCAxMTox
NSBBTSwgQnJpYW4gUmF5bW9yICZsdDs8YSBocmVmPSJtYWlsdG86QnJpYW4uUmF5bW9yQG1pY3Jv
c29mdC5jb20iIHRhcmdldD0iX2JsYW5rIj5Ccmlhbi5SYXltb3JAbWljcm9zb2Z0LmNvbTwvYT4m
Z3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBw
dDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iZ21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50
ZXh0Ij5IaSBZb3NoaSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4
MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3NjY0N21zb3BsYWludGV4dCI+Jmd0OyBPSy4gSSBhbHNv
IHRoaW5rIHdlIHNob3VsZCBzdGF0ZSB0aGF0IHRoZSBwcm90b2NvbCBzaG91bGQgbm90aWZ5IHRo
ZSBmYWlsdXJlIGV2ZW50cyB0byBhcHBsaWNhdGlvbnMuJm5ic3A7PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iZ21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mZ3Q7IFNp
bmNlIGVycm9ycyBjYW4gaGFwcGVuIG5vdCBvbmx5IGluIFRDUCwgYnV0IGFsc28gVExTIGFuZCB3
ZWJzb2NrZXQgbGV2ZWwsIG1lbnRpb25pbmcgb25seSBUQ1AgY2xvc2Ugb3IgcmVzZXQgbWlnaHQg
bm90DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2
NDdtc29wbGFpbnRleHQiPiZndDsgYmUgZW5vdWdoLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3NjY0N21zb3BsYWludGV4dCI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iZ21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0
Ij5BZnRlciByZXZpZXdpbmcgd2l0aCB0aGUgYXV0aG9ycywgYW4gYWRkaXRpb25hbCBjbGFyaWZp
Y2F0aW9uIHdhcyBhcHBlbmRlZCB0byAzLjQgQ29ubmVjdGlvbiBIZWFsdGggLQ0KPGEgaHJlZj0i
aHR0cHM6Ly9naXRodWIuY29tL2NvcmUtd2cvY29hcC10Y3AtdGxzL3B1bGwvMTQwL2ZpbGVzIiB0
YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL2dpdGh1Yi5jb20vY29yZS13Zy9jb2FwLXRjcC10bHMv
cHVsbC8xNDAvZmlsZXM8L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iZ21haWwtbS0zMDU4
NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQiPlRoZSBvcGluaW9u
IG9mIHRoZSBhdXRob3JzIChhbmQgR2VuZ3l1IFdFSeKAmXMgcmVjZW50IHJlc3BvbnNlIC0NCjxh
IGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvY29yZS9jdXJyZW50
L21zZzA4NjIyLmh0bWwiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWwtYXJjaGl2ZS93ZWIvY29yZS9jdXJyZW50L21zZzA4NjIyLmh0bWw8L2E+KSBpcyB0aGF0IFJG
QzY0NTUgY292ZXJzIHRoZSBXZWJTb2NrZXQgY2FzZSBhbmQgZG9lcyBub3QgbmVlZCB0byBiZSBy
ZXBlYXRlZCBoZXJlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgx
NTYzNzY3NjY0N21zb3BsYWludGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
Z21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mZ3Q7IFdoZW4gd2UgdXNl
IDcyNTIsIEkgdGhpbmsgYXBwbGljYXRpb25zIGJhc2ljYWxseSBkb24ndCBuZWVkIHRvIGltcGxl
bWVudCB0aW1lb3V0cyBvciByZXRyeSBtZWNoYW5pc21zIGFzIHRoZSBwcm90b2NvbDxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3NjY0N21zb3BsYWludGV4
dCI+Jmd0OyBwcm92aWRlcyBzdWNoIHRoaW5ncy4gPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
Z21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQi
PlJGQzcyNTIgcHJvdmlkZXMgdGltZW91dHMgYW5kIHJldHJpZXMgYmVjYXVzZSBpdCdzIGltcGxl
bWVudGluZyBhIFRDUC1saWtlIHJlbGlhYmlsaXR5IG1lY2hhbmlzbSBvdmVyIFVEUCAtDQo8YSBo
cmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNzI1MiNzZWN0aW9uLTIuMSIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM3MjUyI3NlY3Rpb24t
Mi4xPC9hPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3
NjY0N21zb3BsYWludGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iZ21haWwt
bS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mZ3Q7IEhvd2V2ZXIsIHdoZW4gd2Ug
dXNlIHRoaXMgb25lLCBpdCBzZWVtcyBhcHBsaWNhdGlvbnMgd2lsbCBuZWVkIHRvIGhhdmUgc3Vj
aCBtZWNoYW5pc21zLiBJc24ndCBpdCBhIGJpdCBjb25mdXNpbmc/IEkgYW0gdGhpbmtpbmcgdGhh
dDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3NjY0N21z
b3BsYWludGV4dCI+Jmd0OyB0aGVyZSBuZWVkIHRvIGJlIHNvbWUgZ3VpZGFuY2UgaGVyZS48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFp
bnRleHQiPiZndDsgQlRXLCBQT05HIGlzIG9uZSBleGFtcGxlLjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgxNTYzNzY3NjY0N21zb3BsYWludGV4dCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iZ21haWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxh
aW50ZXh0Ij5Gb3IgY29hcC10Y3AtdGxzLCB0aGVyZSBhcmUgbXVsdGlwbGUgZWFybHkgaW1wbGVt
ZW50YXRpb25zLiBUaGlzIGhhcyBuZXZlciBiZWVuIHJlcG9ydGVkIGFzIGEgc291cmNlIG9mIGNv
bmZ1c2lvbi4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9ImdtYWlsLW0tMzA1ODQ0ODgxNTYz
NzY3NjY0N21zb3BsYWludGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iZ21h
aWwtbS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mZ3Q7Jmd0OyBNeSBzZW5zZSBp
cyB0aGF0IHdlIHNob3VsZCB0cmVhdCB0aGlzIGFzIGFuIHVwZGF0ZSB0byBSRkM3OTU5IGJhc2Vk
IG9uIHRoZSBvcmlnaW5hbCBsYW5ndWFnZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJnbWFp
bC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQiPiZndDsgSSBkb24ndCBoYXZlIGEg
c3Ryb25nIG9waW5pb24gaGVyZS4gVXBkYXRpbmcgNzk1OSBpcyBmaW5lIGZvciBtZSBpZiBpdCdz
IGNsZWFyZXIgdG8gQ29BUCBwZW9wbGUuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iZ21haWwt
bS0zMDU4NDQ4ODE1NjM3Njc2NjQ3bXNvcGxhaW50ZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQiPkkndmUg
bWVyZ2VkIHRoZSBjaGFuZ2UgLSA8YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vY29yZS13Zy9j
b2FwLXRjcC10bHMvcHVsbC8xMzgvZmlsZXMiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vZ2l0
aHViLmNvbS9jb3JlLXdnL2NvYXAtdGNwLXRscy9wdWxsLzEzOC9maWxlczwvYT48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJnbWFpbC1tLTMwNTg0NDg4MTU2Mzc2NzY2NDdtc29wbGFpbnRleHQi
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWYiPlRoYW5rcyBhZ2FpbiBmb3IgaGVscGluZyB1cyB0byBpbXByb3ZlIHRoZSBxdWFsaXR5
IG9mIHRoZSBkcmFmdCw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojODg4ODg4Ij4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiM4ODg4ODgiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM4ODg4ODgiPuKApkJyaWFuPC9zcGFuPjxz
cGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BY2PR21MB008453149ADC1A998FEA56D3831A0BY2PR21MB0084namp_--


From nobody Fri Apr 21 15:59:36 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A956129AE8; Fri, 21 Apr 2017 15:59:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <ops-dir@ietf.org>
Cc: grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-grow-large-communities-usage-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149281556219.25785.8583671563632752265@ietfa.amsl.com>
Date: Fri, 21 Apr 2017 15:59:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3c5_-QaxKrk_62rSNpCxv-Hl-wA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 22:59:22 -0000

Reviewer: Jouni Korhonen
Review result: Ready

I read the document through and did not spot anything that would have
caught my attention. 

One minor nit I have relates to management & administration to the
large communities functions and description of their semantics. Are
those maintained somewhere? If there are existing repositories,
documentation, etc it would be nice to point out those. The document
now hints to NANOG and NLNOG..


From nobody Fri Apr 21 16:55:31 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C2E129564; Fri, 21 Apr 2017 16:55:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters <paul@nohats.ca>
To: <secdir@ietf.org>
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
Subject: Secdir last call review of draft-ietf-core-links-json-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149281891905.25803.486183286884921759@ietfa.amsl.com>
Date: Fri, 21 Apr 2017 16:55:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DaRFnCyXjlFiXJ7WhwTwRxpWgtw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 23:55:19 -0000

Reviewer: Paul Wouters
Review result: Ready

I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat

these comments just like any other last call comments.

Concise Binary  Object Representation, CBOR (RFC7049) is a binary data
format
of JSON optimized for IoT. This document describes the JSON and CBOR
formats of the CoRE link format of RFC-6690.

The document's security section refers to the security sections of the
respective
formats' RFCs,  [RFC6690], [RFC7049] and [RFC7159]. These describe the
various
issues well. This document introduces no new issues that require
further
security considerations.



From nobody Fri Apr 21 21:16:09 2017
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C8812944A; Fri, 21 Apr 2017 21:16:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ines Robles <mariainesrobles@googlemail.com>
To: <rtg-dir@ietf.org>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Rtgdir last call review of draft-ietf-6man-rfc1981bis-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149283456181.25913.15133934620501134310@ietfa.amsl.com>
Date: Fri, 21 Apr 2017 21:16:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KEP0ORo7FhusS7bgHtqUrt-Jb6I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 04:16:02 -0000

Reviewer: Ines Robles
Review result: Has Nits

Document: draft-ietf-6man-rfc1981bis-06.txt

Reviewer: Ines Robles

Review Date: April 21, 2017

Intended status: Standards Track


Summary:

This document describes Path MTU Discovery for IP version 6

 I believe the draft is technically good. I have no “Major” issues
with this I-D. I have some minor comments.


Comments:

1- I think that it would be nice to add a graphical example that
describes the process of the Path MTU Discovery (including a Packet
Too Big Message). e.g. Figure 1 of RFC 5927[1].

2- Section 1: 

	2.1- I would add a reference when you mention black hole connection.
What about section 2.1 of [2] or [3]?

3- Section 2: 

	3.1- EMTU_S => When it is defined, it references RFC6691. But this
term is not mentioned in RFC6691. I would add additionally a reference
to RFC 1122 [4] which defines EMTU_S.

	3.2- I would add also the same references for EMTU_R.
 
4.Section 3:

	4.1- In the first paragraph, I would add a reference to ICMPv6 the
first time that ICMPv6 Packet Too Big message is mentioned. And I
would add here also "(ICMPv6 PTB)" since it used further in the
document. 

	4.2- In the first paragraph: "...to send smaller fragments or ..."
--> I think it would be clearer "to send smaller packets or..."

	4.3- Second Paragraph: "...process ends when the node's estimate..."
-> "...process ends when the source node's estimate..."?

	4.4- Last Paragraph: "can to appear" -> "can appear" . "...but is in
fact..." -> "...but it is in fact..."

5. Section 4:

	4.1- about this: "The node MUST reduce the size of the packets it is
sending along the path". I would add an explanation to which size the
packet should be reduced (maybe based in an initial example)


6.Section 5: 

	6.1- I would add a reference to RFC 1122 [4] when MMS_S is mentioned.


	6.2- Section 5.5: "Some transport protocols are not allowed to
repacketize when doing a retransmission..." I would add some
examples.

7. Section 6:

	7.1- What about to mention Blind Performance-Degrading Attack [5]?
 



From nobody Sat Apr 22 08:18:53 2017
Return-Path: <izaac@setec.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E93312426E for <ietf@ietfa.amsl.com>; Sat, 22 Apr 2017 08:18:52 -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, RP_MATCHES_RCVD=-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 hDwvXnYjW6uc for <ietf@ietfa.amsl.com>; Sat, 22 Apr 2017 08:18:49 -0700 (PDT)
Received: from abbott.setec.org (abbott.setec.org [IPv6:2610:1c0:4:0:95c6:777c:342b:270e]) by ietfa.amsl.com (Postfix) with ESMTP id B5A6F12009C for <ietf@ietf.org>; Sat, 22 Apr 2017 08:18:49 -0700 (PDT)
Received: from 38-232-201-29.pools.spcsdns.net (66-87-116-38.pools.spcsdns.net [66.87.116.38]) by abbott.setec.org (Postfix) with ESMTPSA id BF3B54CC92B for <ietf@ietf.org>; Sat, 22 Apr 2017 11:18:45 -0400 (EDT) (envelope-from izaac@setec.org)
Date: Sat, 22 Apr 2017 11:18:39 -0400
User-Agent: K-9 Mail for Android
In-Reply-To: <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <CAMm+LwgRegXgM3TqRJW_jfv+S6GrJ5RqJkpfaX0xQ0M7ZO_gPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Predictable Internet Time
To: ietf@ietf.org
From: Izaac <izaac@setec.org>
Message-ID: <AEFF8FFB-A5AC-4BE8-ABE1-D75EF72ECCDE@setec.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DszPdTrS6wKs769LunFvDIKAYAI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 15:18:52 -0000

On April 21, 2017 12:32:11 PM EDT, Phillip Hallam-Baker <phill@hallambaker=
=2Ecom> wrote:
>"All leap seconds are abolished=2E UTC =3D TAI +37 for all future dates=
=2E"

Awesome=2E So code that up, deploy it, and get back to us with the results=
 and a proposal in 2047=2E


--=20
Izaac


From nobody Sun Apr 23 00:28:26 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65919128C81; Sun, 23 Apr 2017 00:28:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <int-dir@ietf.org>
Cc: v6ops@ietf.org, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  ietf@ietf.org
Subject: Intdir last call review of draft-ietf-v6ops-unique-ipv6-prefix-per-host-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149293249738.25897.290627174722663000@ietfa.amsl.com>
Date: Sun, 23 Apr 2017 00:28:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HNJzZbJa1iy6MlBiGAF-v_tEpyM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Apr 2017 07:28:17 -0000

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I think the document is close to ready but some more meat in still
needed. Similar type of configurations have been used in other types
of link with success. A couple of nits and questions.

Line 157: "hosts/subscribers devices connected to the provider managed
shared" is somewhat hard to parse. Does it mean to say
"hosts'/subscribers' devices.."?

RFC6106 reference need to be replaced with 8106.

Line 259: Retransmit timer is the "AdvRetransTimer" or "restrans
timer"? Be more specific here.

Section 4 talks about unicast RAs. I think it would be good to mention
also RFC6085, which allows unicasting an RA to a host on an Ethernet
link, while RAs still use layer-3 multicast addressing. Similar goal,
different approach. At least I would welcome text why RFC6085 is not
endorsed or applicable?

Section 5 gives some guidance regarding unsolicited RAs. However, it
does not say anything about PIOs, although the context of the text
seems to assume the presence of PIOs. I would mention those
explicitly.  I would also be more clear and state the unsolicited RAs
are again unicasted. At least the current text seems to assume so.

What happens when RSes get lost (all MAX_RTR_SOLICITATIONS)? 

How shared links with multiple first hop routers are supposed to work
with the recommendations of this BCP. Current text seems to be only
considering a single first hop router deployments. 


From nobody Sun Apr 23 15:19:37 2017
Return-Path: <kolkman@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4B11270AC; Sun, 23 Apr 2017 15:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=isoc.org
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 8m1iKNzWl7vb; Sun, 23 Apr 2017 15:19:27 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0078.outbound.protection.outlook.com [104.47.37.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A4551243F6; Sun, 23 Apr 2017 15:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=znll+eAQZo0VsE1iZdl4cOka+ct9loF90q5L4vTXwcI=; b=C8K1/W3HX+dmyvESD2fuVHPPJk3fiF0+XzOnVNPMu+fMXnEj4rCTjcDDgsQGCGoLII2uGCLEFB+lMZwKZgPIdvZId6iMCTM47zc5ZxYWAWRAGQco++sQBb69GfOA+r881VIZjMc0J32yVS+iETsb0tvSAuADTYncnwYa2xdqr4w=
Received: from DM5PR06MB3436.namprd06.prod.outlook.com (10.174.243.161) by DM5PR06MB3434.namprd06.prod.outlook.com (10.174.243.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.13; Sun, 23 Apr 2017 22:19:20 +0000
Received: from DM5PR06MB3436.namprd06.prod.outlook.com ([10.174.243.161]) by DM5PR06MB3436.namprd06.prod.outlook.com ([10.174.243.161]) with mapi id 15.01.1047.013; Sun, 23 Apr 2017 22:19:20 +0000
From: Olaf Kolkman <kolkman@isoc.org>
To: ietf-delta <ietf-delta@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, ietf <ietf@ietf.org>
Subject: =?utf-8?B?V2FybmluZyAgcGhpc2ggIC0tICBSZTogW0lldGYtzpRd4pyIdXNlZnVsIHN0?= =?utf-8?Q?uff?=
Thread-Topic: =?utf-8?B?V2FybmluZyAgcGhpc2ggIC0tICBSZTogW0lldGYtzpRd4pyIdXNlZnVsIHN0?= =?utf-8?Q?uff?=
Thread-Index: AQHSvDPIB52pwr6MVkKDUZ+qcpfhZKHThuee
Date: Sun, 23 Apr 2017 22:19:20 +0000
Message-ID: <DM5PR06MB3436CABCB4CE2825FB4D4327D91C0@DM5PR06MB3436.namprd06.prod.outlook.com>
References: <1575215068.20170423161523@queuefull.net>
In-Reply-To: <1575215068.20170423161523@queuefull.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-originating-ip: [25.174.189.132]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB3434; 7:lMeZeDLsciOk08qlv46tajUFIgkPRf0HLfduxLLjLwukw6r/cKDAzx27NMoxXj2PGGiHEAmby+i2ML/9qMmQgV/esJl9gReRJcF4FVuYorD189KLIqE8q2+xA7tjGGg14VUan2OF7JJRzecTYnvYqg0gYJIrWmX9oTzAR4e6WMFdWFYTYrkbYhuhQ6bUyTPaO7Y+vGOb5Aqbe1yShsLASr/A21TC8f8HzBHquPUvGk8hJlBi72q0V4ZRUc6vyf4z3iRvOK/qr+sqxcT0WGrAZPoVhpLurxSXHrolZBOUodfiOLwVMB6VetHXTzzZW3YWQom7hRRm3BKRxkaHpWA9pw==
x-ms-office365-filtering-correlation-id: e2ccc45e-8887-45a2-fb8f-08d48a96ca40
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:DM5PR06MB3434; 
x-microsoft-antispam-prvs: <DM5PR06MB3434EA6D62EA8842BA8C7FA0D91C0@DM5PR06MB3434.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(20161123555025)(20161123564025)(20161123562025)(6072148); SRVR:DM5PR06MB3434; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB3434; 
x-forefront-prvs: 0286D7B531
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39450400003)(39410400002)(39400400002)(377454003)(122556002)(86362001)(3846002)(102836003)(54356999)(50986999)(189998001)(6116002)(76176999)(224303003)(6306002)(8936002)(236005)(54896002)(66066001)(53936002)(38730400002)(606005)(74316002)(99286003)(9686003)(55016002)(6506006)(3280700002)(77096006)(7736002)(7906003)(33656002)(2900100001)(2906002)(305945005)(5660300001)(450100002)(25786009)(7696004)(2950100002)(81166006)(3660700001)(53546009)(58493002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR06MB3434; H:DM5PR06MB3436.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR06MB3436CABCB4CE2825FB4D4327D91C0DM5PR06MB3436namp_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Apr 2017 22:19:20.4943 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB3434
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xSMdJ0W-Rfx6KQ-1KKOFGG1tAeM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Apr 2017 22:19:29 -0000

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

SWYgeW91IGNhcmVmdWxseSBsb29rIGF0IHRoZSBlbnZlbG9wZSBhZGRyZXNzIHlvdSBjYW4gc2Vl
IHRoaXMgcGhpc2ggd2FzIG5vdCBtaW5lLg0KDQpQaXNzZXMgbWUgb2ZmLg0KDQpPbGFmIEtvbGtt
YW4NCg0KR2V0IE91dGxvb2sgZm9yIEFuZHJvaWQ8aHR0cHM6Ly9ha2EubXMvZ2hlaTM2Pg0KDQoN
CkZyb206IE9sYWYgS29sa21hbg0KU2VudDogU3VuZGF5LCBBcHJpbCAyMywgOToxNiBBTQ0KU3Vi
amVjdDogW0lldGYtzpRd4pyIdXNlZnVsIHN0dWZmDQpUbzogaWV0Zi1kZWx0YSwgSUVURiBBbm5v
dW5jZW1lbnQgTGlzdCwgaWV0Zg0KDQpHcmVldGluZ3MhIEkndmUgYWNjaWRlbnRhbGx5IGNvbWUg
YWNyb3NzIHRoYXQgc3R1ZmYsIGl0IG1pZ2h0IGJlIHZlcnkgdXNlZnVsIGZvciB5b3UsIGp1c3Qg
dGFrZSAuLi4uDQoNCkh1Z3MsIE9sYWYgS29sa21hbg0K

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHAgZGlyPSJhdXRv
IiBzdHlsZT0iIHRleHQtYWxpZ246IGxlZnQ7IG1hcmdpbi10b3A6IDI1cHg7IG1hcmdpbi1ib3R0
b206IDI1cHg7IGZvbnQtZmFtaWx5OiBzYW5zLXNlcmlmOyBmb250LXNpemU6IDExcHQ7IGNvbG9y
OiBibGFjazsgYmFja2dyb3VuZC1jb2xvcjogd2hpdGUgIj4NCklmIHlvdSBjYXJlZnVsbHkgbG9v
ayBhdCB0aGUgZW52ZWxvcGUgYWRkcmVzcyB5b3UgY2FuIHNlZSB0aGlzIHBoaXNoIHdhcyBub3Qg
bWluZS48L3A+DQo8cCBkaXI9ImF1dG8iIHN0eWxlPSIgdGV4dC1hbGlnbjogbGVmdDsgbWFyZ2lu
LXRvcDogMjVweDsgbWFyZ2luLWJvdHRvbTogMjVweDsgZm9udC1mYW1pbHk6IHNhbnMtc2VyaWY7
IGZvbnQtc2l6ZTogMTFwdDsgY29sb3I6IGJsYWNrOyBiYWNrZ3JvdW5kLWNvbG9yOiB3aGl0ZSAi
Pg0KUGlzc2VzIG1lIG9mZi4gPC9wPg0KPHAgZGlyPSJhdXRvIiBzdHlsZT0iIHRleHQtYWxpZ246
IGxlZnQ7IG1hcmdpbi10b3A6IDI1cHg7IG1hcmdpbi1ib3R0b206IDI1cHg7IGZvbnQtZmFtaWx5
OiBzYW5zLXNlcmlmOyBmb250LXNpemU6IDExcHQ7IGNvbG9yOiBibGFjazsgYmFja2dyb3VuZC1j
b2xvcjogd2hpdGUgIj4NCk9sYWYgS29sa21hbjwvcD4NCjxwIGRpcj0iYXV0byIgc3R5bGU9IiB0
ZXh0LWFsaWduOiBsZWZ0OyBtYXJnaW4tdG9wOiAyNXB4OyBtYXJnaW4tYm90dG9tOiAyNXB4OyBm
b250LWZhbWlseTogc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxMXB0OyBjb2xvcjogYmxhY2s7IGJh
Y2tncm91bmQtY29sb3I6IHdoaXRlICI+DQo8L3A+DQo8cCBkaXI9ImF1dG8iIHN0eWxlPSIgdGV4
dC1hbGlnbjogbGVmdDsgbWFyZ2luLXRvcDogMjVweDsgbWFyZ2luLWJvdHRvbTogMjVweDsgZm9u
dC1mYW1pbHk6IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTFwdDsgY29sb3I6IGJsYWNrOyBiYWNr
Z3JvdW5kLWNvbG9yOiB3aGl0ZSAiPg0KR2V0IDxhIGhyZWY9Imh0dHBzOi8vYWthLm1zL2doZWkz
NiI+T3V0bG9vayBmb3IgQW5kcm9pZDwvYT48L3A+DQo8YnI+DQo8cD48L3A+DQo8cCBkaXI9ImF1
dG8iIHN0eWxlPSIgdGV4dC1hbGlnbjogbGVmdDsgbWFyZ2luLXRvcDogMjVweDsgbWFyZ2luLWJv
dHRvbTogMjVweDsgZm9udC1mYW1pbHk6IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTFwdDsgY29s
b3I6IGJsYWNrOyBiYWNrZ3JvdW5kLWNvbG9yOiB3aGl0ZSAiPg0KRnJvbTogT2xhZiBLb2xrbWFu
PGJyPg0KU2VudDogU3VuZGF5LCBBcHJpbCAyMywgOToxNiBBTTxicj4NClN1YmplY3Q6IFtJZXRm
Lc6UXeKciHVzZWZ1bCBzdHVmZjxicj4NClRvOiBpZXRmLWRlbHRhLCBJRVRGIEFubm91bmNlbWVu
dCBMaXN0LCBpZXRmPGJyPg0KPC9wPg0KPHAgZGlyPSJhdXRvIiBzdHlsZT0iIHRleHQtYWxpZ246
IGxlZnQ7IG1hcmdpbi10b3A6IDI1cHg7IG1hcmdpbi1ib3R0b206IDI1cHg7IGZvbnQtZmFtaWx5
OiBzYW5zLXNlcmlmOyBmb250LXNpemU6IDExcHQ7IGNvbG9yOiBibGFjazsgYmFja2dyb3VuZC1j
b2xvcjogd2hpdGUgIj4NCkdyZWV0aW5ncyEgSSd2ZSBhY2NpZGVudGFsbHkgY29tZSBhY3Jvc3Mg
dGhhdCBzdHVmZiwgaXQgbWlnaHQgYmUgdmVyeSB1c2VmdWwgZm9yIHlvdSwganVzdCB0YWtlIC4u
Li48L3A+DQo8cCBkaXI9ImF1dG8iIHN0eWxlPSIgdGV4dC1hbGlnbjogbGVmdDsgbWFyZ2luLXRv
cDogMjVweDsgbWFyZ2luLWJvdHRvbTogMjVweDsgZm9udC1mYW1pbHk6IHNhbnMtc2VyaWY7IGZv
bnQtc2l6ZTogMTFwdDsgY29sb3I6IGJsYWNrOyBiYWNrZ3JvdW5kLWNvbG9yOiB3aGl0ZSAiPg0K
SHVncywgT2xhZiBLb2xrbWFuIDwvcD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_DM5PR06MB3436CABCB4CE2825FB4D4327D91C0DM5PR06MB3436namp_--


From nobody Sun Apr 23 16:31:15 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C77C3126CF9 for <ietf@ietfa.amsl.com>; Sun, 23 Apr 2017 16:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TA2R7u1dTN1X for <ietf@ietfa.amsl.com>; Sun, 23 Apr 2017 16:31:12 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::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 C1348126C23 for <ietf@ietf.org>; Sun, 23 Apr 2017 16:31:11 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id t144so65603051lff.1 for <ietf@ietf.org>; Sun, 23 Apr 2017 16:31:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6fca8xz5q10xRiwk2LSmsX8GiX8c0y1R8s0H1gl3CGI=; b=O2ZHwXFn7x+AzrIkk4wNwo9hA6Z6PUaw4njANilDluysPMyT3jwdmVUmEnFwrBkY6S w0NLJPg7ehdKyVGTpHge+1/MHD+KGJP1rUhG7X6AHI/uaA0oiKXbaWkHWKJ0EWvfyus0 zBiv5mkggj1WETsI8Eq+5EQU3jheuxAVuT3ECnhcs9NZSb+PXw0yjcpgQrt+Z5MEWCOr WtHWq9PB1K3QHFzjJC/lyxLdOKSeQjztYcSw3RzjjS46Wf5PRBEtu/DrKnxI8xFdj5Xq SuPnNRNXuUwcedYogUE+Ux6/SP+rsWzSYcGjACrR3Vsj3kNif4/VbbgLf5FgnxHq31dd AlSw==
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=6fca8xz5q10xRiwk2LSmsX8GiX8c0y1R8s0H1gl3CGI=; b=p2Qo7h486rjW5Cn5KgPXHLHQabHv8AbkhfPRNiFeC6qHkGy159zaDcHcnQ/lwhRF3B PQFQWJLKEinYPwbeZG93JV3Rj2jD0+dymrWSUKXQ1gvwXzphS+20Ff1+4ycDBmEc6RAX gz4o6dmb1NglmBdfp7G8q9xkS5Mx82+HK3xAmYfCmkUHM+qRhk+rInavZW5t4VD/JrYK RbvbJ74/wPaEnAYNz7x2cBXKUBOy+ToFx+BXNNlL316nbmfPGL/OYhcAE2OUnylLdhsx sf/wD3CHLrbDFED59dlnDtRgxBSAM6EryKXoWSCyayxtZmjtWyZPk7gDPqp+Swx5Fz4s iwXg==
X-Gm-Message-State: AN3rC/5gOK+RplprYDBJN9OLyv6xsbBCv4RMs5lC0uWXASbEXqDWcouT DgTzc1gbxAWX7eQrRfCzpLDwsi8miJpieWU=
X-Received: by 10.46.87.80 with SMTP id r16mr8249973ljd.50.1492990270138; Sun, 23 Apr 2017 16:31:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.2 with HTTP; Sun, 23 Apr 2017 16:31:09 -0700 (PDT)
In-Reply-To: <20170421143112.28055.qmail@ary.lan>
References: <CABkgnnVmJf66ZJLToFm9_o34P3FswezVRFguuFrgMJeQv_TMgg@mail.gmail.com> <20170421143112.28055.qmail@ary.lan>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 24 Apr 2017 09:31:09 +1000
Message-ID: <CABkgnnUeoLOm=r1fBXw+r5FZobqHXLSbdQ9q=6i=PYkTEOrdfg@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: John Levine <johnl@taugh.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0ef_0C8jWsnCs9AncTj3X0t7AsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Apr 2017 23:31:14 -0000

On 22 April 2017 at 00:31, John Levine <johnl@taugh.com> wrote:
>>> If a recipient is cooperative, and sends you back a message signed
>>> with the same key to which you encrypted the message, that tells you
>>> he got it, but that's not a very interesting case.
>>
>>It's also abuse of the cryptographic primitives, I hope that this
>>isn't really how it works and you are eliding certain key details.
>
> It doesn't use the same session key, it uses the same public key.  It's
> not obvious to me why that would be wrong.

https://tools.ietf.org/html/rfc8017#section-6

If you are using ECDSA/ECDH, then you can also commit the same abuses.
Historically, keys were saved with an "EC" type, and can be used for
either interchangeably (the library I work on commits this sin).  In
the case of EC, there isn't a known path from use of ECDSA to abuse of
ECDH and vice versa, but it isn't known to be safe either.

This is much harder, if not possible with the X25519/Ed25519 pair,
because no library will support you in this.


From nobody Sun Apr 23 19:04:44 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8751A127071; Sun, 23 Apr 2017 19:04:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Date: Sun, 23 Apr 2017 19:04:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9bcMN-n07ZKzFAlD_ZougvIupCU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 02:04:31 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by
the IESG for the IETF Chair.  Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for
data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be
capitalized.  (Between -11 and -12, one instance of this was fixed,
but the other one remains.)

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such,
it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific
interfaces
   for forensics and troubleshooting, but an industry standard
interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second
sentence
seems to mean (though it doesn't say it) is that if you enable a
security function, you don't *know* that the network is protected if
you don't have any monitoring feedback.  (The sentence is stated in
terms of whether the network *is* protected, which it might well be,
even if you don't have monitoring.)  It seems that you need to
replace
"does not mean that a network is protected" with something that is
more literally correct.

The third sentence is constructed "... to have a mechanism to monitor
and provide execution status of NSFs to ...".  There's an awkwardness
that "monitor" isn't connected to "security and compliance management
tools", whereas "provide ... status ... to" *is* connected; there's a
problem that the "monitor" and "provide" are written as if they're
parallel, but they're not.  I think the wording is less confusing
this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific
interfaces
   for forensics and troubleshooting, but an industry standard
interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security
monitoring interfaces".

3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4),
and some times they're not (two places in 3).

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically
run
      to upload or download configuration changes, log information
and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by
a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of
an XXX", but I'm not familiar enough with the subject to know what
XXX
is.

[END]



From nobody Mon Apr 24 03:06:16 2017
Return-Path: <erik.wilde@dret.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B899B12EC13; Mon, 24 Apr 2017 03:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.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 Dho2VUhYH-8b; Mon, 24 Apr 2017 03:06:07 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (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 2863612EBCF; Mon, 24 Apr 2017 02:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=mGRZQ2Pk6IP6/9wtfPWMjnHXt+PJWC1dFb1mTGStjFk=; b=Ra+sR9NwwL+hjijG0dKrBk683O tNqK1vd/2imcrl0ojS7kbmSqjNjVMK1k3RIdDvFw7o76V1/MMAqLII9SrUP5UxLV9Ny5R9NhYzN+q Gi2+3nXRbPhARqNkVCBB9Rb80bri1CrGm2xVzN6VWFo4MMvjv1syfckrldjPPZt1VQd0r0M4Tfmci caQ7AKpBkS+SrKg+Mn1fEni2WFdtCMA9raNB+shgtzMLdJ77L4lrj6saBjG+TlY8gVO6qICW4HISv pWOoPFK8OImqdF6Mm6RjSK8n6cV1iG35XrKtZDqpAmJmP8gNIZ9d1BXNmQA737Vf/uykUJP7UJOJt 08k3+wRg==;
Received: from 201.116.77.83.dynamic.wline.res.cust.swisscom.ch ([83.77.116.201]:55969 helo=dretbook.home) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <erik.wilde@dret.net>) id 1d2amA-0000GX-9t; Mon, 24 Apr 2017 05:59:22 -0400
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Herbert Van de Sompel <hvdsomp@gmail.com>, Carsten Bormann <cabo@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com>
Cc: ietf@ietf.org, art@ietf.org, draft-ietf-core-links-json.all@ietf.org, Mark Nottingham <mnot@mnot.net>, "core@ietf.org WG" <core@ietf.org>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net>
Date: Mon, 24 Apr 2017 10:49:03 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_FiKipNSYqbVaUqj7ByBRQ319dI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 10:06:09 -0000

hello.

just adding my voice here and since i am collaborating with herbert on 
this, my position is relatively clear.

On 2017-04-18 14:47, Herbert Van de Sompel wrote:
> 2. Regarding Mark's comment "This means that any constraints upon
> RFC6690 documents are also
> mirrored into these formats": Mark mentions IRIs as a concern. I am also
> concerned about the rules for interpretation of (the Context IRI of)
> links as described in Section 2.1 of 6690
> (https://tools.ietf.org/html/rfc6690#section-2.1). It seems to me that
> these also introduce constraints that go beyond 5988. I may be mistaken
> with that regard because I have never fully understood that section of
> 6690 (i.e. the use of "base URI", "origin", "Context URI"). But, when
> compared to 5988, the section comes across as imposing constraints that
> are intended to allow the straightforward use of relative URIs in
> constrained environments as a means to decrease the payload. If my
> interpretation is correct, then I would very much favor spec-ing the
> json link format in terms of 5988 rather than 6690.

very much agreed, it would be great to have a generic way of serializing 
links as standalone resources (ideally in a way that is able to preserve 
their context, so that relative URIs are well-defined). my concern is 
that RFC 6690 was not intended to do this (it adds constraints to RFC 
5988), and thus draft-ietf-core-links-json has the same limitations.

to be fair, the draft does not intend to define a general-purpose web 
link serialization, it is simply intended as a serialization of the 
specialized model defined in RFC 6690.

i am not sure what the best way forward is. the representations defined 
in this draft are tantalizingly close to general-purpose serializations 
of RFC 5988. but the draft is clearly intended to be (one more) building 
block in the "CoRE-only" universe. two suggestions:

- add language that makes it clear that because of the limitations of 
RFC 6690, the media types in this draft should not be considered as 
general-purpose serializations of web links.

- consider adding a serialization of web links to RFC 5988bis. this 
would address the problem of how to serialize web links outside of the 
HTTP link header field.

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Mon Apr 24 04:53:11 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFF612EBC7; Mon, 24 Apr 2017 04:53:09 -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 3-_A0SSi7VOd; Mon, 24 Apr 2017 04:53:08 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 5D70E127B73; Mon, 24 Apr 2017 04:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3OBqHMr003090; Mon, 24 Apr 2017 13:52:17 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wBPpS6GrhzDHJ4; Mon, 24 Apr 2017 13:52:16 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net>
Date: Mon, 24 Apr 2017 13:52:15 +0200
Cc: Herbert Van de Sompel <hvdsomp@gmail.com>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514727535.684329-be5ad1644b45dde245ba178c864264fa
Content-Transfer-Encoding: quoted-printable
Message-Id: <027F2C41-E498-4801-86E2-047771E10545@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net>
To: Erik Wilde <erik.wilde@dret.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vJqLUl-excInZezlkduqsO5mVV0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 11:53:10 -0000

On Apr 24, 2017, at 10:49, Erik Wilde <erik.wilde@dret.net> wrote:
>=20
> - consider adding a serialization of web links to RFC 5988bis. this =
would address the problem of how to serialize web links outside of the =
HTTP link header field.

Sounds good to me.

What needs to be done to make sure links-json is a proper subset of =
this?

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Apr 24 05:28:47 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28725129584 for <ietf@ietfa.amsl.com>; Mon, 24 Apr 2017 05:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 XZn35iKQ5NFO for <ietf@ietfa.amsl.com>; Mon, 24 Apr 2017 05:28:43 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 7C7081314F9 for <ietf@ietf.org>; Mon, 24 Apr 2017 05:28:41 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id 70so55744107ita.0 for <ietf@ietf.org>; Mon, 24 Apr 2017 05:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2t6ZcEzUQRy9J7ksUnpLE9VvcKxAqn9xaCjmCb8JmM8=; b=XRrdft5rxAJ3DpGNrdp4Kqs1vwIAcnoJ+bNcVwr7XNsY8iZCfJTRMkmGmpqdARADz0 IHBoSM3RJuEijzjkbwFewVqJgQ8tfxJ6FXUFqgy5GiRL5NwNeDUdUkWzkf6omjWVeptF CORGnse+09r/aWcTrfHvfIz6g0yJiVZUwB/1s7UiiLwOcVclzK/ekhmgLV+sKj5J53wf DKSbvWzTQctwOR+8E1mDH6zmOLAG9g4MeRqt2XlT51lZanpnDsheDc3WqfBDBiJ7KcIK R3PnxLSZi+yvkaDCbEuE5c/4jgYAJAnezI3PO+py/WQfdtSEJD14Y8W4YdrdWkhCDdXZ n/3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2t6ZcEzUQRy9J7ksUnpLE9VvcKxAqn9xaCjmCb8JmM8=; b=ecokxi+vKPWV40AEwBWUVQepGbuLwpnFBecRlHszDAkiBYCadVfXzVQgoRYkeCaqH7 zKbJIyg3rRMIMH+SllEpuVMwSONHvcx+oKpw04U2xWUd/xdFHMGFHiin7L7RPFOiXtaU Bb2ytMZj1o6en43vaBkDig9xMhpNySoNk0W4NppmvUYEZBaf9q67pMoDmHLYLJOpHtct fgPgss89OR7Yl9FHKrGgkYNQWOvbqSYApWpsPGxUHL8Q3h/TUjbUpuoT+ugOqjEQQAuJ dqTRuzyUvkwizpzNWtN/Ar1/bw2w7w8NAvgaCyD5ie7h/qBj0N7J2IQ8Pp5wYCAquGWZ EM0w==
X-Gm-Message-State: AN3rC/4lfW26AN2qtbwvKkA+xYgHHChrvUd98SkhFhE7lBLywf3E1KQv 5l+QjcGPEdqS0CFaN9f3kW45aIr6+g==
X-Received: by 10.202.81.83 with SMTP id f80mr13685864oib.9.1493036920889; Mon, 24 Apr 2017 05:28:40 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.22.175 with HTTP; Mon, 24 Apr 2017 05:28:40 -0700 (PDT)
In-Reply-To: <CABkgnnUeoLOm=r1fBXw+r5FZobqHXLSbdQ9q=6i=PYkTEOrdfg@mail.gmail.com>
References: <CABkgnnVmJf66ZJLToFm9_o34P3FswezVRFguuFrgMJeQv_TMgg@mail.gmail.com> <20170421143112.28055.qmail@ary.lan> <CABkgnnUeoLOm=r1fBXw+r5FZobqHXLSbdQ9q=6i=PYkTEOrdfg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 24 Apr 2017 08:28:40 -0400
X-Google-Sender-Auth: 45QqI2jNYQh3jUAyU4hX8TAjfSA
Message-ID: <CAMm+Lwh80TnDmw90zyATyMy3gmK_wE==fZFW1u8qVc0OoLEJ6Q@mail.gmail.com>
Subject: Re: Why are mail servers not also key servers?
To: Martin Thomson <martin.thomson@gmail.com>
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113b06c44e6564054de8bf75
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a150OQQF_YFX9nuTSzVx6GXUqdk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 12:28:45 -0000

--001a113b06c44e6564054de8bf75
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 23, 2017 at 7:31 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 22 April 2017 at 00:31, John Levine <johnl@taugh.com> wrote:
> >>> If a recipient is cooperative, and sends you back a message signed
> >>> with the same key to which you encrypted the message, that tells you
> >>> he got it, but that's not a very interesting case.
> >>
> >>It's also abuse of the cryptographic primitives, I hope that this
> >>isn't really how it works and you are eliding certain key details.
> >
> > It doesn't use the same session key, it uses the same public key.  It's
> > not obvious to me why that would be wrong.
>
> https://tools.ietf.org/html/rfc8017#section-6
>
> If you are using ECDSA/ECDH, then you can also commit the same abuses.
> Historically, keys were saved with an "EC" type, and can be used for
> either interchangeably (the library I work on commits this sin).  In
> the case of EC, there isn't a known path from use of ECDSA to abuse of
> ECDH and vice versa, but it isn't known to be safe either.
>
> This is much harder, if not possible with the X25519/Ed25519 pair,
> because no library will support you in this.
>
>
=E2=80=8BThat isn't actually true. My library supports encryption on the Ed=
25519
curve and it does it for a very specific reason.

The Montgomery curves are only designed to support scalar multiplication,
they don't expose a primitive for point addition because you don't need
that for operations using EC keys. You do need EC addition for operations
on keys however and that is what a lot of my code does.=E2=80=8B

--001a113b06c44e6564054de8bf75
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Ap=
r 23, 2017 at 7:31 PM, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D"mail=
to:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 22=
 April 2017 at 00:31, John Levine &lt;<a href=3D"mailto:johnl@taugh.com">jo=
hnl@taugh.com</a>&gt; wrote:<br>
&gt;&gt;&gt; If a recipient is cooperative, and sends you back a message si=
gned<br>
&gt;&gt;&gt; with the same key to which you encrypted the message, that tel=
ls you<br>
&gt;&gt;&gt; he got it, but that&#39;s not a very interesting case.<br>
&gt;&gt;<br>
&gt;&gt;It&#39;s also abuse of the cryptographic primitives, I hope that th=
is<br>
&gt;&gt;isn&#39;t really how it works and you are eliding certain key detai=
ls.<br>
&gt;<br>
&gt; It doesn&#39;t use the same session key, it uses the same public key.=
=C2=A0 It&#39;s<br>
&gt; not obvious to me why that would be wrong.<br>
<br>
</span><a href=3D"https://tools.ietf.org/html/rfc8017#section-6" rel=3D"nor=
eferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc8017#section=
-6</a><br>
<br>
If you are using ECDSA/ECDH, then you can also commit the same abuses.<br>
Historically, keys were saved with an &quot;EC&quot; type, and can be used =
for<br>
either interchangeably (the library I work on commits this sin).=C2=A0 In<b=
r>
the case of EC, there isn&#39;t a known path from use of ECDSA to abuse of<=
br>
ECDH and vice versa, but it isn&#39;t known to be safe either.<br>
<br>
This is much harder, if not possible with the X25519/Ed25519 pair,<br>
because no library will support you in this.<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra"><div class=3D"gmail=
_default" style=3D"font-size:small">=E2=80=8BThat isn&#39;t actually true. =
My library supports encryption on the Ed25519 curve and it does it for a ve=
ry specific reason.</div><div class=3D"gmail_default" style=3D"font-size:sm=
all"><br></div><div class=3D"gmail_default" style=3D"font-size:small">The M=
ontgomery curves are only designed to support scalar multiplication, they d=
on&#39;t expose a primitive for point addition because you don&#39;t need t=
hat for operations using EC keys. You do need EC addition for operations on=
 keys however and that is what a lot of my code does.=E2=80=8B</div><br></d=
iv></div>

--001a113b06c44e6564054de8bf75--


From nobody Mon Apr 24 05:48:31 2017
Return-Path: <erik.wilde@dret.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891BA13150F; Mon, 24 Apr 2017 05:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.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 w-LpXFH2X_aM; Mon, 24 Apr 2017 05:48:28 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (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 A7C1D131504; Mon, 24 Apr 2017 05:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UC9sWWxKH1eqF2oU21h1VeiNoG4Wqp4yaF7IlyCwuds=; b=ammD7eky36yaO3MZBCm/PYIoXe OXvTk/bIAizfuJX+U9fje4wwZ44IkbN6T4GLktDoq+XQLCk056oBlpMWzM44h1CXp0UANOkcx8D+f 5Drcwi9xvJTaPEdkZNR47vsyJUi7YUw3LtdcqNYeXlRuJqQJnQKnmW32RWhomkrK1NTNYJGlNdwnO aC/iWAlYpxUJTTWAmtJoh8wT88NJofaaoFgQ0KtdKeos2JDJmaGfoBKagUCXzvfAuGHJeD2LF7gSr tTCD8okTDxQtLaHGzAqctuwh3MpI8v1menCmadCB7qXXaB0ag8wd2MqnOEj9D9cz2G92H/NjawinG 0Fm4Np4w==;
Received: from 201.116.77.83.dynamic.wline.res.cust.swisscom.ch ([83.77.116.201]:55922 helo=dretpro.home) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <erik.wilde@dret.net>) id 1d2dPn-0003r7-Np; Mon, 24 Apr 2017 08:48:27 -0400
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Carsten Bormann <cabo@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org>
Cc: Herbert Van de Sompel <hvdsomp@gmail.com>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net>
Date: Mon, 24 Apr 2017 14:48:29 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <027F2C41-E498-4801-86E2-047771E10545@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MtcuGVi6uz1qz0s2C7IgAAMLX5s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 12:48:30 -0000

On 2017-04-24 13:52, Carsten Bormann wrote:
> On Apr 24, 2017, at 10:49, Erik Wilde <erik.wilde@dret.net> wrote:
>> - consider adding a serialization of web links to RFC 5988bis. this would address the problem of how to serialize web links outside of the HTTP link header field.
> Sounds good to me.
> What needs to be done to make sure links-json is a proper subset of this?

hard to tell as "this" is just speculation at this point. generally 
speaking, i don't think it's such a great idea to piggyback on standards 
and then reduce their expressiveness. imho that's one of the well-known 
anti-patterns of interop: (extended) subsets.

but if you're shooting for a subset i think that's where you are right now.

it would be better to make sure that serializations of web links 
actually can represent web links and not just some of the information 
that they convey. that train may have left the station with RFC 6690, 
but maybe for the JSON and CBOR serializations that can be changed.

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Mon Apr 24 05:57:12 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF137128959; Mon, 24 Apr 2017 05:56:50 -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 7vQKb_6jzFps; Mon, 24 Apr 2017 05:56:49 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 7B40E131448; Mon, 24 Apr 2017 05:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3OCtv8U024072; Mon, 24 Apr 2017 14:55:57 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wBRCx27SHzDHKw; Mon, 24 Apr 2017 14:55:57 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net>
Date: Mon, 24 Apr 2017 14:55:56 +0200
Cc: Herbert Van de Sompel <hvdsomp@gmail.com>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514731356.639242-36f7ee4bca0d5a83208bda5fa5f40929
Content-Transfer-Encoding: quoted-printable
Message-Id: <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net>
To: Erik Wilde <erik.wilde@dret.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/16DSuWmtFRIFsXO6MpxPsFfIfWc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 12:56:51 -0000

On Apr 24, 2017, at 14:48, Erik Wilde <erik.wilde@dret.net> wrote:
>=20
> On 2017-04-24 13:52, Carsten Bormann wrote:
>> On Apr 24, 2017, at 10:49, Erik Wilde <erik.wilde@dret.net> wrote:
>>> - consider adding a serialization of web links to RFC 5988bis. this =
would address the problem of how to serialize web links outside of the =
HTTP link header field.
>> Sounds good to me.
>> What needs to be done to make sure links-json is a proper subset of =
this?
>=20
> hard to tell as "this" is just speculation at this point. generally =
speaking, i don't think it's such a great idea to piggyback on standards =
and then reduce their expressiveness. imho that's one of the well-known =
anti-patterns of interop: (extended) subsets.
>=20
> but if you're shooting for a subset i think that's where you are right =
now.
>=20
> it would be better to make sure that serializations of web links =
actually can represent web links and not just some of the information =
that they convey. that train may have left the station with RFC 6690, =
but maybe for the JSON and CBOR serializations that can be changed.

Right.  Can you be more specific what you would want to see here?

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Apr 24 10:12:22 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2468B13189E; Mon, 24 Apr 2017 10:12:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
Date: Mon, 24 Apr 2017 10:12:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fO6eg5P2EyMxboa4C4pyf9PFuVc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 17:12:08 -0000

Reviewer: Stewart Bryant
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc1981bis-??
Reviewer: Stewart Bryant
Review Date: 2017-04-24
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-05-11

Summary: This is can be published as is, but I think could be
improved.

I thank the authors you for dealing with most of my comments in the
previous round.
There are two unaddressed points that the IETF Chair may wish to
consider, and one
that I missed.

Major issues:
The text has a lot of RFC2119 language, but no RFC2119 declaration.
and the document seems inconsistent about when it uses RFC2119
language and
when it does not. This sends a mixed messages to authors if we are not

consistent on this point throughout the RFC Series.

=======

5.3.  Purging stale PMTU information

   Internetwork topology is dynamic; routes change over time.  While
the
   local representation of a path may remain constant, the actual
   path(s) in use may change.  Thus, PMTU information cached by a
node
   can become stale.

   If the stale PMTU value is too large, this will be discovered
almost
   immediately once a large enough packet is sent on the path.  No
such
   mechanism exists for realizing that a stale PMTU value is too
small,
   so an implementation should "age" cached values.  When a PMTU
value
   has not been decreased for a while (on the order of 10 minutes),
the
   PMTU estimate should be set to the MTU of the first-hop link, and
the
   packetization layers should be notified of the change.  This will
   cause the complete Path MTU Discovery process to take place again.

SB> I still worry that the impact of this advice is going to be a
disruption to what might
SB> be a critical service every 10 mins, and wonder if there should be
some advice along the 
SB> lines of noting the importance of service delivery as part of
deciding whether to
SB> test for bigger PMTU vs improving efficiency?

Minor issues:

 A node MUST NOT reduce its estimate of the Path MTU below the IPv6
 minimum link MTU.

SB> I missed this last time.
SB>
SB> Presumably you mean "A node MUST NOT reduce its estimate of the 
SB> Path MTU below the IPv6 minimum link MTU in response to such
SB> a message."
SB> 
SB> Otherwise I would have thought that this was entirely a matter 
SB> for the host whether it wanted to use a Path MTU below the IPv6 
SB> link minimum. Nothing breaks if the host takes a more conservative

SB> decision.
SB> 

Nits/editorial comments:  None.



From nobody Tue Apr 25 05:36:07 2017
Return-Path: <erik.wilde@dret.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B72C12EC88; Tue, 25 Apr 2017 05:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.109
X-Spam-Level: 
X-Spam-Status: No, score=0.109 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.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 I-qJLzjJYjvS; Tue, 25 Apr 2017 05:35:57 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (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 4780A12EC85; Tue, 25 Apr 2017 05:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=zSyfr+bpXj8QAvL2HVJqpDCw/VifG4EMu3P5i8hEDMo=; b=xQlkMleb/tu1ALgiOrSEnFpOsr 9Dtqigqv7Z4hn6MlPZgbCikNn6T/6ZvSUaDhRCo3EC3jYdSdtog0l8BIp37M/0BpaN8wfXqqDRQ2u LdM1jk5pAadGPP8W5423qvHoEYRbj4fTBPbvRnrdljnK2GQpfPJQVP2M/B/s4pEBt4vMbfrNYmWGh bZB3WxJyejzEbTvVyKktj6lCcrSrquFyHfeE7hnTZkLMsnRCkvkfGUAXklQ4S5WsvpK71VePBtnfw rOxQgQwpMo8jLzJfJ4qRlncsfD1S6QFt20R56ivXUHPA84rnucKiYZpFFUOdpuajF8+2+ajTOt6zu n2Cu8wRw==;
Received: from [141.202.54.2] (port=64523 helo=dretpro.local) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <erik.wilde@dret.net>) id 1d2zhD-0007F1-Pv; Tue, 25 Apr 2017 08:35:55 -0400
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Carsten Bormann <cabo@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org>
Cc: Herbert Van de Sompel <hvdsomp@gmail.com>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net>
Date: Tue, 25 Apr 2017 14:35:54 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ATg0oQeK8DcCJOJBWNct9s88-wc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 12:35:58 -0000

hello carsten.

On 2017-04-24 14:55, Carsten Bormann wrote:
>> it would be better to make sure that serializations of web links actually can represent web links and not just some of the information that they convey. that train may have left the station with RFC 6690, but maybe for the JSON and CBOR serializations that can be changed.
> Right.  Can you be more specific what you would want to see here?

two possibilities:

- to do things well it would be better to have web link serializations 
that cover *all* of RFC 5988 (bis). that's a hard thing to do and will 
take a while.

- for the RFC 6690-based variants under consideration right now, it 
would be helpful to very explicitly point out that they are *not* 
general-purpose serializations of web links, but instead inherit the 
limitations of the underlying spec.

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Tue Apr 25 05:50:38 2017
Return-Path: <hvdsomp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3944112EC9D; Tue, 25 Apr 2017 05:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KroGHSiWTdXU; Tue, 25 Apr 2017 05:50:16 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::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 9F78712ECA4; Tue, 25 Apr 2017 05:50:16 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id h123so57648861qke.0; Tue, 25 Apr 2017 05:50:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5qvgovgsEj6145CjlgdjBcvQgNAGxSCzrRrXNZNl+yg=; b=en4ZqxTx6HwDtZVJrXKaZqAZL4rgwCF0hZBzFNG+TWy/Q5H7/tJJk6gdbzXQtgF+0k ZPSH/pbfpN0OP7BZIiaH25NIo6foeaacz/iTmF27FydcDWcbyqvcPX/+was8rLiz9oGc HfEVMsyAojmV97Y+nBI6POpk/vZdZhDBOcoNnMtr/tYpdp1oonBowGGGyLzXqGFAaXbm +YWvLjXyy/hPTUzEeU6FbUyTMLfoKjF5GxP5JNFf4cCWAQfAgRwALHqVjDjqrJFu+4k3 Ph0oD0rwr5J1hoatEVsl/jPg/yFYqZzmO0iAen8Q0tD+tyt8IOyKtI+LAhOiUNh+FUxs GKGQ==
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=5qvgovgsEj6145CjlgdjBcvQgNAGxSCzrRrXNZNl+yg=; b=jrjg3YbimVAV3YV7dGyRY9AABPfyTBoTngHW2s3Euz44iuA+HFEmGUV6lyv5QyePld si7S7Wo1IwLg8SYaQG2yTDM0vTmKo1roZLRaX0uXoXsRhierG5UlKgmgDbLFHlexBpXZ 8gGYXViREtKT34S3AxUE9WBsZ+kBPN1QTX8uxon++sDjo0zhzUPeOn45WjuQ2qMGYnAY 1aMRnIG8zpbZJJ5vBO9vIq6IPhqsJPrz7OBIZUuP503urM2jfEqfkwVDo2gAezKogJ7G itjJAR3rMgMYWe5miKcLtE7i8w8fmdQjMJ9h0zyrFIeWD+WfWDAe2SgP1XbayxnUEQLp oGIA==
X-Gm-Message-State: AN3rC/6uA1gBQZSGOuTwFLeXuTywCV78IrBSdmqMC7wi4gSIdnx/zszS JO9/CpXP/YXeldEnm8alZkBqjRse/Q==
X-Received: by 10.55.41.74 with SMTP id p71mr11448557qkh.110.1493124615856; Tue, 25 Apr 2017 05:50:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.45.162 with HTTP; Tue, 25 Apr 2017 05:50:15 -0700 (PDT)
In-Reply-To: <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net>
From: Herbert Van de Sompel <hvdsomp@gmail.com>
Date: Tue, 25 Apr 2017 14:50:15 +0200
Message-ID: <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com>
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Erik Wilde <erik.wilde@dret.net>
Cc: Carsten Bormann <cabo@tzi.org>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, ietf@ietf.org,  "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org,  Herbert Van de Sompel <hvdsomp@gmail.com>
Content-Type: multipart/alternative; boundary=001a1147acdc557ada054dfd2adc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/enuAToa2Mx_z6gM9lwsXWelZ37A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 12:50:18 -0000

--001a1147acdc557ada054dfd2adc
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 25, 2017 at 2:35 PM, Erik Wilde <erik.wilde@dret.net> wrote:

> hello carsten.
>
> On 2017-04-24 14:55, Carsten Bormann wrote:
>
>> it would be better to make sure that serializations of web links actually
>>> can represent web links and not just some of the information that they
>>> convey. that train may have left the station with RFC 6690, but maybe for
>>> the JSON and CBOR serializations that can be changed.
>>>
>> Right.  Can you be more specific what you would want to see here?
>>
>
> two possibilities:
>
> - to do things well it would be better to have web link serializations
> that cover *all* of RFC 5988 (bis). that's a hard thing to do and will take
> a while.
>
>
As Erik previously indicated, it would be great if this could be done as
part of RFC5988bis.


> - for the RFC 6690-based variants under consideration right now, it would
> be helpful to very explicitly point out that they are *not* general-purpose
> serializations of web links, but instead inherit the limitations of the
> underlying spec.
>
>
That would, indeed, be good. But, in case RFC5988bis would spec a (JSON)
serialization, it seems to me that it would be rather helpful for the CORE
community if the RFC 6690 JSON serialization would be based on it.

Cheers

herbert



>
> cheers,
>
> dret.
>
> --
> erik wilde | mailto:erik.wilde@dret.net |
>            | http://dret.net/netdret    |
>            | http://twitter.com/dret    |
>



-- 
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/
http://orcid.org/0000-0002-0715-6126

==

--001a1147acdc557ada054dfd2adc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Apr 25, 2017 at 2:35 PM, Erik Wilde <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:erik.wilde@dret.net" target=3D"_blank">erik.wilde@dret.net</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hello carst=
en.<span class=3D"gmail-"><br>
<br>
On 2017-04-24 14:55, Carsten Bormann wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">
it would be better to make sure that serializations of web links actually c=
an represent web links and not just some of the information that they conve=
y. that train may have left the station with RFC 6690, but maybe for the JS=
ON and CBOR serializations that can be changed.<br>
</blockquote>
Right.=C2=A0 Can you be more specific what you would want to see here?<br>
</blockquote>
<br></span>
two possibilities:<br>
<br>
- to do things well it would be better to have web link serializations that=
 cover *all* of RFC 5988 (bis). that&#39;s a hard thing to do and will take=
 a while.<br>
<br></blockquote><div><br></div><div>As Erik previously indicated, it would=
 be great if this could be done as part of RFC5988bis.</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
- for the RFC 6690-based variants under consideration right now, it would b=
e helpful to very explicitly point out that they are *not* general-purpose =
serializations of web links, but instead inherit the limitations of the und=
erlying spec.<div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br></div>=
</div></blockquote><div><br></div><div>That would, indeed, be good. But, in=
 case RFC5988bis would spec a (JSON) serialization, it seems to me that it =
would be rather helpful for the CORE community if the RFC 6690 JSON seriali=
zation would be based on it.=C2=A0</div><div><br></div><div>Cheers</div><di=
v><br></div><div>herbert</div><div><br></div><div>=C2=A0</div><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"><div class=3D"gmail-HOEnZb"><div class=
=3D"gmail-h5">
<br>
cheers,<br>
<br>
dret.<br>
<br>
-- <br>
erik wilde | mailto:<a href=3D"mailto:erik.wilde@dret.net" target=3D"_blank=
">erik.wilde@dret.net</a> |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| <a href=3D"http://dret.net/netdr=
et" rel=3D"noreferrer" target=3D"_blank">http://dret.net/netdret</a>=C2=A0 =
=C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| <a href=3D"http://twitter.com/dr=
et" rel=3D"noreferrer" target=3D"_blank">http://twitter.com/dret</a>=C2=A0 =
=C2=A0 |<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature">Herbert Van de Sompel<br>Digital Library Res=
earch &amp; Prototyping<br>Los Alamos National Laboratory, Research Library=
<br><a href=3D"http://public.lanl.gov/herbertv/" target=3D"_blank">http://p=
ublic.lanl.gov/herbertv/</a><br><a href=3D"http://orcid.org/0000-0002-0715-=
6126" target=3D"_blank">http://orcid.org/0000-0002-0715-6126</a><br><br>=3D=
=3D</div>
</div></div>

--001a1147acdc557ada054dfd2adc--


From nobody Tue Apr 25 06:08:03 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342441200FC; Tue, 25 Apr 2017 06:07:51 -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, RCVD_IN_DNSWL_MED=-2.3, 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 JjSJrpLvIKPH; Tue, 25 Apr 2017 06:07:44 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 89573127B57; Tue, 25 Apr 2017 06:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3PD6pKS026446; Tue, 25 Apr 2017 15:06:51 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wC3Q304RBzDHsc; Tue, 25 Apr 2017 15:06:50 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com>
Date: Tue, 25 Apr 2017 15:06:48 +0200
Cc: Erik Wilde <erik.wilde@dret.net>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, IETF <ietf@ietf.org>, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514818407.59117-b4ffb0b6498cf5f580cda089da02173a
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com>
To: Herbert Van de Sompel <hvdsomp@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SlbN5_o1QMIAG3MVwF2H66N33Cw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 13:07:51 -0000

> On Apr 25, 2017, at 14:50, Herbert Van de Sompel <hvdsomp@gmail.com> =
wrote:
>=20
> On Tue, Apr 25, 2017 at 2:35 PM, Erik Wilde <erik.wilde@dret.net> =
wrote:
> hello carsten.
>=20
> On 2017-04-24 14:55, Carsten Bormann wrote:
> it would be better to make sure that serializations of web links =
actually can represent web links and not just some of the information =
that they convey. that train may have left the station with RFC 6690, =
but maybe for the JSON and CBOR serializations that can be changed.
> Right.  Can you be more specific what you would want to see here?
>=20
> two possibilities:
>=20
> - to do things well it would be better to have web link serializations =
that cover *all* of RFC 5988 (bis). that's a hard thing to do and will =
take a while.
>=20
>=20
> As Erik previously indicated, it would be great if this could be done =
as part of RFC5988bis.

Yes.

But covering all of RFC 5988 is mainly hard because of the vagaries of =
HTTP header field encoding.
We don=E2=80=99t have that problem in RFC 6690, so it is easy to have =
RFC 6690 and links-json as a proper subset if we want to.

>  - for the RFC 6690-based variants under consideration right now, it =
would be helpful to very explicitly point out that they are *not* =
general-purpose serializations of web links, but instead inherit the =
limitations of the underlying spec.
>=20
>=20
> That would, indeed, be good. But, in case RFC5988bis would spec a =
(JSON) serialization, it seems to me that it would be rather helpful for =
the CORE community if the RFC 6690 JSON serialization would be based on =
it.=20

I would hope so, but remember that links-json is already out there.

The RFC 6690 JSON serialization is pretty much a no-brainer, and there =
are no obvious ways to do things very different (well, you could choose =
a different name for =E2=80=9Chref=E2=80=9D, but that would not be very =
bright).   CBOR adds a few bike sheds, but these can be painted in the =
same color with little effort.

If a superset RFC 5988 JSON serialization deviates from this (i.e., is =
not a proper superset), I think this would require some willful effort.
(I=E2=80=99m happy to be proven wrong; that=E2=80=99s why I was asking =
if any specifics are known here already.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 25 07:17:06 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC95131452; Tue, 25 Apr 2017 07:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 Kril4VnfMUYW; Tue, 25 Apr 2017 07:16:52 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 CAFD313144B; Tue, 25 Apr 2017 07:16:51 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.18.96; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
In-Reply-To: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Subject: RE: [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
Date: Tue, 25 Apr 2017 10:11:31 -0400
Message-ID: <006201d2bdcd$d8d21e40$8a765ac0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJj1w0Rmgy1J+ijI/wBRaCzRiot8qCz7RLA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aHtkxGWLqgKcv5Gro9CzHSpYves>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 14:16:54 -0000

Dale: 

Thank you for the second review.  I'll address these issues along with
others later today. 

Sue Hares  

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Sunday, April 23, 2017 10:05 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Genart telechat review of
draft-ietf-i2nsf-problem-and-use-cases-12

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair.  Please wait for direction from your document shepherd or AD
before posting a new version of the draft.

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be capitalized.
(Between -11 and -12, one instance of this was fixed, but the other one
remains.)

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such, it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second sentence seems
to mean (though it doesn't say it) is that if you enable a security
function, you don't *know* that the network is protected if you don't have
any monitoring feedback.  (The sentence is stated in terms of whether the
network *is* protected, which it might well be, even if you don't have
monitoring.)  It seems that you need to replace "does not mean that a
network is protected" with something that is more literally correct.

The third sentence is constructed "... to have a mechanism to monitor and
provide execution status of NSFs to ...".  There's an awkwardness that
"monitor" isn't connected to "security and compliance management tools",
whereas "provide ... status ... to" *is* connected; there's a problem that
the "monitor" and "provide" are written as if they're parallel, but they're
not.  I think the wording is less confusing this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security monitoring
interfaces".

3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
some times they're not (two places in 3).

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically run
      to upload or download configuration changes, log information and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of an
XXX", but I'm not familiar enough with the subject to know what XXX is.

[END]


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


From nobody Tue Apr 25 09:47:35 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE8F212EB44; Tue, 25 Apr 2017 09:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 iioN6VG7Bwdt; Tue, 25 Apr 2017 09:47:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 D05CB129A91; Tue, 25 Apr 2017 09:47:24 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.111.164]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LyVcA-1bxQWf3moo-015uEj; Tue, 25 Apr 2017 18:46:24 +0200
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
To: Carsten Bormann <cabo@tzi.org>, Herbert Van de Sompel <hvdsomp@gmail.com>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org>
Cc: IETF <ietf@ietf.org>, art@ietf.org, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>, draft-ietf-core-links-json.all@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de>
Date: Tue, 25 Apr 2017 18:46:24 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:hc2flPMI2xoEM8PXdvVJ6YpBzL4x35h2N/07C+H5n+WlR2ldIsT kOmSrI+bsgT4Zr2SReDzoV6h0XGPB9KeIlENoBW+ruN5PecCWuDh5AC/MWyKv6BWZK/5G4q YSYp5WVzWm32NumtRWf4xkZheeHL3o+l4MKDqimlN0OqV0XZFabIqvVKOaooXtlSbeayoSx FpUUqbFcgrg6X2jkGjX9w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:rOnBY3m5eYo=:Dn2omTrw4EVngdaeIS8U4O FsUn5q/gNf/bFeuoqsHDzWabMr0gCTYHq1TUzCON45WN/EXz1/WaUs0/9Vr79WasGWT6SKLa3 v5st6ds73Ko/tQWgOlBOj23l9xg3f5DVWy9RrqcIBbni+JHuEKCNUWzFZTl/Ba4jB9PQT0vEU MvZu+MVm2FJx3wh3QsT+NZO81uJa1znx6/+YAP4z/mrUZTkz7LFVxaRz0lCS2UZn0eaZ+4nhP E6xJdEvf5RSTNf1ULyaxc+H9WkqWvOgFqN5hbIqdJVJhuVlOJ8vdd9ODneTVtytdM9oGV4/fD +UaIVBv84JUO1Qw3SGDWsYdpEqy7lGrY8GmRJgVWzyOCDHP+90oZUVXcsTLGFLnfvQ2VJ22Ck UWMusunICnLgl06n3MDxRfl1Jd7kpy5EUfVCDq3ngeKVPeBc/Zdan36iVHj7HNxuuGHlDhNhE g1Oy4wzX0qb6nkP4OIXTz5GxurHvU4pI+QG/pCcW4JFC2vk43JQ2Ye/KzGUQBgxEaOkpgfNBZ luiTFhiX4rpnx7EslAUclVX5rleBDIQ9yuoJyTGC0OqGvML4vvqvkq9IFc3fjIh7tPe60hLHv lUVgvjhnAkU/X36omK1pPng8krm4AP3L5usBwfenj8wRDvgVWwj4TOEGoALhp6y0oE5cC4Ecj vhVjrrTvD4wlEWSJT7sQF0t95dzh3JFxNTIkZnnJgjRf9J8xPze302RTZCF0WdJOsuj32HI+y p2T7G9iY9LhAzKrd3N3dq3VZDHIShZ22VJH02iiecsiuyiNOMc/n7OUcPdADQWYMer66wAFVB iVj+FER
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0x5QoT7RFtmbFFsD8LZJcWYwGtc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 16:47:27 -0000

On 2017-04-25 15:06, Carsten Bormann wrote:
>
>> On Apr 25, 2017, at 14:50, Herbert Van de Sompel <hvdsomp@gmail.com> wrote:
>>
>> On Tue, Apr 25, 2017 at 2:35 PM, Erik Wilde <erik.wilde@dret.net> wrote:
>> hello carsten.
>>
>> On 2017-04-24 14:55, Carsten Bormann wrote:
>> it would be better to make sure that serializations of web links actually can represent web links and not just some of the information that they convey. that train may have left the station with RFC 6690, but maybe for the JSON and CBOR serializations that can be changed.
>> Right.  Can you be more specific what you would want to see here?
>>
>> two possibilities:
>>
>> - to do things well it would be better to have web link serializations that cover *all* of RFC 5988 (bis). that's a hard thing to do and will take a while.
>>
>>
>> As Erik previously indicated, it would be great if this could be done as part of RFC5988bis.
>
> Yes.
>
> But covering all of RFC 5988 is mainly hard because of the vagaries of HTTP header field encoding.
 > ...

Do you have a specific problem in mind?

Best regards, Julian





From nobody Tue Apr 25 10:26:56 2017
Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41FE31316D6; Tue, 25 Apr 2017 10:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=nokia.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 z_GVWp4Riwbm; Tue, 25 Apr 2017 10:26:43 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0095.outbound.protection.outlook.com [104.47.2.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A993C129AB2; Tue, 25 Apr 2017 10:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xrSNF8YSOouXuL+jyq4t1k3/OeIaRENSfwVWiYhZrA8=; b=YymU6rOlnl9lJ0zUTOo2j80qbrlZBpPsCle9IVwznqqgS+iiBeGu0GU0hha4HkxUTQL8uPNsAmTX0F4XGqy6z8EY2rRLN5314X13kiucfynCnmPxhE81Fx0/W74M5faXbglZhZ4lLQvaAT+NH2mCsiXb1sfQJG/a9wv2Wfemy9I=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB2455.eurprd07.prod.outlook.com (10.168.75.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.6; Tue, 25 Apr 2017 17:26:40 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) with mapi id 15.01.1061.011; Tue, 25 Apr 2017 17:26:40 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Martin Thomson <martin.thomson@gmail.com>, "art@ietf.org" <art@ietf.org>
CC: "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Subject: RE: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Topic: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Index: AQHSrnqQeK8CFgpYuE64kjZYAubM4qHWYMDg
Date: Tue, 25 Apr 2017 17:26:40 +0000
Message-ID: <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com>
In-Reply-To: <149144445494.22036.11923880719369865745@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.18]
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB2455; 7:1cBM0Up4I8Aer73/BhkQIv3yAD6n2ASwTylLjQluWHeaRDPNfcrHzusxbJXQFKmPrzrJrFCxArvodk3oemsp4BgwdqwFvqV+sK623Vx0vbMXMb24fmdi+g/wfCGdMckVAJEkNT4Iux0xPvULB9vOu2GW9rilBvERAbqAKx8efZDGhsBFn0ZdWrKFaA4L1JRLh50ZD6OtEW7yc8c3Nny0IsUhe9GN9CzBFpZ1OEgZ3AUyUpUcLp8so0q3f+gHhFypypTmYCjwdVtaPBbAKxT63jeBrQORxlebtcSSJrmPPsz6nBN+k0F2d3jAGpXg0FMi73D524iU2DMfMnO8qk9kSA==
x-ms-office365-filtering-correlation-id: 93ceb0cc-8dc0-4a4d-f14a-08d48c003c26
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:DB6PR0701MB2455; 
x-microsoft-antispam-prvs: <DB6PR0701MB245520EF16E78E2FF62B77C1951E0@DB6PR0701MB2455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(131327999870524);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148); SRVR:DB6PR0701MB2455; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2455; 
x-forefront-prvs: 0288CD37D9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39840400002)(39450400003)(39850400002)(39400400002)(39410400002)(13464003)(51444003)(377424004)(2900100001)(6246003)(2501003)(38730400002)(6306002)(6436002)(54906002)(9686003)(189998001)(6506006)(106356001)(53936002)(230783001)(6116002)(3846002)(102836003)(66066001)(99286003)(55016002)(7696004)(3660700001)(122556002)(39060400002)(2950100002)(7736002)(50986999)(76176999)(54356999)(3280700002)(81166006)(2906002)(8936002)(25786009)(8676002)(4326008)(77096006)(74316002)(33656002)(305945005)(345774005)(5660300001)(229853002)(86362001)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2455; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2017 17:26:40.0604 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2455
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uWfJjqmlqifHqDmlrhe51kEChZ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 17:26:46 -0000

SGVsbG8gTWFydGluLCANCg0KRmlyc3Qgb2YgYWxsIHRoYW5rIHlvdSBmb3IgeW91ciB0aG9yb3Vn
aCByZXZpZXcgYW5kIGNvbW1lbnRzLiANCkEgbmV3IHZlcnNpb24gaGFzIGJlZW4gdXBsb2FkZWQg
dG8gYWRkcmVzcyB0aGVtIGFuZCBpcyBhdmFpbGFibGUgYXQgDQpodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWlldGYtYWx0by1tdWx0aS1jb3N0LTA5IA0KSSBob3Bl
IHRoZSB1cGRhdGVzIGFkZHJlc3MgeW91ciBxdWVzdGlvbnMuIFBsZWFzZSwgbGV0IG1lIGtub3cg
b3RoZXJ3aXNlLg0KDQpQbGVhc2Ugc2VlIGFsc28gaW5saW5lIGZvciBteSBhbnN3ZXJzLA0KDQpC
ZXN0IHJlZ2FyZHMsDQpTYWJpbmUNCg0KDQo+Pi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+
PkZyb206IE1hcnRpbiBUaG9tc29uIFttYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tXQ0K
Pj5TZW50OiAwNiBBcHJpbCAyMDE3IDA0OjA4DQo+PlRvOiBhcnRAaWV0Zi5vcmcNCj4+Q2M6IGFs
dG9AaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtYWx0by1tdWx0aS1jb3N0LmFs
bEBpZXRmLm9yZw0KPj5TdWJqZWN0OiBBcnRhcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtYWx0by1tdWx0aS1jb3N0LTA4DQo+Pg0KPj5SZXZpZXdlcjogTWFydGluIFRob21zb24NCj4+
UmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1ZXMNCj4+DQo+PkRvY3VtZW50OiBkcmFmdC1p
ZXRmLWFsdG8tbXVsdGktY29zdC0wOA0KPj5EYXRlOiAyMDE3LTA0LTA2DQo+PlJldmlld2VyOiBN
YXJ0aW4gVGhvbXNvbg0KPj4NCj4+VGhpcyBkb2N1bWVudCBkZXNjcmliZXMgaG93IEFMVE8gY2Fu
IGJlIHVzZWQgdG8gYWNxdWlyZSBjb3N0IG1hcHMgd2l0aA0KPj5tdWx0aXBsZSBjb3N0IG1ldHJp
YyBpbnN0ZWFkIG9mIGEgc2luZ2xlIG1ldHJpYy4NCj4+DQo+PlRoZSBkb2N1bWVudCB2ZXJ5IGNh
cmVmdWxseSBkZWFscyB3aXRoIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5IHdpdGggZXhpc3RpbmcN
Cj4+QUxUTyBzZXJ2ZXJzIGFuZCBjbGllbnRzLiAgSSBkb24ndCBhbnRpY2lwYXRlIG1hbnkgaXNz
dWVzIGFyaXNpbmcgZnJvbSB0aGUNCj4+ZGVwbG95bWVudCBvZiB0aGlzIHByb3RvY29sLg0KPj4N
Cj4+SSBzdGFydGVkIHJlYWRpbmcgLTA3LCBidXQgZmluaXNoZWQgd2l0aCAtMDguICBJIGNoZWNr
ZWQgdGhhdCB0aGUgaXNzdWVzIEkgcmFpc2UNCj4+c3RpbGwgZXhpc3QsIGJ1dCBJJ20gbm90IGlu
ZmFsbGlibGUuICBBcG9sb2dpZXMgaWYgSSBnZXQgc29tZXRoaW5nIHdyb25nLg0KPj4NCj4+TWlu
b3IgaXNzdWVzOiBJJ3ZlIGlkZW50aWZpZWQgYSBmZXcgaXNzdWVzIHRoYXQgYXJlIG1vcmUgdGhh
biBuaXRzLCB0aGVzZSBhcmUNCj4+bWFya2VkICJJTVBPUlRBTlQiIGJlbG93Lg0KPj4NCj4+DQo+
PlRoZSBhYnN0cmFjdCBpbmNsdWRlcyBjb25zaWRlcmFibGUganVzdGlmaWNpYXRpb24uICBBbiBh
YnN0cmFjdCBvbmx5IG5lZWRzIHRvDQo+PmRlc2NyaWJlIHRoZSAqd2hhdCosIG5vdCB0aGUgKndo
eSouICBUaHVzLCB3aGF0IGlzIHRoZXJlIGNvdWxkIGJlIHNpbXBsaWZpZWQNCj4+Y29uc2lkZXJh
Ymx5LCBlLmcuLA0KPj4NCj4+ICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgbmV3IG1ldGhvZCBm
b3IgcmV0cmlldmluZyBtdWx0aXBsZSBjb3N0IG1ldHJpY3MgaW4NCj4+YQ0KPj4gICBzaW5nbGUg
cmVxdWVzdCBmb3IgYW4gQUxUTyBmaWx0ZXJlZCBjb3N0IG1hcC4gIEl0IGFsc28gZGVmaW5lcyBp
bXByb3ZlbWVudHMNCj4+ICAgdG8gdGhlIGNvbnN0cmFpbnRzIHRoYXQgY2FuIGJlIHVzZWQgZm9y
IGZpbHRlcmVkIGNvc3QgbWFwcy4NCg0KW1NSICAgICBdICBPSy4gQWJzdHJhY3Qgc2hvcnRlbmVk
IGluIHRoYXQgZGlyZWN0aW9uDQo+Pg0KPj5TZWN0aW9uIDENCj4+DQo+PlRoZSBpbnRyb2R1Y3Rp
b24gdXNlcyBhIGJ1bmNoIG9mIG9kZCB0ZXJtcy4gIFNvbWUgb2YgdGhlc2UgYXJlIHJlY29nbml6
YWJsZQ0KPj5mcm9tIHRoZSBBTFRPIHNwZWNpZmljYXRpb24sIGJ1dCBzb21lIG9mIHRoZSBqYXJn
b24gc2VlbXMgdW5uZWNlc3NhcnkuICBJbg0KPj5wYXJ0aWN1bGFyLCAiSW50ZXJuZXQgVmlldyIs
ICJQcm92aWRlciBOZXR3b3JrIHJlZ2lvbiIgYW5kICJWZWN0b3IgY29zdHMiLg0KPj5BbGwgb2Yg
d2hpY2ggSSB0aGluayB0aGF0IEkgdW5kZXJzdGFuZCwgYnV0IHRoZXkgbWFrZSB0aGUgZG9jIGhh
cmQgdG8gZm9sbG93Lg0KPj4NCj4+R2VuZXJhbGx5LCBJIGZvdW5kIHRoZSBpbnRyb2R1Y3Rpb24g
cXVpdGUgaGFyZCB0byBmb2xsb3csIGJvdGggZm9yIHRoYXQgcmVhc29uDQo+PmFuZCBzdHJ1Y3R1
cmFsbHkuICBUaGUgaW50cm9kdWN0aW9uIGNvdWxkIGJlIGEgbG90IHNob3J0ZXIgYW5kIG1vcmUN
Cj4+Y29uY2lzZToNCj4+DQo+PjEuIEFMVE8gZGVmaW5lcyBtdWx0aXBsZSBjb3N0IHR5cGVzIChh
bmQgbW9yZSBhcmUgYmVpbmcgZGVmaW5lZCkuDQo+PjIuIENsaWVudHMgc29tZXRpbWVzIGNvbnN1
bWUgbXVsdGlwbGUgY29zdCB0eXBlcy4NCj4+My4gUmVxdWVzdGluZyBtdWx0aXBsZSBjb3N0IHR5
cGVzIGF0IHRoZSBzYW1lIHRpbWUgaXMgbW9yZSBlZmZpY2llbnQgKGZvcg0KPj4gICBzZXZlcmFs
IHJlYXNvbnMpLg0KPj40LiBUaGlzIGRvY3VtZW50IGRlZmluZXMgaG93IHRvIGRvIHRoYXQuDQo+
PjUuIFNlcGFyYXRlbHksIHdoZW4gbXVsdGlwbGUgY29zdCB0eXBlcyBhcmUgcHJlc2VudCwgbW9y
ZSBzb3BoaXN0aWNhdGVkDQo+PiAgIGZpbHRlcmluZyBjYW4gaW1wcm92ZSBlZmZpY2llbmN5IGZ1
cnRoZXIuDQo+PjYuIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBob3cgdG8gZG8gdGhhdCB0b28uDQo+
Pg0KW1NSICAgICBdIE9LLCBzZWN0aW9uIHJldmlzZWQgaW4gdGhhdCBkaXJlY3Rpb24NCg0KPj5T
ZWN0aW9uIDINCj4+DQo+PlRoZXJlIGFyZSBzZXZlcmFsIGl0ZW1zIGluIHRoZSBsaXN0IGhlcmUg
dGhhdCBhcmUgbm90IHVzZWQ6DQo+PkFwcGxpY2F0aW9uIENsaWVudCwNCj4+TmV0d29yayBTZXJ2
aWNlIFByb3ZpZGVyLCBtYXliZSBtb3JlLiAgUGxlYXNlIGNoZWNrIGFuZCByZW1vdmUgdGhvc2UN
Cj4+dGhhdCBkb24ndCBhcHBseS4NCj4+DQpbU1IgICAgIF0gT0s6IHJlbW92ZWQgMyBkZWZpbml0
aW9ucw0KDQo+PlRoZSBSRkMgNzI4NSBzZWN0aW9uIHJlZmVyZW5jZSB0aGluZyBpcyB1bm5lY2Vz
c2FyeS4NCj4+DQpbU1IgICAgIF0gT0s6IG1vdmVkIHRvIGVuZCBvZiBzZWN0aW9uIDIsIHRvIGF2
b2lkIHJlcGVhdGluZyAib2YgW1JGQzcyODVdIiB0b28gb2Z0ZW4uDQoNCj4+VGhpcyBkb2N1bWVu
dCBkb2Vzbid0IGNpdGUgUkZDIDIxMTksIGJ1dCBpdCB1c2VzIHRoZSBrZXl3b3Jkcy4NCltTUiAg
ICAgXSBSRkMgMjExOSBpcyBjaXRlZCBvbiBwYWdlIDEsIHNlY3Rpb24gIiBSZXF1aXJlbWVudHMg
TGFuZ3VhZ2UiIGFuZCBzZWN0aW9uICI5LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcyIuIFNob3Vs
ZCBpdCBiZSByZWZlcmVuY2VkIGVsc2V3aGVyZT8gDQoNCj4+U2VjdGlvbiAzLjENCj4+DQo+PlRo
ZSBleGFtcGxlIHNob3dzIGFuIGVtcHR5IGNvc3QtdHlwZSwgYnV0IHRoZSBzY2hlbWEgeW91IGRl
ZmluZSBhbGxvd3MgaXQNCj4+dG8gYmUgYWJzZW50LiAgWW91IFJFQUxMWSBuZWVkIHRvIHBpY2sg
b25lLiAgSSBkb24ndCBiZWxpZXZlIHRoYXQgdGhpcyBpcyBhDQo+PmNvbXBhdGliaWxpdHkgaXNz
dWU6IG9uY2UgeW91IGhhdmUgZGV0ZXJtaW5lZCB0aGF0IGEgY2xpZW50IHN1cHBvcnRzIG11bHRp
LQ0KPj5jb3N0LCB0aGVuIHlvdSBjYW4gZG8gYW55dGhpbmcgeW91IGxpa2UsIGp1c3QgYmUgY2xl
YXIgYWJvdXQgaXQuDQpbU1IgICAgIF0gT0ssIGFkZGVkIGV4cGxhbmF0aW9ucyBiZWZvcmUgYW5k
IGFmdGVyIHRoZSBleGFtcGxlIA0KPj4NCj4+U2VjdGlvbiAzLjINCj4+DQo+PkkgZm91bmQgdGhl
IGFyZ3VtZW50IGFib3V0IHRoZSBlYXNlIG9mIHdyaXRpbmcgYSBwYXJzZXIgdG8gYmUgcXVpdGUN
Cj4+dW5jb252aW5jaW5nLiAgSG93ZXZlciwgYSBuZXcgbWVkaWEgdHlwZSB0aGF0IGlzIGxhcmdl
bHkgdGhlIHNhbWUgYXMgdGhlDQo+PmV4aXN0aW5nIG1lZGlhIHR5cGUgd29uJ3QgbmVjZXNzYXJp
bHkgcmVzdWx0IGluIGNvZGUgZHVwbGljYXRpb24uDQo+Pg0KPj5KdXN0IHNheSB3aGF0IGl0IGlz
IHlvdSBleHBlY3QgdG8gaGFwcGVuIGFuZCBkb24ndCB0cnkgdG8gYmUgYXBvbG9nZXRpYyBhYm91
dA0KPj5pdC4gIFdoYXQgeW91IGhhdmUgYXBwZWFycyB0byBiZSBhIHdvcmthYmxlIGRlc2lnbi4N
CltTUiAgICAgXSBPSywgcmVtb3ZlZCAxc3QgcGFyYWdyYXBoLg0KPj4NCj4+U2VjdGlvbiAzLjUN
Cj4+DQo+PlRoaXMgc2VjdGlvbiBpcyBjb25mdXNpbmcuICBZb3Ugb25seSBuZWVkIHRvIHNheSB0
aGF0IHlvdSBhcmUgbm90IGFsdGVyaW5nIGZ1bGwNCj4+Y29zdCBtYXAgcmVzb3VyY2VzIGluIGFu
eSB3YXkgYW5kIHRoYXQgY2xpZW50cyBuZWVkIHRvIHVzZSBmaWx0ZXJlZCBjb3N0IG1hcHMNCj4+
aWYgdGhleSB3YW50IG11bHRpcGxlIGNvc3RzIGF0IHRoZSBzYW1lIHRpbWUuICAoT2J2aW91c2x5
IHlvdSBjb3VsZCBoYXZlLCBidXQNCj4+Y3JlYXRpbmcgbXVsdGlwbGUgcmVzb3VyY2VzIHdpdGgg
dGhlIGZ1bGwgY29tYmluYXRvcmlhbCBtZXNzIGNhdXNlZCBieQ0KPj5jb21iaW5pbmcgbWFueSBj
b3N0IHR5cGVzIGlzIHVud2llbGR5LikgIEF0IGEgbWluaW11bSwgdGhlIHNlY29uZA0KPj5wYXJh
Z3JhcGggaGVyZSBjYW4gYmUgcmVtb3ZlZC4NCltTUiAgICAgXSBPSyBzaG9ydGVuZWQgMm5kIHBh
cmFncmFwaA0KPj4NCj4+U2VjdGlvbiAzLjYuMg0KPj4NCj4+SU1QT1JUQU5UOiBZb3UgZG9uJ3Qg
ZGVmaW5lIHdoYXQgaGFwcGVucyB3aGVuIGEgY2xpZW50IHByb3ZpZGVzICJvci0NCj4+Y29uc3Ry
YWludHMiDQo+PmFuZCAiY29uc3RyYWludHMiIGF0IHRoZSBzYW1lIHRpbWUuICBUaGVyZSBhcmUg
c2V2ZXJhbCB2YWxpZCBvcHRpb25zLCBidXQgeW91DQo+Pm5lZWQgdG8gY2hvb3NlLg0KW1NSICAg
ICBdIE9LIGFkZGVkIHRleHQgYXQgdGhlIGVuZCBvbiB3aHkgYSBjbGllbnQgY2Fubm90IHByb3Zp
ZGUgYm90aA0KPj4NCj4+U2VjdGlvbiAzLjYuMw0KPj4NCj4+SXQgaXMgcHJvYmFibHkgd29ydGgg
ZXhwbGljaXRseSBub3RpbmcgdGhhdCBpZiAidGVzdGFibGUtY29zdC10eXBlcyINCj4+ZG9lcyBu
b3QNCj4+aW5jbHVkZSB2YWx1ZXMgZnJvbSAibXVsdGktY29zdC10eXBlcyIsIHRoZW4gdGhvc2Ug
dHlwZXMgY2FuJ3QgYmUgaW5jbHVkZWQgaW4NCj4+ImNvbnN0cmFpbnRzIi8ib3ItY29uc3RyYWlu
dHMiLg0KW1NSICAgICBdIE9LIGFkZGVkIHRoaXMgYWZ0ZXIgMXN0IHBhcmFncmFwaA0KPj4NCj4+
UGxlYXNlIGV4cGxhaW4gdGhlIGRlZmF1bHQgdmFsdWUgZm9yIHRoZSBpbmRleCBmb3IgdGhlICJj
b25zdHJhaW50cyIvIm9yLQ0KPj5jb25zdHJhaW50cyIgZXhwcmVzcyBpbiB0aGlzIHNlY3Rpb24g
aW4gYWRkaXRpb24gdG8gd2hlcmUgaXQgaXMgaGlkZGVuIGluIGEgbm90ZQ0KPj5sYXRlciBpbiB0
aGUgZG9jdW1lbnQuDQpbU1IgICAgIF0gT0ssIG1vdmVkIHRleHQgdG8gZXhhbXBsZSBpbiBzZWN0
aW9uIDUuNA0KPj4NCj4+U2VjdGlvbiAzLjYuNQ0KPj4NCj4+VXBwZXJjYXNlIGZvciAibXVzdCBu
b3QiIGluIHRoZSBzZWNvbmQgcGFyYWdyYXBoLiAgKFRoZSAibWF5IiBsYXRlciBpbiB0aGUNCj4+
cGFyYWdyYXBoIG1pZ2h0IGJlIGJldHRlciBhcyAiY2FuIi4pDQpbU1IgICAgIF0gT0ssIGRvbmUu
IEFsc28gYWRkZWQgYW4gc2VudGVuY2UgaW4gMXN0IHBhcmFncmFwaCB0byBjbGFyaWZ5IGl0LiAN
Cj4+DQo+PkluIHRoZSBleGFtcGxlLCB0aGUgcmVzb3VyY2UgbmFtZWQgImZpbHRlcmVkLW11bHRp
Y29zdC1tYXAiIGlzIHByb3ZpZGVkIGZvcg0KPj5sZWdhY3kgcmVhc29ucyBvbmx5LiAgV2h5IGJv
dGhlciBpbmNsdWRpbmcgIm1heC1jb3N0LXR5cGVzIiBhbmQgImNvc3QtdHlwZS0NCj4+bmFtZXMi
IGF0IGFsbCB3aGVuICJmaWx0ZXJlZC1jb3N0LW1hcC1leHRlbmRlZCIgaW5jbHVkZXMgYWxsIHRo
YXQgYW5kIG1vcmU/DQpbU1IgICAgIF0gT0ssIGJlZm9yZSBleGFtcGxlLCBhZGRlZCB0ZXh0IGV4
cGxhaW5pbmcgd2hlbiBpdCBpcyB1c2VmdWwgdG8gc3BlY2lmeSBib3RoLiANCkFjdHVhbGx5LCAi
Y29zdC10eXBlLW5hbWVzIiBpcyBhbHdheXMgcHJlc2VudCBpbiBmaWx0ZXJlZCBjb3N0IG1hcCBj
YXBhYmlsaXRpZXMuDQo+Pg0KPj5TZWN0aW9uIDQuMS4xDQo+Pg0KPj5UaGUgZGVmaW5pdGlvbiBv
ZiB0aGUgc2NoZW1hIGhlcmUgKGFuZCBsYXRlcikgYWN0dWFsbHkgcmVkZWZpbmVzIHRoZSBvYmpl
Y3QNCj4+Y29tcGxldGVseS4gIEkgZm91bmQgdGhhdCBjb25mdXNpbmcgaW5pdGlhbGx5LiAgSXQg
d291bGQgYmUgZ29vZCB0byBpZGVudGlmeSB0aGUNCj4+KmNoYW5nZXMqIGZyb20gdGhlIGJhc2Ug
c3BlY2lmaWNhdGlvbiBzb21laG93Lg0KW1NSICAgICBdIGluZGVlZC4gSW4gUkZDNzI4NSB7MTEu
My4yLjR9LCBtZW1iZXIgImNvc3QtY29uc3RyYWludHMiIGlzIG5vdCBvcHRpb25hbCBpbiBvYmpl
Y3Qgc3BlY2lmaWNhdGlvbiBidXQgaXMgb3B0aW9uYWwgaW4gdGhlIG1lbWJlciBkZXNjcmlwdGlv
bi4gQWRkZWQgYSBzZW50ZW5jZSBhdCB0aGUgZW5kIG9mIDFzdCBwYXJhZ3JhcGggc3RyZXNzaW5n
IHRoZSBwcmVzZW5jZSBvZiB0aGUgMiBuZXcgbWVtYmVyIGxpc3RlZCBpbiB0aGUgYmVnaW5uaW5n
IG9mIHRoaXMgcGFyYWdyYXBoLiANCkFsc28gYWRkZWQgc29tZSB0ZXh0IGluIGludHJvZHVjdGlv
biBvZiBzZWN0aW9uIDQsIG9uIHRoZSBub3RhdGlvbnMsIGluIHBhcnRpY3VsYXIgIjxtLi5uPiIu
IA0KPj4NCj4+Q2FuIHRlc3RhYmxlLWNvc3QtdHlwZS1uYW1lcyBiZSBwcmVzZW50IGFuZCBlbXB0
eSBpZiBjb3N0LWNvbnN0cmFpbnRzIGlzDQo+PmZhbHNlPw0KPj5UaGUgZmlyc3QgcGFydCBvZiB0
aGUgZGVmaW5pdGlvbiBwZXJtaXRzIHRoYXQsIHRoZSBzZWNvbmQgZm9yYmlkcyBpdC4NCltTUiAg
ICAgXSBUaGUgZmlyc3QgcGFydCBzcGVjaWZpZXMgbWVtYmVyICJ0ZXN0YWJsZS1jb3N0LXR5cGUt
bmFtZXMiIGFzIGhhdmluZyAiPDEuLio+IiBlbGVtZW50cywgaWYgcHJlc2VudC4gIA0KQWRkZWQg
aXRlbSB0byBkZXNjcmliZSAiY29zdC1jb25zdHJhaW50cyIgYW5kIG1vdmVkIHRleHQgZnJvbSAi
dGVzdGFibGUtY29zdC10eXBlLW5hbWVzIiB0aGVyZS4gDQo+Pg0KPj5TZWN0aW9uIDQuMS4yDQo+
Pg0KPj5UaGUgcmVkZWZpbml0aW9uIG9mIFBJREZpbHRlciBpcyB1bm5lY2Vzc2FyeS4NCltTUiAg
ICAgXSBPSywgZGVsZXRlZA0KPj4NCj4+SU1QT1JUQU5UOiBwaWRzIGlzIG9wdGlvbmFsIGluIFJG
QyA3Mjg1LiAgV2h5IHRoZSBjaGFuZ2U/DQpbU1IgICAgIF0gT0ssIGNvcnJlY3RlZCB0aGlzLCBw
aWRzIG9wdGlvbmFsIGFnYWluLiBUaGFua3MgZm9yIGNhdGNoaW5nIHRoaXMuDQo+Pg0KPj5JIGZp
bmQgdGhlIHJlZGVmaW5pdGlvbiBvZiB0aGUgb3B0aW9uYWxpdHkgb2YgY29zdC10eXBlIHRvIGJl
IHdvcnRoeSBvZiBzcGVjaWFsDQo+Pm5vdGUuDQpbU1IgICAgIF0gT0ssIGFkZGVkIHNlbnRlbmNl
IGluIGRlZmluaXRpb24gb2YgImNvc3QtdHlwZSIgbWVtYmVyDQo+Pg0KPj5JbiB0aGUgZGVmaW5p
dGlvbiBvZiAib3ItY29uc3RyYWludHMiLCB5b3UgdXNlIGEgImRhdGFiYXNlIHF1ZXJ5Ig0KPj53
aGVyZSB3b3Jkcw0KPj53b3VsZCBzdWZmaWNlLg0KW1NSICAgICBdIE9LLCByZXBsYWNlZCAiZGF0
YWJhc2UgcXVlcnkiIHdpdGggIndvcmRzIg0KPj4NCj4+U2VjdGlvbiA0LjEuMw0KPj4NCj4+SSBm
aW5kIHRoZSBjaG9pY2Ugb2YgdmFsdWUgZm9yICJjb3N0LXR5cGUiIHRvIGJlIHByb2JsZW1hdGlj
LiAgSXQgaXMgYSBzdHJpbmcgaW4gdGhlDQo+PmJhc2UgcHJvdG9jb2wsIHNvIGNoYW5naW5nIHRv
IGFuIGVtcHR5IG9iamVjdCBpcyBsaWtlbHkgdG8gY2F1c2UgbW9yZSBpc3N1ZXMNCj4+dGhhbiBz
aW1wbHkgb21pdHRpbmcgaXQuDQpbU1IgICAgIF0gQWN0dWFsbHksICJjb3N0LXR5cGUiIGlzIGRl
ZmluZWQgaW4gezEwLjd9IGFzIGFuIG9iamVjdCB1bmxpa2UgImNvc3QtdHlwZS1uYW1lcyIgd2hp
Y2ggaXMgYXJyYXkgb2YgSlNPTlN0cmluZy4NCj4+DQo+PlNlY3Rpb24gNC4yIGNvbnRhaW5zIG1p
c21hdGNoZWQgYnJhY2VzL3BhcmVucyBmb3Igc2VjdGlvbiByZWZlcmVuY2VzLg0KW1NSICAgICBd
IE9LLCBjb3JyZWN0ZWQNCj4+DQo+PlNlY3Rpb24gNC4yLjINCj4+DQo+PklNUE9SVEFOVDogVGhp
cyBwcm92aWRlcyBhIGRlZmluaXRpb24gZm9yIFJlcUZpbHRlcmVkQ29zdE1hcCB0aGF0IGlzIHZl
cnkNCj4+ZGlmZmVyZW50IHRvIHRoYXQgaW4gdGhlIGJhc2Ugc3BlY2lmaWNhdGlvbi4gIEkgdGhp
bmsgdGhhdCB0aGlzIHNob3VsZCBoYXZlIGJlZW4NCj4+UmVxRW5kcG9pbnRDb3N0TWFwLg0KW1NS
ICAgICBdIE9LLCBjb3JyZWN0ZWQgdGhpcyBhbmQgcmVwbGFjZWQgIiBSZXFGaWx0ZXJlZENvc3RN
YXAgIiB3aXRoICJSZXFFbmRwb2ludENvc3RNYXAiLCB0aGFua3MgZm9yIGNhdGNoaW5nIHRoaXMu
DQo+Pg0KPj5BcyBiZWZvcmUsIHJlcGVhdGluZyB0aGUgZGVmaW5pdGlvbiBvZiBFbmRwb2ludEZp
bHRlciBpcyB1bm5lY2Vzc2FyeS4NCltTUiAgICAgXSBPSyBkZWxldGVkDQo+Pg0KPj5TZWN0aW9u
IDQuMi4zIC0gc2VlIGNvbW1lbnQgb24gNC4xLjMNCltTUiAgICAgXSBPSywgcGxlYXNlIHNlZSBt
eSBhbnN3ZXIuDQo+Pg0KPj5TZWN0aW9uIDUNCj4+DQo+Pkkgd291bGQgYmUgbW9yZSBjb21mb3J0
YWJsZSBpZiB0aGUgZXhhbXBsZXMgdXNlZCBvYnZpb3VzbHktc3B1cmlvdXMNCj4+bWV0cmljcyAo
ZS5nLiwgImNhdHRsZS1oZWFkLWNvdW50IiwgInNtZWxsIiwgInNob2Utc2l6ZSIsIGV0Yy4uLikg
dGhhbiB0aGVzZQ0KPj5tZXRyaWNzIHRoYXQgYXJlIHByZXR0eSBwbGF1c2libGUuICBNb3JlIHNv
IHdoZW4geW91IGNsYWltIHRoYXQgdGhleSBhcmUNCj4+d2lkZWx5IHZhbHVlZCwgd2hpY2ggaW1w
bGllcyBzb21lIHNvcnQgb2YgdmFsaWRpdHkuDQpbU1IgICAgIF0gT0ssIHJlcGxhY2VkICJob3Bj
b3VudCIgd2l0aCAic2hvZXNpemUiIGFuZCAiYmFuZHdpZHRoc2NvcmUiIHdpdGggInNjZW5lcnly
YXRlIiBhbmQgYWRhcHRlZCBzZWN0aW9uIGludHJvZHVjdGlvbiBhY2NvcmRpbmdseS4gDQo+Pg0K
Pj5JdCBzaG91bGQgYmUgcmVsYXRpdmVseSBlYXN5IHRvIHBvcHVsYXRlIENvbnRlbnQtTGVuZ3Ro
IG5vdyB0aGF0IHRoZQ0KPj5leGFtcGxlcyBhcmUgImZpbmFsIi4NCltTUiAgICAgXSBPSywgZG9u
ZQ0KPj4NCj4+U2VjdGlvbiA1LjENCj4+DQo+PllvdSBoYXZlIHVubWF0Y2hlZCBicmFjZXMgaW4g
Im1ldGEiIGR1ZSB0byB0aGUgY29tbWVudC4NCltTUiAgICAgXSBPSywgY29ycmVjdGVkIHRoaXMu
IEFsc28gcmVtb3ZlZCB0aGUgY29tbWVudHMgaW4gdGhlIElSRA0KPj4NCj4+U2VjdGlvbiA1LjIN
Cj4+DQo+PkRvIHlvdSB3YW50IHRvIHNob3cgb25lIG9mIHRoZSBleGFtcGxlcyBhcyBoYXZpbmcg
bm8gY29zdCB2YWx1ZXMgYXQgYWxsDQo+PmFjcm9zcyBhbGwgdGhlIGNvc3QgdHlwZXM/DQpbU1Ig
ICAgIF0gT0ssIHVwZGF0ZWQgdGV4dCB0byBzYXkgdGhpcyBvbmx5IGhvbGRzIGJldHdlZW4gUElE
MiBhbmQgUElEMw0KPj4NCg0K


From nobody Tue Apr 25 11:27:04 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73967128616; Tue, 25 Apr 2017 11:26:56 -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, RP_MATCHES_RCVD=-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 V060TpduJo6C; Tue, 25 Apr 2017 11:26:55 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 DCBD212946A; Tue, 25 Apr 2017 11:26:54 -0700 (PDT)
Received: from [128.9.184.33] ([128.9.184.33]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3PIQ1sq026365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Apr 2017 11:26:03 -0700 (PDT)
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Date: Tue, 25 Apr 2017 11:26:00 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U46lN_YIIqWjFJuT14eXqCZWpTI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 18:26:56 -0000

Hi, Stewart,


On 4/24/2017 10:12 AM, Stewart Bryant wrote:
> Minor issues:
>
>  A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>  minimum link MTU.
>
> SB> I missed this last time.
> SB>
> SB> Presumably you mean "A node MUST NOT reduce its estimate of the 
> SB> Path MTU below the IPv6 minimum link MTU in response to such
> SB> a message."
This seems fine to me, FWIW - i.e., limiting the advice in this doc to
the mechanism in  this doc.

> SB> 
> SB> Otherwise I would have thought that this was entirely a matter 
> SB> for the host whether it wanted to use a Path MTU below the IPv6 
> SB> link minimum. Nothing breaks if the host takes a more conservative
> SB> decision.
I don't agree; the host at that point is violating RFC2460. It should
never think that an IPv6 link or path with an MTU below what RFC2460
requires is valid.

Joe


From nobody Tue Apr 25 12:01:37 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C700913178B; Tue, 25 Apr 2017 12:01:20 -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, RCVD_IN_DNSWL_MED=-2.3, 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 X2qMWII5vINR; Tue, 25 Apr 2017 12:01:17 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 1D3EB13178D; Tue, 25 Apr 2017 12:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3PJ014b017046; Tue, 25 Apr 2017 21:00:01 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCCFX5KBpzDJ5m; Tue, 25 Apr 2017 21:00:00 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de>
Date: Tue, 25 Apr 2017 20:59:59 +0200
Cc: Herbert Van de Sompel <hvdsomp@gmail.com>, art@ietf.org, draft-ietf-core-links-json.all@ietf.org, IETF <ietf@ietf.org>, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>
X-Mao-Original-Outgoing-Id: 514839599.587282-cfed82419b35f701b30329893f680c6a
Content-Transfer-Encoding: quoted-printable
Message-Id: <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org> <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iQ3JNFrdPvNkfKN3q7n4_7Hbqmc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 19:01:21 -0000

On Apr 25, 2017, at 18:46, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Do you have a specific problem in mind?

This work was done half a decade ago (May 18, 2012, that is), so I =
don=E2=80=99t remember all the details.
RFC 6690 says:

   In
   order to convert an HTTP Link Header field to this link format, first
   the "Link:" HTTP header is removed, any linear whitespace (LWS) is
   removed, the header value is converted to UTF-8, and any percent-
   encodings are decoded.

So we get rid of all that fun before it becomes RFC 6690 (and CoAP of =
course is all UTF-8 in any case).

So far, we have run into one real case where that approach is a =
limitation, and that is in URIs:

The link

coap://example.com?stupid%3Dkey=3D4711

is not distinguishable from

coap://example.com?stupid=3Dkey=3D4711

(The typical reaction of an implementer is =E2=80=9Cthen don=E2=80=99t =
do that!=E2=80=9D [1,2].)

We know that because the CoAP protocol itself also completely runs in =
the UTF-8 domain (there is no percent encoding on the wire); I=E2=80=99m =
not sure that simplification actually hurt in RFC 6690 use cases yet.

(Note that it is rather likely to see user-visible strings in DNS-SD =
instance names, which turn into =E2=80=9Cins=E2=80=9D link attributes, =
so this is not only a URI/IRI/WVUS [3] issue.)

We don=E2=80=99t have a lot of experience with lingering legacy charsets =
in HTTP headers in the constrained space, so I=E2=80=99m sure there are =
other side effects.

Gr=C3=BC=C3=9Fe, Carsten

[1]: =
http://www.condenaststore.com/-sp/Then-don-t-do-that-New-Yorker-Cartoon-Pr=
ints_i14788077_.htm
[2]: http://www.catb.org/~esr/jargon/html/D/Don-t-do-that-then-.html
[3]: https://url.spec.whatwg.org/#valid-url-string (WHATWG Valid URL =
String, or WVUS for short)


From nobody Tue Apr 25 13:09:50 2017
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D31651294BD; Tue, 25 Apr 2017 13:09:42 -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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 zO3d1RO-ttsv; Tue, 25 Apr 2017 13:09:41 -0700 (PDT)
Received: from homiemail-a42.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 822F2128CD5; Tue, 25 Apr 2017 13:09:41 -0700 (PDT)
Received: from homiemail-a42.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a42.g.dreamhost.com (Postfix) with ESMTP id E59779018A3E; Tue, 25 Apr 2017 13:09:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=768msT/pCVcCIOXkVMHTvPXcNI8=; b=HKj2hRl35LJd8eNI/Hrp1nCP1VC9 LA29bFPPLMxkvx2idjdYgDl1FscwyCbzj6ZyJ98EuSGm9va3KYzrUeT0r47PUZll Zh8l3Hi600mLG6qa4rHfcx8ezTsK3heIvhmXm8KFD+tTPKSAM27Z2FeUCKP5ycJ6 McWkBzelJXKWWPQ=
Received: from [192.168.1.8] (ip68-228-71-159.oc.oc.cox.net [68.228.71.159]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a42.g.dreamhost.com (Postfix) with ESMTPSA id ADC1C9018A3C; Tue, 25 Apr 2017 13:09:40 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org>
Date: Tue, 25 Apr 2017 13:09:40 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF <ietf@ietf.org>, art@ietf.org, draft-ietf-core-links-json.all@ietf.org, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>, Herbert Van de Sompel <hvdsomp@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A43ECEE0-47C8-485C-A9AC-E7890B0A6AA4@gbiv.com>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org> <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de> <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-NrXqeFt46TwRZC3JqwatmdcOOw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 20:09:43 -0000

> On Apr 25, 2017, at 11:59 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Apr 25, 2017, at 18:46, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>>=20
>> Do you have a specific problem in mind?
>=20
> This work was done half a decade ago (May 18, 2012, that is), so I =
don=E2=80=99t remember all the details.
> RFC 6690 says:
>=20
>   In
>   order to convert an HTTP Link Header field to this link format, =
first
>   the "Link:" HTTP header is removed, any linear whitespace (LWS) is
>   removed, the header value is converted to UTF-8, and any percent-
>   encodings are decoded.

Well, that's broken.

> So we get rid of all that fun before it becomes RFC 6690 (and CoAP of =
course is all UTF-8 in any case).
>=20
> So far, we have run into one real case where that approach is a =
limitation, and that is in URIs:
>=20
> The link
>=20
> coap://example.com?stupid%3Dkey=3D4711
>=20
> is not distinguishable from
>=20
> coap://example.com?stupid=3Dkey=3D4711
>=20
> (The typical reaction of an implementer is =E2=80=9Cthen don=E2=80=99t =
do that!=E2=80=9D [1,2].)

That isn't a "limitation".  It's a bug to decode pct-encoded octets in
a URI before decomposing the reference into its parts.  ASCII is already
in UTF-8.  Decoding a pct-encoding doesn't make it "more UTF-8"; it just
means the string is no longer a URI reference.  That's broken.  So =
utterly
broken that it obviously wasn't reviewed by the right people.

> We know that because the CoAP protocol itself also completely runs in =
the UTF-8 domain (there is no percent encoding on the wire); I=E2=80=99m =
not sure that simplification actually hurt in RFC 6690 use cases yet.

*sigh*

....Roy


From nobody Tue Apr 25 14:27:08 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1670D129436; Tue, 25 Apr 2017 14:26:51 -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 lTWt0hOQbt53; Tue, 25 Apr 2017 14:26:43 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 446DA126B6E; Tue, 25 Apr 2017 14:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3PLPnO8005255; Tue, 25 Apr 2017 23:25:49 +0200 (CEST)
Received: from client-0139.vpn.uni-bremen.de (client-0139.vpn.uni-bremen.de [134.102.107.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCGTn2MXhzDJ7X; Tue, 25 Apr 2017 23:25:49 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <A43ECEE0-47C8-485C-A9AC-E7890B0A6AA4@gbiv.com>
Date: Tue, 25 Apr 2017 23:25:48 +0200
Cc: IETF <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, Herbert Van de Sompel <hvdsomp@gmail.com>, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514848348.452778-61494f675340a082fab68f2a595dd329
Content-Transfer-Encoding: quoted-printable
Message-Id: <26C26E7B-24E1-4982-B3D8-9991AA1CC6DF@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org> <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de> <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org> <A43ECEE0-47C8-485C-A9AC-E7890B0A6AA4@gbiv.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UogIo8QgKzJ2dkcQeAxjV6HyajU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 21:26:51 -0000

>> RFC 6690 says:
>>=20
>>  In
>>  order to convert an HTTP Link Header field to this link format, =
first
>>  the "Link:" HTTP header is removed, any linear whitespace (LWS) is
>>  removed, the header value is converted to UTF-8, and any percent-
>>  encodings are decoded.
>=20
> Well, that's broken.

OK, let me start typing that errata report then.

>> coap://example.com?stupid%3Dkey=3D4711
>>=20
>> is not distinguishable from
>>=20
>> coap://example.com?stupid=3Dkey=3D4711
>>=20
>> (The typical reaction of an implementer is =E2=80=9Cthen don=E2=80=99t =
do that!=E2=80=9D [1,2].)
>=20
> That isn't a "limitation=E2=80=9D. =20

For RFC6690 users, it pretty much is, because certain URIs don=E2=80=99t =
work.
They tend to design their URIs in such a way that they do, probably more =
so because these designs are natural for them than because they are =
fully aware of that limitation.

> It's a bug to decode pct-encoded octets in
> a URI before decomposing the reference into its parts. =20

Well, percent-encoding is playing two roles in RFC 3986: hiding =
characters within syntactic elements from their delimiter roles, and =
encoding non-ASCII (and C0 etc.) characters.
The passage I cited from RFC 6690 got nicely rid of the latter, and =
broke the former(*).

> ASCII is already
> in UTF-8.  Decoding a pct-encoding doesn't make it "more UTF-8"; it =
just
> means the string is no longer a URI reference.  That's broken.  So =
utterly
> broken that it obviously wasn't reviewed by the right people.

So what should I write into the errata report?

Or more generally speaking, how should we fix RFC 6690, without creating =
a need for constrained nodes to do full URI processing?

Maybe it is sufficient to document the limitation in the errata, for =
now?

And, more to the point of the subject line, how should we handle this on =
the JSON/CBOR level?

There definitely will be a round-tripping problem with RFC 6690 if the =
URIs collide with the above limitation of RFC 6690.  But that=E2=80=99s =
OK because that defines the subset.

To be more general, not doing any percent-decoding of URIs when creating =
JSON/CBOR from scratch is probably the easy way, but it means that when =
we want to phase out RFC 6690 on the constrained level by replacing it =
with JSON/CBOR, there is additional complexity.  Horribile dictu, but =
maybe IRIs are the right thing to do here.

Gr=C3=BC=C3=9Fe, Carsten

(*) It may be worth pointing out that the amount of breakage here is =
much larger than for CoAP itself, which does the percent-decoding only =
after decomposing a URI into what CoAP considers to be its components, =
so the URI parsing works properly =E2=80=94 coap://example.com/foo%2fbar =
has one path segment, =E2=80=9Cfoo/bar=E2=80=9D.
But the application semantics of hiding application delimiters, which my =
example above is breaking, is not supported in CoAP either.
Some people think that URIs should be carried around in that decomposed =
form throughout the constrained space, and I can=E2=80=99t blame them.
I don=E2=80=99t have data how many URI libraries in active use in the =
non-constrained space get this particular detail right, either.


From nobody Tue Apr 25 15:20:06 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A999413162A; Tue, 25 Apr 2017 15:19:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Elwyn Davies <elwynd@dial.pipex.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
Subject: Genart last call review of draft-ietf-core-links-json-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Date: Tue, 25 Apr 2017 15:19:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YbsU1UNqK5Kd81Heg-uBvSiLi8k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 22:19:54 -0000

Reviewer: Elwyn Davies
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-core-links-json-07
Reviewer: Elwyn Davies
Review Date: 2017-04-25
IETF LC End Date: 2017-04-21
IESG Telechat date: 2017-04-27

Summary:Not ready for publication.  There a number of issues that need
to be addressed  as discussed below.  In particular whether the
formats could be returned as the web link specification instead of RFC
6990 format in response to a GET /.well-known/core request.

Having thought about the quote stripping/addition issue cited in Adam
Roach's DISCUSS, I would take a slightly different view... see below.

Major issues:

Intentions:
Is it one of the intentions of this draft that a server should be able
to return web link descriptions using JSON or CBOR, specifically in
response to GET /.well-known/core?  Content formats for the new
formats are registered (s3.2) - could a user ask for the alternative
formats by specifying at ct filter with the GET request?  It strikes
me that if one has a constrained server of sufficiently limited
capabilities that it wants to use CBOR then having to encode the RFC
6690 format responses for the web links requests is wasting resources.
 Some more thought needs to be given to this as an update to RFC 6690
- If I read correctly, RFC 6690 implicitly requires that a response to
GET /.well-known/core MUST be encoded as described in RFC6690.

Minor issues:
Title:  The document appears only to address the CoRE Web Links format
rather than any other.  Should the title reflect this more precisely,
e.g.,
      Representing CoRE Web Links Format in JSON and CBOR

s1.1: Concerning:
   o  The simplest thing that could possibly work

      *  Do not cater for RFC 5988 complications caused by HTTP
header
         character set issues [RFC2047]

Having ferreted around in RFC 5988 and RFC 2047, I can't see what is
being referred to here.  However, I observe later that the "title*"
attribute (with language specifier) does not appear to be supported
(It is missing from Table 1) - is this what is relevant here? If so it
needs clarification. 
[Aside: I notice that the relevant ABNF in s5 of RFC 5998 is missing
external references to various productions (e.g., ext-value,
quoted-string) that are defined in other documents - in the given
examples RFC 2987, RFC 2616.]

s2.2/s5: This statement:
   The resulting structure can be represented in CDDL
   [I-D.greevenbosch-appsawg-cbor-cddl] as:

requires that the CDDL draft is a normative reference rather than
informative.
[Aside:  Having skimmed the CDDL draft, I am of the opinion that a
good deal more work will be needed to get this ready for publication,
possibly to the extent that the CDDL quoted here becomes invalid. 
Given the simplicity of the specification could it be done without the
use of CDDL?] 

s2.2: There needs to be some discussion of handling of double quoted
and non-double quoted strings during conversion:
I think it works to require that...
>From RFC 6690 to JSON:
- If the parameter value is a double quoted string then it should have
the double quotes stripped, any necessary JSON character encodings
performed and the double quotes repapplied.
- if the parameter value is anything else, then the necessary JSON
character encodings are done and the result enclosed in double
quotes.
[what about % encodings on the RFC 6690 side?]

>From RFC 6690 to CBOR:
- If the parameter value is a double quoted string, the double quotes
are stripped and the result used as the CBOR string type value.
- Otherwise, the parameter value is used as the CBOR string value. 
[what about % encodings on the RFC 6690 side?]

>From JSON to RFC 6690: 
- Remove the double quotes from the JSON string value and do any
necessary decoding and encoding.  Reapply double quotes.  Note that
this may result in values that were originally not enclosed in double
quotes in the RFC 6690 repreentation becoming enclosed in double
quotes. However, [AFAICS] this does not alter the semantics of any of
the predefined parameters.  For example the ABNF productions mean that
ct=40 and ct="40" are equivalent (the second case is needed so that
one can also have ct="40 41 42").  What IS needed is a statement that
this must also apply to any application specific parameters.  For
example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
transforming to "foo":["bar","3"] and then back to
...;foo="bar";foo="3";.. MUST require that the two RFC 6690
representations are equivalent.

>From CBOR to RFC 6690: 
[Essentially the same process - decode/encode and apply double quotes.
The discussion of equivalent semantics is equally applicable.]

The conversion from CBOR to JSON or in reverse is similar. 

s2.3: It is not stated whether a CBOR decoder should accept literal
use of the encodable parameters - i.e., if the encoded CBOR contains [
"href": "/mumble" ] rather than [1 : "mumble£ ] in CDDL format. 
Similarly, should the use of the encoded values be mandatory on the
CBOR encoder?

s2.3, Table 1:  Is the omission of title* from the list of parameter
names deliberate?  If so the omission justifies a note and rationale. 
Clearly the format of the value for a title* parameter is different
from all the others, which may have something to do with this.

s2.3/s5: eEfereences in Table 1 make RFC 7252 and RFC 7641 normative.

Nits/editorial comments: 
s1: s/e.g. /e.g., / (two places)

s1.1: The term "round-tripping" and the associated text are opaque
jargon that would normally  be applied to message transmission round a
loop rather than format conversion.  A more explicit formulation would
help naive readers.  Suggest (if I understand what was intended):
OLD:
   o  Canonical mapping

      *  lossless round-tripping with [RFC6690] and between JSON and
         CBOR

      *  but not trying for bit-preserving (DER-style) round-tripping
NEW:
   o  Canonical mapping

      *  supporting inter-conversion in both directions between any
pair 
         of [RFC6690] format and the CBOR and JSON formats defined
here 
         with unaltered and unambiguous semantics

      *  but not attempting to ensure that a sequence of conversions
from 
         one of the formats through one or both of the others and back
to 
         the original would result in an identical representation
(c.f., 
         as might be achieved by different BER transcoders rather than
by all 
         DER transcoders with ASN.1 [X.690]).
ENDS
This needs an informative reference to X.690 ... but I am not sure
that the DER comparison is essential.

s2.2:  Suggest:
OLD:
   We straightforwardly map:

   o  the outer collection to an array of links;

   o  each link to a JSON object or CBOR map, mapping attribute names
to
      attribute values.

NEW:
   We straightforwardly map:

   o  the outer collection to an array of parameterized web links;

   o  each parameterized web link to a JSON object or CBOR map,
mapping attribute names to
      attribute values.
ENDS

s2.2:
OLD:
The resulting structure can be represented in CDDL
   [I-D.greevenbosch-appsawg-cbor-cddl] as:
NEW:
The resulting structure can be represented in CBOR Data Definition
Language (CDDL)
   [I-D.greevenbosch-appsawg-cbor-cddl] as shown in Figure 1.
 
s2.4: Note that the use of ct=40 in RFC 6690 is an anchronism.  The ct
parameter appeared in earlier versions of the draft that led to RFC
6690 but was moved out to be used more generally in CoAP and is
actually defined in RFC 7252 as mentioned in Table 1 here.  Thus use
of ct=40 in the example copied from RFC 6690 really needs an erratum
for 6690 but that is for another day!   


From nobody Tue Apr 25 16:08:53 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053DB1205F0; Tue, 25 Apr 2017 16:08:39 -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 Tq8gvNDBxS4f; Tue, 25 Apr 2017 16:08:35 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 14F7E126B71; Tue, 25 Apr 2017 16:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3PN8TaM010863; Wed, 26 Apr 2017 01:08:29 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCJmF1FYXzDJ8x; Wed, 26 Apr 2017 01:08:29 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 01:08:28 +0200
Cc: gen-art@ietf.org, ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514854508.320519-706d79887a403956b4df6ab96ff401e3
Content-Transfer-Encoding: quoted-printable
Message-Id: <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UFqVy9nfMdE-OTCFpkiVnmWOGJY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 23:08:39 -0000

Hi Elwyn,

thank you for your review =E2=80=94 that is a lot of good input.

Before I start thinking about fixes for the WG to consider, let me =
comment on a few items:

> Summary:Not ready for publication.  There a number of issues that need
> to be addressed  as discussed below.  In particular whether the
> formats could be returned as the web link specification instead of RFC
> 6990 format in response to a GET /.well-known/core request.
>=20
> Having thought about the quote stripping/addition issue cited in Adam
> Roach's DISCUSS, I would take a slightly different view... see below.
>=20
> Major issues:
>=20
> Intentions:
> Is it one of the intentions of this draft that a server should be able
> to return web link descriptions using JSON or CBOR, specifically in
> response to GET /.well-known/core? =20

Maybe not as much an intention as a possible direction that should =
remain open.

This draft defines two media types.  RFC 6690 defined another media =
type.
=46rom the point of RFC 6690=E2=80=99s registration of =
/.well-known/core, RFC 6690 was the only media type available, so the =
assumption there is that application/link-format is returned.
But if a client sends a CoAP Accept option for one of the two media =
types defined here, that should be returnable, too.
So we probably should say this explicitly (i.e., update RFC 6690 by =
saying this).

> Content formats for the new
> formats are registered (s3.2) - could a user ask for the alternative
> formats by specifying at ct filter with the GET request?  It strikes
> me that if one has a constrained server of sufficiently limited
> capabilities that it wants to use CBOR then having to encode the RFC
> 6690 format responses for the web links requests is wasting resources.
> Some more thought needs to be given to this as an update to RFC 6690
> - If I read correctly, RFC 6690 implicitly requires that a response to
> GET /.well-known/core MUST be encoded as described in RFC6690.

That is one way to read it =E2=80=94 however, if you apply the Web model =
and the fact that the Accept and Content-Format (integer version of =
media type + content coding) options are central to CoAP, a reading that =
RFC 6690 just specifies the initial media type for the well-known URI it =
defines becomes more likely.
But, again, we should make this explicit.

> Minor issues:
> Title:  The document appears only to address the CoRE Web Links format
> rather than any other.  Should the title reflect this more precisely,
> e.g.,
>      Representing CoRE Web Links Format in JSON and CBOR

The RFC editor will force us to expand CoRE.
Probably even simpler:
          Representing
          Constrained RESTful Environments (CoRE) Link Format
	  in JSON and CBOR

(The middle line is the title of RFC 6690.)

> s1.1: Concerning:
>   o  The simplest thing that could possibly work
>=20
>      *  Do not cater for RFC 5988 complications caused by HTTP
> header
>         character set issues [RFC2047]
>=20
> Having ferreted around in RFC 5988 and RFC 2047, I can't see what is
> being referred to here.  However, I observe later that the "title*"
> attribute (with language specifier) does not appear to be supported
> (It is missing from Table 1) - is this what is relevant here? If so it
> needs clarification.=20

Indeed.

> [Aside: I notice that the relevant ABNF in s5 of RFC 5998 is missing
> external references to various productions (e.g., ext-value,
> quoted-string) that are defined in other documents - in the given
> examples RFC 2987, RFC 2616.]
>=20
> s2.2/s5: This statement:
>   The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
>=20
> requires that the CDDL draft is a normative reference rather than
> informative.

Well, this was meant to be interpreted as informative, but maybe that =
should be made more explicit.

> [Aside:  Having skimmed the CDDL draft, I am of the opinion that a
> good deal more work will be needed to get this ready for publication,
> possibly to the extent that the CDDL quoted here becomes invalid.=20

I don=E2=80=99t think so, but we would like to hear this opinion in the =
CBOR WG, where CDDL is being worked on.

> Given the simplicity of the specification could it be done without the
> use of CDDL?]=20

The intention was that all the normative information is in English, =
that=E2=80=99s why the CDDL reference is informative.

> s2.2: There needs to be some discussion of handling of double quoted
> and non-double quoted strings during conversion:
> I think it works to require that...
>> =46rom RFC 6690 to JSON:
> - If the parameter value is a double quoted string then it should have
> the double quotes stripped, any necessary JSON character encodings
> performed and the double quotes repapplied.

That=E2=80=99s not how the spec is written.  The assumption is that you =
already have a JSON or CBOR implementation, so the spec is at the data =
model level; it is not going to tell you how to parse or generate JSON =
or CBOR.  (Parsing and generating does, however, play a role for =
RFC6690.  Compare the example implementation, which is 90 % RFC 6690 =
implementation=E2=80=A6)

> - if the parameter value is anything else, then the necessary JSON
> character encodings are done and the result enclosed in double
> quotes.
> [what about % encodings on the RFC 6690 side?]

We are having a lovely discussion about percent-encoding right now in a =
thread over at art@, ietf@, core@.
Let me cite this part from RFC 6690 so you can share the fun:

   In
   order to convert an HTTP Link Header field to this link format, first
   the "Link:" HTTP header is removed, any linear whitespace (LWS) is
   removed, the header value is converted to UTF-8, and any percent-
   encodings are decoded.

(This obviously creates a limitation on RFC 6690; essentially it can=E2=80=
=99t represent URIs with percent-encoded reserved characters.  Whether =
that limitation should mirror over to the JSON/CBOR side is to be =
discussed in that other discussion.)

>> =46rom RFC 6690 to CBOR:
> - If the parameter value is a double quoted string, the double quotes
> are stripped and the result used as the CBOR string type value.
> - Otherwise, the parameter value is used as the CBOR string value.=20
> [what about % encodings on the RFC 6690 side?]

(See above)

>=20
>> =46rom JSON to RFC 6690:=20
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=3D40 and ct=3D"40" are equivalent (the second case is needed so =
that
> one can also have ct=3D"40 41 42").  What IS needed is a statement =
that
> this must also apply to any application specific parameters. =20

Yes, that was one of the points that Mark=E2=80=99s comments pointed =
out.

> For
> example the case in examples 4 and 5 of ..;foo=3D"bar";foo=3D3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo=3D"bar";foo=3D"3";.. MUST require that the two RFC 6690
> representations are equivalent.

That is essentially an RFC 5988 limitation that RFC 6690 inherits and =
Mark=E2=80=99s RFC5988bis repairs by pretty much stating just this.

>> =46rom CBOR to RFC 6690:=20
> [Essentially the same process - decode/encode and apply double quotes.
> The discussion of equivalent semantics is equally applicable.]
>=20
> The conversion from CBOR to JSON or in reverse is similar.=20

(Ditto)

> s2.3: It is not stated whether a CBOR decoder should accept literal
> use of the encodable parameters - i.e., if the encoded CBOR contains [
> "href": "/mumble" ] rather than [1 : "mumble=C2=A3 ] in CDDL format.=20=


It should not.

   The above specification for JSON could be used as is for the CBOR
   encoding as well.  However, to further reduce message sizes, an extra
   encoding step is performed: "href" and some commonly occurring
   attribute names are encoded as small integers.

The =E2=80=9Cis=E2=80=9D/=E2=80=9Care" should be interpreted as MUST do =
that =E2=80=94 maybe again this needs to be explicit.

Should a links-cbor decoder required to reject those 13 strings?  Hmm.
Interoperability probably says yes, complexity says no.

> Similarly, should the use of the encoded values be mandatory on the
> CBOR encoder?

Yes.

> s2.3, Table 1:  Is the omission of title* from the list of parameter
> names deliberate?  If so the omission justifies a note and rationale.=20=

> Clearly the format of the value for a title* parameter is different
> from all the others, which may have something to do with this.

Yes.  I=E2=80=99m forgetting what title* is being used for over in the =
Big Web, so I=E2=80=99ll have to look this up again.

>=20
> s2.3/s5: eEfereences in Table 1 make RFC 7252 and RFC 7641 normative.

Here, I fully disagree (sorry, pet peeve =E2=80=94 we are way too lax =
with the concept of normative references in the IETF).
When specification B uses a string that is mentioned in specification A, =
without needing anything else from specification A, this doesn=E2=80=99t =
make specification A normative for B.
A is normative if you need to read it to implement B; that is not the =
case here.


> Nits/editorial comments:=20
> s1: s/e.g. /e.g., / (two places)

Thanks, a favorite mistake of this non-native speaker.

> s1.1: The term "round-tripping" and the associated text are opaque
> jargon that would normally  be applied to message transmission round a
> loop rather than format conversion. =20

(Actually, for me that is a term of art in format conversion.  But I =
only have worked on format conversions since 1982 :-)
Yes, we need to avoid jargon.

> A more explicit formulation would
> help naive readers.  Suggest (if I understand what was intended):
> OLD:
>   o  Canonical mapping
>=20
>      *  lossless round-tripping with [RFC6690] and between JSON and
>         CBOR
>=20
>      *  but not trying for bit-preserving (DER-style) round-tripping
> NEW:
>   o  Canonical mapping
>=20
>      *  supporting inter-conversion in both directions between any
> pair=20
>         of [RFC6690] format and the CBOR and JSON formats defined
> here=20
>         with unaltered and unambiguous semantics
>=20
>      *  but not attempting to ensure that a sequence of conversions
> from=20
>         one of the formats through one or both of the others and back
> to=20
>         the original would result in an identical representation
> (c.f.,=20
>         as might be achieved by different BER transcoders rather than
> by all=20
>         DER transcoders with ASN.1 [X.690]).
> ENDS
> This needs an informative reference to X.690 ... but I am not sure
> that the DER comparison is essential.

(I hope, not.  But thanks for the text suggestion, that will certainly =
help.)

> s2.2:  Suggest:
> OLD:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of links;
>=20
>   o  each link to a JSON object or CBOR map, mapping attribute names
> to
>      attribute values.
>=20
> NEW:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of parameterized web links;
>=20
>   o  each parameterized web link to a JSON object or CBOR map,
> mapping attribute names to
>      attribute values.
> ENDS

Hmm, do we need the term =E2=80=9Cparameterized web link=E2=80=9D for =
what most of us call =E2=80=9Clink=E2=80=9D?

> s2.2:
> OLD:
> The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
> NEW:
> The resulting structure can be represented in CBOR Data Definition
> Language (CDDL)
>   [I-D.greevenbosch-appsawg-cbor-cddl] as shown in Figure 1.

Yes.

> s2.4: Note that the use of ct=3D40 in RFC 6690 is an anchronism.  The =
ct
> parameter appeared in earlier versions of the draft that led to RFC
> 6690 but was moved out to be used more generally in CoAP and is
> actually defined in RFC 7252 as mentioned in Table 1 here.  Thus use
> of ct=3D40 in the example copied from RFC 6690 really needs an erratum
> for 6690 but that is for another day!  =20

Actually, not quite, as =E2=80=9Cct=E2=80=9D is deliberately used in RFC =
6690 in an example only =E2=80=94 you wouldn=E2=80=99t look for a =
normative reference to a document defining =E2=80=9Cfoo=E2=80=9D if we =
had used that :-)

Again, thank you for that thoughtful feedback, this will help us =
significantly in making the specification better.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 25 16:27:21 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E288127369 for <ietf@ietfa.amsl.com>; Tue, 25 Apr 2017 16:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=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 luQbbusLguho for <ietf@ietfa.amsl.com>; Tue, 25 Apr 2017 16:27:17 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071037.outbound.protection.outlook.com [40.92.71.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DC2A12EC2F for <ietf@ietf.org>; Tue, 25 Apr 2017 16:27:17 -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; bh=g5FCg9H6jK/zjs+FeWGBu+WHp06OdQVGWtBZdL7ObHk=; b=enF/WKYcvvFnPSBDTdNZ7TL26Z/06ai245efRG//8IqB9fqpnuwMgAi8MWJOn2F1pjXdBWNDuv8BjxM/Mo/BGYEQhpzxYBeZk8RhH6/TlvTaRRPQFgHBJAnBm8pI+GFUqDuAkVpFVbP7BfI4R1cw6/HGKd0EVPP9Y7K4/Q4BipmYhMLShD6WRv5Az3UimcwV7JyvC5J5I+cyeTKkCLE6zjjOOjDnNH0z0ITVIvpDLrnOShdzdoEG9/CGjVd/P34ZP9h3el3PRTYmtq2zzcVhikPD0jHiKlyyt5wzcmIL8jyNrL1OlHAjxtOrU/KchggkxLzdCXbf++BiwMikPViUKg==
Received: from VE1EUR03FT040.eop-EUR03.prod.protection.outlook.com (10.152.18.56) by VE1EUR03HT075.eop-EUR03.prod.protection.outlook.com (10.152.19.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Tue, 25 Apr 2017 23:27:14 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.18.60) by VE1EUR03FT040.mail.protection.outlook.com (10.152.18.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Tue, 25 Apr 2017 23:27:14 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.019; Tue, 25 Apr 2017 23:27:14 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Tue, 25 Apr 2017 23:27:14 +0000
Message-ID: <AM4PR0401MB2241F91F390678CE3C0F3193BD1E0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:396DC7CE5DAD6C8AB459929F62EF4733E71424804E397636667EDF88542D8CE2; UpperCasedChecksum:C68FFB38AA68E82139F6E7CC834EE21065B54ED5C700FB6387F34A9558A37C1D; SizeAsReceived:7884; Count:39
x-tmn: [2eyAMxUTMeqBwQcBZRXnCqvVLbtrr1J0]
x-microsoft-exchange-diagnostics: 1; VE1EUR03HT075; 5:i/0bzK7uAAlQ9TEBin4WBYNTwp9MGWAOHRxtcTsiZCB9fptVolBWPZYjBIxGOIhJEcU8SeLWCseYjNfD9sMV1Udubwufg1G4H5lfzIliMz2N4t/Sb3dcJXj+CovifAjfx1Heb6GJ2jGyBS360ohCtQ==; 24:x3foWzCfl6hELfD5UiSJv+xOKw4ytohsjbdY5bvwsZ44AnEA7KxPOtmS5zcfLUt0HhoUI6RMK4rvgvuXgMIFZDADytJvjLrfRIf0AS3wbxU=; 7:Rc/VGvZZYk03rkfOku02SQmvQlkKZfAHTxzDlLIdEkyztoX9/RmzdfdvDpTEBViL8KDX53mXowijmvAF2X/V/hivvGKwDUtCkkSEU+NXNYNf7rELz7xg/uwNWnpIarxQ67PJTBE5NUjjfqY5qTyPcutSOamJuwC6P8WRRaOeAikFSFTZMP8cuZG2P6EghKso24agQbN6wQgQQW4ScUDVnMVnTAHSJRnTU4fsx5JoJ0+DwtLjsu1vKPcNG5z28xjTIodHs8xqOwt4YJjJ0toT0zuUDCWntc7WTHb82wzLWA1ZF8mKG/RL4IeONxqqfxlM
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR03HT075; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:; 
x-ms-office365-filtering-correlation-id: 7356a2b3-c82d-47e7-8452-08d48c329b33
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:VE1EUR03HT075; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR03HT075; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR03HT075; 
x-forefront-prvs: 0288CD37D9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241F91F390678CE3C0F3193BD1E0AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2017 23:27:14.4799 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR03HT075
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mZldPdkncn8uxUFL7Qb7YGO9Cas>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 23:27:19 -0000

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

Hi All,

I think you all received the notification regarding the KRP ID submission, =
so here is the link for this Internet Draft:

https://datatracker.ietf.org/doc/draft-omar-krp/

For those who are interested in it, you will be welcomed to discuss it dire=
ctly with me.

Looking for your thoughts, suggestions, comments, modifications or any kind=
 of positive participation.

If you are not interested in the idea after reading the draft, please ignor=
e this e-mail.

Best Regards,


--_000_AM4PR0401MB2241F91F390678CE3C0F3193BD1E0AM4PR0401MB2241_
Content-Type: text/html; charset="us-ascii"
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" 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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I think you all received the notification regarding =
the KRP ID submission, so here is the link for this Internet Draft:<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-om=
ar-krp/">https://datatracker.ietf.org/doc/draft-omar-krp/</a><o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For those who are interested in it, you will be welc=
omed to discuss it directly with me.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Looking for your thoughts, suggestions, comments, mo=
difications or any kind of positive participation.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you are not interested in the idea after reading =
the draft, please ignore this e-mail.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_AM4PR0401MB2241F91F390678CE3C0F3193BD1E0AM4PR0401MB2241_--


From nobody Tue Apr 25 23:39:40 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C9B13186C; Tue, 25 Apr 2017 23:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 U3JY-jIw2wGo; Tue, 25 Apr 2017 23:39:24 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::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 E808013186A; Tue, 25 Apr 2017 23:39:09 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id t144so102422483lff.1; Tue, 25 Apr 2017 23:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/D9VKNVJ8QYkQ89Mo4kvOhkroqt7wfnupPkMcBMphpM=; b=Jz8mQqFcl34Ll+z5XLE7rbIftbfdbZS6fBfLRzu5jjHYLIz/jqGfVi4B//sJBiwDDW 8Uha1ZH2bb3uCra5OI0zDVjjcRf7PI19rjC87MGOtvacgDzMsTe5bipWBXMmqXPKFPH/ QTW3EiTTFu4O48Bs9eZFeGNKCZ71IKieCdqNHfb3njAtT3ylWhC/DFF3VkyLF3zXlOBu YPuTBwVkW43H7aFyck6h1SPhzcXCaE3xU+TRZhZSP+IjQSPFncU1WWo0n7J8YEI5ANQO PAb+ks0UsCY2j0gNtqJRE7Fc5f1wg6pd/r3FJIJgMDGZ779p0kto0/tgeF4whyUbSkJe NWuA==
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=/D9VKNVJ8QYkQ89Mo4kvOhkroqt7wfnupPkMcBMphpM=; b=SdOWT44ImTPLWeWIAW1DrxPhJQn5gXH9Wc60ZaUaFjae8tHrR3FyUZ159MPCGr96sI WQZMC95ifedjE4jbdei+2YNyQ2OHpUD48aZ4mayiPMjj9ltp05qr/P48Sa3mXU8s+ti0 3EhIpxGHQHlMOqQ4fYfzZlb6g2hzPkj3j9p1dZagxqAN5y/lwl7KhNfxL58ujnyEdpR7 OSae5wqvIatNBeMI4aE1Jtp13WuXD6ZiY1tXa8XQL+jnnN+nhUq8zVi8QN5Zz/auisbe Jh7Aoxr7a4+XvbauxP3bN1Y+ADm55ALVdEZtR8ymZAIH9Wdez+s+SxmsNYfFdT7qV2iG /Jwg==
X-Gm-Message-State: AN3rC/5Vk8PibYXVTQZhO5HGoLAS/e86plMu1OHlHPRLIJfgZiOE/rtv L0hwZV2rXyGutELMWxZSz6cGBrycmw==
X-Received: by 10.46.21.2 with SMTP id s2mr2644800ljd.50.1493188748139; Tue, 25 Apr 2017 23:39:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.2 with HTTP; Tue, 25 Apr 2017 23:39:07 -0700 (PDT)
In-Reply-To: <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 26 Apr 2017 16:39:07 +1000
Message-ID: <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com>
Subject: Re: Artart telechat review of draft-ietf-alto-multi-cost-08
To: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
Cc: "art@ietf.org" <art@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ctvwNyBMjAQJv-gca4gR3BNB_os>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 06:39:26 -0000

On 26 April 2017 at 03:26, Randriamasy, Sabine (Nokia - FR/Nozay)
<sabine.randriamasy@nokia-bell-labs.com> wrote:
>>>This document doesn't cite RFC 2119, but it uses the keywords.
> [SR     ] RFC 2119 is cited on page 1, section " Requirements Language" and section "9.1.  Normative References". Should it be referenced elsewhere?

The convention is to put those in the body, I missed it in the boilerplate.

I skimmed the other changes, and they look fine.


From nobody Wed Apr 26 00:38:32 2017
Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A44131C14; Wed, 26 Apr 2017 00:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.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 ydjtCvy3xHff; Wed, 26 Apr 2017 00:38:22 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40125.outbound.protection.outlook.com [40.107.4.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C91A131C13; Wed, 26 Apr 2017 00:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YWcG7kBnAZ52eR+8yImeRnsbwaN4vcuIn+Rp8Sy8ydg=; b=Lw9frEDq4sb/gfbUVjd1dyDgYvaNf+ZK6FpRHLMeFHZfMSOMUrtvgEmVLJWMaCaq5DAdtIa2rdyfnoghDL+SPd8RsRQw5xJYe3sg3wkbGtL+JW07kAmpX5wu76RviYxpUIt0AjZmz2AkS/MzhdopvSgNsPOddqIGQ6Kp84IwEf4=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.6; Wed, 26 Apr 2017 07:38:20 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) with mapi id 15.01.1061.011; Wed, 26 Apr 2017 07:38:20 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Martin Thomson <martin.thomson@gmail.com>
CC: "art@ietf.org" <art@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Subject: RE: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Topic: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Index: AQHSrnqQeK8CFgpYuE64kjZYAubM4qHWYMDggADx5oCAABAUYA==
Date: Wed, 26 Apr 2017 07:38:19 +0000
Message-ID: <DB6PR0701MB24546B4B6A323AD5CBB0569695110@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com> <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com>
In-Reply-To: <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [86.242.114.166]
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB2454; 7:KwlDfJIPf1h3NQKPXcDX90PdAateKyw4hKoNjPM52eewKxmGTrOqGzZ8JhmcUWizbLR2i1rL7irxIjsnrs/60GUklqPP6O0JwPwwb2S/SgR9OWpe72a+UwE71s7OSBXsV6zS0As0/rf5LOh2AagNRD8QSTXvZRS+toNaGs1Sr7BTxSnSLUeX5e/R1V28k9P35kwZzl0nBLEcS34F8xh59oJWCPSwxR4vqvURw8MbhAC/Hg7mqyI7nMyE6EYDppAhu0V1Lk/I1Fmur13UbJVq4Ns64WlZLXmOM2xlR3AeujtR+5e9kZn/qVnHVU1kQlMZfvrbsqXJdEls3CWW6VCC8w==
x-ms-office365-filtering-correlation-id: d644fa95-8177-4d45-40ea-08d48c773609
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:DB6PR0701MB2454; 
x-microsoft-antispam-prvs: <DB6PR0701MB2454C698E4E81C55B27912CB95110@DB6PR0701MB2454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(6055026)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148); SRVR:DB6PR0701MB2454; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2454; 
x-forefront-prvs: 0289B6431E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39450400003)(39400400002)(39410400002)(39850400002)(39840400002)(13464003)(24454002)(8936002)(5660300001)(55016002)(54906002)(99286003)(2906002)(8676002)(77096006)(68736007)(81166006)(3280700002)(38730400002)(6506006)(74316002)(305945005)(9686003)(39060400002)(7736002)(81156014)(3660700001)(6436002)(4326008)(33656002)(53936002)(122556002)(2950100002)(6916009)(3846002)(6116002)(102836003)(25786009)(230783001)(2900100001)(50986999)(229853002)(76176999)(54356999)(7696004)(6246003)(66066001)(189998001)(110136004)(86362001)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2454; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Apr 2017 07:38:19.9984 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2454
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KJPr0oGpq2aZ6HNPzcOgnfIyVj4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 07:38:24 -0000

SGVsbG8gTWFydGluLA0KDQpUaGFua3MsIEknbGwgdXBkYXRlIHdpdGggUkZDIDIxMTkgY2l0ZWQg
YXQgYXBwcm9wcmlhdGUgcGxhY2VzIA0KU2FiaW5lDQoNCg0KPj4tLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPj5Gcm9tOiBNYXJ0aW4gVGhvbXNvbiBbbWFpbHRvOm1hcnRpbi50aG9tc29uQGdt
YWlsLmNvbV0NCj4+U2VudDogMjYgQXByaWwgMjAxNyAwODozOQ0KPj5UbzogUmFuZHJpYW1hc3ks
IFNhYmluZSAoTm9raWEgLSBGUi9Ob3pheSkgPHNhYmluZS5yYW5kcmlhbWFzeUBub2tpYS0NCj4+
YmVsbC1sYWJzLmNvbT4NCj4+Q2M6IGFydEBpZXRmLm9yZzsgYWx0b0BpZXRmLm9yZzsgaWV0ZkBp
ZXRmLm9yZzsgZHJhZnQtaWV0Zi1hbHRvLW11bHRpLQ0KPj5jb3N0LmFsbEBpZXRmLm9yZw0KPj5T
dWJqZWN0OiBSZTogQXJ0YXJ0IHRlbGVjaGF0IHJldmlldyBvZiBkcmFmdC1pZXRmLWFsdG8tbXVs
dGktY29zdC0wOA0KPj4NCj4+T24gMjYgQXByaWwgMjAxNyBhdCAwMzoyNiwgUmFuZHJpYW1hc3ks
IFNhYmluZSAoTm9raWEgLSBGUi9Ob3pheSkNCj4+PHNhYmluZS5yYW5kcmlhbWFzeUBub2tpYS1i
ZWxsLWxhYnMuY29tPiB3cm90ZToNCj4+Pj4+VGhpcyBkb2N1bWVudCBkb2Vzbid0IGNpdGUgUkZD
IDIxMTksIGJ1dCBpdCB1c2VzIHRoZSBrZXl3b3Jkcy4NCj4+PiBbU1IgICAgIF0gUkZDIDIxMTkg
aXMgY2l0ZWQgb24gcGFnZSAxLCBzZWN0aW9uICIgUmVxdWlyZW1lbnRzIExhbmd1YWdlIiBhbmQN
Cj4+c2VjdGlvbiAiOS4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMiLiBTaG91bGQgaXQgYmUgcmVm
ZXJlbmNlZCBlbHNld2hlcmU/DQo+Pg0KPj5UaGUgY29udmVudGlvbiBpcyB0byBwdXQgdGhvc2Ug
aW4gdGhlIGJvZHksIEkgbWlzc2VkIGl0IGluIHRoZSBib2lsZXJwbGF0ZS4NCj4+DQo+Pkkgc2tp
bW1lZCB0aGUgb3RoZXIgY2hhbmdlcywgYW5kIHRoZXkgbG9vayBmaW5lLg0K


From nobody Wed Apr 26 01:48:54 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFE3131A10; Wed, 26 Apr 2017 01:48:53 -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 9wWFl6aZayu3; Wed, 26 Apr 2017 01:48:52 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 19730131A12; Wed, 26 Apr 2017 01:48:52 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id l9so19315062wre.1; Wed, 26 Apr 2017 01:48:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=OPpzDn4dLZdj73y5j1tvgCeWiWSxiLQI1WqVx/K5boc=; b=q94HxZQRuMSPwczQZB9fM30LBtX35/tdscfe6z6QHtCAh0C/nZkzyDz0e4nxWJUuYm pRs6xyZa0q/GR0YOcx16NaIO7J+2vxpvptduZxWKn67hmPJZ10KET+4rLkpZlCAFVDyf 3NOSYiLkLkiZGeg67rszTHH/ZIp1tBv9oeQO7zfqs7knHRVLyNfJ1t4OTX1npC9/8ajP broo/Q81BmyVnH1FoMyqIOMLVPthto7GLNVHuwOBJd/YQ5I2Frzvc4bgqQFruh3yCaTG d3drm0OC16Vv9MzPieFKKEX72uFsu8QAY8z7YaBZp7PpkJ7x28tbx+0YwgIBU6MxtI14 0UfQ==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=OPpzDn4dLZdj73y5j1tvgCeWiWSxiLQI1WqVx/K5boc=; b=qP8/wkLxZa35sgnrPv8us9JI3RwoD/cyufwbaTBX7grioj6Rerl52EFBkb8udWZ73b VEYm0FG2qOI9TQ5t/Lbtv1r4gB7JYU7QRrHoUI3Bz9QYoow6RZvInciPnmRUmsA0IA+V ovvq/v7UJW05iqWiMcaMbObdNEIa5Uo6zNKzFx8RVdvM3xwRYCAPsI1OMeX+6jakf6TW 5OlPr1lDv7S/EaWWcEmCMhjWMiyx3t0o/C/OkB9Ra71GruS/zMGWoT0EwwtQ2aLjnzKh v7SeWLYTjdp51psafr9RQc03YbAUeaFa3tLi95TgtLQbKkl0KIeQxumFA6Ew2WA+ILq7 7GjA==
X-Gm-Message-State: AN3rC/50tcG2b6HxoG+cTrlreiGJjeAfZrc+wLRtnUAC/UyyDGxUd/xj 8kTM0WoZ7iLo5odjfms=
X-Received: by 10.223.165.138 with SMTP id g10mr14232293wrc.19.1493196530389;  Wed, 26 Apr 2017 01:48:50 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id m83sm7988509wmc.7.2017.04.26.01.48.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 01:48:49 -0700 (PDT)
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Joe Touch <touch@isi.edu>, gen-art@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com>
Date: Wed, 26 Apr 2017 09:48:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PvaiZ0Um_b0K3KenkWtuiyqUcKQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 08:48:54 -0000

On 25/04/2017 19:26, Joe Touch wrote:
> Hi, Stewart,
>
>
> On 4/24/2017 10:12 AM, Stewart Bryant wrote:
>> Minor issues:
>>
>>   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>   minimum link MTU.
>>
>> SB> I missed this last time.
>> SB>
>> SB> Presumably you mean "A node MUST NOT reduce its estimate of the
>> SB> Path MTU below the IPv6 minimum link MTU in response to such
>> SB> a message."
> This seems fine to me, FWIW - i.e., limiting the advice in this doc to
> the mechanism in  this doc.
>
>> SB>
>> SB> Otherwise I would have thought that this was entirely a matter
>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>> SB> link minimum. Nothing breaks if the host takes a more conservative
>> SB> decision.
> I don't agree; the host at that point is violating RFC2460. It should
> never think that an IPv6 link or path with an MTU below what RFC2460
> requires is valid.
>
> Joe
>

That is as maybe, but a host can do more or less what it wants, so this 
is surely an
unenforceable constraint, or are you telling me that the receiving host 
MUST drop a
fragment that is shorter than this? In which case the question whether 
in practice
they do, and whether such a constraint is reasonable.

- Stewart


From nobody Wed Apr 26 07:07:52 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C32B612EB07 for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:07: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 PffzG8fu9EtD for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:07:46 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBF6F129C27 for <ietf@ietf.org>; Wed, 26 Apr 2017 07:05:00 -0700 (PDT)
Received: from dooku.sandelman.ca (cl-27.chi-03.us.sixxs.net [IPv6:2604:8800:100:1a::2]) by relay.sandelman.ca (Postfix) with ESMTPS id E53DD1F8EE for <ietf@ietf.org>; Wed, 26 Apr 2017 14:04:58 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D8CC358A; Wed, 26 Apr 2017 10:04:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: IAOC requesting input on (potential) meeting cities
In-reply-to: <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Tue, 18 Apr 2017 23:22:54 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 26 Apr 2017 10:04:57 -0400
Message-ID: <28718.1493215497@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QizfDsIxX9pgP4DkHzbcAiLCODM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:07:51 -0000

--=-=-=
Content-Type: text/plain


Toerless Eckert <tte@cs.fau.de> wrote:
    > For example, there is a lot of death by powerpoint in meetings that
    > pushes off high bandwidth discussions ("oh, we're out of time"). AFAIK,
    > most active work on drafts during IETF meeting week happens outside of

I am among those who pushes back on death by powerpoint, so I agree with you
strongly.  Presentations are very easily supported through completely remote
attendance.  Concurrent jabber back-channel discussion among the participants
can often bring out points that are sometimes lost in the foreground presentation.

{Maybe we should dispense with the meeting rooms, just wire the hotel rooms
for GbE, and all be on-site, but "remote".  Then the critical criteria for
which city to meet in is reduced to where the best beer can be had.  (And so
Prague wins?)}

But, on somewhat more serious note [note lack of :-) above], I have been told
the following features about the deathly powerpoints:
  1) provides a record of thoughts for later on.
  2) permits non-english speakers to understand what is being said by
     other non-english speakers!!!
  3) can be pushed through google-translate.
  4) can be read ahead of time by chairs and participants so that they
     can ask intelligent questions, and/or can allocate appropriate amounts
     of time.




--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZAKkJAAoJEJVM4Vb9/EKQpQsH/22vQp8Ee8qj5tMt+gRVDCiz
rOk14VkcVZCB2w5vczaAPXH+w3/YdDwmeKkeCzmMuddIilcekjdlVlLPnAAgL1ux
eLsvP1CaTLIrfTJxTcLfoHtjlz/8uhe6KlrQ4/vKX54nyU0PoUfHXmAE0PBijWU0
MJLsssmTyn+rKSKPkTa5dsDyUFMcPoOwlXoIcizK9i34y2QyHe3ZeAy0A0Bw8+sE
12D3TwznnOZkyCGh8Mvt0bJ/QBOICV8xiXZOoWmCpga7iOYFYRRblTota2iwwD+W
TMdipU9x6jaZVMr3VdD2pcf5TNCyq+gCNSs5Qk0fEkcSxiYLYUOWct7JZdt6ADI=
=GfM4
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 26 07:13:40 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 796C812EAA6 for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:13:38 -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 QVHhRBFRdGrs for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:13:36 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BE4312EB19 for <ietf@ietf.org>; Wed, 26 Apr 2017 07:08:06 -0700 (PDT)
Received: from dooku.sandelman.ca (otwaon0812w-lp140-01-64-229-175-123.dsl.bell.ca [64.229.175.123]) by relay.sandelman.ca (Postfix) with ESMTPS id 3914C1F8EE for <ietf@ietf.org>; Wed, 26 Apr 2017 14:08:05 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 688D2E2; Wed, 26 Apr 2017 10:08:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
In-reply-to: <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
Comments: In-reply-to Bob Hinden <bob.hinden@gmail.com> message dated "Tue, 18 Apr 2017 16:08:46 -0700."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 26 Apr 2017 10:08:04 -0400
Message-ID: <28974.1493215684@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2D4msM_9DLtHnwI0tHFipeWPJRI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:13:38 -0000

--=-=-=
Content-Type: text/plain


Bob Hinden <bob.hinden@gmail.com> wrote:
    > I think the meetings would be a lot more productive if a w.g. could
    > have a meeting at the start of the week, work on the the issues during
    > the week, send updates to the mailing list, have email and face to face
    > discussions, and then have a second session at the end of the week to
    > get consensus.  Clearly, impossible to schedule this with our current
    > number of working groups, but I think it would make for a more
    > productive week.

I have repeatedly suggested this to the IESG, most recently last week...

Every WG gets a 1hr slot Mon/Tue (Wed), with *FULL* consideration of
conflicts.  Then a second (1-2h) slot later in the week, with much more
minimal concern for conflicts.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZAKnEAAoJEJVM4Vb9/EKQ3SUH/i0qJsdXQGQuRra2oL/w8YFg
zCFKLPL4OVh5RP9BoMOYSY78eWWhfryizTp8J9qfu/X7cOSjxtKs5eoUz338UMPv
l3pr/Vs5467Y124HY/oGh8zooMXg1YaB1z1hyDs6kVGBWhmgI01Q+NLu3Q2I9FV7
fi1+TuuUew+/UsI4ukDoD7ZPD078ZwVKq07JLfga758zCHwAnidaWigxDwdi62Nx
4uKAYXH6rJURFqSJbLxYwSCNB3fs1cOJXvh7thVR7CmNgoE4Kp9+RQHP9djdnAwU
Yp6T/AwSItPmASmbxoOorNZmfbkQVyUYLyx2qyMoa7Xt/ObD18kQ1Z2SzBEdJbw=
=ppqC
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 26 07:23:58 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BAB12EC3D for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 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_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 cMD9X7t6izRY for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:23:55 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 2C17212E855 for <ietf@ietf.org>; Wed, 26 Apr 2017 07:17:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 143491000320; Wed, 26 Apr 2017 07:17:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1493216236; bh=h5BjmB+LWZ0h4ogV8yXQnhtekjbMTonW1AMRxpFrtkQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=epzyqkdHwDgvgNgspiz4Fd5jARAE0kT27UpTiOc610FZ7n0c99Wh+2wt0m9j6VVlw SJMO0xQNq/+IqXLEPw2Ih+xh9U1OLnM/UNgingSiN0Aya35DiEamdLSaLR2IR8Fc9V xI9TOWNwNJ85J+lNV1xjGsGoU5rqgxMDnyJdZ97k=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [195.50.183.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 32A62240C4F; Wed, 26 Apr 2017 07:17:15 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <28718.1493215497@dooku.sandelman.ca>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b13a768b-fc53-21f3-9e26-d27f16a32433@joelhalpern.com>
Date: Wed, 26 Apr 2017 10:17:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <28718.1493215497@dooku.sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pSQ_8przL0d84VnYUmEBSs6I5pg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:23:57 -0000

Whether in the IETF or elsewhere, there is one aspect you do not mention 
that I find useful asa presenter, and one aspect that I find useful in 
well-done presentations as a participant.

1) As a Presenter, if I have managed to do my presentation right, it 
helps me get the important points covered in the right order.  yes, I 
usually remember them.  But not always.  And it helps in getting back on 
track after useful discussions of particular points.

2) As a participant, I find it very helpful if the slide tells me what 
the presenter considers the critical points for me to think about. 
(There are also the not uncommon cases where a diagram helps me 
understand the point the speaker is trying to make.)

Yours,
Joel

On 4/26/17 10:04 AM, Michael Richardson wrote:
>
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > For example, there is a lot of death by powerpoint in meetings that
>     > pushes off high bandwidth discussions ("oh, we're out of time"). AFAIK,
>     > most active work on drafts during IETF meeting week happens outside of
>
> I am among those who pushes back on death by powerpoint, so I agree with you
> strongly.  Presentations are very easily supported through completely remote
> attendance.  Concurrent jabber back-channel discussion among the participants
> can often bring out points that are sometimes lost in the foreground presentation.
>
> {Maybe we should dispense with the meeting rooms, just wire the hotel rooms
> for GbE, and all be on-site, but "remote".  Then the critical criteria for
> which city to meet in is reduced to where the best beer can be had.  (And so
> Prague wins?)}
>
> But, on somewhat more serious note [note lack of :-) above], I have been told
> the following features about the deathly powerpoints:
>   1) provides a record of thoughts for later on.
>   2) permits non-english speakers to understand what is being said by
>      other non-english speakers!!!
>   3) can be pushed through google-translate.
>   4) can be read ahead of time by chairs and participants so that they
>      can ask intelligent questions, and/or can allocate appropriate amounts
>      of time.
>
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>


From nobody Wed Apr 26 08:53:05 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00FE131476; Wed, 26 Apr 2017 08:52:50 -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 rHfLtRPALlI5; Wed, 26 Apr 2017 08:52:48 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 57BED131460; Wed, 26 Apr 2017 08:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3QFpku5028088; Wed, 26 Apr 2017 17:51:46 +0200 (CEST)
Received: from client-0227.vpn.uni-bremen.de (client-0227.vpn.uni-bremen.de [134.102.107.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCl1s6lR2zDH15; Wed, 26 Apr 2017 17:51:45 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <26C26E7B-24E1-4982-B3D8-9991AA1CC6DF@tzi.org>
Date: Wed, 26 Apr 2017 17:51:45 +0200
Cc: IETF <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, draft-ietf-core-links-json.all@ietf.org, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>, Herbert Van de Sompel <hvdsomp@gmail.com>
X-Mao-Original-Outgoing-Id: 514914705.088075-62d7dcc2c4f9f617e52eb3a25c091a6c
Content-Transfer-Encoding: quoted-printable
Message-Id: <FEA936B1-3DCE-4376-8E0D-0C57202FF777@tzi.org>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org> <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de> <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org> <A43ECEE0-47C8-485C-A9AC-E7890B0A6AA4@gbiv.com> <26C26E7B-24E1-4982-B3D8-9991AA1CC6DF@tzi.org>
To: "Roy T. Fielding" <fielding@gbiv.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hWTboRcybcEyyn-WAcigZ-5pbu0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 15:52:51 -0000

On Apr 25, 2017, at 23:25, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> OK, let me start typing that errata report then.

Below is a draft errata report.

Is this information correct?
Is it sufficient?

Obviously, this errata report doesn=E2=80=99t by itself answer the =
important questions raised about links-json, but it might be a useful =
outcome of this discussion anyway.

Gr=C3=BC=C3=9Fe, Carsten



Report Errata for RFC6690

Date:	2017-04-26
Name:	Carsten Bormann
Email:	cabo@tzi.org
Type:	Editorial
Section:	2

Original Text:

   [...] In
   order to convert an HTTP Link Header field to this link format, first
   the "Link:" HTTP header is removed, any linear whitespace (LWS) is
   removed, the header value is converted to UTF-8, and any percent-
   encodings are decoded.

Corrected Text:

   (add after unchanged original text:)

   Note that this percent-decoding damages URIs that percent-encode
   reserved characters (i.e., characters out of ":/?#[]@!$&'()*+,;=3D",
   not including the double quotes).  Such URIs therefore generally
   cannot be successfully used with RFC 6690 link-format.

Notes:

   Fully percent-decoding URIs before placing them into the
   link-format reduces complexity in processing link-format, but
   creates a limitation on the set of URIs that link-format faithfully
   can represent.  This may not be as widely known as is desirable,
   creating a pitfall for unwitting users of RFC 6990.



From nobody Wed Apr 26 09:05:52 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 960B11300E8; Wed, 26 Apr 2017 09:05:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Subject: Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 09:05:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dYA5wzh3FujjKp3PQGghiJ7febo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:05:22 -0000

Reviewer: Robert Sparks
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
Reviewer: Robert Sparks
Review Date: 2017-04-26
IETF LC End Date: 2017-05-02
IESG Telechat date: Not scheduled for a telechat

Summary: Essentially Ready for publication as an Informational RFC,
but with some minor issues to address before publication

This document is (with exceptions noted below) straightforward and
easy to follow

Minor Issues:

Section 8 is very confusing - I suspect it has been made so by
removing things that were in it earlier. Right now it claims to
provide additional tests, but the only content is about testing things
with firewalls, along with a statement that this document is only
targeting network devices that do not have a firewall function. I
think you can keep most of the text here (except the statement that
you aren't talking about things with firewalls) and remove the
confusion by changing the section heading to something like "Tests in
the presence of a firewall function".

It's unclear how to apply the formula in Section 10.2.1 to the results
that come out of, say, Section 7.3.2, where you are reporting a
(minimum, median, maximum) tuple. Some discussion about the
applicability of the tests where you recommend against reporting a
single number to the methods in this section would help. It would also
help to point out that the Xpd result can be go negative (it will go
negative for things that become smaller as the number of flows
increase, and positive for things that get bigger). If I read this
correctly, if throughput (for example) goes to 0 as n increases, Xpd
will go to -100%. Similary if latency doubles as n increases, Xpd will
go to +100% (and will go to +200% if latency triples).

Nits:

There are several places where you point to Section 6 where I think
you meant to point to Section 7. See the Procedure: line in 10.2.1 for
an example. Also make sure 9 is correct where you say "Sections 6
through 9" in section 12.

Please double-check that you meant "larger MTU" in the last paragraph
of 5.1. It might be correct, but I find the paragraph confusing.

In 8.1 you meant to point to 5.2, not 5.3

Please try to simplify this sentence: 
  "The duration of each trial SHOULD be at least 60 seconds to reduce
the potential gain of a DNS64 server, which is able to exhibit higher
performance by storing the requests and thus utilizing also the
timeout time for answering them."

(Style comment - please feel free to ignore): Consider deleting "as
well" everywhere it occurs in the document - most of the places it is
used, the sentence works just as well, and sometimes better, without
it.

Typos:
end of section 5.1.1: Appendix A1 should be Appendix A
please remove the comma in the first sentence of the second paragraph
of section 5.2



From nobody Wed Apr 26 09:27:44 2017
Return-Path: <sarah.banks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF73131491; Wed, 26 Apr 2017 09:27:41 -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 UngOZXbxf_3e; Wed, 26 Apr 2017 09:27:39 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::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 196D0124B0A; Wed, 26 Apr 2017 09:27:36 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id m34so1441646oik.2; Wed, 26 Apr 2017 09:27:36 -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 :content-transfer-encoding:message-id:references:to; bh=IKasMraTRyvHWJ8U7oqEhFKH4QCq8fy89khGsA2KoEA=; b=q+Khg7PM6cHv+h6kIywxgD3N625KZZ+0dgw/qFTDraneg+3tohcuDHhLcDyidvxRaW VeKtoKnGUEWVqzdpwe7qYxS5gbh8PXMMkYCLW1FYRwJQB/5JLTezRgimyQ813GB8DjeS rgU0uLip2qVlgdbuk7JPaC+h3riN6K7UVy14Gp8B6nZ4sixtdCxPd7bRxuLYdCGDiGNh p/YKXKYJo/nOzDb7TTKASrmqkKLDoJnS4gUnsoL7AU08hssnUMTeezHlCE1DmOVbDtX1 s+VKscfvOQlQ3y8Cr/Q/i8OLjC0YfNhb83k2ndhf/iFpJQye7mEzXypibG8asHfCFg6K KKHg==
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 :content-transfer-encoding:message-id:references:to; bh=IKasMraTRyvHWJ8U7oqEhFKH4QCq8fy89khGsA2KoEA=; b=Ooc4CkMXonMYH9V0F8ELNksjQFeG7/wbzvAVdFy8dDBjt4Wsc//O/8ju2D2khD89Et 1rq/boqVlAxXViOlfXz1Fi1Duage+k9Rh60TdYz+AfELueqeJ7yaz5tsNxgefiOH883R zwUl/dRZ81BW16q52bVkxNOf3Bx3gI+Ofq3yM9Ko3qRkEXQ1/Ma3RK43qgtwzn0xJ9AB /eBoXPXIPHjwwdicueTKOetinkmywsh8p+8S/BpFQzkisgb26vGoVCoFf1XAchiwTVq0 ZZNkkSEBtpA9RalZPq67OGS7PVnI5vScR18777hstl4ev3PFcDy9GdVmwHmjKSgmCQs/ QIxA==
X-Gm-Message-State: AN3rC/62HfgqOSf85sOZzfuiVkfmCfuyXhEabmdTDcDk2Vo5xUiGrNui xwFVYsu+NdaR/e0pytQ=
X-Received: by 10.157.49.17 with SMTP id e17mr405178otc.42.1493224055173; Wed, 26 Apr 2017 09:27:35 -0700 (PDT)
Received: from [10.211.187.101] (mobile-166-176-123-51.mycingular.net. [166.176.123.51]) by smtp.gmail.com with ESMTPSA id j51sm291042otc.47.2017.04.26.09.27.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 09:27:34 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [bmwg] Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
From: Sarah Banks <sarah.banks@gmail.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 12:27:33 -0400
Cc: gen-art@ietf.org, draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <85B5ED62-14E2-4103-9B59-20DAA8763E01@gmail.com>
References: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TQX-GCMY9yXhZfK6b0FOUMWZk9s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:27:41 -0000

Hi Robert,
    Thank you for your review; we appreciate your time and comments, and the=
 authors will review in due course.=20

Thanks
Sarah

> On Apr 26, 2017, at 12:05 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
> Reviewer: Robert Sparks
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
> Reviewer: Robert Sparks
> Review Date: 2017-04-26
> IETF LC End Date: 2017-05-02
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Essentially Ready for publication as an Informational RFC,
> but with some minor issues to address before publication
>=20
> This document is (with exceptions noted below) straightforward and
> easy to follow
>=20
> Minor Issues:
>=20
> Section 8 is very confusing - I suspect it has been made so by
> removing things that were in it earlier. Right now it claims to
> provide additional tests, but the only content is about testing things
> with firewalls, along with a statement that this document is only
> targeting network devices that do not have a firewall function. I
> think you can keep most of the text here (except the statement that
> you aren't talking about things with firewalls) and remove the
> confusion by changing the section heading to something like "Tests in
> the presence of a firewall function".
>=20
> It's unclear how to apply the formula in Section 10.2.1 to the results
> that come out of, say, Section 7.3.2, where you are reporting a
> (minimum, median, maximum) tuple. Some discussion about the
> applicability of the tests where you recommend against reporting a
> single number to the methods in this section would help. It would also
> help to point out that the Xpd result can be go negative (it will go
> negative for things that become smaller as the number of flows
> increase, and positive for things that get bigger). If I read this
> correctly, if throughput (for example) goes to 0 as n increases, Xpd
> will go to -100%. Similary if latency doubles as n increases, Xpd will
> go to +100% (and will go to +200% if latency triples).
>=20
> Nits:
>=20
> There are several places where you point to Section 6 where I think
> you meant to point to Section 7. See the Procedure: line in 10.2.1 for
> an example. Also make sure 9 is correct where you say "Sections 6
> through 9" in section 12.
>=20
> Please double-check that you meant "larger MTU" in the last paragraph
> of 5.1. It might be correct, but I find the paragraph confusing.
>=20
> In 8.1 you meant to point to 5.2, not 5.3
>=20
> Please try to simplify this sentence:=20
>  "The duration of each trial SHOULD be at least 60 seconds to reduce
> the potential gain of a DNS64 server, which is able to exhibit higher
> performance by storing the requests and thus utilizing also the
> timeout time for answering them."
>=20
> (Style comment - please feel free to ignore): Consider deleting "as
> well" everywhere it occurs in the document - most of the places it is
> used, the sentence works just as well, and sometimes better, without
> it.
>=20
> Typos:
> end of section 5.1.1: Appendix A1 should be Appendix A
> please remove the comma in the first sentence of the second paragraph
> of section 5.2
>=20
>=20
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://www.ietf.org/mailman/listinfo/bmwg


From nobody Wed Apr 26 10:12:18 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D71A12EE44; Wed, 26 Apr 2017 10:12:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Cc: draft-ietf-rtgwg-yang-key-chain.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
Subject: Genart telechat review of draft-ietf-rtgwg-yang-key-chain-20
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149322673002.13018.17056147061701748095@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 10:12:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wBz3sk44Fpfi4cQernaKiHnObyc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:12:10 -0000

Reviewer: Matthew Miller
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rtgwg-yang-key-chain-??
Reviewer: Matthew Miller
Review Date: 2017-04-26
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-27

Summary:

This document is ready to be published as Proposed Standard.  This
version (-20) addresses all concerns raised in the review of a
previous version (-17).

Major issues: NONE

Minor issues: NONE

Nits/editorial comments:  NONE



From nobody Wed Apr 26 10:13:02 2017
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9432712955D; Wed, 26 Apr 2017 10:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 CsqE8Dichnhf; Wed, 26 Apr 2017 10:12:54 -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 ACCBB131544; Wed, 26 Apr 2017 10:12:54 -0700 (PDT)
Received: from Orochi.local (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 v3QHCgq7059727 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Apr 2017 12:12:43 -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 Orochi.local
Subject: Re: Genart last call review of draft-ietf-core-links-json-07
To: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 12:12:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
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/ietf/AW-dD99pPJvtjyZY6Epz0d5gKZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:12:56 -0000

On 4/25/17 17:19, Elwyn Davies wrote:
> >From JSON to RFC 6690: 
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=40 and ct="40" are equivalent (the second case is needed so that
> one can also have ct="40 41 42").  What IS needed is a statement that
> this must also apply to any application specific parameters.  For
> example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo="bar";foo="3";.. MUST require that the two RFC 6690
> representations are equivalent.


This has the reciprocal problem that using quotes with (e.g.) sz and 
hreflang is a violation of the ABNF in RFC6690.

/a


From nobody Wed Apr 26 11:21:06 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE9C13156A; Wed, 26 Apr 2017 11:20:58 -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 4yTDYMOUd1-9; Wed, 26 Apr 2017 11:20:55 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 40982131565; Wed, 26 Apr 2017 11:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3QIKnc6028132; Wed, 26 Apr 2017 20:20:49 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCpKs0RWgzDH41; Wed, 26 Apr 2017 20:20:49 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 20:20:47 +0200
Cc: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514923647.182059-f87b135b40f402b437f2bb96c0d3467d
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6D9E89E-2D94-401C-9B00-84CE7E36657C@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com> <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vueh-BPnVqylBQkYYv8nAQZ6Cpw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 18:20:58 -0000

On Apr 26, 2017, at 19:12, Adam Roach <adam@nostrum.com> wrote:
>=20
> This has the reciprocal problem that using quotes with (e.g.) sz and =
hreflang is a violation of the ABNF in RFC6690.

Yes.  Using ABNF for the serialization of an item that should be =
described at the data model level (as in 5988bis) is now generally =
considered a mistake.  To stay compatible with the letter of RFC 6690 =
(which probably continues to be a good idea), the reference =
implementation in Appendix A of links-json uses the quote-less form =
whenever the value is a ptoken, i.e. a sequence of one or more =
ptokenchar characters(*).  Should we require this, and if yes, should =
this be a SHOULD or a MUST?

Gr=C3=BC=C3=9Fe, Carsten

(*)
    ptoken         =3D 1*ptokenchar
    ptokenchar     =3D "!" / "#" / "$" / "%" / "&" / "'" / "("
                   / ")" / "*" / "+" / "-" / "." / "/" / DIGIT
                   / ":" / "<" / "=3D" / ">" / "?" / "@" / ALPHA
                   / "[" / "]" / "^" / "_" / "`" / "{" / "|"
                   / "}" / "~"


From nobody Wed Apr 26 11:35:44 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07FF4131586; Wed, 26 Apr 2017 11:35:43 -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, RP_MATCHES_RCVD=-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 XcqK_u85ov-y; Wed, 26 Apr 2017 11:35:40 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 B1782131582; Wed, 26 Apr 2017 11:35:40 -0700 (PDT)
Received: from [128.9.184.33] ([128.9.184.33]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3QIZDKk005153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 11:35:13 -0700 (PDT)
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
Date: Wed, 26 Apr 2017 11:35:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jxx03e8soAW17CWogz2RBVaPacs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 18:35:43 -0000

Hi, Stewart,


On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>
>
> On 25/04/2017 19:26, Joe Touch wrote:
>> Hi, Stewart,
>>
>> ...
>>
>>> SB>
>>> SB> Otherwise I would have thought that this was entirely a matter
>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>> SB> decision.
>> I don't agree; the host at that point is violating RFC2460. It should
>> never think that an IPv6 link or path with an MTU below what RFC2460
>> requires is valid.
>>
>> Joe
>>
>
> That is as maybe, but a host can do more or less what it wants, so
> this is surely an
> unenforceable constraint, or are you telling me that the receiving
> host MUST drop a
> fragment that is shorter than this? In which case the question whether
> in practice
> they do, and whether such a constraint is reasonable.

A "path MTU" is a value calculated from information from various sources
(attached links, ICMP messages, and perhaps other information), but IMO
it's never appropriate to set a "path MTU" smaller than the limit
established by IPv6 for a single link.

Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.

Joe


From nobody Wed Apr 26 13:09:04 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5ABA12EB55; Wed, 26 Apr 2017 13:08:38 -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 Wxfv12-ExCL2; Wed, 26 Apr 2017 13:08:37 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::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 925CB1294A9; Wed, 26 Apr 2017 13:08:31 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id g12so1450040wrg.2; Wed, 26 Apr 2017 13:08:31 -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 :content-transfer-encoding:message-id:references:to; bh=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Ai/urVsadKiIfFc6DOvBt563jFnPvN0xV4kTW14eAA5w2aoUYKHsG6UysZW6RCNdjl it9eBmgWpfqdumyzKJU0JnsdO8KVHkG/Fvx2KfLlF/mswmu4wU49XhznVKZOxrxwomKZ BfuT7/wcMR6G/0Gh2afvMzfyxhHbG3kDX1bWPSMc0WOn/85Tke6DCMqJxl4nxPe9wNHL VfTRcsr34/6g4fGKimDMCmunu13xs7SgTc5FVgbXyDQhT4FeR4x+pIDBRsWIP3kDrKT7 D7hOKIqRNqFts6NZReAKFujY8JuoPwaEq4z7sU1jYfA0krr391veCHWS3v4sArR2+KeZ RP7Q==
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 :content-transfer-encoding:message-id:references:to; bh=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Bju76Gica9+F0AH9R1ABK11P9S3Obf8C8krFHIUf+OZ1N16ZRjrKxA6t9vISWcBwdG s6voANOYt3ud3aUA/GqwQ5o/laI79Cawc9+6mDNtpkTi6vUZAxmK03ot01JRTRZ63uDv aj8deDH+dv7d7kHvvK65VLVJ5YMkUsWaCltSD2EqQ0OIAMn4OBr7JeM2aodc2PvQ+Eze wya0CbIadG5V0yvCX4KUos8t/8U77/NPz33O9q0+nptxs3bZgo2Zbsf/Bl/ycx/lqNR4 kAls4T8JpDfwi9sQkkdk4wrrGjC+rmt9eGiXcnQ4h7RahgTgFsRPPjy/112SkfNn9TeT TbnA==
X-Gm-Message-State: AN3rC/4usKrtpzWbHh1OPG4u9RO73sBHOmpCrVVux7TOqExoMs9FwICn AqOVQS3Yaw83CVoOSAM=
X-Received: by 10.223.154.240 with SMTP id a103mr1018926wrc.5.1493237310104; Wed, 26 Apr 2017 13:08:30 -0700 (PDT)
Received: from 202.66.20.149.in-addr.arpa (202.66.20.149.in-addr.arpa. [149.20.66.202]) by smtp.gmail.com with ESMTPSA id 39sm280734wru.50.2017.04.26.13.08.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:08:29 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
Date: Wed, 26 Apr 2017 13:08:25 -0700
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nfuO80OUMzKzs9Y91iXm39l09_A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:08:39 -0000

> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>=20
> Hi, Stewart,
>=20
>=20
> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>=20
>>=20
>> On 25/04/2017 19:26, Joe Touch wrote:
>>> Hi, Stewart,
>>>=20
>>> ...
>>>=20
>>>> SB>
>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>> SB> link minimum. Nothing breaks if the host takes a more =
conservative
>>>> SB> decision.
>>> I don't agree; the host at that point is violating RFC2460. It =
should
>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>> requires is valid.
>>>=20
>>> Joe
>>>=20
>>=20
>> That is as maybe, but a host can do more or less what it wants, so
>> this is surely an
>> unenforceable constraint, or are you telling me that the receiving
>> host MUST drop a
>> fragment that is shorter than this? In which case the question =
whether
>> in practice
>> they do, and whether such a constraint is reasonable.
>=20
> A "path MTU" is a value calculated from information from various =
sources
> (attached links, ICMP messages, and perhaps other information), but =
IMO
> it's never appropriate to set a "path MTU" smaller than the limit
> established by IPv6 for a single link.

You are, of course, quoting RFC 1981:
   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

> Individual packets and fragments can be smaller than the MTU, of =
course.
> Nothing forces fragments to push up against any MTU limit at all. But =
I
> would not describe that has a host changing its path MTU; it's just
> sending packets.

I disagree, both on the definition and the action. You are correct in =
"how the Path MTU is calculated". But the Path MTU, by definition, is =
the largest packet that can be sent end to end under current routing =
conditions. It is not, actually, an IP concept: it's a TCP concept if =
anything, or a transport layer concept (if UDP ever decides to have =
one). I can imagine TCP probing the Path MTU by trying packets that are =
larger than its current estimate to see if the estimate is still =
accurate (1981 section 4), but I can't imagine any reason that TCP would =
send packets larger than the "largest packet that can be sent end to end =
under current routing conditions" in the normal case, as those packets =
will by definition either be fragmented or not arrive.


From nobody Wed Apr 26 13:18:53 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48EE13144C; Wed, 26 Apr 2017 13:18:41 -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, RP_MATCHES_RCVD=-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 FtEpxc8LSQFm; Wed, 26 Apr 2017 13:18:39 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 440E21314D6; Wed, 26 Apr 2017 13:18:25 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v3QKIBwB000870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 13:18:11 -0700 (PDT)
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <b1a1dba3-4d8f-4fb7-984f-5fd4689069f9@isi.edu>
Date: Wed, 26 Apr 2017 13:18:11 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Content-Type: multipart/alternative; boundary="------------9304196B38F0127139E7B07B"
Content-Language: en-US
X-MailScanner-ID: v3QKIBwB000870
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zb5Gh9N-fZ0_sjwMqV2HF7SU0do>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:18:42 -0000

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

Hi, Fred,


On 4/26/2017 1:08 PM, Fred Baker wrote:
>> Individual packets and fragments can be smaller than the MTU, of course.
>> Nothing forces fragments to push up against any MTU limit at all. But I
>> would not describe that has a host changing its path MTU; it's just
>> sending packets.
> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). 
While it might apply differently based on port-based routing, path MTU
is an IP concept. It sets IP limits (MTU is an IP-ism, including all its
variants, such as EMTU_S, EMTUR, etc. - from RFC1122), which then
cascades into TCP limits (MSS and MMS_*, again per RFC1122).

And it's not the largest packet - it's strictly the largest IP fragment.
Transport uses that as the limit on IP messages to avoid fragmentation.
Technically, though, PMTU could also be used by the IP layer to guide
source fragmentation if the transport layer presents messages that are
too large to fit in a single datagram.

> I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
TCP probably wouldn't, but UDP can, would, and does.

Joe



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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi, Fred,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 4/26/2017 1:08 PM, Fred Baker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.
</pre>
      </blockquote>
      <pre wrap="">I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). </pre>
    </blockquote>
    While it might apply differently based on port-based routing, path
    MTU is an IP concept. It sets IP limits (MTU is an IP-ism, including
    all its variants, such as EMTU_S, EMTUR, etc. - from RFC1122), which
    then cascades into TCP limits (MSS and MMS_*, again per RFC1122). <br>
    <br>
    And it's not the largest packet - it's strictly the largest IP
    fragment. Transport uses that as the limit on IP messages to avoid
    fragmentation. Technically, though, PMTU could also be used by the
    IP layer to guide source fragmentation if the transport layer
    presents messages that are too large to fit in a single datagram.<br>
    <br>
    <blockquote type="cite"
      cite="mid:99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com">
      <pre wrap="">I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.</pre>
    </blockquote>
    TCP probably wouldn't, but UDP can, would, and does.<br>
    <br>
    Joe<br>
    <pre wrap="">
</pre>
    <br>
  </body>
</html>

--------------9304196B38F0127139E7B07B--


From nobody Wed Apr 26 13:30:18 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606FF12778D; Wed, 26 Apr 2017 13:30:16 -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 yVwXCARIihF3; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 98562127342; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: by mail-pf0-x243.google.com with SMTP id c198so2441387pfc.0; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ymWQklo4o9ij64ii/b86yWzGhaOzaFyAGJZ/J4JYBLE=; b=sQeaVh2FsTQDRk20qfOBW1igbOt+ANsnOafDOcPDBPvsTXc8+0dKeXdiaViPn+SmYo 3X5D62xxbKresEHJpzsCAQer6bx8vQeVHut0OHBMytple68v0kt8m6B05uBisj8RzKEB 770QN5f1FeCepeoKCRUF8ZoJu2di0FZ9rqEkQe1LWc+3bot5r+9ln0gnRfViYgJe60VD L8yR329zH0wGELlfD7nYLIvHMiBu4juR9DxZipIBhwX8KP17TIdTv+X/4Gt3IrIlBQIt 9P4L4dzeCCqN1q1/s4hCfL+bVqkeHeDEYyBDjMYNwC5/LNMPrzfFrGcwXMGWLn7/+0Ne fWYQ==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ymWQklo4o9ij64ii/b86yWzGhaOzaFyAGJZ/J4JYBLE=; b=DBWpTLnsL9qR0N4Vtf9pMGyt+oPo410S54a3dbGaUDDpNsamK28XE7pChlR8tEUxfB 5xTt6bfgPBYbkEWOKTvZh6sw8Ps2s2sWnZkbwCt4agpAHJdeoMtgFfgtMMQeTOVInthb uS0msE6V9DLd3kvbapSXFb3tTDEByB7wYuomO8vo4uAEaQ0gWnTI9Lolg2JszGX3cVDT XmzlSVE3tEhfGfOkOiXxPXMw+52rxTzKGEWuhaM4Onm6t2slLee0P7ca8scCHqJrej7W iYVFPOaNpPkeecL9OF0I11IpzRLkRusf0tFJnBp3Ohk26mJyyyHpe7+8JTCdaTYGm7Y7 8SOA==
X-Gm-Message-State: AN3rC/540o9QkrrRT6bTmNvL0DbVW5IwVAf3Kxrg+IP2biZSs/QvtVOU dDlfKTqz6xnQ3A==
X-Received: by 10.84.217.215 with SMTP id d23mr2189439plj.59.1493238613087; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: from [192.168.178.21] ([118.149.100.28]) by smtp.gmail.com with ESMTPSA id 17sm259899pgg.48.2017.04.26.13.30.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:30:12 -0700 (PDT)
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Fred Baker <fredbaker.ietf@gmail.com>, Joe Touch <touch@isi.edu>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Date: Thu, 27 Apr 2017 08:30:12 +1200
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: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gx9_VpgZIw5jpvh_fa6HUuSI0Yc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:30:16 -0000

On 27/04/2017 08:08, Fred Baker wrote:
> 
>> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>>
>> Hi, Stewart,
>>
>>
>> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>>
>>>
>>> On 25/04/2017 19:26, Joe Touch wrote:
>>>> Hi, Stewart,
>>>>
>>>> ...
>>>>
>>>>> SB>
>>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>>>> SB> decision.
>>>> I don't agree; the host at that point is violating RFC2460. It should
>>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>>> requires is valid.
>>>>
>>>> Joe
>>>>
>>>
>>> That is as maybe, but a host can do more or less what it wants, so
>>> this is surely an
>>> unenforceable constraint, or are you telling me that the receiving
>>> host MUST drop a
>>> fragment that is shorter than this? In which case the question whether
>>> in practice
>>> they do, and whether such a constraint is reasonable.
>>
>> A "path MTU" is a value calculated from information from various sources
>> (attached links, ICMP messages, and perhaps other information), but IMO
>> it's never appropriate to set a "path MTU" smaller than the limit
>> established by IPv6 for a single link.
> 
> You are, of course, quoting RFC 1981:
>    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>    minimum link MTU.
> 
>> Individual packets and fragments can be smaller than the MTU, of course.
>> Nothing forces fragments to push up against any MTU limit at all. But I
>> would not describe that has a host changing its path MTU; it's just
>> sending packets.
> 
> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.

istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?

    Brian


From nobody Wed Apr 26 13:34:09 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CFE1294AB; Wed, 26 Apr 2017 13:34:07 -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, RP_MATCHES_RCVD=-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 ulEldP2NKcW2; Wed, 26 Apr 2017 13:34:06 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 1BAE9129464; Wed, 26 Apr 2017 13:34:06 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v3QKXrTa006565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 13:33:53 -0700 (PDT)
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <c1888839-94fb-437c-a9af-e8309308cc8b@isi.edu>
Date: Wed, 26 Apr 2017 13:33:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Content-Type: multipart/alternative; boundary="------------7459DC2F1AB0CBA15FBD1564"
Content-Language: en-US
X-MailScanner-ID: v3QKXrTa006565
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pJKrWT2uB7aEjHh-QWoCRhrMNvY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:34:08 -0000

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



On 4/26/2017 1:30 PM, Brian E Carpenter wrote:
>>> Individual packets and fragments can be smaller than the MTU, of course.
>>> Nothing forces fragments to push up against any MTU limit at all. But I
>>> would not describe that has a host changing its path MTU; it's just
>>> sending packets.
>> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
> istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?
IMO, the best thing is to loudly flag the path as no longer valid.

Either we have required minimums or not. If not, then we have a LOT of
new work to do.

Joe


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

<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 4/26/2017 1:30 PM, Brian E Carpenter
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com">
      <blockquote type="cite" style="color: #000000;">
        <blockquote type="cite" style="color: #000000;">
          <pre wrap="">Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.
</pre>
        </blockquote>
        <pre wrap="">I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
</pre>
      </blockquote>
      <pre wrap="">istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?</pre>
    </blockquote>
    IMO, the best thing is to loudly flag the path as no longer valid.<br>
    <br>
    Either we have required minimums or not. If not, then we have a LOT
    of new work to do.<br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------7459DC2F1AB0CBA15FBD1564--


From nobody Wed Apr 26 13:41:17 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5213612EBC6 for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 13:41:11 -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 rwp4pRH2SXr2 for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 13:41:09 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 9A14D127342 for <ietf@ietf.org>; Wed, 26 Apr 2017 13:41:04 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id 194so5445965pfv.3 for <ietf@ietf.org>; Wed, 26 Apr 2017 13:41:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Yk9+8dD32bVdYbHBAEaRH7Cw/53d6Sxux97bBXQ1n5Y=; b=U62r64zyJya3GywnkAcktIWQgdkxdHzU2iljn/pu48PZH2iPRx7EuGRBOMSm48N54n vIrqU7jvJN1JNXRU7civ3tNKbu4/pHWjYQrxRBhs9jrEIS6n/ukT2fEcExBgEKCufD5k Drp3gjMXvtrOD9zpRitsZFNLd8ygGvEevT5puSXOdhmHrMIJefznVzdEGc1Ak62mGXss Aix5qOh7Q4BLSheKJdQtnFpYkQzOGb4pTEiB5TAawXkWBYx/rim5BZZpiAzyn4AkjvRs aE2aNDyVKZWEfWc5VOCujNm1bbpEYoSiHk+dirgHJTWdn3kkybP/8CnDOhIVSyC9Pil8 26JQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Yk9+8dD32bVdYbHBAEaRH7Cw/53d6Sxux97bBXQ1n5Y=; b=hD4NQJzbGlvE/IsYOjlbNlE4nZbcRUn2Scmk078jN1vnDL3PfYxwuZyW+Wnn6JpdpP xVQoh6YDWR+/qlnkKhSdlD9dQ97jyes6Y2jev0gRAOBAlkp+luG8yRn5dUue8jZ1ReTJ olnOWxv+JuTkPMvoRjaZ7YmY1M32yvhauho9Azev9QIKiwfug68PrxQwgcJ9pyw3l47v z7/pmMuOZ7jmxlnPGAMFHpeUHtdRkmBJGYl/YkA9za9rwGlttfYkkFUeMDwUhp4xvJJ3 mKcyyqjzAKVMKTvCcnAGSgQaemCA2Avz9f30Wr/hH8wjMGkor1MiX4GEDCDPGp+4pFYN BVUQ==
X-Gm-Message-State: AN3rC/7e/k+vM1U2GLLmJKF2Tf4rNpmqb1ax5ER1WtS7Eqv2JzFQPDhJ C0pxIUJGs16v/G9B
X-Received: by 10.99.109.9 with SMTP id i9mr1730036pgc.91.1493239264043; Wed, 26 Apr 2017 13:41:04 -0700 (PDT)
Received: from [192.168.178.21] ([118.149.100.28]) by smtp.gmail.com with ESMTPSA id j73sm293488pfe.108.2017.04.26.13.41.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:41:03 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <28718.1493215497@dooku.sandelman.ca> <b13a768b-fc53-21f3-9e26-d27f16a32433@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <557642ad-4417-d9e1-e4ce-c27ea4e4c6ac@gmail.com>
Date: Thu, 27 Apr 2017 08:41:05 +1200
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: <b13a768b-fc53-21f3-9e26-d27f16a32433@joelhalpern.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IQ9txDNn49xeRAw72hVIhHFiEZw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:41:11 -0000

On 27/04/2017 02:17, Joel M. Halpern wrote:
> Whether in the IETF or elsewhere, there is one aspect you do not mention 
> that I find useful asa presenter, and one aspect that I find useful in 
> well-done presentations as a participant.
> 
> 1) As a Presenter, if I have managed to do my presentation right, it 
> helps me get the important points covered in the right order.  yes, I 
> usually remember them.  But not always.  And it helps in getting back on 
> track after useful discussions of particular points.
> 
> 2) As a participant, I find it very helpful if the slide tells me what 
> the presenter considers the critical points for me to think about. 
> (There are also the not uncommon cases where a diagram helps me 
> understand the point the speaker is trying to make.)

Both points are true, and neither requires the slides to be read out loud.
Perhaps we could add to the standard question "Has everybody read the
draft?" a new question "Has everybody read the slides? Good, so we'll go
straight to the open issues."

Ideally, meetings should discuss either new work items or open issues on
unfinished work items.

   Brian

> 
> Yours,
> Joel
> 
> On 4/26/17 10:04 AM, Michael Richardson wrote:
>>
>> Toerless Eckert <tte@cs.fau.de> wrote:
>>     > For example, there is a lot of death by powerpoint in meetings that
>>     > pushes off high bandwidth discussions ("oh, we're out of time"). AFAIK,
>>     > most active work on drafts during IETF meeting week happens outside of
>>
>> I am among those who pushes back on death by powerpoint, so I agree with you
>> strongly.  Presentations are very easily supported through completely remote
>> attendance.  Concurrent jabber back-channel discussion among the participants
>> can often bring out points that are sometimes lost in the foreground presentation.
>>
>> {Maybe we should dispense with the meeting rooms, just wire the hotel rooms
>> for GbE, and all be on-site, but "remote".  Then the critical criteria for
>> which city to meet in is reduced to where the best beer can be had.  (And so
>> Prague wins?)}
>>
>> But, on somewhat more serious note [note lack of :-) above], I have been told
>> the following features about the deathly powerpoints:
>>   1) provides a record of thoughts for later on.
>>   2) permits non-english speakers to understand what is being said by
>>      other non-english speakers!!!
>>   3) can be pushed through google-translate.
>>   4) can be read ahead of time by chairs and participants so that they
>>      can ask intelligent questions, and/or can allocate appropriate amounts
>>      of time.
>>
>>
>>
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -= IPv6 IoT consulting =-
>>
>>
>>
> 
> 


From nobody Wed Apr 26 14:12:28 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0451294EC for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 14:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 eqgtYUe9zLcl for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 14:12:26 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 5ED291294C0 for <ietf@ietf.org>; Wed, 26 Apr 2017 14:12:26 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3QLEiV2021150 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 26 Apr 2017 14:14:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1493241285; bh=QRKGOlnREhJ282e3mQRme1ZKrJMjNHPs3vjyC+7C0II=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=L1nVS90mW9PifVbeA1rZUlESQ7bqUhpLoE5I8j+SWqS4ZiO+rxX9xrac57NChxDNF y13u9534OdpQFTl6xDEi+PrdF/X3BJ9iKrJEFl8qLfxFTFMcWTzpwJTJBB9rY175r0 8KRq7TEouHz40RHIW+jH5G/f/+1+JHkjtunPe+5Y=
Subject: Re: Why are mail servers not also key servers?
To: Jon <jmoroney@hawaii.edu>, ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <25a21fd6-467f-40c7-a16d-644b90e87574@dcrocker.net>
Date: Wed, 26 Apr 2017 14:12:17 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BfDM2iff09A-tPEnkD9UFp9z8Ko>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 21:12:27 -0000

On 4/20/2017 6:20 AM, Jon wrote:
> So, why hasn't key exchange been made to
> be transparent? Why are (E)SMTP servers not also key servers?


SMTP is a transfer protocol, for sending a specialized 'file' /to/ a 
server.  A key server needs a query transaction, to get small bits of 
data /from/ a server.  They are fundamentally different interaction 
service models.

A closer approximation would be DNS, which perhaps explains DKIM and 
DANE, as has been cited in this thread.  (However they are at the domain 
level and you appear to be targeting per-user keys, given the PGP 
reference.  That's a much harder problem.)

The deeper concern is the apparent view that lack of key servers is the 
limiting factor in use of encryption.  Typically, the problem is 
assessed as usability -- key management on the infrastructure side, and 
end-user interface on the apps side.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 26 14:37:57 2017
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF49A1292CE; Wed, 26 Apr 2017 14:37:43 -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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 SXoZCa_LWWsv; Wed, 26 Apr 2017 14:37:42 -0700 (PDT)
Received: from homiemail-a121.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B37912709D; Wed, 26 Apr 2017 14:37:42 -0700 (PDT)
Received: from homiemail-a121.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a121.g.dreamhost.com (Postfix) with ESMTP id CB86F60001A09; Wed, 26 Apr 2017 14:37:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=kTIV2paK+Y/7/+g0K87Ygnu4MQU=; b=BqwGNUhv3uZYNaYSBiQb63Bk6WRC NXP3WFn5IB2klpPiHQ8MQtHOugvE/9zovU3en5vfRPgEZuYx3YiDAosgh0vjO9aZ fiL0/EcM2sL520MlTYQCWTbhpfgHfyalY2lxmDtrxUYHHtLM9NkrFjpb2gEeTr3o L4Pp/6U5bd3EhHo=
Received: from [192.168.1.8] (ip68-228-71-159.oc.oc.cox.net [68.228.71.159]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a121.g.dreamhost.com (Postfix) with ESMTPSA id 103D360001104; Wed, 26 Apr 2017 14:37:40 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [art] Artart last call review of draft-ietf-core-links-json-07
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <FEA936B1-3DCE-4376-8E0D-0C57202FF777@tzi.org>
Date: Wed, 26 Apr 2017 14:37:40 -0700
Cc: IETF <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, Herbert Van de Sompel <hvdsomp@gmail.com>, "core@ietf.org WG" <core@ietf.org>, Erik Wilde <erik.wilde@dret.net>, draft-ietf-core-links-json.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E2E3319-0540-441C-A2D3-2325FBE199D9@gbiv.com>
References: <149188258769.15738.17473942496982365590@ietfa.amsl.com> <A12A8CB3-F756-4790-806A-A67AA8CE1D78@tzi.org> <CAOywMHdqitw-uN09p11j2xkBK6TO8y3wjAWipK7vhqbTWp0T1w@mail.gmail.com> <a2350664-05a7-8909-4cf4-5b765e09f9e7@dret.net> <027F2C41-E498-4801-86E2-047771E10545@tzi.org> <4cd01462-2a0f-803e-df10-e68b3eed0226@dret.net> <B04F33DD-51C1-4545-AD59-2F1A3AF14FF6@tzi.org> <feee7d84-263a-49e4-d95e-09ab8526b703@dret.net> <CAOywMHfJpYB6u7BFVf10Gf=Nxk0E1h5iEvyVX5VeAW0UKQOSzQ@mail.gmail.com> <5EB045F7-09FA-4EE8-844A-5AC0E3BF5C1E@tzi.org> <f1b9f42f-559d-d146-e355-c3e2ba31cb01@gmx.de> <23DDC7F2-D46F-4C19-AEA8-C71187099414@tzi.org> <A43ECEE0-47C8-485C-A9AC-E7890B0A6AA4@gbiv.com> <26C26E7B-24E1-4982-B3D8-9991AA1CC6DF@tzi.org> <FEA936B1-3DCE-4376-8E0D-0C57202FF777@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2jgZmn4bZdvis34oCVwRKYzSWhY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 21:37:44 -0000

> On Apr 26, 2017, at 8:51 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Apr 25, 2017, at 23:25, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> OK, let me start typing that errata report then.
>=20
> Below is a draft errata report.
>=20
> Is this information correct?

No.  An RFC that isn't interoperable (in this case, because it
contradicts its own normative references) is a design error.

I don't agree with the entire contents of RFC6690.  The abstract alone =
is
enough for me to drop it in the nearest recycling bin; the design has
nothing to do with REST (an architectural style, not an architecture).

Nevertheless, the error (a non-interoperable design error) in RFC6690 is =
in
section 4.1.  It is either a bad URI template (if the examples are =
correct)
or a bad description of how to process that template.

  /.well-known/core{?search*}

RFC6570 requires that the above template's values be pct-encoded during
expansion, so the examples given in 4.1:

  The following are examples of valid query URIs:

  o  ?href=3D/foo matches a link-value that is anchored at /foo

  o  ?href=3D/foo* matches a link-value that is anchored at a URI that
     starts with /foo

  o  ?foo=3Dbar matches a link-value that has a target attribute named
     foo with the exact value bar

  o  ?foo=3Dbar* matches a link-value that has a target attribute named
     foo, the value of which starts with bar, e.g., bar or barley

  o  ?foo=3D* matches a link-value that has a target attribute named foo

are almost all wrong.  They would have to be

  The following are examples of valid query URIs:

  o  ?href=3D%2Ffoo matches a link-value that is anchored at /foo

  o  ?href=3D%2Ffoo%2A matches a link-value that is anchored at a URI =
that
     starts with /foo

  o  ?foo=3Dbar matches a link-value that has a target attribute named
     foo with the exact value bar

  o  ?foo=3Dbar%2A matches a link-value that has a target attribute =
named
     foo, the value of which starts with bar, e.g., bar or barley

  o  ?foo=3D%2A matches a link-value that has a target attribute named =
foo


Alternatively, if the examples are correct, the specification needs to =
replace
the above URI template with a more accurate list of such templates to =
match
the examples:

  /.well-known/core
  /.well-known/core?href=3D{+reference}
  /.well-known/core?anchor=3D{+anchor}
  /.well-known/core?type=3D{+mt}
  /.well-known/core{?rel}
  /.well-known/core{?rev}
  /.well-known/core{?hreflang}
  /.well-known/core{?media}
  /.well-known/core{?title}
  /.well-known/core{?rt}
  /.well-known/core{?if}
  /.well-known/core{?sz}
  /.well-known/core{?link-extension*}
  /.well-known/core?href=3D{+reference}*
  /.well-known/core?anchor=3D{+anchor}*
  /.well-known/core?type=3D{+mt}*
  /.well-known/core{?rel}*
  /.well-known/core{?rev}*
  /.well-known/core{?hreflang}*
  /.well-known/core{?media}*
  /.well-known/core{?title}*
  /.well-known/core{?rt}*
  /.well-known/core{?if}*
  /.well-known/core{?sz}*
  /.well-known/core{?link-extension*}*

... [note that this still has an ambiguity problem for href string
    values that happen to end in "*"]

and then the text in 4.1 should be fixed as well:

Original Text:

  Value Strings are percent-decoded
  ([RFC3986], Section 2.1) before matching; similarly,

Corrected Text:

  Value Strings for the href, anchor, and type attributes (reserved =
templates)
  are not percent-decoded ([RFC3986], Section 2.1) before matching;
  for all other templates, Value Strings are percent-decoded only once
  before matching; note that a value which originally contained a
  percent-encoded triplet of "%20" would be encoded as "%2520" by a
  non-reserved template expansion and restored here as "%20".  =
Similarly,


The above would make RFC6690 consistent with its normative references.

A more sensible design would separate the response format (which is fine
as a media type) from the query syntax (which doesn't need to be limited
to link attributes anyway).

....Roy


From nobody Wed Apr 26 17:28:47 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE252128959 for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 17:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuRnGjEvxT_q for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 17:28:44 -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 77C031279E5 for <ietf@ietf.org>; Wed, 26 Apr 2017 17:28:44 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id j201so20540479oih.2 for <ietf@ietf.org>; Wed, 26 Apr 2017 17:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=lAljMjcOU/IBCABNia+hno2l3mf/iHDS/vAXJ3bGTN4=; b=Ou7b5Bb5g9xf3VwRNy5YprCnGXSjAoH92Gdzp0gp/UeDTykLw4nMrkVc/VvOTeUJni 87OKDyr16L+QxsLmBgSIwgxYJRu1+QLLL9O/dpGFDN9LRGWk7HCO0OGOstR9MrWd9WLE xAN+R0k/C0EKQmEtjUYdcGpHBb9llu4LIKtslAWJLcUIHJ5qCxdXebPQ7v2NjAhxn6td 7695lfJrLiinS8qs2bw7nmyMNcM+z4J2Rwg0sOB/Ih4wXVxNOD/aVnNiLdhLVBUUMUPz Va+UrFEnusLbe5f1YMlgM4+5C8dBeW/RBApJxHbyrus5j3i5VuKxZXXQyFxHaWkLg5cz 2xYg==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=lAljMjcOU/IBCABNia+hno2l3mf/iHDS/vAXJ3bGTN4=; b=QPKonzneZ/L3K7yCNGMDRq5xkeT41tPrvekU6lhU63cM40wV/GpPZaLg0VWLJARdLE 1g7dPJyjPfGRh+EEKGR9kMZmuHSfeeD1SUJt1amsKP3EO80+m0iCBwKz+ay6s55cyaYT 1aOI3ZZ4KGei0ejXw2I1kukaN/96YAX1orUYKNVp9Dkp1QzusGr9qHGQ5E4ktKOcatXp XC9eOEurRhTAhMRR4MGjI2s6Wim5QKPB0DHYZ391L1Jq9JJrbQFTvCDnuySUCwXXGlYn h9cqB7sHnxxoQmL/pzev+IhjT2k48PuZf0k6J5W2xjDnYn7arEfR3ua+m38m8d//chqG C35Q==
X-Gm-Message-State: AN3rC/5CfNUP+DNsLsylalbp5iYjk5gOBCroAuoj6qlmtntIXGDvp1X6 ONWRfbn5JtWbA0zIvCg=
X-Received: by 10.157.23.232 with SMTP id j95mr1505071otj.217.1493252923344; Wed, 26 Apr 2017 17:28:43 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id j51sm444081otc.47.2017.04.26.17.28.41 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 17:28:41 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <25a21fd6-467f-40c7-a16d-644b90e87574@dcrocker.net>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <737251d5-3684-4d22-93f7-0dfdc19efaad@gmail.com>
Date: Wed, 26 Apr 2017 18:28:40 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <25a21fd6-467f-40c7-a16d-644b90e87574@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms060509090708050106050006"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kDPikBxWfJKBWRiX-fzIVqYSmWk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 00:28:46 -0000

This is a cryptographically signed message in MIME format.

--------------ms060509090708050106050006
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/26/2017 03:12 PM, Dave Crocker wrote:
> On 4/20/2017 6:20 AM, Jon wrote:
>> So, why hasn't key exchange been made to
>> be transparent? Why are (E)SMTP servers not also key servers?
>=20
>=20
> SMTP is a transfer protocol, for sending a specialized 'file' /to/ a=20
> server.  A key server needs a query transaction, to get small bits of=20
> data /from/ a server.  They are fundamentally different interaction=20
> service models.

Yes.

 From an implementation point of view the MX/MTA is currently the only=20
'authority' for what is a known email for a domain.

LDAP is generally not exposed to the Internet.

I understand that if a new non-MX/MTA protocol is designed, any=20
compliant MUA and MTA would have to be rewritten, along with a new key=20
server.

I was thinking that having them combined would be less new code and=20
typing :-)

> A closer approximation would be DNS, which perhaps explains DKIM and=20
> DANE, as has been cited in this thread.  (However they are at the domai=
n=20
> level and you appear to be targeting per-user keys, given the PGP=20
> reference.  That's a much harder problem.)
>=20
> The deeper concern is the apparent view that lack of key servers is the=
=20
> limiting factor in use of encryption.  Typically, the problem is=20
> assessed as usability -- key management on the infrastructure side, and=
=20
> end-user interface on the apps side.

I tend to believe the deeper concert is the lack of any standard way to=20
get an individuals key. Once a protocol exists, then the MUA's can=20
implement it. And there should be NO UI issue. User enters the=20
destination email address, user says encrypt this, it works or is told=20
the destination email has no cert available.


--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDI3MDAyODQwWjAvBgkqhkiG9w0BCQQxIgQg/APhsAdIJVbKv3uF9ZewVA949QA5jh8z
1rFqIAzSSfQwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAWxG7LGq3bZ+b
cSMthrPd0FjFe562F+lZetqaxiNIdgZTj50kfP92IgMG+TBzR4Sth+mrWRHgKoijGrQebItd
yWlAMC9bYoVNKnt2FvnbO3vBY1hlwP/XsJyD07NtPwkdnuW41cTyR18jirsAXB1fvFHfKFL0
dwSIECX0rjhOOotN+nHVNzaYkxbWq4QXmOYuZH6RWK55I5p2ihgAlN6WDEsVdlQ64n1QF6am
sbFcVDKiR7KGrvt0HqGWi2fM0yJgKWviAB50FNG9lI/tAyq+sGobYYIwzOsRUPtYnxB6a3UP
42tt0FyDMaS3/3Quxi3PXQE9F9T2S95u9mUoIZhbIQAAAAAAAA==
--------------ms060509090708050106050006--


From nobody Wed Apr 26 21:27:04 2017
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AADF12EC6B for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 21:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XV0iNwn7rmJB for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 21:27:00 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::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 A913212F29A for <ietf@ietf.org>; Wed, 26 Apr 2017 21:27:00 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id j201so24683278oih.2 for <ietf@ietf.org>; Wed, 26 Apr 2017 21:27:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=9n6gUvowzopOyJcUVGtvnkAoNoZq8CzzU3gKvui6e7Q=; b=KC/A/TwysZYbBFMixk2PqHEAkfQZvYCKufRFdlEwRBUuYpzamZrGmyG6d6SK7mbWKZ KzGXB8ImmZ5nz55Sk5b0BG3EIDzR7FDSTuCLi6GOz8m1DTYXt+9vuH9QnXjPef+MyqjA uvuSf+g3XFwBv+N4uAPR134/rwqTJrBbtfIkZThwMnVgXU7h5zOsueAkaluD94FznbgY rIEnxqf5FchukfWPFWTxduvYfLV4gSzKrXbJRmAtHYdr7f7yphKnWQ0/sTV8R/NzLFJK UkFuUctIUByg59q+U1DJhh8HRur3dSR7/5XGz/u3aW7cm4l2nueJVSppfCr8FYEg3M/x YQgQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=9n6gUvowzopOyJcUVGtvnkAoNoZq8CzzU3gKvui6e7Q=; b=M+pBIv+/ex6Bbtz0ocyC7dAlJpT528//sB3wPN0bySPTryK0k3wGnorsb3db0EnsFm Aw+dI0bO/+vxOOBZNPrzwruSQL1wcPLW2Swg9Shr5CyOE/UkRY6lTId5+KCaSCI7ghPa lU/Asq87P1p1OESqLYQdmQgCvLu/fCDSw7veuqr17t3i+LzJyeUpaUgOBehiEKNXR6Xn d5hblscEfzad/iXQLCGlk5C9D3ZExOv563w9ts8+5aBTfEPpO2dT62138/Cwao+JRBZ9 5k+SHVZ8r8rtWifucPWxwd+8QNtyKJTDJ0qfsvxMsv35MNrxEZwi8HHTKaf+U2NeGbG4 5dZQ==
X-Gm-Message-State: AN3rC/6lFJtsx9UlcKFA89HGZAA89WotcC6IotSt5aQLnfj9NnQ7RT+C 2Zmt3MZwMQ4j4kSafvs=
X-Received: by 10.157.2.196 with SMTP id 62mr1846880otl.71.1493267219459; Wed, 26 Apr 2017 21:26:59 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id f40sm734472otd.15.2017.04.26.21.26.57 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 21:26:57 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <07417f97-ada3-dc37-71ec-fcf68d67bee0@gmail.com>
Date: Wed, 26 Apr 2017 22:26:56 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080700000409080604080505"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8XKuVGyWg_JMHz5rJEy4ro2eFdE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 04:27:02 -0000

This is a cryptographically signed message in MIME format.

--------------ms080700000409080604080505
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable


While discussing this topic in non-list email. I had other points that=20
came up.

(1) The cert for a domain does not necessarily have the same CA as all=20
other certs for users in a domain.

	Example:
		admin@example.com may have a CA assigned by
		the example.com, it could be self signed.

		doug@example.com may have a cert provided by an
		unrelated CA to admin@example.com

		Which can be a different cert from the site:
			https://virtual-host.com

		That happens to be hosted on example.com

Real life example, DouglasRoyer@gmail.com has a cert, the CA is=20
StartCom. (This email is signed by that StartCom cert).
And it is not the same CA used by dns-admin@google.com

Both are at google.com, both have a different CA.

(2) Certificate chains.  Doug@eng.example.com may have a cert signed by=20
the eng.example.com, and the eng.example.com cert may be signed by the=20
example.com CA. The example.com CA, could be self signed, or be signed=20
by an outside CA.



--=20

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135


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

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfowggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggVDMIIEK6ADAgECAhA5Slmr+9YRiiUNE3uNg5OMMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTcwNDA0MDAwMDAwWhcNMTgwNDA0MjM1OTU5WjAnMSUwIwYJKoZIhvcNAQkB
FhZkb3VnbGFzcm95ZXJAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAwL60WA/naGMhGT7VQ3tTq3MSyKJJnSkRD0YCwdk9QzqOtBwsrT6i9a61OINNe2/F8NiL
U2+Xy3EzUu5J0cbfXywJT/vFoq9g4Si1phQEcOKOWVwgPcRvycwLZlYDRM7OqwcoG9vuRhXo
2vGaYwBbzBiHKkIhEgN6CN06YzT3wjU4d69B0kIgAr6/vBW/flGzPZUPOe8NSnlVRHZ0QMCf
3NtwGLV6SHls3Q5ZCBhYzn9abCIkNvedB49LqDcUXy3BYQMldpVhW615+vBhChLb1Xpyc2rq
dqXRVc8qzGzHRkV3WzW5+lf+jFZy/CEcD0q4gDXvWP2YK/flZ86LiaeSmQIDAQABo4IB9DCC
AfAwHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFKflWc164g9V
NKG3f5bKDo/motKvMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7
BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5l
dC9DUFMwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RP
U0hBMjU2Q2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYB
BQUHAQEEgYMwgYAwWAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9E
T1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAhBgNVHREEGjAYgRZkb3VnbGFzcm95
ZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBcDZbduvqneBO0ELaqDgN3AR+UPubC
gDyH4zyYUH4L5UesegPZTEY9/a9AfvK7Jh/Wy13KVjH2BPYNlnnkGs/2QJAhB3uYcR975Na5
/WHKFcGkC6fDU1UQcRj3nAwCPOOKC32u0oWI8nyHnNmnB/oEL+yqZJWJuj6/WhZT1ps1O4HU
TVRsFcGOW49xE88KuHHc6nRdALkzbpUSaebUnrTEG1d3iqhWk3fO9D5qRUXs+Vkg860VblVB
Q/44kMXkxZ5xvD9Meg1wMrmrdRSZnJVJXkBHpmnf1tuyCr8LnoJwdcYEDpS1gUqd30w3AflU
6eRLxXy7FS0FR2RmsRaQ0TymMYIEQTCCBD0CAQEwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQOUpZq/vWEYolDRN7jYOTjDANBglghkgB
ZQMEAgEFAKCCAmEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTcwNDI3MDQyNjU2WjAvBgkqhkiG9w0BCQQxIgQgvRKiFCyjsaKTFm/DfEOKbH7bPDu6oHoP
iGwmbx1eMJswbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBwQYJKwYBBAGCNxAEMYGzMIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UE
CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwgcMGCyqGSIb3
DQEJEAILMYGzoIGwMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8G
A1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDlKWav71hGKJQ0Te42Dk4wwDQYJKoZIhvcNAQEBBQAEggEAIDs1thlKPe16
OSnH1MDJ8n2v3OIwdmD/Vx5Igf1nKA2EHD/5aVT2fadN5y5bck5Vm1XimWbVa89zhLOFF5TS
x8hjtrHn/bNhPYjZaaT0S+4Nu3REwrArjZFrYedyA30QOeeRD4CQ/Qk+7tGl/I2WJIFTWJCI
Eu58WSemtGVGZcTvM/1efwhyoWxNbOdTYQ5oQz0ngMXgI32kJhvYdToySwhJcNA85LF7Jqwc
RnstpVPyG1UJibDow+gvfnNqQW3IBUjGTLYV66//Ve9QlqSbUcHotkHrsU3tIFLpDSk71kwP
0QkYFwbRF7JNchlFtmxky9NLhPg2MFq7t+WAAxXsvAAAAAAAAA==
--------------ms080700000409080604080505--


From nobody Thu Apr 27 04:34:05 2017
Return-Path: <menachemdodge1@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8E80124D6C; Thu, 27 Apr 2017 04:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wN5w9YFVyCbY; Thu, 27 Apr 2017 04:33:55 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 3AB66128BB7; Thu, 27 Apr 2017 04:33:55 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c80so15691597lfh.3; Thu, 27 Apr 2017 04:33:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=281VB2Czyd2l4+cxZ6vXQiWeZ3Q9IHnxyOr6lWqlWBI=; b=C6/fDWbSqBsqp9FzfcgHnZu79sVLqOK7S5Bp1hqas5MMEjfN0XXjYlpgG/CQkBibxt hifCNSiYS1QJfWGkZKrDc2/TMEToq3PanweX37UF4sBa+ZXbJV0cXLnvDUfSROaOmRKD 9DMKZ9thmQWdnVSOTOkd+ooNACsafu1GzvYvBUniVTJ2fYuBJgN4KSucaAYh0W4h1Wrv Tp7Iz4GUlUHXMtKmV0TjToWXxaEyW3jK5kZUxPXJ2JrXouWUHmAh168eGp5B/hWwEcO6 skniJQj7Y3G7jkIgiDpe7vggDhCY+42qVABHD7wd9emanrzibQk+9oCSjgABLA6941aT rMzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=281VB2Czyd2l4+cxZ6vXQiWeZ3Q9IHnxyOr6lWqlWBI=; b=Q17qdz60Ovz37X+u2oZFDgAUJxkeL9MMqb7icxakisEibs0FmTjlUytGN0lEUGdvft +N8uZHb5DEf+pkXJqAKAF3yHwbUgxPD0N97n5w12mr8uE1fb8gtpnwQ5b9ljLAkiT+sd Tw5HD7UXYYi962aZAcIpEoaQyHQYthTPilUp+On96ot5BWjWzB86fhbg5za8+DRHq27S fb9sdWt1mmSwCYxH1bhmFPPnvmha2Zj/Fqhvpn9yAblfW3+gZNtJecQdqxu8YHEdve5M OsO284U78XVclosFSHwwceNKmgYie8AWpVK8zRMGDT/wIFsIkzqgKK/sgskVmWVJeu2T Z2rA==
X-Gm-Message-State: AN3rC/7tAsEGD+kxTlaoCkm+Qv7OrIX9BrwGqu9/jimF0dMG0AysufqE AJ7TmsZEPbCCh/IYn4FpnIqhvBbAKSqw
X-Received: by 10.25.22.197 with SMTP id 66mr1700490lfw.46.1493292833123; Thu, 27 Apr 2017 04:33:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.1.203 with HTTP; Thu, 27 Apr 2017 04:33:52 -0700 (PDT)
From: =?UTF-8?B?157XoNeX150g15PXldeT15In?= <menachemdodge1@gmail.com>
Date: Thu, 27 Apr 2017 14:33:52 +0300
Message-ID: <CAJ2jOhV_FYt1ZhWUcX+_N-Dhbd94dSXSQxK8o_hiR6Nj8=aUzw@mail.gmail.com>
Subject: [OPS-DIR] Review of draft-ietf-6man-rfc4291bis-07
To: ops-dir@ietf.org, draft-ietf-6man-rfc4291bis.all@ietf.org
Cc: ietf@ietf.org, Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a113f212edd34b2054e24548e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gD7Og94bSqdqIHOHjqJjPfbaIlM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 11:33:58 -0000

--001a113f212edd34b2054e24548e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Reviewer: Menachem Dodge
Review result: Has Nits
Intended Status: Standards Track
Obsoletes: 4291 (if approved)

Hi all,

I have reviewed draft-ietf-6man-rfc4291bis-07 as part of the Operational
directorate's ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be included in AD reviews during
the IESG review.  Document editors and WG chairs should treat these
comments just like any other last call comments.

=E2=80=9CThis document defines the addressing architecture of the IP Versio=
n 6
protocol. It includes the basic formats for the various
types of IPv6 addresses (unicast, anycast, and multicast).

My overall view of the document is 'Ready with nits' for publication.

*Technical*
No.


*Editorial *


The Nit tool has found the following:

  Checking nits according to http://www.ietf.org/id-info/checklist :
  -------------------------------------------------------------------------=
---

  =3D=3D There are 16 instances of lines with non-RFC3849-compliant IPv6
     addresses in the document.  If these are example addresses, they shoul=
d
     be changed.


  Miscellaneous warnings:
  -------------------------------------------------------------------------=
---

  =3D=3D Line 237 has weird spacing: '...address  is an...'


  Checking references for intended status: Proposed Standard
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  =3D=3D Unused Reference: 'RFC7217' is defined on line 1109, but no explic=
it
     reference was found in the text

  =3D=3D Outdated reference: A later version (-10) exists of
     draft-ietf-6man-rfc2460bis-08

  -- Possible downref: Normative reference to a draft: ref.
     'I-D.ietf-6man-rfc2460bis'

  -- Obsolete informational reference (is this intentional?): RFC 3513
     (Obsoleted by RFC 4291)


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

In addition I have the following:

Section 2.4.1 - Second Paragraph -- suggest to add 'the'
---------------------------------------------------------------------------=
-----

*OLD: *Interface IDs must be viewed outside of the node that created
Interface ID as an opaque bit string without any internal structure

*SUGGEST:* Interface IDs must be viewed outside of the node that
created *the *Interface ID as an opaque bit string without any
internal structure

Section 2.4.1 - FourthParagraph -- suggest to clarify
---------------------------------------------------------------------------=
------------

*OLD:* As noted in Section 2.4, all unicast addresses, except those
that start with the binary value 000, Interface IDs are required to be
64 bits long.

*SUGGEST:* As noted in Section 2.4, the Interface IDs of all unicast
addresses, except those that start with the binary value 000, are
required to be 64 bits long.


Thank you kindly,

Menachem Dodge

--001a113f212edd34b2054e24548e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"rtl"><div dir=3D"ltr"><br></div><div dir=3D"ltr"><span style=3D=
"font-size:12.8px">Reviewer: Menachem Dodge</span><br style=3D"font-size:12=
.8px"><span style=3D"font-size:12.8px">Review result: Has Nits</span></div>=
<div dir=3D"ltr">Intended Status: Standards Track</div><div dir=3D"ltr">Obs=
oletes: 4291 (if approved)<br><br style=3D"font-size:12.8px"><span style=3D=
"font-size:12.8px">Hi all,</span><br style=3D"font-size:12.8px"><br style=
=3D"font-size:12.8px"><span style=3D"font-size:12.8px">I have reviewed=C2=
=A0</span><span style=3D"background-color:rgb(255,253,245);color:rgb(0,0,0)=
;font-family:&quot;pt mono&quot;,monaco,monospace;font-size:14px">draft-iet=
f-6man-rfc4291bis-07=C2=A0</span><span style=3D"font-size:12.8px">as part o=
f the Operational</span><br><span style=3D"font-size:12.8px">directorate&#3=
9;s ongoing effort to review all IETF documents being</span><br style=3D"fo=
nt-size:12.8px"><span style=3D"font-size:12.8px">processed by the IESG.=C2=
=A0 These comments were written with the intent of</span><br style=3D"font-=
size:12.8px"><span style=3D"font-size:12.8px">improving the operational asp=
ects of the IETF drafts. Comments that</span><br style=3D"font-size:12.8px"=
><span style=3D"font-size:12.8px">are not addressed in last call may be inc=
luded in AD reviews during</span><br style=3D"font-size:12.8px"><span style=
=3D"font-size:12.8px">the IESG review.=C2=A0 Document editors and WG chairs=
 should treat these</span><br style=3D"font-size:12.8px"><span style=3D"fon=
t-size:12.8px">comments just like any other last call comments.</span><br s=
tyle=3D"font-size:12.8px"><br style=3D"font-size:12.8px"><span style=3D"fon=
t-size:12.8px">=E2=80=9CThis document defines=C2=A0</span><span style=3D"ba=
ckground-color:rgb(255,253,245);color:rgb(0,0,0);font-family:&quot;pt mono&=
quot;,monaco,monospace;font-size:14px">the addressing architecture of the I=
P=C2=A0</span><span style=3D"color:rgb(0,0,0);font-family:&quot;pt mono&quo=
t;,monaco,monospace;font-size:14px;white-space:pre;background-color:rgb(255=
,253,245)">Version 6 protocol. </span><span style=3D"background-color:rgb(2=
55,253,245);color:rgb(0,0,0);font-family:&quot;pt mono&quot;,monaco,monospa=
ce;font-size:14px;white-space:pre">It includes the basic formats for the va=
rious</span></div><div dir=3D"ltr"><span style=3D"color:rgb(0,0,0);font-fam=
ily:&quot;pt mono&quot;,monaco,monospace;font-size:14px;white-space:pre;bac=
kground-color:rgb(255,253,245)">types of IPv6 addresses (unicast, anycast, =
and multicast).</span></div><div dir=3D"ltr"><span style=3D"color:rgb(0,0,0=
);font-family:&quot;pt mono&quot;,monaco,monospace;font-size:14px;white-spa=
ce:pre;background-color:rgb(255,253,245)"><br></span></div><div dir=3D"ltr"=
><span style=3D"font-size:12.8px">My overall view of the document is &#39;R=
eady with nits&#39; for publication.</span></div><div dir=3D"ltr"><br style=
=3D"font-size:12.8px"><span style=3D"font-size:12.8px"><b><u>Technical</u><=
/b></span><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">N=
o.</span><br style=3D"font-size:12.8px"><br style=3D"font-size:12.8px"><br =
style=3D"font-size:12.8px"><span style=3D"font-size:12.8px"><b><u>Editorial=
=C2=A0</u></b></span><br style=3D"font-size:12.8px"></div><div dir=3D"ltr">=
<span style=3D"font-size:12.8px"><br></span></div><div dir=3D"ltr"><span st=
yle=3D"font-size:12.8px"><br></span></div><div dir=3D"ltr"><span style=3D"f=
ont-size:12.8px">The Nit tool has found the following:</span></div><div dir=
=3D"ltr"><span style=3D"font-size:12.8px"><br></span></div><div dir=3D"ltr"=
><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">=
  Checking nits according to <a href=3D"http://www.ietf.org/id-info/checkli=
st">http://www.ietf.org/id-info/checklist</a> :
  -------------------------------------------------------------------------=
---

  =3D=3D There are 16 instances of lines with non-RFC3849-compliant IPv6
     addresses in the document.  If these are example addresses, they shoul=
d
     be changed.


  Miscellaneous warnings:
  -------------------------------------------------------------------------=
---

  =3D=3D Line 237 has weird spacing: &#39;...address  is an...&#39;


  Checking references for intended status: Proposed Standard
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  =3D=3D Unused Reference: &#39;RFC7217&#39; is defined on line 1109, but n=
o explicit
     reference was found in the text

  =3D=3D Outdated reference: A later version (-10) exists of
     draft-ietf-6man-rfc2460bis-08

  -- Possible downref: Normative reference to a draft: ref.
     &#39;I-D.ietf-6man-rfc2460bis&#39;=20

  -- Obsolete informational reference (is this intentional?): RFC 3513
     (Obsoleted by RFC 4291)
</pre><div><br></div></div><div dir=3D"ltr"><span style=3D"font-size:12.8px=
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span></div><di=
v dir=3D"ltr"><span style=3D"font-size:12.8px"><br></span></div><div dir=3D=
"ltr"><span style=3D"font-size:12.8px">In addition I have the following:</s=
pan></div><div dir=3D"ltr"><span style=3D"font-size:12.8px"><br></span></di=
v><div dir=3D"ltr"><span style=3D"font-size:12.8px">Section 2.4.1 - Second=
=C2=A0Paragraph -- suggest to add &#39;the&#39;</span></div><div dir=3D"ltr=
"><span style=3D"font-size:12.8px">----------------------------------------=
----------------------------------------</span></div><div dir=3D"ltr"><span=
 style=3D"font-size:12.8px"><br></span></div><div dir=3D"ltr"><pre style=3D=
"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><b>OLD: </b>In=
terface IDs must be viewed outside of the node that created Interface ID as=
 an opaque bit string without any internal structure</pre><pre style=3D"col=
or:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><b>SUGGEST:</b> In=
terface IDs must be viewed outside of the node that created <b>the </b>Inte=
rface ID as an opaque bit string without any internal structure</pre><pre s=
tyle=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><div di=
r=3D"ltr" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;white-s=
pace:normal"><span style=3D"font-size:12.8px">Section 2.4.1 - FourthParagra=
ph -- suggest to clarify</span></div><div dir=3D"ltr" style=3D"color:rgb(34=
,34,34);font-family:arial,sans-serif;white-space:normal"><span style=3D"fon=
t-size:12.8px">------------------------------------------------------------=
---------------------------</span></div></pre><pre style=3D"color:rgb(0,0,0=
);word-wrap:break-word;white-space:pre-wrap"><pre style=3D"word-wrap:break-=
word;white-space:pre-wrap"><b>OLD:</b> As noted in Section 2.4, all unicast=
 addresses, except those that start with the binary value 000, Interface ID=
s are required to be 64 bits long.</pre></pre><pre style=3D"color:rgb(0,0,0=
);word-wrap:break-word;white-space:pre-wrap"><b>SUGGEST:</b> As noted in Se=
ction 2.4, the Interface IDs of all unicast addresses, except those that st=
art with the binary value 000, are required to be 64 bits long.</pre><pre s=
tyle=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><br></p=
re></div><div dir=3D"ltr"><span style=3D"font-size:12.8px">Thank you kindly=
,</span></div><div dir=3D"ltr"><span style=3D"font-size:12.8px"><br></span>=
</div><div dir=3D"ltr"><span style=3D"font-size:12.8px">Menachem Dodge</spa=
n></div><div dir=3D"ltr"><span style=3D"font-size:12.8px"><br></span></div>=
<div dir=3D"ltr"><span style=3D"font-size:12.8px"><br></span></div></div>

--001a113f212edd34b2054e24548e--


From nobody Thu Apr 27 04:57:36 2017
Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFE31293F5; Thu, 27 Apr 2017 04:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=nokia.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 hLQnJM0TLsoO; Thu, 27 Apr 2017 04:57:26 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10130.outbound.protection.outlook.com [40.107.1.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F8D8120724; Thu, 27 Apr 2017 04:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=O76leYrZmQuaQ8966PcOihX9I+7vjTPVi8SpcRI1H10=; b=MK8vmr22KAH2g613KMrJ3mscdzBR4BexPu9P8giES5xtcx+hU/JXfLaG4oCIC7/0TMBL9c+FtR5vflMWRgS0HxIsdiwud04LDXLz0Xz6UFZsioH4wKK2OO/8Y1isqJYEGsk/TZa+EQKvmt/r14DuNETjax51nr8stoicRbXqcJI=
Received: from HE1PR0701MB2459.eurprd07.prod.outlook.com (10.168.128.141) by HE1PR0701MB2459.eurprd07.prod.outlook.com (10.168.128.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.6; Thu, 27 Apr 2017 11:57:22 +0000
Received: from HE1PR0701MB2459.eurprd07.prod.outlook.com ([10.168.128.141]) by HE1PR0701MB2459.eurprd07.prod.outlook.com ([10.168.128.141]) with mapi id 15.01.1061.013; Thu, 27 Apr 2017 11:57:22 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Martin Thomson <martin.thomson@gmail.com>
CC: "art@ietf.org" <art@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Subject: RE: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Topic: Artart telechat review of draft-ietf-alto-multi-cost-08
Thread-Index: AQHSrnqQeK8CFgpYuE64kjZYAubM4qHWYMDggADx5oCAAeoBoA==
Date: Thu, 27 Apr 2017 11:57:22 +0000
Message-ID: <HE1PR0701MB2459B2173C921635A61CC24695100@HE1PR0701MB2459.eurprd07.prod.outlook.com>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com> <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com>
In-Reply-To: <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.18]
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2459; 7:yy2XgWH2l6d2Oe8cFawc5PdzNrntO4PqbpmhY/9ytE19vWvC/EkEhtlafQ/9nUStgUq7lBkZTuXOo559+aW8Z3xxAHJAC9K9rz3jlvJHSmgJdUr7X85l7fPdlAjRmRXK5Olx1QarrAeC2rsiPN0rQ4ToP5V7PDFGfbQfntAlynvQaFsaXlowJfAcg9xQ1zIWb2Rdo3uxcnEiZFzn4xbulrYPcJcECnaSutvHz9B42ewSqbA4bFzd8McnMgW6bg/nc5HvlzGHIdH3KpIzScLvV5TuzuJA7G1hJ4ptuJUDf0QSurtnmewHnUb/FkSOnuo5NlxtT/gUefzwMCjjBEKauw==
x-ms-office365-filtering-correlation-id: 732930a5-f84f-48b6-6b5e-08d48d649096
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:HE1PR0701MB2459; 
x-microsoft-antispam-prvs: <HE1PR0701MB24598D9B55583EFD00F06A6095100@HE1PR0701MB2459.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148); SRVR:HE1PR0701MB2459; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2459; 
x-forefront-prvs: 029097202E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39450400003)(39860400002)(39410400002)(39840400002)(39400400002)(24454002)(13464003)(6246003)(74316002)(305945005)(77096006)(38730400002)(110136004)(229853002)(230783001)(6116002)(3846002)(102836003)(6436002)(7696004)(6506006)(7736002)(8936002)(2906002)(81166006)(8676002)(33656002)(4326008)(25786009)(5660300001)(3660700001)(3280700002)(39060400002)(2950100002)(6916009)(9686003)(6306002)(189998001)(122556002)(2900100001)(53936002)(54906002)(99286003)(55016002)(66066001)(54356999)(106356001)(76176999)(50986999)(86362001)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2459; H:HE1PR0701MB2459.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2017 11:57:22.6644 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2459
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2cGC30GFFvAC7g7tTL7xzJrunD8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 11:57:29 -0000

SGVsbG8gTWFydGluLA0KDQpJIGp1c3QgcG9zdGVkIGFuIHVwZGF0ZSB3aGVyZSB0aGUgIiBSZXF1
aXJlbWVudHMgTGFuZ3VhZ2UiIHRleHQgaGFzIGJlZW4gbW92ZWQgaW4gYSBzZWN0aW9uIDEuMS4N
CkFzIEkgc2F3IGl0IG9uIGEgbnVtYmVyIG9mIG90aGVyIGlldGYgZHJhZnRzLCBJIGFsc28gYWRk
ZWQgdGhlIHNlbnRlbmNlIA0KIldoZW4gdGhlIHdvcmRzIGFwcGVhciBpbiBsb3dlciBjYXNlLCB0
aGVpciBuYXR1cmFsIGxhbmd1YWdlIG1lYW5pbmcgaXMgdXNlZC4iDQoNClRoZSB1cGRhdGUgYW5k
IHN0YXR1cyBhcmUgYXZhaWxhYmxlIGF0IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9j
L2RyYWZ0LWlldGYtYWx0by1tdWx0aS1jb3N0Lw0KDQpUaGFua3MsDQpTYWJpbmUNCg0KDQo+Pi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PkZyb206IE1hcnRpbiBUaG9tc29uIFttYWlsdG86
bWFydGluLnRob21zb25AZ21haWwuY29tXQ0KPj5TZW50OiAyNiBBcHJpbCAyMDE3IDA4OjM5DQo+
PlRvOiBSYW5kcmlhbWFzeSwgU2FiaW5lIChOb2tpYSAtIEZSL05vemF5KSA8c2FiaW5lLnJhbmRy
aWFtYXN5QG5va2lhLQ0KPj5iZWxsLWxhYnMuY29tPg0KPj5DYzogYXJ0QGlldGYub3JnOyBhbHRv
QGlldGYub3JnOyBpZXRmQGlldGYub3JnOyBkcmFmdC1pZXRmLWFsdG8tbXVsdGktDQo+PmNvc3Qu
YWxsQGlldGYub3JnDQo+PlN1YmplY3Q6IFJlOiBBcnRhcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRy
YWZ0LWlldGYtYWx0by1tdWx0aS1jb3N0LTA4DQo+Pg0KPj5PbiAyNiBBcHJpbCAyMDE3IGF0IDAz
OjI2LCBSYW5kcmlhbWFzeSwgU2FiaW5lIChOb2tpYSAtIEZSL05vemF5KQ0KPj48c2FiaW5lLnJh
bmRyaWFtYXN5QG5va2lhLWJlbGwtbGFicy5jb20+IHdyb3RlOg0KPj4+Pj5UaGlzIGRvY3VtZW50
IGRvZXNuJ3QgY2l0ZSBSRkMgMjExOSwgYnV0IGl0IHVzZXMgdGhlIGtleXdvcmRzLg0KPj4+IFtT
UiAgICAgXSBSRkMgMjExOSBpcyBjaXRlZCBvbiBwYWdlIDEsIHNlY3Rpb24gIiBSZXF1aXJlbWVu
dHMgTGFuZ3VhZ2UiIGFuZA0KPj5zZWN0aW9uICI5LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcyIu
IFNob3VsZCBpdCBiZSByZWZlcmVuY2VkIGVsc2V3aGVyZT8NCj4+DQo+PlRoZSBjb252ZW50aW9u
IGlzIHRvIHB1dCB0aG9zZSBpbiB0aGUgYm9keSwgSSBtaXNzZWQgaXQgaW4gdGhlIGJvaWxlcnBs
YXRlLg0KPj4NCj4+SSBza2ltbWVkIHRoZSBvdGhlciBjaGFuZ2VzLCBhbmQgdGhleSBsb29rIGZp
bmUuDQo=


From nobody Thu Apr 27 05:30:56 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B685129463; Thu, 27 Apr 2017 05:30:39 -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, RCVD_IN_DNSWL_MED=-2.3, 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 nqUhh2g3iTSg; Thu, 27 Apr 2017 05:30:37 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 DF56A1273B1; Thu, 27 Apr 2017 05:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3RCURe0018959; Thu, 27 Apr 2017 14:30:27 +0200 (CEST)
Received: from client-0199.vpn.uni-bremen.de (client-0199.vpn.uni-bremen.de [134.102.107.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wDGW70pv5zDHMX; Thu, 27 Apr 2017 14:30:27 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [core] Genart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
Date: Thu, 27 Apr 2017 14:30:26 +0200
Cc: gen-art@ietf.org, ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514989026.323576-92920dfcf09ad9fd924409fa3dea0ae4
Content-Transfer-Encoding: quoted-printable
Message-Id: <218E712A-7379-4764-B59A-FD0A186F4520@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com> <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C6ImZce5TyEb0d7icWUp7DbOtaQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:30:39 -0000

Hi Elwyn,

we tried one round at your comments.

We didn=E2=80=99t tackle the interaction with /.well-known/core =E2=80=94 =
I continue to believe what I said yesterday, but we still have to find a =
good way to put this into the document.

We added a note that we need to decide whether there is an onus on a =
receiving CBOR implementation to check for the absence of the 13 strings =
as names (=E2=80=9CAdam=E2=80=99s second issue=E2=80=9D).

The title* issue also requires some more thinking =E2=80=94 do we even =
want to have language tags on a constrained device.  Right now, the =
document simply leaves the whole subject out, but probably needs a =
position on that.

Finally, there is the issue that RFC 6690 percent-decodes and how that =
should be reflected in the JSON and CBOR variants.

We added a whole subsection on converting back to RFC 6690, which =
discusses the current pragmatic approach on solving the =E2=80=9Cto =
quote or not to quote=E2=80=9D issue.

On the editorial side, we addressed the document title, added some =
language to make it clear that the CDDL is informative (and actually =
added build tool rules to check the examples against the CDDL, ouch), =
and quite a few nits.  Thank you for the text suggestions (and no, we =
didn=E2=80=99t add a reference to X.690 yet :-).  Based on Adam=E2=80=99s =
suggestions, we found a way to fix the bullet list in 2.2.

We still need to review the editorial comments on the detailed =
processing of strings etc. (see may previous comments why these didn=E2=80=
=99t just drop in).

Please have a look at the new text at:

https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-links-json-08.txt

Thank you!

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Apr 27 05:36:56 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2D0A127909; Thu, 27 Apr 2017 05:36:36 -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 tidE2CuCJ5qs; Thu, 27 Apr 2017 05:36:34 -0700 (PDT)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::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 8EB0D126B7F; Thu, 27 Apr 2017 05:36:34 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id v42so3630544wrc.3; Thu, 27 Apr 2017 05:36:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=5VudjgTR5zvQXsq5QUfqINOO5xHr5CN60JUHEd4AQzc=; b=oOo9XLx2hviC5JdIn/usK3Tb55cNEHmC7gztnhPPd611GAMDWWRA4EAWOuLKGxunTj 0qNs8hpFCAPrvRplPJi2hR6gcFq/uHT4tf4DJAUUE48NU8z5fPUp780jnVgssGFwrumE xZ1gc6RUZ/iF3aGODy3ulFAiljtRQ+pC+X8N3L/QZsLpqActVx8Xp/tfeJOvl1kpR1c1 9bGv2VILBv6eQo9zNq02pm7fQCaBDSXM3rEHAN93II82iMRtq1Zy9+jthv9vRiamXoe0 XT8zeuPMFlILbQ44SVLLeMDLN2l+ThLfH/qyLdF7H74IPFUEPlJUia7HOtJQ6tQXdWvQ mAsA==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5VudjgTR5zvQXsq5QUfqINOO5xHr5CN60JUHEd4AQzc=; b=SjZP/3Umm8t7Qa0oGjCxkbd+RMy6s0UtZPvfFwzSOy2nq8UTE2l6uXJXFq4BEbAxmk 1kNZTVqJBKOwL1yLGdbWb/KNVjM03UKEtC89cMPIgQAJ7SpZ3sQy2lLW0toft+PGiB6y XD13BJ2DJ6Gnyt1F9990cpJeq7+IBh7knqY/FXqly0bCrOSHXnEJKtPx0ld01pDRtbge JAHhicuBW2bJ3I+ScsZL4KlEq0rEzmwc05SDBzqqOANtig8xhs8PeAxh9JQmDaprZSU/ LOs+9fHe8fuQPU2IPA2AmwW/9FsLAoxeeQWd9l1koqjCtXccAJHJHRGa1VBVlUnllOd9 NmpQ==
X-Gm-Message-State: AN3rC/4pgIHaPxfz5VZoBzJbk1w9D6bj6Iy+4DsiVKCjjdsJbqOvQj24 IMlFa7M7yknPvA==
X-Received: by 10.223.162.147 with SMTP id s19mr3355901wra.142.1493296592995;  Thu, 27 Apr 2017 05:36:32 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id i199sm3164441wmf.33.2017.04.27.05.36.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Apr 2017 05:36:32 -0700 (PDT)
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>, Joe Touch <touch@isi.edu>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
Date: Thu, 27 Apr 2017 13:36:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PBB89xC3RQuOO4G_vhwsItQVVe4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:36:37 -0000

On 26/04/2017 21:30, Brian E Carpenter wrote:
> On 27/04/2017 08:08, Fred Baker wrote:
>>> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>>>
>>> Hi, Stewart,
>>>
>>>
>>> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>>>
>>>> On 25/04/2017 19:26, Joe Touch wrote:
>>>>> Hi, Stewart,
>>>>>
>>>>> ...
>>>>>
>>>>>> SB>
>>>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>>>>> SB> decision.
>>>>> I don't agree; the host at that point is violating RFC2460. It should
>>>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>>>> requires is valid.
>>>>>
>>>>> Joe
>>>>>
>>>> That is as maybe, but a host can do more or less what it wants, so
>>>> this is surely an
>>>> unenforceable constraint, or are you telling me that the receiving
>>>> host MUST drop a
>>>> fragment that is shorter than this? In which case the question whether
>>>> in practice
>>>> they do, and whether such a constraint is reasonable.
>>> A "path MTU" is a value calculated from information from various sources
>>> (attached links, ICMP messages, and perhaps other information), but IMO
>>> it's never appropriate to set a "path MTU" smaller than the limit
>>> established by IPv6 for a single link.
>> You are, of course, quoting RFC 1981:
>>     A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>     minimum link MTU.
>>
>>> Individual packets and fragments can be smaller than the MTU, of course.
>>> Nothing forces fragments to push up against any MTU limit at all. But I
>>> would not describe that has a host changing its path MTU; it's just
>>> sending packets.
>> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
> istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?
>
>      Brian
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

So this seems to me to be an argument of principle vs pragmatism, and in 
general pragmatism has served the Internet well so far.

I think pragmatism is what Fred and Brian arguing for. It is certainly 
the general approach that I support.

I think we have agreed that nothing actually breaks if the host takes a 
more conservative approach, and that the communications path is less 
likely to be disrupted if that is what the host does. I would have 
thought that we should write the text in such a way to "allow" a 
pragmatic mode of operation.

- Stewart




From nobody Thu Apr 27 05:52:15 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BF01294A1; Thu, 27 Apr 2017 05:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 WAS7zLiJza0e; Thu, 27 Apr 2017 05:52:01 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 EED371294C5; Thu, 27 Apr 2017 05:52:00 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.23.139; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
In-Reply-To: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Subject: RE: [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
Date: Thu, 27 Apr 2017 08:46:06 -0400
Message-ID: <012d01d2bf54$3d9bbb60$b8d33220$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJj1w0Rmgy1J+ijI/wBRaCzRiot8qC29IzQ
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U5ncson9XuUP2KTU8VI5X4s-T2E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:52:03 -0000

Dale: 

Thank you for taking the time do a second careful review.   I can only wish
I such an excellent review of documents I am an editor on. Version 14
addresses all of your comments. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Sunday, April 23, 2017 10:05 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Genart telechat review of
draft-ietf-i2nsf-problem-and-use-cases-12

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair.  Please wait for direction from your document shepherd or AD
before posting a new version of the draft.

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be capitalized.
(Between -11 and -12, one instance of this was fixed, but the other one
remains.)

Changed in version 14.  

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such, it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second sentence seems
to mean (though it doesn't say it) is that if you enable a security
function, you don't *know* that the network is protected if you don't have
any monitoring feedback.  (The sentence is stated in terms of whether the
network *is* protected, which it might well be, even if you don't have
monitoring.)  It seems that you need to replace "does not mean that a
network is protected" with something that is more literally correct.

The third sentence is constructed "... to have a mechanism to monitor and
provide execution status of NSFs to ...".  There's an awkwardness that
"monitor" isn't connected to "security and compliance management tools",
whereas "provide ... status ... to" *is* connected; there's a problem that
the "monitor" and "provide" are written as if they're parallel, but they're
not.  I think the wording is less confusing this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security monitoring
interfaces".

Sue:  Dale I rewrote the whole paragraph in version 14. 

New/ A challenge for monitoring prior to mitigation of a security intrusion
is that an NSF cannot monitor what it cannot view. For example, enabling a 
security function to mitigate an intrusion 
(e.g., firewall <xref target="I-D.ietf-opsawg-firewalls"></xref>) 
must include a mechanism to provide monitoring feedback in order to 
determine the intrusion has been stopped. Therefore, it is  
 necessary to have a mechanism to monitor 
and provide execution status of NSFs to security and
compliance management tools. There exist such mechanisms 
in vendor-specific network security interfaces for forensics and
troubleshooting, but an industry standard interface could 
provide monitoring across a variety of NSFs./


3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
some times they're not (two places in 3).

Sue: Thank you for catching this.  I moved all of these words to small case
except in titles. 

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically run
      to upload or download configuration changes, log information and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of an
XXX", but I'm not familiar enough with the subject to know what XXX is.

Sue:
Old/provider side/New/Provide/ 


[END]


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


From nobody Thu Apr 27 08:36:25 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1E03129AD1 for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 08:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 xB7RvBEU7qNi for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 08:36:22 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 B4A06129B18 for <ietf@ietf.org>; Thu, 27 Apr 2017 08:34:42 -0700 (PDT)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-04v.sys.comcast.net with SMTP id 3lR9dxV4kscBP3lRJd8QA5; Thu, 27 Apr 2017 15:34:41 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-04v.sys.comcast.net with SMTP id 3lRHd0yrWFcZ23lRJd6sqp; Thu, 27 Apr 2017 15:34:41 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v3RFYbmi010046; Thu, 27 Apr 2017 11:34:38 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v3RFYa2n010027; Thu, 27 Apr 2017 11:34:36 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Susan Hares" <shares@ndzh.com>
Cc: gen-art@ietf.org, i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: Re: [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
In-Reply-To: <012d01d2bf54$3d9bbb60$b8d33220$@ndzh.com> (shares@ndzh.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 27 Apr 2017 11:34:34 -0400
Message-ID: <8737ctrhit.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfMU/myGjX5MRLWJJP6QFWDh0apPIByWYoYsEzaVfPzskhuCu/rClk3pHbAP4uHRsBZebwTWZRiC4sYcIULtiNuz+tjykKzqMPboSJmL7oyfph72a6S/P 5CJ/QBMh1Qg1alyj28HAXDbABcVyNKngDGCkmpU9rf/KBFCeoB/JdTM4kivOaHxQ1bLbtngcn62gmaz2ljUWJkYTqDsE1hbw4Az4SSqC5fYGzpcX6Fpwm1or TleS5qh3zmamY7li4nJNhbOQZcszYA3JktIE8h2KWiKW3Xn0BIyvAriciDvbs1hBAnonvgd3bdQE8HcmrPmRFw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p-UurXuPmxAwmsMxDRk_6UvIk20>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 15:36:24 -0000

"Susan Hares" <shares@ndzh.com> writes:
> Thank you for taking the time do a second careful review.   I can only wish
> I such an excellent review of documents I am an editor on. Version 14
> addresses all of your comments. 

Thanks!  -15 looks great, except (ugh) for one remaining nit:

> Sue:  Dale I rewrote the whole paragraph in version 14. 

When I read the new paragraph, I get a slightly different impression
than I did from the old paragraph (which is likely something you
indend), viz., that it's about what could be called "the mitigation
action lifecycle", the entire process from identification of the problem
to verification that it has been mitigated, rather than just the
*action* of mitigating the traffic problem.  Within that broader
context, the importance of monitoring is obvious.

> 3.1.4.  More Demand to Control NSFs Dynamically
>
>    The Security Service Providers ...
>
> The capitalization of "security service providers" is inconsistent.
> Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
> some times they're not (two places in 3).
>
> Sue: Thank you for catching this.  I moved all of these words to small case
> except in titles. 

I overlooked (ugh) that there's an instance in section 2:

   Security Service Provider:    A provider of security services to the
      customers (end-users or enterprises) using NSF equipment purchased
      from vendors or created by the service provider.

It turns out that there are only 2 multi-word terms defined in section
2 where the later words aren't acronyms, which are the terms whose
capitalization should be consistent.  The other one is:

   Bespoke security management:   Security management which is made to
      fit a particular customer.

Dale


From nobody Thu Apr 27 10:00:18 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4F2129B37; Thu, 27 Apr 2017 10:00:16 -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, RP_MATCHES_RCVD=-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 Vy4WfhiOxJxD; Thu, 27 Apr 2017 10:00:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 A61B0129B51; Thu, 27 Apr 2017 09:57:59 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3RGvh92009153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 27 Apr 2017 09:57:43 -0700 (PDT)
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com> <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <d998ea12-71d3-1a8f-03cf-91be1f710f9e@isi.edu>
Date: Thu, 27 Apr 2017 09:57:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tsIUZiz8WhM1iCqzt0ZE6pS8CT0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 17:00:17 -0000

On 4/27/2017 5:36 AM, Stewart Bryant wrote:
> ...
> So this seems to me to be an argument of principle vs pragmatism, and
> in general pragmatism has served the Internet well so far.
>
> I think pragmatism is what Fred and Brian arguing for. It is certainly
> the general approach that I support.

IMO, 1981bis should limit its advice to behavior in response to ICMPs, e.g.:

   In reaction to a received ICMP message, a node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

Doing otherwise presents too big an attack surface.

Any other advice on how an end system manages its idea of MTU or
otherwise overrides the 1981bis computation of path MTU should be
limited to host requirements documents, not this one.

Joe


From nobody Thu Apr 27 17:32:11 2017
Return-Path: <eckelcu@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84FD0126CD8; Thu, 27 Apr 2017 17:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 ZhxWJrRh3UIf; Thu, 27 Apr 2017 17:32:00 -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 D0215129C0C; Thu, 27 Apr 2017 17:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5800; q=dns/txt; s=iport; t=1493339332; x=1494548932; h=from:to:cc:subject:date:message-id:mime-version; bh=B0M4yqpy1jXaBL1Rt5MmwUDFZiO1iiFA9Q7Nbe7F2Cw=; b=YNcgaMknJLz5DuHnEAVBPqvoC9BgFICYGyMlebEqXn6LAOfeTlkbstzr Mc7x7Hh6OI991WHPYiAwW5ZsvXGwLAy1GYnDQNrmFIjgGNT9Zzl0N+62l dxBP+aUrX7rsmmKRqtBu7mXrq7JfbucXVwc+qfCSrjL03R4WCKFoib3vQ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BLAgBwjAJZ/5hdJa1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm5nYYEMB4NhihiRLJBWhTeCDyyFLkochAk/GAECAQEBAQEBAWs?= =?us-ascii?q?dC4U/VhIBDCAbAwIEMBQTBA4Fih0OriqCJiuKWwEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARgFiF0LikkugjEFnVABkwuCAoU3iiWUJgEfOIEKbxVWAYZddQGHf4ENAQE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.37,386,1488844800";  d="scan'208,217";a="242290127"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Apr 2017 00:28:48 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v3S0Smfj026496 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 28 Apr 2017 00:28:48 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 27 Apr 2017 19:28:47 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Thu, 27 Apr 2017 19:28:47 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "hackathon@ietf.org" <hackathon@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: IETF Hackathon 99 Registration and Wiki now available
Thread-Topic: IETF Hackathon 99 Registration and Wiki now available
Thread-Index: AQHSv7Zm3HUKfB9RF0eErdphwQknLQ==
Date: Fri, 28 Apr 2017 00:28:47 +0000
Message-ID: <4F511C41-9C3B-4561-8F21-E9C88198B2A9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.59.212]
Content-Type: multipart/alternative; boundary="_000_4F511C419C3B45618F21E9C88198B2A9ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RwdK9yHfhZBJuSNRgw2GDDqW6yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 00:32:02 -0000

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

VGhlIElFVEYgSGFja2F0aG9uPGh0dHBzOi8vd3d3LmlldGYub3JnL2hhY2thdGhvbi8+IHNpdGUg
aGFzIGJlZW4gdXBkYXRlZCB0byBpbmNsdWRlIGxpbmtzIGZvciB0aGUgSUVURiA5OSBIYWNrYXRo
b248aHR0cHM6Ly93d3cuaWV0Zi5vcmcvaGFja2F0aG9uLzk5LWhhY2thdGhvbi5odG1sPi4NCg0K
V2UgYXJlIGNvbGxlY3RpbmcgcHJvamVjdHMgZm9yIHRoZSBoYWNrYXRob24uIFBsZWFzZSBjb25z
aWRlciBjaGFtcGlvbmluZyBhIHByb2plY3QgcmVsYXRlZCB0byB5b3VyIElFVEYgd29yay4gVGhl
IHdpa2k8aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmVnaXN0cmF0aW9uL01lZXRpbmdXaWtpL3dpa2kv
OTloYWNrYXRob24+IGxpc3RzIHRoZSBwcm9qZWN0cyBjaGFtcGlvbmVkIHNvIGZhci4gQWRkaXRp
b25hbCBwcm9qZWN0cyBhcmUgd2VsY29tZWQgYW5kIGVuY291cmFnZWQgYnkgYW55b25lIHdpbGxp
bmcgdG8gY2hhbXBpb24gdGhlbS4NCg0KDQoNClJlZ2lzdHJhdGlvbiBmb3IgdGhlIGhhY2thdGhv
biBpcyBmcmVlIGJ1dCByZXF1aXJlZC4gUGxlYXNlIHJlZ2lzdGVyPGh0dHBzOi8vd3d3LmlldGYu
b3JnL3JlZ2lzdHJhdGlvbi9pZXRmOTkvaGFja2F0aG9ucmVnaXN0cmF0aW9uLnB5PiBzb29uZXIg
cmF0aGVyIHRoYW4gbGF0ZXIgdG8gaGVscCB1cyBwbGFuIHNwYWNlLCBmb29kLCBldGMuLCBwcm9w
ZXJseS4gSWYgeW91IGhhdmUgYW55IHN1Z2dlc3Rpb25zIG9yIHF1ZXN0aW9ucywgeW91IGNhbiBz
dWJzY3JpYmUgYW5kIHNlbmQgdG8gaGFja2F0aG9uQGlldGYub3JnPG1haWx0bzpoYWNrYXRob25A
aWV0Zi5vcmc+LCBvciB5b3UgY2FuIGNvbnRhY3QgbWUgZGlyZWN0bHkuIEkgaG9wZSB0byBzZWUg
eW91IGF0IHRoZSBoYWNrYXRob24gaW4gUHJhZ3VlLg0KDQoNCg0KQ2hlZXJzLA0KDQpDaGFybGVz
DQoNCg0KDQoNCg0KDQo=

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7fQ0K
YTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29s
b3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bh
bi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBs
aS5Nc29QbGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRp
bWVzIE5ldyBSb21hbiI7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQ
bGFpbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu
azoiUGxhaW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0Kc3Bhbi5t
c29JbnMNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJbXNvLXN0eWxlLW5hbWU6IiI7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTsNCgljb2xvcjp0ZWFsO30NCi5Nc29DaHBEZWZh
dWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7
fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBp
biAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rp
b24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0i
RU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRT
ZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5UaGUgPGEgaHJlZj0iaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvaGFja2F0aG9uLyI+SUVURiBIYWNrYXRob248L2E+IHNpdGUgaGFzIGJlZW4g
dXBkYXRlZCB0byBpbmNsdWRlIGxpbmtzIGZvciB0aGUNCjxhIGhyZWY9Imh0dHBzOi8vd3d3Lmll
dGYub3JnL2hhY2thdGhvbi85OS1oYWNrYXRob24uaHRtbCI+SUVURiA5OSBIYWNrYXRob248L2E+
LjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPldlIGFyZSBjb2xsZWN0aW5nIHByb2plY3Rz
IGZvciB0aGUgaGFja2F0aG9uLiBQbGVhc2UgY29uc2lkZXIgY2hhbXBpb25pbmcgYSBwcm9qZWN0
IHJlbGF0ZWQgdG8geW91ciBJRVRGIHdvcmsuIFRoZQ0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvcmVnaXN0cmF0aW9uL01lZXRpbmdXaWtpL3dpa2kvOTloYWNrYXRob24iPndpa2k8L2E+
IGxpc3RzIHRoZSBwcm9qZWN0cyBjaGFtcGlvbmVkIHNvIGZhci4gQWRkaXRpb25hbCBwcm9qZWN0
cyBhcmUgd2VsY29tZWQgYW5kIGVuY291cmFnZWQgYnkgYW55b25lIHdpbGxpbmcgdG8gY2hhbXBp
b24gdGhlbS48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJlZ2lzdHJhdGlvbiBmb3IgdGhlIGhhY2thdGhv
biBpcyBmcmVlIGJ1dCByZXF1aXJlZC4gUGxlYXNlDQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRm
Lm9yZy9yZWdpc3RyYXRpb24vaWV0Zjk5L2hhY2thdGhvbnJlZ2lzdHJhdGlvbi5weSI+cmVnaXN0
ZXI8L2E+IHNvb25lciByYXRoZXIgdGhhbiBsYXRlciB0byBoZWxwIHVzIHBsYW4gc3BhY2UsIGZv
b2QsIGV0Yy4sIHByb3Blcmx5LiBJZiB5b3UgaGF2ZSBhbnkgc3VnZ2VzdGlvbnMgb3IgcXVlc3Rp
b25zLCB5b3UgY2FuIHN1YnNjcmliZSBhbmQgc2VuZCB0bw0KPGEgaHJlZj0ibWFpbHRvOmhhY2th
dGhvbkBpZXRmLm9yZyI+aGFja2F0aG9uQGlldGYub3JnPC9hPiwgb3IgeW91IGNhbiBjb250YWN0
IG1lIGRpcmVjdGx5LiBJIGhvcGUgdG8gc2VlIHlvdSBhdCB0aGUgaGFja2F0aG9uIGluIFByYWd1
ZS48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPkNoZWVycyw8L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij5DaGFybGVzPC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_4F511C419C3B45618F21E9C88198B2A9ciscocom_--


From nobody Thu Apr 27 21:55:54 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D4C1294FD for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 21:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level: 
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 vg_OBXDRlkso for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 21:55:50 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 E3428129B98 for <ietf@ietf.org>; Thu, 27 Apr 2017 21:53:14 -0700 (PDT)
Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v3S4msSu071230 for <ietf@ietf.org>; Fri, 28 Apr 2017 00:53:12 -0400
Received: from e15.ny.us.ibm.com (e15.ny.us.ibm.com [129.33.205.205]) by mx0b-001b2d01.pphosted.com with ESMTP id 2a3d868rt5-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 28 Apr 2017 00:53:11 -0400
Received: from localhost by e15.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 28 Apr 2017 00:53:11 -0400
Received: from b01cxnp23034.gho.pok.ibm.com (9.57.198.29) by e15.ny.us.ibm.com (146.89.104.202) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 28 Apr 2017 00:53:09 -0400
Received: from b01ledav005.gho.pok.ibm.com (b01ledav005.gho.pok.ibm.com [9.57.199.110]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v3S4r9ok45285554 for <ietf@ietf.org>; Fri, 28 Apr 2017 04:53:09 GMT
Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 90E47AE043 for <ietf@ietf.org>; Fri, 28 Apr 2017 00:52:57 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav005.gho.pok.ibm.com (Postfix) with ESMTPS id 7DA0BAE03B for <ietf@ietf.org>; Fri, 28 Apr 2017 00:52:57 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v3S4r79U009381 for <ietf@ietf.org>; Fri, 28 Apr 2017 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v3S4r7L2009345 for ietf@ietf.org; Fri, 28 Apr 2017 00:53:07 -0400
From: narten@us.ibm.com
Date: Fri, 28 Apr 2017 00:53:07 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17042804-0036-0000-0000-000001F24FCF
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006987; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000208; SDB=6.00853418; UDB=6.00422011; IPR=6.00632359;  BA=6.00005316; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015214; XFM=3.00000014; UTC=2017-04-28 04:53:10
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17042804-0037-0000-0000-0000400D2E5E
Message-Id: <201704280453.v3S4r7L2009345@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-28_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=89 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704280079
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y1F3ubLL0I9l4tvg_007Ax4eKYc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 04:55:53 -0000

Total of 73 messages in the last 7 days.
 
script run at: Fri Apr 28 00:53:07 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.96% |    8 | 15.16% |   124364 | phill@hallambaker.com
 10.96% |    8 |  9.52% |    78077 | cabo@tzi.org
  8.22% |    6 | 11.07% |    90825 | douglasroyer@gmail.com
  6.85% |    5 |  7.43% |    60990 | touch@isi.edu
  2.74% |    2 |  6.41% |    52594 | brian.raymor@microsoft.com
  4.11% |    3 |  3.37% |    27614 | erik.wilde@dret.net
  4.11% |    3 |  2.95% |    24161 | martin.thomson@gmail.com
  2.74% |    2 |  3.66% |    30065 | sabine.randriamasy@nokia-bell-labs.com
  2.74% |    2 |  3.61% |    29616 | nishida@sfc.wide.ad.jp
  2.74% |    2 |  2.06% |    16920 | john-ietf@jck.com
  2.74% |    2 |  2.02% |    16538 | stewart.bryant@gmail.com
  2.74% |    2 |  2.01% |    16517 | mcr+ietf@sandelman.ca
  2.74% |    2 |  1.76% |    14422 | pch-ietf-6@u-1.phicoh.com
  2.74% |    2 |  1.73% |    14206 | johnl@taugh.com
  2.74% |    2 |  1.40% |    11458 | jouni.nospam@gmail.com
  1.37% |    1 |  2.16% |    17690 | weihaw@google.com
  1.37% |    1 |  1.60% |    13110 | hvdsomp@gmail.com
  1.37% |    1 |  1.59% |    13041 | eng.khaled.omar@hotmail.com
  1.37% |    1 |  1.56% |    12824 | kolkman@isoc.org
  1.37% |    1 |  1.54% |    12655 | elwynd@dial.pipex.com
  1.37% |    1 |  1.44% |    11833 | narten@us.ibm.com
  1.37% |    1 |  1.38% |    11340 | sarah.banks@gmail.com
  1.37% |    1 |  1.28% |    10475 | shares@ndzh.com
  1.37% |    1 |  1.18% |     9716 | weigengyu@bupt.edu.cn
  1.37% |    1 |  1.15% |     9441 | jmh@joelhalpern.com
  1.37% |    1 |  1.12% |     9151 | fielding@gbiv.com
  1.37% |    1 |  1.08% |     8838 | worley@ariadne.com
  1.37% |    1 |  1.08% |     8833 | nico@cryptonector.com
  1.37% |    1 |  1.07% |     8772 | julian.reschke@gmx.de
  1.37% |    1 |  0.97% |     7953 | rjsparks@nostrum.com
  1.37% |    1 |  0.92% |     7582 | tobias@inet.tu-berlin.de
  1.37% |    1 |  0.88% |     7228 | adam@nostrum.com
  1.37% |    1 |  0.83% |     6832 | mariainesrobles@googlemail.com
  1.37% |    1 |  0.83% |     6791 | rsk@gsp.org
  1.37% |    1 |  0.82% |     6704 | izaac@setec.org
  1.37% |    1 |  0.68% |     5593 | linuxwolf+ietf@outer-planes.net
  1.37% |    1 |  0.68% |     5580 | paul@nohats.ca
--------+------+--------+----------+------------------------
100.00% |   73 |100.00% |   820349 | Total


From nobody Thu Apr 27 23:43:21 2017
Return-Path: <lloyd.wood@yahoo.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C67D3129C3E for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 23:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.21
X-Spam-Level: 
X-Spam-Status: No, score=0.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.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 1JckzaXUv5Ul for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 23:43:18 -0700 (PDT)
Received: from nm31-vm9.bullet.mail.ir2.yahoo.com (nm31-vm9.bullet.mail.ir2.yahoo.com [212.82.97.96]) (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 EEC91124D37 for <ietf@ietf.org>; Thu, 27 Apr 2017 23:40:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1493361635; bh=VySyMBB8Zop1pBDm0c1PVqF+i+T9AN4xxd34qYtcUb4=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=Hieg6cwQXJl4wsG/xojn4ikjOIixe/DNVzJ2fEq0gVP6RUwLGrAWTCeMt725FN279cS9YN1MMc71VOxsPByciciYq3L9zx6eNr2sbXMY6/lw6lRNrOgA0zS1Oc9oEMnpC55hlMEVC+TZG4mmM9+W99yRiGNwUrnkDB2V0CG0uv1GZmtb9oosJ2eHqVHLECE7B5sioXCAP6MwETaBRgIrZeHnBkDReloCk8PSyF0BG74DBuke9NiCaI/wuRBFoNpb8I3VVzPt3mSIGd32boXHCVbrUMQ3HspiGR7GaUys24f303ayo5KLj33YHTY9BTXJsKlaN7tI4PiCJJ7YfcIckw==
Received: from [212.82.98.56] by nm31.bullet.mail.ir2.yahoo.com with NNFMP; 28 Apr 2017 06:40:35 -0000
Received: from [212.82.98.90] by tm9.bullet.mail.ir2.yahoo.com with NNFMP; 28 Apr 2017 06:40:35 -0000
Received: from [127.0.0.1] by omp1027.mail.ir2.yahoo.com with NNFMP; 28 Apr 2017 06:40:35 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 369599.65987.bm@omp1027.mail.ir2.yahoo.com
X-YMail-OSG: mmQUKXoVM1kN6RERyTqJ361m3YMVL2dxTLsq0bjcNg1vLpSyMOzGJUUtHIgZkXF AXV.DR.D5fzqTne6A6qd7brxElp5Q1XetthmJ6ID8ke8R13EGRyY2taFviuNcUJyHSl5IWmsQWmW 1zarW4cYpRC7.PvaPEHw86Hjh22.1YSBizAoi6suVeADtaAksStk4r3tT6faHZ0qE4vg9DznoRe. vU1eTmTOyZu.4EdadpMHtKHIba02zRHeIY3YxzesYXMZJp3rgCqo_9XJCNvsUEJwOGneHTA4oIsZ IhMNy_cEBtr_kAg1mx23GOxVxdulN_wQX1DgKYRkxk.sLrh_9Me_1btqFV5r_OO8QjuFg_8K8ECM AEYx5Mq0j66hoF1RWrSF2XzaVXrVoRW9q8AM89BjWNMyO2Fw0V0NW8eHWlcwFgfOtPgXvi1b5AjX b53qQZKcv0zcKN_41mp5yJqxoCr.WEfmEH3LoEypi36BQQqWZArAs2BrnVzaYMk1VoziTdMYz7Nd DbgdvwgBQQuFls9aOfXw0uj7P8Gahc8SK11OdtaYTmzNm8OZoTcV4OGvhwm8-
Received: from jws700046.mail.ir2.yahoo.com by sendmailws165.mail.ir2.yahoo.com; Fri, 28 Apr 2017 06:40:34 +0000; 1493361634.792
Date: Fri, 28 Apr 2017 06:40:34 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Khaled Omar <eng.khaled.omar@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <759171555.14366772.1493361634237@mail.yahoo.com>
In-Reply-To: <AM4PR0401MB2241F91F390678CE3C0F3193BD1E0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241F91F390678CE3C0F3193BD1E0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Subject: Re: KHALED Routing Protocol (KRP).
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_14366771_85814701.1493361634234"
X-Mailer: WebService/1.1.9408 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64;  x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NVkm7RKsEYDo6A59Vysy_S0tBjE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 06:43:20 -0000

------=_Part_14366771_85814701.1493361634234
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

"KRP"?
How do you pronounce the name?=C2=A0Lloyd Wood http://about.me/lloydwood=C2=
=A0

      From: Khaled Omar <eng.khaled.omar@hotmail.com>
 To: "ietf@ietf.org" <ietf@ietf.org>=20
 Sent: Wednesday, 26 April 2017, 9:27
 Subject: KHALED Routing Protocol (KRP).
  =20
 <!--#yiv9873945094 _filtered #yiv9873945094 {font-family:"Cambria Math";pa=
nose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv9873945094 {font-family:Calibri;=
panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv9873945094 #yiv9873945094 p.yiv987394509=
4MsoNormal, #yiv9873945094 li.yiv9873945094MsoNormal, #yiv9873945094 div.yi=
v9873945094MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;fon=
t-family:"Calibri", "sans-serif";}#yiv9873945094 a:link, #yiv9873945094 spa=
n.yiv9873945094MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv9=
873945094 a:visited, #yiv9873945094 span.yiv9873945094MsoHyperlinkFollowed =
{color:#954F72;text-decoration:underline;}#yiv9873945094 span.yiv9873945094=
EmailStyle17 {font-family:"Calibri", "sans-serif";color:windowtext;}#yiv987=
3945094 .yiv9873945094MsoChpDefault {font-family:"Calibri", "sans-serif";} =
_filtered #yiv9873945094 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv9873945094 di=
v.yiv9873945094WordSection1 {}-->Hi All,  =C2=A0 I think you all received t=
he notification regarding the KRP ID submission, so here is the link for th=
is Internet Draft:  =C2=A0 https://datatracker.ietf.org/doc/draft-omar-krp/=
  =C2=A0 For those who are interested in it, you will be welcomed to discus=
s it directly with me.  =C2=A0 Looking for your thoughts, suggestions, comm=
ents, modifications or any kind of positive participation.  =C2=A0 If you a=
re not interested in the idea after reading the draft, please ignore this e=
-mail.  =C2=A0 Best Regards, =C2=A0=20

  =20
------=_Part_14366771_85814701.1493361634234
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:Courier New, courier, monaco, monospace, sans-serif;font-size:16=
px"><div id=3D"yui_3_16_0_ym19_1_1493359115215_7210"><span>"KRP"?</span></d=
iv><div id=3D"yui_3_16_0_ym19_1_1493359115215_7211"><span><br></span></div>=
<div id=3D"yui_3_16_0_ym19_1_1493359115215_7212"><span id=3D"yui_3_16_0_ym1=
9_1_1493359115215_7229">How do you pronounce the name?</span></div><div></d=
iv><div id=3D"yui_3_16_0_ym19_1_1493359115215_7213">&nbsp;</div><div class=
=3D"signature" id=3D"yui_3_16_0_ym19_1_1493359115215_7214">Lloyd Wood http:=
//about.me/lloydwood&nbsp;</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16=
_0_ym19_1_1493359115215_7230"><br><br></div><div class=3D"yahoo_quoted" id=
=3D"yui_3_16_0_ym19_1_1493359115215_7235" style=3D"display: block;">  <div =
style=3D"font-family: Courier New, courier, monaco, monospace, sans-serif; =
font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1493359115215_7234"> <div style=
=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Gr=
ande, Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1493359115215_7=
233"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1493359115215_7232"> <font s=
ize=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1493359115215_7231"> <hr s=
ize=3D"1"> <b><span style=3D"font-weight:bold;">From:</span></b> Khaled Oma=
r &lt;eng.khaled.omar@hotmail.com&gt;<br> <b><span style=3D"font-weight: bo=
ld;">To:</span></b> "ietf@ietf.org" &lt;ietf@ietf.org&gt; <br> <b><span sty=
le=3D"font-weight: bold;">Sent:</span></b> Wednesday, 26 April 2017, 9:27<b=
r> <b><span style=3D"font-weight: bold;">Subject:</span></b> KHALED Routing=
 Protocol (KRP).<br> </font> </div> <div class=3D"y_msg_container" id=3D"yu=
i_3_16_0_ym19_1_1493359115215_7236"><br><div id=3D"yiv9873945094">

=20
=20
<style><!--
#yiv9873945094 =20
 _filtered #yiv9873945094 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 =
6 3 2 4;}
 _filtered #yiv9873945094 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 =
4;}
#yiv9873945094 =20
#yiv9873945094 p.yiv9873945094MsoNormal, #yiv9873945094 li.yiv9873945094Mso=
Normal, #yiv9873945094 div.yiv9873945094MsoNormal
=09{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri"=
, "sans-serif";}
#yiv9873945094 a:link, #yiv9873945094 span.yiv9873945094MsoHyperlink
=09{color:#0563C1;text-decoration:underline;}
#yiv9873945094 a:visited, #yiv9873945094 span.yiv9873945094MsoHyperlinkFoll=
owed
=09{color:#954F72;text-decoration:underline;}
#yiv9873945094 span.yiv9873945094EmailStyle17
=09{font-family:"Calibri", "sans-serif";color:windowtext;}
#yiv9873945094 .yiv9873945094MsoChpDefault
=09{font-family:"Calibri", "sans-serif";}
 _filtered #yiv9873945094 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv9873945094 div.yiv9873945094WordSection1
=09{}
--></style>

<div id=3D"yui_3_16_0_ym19_1_1493359115215_7239">
<div class=3D"yiv9873945094WordSection1" id=3D"yui_3_16_0_ym19_1_1493359115=
215_7238">
<div class=3D"yiv9873945094MsoNormal" id=3D"yui_3_16_0_ym19_1_1493359115215=
_7237">Hi All,</div>=20
<div class=3D"yiv9873945094MsoNormal"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal" id=3D"yui_3_16_0_ym19_1_1493359115215=
_7240">I think you all received the notification regarding the KRP ID submi=
ssion, so here is the link for this Internet Draft:</div>=20
<div class=3D"yiv9873945094MsoNormal"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal" id=3D"yui_3_16_0_ym19_1_1493359115215=
_7242"><a rel=3D"nofollow" target=3D"_blank" href=3D"https://datatracker.ie=
tf.org/doc/draft-omar-krp/" id=3D"yui_3_16_0_ym19_1_1493359115215_7241">htt=
ps://datatracker.ietf.org/doc/draft-omar-krp/</a></div>=20
<div class=3D"yiv9873945094MsoNormal"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal" id=3D"yui_3_16_0_ym19_1_1493359115215=
_7243">For those who are interested in it, you will be welcomed to discuss =
it directly with me.</div>=20
<div class=3D"yiv9873945094MsoNormal" id=3D"yui_3_16_0_ym19_1_1493359115215=
_7244"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal">Looking for your thoughts, suggestion=
s, comments, modifications or any kind of positive participation.</div>=20
<div class=3D"yiv9873945094MsoNormal"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal">If you are not interested in the idea=
 after reading the draft, please ignore this e-mail.</div>=20
<div class=3D"yiv9873945094MsoNormal"> &nbsp;</div>=20
<div class=3D"yiv9873945094MsoNormal">Best Regards,</div>=20
<div class=3D"yiv9873945094MsoNormal">&nbsp;</div>=20
</div>
</div>
</div><br><br></div> </div> </div>  </div></div></body></html>
------=_Part_14366771_85814701.1493361634234--


From nobody Thu Apr 27 23:58:50 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA44129C4E for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 23:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 sh4QyTR_D8VH for <ietf@ietfa.amsl.com>; Thu, 27 Apr 2017 23:58:47 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-oln040092072064.outbound.protection.outlook.com [40.92.72.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E421129480 for <ietf@ietf.org>; Thu, 27 Apr 2017 23:56:18 -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; bh=bSzdEl07LReGWhLKjn7rIWHMUBh+v6md/dQ1pjz38Mk=; b=DHIoMV9L9h+5tC9PnpCi3D61R95l4CKTPDBbT65v+Fnbj2oBovgWZGk5WGAtq+J27UlMbeV4WZasLPWhjjH0pFIIBKz45T7QP73LoezU/tfM0DtxExugK1FDsnnif6Snbz2Hn/Uru25Q3QkHEGlQ/BLRCw2NvABBAk28FTSfHua5Gp12SMD6qtPisbXRt3j6nOFFA8wxIX4/6q8yIJXqzGUgQTxD/hbwdlA08uJsScwUN7GkLlTugepHaDk+JEQRddewByDq++9Pz4xbGoUI6tbr+7SfDuPA+AV1E2VNBT9yE1m9rbA3CXA6pBNyLNPzYO5MxguPBsI1eWHTjeFq4Q==
Received: from AM5EUR03FT031.eop-EUR03.prod.protection.outlook.com (10.152.16.55) by AM5EUR03HT105.eop-EUR03.prod.protection.outlook.com (10.152.17.239) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 06:56:16 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.56) by AM5EUR03FT031.mail.protection.outlook.com (10.152.16.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 06:56:16 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 06:56:16 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
CC: ietf <ietf@ietf.org>
Subject: Re: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 06:56:15 +0000
Message-ID: <AM4PR0401MB2241C6379B03E5BDF089FFA1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <759171555.14366772.1493361634237@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: yahoo.co.uk; dkim=none (message not signed) header.d=none;yahoo.co.uk; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:942ED5E5284B2FC4B90B36254C5188270C8CE130007EBB8F269A56414B43F1E7; UpperCasedChecksum:1B20D406D92515CDFC30FF2317D1BD267E64923ACF6DB4931B0A3AC03CA5F7FA; SizeAsReceived:7850; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT105; 5:R+RrDpoSZUcR8vo/waFzVq7ArRWZijlmCiuWnaqzig3Iv6uE/v4HDN/lyp2gIgmalGGu2JtNBKEPoVnN6dkHsMXaaVOT8vEyHby9M9tF4tGeoeseCOykmIvygsUYhB4Kg1zv6/Wo13A92AvU+cqv8w==; 24:KUKhlCD4GxOphc5q7CFJtL1j6qcXs4qSIXEegecRZjmuMIIS3SntqgQr0rz6FSsNWcvjV+Swj4j7hRLNDzeHXKQTvjQmlUIVnowZ9/yTp/k=; 7:G9vZe9hSNMzweDATC2E+Pf9Ogi1IeRukFpFFp8gk44fhZC2FqfOZuxIMRy1Elfhb9pPKmgongt/L75JYF6fuLPF+mDRnnd43+pJt8vHzotn1294l2zdl4YZ1rKxOTGd3A/CeG44uSkSdVWZ169dQM4nSwabOtyyrNAjcclSOUft9Wsk7R7q4MuD2ZBBNF9oj4iRWMsaepko5vKOEAhOQGICTfWMh8EdGrMXQn2+GYKPq4ZLpkUUYOszPQ1M7bGbNKmfkxmBNOZGiBjzP90HXBajwCOFUZu11Ff/gfW+HGvGfZ2lb5o63wXnZDYxddTPC
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT105; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: e1774058-6200-4a78-48c5-08d48e03a994
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(201702181274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR03HT105; 
x-ms-exchange-slblob-mailprops: 7vaohneSo7rqyCz6eto6Kp1fVSJJNaaTLH6s63LQ2kLbn7dbs6FoTh+AKJ5sAY14sneE272LqPcL64R63jzgXq0iKZBGVATag2w0/pJB6SRT2Q/Zdo/Q71yOz7XRZZECJjYWyw92vAeqQI2KFm0MSispwJQ93GJWYRu2cZYE4fQYHZ4BKDbv0/7rRbKuCdy+knWwX7WLfPOt3xJfZf4PuUCaLlWdGu8npjlGbWv3p9ffBJ9CwAShSb0DUwnJdvMjzZXT1yhRxnrqFyNkUzQGGaGj169K8cv38Wc1GzvOG7LacHEfLjVUxeVf5XfLDG0qqzW4d9bMDdRjeivLT8GaNlvwoDty53ZYu5hc2FdAUs/nhVO/jz8T16NM2OiLRXAgXFiDXN2mhvAqUYsMOtxXhEkHc3zXLf2XCzf0l5V+AuyN4t2vtZCJ1OJbKhdAbvv4hUzD95h480nR1olCBysCL/vxVGiBzK6Q8CJHPahv+KRC8W5vdXv46GW3PPCAjhhPdnnMNhfnOpPNK8PrliP0T6qmbkEQPyzG8IrDlqJ94Wf9qTP5+F50tFD2F4ltfC7jLm86+Y7jFeC3uAw+aOEeiXxRURjVlvex6xA8y1gqjReiugwe+yF8RwUeFTvqIXtcR8k8vINyo1okXL+fTjZmcpROdz1vH/EmqoCcQ6HOOVSKEKEr1G78Rw/SJWIn02RNnV5yUbSQBe920ugwf8bltRFfrjwO81fAFIipmSSLAPnW2/WtSfzcDOTBkInetoHoZNTfrzmxq0+9nKFBQ9ZJUM7jKs7OQhnFcr/wYwLlkLguLb/9mdMQg19sLh0NujH6qPinlq9DMVaEB7QYfoaom24fz1ODwLeZd10H3MYFd3hj3o6EpPlcon2uEc4a+ESugMmHIVcQC56I3cWGpgEGDTdCpQju8Rq37t21rQdXKkY=
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT105; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT105; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241C6379B03E5BDF089FFA1BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 06:56:15.8945 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT105
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ljoI9GnvZHXTEGEelf8mP9aEN5Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 06:58:48 -0000

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

U3RlcCBieSBzdGVwLCBLaGFsZWQgUm91dGluZyBQcm90b2NvbCwgS1JQLg0KDQoNCi0tLS0tLS0t
IE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQ
cm90b2NvbCAoS1JQKS4NCkZyb206IExsb3lkIFdvb2QNClRvOiBLaGFsZWQgT21hciAsIiBpZXRm
QGlldGYub3JnIg0KQ0M6DQoNCg0KIktSUCI/DQoNCkhvdyBkbyB5b3UgcHJvbm91bmNlIHRoZSBu
YW1lPw0KDQpMbG95ZCBXb29kIGh0dHA6Ly9hYm91dC5tZS9sbG95ZHdvb2QNCg0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQu
b21hckBob3RtYWlsLmNvbT4NClRvOiAiaWV0ZkBpZXRmLm9yZyIgPGlldGZAaWV0Zi5vcmc+DQpT
ZW50OiBXZWRuZXNkYXksIDI2IEFwcmlsIDIwMTcsIDk6MjcNClN1YmplY3Q6IEtIQUxFRCBSb3V0
aW5nIFByb3RvY29sIChLUlApLg0KDQpIaSBBbGwsDQoNCkkgdGhpbmsgeW91IGFsbCByZWNlaXZl
ZCB0aGUgbm90aWZpY2F0aW9uIHJlZ2FyZGluZyB0aGUgS1JQIElEIHN1Ym1pc3Npb24sIHNvIGhl
cmUgaXMgdGhlIGxpbmsgZm9yIHRoaXMgSW50ZXJuZXQgRHJhZnQ6DQoNCmh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXIta3JwLw0KDQpGb3IgdGhvc2Ugd2hvIGFyZSBp
bnRlcmVzdGVkIGluIGl0LCB5b3Ugd2lsbCBiZSB3ZWxjb21lZCB0byBkaXNjdXNzIGl0IGRpcmVj
dGx5IHdpdGggbWUuDQoNCkxvb2tpbmcgZm9yIHlvdXIgdGhvdWdodHMsIHN1Z2dlc3Rpb25zLCBj
b21tZW50cywgbW9kaWZpY2F0aW9ucyBvciBhbnkga2luZCBvZiBwb3NpdGl2ZSBwYXJ0aWNpcGF0
aW9uLg0KDQpJZiB5b3UgYXJlIG5vdCBpbnRlcmVzdGVkIGluIHRoZSBpZGVhIGFmdGVyIHJlYWRp
bmcgdGhlIGRyYWZ0LCBwbGVhc2UgaWdub3JlIHRoaXMgZS1tYWlsLg0KDQpCZXN0IFJlZ2FyZHMs
DQoNCg0KDQo=

--_000_AM4PR0401MB2241C6379B03E5BDF089FFA1BD130AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <2CEB811012407242AC4F0D2249516B0B@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KU3RlcCBieSBzdGVw
LCBLaGFsZWQgUm91dGluZyBQcm90b2NvbCwgS1JQLg0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxl
PSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEtIQUxFRCBSb3V0aW5nIFByb3RvY29sIChLUlAp
Ljxicj4NCkZyb206IExsb3lkIFdvb2QgPGxsb3lkLndvb2RAeWFob28uY28udWs+PGJyPg0KVG86
IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+LCZxdW90OyBpZXRmQGll
dGYub3JnJnF1b3Q7IDxpZXRmQGlldGYub3JnPjxicj4NCkNDOiA8YnI+DQo8YnI+DQo8YnIgdHlw
ZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2lu
OjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+
DQo8ZGl2IHN0eWxlPSJjb2xvcjojMDAwOyBiYWNrZ3JvdW5kLWNvbG9yOiNmZmY7IGZvbnQtZmFt
aWx5OkNvdXJpZXIgTmV3LCBjb3VyaWVyLCBtb25hY28sIG1vbm9zcGFjZSwgc2Fucy1zZXJpZjtm
b250LXNpemU6MTZweCI+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1
XzcyMTAiPjxzcGFuPiZxdW90O0tSUCZxdW90Oz88L3NwYW4+PC9kaXY+DQo8ZGl2IGlkPSJ5dWlf
M18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMTEiPjxzcGFuPjxicj4NCjwvc3Bhbj48L2Rp
dj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIxMiI+PHNwYW4g
aWQ9Inl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIyOSI+SG93IGRvIHlvdSBwcm9u
b3VuY2UgdGhlIG5hbWU/PC9zcGFuPjwvZGl2Pg0KPGRpdj48L2Rpdj4NCjxkaXYgaWQ9Inl1aV8z
XzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIxMyI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNz
PSJzaWduYXR1cmUiIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMTQiPkxs
b3lkIFdvb2QgaHR0cDovL2Fib3V0Lm1lL2xsb3lkd29vZCZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFz
cz0icXRkU2VwYXJhdGVCUiIgaWQ9Inl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIz
MCI+PGJyPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJ5YWhvb19xdW90ZWQiIGlkPSJ5dWlf
M18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzUiIHN0eWxlPSJkaXNwbGF5OiBibG9jazsi
Pg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IENvdXJpZXIgTmV3LCBjb3VyaWVyLCBtb25hY28s
IG1vbm9zcGFjZSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNnB4OyIgaWQ9Inl1aV8zXzE2XzBf
eW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzNCI+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogSGVs
dmV0aWNhTmV1ZSwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgQXJpYWwsIEx1Y2lkYSBHcmFu
ZGUsIFNhbnMtU2VyaWY7IGZvbnQtc2l6ZTogMTZweDsiIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8x
NDkzMzU5MTE1MjE1XzcyMzMiPg0KPGRpdiBkaXI9Imx0ciIgaWQ9Inl1aV8zXzE2XzBfeW0xOV8x
XzE0OTMzNTkxMTUyMTVfNzIzMiI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiIGlkPSJ5dWlf
M18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzEiPg0KPGhyIHNpemU9IjEiPg0KPGI+PHNw
YW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQ7Ij5Gcm9tOjwvc3Bhbj48L2I+IEtoYWxlZCBPbWFy
ICZsdDtlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20mZ3Q7PGJyPg0KPGI+PHNwYW4gc3R5bGU9
ImZvbnQtd2VpZ2h0OiBib2xkOyI+VG86PC9zcGFuPjwvYj4gJnF1b3Q7aWV0ZkBpZXRmLm9yZyZx
dW90OyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsNCjxicj4NCjxiPjxzcGFuIHN0eWxlPSJmb250LXdl
aWdodDogYm9sZDsiPlNlbnQ6PC9zcGFuPjwvYj4gV2VkbmVzZGF5LCAyNiBBcHJpbCAyMDE3LCA5
OjI3PGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OiBib2xkOyI+U3ViamVjdDo8L3Nw
YW4+PC9iPiBLSEFMRUQgUm91dGluZyBQcm90b2NvbCAoS1JQKS48YnI+DQo8L2ZvbnQ+PC9kaXY+
DQo8ZGl2IGNsYXNzPSJ5X21zZ19jb250YWluZXIiIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkz
MzU5MTE1MjE1XzcyMzYiPjxicj4NCjxkaXYgaWQ9Inlpdjk4NzM5NDUwOTQiPjxzdHlsZT48IS0t
DQojeWl2OTg3Mzk0NTA5NCAgDQogX2ZpbHRlcmVkICN5aXY5ODczOTQ1MDk0IHtmb250LWZhbWls
eToiQ2FtYnJpYSBNYXRoIjtwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCiBfZmlsdGVy
ZWQgI3lpdjk4NzM5NDUwOTQge2ZvbnQtZmFtaWx5OkNhbGlicmk7cGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KI3lpdjk4NzM5NDUwOTQgIA0KI3lpdjk4NzM5NDUwOTQgcC55aXY5ODcz
OTQ1MDk0TXNvTm9ybWFsLCAjeWl2OTg3Mzk0NTA5NCBsaS55aXY5ODczOTQ1MDk0TXNvTm9ybWFs
LCAjeWl2OTg3Mzk0NTA5NCBkaXYueWl2OTg3Mzk0NTA5NE1zb05vcm1hbA0KCXttYXJnaW46MGlu
O21hcmdpbi1ib3R0b206LjAwMDFwdDtmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwgInNhbnMtc2VyaWYiO30NCiN5aXY5ODczOTQ1MDk0IGE6bGluaywgI3lpdjk4NzM5NDUw
OTQgc3Bhbi55aXY5ODczOTQ1MDk0TXNvSHlwZXJsaW5rDQoJe2NvbG9yOiMwNTYzQzE7dGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQojeWl2OTg3Mzk0NTA5NCBhOnZpc2l0ZWQsICN5aXY5ODcz
OTQ1MDk0IHNwYW4ueWl2OTg3Mzk0NTA5NE1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe2NvbG9yOiM5
NTRGNzI7dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQojeWl2OTg3Mzk0NTA5NCBzcGFuLnlp
djk4NzM5NDUwOTRFbWFpbFN0eWxlMTcNCgl7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCAic2Fucy1z
ZXJpZiI7Y29sb3I6d2luZG93dGV4dDt9DQojeWl2OTg3Mzk0NTA5NCAueWl2OTg3Mzk0NTA5NE1z
b0NocERlZmF1bHQNCgl7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCAic2Fucy1zZXJpZiI7fQ0KIF9m
aWx0ZXJlZCAjeWl2OTg3Mzk0NTA5NCB7bWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CiN5aXY5ODczOTQ1MDk0IGRpdi55aXY5ODczOTQ1MDk0V29yZFNlY3Rpb24xDQoJe30NCi0tPjwv
c3R5bGU+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzkiPg0K
PGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NFdvcmRTZWN0aW9uMSIgaWQ9Inl1aV8zXzE2XzBfeW0x
OV8xXzE0OTMzNTkxMTUyMTVfNzIzOCI+DQo8ZGl2IGNsYXNzPSJ5aXY5ODczOTQ1MDk0TXNvTm9y
bWFsIiBpZD0ieXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjM3Ij5IaSBBbGwsPC9k
aXY+DQo8ZGl2IGNsYXNzPSJ5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj4mbmJzcDs8L2Rpdj4NCjxk
aXYgY2xhc3M9Inlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8x
NDkzMzU5MTE1MjE1XzcyNDAiPkkgdGhpbmsgeW91IGFsbCByZWNlaXZlZCB0aGUgbm90aWZpY2F0
aW9uIHJlZ2FyZGluZyB0aGUgS1JQIElEIHN1Ym1pc3Npb24sIHNvIGhlcmUgaXMgdGhlIGxpbmsg
Zm9yIHRoaXMgSW50ZXJuZXQgRHJhZnQ6PC9kaXY+DQo8ZGl2IGNsYXNzPSJ5aXY5ODczOTQ1MDk0
TXNvTm9ybWFsIj4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9Inlpdjk4NzM5NDUwOTRNc29Ob3Jt
YWwiIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyNDIiPjxhIHJlbD0ibm9m
b2xsb3ciIHRhcmdldD0iX2JsYW5rIiBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1vbWFyLWtycC8iIGlkPSJ5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1
XzcyNDEiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXIta3JwLzwv
YT48L2Rpdj4NCjxkaXYgY2xhc3M9Inlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2
Pg0KPGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Inl1aV8zXzE2XzBfeW0x
OV8xXzE0OTMzNTkxMTUyMTVfNzI0MyI+Rm9yIHRob3NlIHdobyBhcmUgaW50ZXJlc3RlZCBpbiBp
dCwgeW91IHdpbGwgYmUgd2VsY29tZWQgdG8gZGlzY3VzcyBpdCBkaXJlY3RseSB3aXRoIG1lLjwv
ZGl2Pg0KPGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Inl1aV8zXzE2XzBf
eW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0NCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJ5aXY5
ODczOTQ1MDk0TXNvTm9ybWFsIj5Mb29raW5nIGZvciB5b3VyIHRob3VnaHRzLCBzdWdnZXN0aW9u
cywgY29tbWVudHMsIG1vZGlmaWNhdGlvbnMgb3IgYW55IGtpbmQgb2YgcG9zaXRpdmUgcGFydGlj
aXBhdGlvbi48L2Rpdj4NCjxkaXYgY2xhc3M9Inlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNw
OzwvZGl2Pg0KPGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+SWYgeW91IGFyZSBu
b3QgaW50ZXJlc3RlZCBpbiB0aGUgaWRlYSBhZnRlciByZWFkaW5nIHRoZSBkcmFmdCwgcGxlYXNl
IGlnbm9yZSB0aGlzIGUtbWFpbC48L2Rpdj4NCjxkaXYgY2xhc3M9Inlpdjk4NzM5NDUwOTRNc29O
b3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+
QmVzdCBSZWdhcmRzLDwvZGl2Pg0KPGRpdiBjbGFzcz0ieWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+
Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8YnI+DQo8YnI+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM4PR0401MB2241C6379B03E5BDF089FFA1BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 00:16:03 2017
Return-Path: <darwin.ggl@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D5B129527 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:16:01 -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 qhfQnWE5TETf for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:15:59 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::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 860DB126DCA for <ietf@ietf.org>; Fri, 28 Apr 2017 00:13:18 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id l50so28465530wrc.3 for <ietf@ietf.org>; Fri, 28 Apr 2017 00:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=93Xk/6mKJ2BPb/L2BicenSca2rqgvlx8x9I2NsQwLzo=; b=dLfAqxOUGJOYuskmad8L9cnwipwQ701iEBcHFszCmFxGy1hQxL0JJ6qsnt+A+BsmJS d026H/xLj5LhlmbSnyG6PtWBFs9bUFFswqegpQ8v85GtVH3P6inMod7wskY+uO8nrDGE YhJVg2RQXOKfREqbHWHt8c8KQVffQrC02AQEFWjZOvH/RPp3LVmSML/Jh6i3vpA/FbB6 NZH6B+i4dDE7dWPmEoqvd3luvATF+9yuwnZK+Xz9wSK0s+rMnjKVR2ME5ZzrTFwuO1XS 74o8BVKEy7TiNPFZJCBBgjSqQkNBrdSnZMo8khy2MBVjwXicmEwRuoaaJZhd5N075ohm ZG5g==
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=93Xk/6mKJ2BPb/L2BicenSca2rqgvlx8x9I2NsQwLzo=; b=P5k1qlPhMTAveqMChh8nZ0tleIG0ryGtT5LZA5G0b42F/fxEZGJjY920nDS5G5l+L7 1dTGabaXSX4mrGp1rfiIuWb8ZOdSarIpYrCUNNGTXEzpNctXXmPYmaxPOXbm+QFe3RWW GYhU96tpzwx//JzttUcBKRkywFLgPGli4pXF6wAhtFRm2R52c4gWZz02YxicA0Bcsfjn P/TTIpvcWNeWvcVLCeHukd12dfCIRw2Ema0WRB1uZacTyfWZMVdPUv0ZIth3liMT8TlL QvcFXHA4U1EXtBbtM1xaVnq+RKhora5Yzw5dzV6USQ18Cbv/9cGwF11a8bGdzFMNvxg1 1CKQ==
X-Gm-Message-State: AN3rC/5BYu/2NJ5pFvQcNfu1KTaTPGAR00Qe09XS4FMyip6TYmtZJ59C f6neg7iepIfzBjgcDi5QjyT/vfj89w==
X-Received: by 10.223.163.215 with SMTP id m23mr5501151wrb.100.1493363597114;  Fri, 28 Apr 2017 00:13:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.151.202 with HTTP; Fri, 28 Apr 2017 00:13:16 -0700 (PDT)
In-Reply-To: <AM4PR0401MB2241C6379B03E5BDF089FFA1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <759171555.14366772.1493361634237@mail.yahoo.com> <AM4PR0401MB2241C6379B03E5BDF089FFA1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Artem Pleschenko <darwin.ggl@gmail.com>
Date: Fri, 28 Apr 2017 10:13:16 +0300
Message-ID: <CACQDv=K-P6hdec+E-k7Z4r1rbZaREXCfaCrsLnav+JXPz6D_YQ@mail.gmail.com>
Subject: Re: KHALED Routing Protocol (KRP).
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: Lloyd Wood <lloyd.wood@yahoo.co.uk>, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f403045f22baba091a054e34ced8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MAfwnVJ26CcM8jqfpvzLhN9-6Kg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 07:16:02 -0000

--f403045f22baba091a054e34ced8
Content-Type: text/plain; charset=UTF-8

A phonetic transcription would be very useful

On 28 April 2017 at 09:56, Khaled Omar <eng.khaled.omar@hotmail.com> wrote:

> Step by step, Khaled Routing Protocol, KRP.
>
>
> -------- Original Message --------
> Subject: Re: KHALED Routing Protocol (KRP).
> From: Lloyd Wood
> To: Khaled Omar ," ietf@ietf.org"
> CC:
>
>
> "KRP"?
>
> How do you pronounce the name?
>
> Lloyd Wood http://about.me/lloydwood
>
>
> ------------------------------
> *From:* Khaled Omar <eng.khaled.omar@hotmail.com>
> *To:* "ietf@ietf.org" <ietf@ietf.org>
> *Sent:* Wednesday, 26 April 2017, 9:27
> *Subject:* KHALED Routing Protocol (KRP).
>
> Hi All,
>
> I think you all received the notification regarding the KRP ID submission,
> so here is the link for this Internet Draft:
>
> https://datatracker.ietf.org/doc/draft-omar-krp/
>
> For those who are interested in it, you will be welcomed to discuss it
> directly with me.
>
> Looking for your thoughts, suggestions, comments, modifications or any
> kind of positive participation.
>
> If you are not interested in the idea after reading the draft, please
> ignore this e-mail.
>
> Best Regards,
>
>
>
>

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

<div dir=3D"ltr"><span style=3D"font-size:12.8px">A phonetic transcription =
would be very useful</span><br></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On 28 April 2017 at 09:56, Khaled Omar <span dir=3D"ltr=
">&lt;<a href=3D"mailto:eng.khaled.omar@hotmail.com" target=3D"_blank">eng.=
khaled.omar@hotmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">



<div>
Step by step, Khaled Routing Protocol, KRP.
<div><div class=3D"h5"><div class=3D"m_2447578687131626804quote" style=3D"l=
ine-height:1.5"><br>
<br>
-------- Original Message --------<br>
Subject: Re: KHALED Routing Protocol (KRP).<br>
From: Lloyd Wood <u></u><br>
To: Khaled Omar <u></u>,&quot; <a href=3D"mailto:ietf@ietf.org" target=3D"_=
blank">ietf@ietf.org</a>&quot; <u></u><br>
CC: <br>
<br>
<br type=3D"attribution">
<blockquote class=3D"m_2447578687131626804quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"color:#000;background-color:#fff;font-family:Courier New,cour=
ier,monaco,monospace,sans-serif;font-size:16px">
<div id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7210"><span=
>&quot;KRP&quot;?</span></div>
<div id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7211"><span=
><br>
</span></div>
<div id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7212"><span=
 id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7229">How do yo=
u pronounce the name?</span></div>
<div></div>
<div id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7213">=C2=
=A0</div>
<div class=3D"m_2447578687131626804signature" id=3D"m_2447578687131626804yu=
i_3_16_0_ym19_1_1493359115215_7214">Lloyd Wood <a href=3D"http://about.me/l=
loydwood" target=3D"_blank">http://about.me/lloydwood</a>=C2=A0</div>
<div class=3D"m_2447578687131626804qtdSeparateBR" id=3D"m_24475786871316268=
04yui_3_16_0_ym19_1_1493359115215_7230"><br>
<br>
</div>
<div class=3D"m_2447578687131626804yahoo_quoted" id=3D"m_244757868713162680=
4yui_3_16_0_ym19_1_1493359115215_7235" style=3D"display:block">
<div style=3D"font-family:Courier New,courier,monaco,monospace,sans-serif;f=
ont-size:16px" id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7=
234">
<div style=3D"font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Luci=
da Grande,Sans-Serif;font-size:16px" id=3D"m_2447578687131626804yui_3_16_0_=
ym19_1_1493359115215_7233">
<div dir=3D"ltr" id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215=
_7232"><font size=3D"2" face=3D"Arial" id=3D"m_2447578687131626804yui_3_16_=
0_ym19_1_1493359115215_7231">
<hr size=3D"1">
<b><span style=3D"font-weight:bold">From:</span></b> Khaled Omar &lt;<a hre=
f=3D"mailto:eng.khaled.omar@hotmail.com" target=3D"_blank">eng.khaled.omar@=
hotmail.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">To:</span></b> &quot;<a href=3D"mailto:=
ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&quot; &lt;<a href=3D"mai=
lto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Wednesday, 26 April 20=
17, 9:27<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> KHALED Routing Prot=
ocol (KRP).<br>
</font></div>
<div class=3D"m_2447578687131626804y_msg_container" id=3D"m_244757868713162=
6804yui_3_16_0_ym19_1_1493359115215_7236"><br>
<div id=3D"m_2447578687131626804yiv9873945094">
<div id=3D"m_2447578687131626804yui_3_16_0_ym19_1_1493359115215_7239">
<div class=3D"m_2447578687131626804yiv9873945094WordSection1" id=3D"m_24475=
78687131626804yui_3_16_0_ym19_1_1493359115215_7238">
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal" id=3D"m_24475786=
87131626804yui_3_16_0_ym19_1_1493359115215_7237">Hi All,</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal" id=3D"m_24475786=
87131626804yui_3_16_0_ym19_1_1493359115215_7240">I think you all received t=
he notification regarding the KRP ID submission, so here is the link for th=
is Internet Draft:</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal" id=3D"m_24475786=
87131626804yui_3_16_0_ym19_1_1493359115215_7242"><a rel=3D"nofollow" href=
=3D"https://datatracker.ietf.org/doc/draft-omar-krp/" id=3D"m_2447578687131=
626804yui_3_16_0_ym19_1_1493359115215_7241" target=3D"_blank">https://datat=
racker.ietf.org/<wbr>doc/draft-omar-krp/</a></div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal" id=3D"m_24475786=
87131626804yui_3_16_0_ym19_1_1493359115215_7243">For those who are interest=
ed in it, you will be welcomed to discuss it directly with me.</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal" id=3D"m_24475786=
87131626804yui_3_16_0_ym19_1_1493359115215_7244">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">Looking for your=
 thoughts, suggestions, comments, modifications or any kind of positive par=
ticipation.</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">If you are not i=
nterested in the idea after reading the draft, please ignore this e-mail.</=
div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">Best Regards,</d=
iv>
<div class=3D"m_2447578687131626804yiv9873945094MsoNormal">=C2=A0</div>
</div>
</div>
</div>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div></div></div>

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

--f403045f22baba091a054e34ced8--


From nobody Fri Apr 28 00:28:34 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46D96129453 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 ieb_ZmWXh8DD for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:28:31 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-oln040092068058.outbound.protection.outlook.com [40.92.68.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F8EC1270FC for <ietf@ietf.org>; Fri, 28 Apr 2017 00:26:06 -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; bh=JdPe5/4i9UZZXxrBXa8X1j7jh3lErJSDUvcR7/BeYeE=; b=I0ky6Ry/THKfqmkm6UhLxC9zzxmOPflVDEjITy+azvsU3YPfZk5ltC6FY6Klm/4CLNNvJOALumSalktBORkPEMQioHBMv6cieg4ufmWoUbW/9CRmoOx6zRxtdvLV9ylSLwNjHaWdkm7luRyRY+tCaNJeGMqVoF8cC+jGjsMwA6HUQC6/pK7dXUvN6EgEXnevCUC96SN5vnAYrMLzSWSNS8ft95xHtKyhF7hbCbwqMwYG2LqBONIzwn45tX7wSdO+PUdrimRmO0KFcRCJT21iYCVCj3a5SiIFZtnbykRKuDVPju5XGrEJzZzGeqrsBCSDvsoX2Sfcc85OCW56fmQNCA==
Received: from HE1EUR02FT063.eop-EUR02.prod.protection.outlook.com (10.152.10.55) by HE1EUR02HT174.eop-EUR02.prod.protection.outlook.com (10.152.11.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 07:26:03 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.10.53) by HE1EUR02FT063.mail.protection.outlook.com (10.152.11.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 07:26:03 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 07:26:03 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>, lloyd.wood <lloyd.wood@yahoo.co.uk>
Subject: Fw: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 07:26:03 +0000
Message-ID: <AM4PR0401MB2241C0BB341D0F76D45C38B6BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CACQDv=K-P6hdec+E-k7Z4r1rbZaREXCfaCrsLnav+JXPz6D_YQ@mail.gmail.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:4EEE2AAED5A84E6388B63CB6D8075972B64A45D4B96EAE10A0B9B6236A73CB62; UpperCasedChecksum:30D574619850D1E70624D4A12A7FF890D737B286D0C264D353DE8944D761CD3B; SizeAsReceived:7875; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT174; 5:R56OeVHyGaYGQssRn6nqA92AWZQBAWeFpJ5dD6XIGgStmF8iZ2d5qKFGKPp0PWoTbHYaZDDOIBAP26GcVk2bmc10bkskGmSp5mrB9rJ1U7TDpvPrWvtIifuxxwl5ZQg7w77xX/Cfacb+tH9GVPPw1wMFapiHQ80U0S0DfTK8ET4=; 24:46ON8Iv6IQYQtKnY6XBteUDmhqIFPhDy44lEqa1in4z/K08t4YriuIWKxcMYNYHu6r1LGc7oJqR0Pq1091ijH9At60Rwc+wPxZecJhgDglg=; 7:oOZONr/xIDrIBxi9/hqOu6N6l6pXG5BboFXYlhN/JPD5IcFas0xJrghZcBD8cKAMr6+SdOvCtY0DyhyZ86lH8kR4vYumIO9nNkSBbhHrzOLalxuZC3SAPaUG9r8lOiQqeJOvcVPjXIgBX9cqrfhfVp0xnVi4cGoFQxo7B0VxTdYOEH2CBYHFHKe7PZjPMza0X8kas7BYFNCjzMw5D5cCvBZAFkr6Guzsx2TGgSSMI0V/TDj41IwODBOZa11+EuK8kIDZ6wd9HsppvIP0CBQUfp6Gjt93RQJ7q6QS6iaoFgpJfankh/+JmI3I+Zd3LVKF
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT174; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: b236b67a-1aa7-4791-8f57-08d48e07d327
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HE1EUR02HT174; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR02HT174; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT174; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241C0BB341D0F76D45C38B6BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 07:26:03.3160 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT174
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WuV3NCp2soJWB1bISjGMhN3rkys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 07:28:33 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFM
RUQgUm91dGluZyBQcm90b2NvbCAoS1JQKS4NCkZyb206IEtoYWxlZCBPbWFyDQpUbzogQXJ0ZW0g
UGxlc2NoZW5rbw0KQ0M6DQoNCg0KQ2hlY2sgdGhpcyBvdXQgaHR0cHM6Ly9tLnlvdXR1YmUuY29t
L3dhdGNoP3Y9WUdlcGZhQ3BhOGMNCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0t
LS0tDQpTdWJqZWN0OiBSZTogS0hBTEVEIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCkuDQpGcm9tOiBB
cnRlbSBQbGVzY2hlbmtvDQpUbzogS2hhbGVkIE9tYXINCkNDOiBMbG95ZCBXb29kICxpZXRmDQoN
Cg0KQSBwaG9uZXRpYyB0cmFuc2NyaXB0aW9uIHdvdWxkIGJlIHZlcnkgdXNlZnVsDQoNCk9uIDI4
IEFwcmlsIDIwMTcgYXQgMDk6NTYsIEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFp
bC5jb208bWFpbHRvOmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4+IHdyb3RlOg0KU3RlcCBi
eSBzdGVwLCBLaGFsZWQgUm91dGluZyBQcm90b2NvbCwgS1JQLg0KDQoNCi0tLS0tLS0tIE9yaWdp
bmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQcm90b2Nv
bCAoS1JQKS4NCkZyb206IExsb3lkIFdvb2QNClRvOiBLaGFsZWQgT21hciAsIiBpZXRmQGlldGYu
b3JnPG1haWx0bzppZXRmQGlldGYub3JnPiINCkNDOg0KDQoNCiJLUlAiPw0KDQpIb3cgZG8geW91
IHByb25vdW5jZSB0aGUgbmFtZT8NCg0KTGxveWQgV29vZCBodHRwOi8vYWJvdXQubWUvbGxveWR3
b29kDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IEtoYWxlZCBP
bWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb208bWFpbHRvOmVuZy5raGFsZWQub21hckBo
b3RtYWlsLmNvbT4+DQpUbzogImlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+IiA8
aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4+DQpTZW50OiBXZWRuZXNkYXksIDI2
IEFwcmlsIDIwMTcsIDk6MjcNClN1YmplY3Q6IEtIQUxFRCBSb3V0aW5nIFByb3RvY29sIChLUlAp
Lg0KDQpIaSBBbGwsDQoNCkkgdGhpbmsgeW91IGFsbCByZWNlaXZlZCB0aGUgbm90aWZpY2F0aW9u
IHJlZ2FyZGluZyB0aGUgS1JQIElEIHN1Ym1pc3Npb24sIHNvIGhlcmUgaXMgdGhlIGxpbmsgZm9y
IHRoaXMgSW50ZXJuZXQgRHJhZnQ6DQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9j
L2RyYWZ0LW9tYXIta3JwLw0KDQpGb3IgdGhvc2Ugd2hvIGFyZSBpbnRlcmVzdGVkIGluIGl0LCB5
b3Ugd2lsbCBiZSB3ZWxjb21lZCB0byBkaXNjdXNzIGl0IGRpcmVjdGx5IHdpdGggbWUuDQoNCkxv
b2tpbmcgZm9yIHlvdXIgdGhvdWdodHMsIHN1Z2dlc3Rpb25zLCBjb21tZW50cywgbW9kaWZpY2F0
aW9ucyBvciBhbnkga2luZCBvZiBwb3NpdGl2ZSBwYXJ0aWNpcGF0aW9uLg0KDQpJZiB5b3UgYXJl
IG5vdCBpbnRlcmVzdGVkIGluIHRoZSBpZGVhIGFmdGVyIHJlYWRpbmcgdGhlIGRyYWZ0LCBwbGVh
c2UgaWdub3JlIHRoaXMgZS1tYWlsLg0KDQpCZXN0IFJlZ2FyZHMsDQoNCg0KDQoNCg==

--_000_AM4PR0401MB2241C0BB341D0F76D45C38B6BD130AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <318BBD617587D649B7BA24111BB06B42@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEtIQUxFRCBSb3V0aW5nIFBy
b3RvY29sIChLUlApLjxicj4NCkZyb206IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90
bWFpbC5jb20+PGJyPg0KVG86IEFydGVtIFBsZXNjaGVua28gPGRhcndpbi5nZ2xAZ21haWwuY29t
Pjxicj4NCkNDOiA8YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVv
dGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4
ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpDaGVjayB0aGlzIG91dCBodHRwczovL20u
eW91dHViZS5jb20vd2F0Y2g/dj1ZR2VwZmFDcGE4Yw0KPGRpdiBjbGFzcz0icXVvdGUiIHN0eWxl
PSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEtIQUxFRCBSb3V0aW5nIFByb3RvY29sIChLUlAp
Ljxicj4NCkZyb206IEFydGVtIFBsZXNjaGVua28gPGRhcndpbi5nZ2xAZ21haWwuY29tPjxicj4N
ClRvOiBLaGFsZWQgT21hciA8ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPjxicj4NCkNDOiBM
bG95ZCBXb29kIDxsbG95ZC53b29kQHlhaG9vLmNvLnVrPixpZXRmIDxpZXRmQGlldGYub3JnPjxi
cj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8YmxvY2txdW90ZSBjbGFzcz0icXVv
dGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtw
YWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgZGlyPSJsdHIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuOHB4Ij5BIHBob25ldGljIHRyYW5zY3JpcHRpb24gd291bGQgYmUgdmVyeSB1c2VmdWw8L3Nw
YW4+PGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPg0KPGRpdiBjbGFz
cz0iZ21haWxfcXVvdGUiPk9uIDI4IEFwcmlsIDIwMTcgYXQgMDk6NTYsIEtoYWxlZCBPbWFyIDxz
cGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmVuZy5raGFsZWQub21hckBob3RtYWls
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTwvYT4mZ3Q7
PC9zcGFuPiB3cm90ZTo8YnI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxl
PSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxl
ZnQ6MWV4Ij4NCjxkaXY+U3RlcCBieSBzdGVwLCBLaGFsZWQgUm91dGluZyBQcm90b2NvbCwgS1JQ
Lg0KPGRpdj4NCjxkaXYgY2xhc3M9Img1Ij4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYy
NjgwNHF1b3RlIiBzdHlsZT0ibGluZS1oZWlnaHQ6MS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBP
cmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEtIQUxFRCBSb3V0aW5n
IFByb3RvY29sIChLUlApLjxicj4NCkZyb206IExsb3lkIFdvb2QgPHU+PC91Pjxicj4NClRvOiBL
aGFsZWQgT21hciA8dT48L3U+LCZxdW90OyA8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyIg
dGFyZ2V0PSJfYmxhbmsiPmlldGZAaWV0Zi5vcmc8L2E+JnF1b3Q7DQo8dT48L3U+PGJyPg0KQ0M6
IDxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8YmxvY2txdW90ZSBjbGFzcz0i
bV8yNDQ3NTc4Njg3MTMxNjI2ODA0cXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3Jk
ZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgc3R5bGU9ImNv
bG9yOiMwMDA7YmFja2dyb3VuZC1jb2xvcjojZmZmO2ZvbnQtZmFtaWx5OkNvdXJpZXIgTmV3LGNv
dXJpZXIsbW9uYWNvLG1vbm9zcGFjZSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxNnB4Ij4NCjxkaXYg
aWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVf
NzIxMCI+PHNwYW4+JnF1b3Q7S1JQJnF1b3Q7Pzwvc3Bhbj48L2Rpdj4NCjxkaXYgaWQ9Im1fMjQ0
NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIxMSI+PHNw
YW4+PGJyPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVp
XzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjEyIj48c3BhbiBpZD0ibV8yNDQ3NTc4Njg3
MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjI5Ij5Ib3cgZG8geW91
IHByb25vdW5jZSB0aGUgbmFtZT88L3NwYW4+PC9kaXY+DQo8ZGl2PjwvZGl2Pg0KPGRpdiBpZD0i
bV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjEz
Ij4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHNpZ25hdHVy
ZSIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUy
MTVfNzIxNCI+DQpMbG95ZCBXb29kIDxhIGhyZWY9Imh0dHA6Ly9hYm91dC5tZS9sbG95ZHdvb2Qi
IHRhcmdldD0iX2JsYW5rIj5odHRwOi8vYWJvdXQubWUvbGxveWR3b29kPC9hPiZuYnNwOzwvZGl2
Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0cXRkU2VwYXJhdGVCUiIgaWQ9Im1f
MjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzMCI+
DQo8YnI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlh
aG9vX3F1b3RlZCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0
OTMzNTkxMTUyMTVfNzIzNSIgc3R5bGU9ImRpc3BsYXk6YmxvY2siPg0KPGRpdiBzdHlsZT0iZm9u
dC1mYW1pbHk6Q291cmllciBOZXcsY291cmllcixtb25hY28sbW9ub3NwYWNlLHNhbnMtc2VyaWY7
Zm9udC1zaXplOjE2cHgiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlf
MV8xNDkzMzU5MTE1MjE1XzcyMzQiPg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6SGVsdmV0aWNh
TmV1ZSxIZWx2ZXRpY2EgTmV1ZSxIZWx2ZXRpY2EsQXJpYWwsTHVjaWRhIEdyYW5kZSxTYW5zLVNl
cmlmO2ZvbnQtc2l6ZToxNnB4IiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95
bTE5XzFfMTQ5MzM1OTExNTIxNV83MjMzIj4NCjxkaXYgZGlyPSJsdHIiIGlkPSJtXzI0NDc1Nzg2
ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzIiPjxmb250IHNp
emU9IjIiIGZhY2U9IkFyaWFsIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95
bTE5XzFfMTQ5MzM1OTExNTIxNV83MjMxIj4NCjxociBzaXplPSIxIj4NCjxiPjxzcGFuIHN0eWxl
PSJmb250LXdlaWdodDpib2xkIj5Gcm9tOjwvc3Bhbj48L2I+IEtoYWxlZCBPbWFyICZsdDs8YSBo
cmVmPSJtYWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+
ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPC9hPiZndDs8YnI+DQo8Yj48c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+VG86PC9zcGFuPjwvYj4gJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmll
dGZAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZXRmQGlldGYub3JnPC9hPiZxdW90OyAmbHQ7
PGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZXRmQGlldGYu
b3JnPC9hPiZndDsNCjxicj4NCjxiPjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5TZW50
Ojwvc3Bhbj48L2I+IFdlZG5lc2RheSwgMjYgQXByaWwgMjAxNywgOToyNzxicj4NCjxiPjxzcGFu
IHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5TdWJqZWN0Ojwvc3Bhbj48L2I+IEtIQUxFRCBSb3V0
aW5nIFByb3RvY29sIChLUlApLjxicj4NCjwvZm9udD48L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0
NzU3ODY4NzEzMTYyNjgwNHlfbXNnX2NvbnRhaW5lciIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgw
NHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzNiI+DQo8YnI+DQo8ZGl2IGlkPSJt
XzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0Ij4NCjxkaXYgaWQ9Im1fMjQ0NzU3ODY4
NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzOSI+DQo8ZGl2IGNs
YXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0V29yZFNlY3Rpb24xIiBpZD0i
bV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjM4
Ij4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3Jt
YWwiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1
MjE1XzcyMzciPg0KSGkgQWxsLDwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2
ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0
NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIiBpZD0ibV8yNDQ3NTc4Njg3
MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjQwIj4NCkkgdGhpbmsg
eW91IGFsbCByZWNlaXZlZCB0aGUgbm90aWZpY2F0aW9uIHJlZ2FyZGluZyB0aGUgS1JQIElEIHN1
Ym1pc3Npb24sIHNvIGhlcmUgaXMgdGhlIGxpbmsgZm9yIHRoaXMgSW50ZXJuZXQgRHJhZnQ6PC9k
aXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9y
bWFsIj4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4
NzM5NDUwOTRNc29Ob3JtYWwiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3lt
MTlfMV8xNDkzMzU5MTE1MjE1XzcyNDIiPg0KPGEgcmVsPSJub2ZvbGxvdyIgaHJlZj0iaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtb21hci1rcnAvIiBpZD0ibV8yNDQ3NTc4
Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjQxIiB0YXJnZXQ9
Il9ibGFuayI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy88d2JyPmRvYy9kcmFmdC1vbWFy
LWtycC88L2E+PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODcz
OTQ1MDk0TXNvTm9ybWFsIj4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEz
MTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5
dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyNDMiPg0KRm9yIHRob3NlIHdobyBhcmUg
aW50ZXJlc3RlZCBpbiBpdCwgeW91IHdpbGwgYmUgd2VsY29tZWQgdG8gZGlzY3VzcyBpdCBkaXJl
Y3RseSB3aXRoIG1lLjwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2
OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBf
eW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0NCI+DQombmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9Im1f
MjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPkxvb2tpbmcgZm9yIHlv
dXIgdGhvdWdodHMsIHN1Z2dlc3Rpb25zLCBjb21tZW50cywgbW9kaWZpY2F0aW9ucyBvciBhbnkg
a2luZCBvZiBwb3NpdGl2ZSBwYXJ0aWNpcGF0aW9uLjwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3
NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+Jm5ic3A7PC9kaXY+DQo8ZGl2
IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj5JZiB5
b3UgYXJlIG5vdCBpbnRlcmVzdGVkIGluIHRoZSBpZGVhIGFmdGVyIHJlYWRpbmcgdGhlIGRyYWZ0
LCBwbGVhc2UgaWdub3JlIHRoaXMgZS1tYWlsLjwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4
Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNs
YXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj5CZXN0IFJl
Z2FyZHMsPC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1
MDk0TXNvTm9ybWFsIj4mbmJzcDs8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxicj4N
Cjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPGJyPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM4PR0401MB2241C0BB341D0F76D45C38B6BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 00:44:54 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71442127369 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 pkUWT5fzfFBO for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 00:44:51 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071067.outbound.protection.outlook.com [40.92.71.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 948BA129C56 for <ietf@ietf.org>; Fri, 28 Apr 2017 00:42:01 -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; bh=K+XAFv3kdAKq5bpYutJlvHGFuh6o8uI0Vv9HlLJmK90=; b=I1F2ieJeR1CIBIQbjNIHOO5JSicA9puf1aiXhpEy/AES1qS/UJKttKqc/61ur/tQOGfDzo00Z4QnjavJYMHOZyjRoN8nCUog0diXec/ea2nthiId7UOrg69hB8mH2XK2Tx3akjcGI56D9TV+3tFE3ojnWFUE8yCIDXA2XZAvObRZ7tej1KZwAULrLQSoeL3uMA2GyHpNQaHWm/oXWEIyBz/hRyhew6YApl7J0313YxN7k98mcpkk3Zu9PxBk/Zm03595CQtYLd+FgDVp4K0e6xOVJ4LyGWOl2zPJOpQ2u/kk92KXEyZP45JRiegF1oHbGcnKkLU0xcakXHP11OPkQg==
Received: from VE1EUR03FT056.eop-EUR03.prod.protection.outlook.com (10.152.18.54) by VE1EUR03HT248.eop-EUR03.prod.protection.outlook.com (10.152.19.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 07:41:59 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.18.58) by VE1EUR03FT056.mail.protection.outlook.com (10.152.19.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 07:41:59 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 07:41:59 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Artem Pleschenko <darwin.ggl@gmail.com>
CC: ietf <ietf@ietf.org>
Subject: Re: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 07:41:58 +0000
Message-ID: <AM4PR0401MB22419FC836CB84B868EFFA79BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CACQDv=K-P6hdec+E-k7Z4r1rbZaREXCfaCrsLnav+JXPz6D_YQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:55F03A814CB8B3A5E397EC42D22BF2C523FD066268954EC57B0117AA82F8CC35; UpperCasedChecksum:064E50794D43DF79A222E642C970399E8AE0FC70A96613912A0FA6F73C91BF0E; SizeAsReceived:7873; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR03HT248; 5:x01iQGKbDfCFiUULU8eHyyxf5prisPZB8ex9T0Jqu9SMKNzdjqK2ps/lMiMTNpbEDdnzExl/QxoMcyohmTKI0aZa0FsB8ryl9H9VkkwQ5PaLjNh6z31AC0kaldkEqHyNV8dnzoLJOG07g2+SncmE6F4V9IkHJPQ70qaoHeWf6AA=; 24:H9GsDDqHdHSO2Ly4LqPW9OKg5YiMgHe1SQGUNK9fmLzPqomjS88+S2iby1Ht7fuSMMQ40kougQCuHeanJ+Oqf5CuSIXTOzPAjzPOSlE0DJI=; 7:UurvQFIEHvBuykt2fxfyfm4/G4byc9umE2XxW88+hFcDq1Wgn/4xlyPJoc1J0AezwKBqozYYpN8aSDsz+CueXuUyYFA3Pw88rzFGugcpMcfUS8DH/7V/CBPidHfml9p21EWg5USVQT18897MpDM7qYXp9lJ4kspFJZ1jLPEJY6tPUGJw+gH7nkekZUsde+6JAdpmwocCbJKfFI1zy9DrPZYfqUPBTK/dJfj4S30YF+Lad0ZhG0o5fSu2G7en1Hr8Gz/hi8iP8eLzr/eOXZrrDcwc4j6buc75iiyYRCTXefAyzbSaKLwh8WZEuiBnlQiy
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR03HT248; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: b909c712-8e98-4271-c389-08d48e0a0ca6
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR03HT248; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR03HT248; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR03HT248; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB22419FC836CB84B868EFFA79BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 07:41:59.0074 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR03HT248
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SyQfgMSWb2HSJmTx0gHtYCVDEjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 07:44:52 -0000

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

SSBwcmVmZXIgdGhlIGZpcnN0IHByb25vdW5jaWF0aW9uLCBiZWNhdXNlIHRoZSBLSCBpcyBhIGxl
dHRlciBpbiBhcmFiaWMgbm90IGV4aXN0aW5nIGluIGVuZ2xpc2guDQoNCg0KaHR0cHM6Ly9tLnlv
dXR1YmUuY29tL3dhdGNoP3Y9WGMxYnFZN2V5WFUNCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNz
YWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogS0hBTEVEIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCku
DQpGcm9tOiBBcnRlbSBQbGVzY2hlbmtvDQpUbzogS2hhbGVkIE9tYXINCkNDOiBMbG95ZCBXb29k
ICxpZXRmDQoNCg0KQSBwaG9uZXRpYyB0cmFuc2NyaXB0aW9uIHdvdWxkIGJlIHZlcnkgdXNlZnVs
DQoNCk9uIDI4IEFwcmlsIDIwMTcgYXQgMDk6NTYsIEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9t
YXJAaG90bWFpbC5jb208bWFpbHRvOmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4+IHdyb3Rl
Og0KU3RlcCBieSBzdGVwLCBLaGFsZWQgUm91dGluZyBQcm90b2NvbCwgS1JQLg0KDQoNCi0tLS0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGlu
ZyBQcm90b2NvbCAoS1JQKS4NCkZyb206IExsb3lkIFdvb2QNClRvOiBLaGFsZWQgT21hciAsIiBp
ZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPiINCkNDOg0KDQoNCiJLUlAiPw0KDQpI
b3cgZG8geW91IHByb25vdW5jZSB0aGUgbmFtZT8NCg0KTGxveWQgV29vZCBodHRwOi8vYWJvdXQu
bWUvbGxveWR3b29kDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206
IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb208bWFpbHRvOmVuZy5raGFs
ZWQub21hckBob3RtYWlsLmNvbT4+DQpUbzogImlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0
Zi5vcmc+IiA8aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4+DQpTZW50OiBXZWRu
ZXNkYXksIDI2IEFwcmlsIDIwMTcsIDk6MjcNClN1YmplY3Q6IEtIQUxFRCBSb3V0aW5nIFByb3Rv
Y29sIChLUlApLg0KDQpIaSBBbGwsDQoNCkkgdGhpbmsgeW91IGFsbCByZWNlaXZlZCB0aGUgbm90
aWZpY2F0aW9uIHJlZ2FyZGluZyB0aGUgS1JQIElEIHN1Ym1pc3Npb24sIHNvIGhlcmUgaXMgdGhl
IGxpbmsgZm9yIHRoaXMgSW50ZXJuZXQgRHJhZnQ6DQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LW9tYXIta3JwLw0KDQpGb3IgdGhvc2Ugd2hvIGFyZSBpbnRlcmVzdGVk
IGluIGl0LCB5b3Ugd2lsbCBiZSB3ZWxjb21lZCB0byBkaXNjdXNzIGl0IGRpcmVjdGx5IHdpdGgg
bWUuDQoNCkxvb2tpbmcgZm9yIHlvdXIgdGhvdWdodHMsIHN1Z2dlc3Rpb25zLCBjb21tZW50cywg
bW9kaWZpY2F0aW9ucyBvciBhbnkga2luZCBvZiBwb3NpdGl2ZSBwYXJ0aWNpcGF0aW9uLg0KDQpJ
ZiB5b3UgYXJlIG5vdCBpbnRlcmVzdGVkIGluIHRoZSBpZGVhIGFmdGVyIHJlYWRpbmcgdGhlIGRy
YWZ0LCBwbGVhc2UgaWdub3JlIHRoaXMgZS1tYWlsLg0KDQpCZXN0IFJlZ2FyZHMsDQoNCg0KDQoN
Cg==

--_000_AM4PR0401MB22419FC836CB84B868EFFA79BD130AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <DD0C088780E9344C93944D461A272B98@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSSBwcmVmZXIgdGhl
IGZpcnN0IHByb25vdW5jaWF0aW9uLCBiZWNhdXNlIHRoZSBLSCBpcyBhIGxldHRlciBpbiBhcmFi
aWMgbm90IGV4aXN0aW5nIGluIGVuZ2xpc2guPGJyPg0KPGJyPg0KPGJyPg0KaHR0cHM6Ly9tLnlv
dXR1YmUuY29tL3dhdGNoP3Y9WGMxYnFZN2V5WFUNCjxkaXYgY2xhc3M9InF1b3RlIiBzdHlsZT0i
bGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAt
LS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQcm90b2NvbCAoS1JQKS48
YnI+DQpGcm9tOiBBcnRlbSBQbGVzY2hlbmtvIDxkYXJ3aW4uZ2dsQGdtYWlsLmNvbT48YnI+DQpU
bzogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpDQzogTGxv
eWQgV29vZCA8bGxveWQud29vZEB5YWhvby5jby51az4saWV0ZiA8aWV0ZkBpZXRmLm9yZz48YnI+
DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9InF1b3Rl
IiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFk
ZGluZy1sZWZ0OjFleCI+DQo8ZGl2IGRpcj0ibHRyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjhweCI+QSBwaG9uZXRpYyB0cmFuc2NyaXB0aW9uIHdvdWxkIGJlIHZlcnkgdXNlZnVsPC9zcGFu
Pjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj4NCjxkaXYgY2xhc3M9
ImdtYWlsX3F1b3RlIj5PbiAyOCBBcHJpbCAyMDE3IGF0IDA5OjU2LCBLaGFsZWQgT21hciA8c3Bh
biBkaXI9Imx0ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzplbmcua2hhbGVkLm9tYXJAaG90bWFpbC5j
b20iIHRhcmdldD0iX2JsYW5rIj5lbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb208L2E+Jmd0Ozwv
c3Bhbj4gd3JvdGU6PGJyPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0i
bWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0
OjFleCI+DQo8ZGl2PlN0ZXAgYnkgc3RlcCwgS2hhbGVkIFJvdXRpbmcgUHJvdG9jb2wsIEtSUC4N
CjxkaXY+DQo8ZGl2IGNsYXNzPSJoNSI+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4
MDRxdW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OjEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQ
cm90b2NvbCAoS1JQKS48YnI+DQpGcm9tOiBMbG95ZCBXb29kIDx1PjwvdT48YnI+DQpUbzogS2hh
bGVkIE9tYXIgPHU+PC91PiwmcXVvdDsgPGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj5pZXRmQGlldGYub3JnPC9hPiZxdW90Ow0KPHU+PC91Pjxicj4NCkNDOiA8
YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xhc3M9Im1f
MjQ0NzU3ODY4NzEzMTYyNjgwNHF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVy
LWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8ZGl2IHN0eWxlPSJjb2xv
cjojMDAwO2JhY2tncm91bmQtY29sb3I6I2ZmZjtmb250LWZhbWlseTpDb3VyaWVyIE5ldyxjb3Vy
aWVyLG1vbmFjbyxtb25vc3BhY2Usc2Fucy1zZXJpZjtmb250LXNpemU6MTZweCI+DQo8ZGl2IGlk
PSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1Xzcy
MTAiPjxzcGFuPiZxdW90O0tSUCZxdW90Oz88L3NwYW4+PC9kaXY+DQo8ZGl2IGlkPSJtXzI0NDc1
Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMTEiPjxzcGFu
Pjxicj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXYgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8z
XzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIxMiI+PHNwYW4gaWQ9Im1fMjQ0NzU3ODY4NzEz
MTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIyOSI+SG93IGRvIHlvdSBw
cm9ub3VuY2UgdGhlIG5hbWU/PC9zcGFuPjwvZGl2Pg0KPGRpdj48L2Rpdj4NCjxkaXYgaWQ9Im1f
MjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIxMyI+
Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDRzaWduYXR1cmUi
IGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1
XzcyMTQiPg0KTGxveWQgV29vZCA8YSBocmVmPSJodHRwOi8vYWJvdXQubWUvbGxveWR3b29kIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cDovL2Fib3V0Lm1lL2xsb3lkd29vZDwvYT4mbmJzcDs8L2Rpdj4N
CjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHF0ZFNlcGFyYXRlQlIiIGlkPSJtXzI0
NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzAiPg0K
PGJyPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5YWhv
b19xdW90ZWQiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkz
MzU5MTE1MjE1XzcyMzUiIHN0eWxlPSJkaXNwbGF5OmJsb2NrIj4NCjxkaXYgc3R5bGU9ImZvbnQt
ZmFtaWx5OkNvdXJpZXIgTmV3LGNvdXJpZXIsbW9uYWNvLG1vbm9zcGFjZSxzYW5zLXNlcmlmO2Zv
bnQtc2l6ZToxNnB4IiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFf
MTQ5MzM1OTExNTIxNV83MjM0Ij4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkhlbHZldGljYU5l
dWUsSGVsdmV0aWNhIE5ldWUsSGVsdmV0aWNhLEFyaWFsLEx1Y2lkYSBHcmFuZGUsU2Fucy1TZXJp
Zjtmb250LXNpemU6MTZweCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0x
OV8xXzE0OTMzNTkxMTUyMTVfNzIzMyI+DQo8ZGl2IGRpcj0ibHRyIiBpZD0ibV8yNDQ3NTc4Njg3
MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjMyIj48Zm9udCBzaXpl
PSIyIiBmYWNlPSJBcmlhbCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0x
OV8xXzE0OTMzNTkxMTUyMTVfNzIzMSI+DQo8aHIgc2l6ZT0iMSI+DQo8Yj48c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTo8L3NwYW4+PC9iPiBLaGFsZWQgT21hciAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmVu
Zy5raGFsZWQub21hckBob3RtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZv
bnQtd2VpZ2h0OmJvbGQiPlRvOjwvc3Bhbj48L2I+ICZxdW90OzxhIGhyZWY9Im1haWx0bzppZXRm
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT4mcXVvdDsgJmx0Ozxh
IGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9y
ZzwvYT4mZ3Q7DQo8YnI+DQo8Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U2VudDo8
L3NwYW4+PC9iPiBXZWRuZXNkYXksIDI2IEFwcmlsIDIwMTcsIDk6Mjc8YnI+DQo8Yj48c3BhbiBz
dHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDo8L3NwYW4+PC9iPiBLSEFMRUQgUm91dGlu
ZyBQcm90b2NvbCAoS1JQKS48YnI+DQo8L2ZvbnQ+PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1
Nzg2ODcxMzE2MjY4MDR5X21zZ19jb250YWluZXIiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5
dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzYiPg0KPGJyPg0KPGRpdiBpZD0ibV8y
NDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NCI+DQo8ZGl2IGlkPSJtXzI0NDc1Nzg2ODcx
MzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzkiPg0KPGRpdiBjbGFz
cz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NFdvcmRTZWN0aW9uMSIgaWQ9Im1f
MjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzOCI+
DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFs
IiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIx
NV83MjM3Ij4NCkhpIEFsbCw8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgw
NHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3
NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Im1fMjQ0NzU3ODY4NzEz
MTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0MCI+DQpJIHRoaW5rIHlv
dSBhbGwgcmVjZWl2ZWQgdGhlIG5vdGlmaWNhdGlvbiByZWdhcmRpbmcgdGhlIEtSUCBJRCBzdWJt
aXNzaW9uLCBzbyBoZXJlIGlzIHRoZSBsaW5rIGZvciB0aGlzIEludGVybmV0IERyYWZ0OjwvZGl2
Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1h
bCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODcz
OTQ1MDk0TXNvTm9ybWFsIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5
XzFfMTQ5MzM1OTExNTIxNV83MjQyIj4NCjxhIHJlbD0ibm9mb2xsb3ciIGhyZWY9Imh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXIta3JwLyIgaWQ9Im1fMjQ0NzU3ODY4
NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0MSIgdGFyZ2V0PSJf
YmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvPHdicj5kb2MvZHJhZnQtb21hci1r
cnAvPC9hPjwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0
NTA5NE1zb05vcm1hbCI+Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2
MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVp
XzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjQzIj4NCkZvciB0aG9zZSB3aG8gYXJlIGlu
dGVyZXN0ZWQgaW4gaXQsIHlvdSB3aWxsIGJlIHdlbGNvbWVkIHRvIGRpc2N1c3MgaXQgZGlyZWN0
bHkgd2l0aCBtZS48L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4
NzM5NDUwOTRNc29Ob3JtYWwiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3lt
MTlfMV8xNDkzMzU5MTE1MjE1XzcyNDQiPg0KJm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0
NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj5Mb29raW5nIGZvciB5b3Vy
IHRob3VnaHRzLCBzdWdnZXN0aW9ucywgY29tbWVudHMsIG1vZGlmaWNhdGlvbnMgb3IgYW55IGtp
bmQgb2YgcG9zaXRpdmUgcGFydGljaXBhdGlvbi48L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3
ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBj
bGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+SWYgeW91
IGFyZSBub3QgaW50ZXJlc3RlZCBpbiB0aGUgaWRlYSBhZnRlciByZWFkaW5nIHRoZSBkcmFmdCwg
cGxlYXNlIGlnbm9yZSB0aGlzIGUtbWFpbC48L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4
NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFz
cz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+QmVzdCBSZWdh
cmRzLDwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5
NE1zb05vcm1hbCI+Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8YnI+DQo8
YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
Cjxicj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM4PR0401MB22419FC836CB84B868EFFA79BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 01:20:54 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 107CE129C4A for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 01:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 4grTsOlWzVD2 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 01:20:50 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069074.outbound.protection.outlook.com [40.92.69.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1311129C6C for <ietf@ietf.org>; Fri, 28 Apr 2017 01:18:10 -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; bh=Qs1sCCK90AFovMSsnBLgjsU8SyLmngvgo7TM48b31g4=; b=l49cV2cSo0xTh+jd9oUWUAwnFrialOzG/i48poRBVYGt71OXn9ytsay85bzs/yQwvG2HzUQ26RLZRkNC/te6s26MASWSWUO2SamusrpyxiicVscqGB7UPosJd3baUhK1t4eEJ1+Z7Mu4Vf2lryQKkMV9Alf+adW3soVZdOlWLS5ajJ61z2pi78a6zAPpAMJrOKuoAaFSbsa97+2fBTUpZeyOt7ZdcD/L4gwmkRAU+IIL06hcEtvm5GXe0RZWOrQ9S689sSLEDyjjYzXuBiHhXaUQaSpce8n5F5eWjh2X7c48DdmjoiuEuBE7JwCz+K6WBOX6MB0GmJn5GO421nRmRg==
Received: from VE1EUR02FT011.eop-EUR02.prod.protection.outlook.com (10.152.12.59) by VE1EUR02HT009.eop-EUR02.prod.protection.outlook.com (10.152.12.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 08:18:08 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.12.60) by VE1EUR02FT011.mail.protection.outlook.com (10.152.12.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 08:18:08 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 08:18:08 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Re: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 08:18:08 +0000
Message-ID: <AM4PR0401MB224196ADFBE0D14995555B06BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CACQDv=K-P6hdec+E-k7Z4r1rbZaREXCfaCrsLnav+JXPz6D_YQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:699B3D6BC93AC8910597163745D90B13312DB61E95A0E05A91964690DD13F3E6; UpperCasedChecksum:1B6AEBB5789EC031DAA14A2041EDE8BC944D3A19F5A34E479C7319F90129869F; SizeAsReceived:7819; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR02HT009; 5:V9O7nBnvi9abV/K8j7/IVoT5o8Q8MNEWcZj3HfDsIRfejw6A9EuaVnCeYoTpQXP93U7TGMmxE1VZVYZO4/kS1TqEuibPWFUvgoKBdUgd9vF85k09PZ62zg4o3oogkugwt8foQ1UFTLTegGpEt8Bj3Q==; 24:ICiKJP/6Ywq16AaQ7xW6t1GROFjXcU9WxmwL6HiuFPkhZRcBepl+QAjInFqKkmXLUIWww+w+BccMogYKIvKecKM/NuvBEGi63nnTzGpYFNE=; 7:Bnd4NKz52v/fcuttoqlNSrh93S4TXNjYJWJ+LANCs96Ldykgnc0paJ42gxPFbKiaR+gwvkdX2AgbOj5BIS9h8tm1GtmeCzhvxCaL+EivtXCHPV7O8EvznC+Ll8eKHwtKg8SMeJS4X+ku3yzVUnhl0PIwYXKTggnlurasIvzkzjQFlxcKMaNNIM8SoWv9rtZMfdge94IijlDoIPJakhkLf4x0nG10YauxXUgopKOMzqTrDRDvsf8e5/AxM4WI79TsU20Ta1MuBlmyGmdjTupykLevw/044RDFdIqQ0dwIbgYzso+HQAT1rdta9kGBUONI
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR02HT009; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: cbfc5526-8b42-49a2-e49e-08d48e0f19c9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(201702181274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR02HT009; 
x-ms-exchange-slblob-mailprops: ZK1LJjhzK/CyLS8UtIYV+m3tT4su7Jiz1Dv4njdyUhO6K03ab9ec2y7X01C2d8s38gIgB1uCyUZk1GohOZC8E4NiNNkP0OQhoFfzIGbTyKX27NKnOvaQZrONXm8vBwpxkD34he4/REOkjD+t8GQSqX3jWtuBz8pi4uFy0/j7F+ExnZKbxzAx7kDKCB/9DKHIXEF/MmiLjXbvR/4/dl8VkzrHiqI8BRASXIWSHwemuyN8OQC0TUE/tI+8uClI9AZPadQyojZfP44Hnufj5XIMI7FOs1XTAXEqu7fwjZRPkvZTvSOlDx5N3d+AM38zRij2r264vijwaLhBoOrpVjafVieP8drham9fOTEnOJvcA1iTepIERB7MuVTNhNUAQtyL7KiUxpdJFpEN94Cusm1M+SMCoGRWxpqajuyDT1CAHkPQHuYQTSYkYPUaJccYtaHDoME4apdO4yRP6HkWhjbcMO+VvLvUYMLZFhY9PSqWTxeHNp/1nHw816g36FlvPIuUt3NvRnKTSpuuTZD75x+Wac8dfbVx16dla3i6lzENz2FYJcgV8f89lg2/m/UhSNrHaOOIm46eA6nrcmf7t1VJ24mTzjVPao3Kgjiz86jWttP1CH80S5NKk+neyoRcXftZgWW68ybd5TMEvruwTJ5lSYjFXPvPHe0m62rzOr0cU//pI/SsjVUi+0js3RAotR1z85nDS6TPK/oq/O+FRf3gXi9bRoYiKMWmO41/ZcwIUuKtRXwy8R796mjaSxuWAIAR85A5VuAMizucqrqiVJe+DTtKCk6+q+lXfInH8zulK+a3NrLcNR8M2d8hG455iyRYOALyJZBUoHFlTBdGyUc7S4qeJ8xJ5TjK5DjH6mKRwg5VZtrbjzTRUhb40dpiz+SMSbaG1PrIFxKdZ/z74lff16TJOfFuOaM1R0+YZ29EcXFc5Q7PhBiJdnBYF3j3171A
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR02HT009; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR02HT009; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB224196ADFBE0D14995555B06BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 08:18:08.3865 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT009
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lN2gaH1uuDvMbmMlLaPmEl7wXEM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 08:20:52 -0000

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

QWxsLA0KDQpQbGVhc2UgbGV0cyBmb2N1cyBvbiB0aGUgY29yZSB2YWx1ZSByZWdhcmRsZXNzIHdo
YXQgaXMgdGhlIG5ldyBwcm90b2NvbCdzIG5hbWUgYmVjYXVzZSB0aGlzIG5hbWUgY2FuIGJlIGNo
YW5nZWQgYmFzZWQgb24gd2hhdCB3aWxsIGJlIGFkZGVkIG1vcmUgYW5kIHdobyB3aWxsIGFkZCwg
Y2hvb3NpbmcgYSBuZXcgbmFtZSByZXF1aXJlcyBhIGRpc2N1c3Npb24gYW5kIEkgZG9uJ3QgbWlu
ZCwgYnV0IGZpcnN0IHdlIG5lZWQgdG8gZGlzY3VzcyBob3cgdG8gbWFrZSB0aGUgZHJhZnQgaW4g
dGhlIGJlc3QgZm9ybSBiZWZvcmUgaXQgaXMgYmVpbmcgcHVibGlzaGVkLg0KDQoNCi0tLS0tLS0t
IE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQ
cm90b2NvbCAoS1JQKS4NCkZyb206IEFydGVtIFBsZXNjaGVua28NClRvOiBLaGFsZWQgT21hcg0K
Q0M6IExsb3lkIFdvb2QgLGlldGYNCg0KDQpBIHBob25ldGljIHRyYW5zY3JpcHRpb24gd291bGQg
YmUgdmVyeSB1c2VmdWwNCg0KT24gMjggQXByaWwgMjAxNyBhdCAwOTo1NiwgS2hhbGVkIE9tYXIg
PGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTxtYWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhvdG1h
aWwuY29tPj4gd3JvdGU6DQpTdGVwIGJ5IHN0ZXAsIEtoYWxlZCBSb3V0aW5nIFByb3RvY29sLCBL
UlAuDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0KU3ViamVjdDogUmU6
IEtIQUxFRCBSb3V0aW5nIFByb3RvY29sIChLUlApLg0KRnJvbTogTGxveWQgV29vZA0KVG86IEto
YWxlZCBPbWFyICwiIGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+Ig0KQ0M6DQoN
Cg0KIktSUCI/DQoNCkhvdyBkbyB5b3UgcHJvbm91bmNlIHRoZSBuYW1lPw0KDQpMbG95ZCBXb29k
IGh0dHA6Ly9hYm91dC5tZS9sbG95ZHdvb2QNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KRnJvbTogS2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbTxt
YWlsdG86ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwuY29tPj4NClRvOiAiaWV0ZkBpZXRmLm9yZzxt
YWlsdG86aWV0ZkBpZXRmLm9yZz4iIDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3Jn
Pj4NClNlbnQ6IFdlZG5lc2RheSwgMjYgQXByaWwgMjAxNywgOToyNw0KU3ViamVjdDogS0hBTEVE
IFJvdXRpbmcgUHJvdG9jb2wgKEtSUCkuDQoNCkhpIEFsbCwNCg0KSSB0aGluayB5b3UgYWxsIHJl
Y2VpdmVkIHRoZSBub3RpZmljYXRpb24gcmVnYXJkaW5nIHRoZSBLUlAgSUQgc3VibWlzc2lvbiwg
c28gaGVyZSBpcyB0aGUgbGluayBmb3IgdGhpcyBJbnRlcm5ldCBEcmFmdDoNCg0KaHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtb21hci1rcnAvDQoNCkZvciB0aG9zZSB3aG8g
YXJlIGludGVyZXN0ZWQgaW4gaXQsIHlvdSB3aWxsIGJlIHdlbGNvbWVkIHRvIGRpc2N1c3MgaXQg
ZGlyZWN0bHkgd2l0aCBtZS4NCg0KTG9va2luZyBmb3IgeW91ciB0aG91Z2h0cywgc3VnZ2VzdGlv
bnMsIGNvbW1lbnRzLCBtb2RpZmljYXRpb25zIG9yIGFueSBraW5kIG9mIHBvc2l0aXZlIHBhcnRp
Y2lwYXRpb24uDQoNCklmIHlvdSBhcmUgbm90IGludGVyZXN0ZWQgaW4gdGhlIGlkZWEgYWZ0ZXIg
cmVhZGluZyB0aGUgZHJhZnQsIHBsZWFzZSBpZ25vcmUgdGhpcyBlLW1haWwuDQoNCkJlc3QgUmVn
YXJkcywNCg0KDQoNCg0K

--_000_AM4PR0401MB224196ADFBE0D14995555B06BD130AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <257DBEA07641CF48BC567857FB022922@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KQWxsLCA8YnI+DQo8
YnI+DQpQbGVhc2UgbGV0cyBmb2N1cyBvbiB0aGUgY29yZSB2YWx1ZSByZWdhcmRsZXNzIHdoYXQg
aXMgdGhlIG5ldyBwcm90b2NvbCdzIG5hbWUgYmVjYXVzZSB0aGlzIG5hbWUgY2FuIGJlIGNoYW5n
ZWQgYmFzZWQgb24gd2hhdCB3aWxsIGJlIGFkZGVkIG1vcmUgYW5kIHdobyB3aWxsIGFkZCwgY2hv
b3NpbmcgYSBuZXcgbmFtZSByZXF1aXJlcyBhIGRpc2N1c3Npb24gYW5kIEkgZG9uJ3QgbWluZCwg
YnV0IGZpcnN0IHdlIG5lZWQgdG8gZGlzY3VzcyBob3cgdG8NCiBtYWtlIHRoZSBkcmFmdCBpbiB0
aGUgYmVzdCBmb3JtIGJlZm9yZSBpdCBpcyBiZWluZyBwdWJsaXNoZWQuDQo8ZGl2IGNsYXNzPSJx
dW90ZSIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0tIE9yaWdp
bmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogS0hBTEVEIFJvdXRpbmcgUHJv
dG9jb2wgKEtSUCkuPGJyPg0KRnJvbTogQXJ0ZW0gUGxlc2NoZW5rbyA8ZGFyd2luLmdnbEBnbWFp
bC5jb20+PGJyPg0KVG86IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+
PGJyPg0KQ0M6IExsb3lkIFdvb2QgPGxsb3lkLndvb2RAeWFob28uY28udWs+LGlldGYgPGlldGZA
aWV0Zi5vcmc+PGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1b3Rl
IGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAj
Y2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdiBkaXI9Imx0ciI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi44cHgiPkEgcGhvbmV0aWMgdHJhbnNjcmlwdGlvbiB3b3VsZCBiZSB2ZXJ5
IHVzZWZ1bDwvc3Bhbj48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48YnI+
DQo8ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gMjggQXByaWwgMjAxNyBhdCAwOTo1NiwgS2hh
bGVkIE9tYXIgPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86ZW5nLmtoYWxlZC5v
bWFyQGhvdG1haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+ZW5nLmtoYWxlZC5vbWFyQGhvdG1haWwu
Y29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9x
dW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlk
O3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdj5TdGVwIGJ5IHN0ZXAsIEtoYWxlZCBSb3V0aW5nIFBy
b3RvY29sLCBLUlAuDQo8ZGl2Pg0KPGRpdiBjbGFzcz0iaDUiPg0KPGRpdiBjbGFzcz0ibV8yNDQ3
NTc4Njg3MTMxNjI2ODA0cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDoxLjUiPjxicj4NCjxicj4N
Ci0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogS0hB
TEVEIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCkuPGJyPg0KRnJvbTogTGxveWQgV29vZCA8dT48L3U+
PGJyPg0KVG86IEtoYWxlZCBPbWFyIDx1PjwvdT4sJnF1b3Q7IDxhIGhyZWY9Im1haWx0bzppZXRm
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT4mcXVvdDsNCjx1Pjwv
dT48YnI+DQpDQzogPGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJpYnV0aW9uIj4NCjxibG9ja3F1
b3RlIGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDRxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAg
MCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRp
diBzdHlsZT0iY29sb3I6IzAwMDtiYWNrZ3JvdW5kLWNvbG9yOiNmZmY7Zm9udC1mYW1pbHk6Q291
cmllciBOZXcsY291cmllcixtb25hY28sbW9ub3NwYWNlLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE2
cHgiPg0KPGRpdiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5
MzM1OTExNTIxNV83MjEwIj48c3Bhbj4mcXVvdDtLUlAmcXVvdDs/PC9zcGFuPjwvZGl2Pg0KPGRp
diBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIx
NV83MjExIj48c3Bhbj48YnI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2IGlkPSJtXzI0NDc1Nzg2ODcx
MzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMTIiPjxzcGFuIGlkPSJt
XzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMjki
PkhvdyBkbyB5b3UgcHJvbm91bmNlIHRoZSBuYW1lPzwvc3Bhbj48L2Rpdj4NCjxkaXY+PC9kaXY+
DQo8ZGl2IGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5
MTE1MjE1XzcyMTMiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2
ODA0c2lnbmF0dXJlIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFf
MTQ5MzM1OTExNTIxNV83MjE0Ij4NCkxsb3lkIFdvb2QgPGEgaHJlZj0iaHR0cDovL2Fib3V0Lm1l
L2xsb3lkd29vZCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9hYm91dC5tZS9sbG95ZHdvb2Q8L2E+
Jm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDRxdGRTZXBhcmF0
ZUJSIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTEx
NTIxNV83MjMwIj4NCjxicj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3
MTMxNjI2ODA0eWFob29fcXVvdGVkIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZf
MF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjM1IiBzdHlsZT0iZGlzcGxheTpibG9jayI+DQo8ZGl2
IHN0eWxlPSJmb250LWZhbWlseTpDb3VyaWVyIE5ldyxjb3VyaWVyLG1vbmFjbyxtb25vc3BhY2Us
c2Fucy1zZXJpZjtmb250LXNpemU6MTZweCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8z
XzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIzNCI+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWls
eTpIZWx2ZXRpY2FOZXVlLEhlbHZldGljYSBOZXVlLEhlbHZldGljYSxBcmlhbCxMdWNpZGEgR3Jh
bmRlLFNhbnMtU2VyaWY7Zm9udC1zaXplOjE2cHgiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5
dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzMiPg0KPGRpdiBkaXI9Imx0ciIgaWQ9
Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzIz
MiI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5
dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyMzEiPg0KPGhyIHNpemU9IjEiPg0KPGI+
PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkZyb206PC9zcGFuPjwvYj4gS2hhbGVkIE9t
YXIgJmx0OzxhIGhyZWY9Im1haWx0bzplbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20iIHRhcmdl
dD0iX2JsYW5rIj5lbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPjxz
cGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Ubzo8L3NwYW4+PC9iPiAmcXVvdDs8YSBocmVm
PSJtYWlsdG86aWV0ZkBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmlldGZAaWV0Zi5vcmc8L2E+
JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsi
PmlldGZAaWV0Zi5vcmc8L2E+Jmd0Ow0KPGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0
OmJvbGQiPlNlbnQ6PC9zcGFuPjwvYj4gV2VkbmVzZGF5LCAyNiBBcHJpbCAyMDE3LCA5OjI3PGJy
Pg0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlN1YmplY3Q6PC9zcGFuPjwvYj4g
S0hBTEVEIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCkuPGJyPg0KPC9mb250PjwvZGl2Pg0KPGRpdiBj
bGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eV9tc2dfY29udGFpbmVyIiBpZD0ibV8yNDQ3NTc4
Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjM2Ij4NCjxicj4N
CjxkaXYgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTQiPg0KPGRpdiBpZD0i
bV8yNDQ3NTc4Njg3MTMxNjI2ODA0eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjM5
Ij4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRXb3JkU2Vj
dGlvbjEiIGlkPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5
MTE1MjE1XzcyMzgiPg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0
NTA5NE1zb05vcm1hbCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8x
XzE0OTMzNTkxMTUyMTVfNzIzNyI+DQpIaSBBbGwsPC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1
Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj4mbmJzcDs8L2Rpdj4NCjxkaXYg
Y2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiIGlkPSJt
XzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1XzcyNDAi
Pg0KSSB0aGluayB5b3UgYWxsIHJlY2VpdmVkIHRoZSBub3RpZmljYXRpb24gcmVnYXJkaW5nIHRo
ZSBLUlAgSUQgc3VibWlzc2lvbiwgc28gaGVyZSBpcyB0aGUgbGluayBmb3IgdGhpcyBJbnRlcm5l
dCBEcmFmdDo8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5
NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMx
NjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHl1
aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0MiI+DQo8YSByZWw9Im5vZm9sbG93IiBo
cmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1vbWFyLWtycC8iIGlk
PSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5dWlfM18xNl8wX3ltMTlfMV8xNDkzMzU5MTE1MjE1Xzcy
NDEiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnLzx3YnI+ZG9j
L2RyYWZ0LW9tYXIta3JwLzwvYT48L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYy
NjgwNHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0ibV8y
NDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCIgaWQ9Im1fMjQ0NzU3ODY4
NzEzMTYyNjgwNHl1aV8zXzE2XzBfeW0xOV8xXzE0OTMzNTkxMTUyMTVfNzI0MyI+DQpGb3IgdGhv
c2Ugd2hvIGFyZSBpbnRlcmVzdGVkIGluIGl0LCB5b3Ugd2lsbCBiZSB3ZWxjb21lZCB0byBkaXNj
dXNzIGl0IGRpcmVjdGx5IHdpdGggbWUuPC9kaXY+DQo8ZGl2IGNsYXNzPSJtXzI0NDc1Nzg2ODcx
MzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIiBpZD0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0
eXVpXzNfMTZfMF95bTE5XzFfMTQ5MzM1OTExNTIxNV83MjQ0Ij4NCiZuYnNwOzwvZGl2Pg0KPGRp
diBjbGFzcz0ibV8yNDQ3NTc4Njg3MTMxNjI2ODA0eWl2OTg3Mzk0NTA5NE1zb05vcm1hbCI+TG9v
a2luZyBmb3IgeW91ciB0aG91Z2h0cywgc3VnZ2VzdGlvbnMsIGNvbW1lbnRzLCBtb2RpZmljYXRp
b25zIG9yIGFueSBraW5kIG9mIHBvc2l0aXZlIHBhcnRpY2lwYXRpb24uPC9kaXY+DQo8ZGl2IGNs
YXNzPSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj4mbmJzcDs8
L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29O
b3JtYWwiPklmIHlvdSBhcmUgbm90IGludGVyZXN0ZWQgaW4gdGhlIGlkZWEgYWZ0ZXIgcmVhZGlu
ZyB0aGUgZHJhZnQsIHBsZWFzZSBpZ25vcmUgdGhpcyBlLW1haWwuPC9kaXY+DQo8ZGl2IGNsYXNz
PSJtXzI0NDc1Nzg2ODcxMzE2MjY4MDR5aXY5ODczOTQ1MDk0TXNvTm9ybWFsIj4mbmJzcDs8L2Rp
dj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgwNHlpdjk4NzM5NDUwOTRNc29Ob3Jt
YWwiPkJlc3QgUmVnYXJkcyw8L2Rpdj4NCjxkaXYgY2xhc3M9Im1fMjQ0NzU3ODY4NzEzMTYyNjgw
NHlpdjk4NzM5NDUwOTRNc29Ob3JtYWwiPiZuYnNwOzwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPGJyPg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8YnI+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5
Pg0KPC9odG1sPg0K

--_000_AM4PR0401MB224196ADFBE0D14995555B06BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 02:03:35 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26975129C48 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 02:03:34 -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 (1024-bit key) header.d=cridland.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 xQHSBq1y-0Mg for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 02:03:32 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::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 E84D5129436 for <ietf@ietf.org>; Fri, 28 Apr 2017 02:00:35 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id l9so30029758wre.1 for <ietf@ietf.org>; Fri, 28 Apr 2017 02:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/NgDG6VYQG0R4JChjTui301jI7ucOlAUzE4UWnVzuEg=; b=R5OcdhQp14ffejJ6Sz3p5PjIakZ/uDaONVH2qaT38kNw4N4/0UaW2bRsT1FhGl7/f4 HaSSrbZshNwoOgUhGT4NQJJ5nnqPJESPgPItAB4Ib4mMwsrIcbwhF58OwEmZs9A2pciM 83gKhP+O7bdJUr2ktdEFhZgK/fmCLd8yTEwCw=
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=/NgDG6VYQG0R4JChjTui301jI7ucOlAUzE4UWnVzuEg=; b=dmnp8hdUmH2SAO6FbWtr0V0k2Id+jL+BkatAwvc4wwJwT3Vy8gd6CPaoxMG15XuHr+ Y/u4kZcLPEUB7/bKfVmx6z38XaFj7+I23KbzNPGiLINusZwzQL1+W7+BrOmY/RVT1I3T isqxR2CtoIBIET4B1Q1Mm7F5+2m7nsRIQC3VdQTYFObZDcyGn+2rNLhpzo+JSeHAXL4y pvsy15llGHuX2OV4vzQs6k3dlXd1qBgZ+5d4GtXBTn9etD5KCjMOLwKLmVvnhKHjHWyz 0JsJP4KazNxv4iUImod32ETbQ+pO49GkXs7AFw3um3/k0I3yXinU5CoOstuGR0Uob1Bm qyxg==
X-Gm-Message-State: AN3rC/5LfzdU5ZfE5Z9FUCuk9lxeXEqgR6QTSGJEPkuvRho9J/6VHg+p QyWvbbTfneepaSSMC8CFjoB9YmWpfYp4vDI=
X-Received: by 10.223.135.216 with SMTP id c24mr6601900wrc.109.1493370034385;  Fri, 28 Apr 2017 02:00:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.135.135 with HTTP; Fri, 28 Apr 2017 02:00:33 -0700 (PDT)
In-Reply-To: <AM4PR0401MB2241F91F390678CE3C0F3193BD1E0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241F91F390678CE3C0F3193BD1E0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Dave Cridland <dave@cridland.net>
Date: Fri, 28 Apr 2017 10:00:33 +0100
Message-ID: <CAKHUCzxK9-McSigoCn-4MvWM-ZPjTzQ+xUj8eB9U1yrA8otGKA@mail.gmail.com>
Subject: Re: KHALED Routing Protocol (KRP).
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sHhXeBMh93dItaTHfAbRGvSDUP8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 09:03:34 -0000

On 26 April 2017 at 00:27, Khaled Omar <eng.khaled.omar@hotmail.com> wrote:
> https://datatracker.ietf.org/doc/draft-omar-krp/

I like this idea, but I think it's sufficiently similar to the
original aim of EGP/BGP that it's already been proven impractical, and
moving to it would also be impractical. I am not a routing expert, so
I'll cheerfully wait being shot down by others, but this is my
rationale:

The reason why we have large routing tables within BGP routers is
mostly that ASNs now consist of many more prefixes than were
originally expected, and so the prefixes do not aggregate well enough.

This proposal involves, essentially, renumbering the entire internet
(which is very difficult in practical terms), such that aggregation
then works more efficiently. However, history has shown that while
this would work for the short term, it would require continuous
renumbering in response to many factors (new addresses, corporate
mergers, etc) in order to maintain its efficiency.

Since we have not solved renumbering very effectively in the first
place, I feel that this is not worth working on.

I would, however, suggest that addressing renumbering would be an
excellent use of your time. A viable solution to renumbering large
public networks would mean that the BGP table would shrink, by the
same logic as above.

That is, if we had a method for renumbering continuously, then it
would improve the efficiency of BGP as well, to almost the same
extent, without incurring the initial internet-wide renumbering
effort.

Finally, I would note that while routing tables are large, the
internet still functions - this may not be the best use of your time
therefore.

Dave.


From nobody Fri Apr 28 05:11:55 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1501205F0 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 wmRG07pjhSxJ for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:11:52 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066050.outbound.protection.outlook.com [40.92.66.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95CFF127342 for <ietf@ietf.org>; Fri, 28 Apr 2017 05:08:58 -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; bh=gjP106Z9nfeFVaT2aj/IXMj8KKW318Qp/Bh55IyTadE=; b=ebleEc/jPDh3xnm7WUk2QSHnLKn5ye6R6FkUdo98guN7R/q/g7rI/WhvldzoQONHGh/sAgJVjbpQatcA+qWsHDfzv4ONRpW+Ap20TOKPF0Nt9yOtkO4k+Z9TaPjSG/ZGzV9+uitIHYXOQVj5j8Bay8WdDu14mABM6d14MGwY2bqVuIUYyykiSvFBv+LtNvrRnvGEPUO6QaDu74wE9XMLf0CCQCQKP2220inwHpDExSbI31OK39CUBoO5utq9882UCd2yaK4/vmZ1mKcL57qESExTyWs8GlcLdMjwxNL0lFCSCHqc5+XM9EaKqRZxU9ik19ulNdYBFGi2qdA8x1mkCg==
Received: from VE1EUR01FT042.eop-EUR01.prod.protection.outlook.com (10.152.2.56) by VE1EUR01HT033.eop-EUR01.prod.protection.outlook.com (10.152.3.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 12:08:56 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.2.58) by VE1EUR01FT042.mail.protection.outlook.com (10.152.3.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 12:08:56 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 12:08:56 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 12:08:56 +0000
Message-ID: <AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAKHUCzxK9-McSigoCn-4MvWM-ZPjTzQ+xUj8eB9U1yrA8otGKA@mail.gmail.com> null
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:A819C04D7D511B140811F92DA2978D662A7634AC8678DD5E381B4FFA7CAF3AE1; UpperCasedChecksum:360AFA9D1E18DCF41B5ABA5786BB50FBC885507AADDE3D221EFC04B272696D94; SizeAsReceived:7832; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT033; 5:0fOpyHJN6t1gb9gl1CG6UW1qjSPgLx4Owqc1hn425wJ0XU809lyp/pvb4fUj6s1KjTFdOuBNiaHa11qZH5yYj7d2XvdaKx8oJVCkF1RX++WFI8SlG/DBIpZ1nCpD7n1xwUY/FIDZ1Kj95UzD7mRGhw==; 24:BrgVRT6BPiVQZ+5deOeGepeDQqCLPQpHwZLtjYsqDMz9ekPig0QewZgAUFJMtO2WwyvS92bp0Bk6PWOEs64n8dfhcNYP7o0Yeb84nRnM7T0=; 7:dZbdw/5JrXyedFSwoZsn/vgdva6okmVOliqEsNNv5fH+118utVJrQ1pwW7IeUwu5zbU8ItD2Cx6Qdga52hb4L4Ziw7z8xjXpHWhPPX7GCfzvhr1whQJB20XPYJW2K5pVr3iQHT9ZtocIJkKhGC1xjCgSBg+ZbZcWxTbxnd+41jkc72K+be0lzrpOQ5hKiOevO59Gb3fXRqTQqaaVmack4hAvtUkD7mL9oc3emo6ymH4yUtp4SwoJZHTCmzYab/He7QPRS72qRBEW83FIgn4L+4C5cg0U92OAl1xW06X9wRnEKBKi3/scut1ZVVFG29c7
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT033; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: dcab916d-7069-4278-6188-08d48e2f57be
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR01HT033; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT033; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT033; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 12:08:56.1021 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT033
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O9koaB7gqkIcOQ-th92u4QlGFQ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 12:11:54 -0000

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

DQoNCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IFJlOiBLSEFM
RUQgUm91dGluZyBQcm90b2NvbCAoS1JQKS4NCkZyb206IEtoYWxlZCBPbWFyDQpUbzogRGF2ZSBD
cmlkbGFuZA0KQ0M6DQoNCg0KRGF2ZSwNCg0KUmVnYXJkaW5nIHRoZSBkaWZmZXJlbmNlIGJldHdl
ZW4gdGFibGVzLCBLUlAgd2l0aGluIGVhY2ggcmVnaW9uIHVzZXMgYSB0YWJsZSBvZiBvbmx5IFJC
UnMgYW5kIFJScywgdGhlIHRhYmxlIGlzIG5vdCBsaXN0aW5nIHByZWZpeGVzIGJlY2F1c2UgS1JQ
IHVzZXMgdGhlIGluZm9ybWF0aW9uIHN0b3JlZCBvbiBldmVyeSBzaW5nbGUgSVAgYWRkcmVzcyBh
bmQgdGhlIElHUCByb3V0aW5nIHRhYmxlLCBhbHNvLCB0aGUgRm9yd2FyZGluZyB0YWJsZSBkZXRh
aWxzIG9mIG9uZSByZWdpb24gaXMgbm90IGFkdmVydGlzZWQgdG8gb3RoZXIgcmVnaW9ucyBiZWNh
dXNlIHRoZXkgZG9uJ3QgbmVlZCB0byBrbm93IGl0LCBlbm91Z2ggdG8ga25vdyBob3cgdG8gcmVh
Y2ggdGhlIFJCUiBhbmQgdGhlbiBpdCBjYW4gZGVsaXZlciB0aGUgcGFja2V0IGZhc3RlciBhbmQg
Y29ycmVjdGx5Lg0KDQpLUlAgd2lsbCBub3QgcmVxdWlyZSByZW51bWJlcmluZyAocmVhbGxvY2F0
aW9uKSBvZiBJUCBhZGRyZXNzZXMgYWZ0ZXIgdGhlIG1vZGlmaWNhdGlvbiBtYWRlIHRvIHRoZSAx
c3QgdmVyc2lvbiBvZiB0aGUgZHJhZnQgdGhhdCB1c2VkIHRoZSAxc3QgdHdvIGdyb3VwcyBvZiBJ
UHY2IGFkZHJlc3NlcyBhcyB0aGUgS1JQIEFTTiwgYnV0IHRoZSAybmQgdmVyc2lvbiB1c2VkIHRo
ZSBtaWRkbGUgdHdvIGdyb3VwcywgYW5kIHRoYXQgd2lsbCBtYWtlIHRoZSB1c2FnZSBvZiBLUlAg
ZWFzaWVyLg0KDQpGaW5hbGx5LCBkb24ndCBzdG9wIG9uIHdoYXQgeW91IHRoaW5rIGlzIG5vdCBh
cHBsaWNhYmxlLCBzaGFyZSB5b3VyIHRob3VnaHRzIHRvIGFkZCBhIHNvbHV0aW9uIHRvIG1ha2Ug
dGhpbmdzIGFwcGxpY2FibGUgdGhhdHMgdGhlIGFpbSBvZiB0aGUgZGlzY3Vzc2lvbiwgYmVjYXVz
ZSBLUlAgY2FuIHJvdXRlIHBhY2tldHMgc3VjY2Vzc2Z1bGx5IGZyb20gdGhlIHNvdXJjZSB0byB0
aGUgZGVzdGluYXRpb24gdXNpbmcgdGhlIEJlc3QgYmVzdCByb3V0ZSBhbmQgd2l0aCB0aGUgbG93
ZXN0IHRhYmxlIGVudHJpZXMgZm9yIGZhc3RlciByb3V0aW5nIGRlY2lzaW9ucy4NCg0KDQotLS0t
LS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiBSZTogS0hBTEVEIFJvdXRp
bmcgUHJvdG9jb2wgKEtSUCkuDQpGcm9tOiBEYXZlIENyaWRsYW5kDQpUbzogS2hhbGVkIE9tYXIN
CkNDOiBpZXRmQGlldGYub3JnDQoNCg0KT24gMjYgQXByaWwgMjAxNyBhdCAwMDoyNywgS2hhbGVk
IE9tYXIgd3JvdGU6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9t
YXIta3JwLw0KDQpJIGxpa2UgdGhpcyBpZGVhLCBidXQgSSB0aGluayBpdCdzIHN1ZmZpY2llbnRs
eSBzaW1pbGFyIHRvIHRoZQ0Kb3JpZ2luYWwgYWltIG9mIEVHUC9CR1AgdGhhdCBpdCdzIGFscmVh
ZHkgYmVlbiBwcm92ZW4gaW1wcmFjdGljYWwsIGFuZA0KbW92aW5nIHRvIGl0IHdvdWxkIGFsc28g
YmUgaW1wcmFjdGljYWwuIEkgYW0gbm90IGEgcm91dGluZyBleHBlcnQsIHNvDQpJJ2xsIGNoZWVy
ZnVsbHkgd2FpdCBiZWluZyBzaG90IGRvd24gYnkgb3RoZXJzLCBidXQgdGhpcyBpcyBteQ0KcmF0
aW9uYWxlOg0KDQpUaGUgcmVhc29uIHdoeSB3ZSBoYXZlIGxhcmdlIHJvdXRpbmcgdGFibGVzIHdp
dGhpbiBCR1Agcm91dGVycyBpcw0KbW9zdGx5IHRoYXQgQVNOcyBub3cgY29uc2lzdCBvZiBtYW55
IG1vcmUgcHJlZml4ZXMgdGhhbiB3ZXJlDQpvcmlnaW5hbGx5IGV4cGVjdGVkLCBhbmQgc28gdGhl
IHByZWZpeGVzIGRvIG5vdCBhZ2dyZWdhdGUgd2VsbCBlbm91Z2guDQoNClRoaXMgcHJvcG9zYWwg
aW52b2x2ZXMsIGVzc2VudGlhbGx5LCByZW51bWJlcmluZyB0aGUgZW50aXJlIGludGVybmV0DQoo
d2hpY2ggaXMgdmVyeSBkaWZmaWN1bHQgaW4gcHJhY3RpY2FsIHRlcm1zKSwgc3VjaCB0aGF0IGFn
Z3JlZ2F0aW9uDQp0aGVuIHdvcmtzIG1vcmUgZWZmaWNpZW50bHkuIEhvd2V2ZXIsIGhpc3Rvcnkg
aGFzIHNob3duIHRoYXQgd2hpbGUNCnRoaXMgd291bGQgd29yayBmb3IgdGhlIHNob3J0IHRlcm0s
IGl0IHdvdWxkIHJlcXVpcmUgY29udGludW91cw0KcmVudW1iZXJpbmcgaW4gcmVzcG9uc2UgdG8g
bWFueSBmYWN0b3JzIChuZXcgYWRkcmVzc2VzLCBjb3Jwb3JhdGUNCm1lcmdlcnMsIGV0YykgaW4g
b3JkZXIgdG8gbWFpbnRhaW4gaXRzIGVmZmljaWVuY3kuDQoNClNpbmNlIHdlIGhhdmUgbm90IHNv
bHZlZCByZW51bWJlcmluZyB2ZXJ5IGVmZmVjdGl2ZWx5IGluIHRoZSBmaXJzdA0KcGxhY2UsIEkg
ZmVlbCB0aGF0IHRoaXMgaXMgbm90IHdvcnRoIHdvcmtpbmcgb24uDQoNCkkgd291bGQsIGhvd2V2
ZXIsIHN1Z2dlc3QgdGhhdCBhZGRyZXNzaW5nIHJlbnVtYmVyaW5nIHdvdWxkIGJlIGFuDQpleGNl
bGxlbnQgdXNlIG9mIHlvdXIgdGltZS4gQSB2aWFibGUgc29sdXRpb24gdG8gcmVudW1iZXJpbmcg
bGFyZ2UNCnB1YmxpYyBuZXR3b3JrcyB3b3VsZCBtZWFuIHRoYXQgdGhlIEJHUCB0YWJsZSB3b3Vs
ZCBzaHJpbmssIGJ5IHRoZQ0Kc2FtZSBsb2dpYyBhcyBhYm92ZS4NCg0KVGhhdCBpcywgaWYgd2Ug
aGFkIGEgbWV0aG9kIGZvciByZW51bWJlcmluZyBjb250aW51b3VzbHksIHRoZW4gaXQNCndvdWxk
IGltcHJvdmUgdGhlIGVmZmljaWVuY3kgb2YgQkdQIGFzIHdlbGwsIHRvIGFsbW9zdCB0aGUgc2Ft
ZQ0KZXh0ZW50LCB3aXRob3V0IGluY3VycmluZyB0aGUgaW5pdGlhbCBpbnRlcm5ldC13aWRlIHJl
bnVtYmVyaW5nDQplZmZvcnQuDQoNCkZpbmFsbHksIEkgd291bGQgbm90ZSB0aGF0IHdoaWxlIHJv
dXRpbmcgdGFibGVzIGFyZSBsYXJnZSwgdGhlDQppbnRlcm5ldCBzdGlsbCBmdW5jdGlvbnMgLSB0
aGlzIG1heSBub3QgYmUgdGhlIGJlc3QgdXNlIG9mIHlvdXIgdGltZQ0KdGhlcmVmb3JlLg0KDQpE
YXZlLg0K

--_000_AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <EF8D9E4078911A40B4F31107D18B63FC@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdiBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJsaW5lLWhlaWdodDogMS41Ij48YnI+DQo8YnI+DQotLS0tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPg0KU3ViamVjdDogUmU6IEtIQUxFRCBSb3V0aW5nIFBy
b3RvY29sIChLUlApLjxicj4NCkZyb206IEtoYWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90
bWFpbC5jb20+PGJyPg0KVG86IERhdmUgQ3JpZGxhbmQgPGRhdmVAY3JpZGxhbmQubmV0Pjxicj4N
CkNDOiA8YnI+DQo8YnI+DQo8YnIgdHlwZT0iYXR0cmlidXRpb24iPg0KPGJsb2NrcXVvdGUgY2xh
c3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mg
c29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpEYXZlLDxicj4NCjxicj4NClJlZ2FyZGluZyB0aGUg
ZGlmZmVyZW5jZSBiZXR3ZWVuIHRhYmxlcywgS1JQIHdpdGhpbiBlYWNoIHJlZ2lvbiB1c2VzIGEg
dGFibGUgb2Ygb25seSBSQlJzIGFuZCBSUnMsIHRoZSB0YWJsZSBpcyBub3QgbGlzdGluZyBwcmVm
aXhlcyBiZWNhdXNlIEtSUCB1c2VzIHRoZSBpbmZvcm1hdGlvbiBzdG9yZWQgb24gZXZlcnkgc2lu
Z2xlIElQIGFkZHJlc3MgYW5kIHRoZSBJR1Agcm91dGluZyB0YWJsZSwgYWxzbywgdGhlIEZvcndh
cmRpbmcgdGFibGUgZGV0YWlscw0KIG9mIG9uZSByZWdpb24gaXMgbm90IGFkdmVydGlzZWQgdG8g
b3RoZXIgcmVnaW9ucyBiZWNhdXNlIHRoZXkgZG9uJ3QgbmVlZCB0byBrbm93IGl0LCBlbm91Z2gg
dG8ga25vdyBob3cgdG8gcmVhY2ggdGhlIFJCUiBhbmQgdGhlbiBpdCBjYW4gZGVsaXZlciB0aGUg
cGFja2V0IGZhc3RlciBhbmQgY29ycmVjdGx5Ljxicj4NCjxicj4NCktSUCB3aWxsIG5vdCByZXF1
aXJlIHJlbnVtYmVyaW5nIChyZWFsbG9jYXRpb24pIG9mIElQIGFkZHJlc3NlcyBhZnRlciB0aGUg
bW9kaWZpY2F0aW9uIG1hZGUgdG8gdGhlIDFzdCB2ZXJzaW9uIG9mIHRoZSBkcmFmdCB0aGF0IHVz
ZWQgdGhlIDFzdCB0d28gZ3JvdXBzIG9mIElQdjYgYWRkcmVzc2VzIGFzIHRoZSBLUlAgQVNOLCBi
dXQgdGhlIDJuZCB2ZXJzaW9uIHVzZWQgdGhlIG1pZGRsZSB0d28gZ3JvdXBzLCBhbmQgdGhhdCB3
aWxsIG1ha2UgdGhlDQogdXNhZ2Ugb2YgS1JQIGVhc2llci48YnI+DQo8YnI+DQpGaW5hbGx5LCBk
b24ndCBzdG9wIG9uIHdoYXQgeW91IHRoaW5rIGlzIG5vdCBhcHBsaWNhYmxlLCBzaGFyZSB5b3Vy
IHRob3VnaHRzIHRvIGFkZCBhIHNvbHV0aW9uIHRvIG1ha2UgdGhpbmdzIGFwcGxpY2FibGUgdGhh
dHMgdGhlIGFpbSBvZiB0aGUgZGlzY3Vzc2lvbiwgYmVjYXVzZSBLUlAgY2FuIHJvdXRlIHBhY2tl
dHMgc3VjY2Vzc2Z1bGx5IGZyb20gdGhlIHNvdXJjZSB0byB0aGUgZGVzdGluYXRpb24gdXNpbmcg
dGhlIEJlc3QgYmVzdCByb3V0ZQ0KIGFuZCB3aXRoIHRoZSBsb3dlc3QgdGFibGUgZW50cmllcyBm
b3IgZmFzdGVyIHJvdXRpbmcgZGVjaXNpb25zLjxicj4NCjxkaXYgY2xhc3M9InF1b3RlIiBzdHls
ZT0ibGluZS1oZWlnaHQ6IDEuNSI+PGJyPg0KPGJyPg0KLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2Fn
ZSAtLS0tLS0tLTxicj4NClN1YmplY3Q6IFJlOiBLSEFMRUQgUm91dGluZyBQcm90b2NvbCAoS1JQ
KS48YnI+DQpGcm9tOiBEYXZlIENyaWRsYW5kIDxkYXZlQGNyaWRsYW5kLm5ldD48YnI+DQpUbzog
S2hhbGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48YnI+DQpDQzogaWV0ZkBp
ZXRmLm9yZzxicj4NCjxicj4NCjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+DQo8YmxvY2txdW90ZSBj
bGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2Nj
YyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCk9uIDI2IEFwcmlsIDIwMTcgYXQgMDA6MjcsIEto
YWxlZCBPbWFyIDxlbmcua2hhbGVkLm9tYXJAaG90bWFpbC5jb20+d3JvdGU6PGJyPg0KJmd0OyBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1vbWFyLWtycC88YnI+DQo8YnI+
DQpJIGxpa2UgdGhpcyBpZGVhLCBidXQgSSB0aGluayBpdCdzIHN1ZmZpY2llbnRseSBzaW1pbGFy
IHRvIHRoZTxicj4NCm9yaWdpbmFsIGFpbSBvZiBFR1AvQkdQIHRoYXQgaXQncyBhbHJlYWR5IGJl
ZW4gcHJvdmVuIGltcHJhY3RpY2FsLCBhbmQ8YnI+DQptb3ZpbmcgdG8gaXQgd291bGQgYWxzbyBi
ZSBpbXByYWN0aWNhbC4gSSBhbSBub3QgYSByb3V0aW5nIGV4cGVydCwgc288YnI+DQpJJ2xsIGNo
ZWVyZnVsbHkgd2FpdCBiZWluZyBzaG90IGRvd24gYnkgb3RoZXJzLCBidXQgdGhpcyBpcyBteTxi
cj4NCnJhdGlvbmFsZTo8YnI+DQo8YnI+DQpUaGUgcmVhc29uIHdoeSB3ZSBoYXZlIGxhcmdlIHJv
dXRpbmcgdGFibGVzIHdpdGhpbiBCR1Agcm91dGVycyBpczxicj4NCm1vc3RseSB0aGF0IEFTTnMg
bm93IGNvbnNpc3Qgb2YgbWFueSBtb3JlIHByZWZpeGVzIHRoYW4gd2VyZTxicj4NCm9yaWdpbmFs
bHkgZXhwZWN0ZWQsIGFuZCBzbyB0aGUgcHJlZml4ZXMgZG8gbm90IGFnZ3JlZ2F0ZSB3ZWxsIGVu
b3VnaC48YnI+DQo8YnI+DQpUaGlzIHByb3Bvc2FsIGludm9sdmVzLCBlc3NlbnRpYWxseSwgcmVu
dW1iZXJpbmcgdGhlIGVudGlyZSBpbnRlcm5ldDxicj4NCih3aGljaCBpcyB2ZXJ5IGRpZmZpY3Vs
dCBpbiBwcmFjdGljYWwgdGVybXMpLCBzdWNoIHRoYXQgYWdncmVnYXRpb248YnI+DQp0aGVuIHdv
cmtzIG1vcmUgZWZmaWNpZW50bHkuIEhvd2V2ZXIsIGhpc3RvcnkgaGFzIHNob3duIHRoYXQgd2hp
bGU8YnI+DQp0aGlzIHdvdWxkIHdvcmsgZm9yIHRoZSBzaG9ydCB0ZXJtLCBpdCB3b3VsZCByZXF1
aXJlIGNvbnRpbnVvdXM8YnI+DQpyZW51bWJlcmluZyBpbiByZXNwb25zZSB0byBtYW55IGZhY3Rv
cnMgKG5ldyBhZGRyZXNzZXMsIGNvcnBvcmF0ZTxicj4NCm1lcmdlcnMsIGV0YykgaW4gb3JkZXIg
dG8gbWFpbnRhaW4gaXRzIGVmZmljaWVuY3kuPGJyPg0KPGJyPg0KU2luY2Ugd2UgaGF2ZSBub3Qg
c29sdmVkIHJlbnVtYmVyaW5nIHZlcnkgZWZmZWN0aXZlbHkgaW4gdGhlIGZpcnN0PGJyPg0KcGxh
Y2UsIEkgZmVlbCB0aGF0IHRoaXMgaXMgbm90IHdvcnRoIHdvcmtpbmcgb24uPGJyPg0KPGJyPg0K
SSB3b3VsZCwgaG93ZXZlciwgc3VnZ2VzdCB0aGF0IGFkZHJlc3NpbmcgcmVudW1iZXJpbmcgd291
bGQgYmUgYW48YnI+DQpleGNlbGxlbnQgdXNlIG9mIHlvdXIgdGltZS4gQSB2aWFibGUgc29sdXRp
b24gdG8gcmVudW1iZXJpbmcgbGFyZ2U8YnI+DQpwdWJsaWMgbmV0d29ya3Mgd291bGQgbWVhbiB0
aGF0IHRoZSBCR1AgdGFibGUgd291bGQgc2hyaW5rLCBieSB0aGU8YnI+DQpzYW1lIGxvZ2ljIGFz
IGFib3ZlLjxicj4NCjxicj4NClRoYXQgaXMsIGlmIHdlIGhhZCBhIG1ldGhvZCBmb3IgcmVudW1i
ZXJpbmcgY29udGludW91c2x5LCB0aGVuIGl0PGJyPg0Kd291bGQgaW1wcm92ZSB0aGUgZWZmaWNp
ZW5jeSBvZiBCR1AgYXMgd2VsbCwgdG8gYWxtb3N0IHRoZSBzYW1lPGJyPg0KZXh0ZW50LCB3aXRo
b3V0IGluY3VycmluZyB0aGUgaW5pdGlhbCBpbnRlcm5ldC13aWRlIHJlbnVtYmVyaW5nPGJyPg0K
ZWZmb3J0Ljxicj4NCjxicj4NCkZpbmFsbHksIEkgd291bGQgbm90ZSB0aGF0IHdoaWxlIHJvdXRp
bmcgdGFibGVzIGFyZSBsYXJnZSwgdGhlPGJyPg0KaW50ZXJuZXQgc3RpbGwgZnVuY3Rpb25zIC0g
dGhpcyBtYXkgbm90IGJlIHRoZSBiZXN0IHVzZSBvZiB5b3VyIHRpbWU8YnI+DQp0aGVyZWZvcmUu
PGJyPg0KPGJyPg0KRGF2ZS48YnI+DQo8L2VuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48L2Js
b2NrcXVvdGU+DQo8L2VuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT48L2RhdmVAY3JpZGxhbmQu
bmV0PjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kYXZlQGNyaWRsYW5kLm5ldD48L2VuZy5raGFs
ZWQub21hckBob3RtYWlsLmNvbT48L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 05:45:46 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6C9812951C for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.898
X-Spam-Level: 
X-Spam-Status: No, score=-4.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.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 9Nrar8CvnYwc for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:45:41 -0700 (PDT)
Received: from atl4mhob17.registeredsite.com (atl4mhob17.myregisteredsite.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 A67A2129AD1 for <ietf@ietf.org>; Fri, 28 Apr 2017 05:42:19 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob17.registeredsite.com (8.14.4/8.14.4) with ESMTP id v3SCgF9T048618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Fri, 28 Apr 2017 08:42:15 -0400
Received: (qmail 21745 invoked by uid 0); 28 Apr 2017 12:42:15 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 28 Apr 2017 12:42:15 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Fri, 28 Apr 2017 08:42:09 -0400
Subject: Re: KHALED Routing Protocol (KRP).
From: Lee Howard <lee@asgard.org>
To: Khaled Omar <eng.khaled.omar@hotmail.com>, ietf <ietf@ietf.org>
Message-ID: <D528AF97.7A8F6%lee@asgard.org>
Thread-Topic: KHALED Routing Protocol (KRP).
References: <CAKHUCzxK9-McSigoCn-4MvWM-ZPjTzQ+xUj8eB9U1yrA8otGKA@mail.gmail.com> <AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3576213734_3096738"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m7ONsv5taaL_K45qwx4Ki6v7ims>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 12:45:44 -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_3576213734_3096738
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable



From:  ietf <ietf-bounces@ietf.org> on behalf of Khaled Omar
<eng.khaled.omar@hotmail.com>
Date:  Friday, April 28, 2017 at 8:08 AM
To:  ietf <ietf@ietf.org>
Subject:  Fw: KHALED Routing Protocol (KRP).
>=20
> Regarding the difference between tables, KRP within each region uses a ta=
ble
> of only RBRs and RRs, the table is not listing prefixes because KRP uses =
the
> information stored on every single IP address and the IGP routing table, =
also,
> the Forwarding table details of one region is not advertised to other reg=
ions
> because they don't need to know it, enough to know how to reach the RBR a=
nd
> then it can deliver the packet faster and correctly.

Sorry, you=B9re carrying full routes for every /32 and every /128 in your IGP=
?

>=20
>=20
> KRP will not require renumbering (reallocation) of IP addresses after the
> modification made to the 1st version of the draft that used the 1st two g=
roups
> of IPv6 addresses as the KRP ASN, but the 2nd version used the middle two
> groups, and that will make the usage of KRP easier.

What about IPv4?

>=20
>=20
> Finally, don't stop on what you think is not applicable, share your thoug=
hts
> to add a solution to make things applicable thats the aim of the discussi=
on,
> because KRP can route packets successfully from the source to the destina=
tion
> using the Best best route and with the lowest table entries for faster ro=
uting
> decisions.

Define =B3Best best.=B2
Shortest AS hops? Fewest intermediate devices? Cheapest link? Least
saturated link? Hot potato? Lowest packet one-way latency?

I agree with Dave; the 6renum WG published rfc7010 IPv6 Site Renumbering Ga=
p
Analysis and then shut down; filling those gaps would be useful.

Lee

>=20
>=20
>=20
> -------- Original Message --------
> Subject: Re: KHALED Routing Protocol (KRP).
> From: Dave Cridland
> To: Khaled Omar=20
> CC: ietf@ietf.org
>=20
>=20
>> On 26 April 2017 at 00:27, Khaled Omar wrote:
>>> > https://datatracker.ietf.org/doc/draft-omar-krp/
>>=20
>> I like this idea, but I think it's sufficiently similar to the
>> original aim of EGP/BGP that it's already been proven impractical, and
>> moving to it would also be impractical. I am not a routing expert, so
>> I'll cheerfully wait being shot down by others, but this is my
>> rationale:
>>=20
>> The reason why we have large routing tables within BGP routers is
>> mostly that ASNs now consist of many more prefixes than were
>> originally expected, and so the prefixes do not aggregate well enough.
>>=20
>> This proposal involves, essentially, renumbering the entire internet
>> (which is very difficult in practical terms), such that aggregation
>> then works more efficiently. However, history has shown that while
>> this would work for the short term, it would require continuous
>> renumbering in response to many factors (new addresses, corporate
>> mergers, etc) in order to maintain its efficiency.
>>=20
>> Since we have not solved renumbering very effectively in the first
>> place, I feel that this is not worth working on.
>>=20
>> I would, however, suggest that addressing renumbering would be an
>> excellent use of your time. A viable solution to renumbering large
>> public networks would mean that the BGP table would shrink, by the
>> same logic as above.
>>=20
>> That is, if we had a method for renumbering continuously, then it
>> would improve the efficiency of BGP as well, to almost the same
>> extent, without incurring the initial internet-wide renumbering
>> effort.
>>=20
>> Finally, I would note that while routing tables are large, the
>> internet still functions - this may not be the best use of your time
>> therefore.
>>=20
>> Dave.



--B_3576213734_3096738
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<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; -we=
bkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; fo=
nt-family: Calibri, sans-serif;"><div><br></div><div><br></div><span id=3D"OLK=
_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:11pt; text-ali=
gn:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c=
4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"fon=
t-weight:bold">From: </span> ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org"=
>ietf-bounces@ietf.org</a>&gt; on behalf of Khaled Omar &lt;<a href=3D"mailto:=
eng.khaled.omar@hotmail.com">eng.khaled.omar@hotmail.com</a>&gt;<br><span st=
yle=3D"font-weight:bold">Date: </span> Friday, April 28, 2017 at 8:08 AM<br><s=
pan style=3D"font-weight:bold">To: </span> ietf &lt;<a href=3D"mailto:ietf@ietf.=
org">ietf@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span=
> Fw: KHALED Routing Protocol (KRP).<br></div><blockquote id=3D"MAC_OUTLOOK_AT=
TRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; =
MARGIN:0 0 0 5;"><div><div><div class=3D"quote" style=3D"line-height: 1.5"><eng.=
khaled.omar@hotmail.com><dave@cridland.net><div><br></div><div>
Regarding the difference between tables, KRP within each region uses a tabl=
e of only RBRs and RRs, the table is not listing prefixes because KRP uses t=
he information stored on every single IP address and the IGP routing table, =
also, the Forwarding table details
 of one region is not advertised to other regions because they don't need t=
o know it, enough to know how to reach the RBR and then it can deliver the p=
acket faster and correctly.</div></dave@cridland.net></eng.khaled.omar@hotma=
il.com></div></div></div></blockquote></span><div><br></div><div>Sorry, you&=
#8217;re carrying full routes for every /32 and every /128 in your IGP?</div=
><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><blockquote id=3D"MAC_OUTLOOK_=
ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5=
; MARGIN:0 0 0 5;"><div><div><div class=3D"quote" style=3D"line-height: 1.5"><en=
g.khaled.omar@hotmail.com><dave@cridland.net><div><br></div><div><br></div><=
div>
KRP will not require renumbering (reallocation) of IP addresses after the m=
odification made to the 1st version of the draft that used the 1st two group=
s of IPv6 addresses as the KRP ASN, but the 2nd version used the middle two =
groups, and that will make the
 usage of KRP easier.</div></dave@cridland.net></eng.khaled.omar@hotmail.co=
m></div></div></div></blockquote></span><div><br></div><div>What about IPv4?=
</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><blockquote id=3D"MAC_OUT=
LOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 =
0 0 5; MARGIN:0 0 0 5;"><div><div><div class=3D"quote" style=3D"line-height: 1.5=
"><eng.khaled.omar@hotmail.com><dave@cridland.net><div><br></div><div><br></=
div><div>
Finally, don't stop on what you think is not applicable, share your thought=
s to add a solution to make things applicable thats the aim of the discussio=
n, because KRP can route packets successfully from the source to the destina=
tion using the Best best route
 and with the lowest table entries for faster routing decisions.</div></dav=
e@cridland.net></eng.khaled.omar@hotmail.com></div></div></div></blockquote>=
</span><div><br></div><div>Define &#8220;Best best.&#8221;</div><div>Shortes=
t AS hops? Fewest intermediate devices? Cheapest link? Least saturated link?=
 Hot potato? Lowest packet one-way latency?</div><div><br></div><div>I agree=
 with Dave; the 6renum WG published rfc7010 IPv6 Site Renumbering Gap Analys=
is and then shut down; filling those gaps would be useful.</div><div><br></d=
iv><div>Lee</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><blockquote =
id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid;=
 PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div class=3D"quote" style=3D"line-=
height: 1.5"><eng.khaled.omar@hotmail.com><dave@cridland.net><div><br></div>=
<div class=3D"quote" style=3D"line-height: 1.5"><br><br>
-------- Original Message --------<br>
Subject: Re: KHALED Routing Protocol (KRP).<br>
From: Dave Cridland <dave@cridland.net><br>
To: Khaled Omar <eng.khaled.omar@hotmail.com><br>
CC: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br><br><br type=3D"attri=
bution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
On 26 April 2017 at 00:27, Khaled Omar <eng.khaled.omar@hotmail.com>wrote:<=
br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-omar-krp/">https://dat=
atracker.ietf.org/doc/draft-omar-krp/</a><br><br>
I like this idea, but I think it's sufficiently similar to the<br>
original aim of EGP/BGP that it's already been proven impractical, and<br>
moving to it would also be impractical. I am not a routing expert, so<br>
I'll cheerfully wait being shot down by others, but this is my<br>
rationale:<br><br>
The reason why we have large routing tables within BGP routers is<br>
mostly that ASNs now consist of many more prefixes than were<br>
originally expected, and so the prefixes do not aggregate well enough.<br><=
br>
This proposal involves, essentially, renumbering the entire internet<br>
(which is very difficult in practical terms), such that aggregation<br>
then works more efficiently. However, history has shown that while<br>
this would work for the short term, it would require continuous<br>
renumbering in response to many factors (new addresses, corporate<br>
mergers, etc) in order to maintain its efficiency.<br><br>
Since we have not solved renumbering very effectively in the first<br>
place, I feel that this is not worth working on.<br><br>
I would, however, suggest that addressing renumbering would be an<br>
excellent use of your time. A viable solution to renumbering large<br>
public networks would mean that the BGP table would shrink, by the<br>
same logic as above.<br><br>
That is, if we had a method for renumbering continuously, then it<br>
would improve the efficiency of BGP as well, to almost the same<br>
extent, without incurring the initial internet-wide renumbering<br>
effort.<br><br>
Finally, I would note that while routing tables are large, the<br>
internet still functions - this may not be the best use of your time<br>
therefore.<br><br>
Dave.<br></eng.khaled.omar@hotmail.com></blockquote></eng.khaled.omar@hotma=
il.com></dave@cridland.net></div></dave@cridland.net></eng.khaled.omar@hotma=
il.com></div></div></div></blockquote></span></body></html>

--B_3576213734_3096738--



From nobody Fri Apr 28 06:16:10 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E301292FC for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 06:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 CUaf61Okg-Uk for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 06:16:06 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069052.outbound.protection.outlook.com [40.92.69.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF6FF129C21 for <ietf@ietf.org>; Fri, 28 Apr 2017 06:12:15 -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; bh=xg5G2dRaSSkGABgv7reNZKzaRr+jSBjjiCnO9Z2GvIw=; b=r91jSb+FS5+vR32QoRwCUr3Lz5uHnxdvSZh95c0OF581SSReiccqlZcAAm/tgre+DeRUslhTK7VbUW1tNGb4RFWzfwY49utUmUUH6y5OlCVvUCIGGgaN5P5IGghrimMId2WZv4CoZ4ubjO7VhzLbWVjXMQdFJOY6Wso4yQMDuxFupJNUJNsSWKZ8bQ95s109h+eg5Q178C2HL2dSLthbeb57mf42XkjTIhnB91ii+Wdcfq4tAyq4Y63Ig1S1LxbzmGyoa8/BseQdYaGKd5skEzt5HOLl7jUwXpaUW/bCSe4k36QaO+Y45oNJojfBECaxaJiaswZDXJN6MWoK1H6m8w==
Received: from HE1EUR02FT055.eop-EUR02.prod.protection.outlook.com (10.152.10.53) by HE1EUR02HT034.eop-EUR02.prod.protection.outlook.com (10.152.11.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 13:12:13 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.10.55) by HE1EUR02FT055.mail.protection.outlook.com (10.152.11.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 13:12:13 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 13:12:13 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Lee Howard <lee@asgard.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQCAWvGAAAB/igA=
Date: Fri, 28 Apr 2017 13:12:12 +0000
Message-ID: <AM4PR0401MB2241174F682EE6776E9E27E6BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAKHUCzxK9-McSigoCn-4MvWM-ZPjTzQ+xUj8eB9U1yrA8otGKA@mail.gmail.com> <AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com> <D528AF97.7A8F6%lee@asgard.org>
In-Reply-To: <D528AF97.7A8F6%lee@asgard.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: asgard.org; dkim=none (message not signed) header.d=none;asgard.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:C853A4D6E4A8A287103640BA1CA94554D9EDF42E811CD9B1DDA5C2DB619C08EF; UpperCasedChecksum:DAF9F236987594609ED4FAF7651184BB9E4AA37CEB450B3CC05BC4A47873CDD7; SizeAsReceived:8181; Count:42
x-tmn: [hKjgk9CLtH68s+fj2sbGpU+v0LUUVSaS]
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT034; 5:n7qiWANpIz7eFY5ry03/t0tca0fUgHS4InF2JCNl1hBpHDtxlTrBgAqJ/d2OpBfYhRQmEk8akKhBKTZrGCqsBMovUQdFhAs6dMeZEPpFrKMqbGmDnFiN6czdm3ysZreTiXccWOwpEidxa1ZYnzsjLg==; 24:h596KhsUM5Y5jBekHq/T8LFjAeSIZK5OxAf9ZmcrRK3UfyRdZ+3eVuHq1zP5m325nQDKvWNuZ13V9701Qzyj+zP/wKvyJ0QEG9WYmbfWZk4=; 7:Z6kAux2f3h5taiBCv+mRdCB6FHe43hVwj5kWWpN6IYLggxt7KI+mJ6t67LqZV80dgBjFmddBa06CC4zdHbYADnPNmqyFIc16bZpOG14hDzooLQ9PYbgoSqRK/qI5W0zU/5bKD9sC8SEZM4do6IvY8KlQTw6MhbR5EYEyY9aU8RMoazP51UhzOdhnaNFQrxgaAxs4L5zeOfgyZ9EH/jpn4Wh2VQaWlDmjuKNHyvxvRnb9DMT2mdEuRNmOLWvPiaH++IZrpAqPMmgkeea2Yvql3vs2k2LKtkkvcNPk46P70CTDgSLb3Ezc50j6MCnGIdIl
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT034; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: a2d86f5b-a072-483e-08d4-08d48e382f7c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:HE1EUR02HT034; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR02HT034; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT034; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241174F682EE6776E9E27E6BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 13:12:13.1292 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT034
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RZxLSKEqrJuhSu866_K9C6g1Fq0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:16:08 -0000

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



KRP router Forwarding Table (FT):


Local KRP ASN

Remote KRP ASN

RBR KRP ASN

Best AS Path

Output Interface

Next-hop IP address



This is the used KRP Forwarding Table, it lists KRP ASNs and the Best AS pa=
th from the local KRP ASN and every single destination KRP ASN.

When the packet travels between KRP ASNs, it uses the already existing IGP =
Routing Table that lists full local prefixes/subnets within this local KRP =
ASN until reaching the RR or the RBR.

Regarding IPv4, the 1st two octets are used as KRP ASN for ISPs but still a=
n issue for enterprises because the KRP ASN must be unique and this is unde=
r development.

The Best best route means respectively:


1)      The shortest AS path.

2)      The lowest IGP metric route.

From: Lee Howard [mailto:lee@asgard.org]
Sent: Friday, April 28, 2017 2:42 PM
To: Khaled Omar; ietf
Subject: Re: KHALED Routing Protocol (KRP).



From: ietf <ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org>> on behalf =
of Khaled Omar <eng.khaled.omar@hotmail.com<mailto:eng.khaled.omar@hotmail.=
com>>
Date: Friday, April 28, 2017 at 8:08 AM
To: ietf <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Fw: KHALED Routing Protocol (KRP).

Regarding the difference between tables, KRP within each region uses a tabl=
e of only RBRs and RRs, the table is not listing prefixes because KRP uses =
the information stored on every single IP address and the IGP routing table=
, also, the Forwarding table details of one region is not advertised to oth=
er regions because they don't need to know it, enough to know how to reach =
the RBR and then it can deliver the packet faster and correctly.

Sorry, you're carrying full routes for every /32 and every /128 in your IGP=
?



KRP will not require renumbering (reallocation) of IP addresses after the m=
odification made to the 1st version of the draft that used the 1st two grou=
ps of IPv6 addresses as the KRP ASN, but the 2nd version used the middle tw=
o groups, and that will make the usage of KRP easier.

What about IPv4?



Finally, don't stop on what you think is not applicable, share your thought=
s to add a solution to make things applicable thats the aim of the discussi=
on, because KRP can route packets successfully from the source to the desti=
nation using the Best best route and with the lowest table entries for fast=
er routing decisions.

Define "Best best."
Shortest AS hops? Fewest intermediate devices? Cheapest link? Least saturat=
ed link? Hot potato? Lowest packet one-way latency?

I agree with Dave; the 6renum WG published rfc7010 IPv6 Site Renumbering Ga=
p Analysis and then shut down; filling those gaps would be useful.

Lee




-------- Original Message --------
Subject: Re: KHALED Routing Protocol (KRP).
From: Dave Cridland
To: Khaled Omar
CC: ietf@ietf.org<mailto:ietf@ietf.org>


On 26 April 2017 at 00:27, Khaled Omar wrote:
> https://datatracker.ietf.org/doc/draft-omar-krp/

I like this idea, but I think it's sufficiently similar to the
original aim of EGP/BGP that it's already been proven impractical, and
moving to it would also be impractical. I am not a routing expert, so
I'll cheerfully wait being shot down by others, but this is my
rationale:

The reason why we have large routing tables within BGP routers is
mostly that ASNs now consist of many more prefixes than were
originally expected, and so the prefixes do not aggregate well enough.

This proposal involves, essentially, renumbering the entire internet
(which is very difficult in practical terms), such that aggregation
then works more efficiently. However, history has shown that while
this would work for the short term, it would require continuous
renumbering in response to many factors (new addresses, corporate
mergers, etc) in order to maintain its efficiency.

Since we have not solved renumbering very effectively in the first
place, I feel that this is not worth working on.

I would, however, suggest that addressing renumbering would be an
excellent use of your time. A viable solution to renumbering large
public networks would mean that the BGP table would shrink, by the
same logic as above.

That is, if we had a method for renumbering continuously, then it
would improve the efficiency of BGP as well, to almost the same
extent, without incurring the initial internet-wide renumbering
effort.

Finally, I would note that while routing tables are large, the
internet still functions - this may not be the best use of your time
therefore.

Dave.


--_000_AM4PR0401MB2241174F682EE6776E9E27E6BD130AM4PR0401MB2241_
Content-Type: text/html; charset="us-ascii"
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" 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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1698462736;
	mso-list-type:hybrid;
	mso-list-template-ids:801518110 67698705 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#757575;background:white"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#757575;background:white"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#757575;background:white">KRP router=
 Forwarding Table (FT):</span><span style=3D"font-size:11.5pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#757575"><br>
<br>
<br>
</span><o:p></o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0" width=3D"593" style=3D"width:444.75pt;background:white;border-collap=
se:collapse">
<tbody>
<tr style=3D"height:36.4pt">
<td width=3D"87" style=3D"width:65.0pt;border:double windowtext 1.5pt;backg=
round:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">Local KRP ASN</span></b><span st=
yle=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:#757575"><o:p></o:p></span></p>
</td>
<td width=3D"101" style=3D"width:75.45pt;border:double windowtext 1.5pt;bor=
der-left:none;background:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt"=
>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">Remote KRP ASN</span></b><span s=
tyle=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:#757575"><o:p></o:p></span></p>
</td>
<td width=3D"81" style=3D"width:60.4pt;border:double windowtext 1.5pt;borde=
r-left:none;background:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">RBR KRP ASN</span></b><span styl=
e=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;=
color:#757575"><o:p></o:p></span></p>
</td>
<td width=3D"79" style=3D"width:59.2pt;border:double windowtext 1.5pt;borde=
r-left:none;background:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">Best AS Path</span></b><span sty=
le=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;=
;color:#757575"><o:p></o:p></span></p>
</td>
<td width=3D"118" style=3D"width:88.55pt;border:double windowtext 1.5pt;bor=
der-left:none;background:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt"=
>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">Output Interface</span></b><span=
 style=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&q=
uot;;color:#757575"><o:p></o:p></span></p>
</td>
<td width=3D"128" style=3D"width:96.15pt;border:double windowtext 1.5pt;bor=
der-left:none;background:#D0CECE;padding:0in 5.4pt 0in 5.4pt;height:36.4pt"=
>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"font-size:18.0pt;color:#757575">Next-hop IP address</span></b><s=
pan style=3D"font-size:11.5pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:#757575"><o:p></o:p></span></p>
</td>
</tr>
<tr style=3D"height:26.5pt">
<td width=3D"87" style=3D"width:65.0pt;border:double windowtext 1.5pt;borde=
r-top:none;padding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
<td width=3D"101" style=3D"width:75.45pt;border-top:none;border-left:none;b=
order-bottom:double windowtext 1.5pt;border-right:double windowtext 1.5pt;p=
adding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
<td width=3D"81" style=3D"width:60.4pt;border-top:none;border-left:none;bor=
der-bottom:double windowtext 1.5pt;border-right:double windowtext 1.5pt;pad=
ding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
<td width=3D"79" style=3D"width:59.2pt;border-top:none;border-left:none;bor=
der-bottom:double windowtext 1.5pt;border-right:double windowtext 1.5pt;pad=
ding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
<td width=3D"118" style=3D"width:88.55pt;border-top:none;border-left:none;b=
order-bottom:double windowtext 1.5pt;border-right:double windowtext 1.5pt;p=
adding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
<td width=3D"128" style=3D"width:96.15pt;border-top:none;border-left:none;b=
order-bottom:double windowtext 1.5pt;border-right:double windowtext 1.5pt;p=
adding:0in 5.4pt 0in 5.4pt;height:26.5pt">
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This is the used KRP Forw=
arding Table, it lists KRP ASNs and the Best AS path from the local KRP ASN=
 and every single destination KRP ASN.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">When the packet travels b=
etween KRP ASNs, it uses the already existing IGP Routing Table that lists =
full local prefixes/subnets within this local KRP ASN until
 reaching the RR or the RBR.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regarding IPv4, the 1<sup=
>st</sup> two octets are used as KRP ASN for ISPs but still an issue for en=
terprises because the KRP ASN must be unique and this is
 under development.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The Best best route means=
 respectively:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D">The shortest AS path.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D">The lowest IGP metric route.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> Lee Ho=
ward [mailto:lee@asgard.org]
<br>
<b>Sent:</b> Friday, April 28, 2017 2:42 PM<br>
<b>To:</b> Khaled Omar; ietf<br>
<b>Subject:</b> Re: KHALED Routing Protocol (KRP).<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black">ietf &lt;<a href=3D"mailto:ietf-bounces=
@ietf.org">ietf-bounces@ietf.org</a>&gt; on behalf of Khaled Omar &lt;<a hr=
ef=3D"mailto:eng.khaled.omar@hotmail.com">eng.khaled.omar@hotmail.com</a>&g=
t;<br>
<b>Date: </b>Friday, April 28, 2017 at 8:08 AM<br>
<b>To: </b>ietf &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<=
br>
<b>Subject: </b>Fw: KHALED Routing Protocol (KRP).<o:p></o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Regarding the difference be=
tween tables, KRP within each region uses a table of only RBRs and RRs, the=
 table is not listing prefixes because KRP uses the information
 stored on every single IP address and the IGP routing table, also, the For=
warding table details of one region is not advertised to other regions beca=
use they don't need to know it, enough to know how to reach the RBR and the=
n it can deliver the packet faster
 and correctly.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Sorry, you&#8217;re carryin=
g full routes for every /32 and every /128 in your IGP?<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">KRP will not require renumb=
ering (reallocation) of IP addresses after the modification made to the 1st=
 version of the draft that used the 1st two groups of IPv6
 addresses as the KRP ASN, but the 2nd version used the middle two groups, =
and that will make the usage of KRP easier.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">What about IPv4?<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Finally, don't stop on what=
 you think is not applicable, share your thoughts to add a solution to make=
 things applicable thats the aim of the discussion, because
 KRP can route packets successfully from the source to the destination usin=
g the Best best route and with the lowest table entries for faster routing =
decisions.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Define &#8220;Best best.&#8=
221;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Shortest AS hops? Fewest in=
termediate devices? Cheapest link? Least saturated link? Hot potato? Lowest=
 packet one-way latency?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I agree with Dave; the 6ren=
um WG published rfc7010 IPv6 Site Renumbering Gap Analysis and then shut do=
wn; filling those gaps would be useful.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Lee<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
-------- Original Message --------<br>
Subject: Re: KHALED Routing Protocol (KRP).<br>
From: Dave Cridland <br>
To: Khaled Omar <br>
CC: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">On 26 April 2017 at 00:27, =
Khaled Omar wrote:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-omar-krp/">https://d=
atatracker.ietf.org/doc/draft-omar-krp/</a><br>
<br>
I like this idea, but I think it's sufficiently similar to the<br>
original aim of EGP/BGP that it's already been proven impractical, and<br>
moving to it would also be impractical. I am not a routing expert, so<br>
I'll cheerfully wait being shot down by others, but this is my<br>
rationale:<br>
<br>
The reason why we have large routing tables within BGP routers is<br>
mostly that ASNs now consist of many more prefixes than were<br>
originally expected, and so the prefixes do not aggregate well enough.<br>
<br>
This proposal involves, essentially, renumbering the entire internet<br>
(which is very difficult in practical terms), such that aggregation<br>
then works more efficiently. However, history has shown that while<br>
this would work for the short term, it would require continuous<br>
renumbering in response to many factors (new addresses, corporate<br>
mergers, etc) in order to maintain its efficiency.<br>
<br>
Since we have not solved renumbering very effectively in the first<br>
place, I feel that this is not worth working on.<br>
<br>
I would, however, suggest that addressing renumbering would be an<br>
excellent use of your time. A viable solution to renumbering large<br>
public networks would mean that the BGP table would shrink, by the<br>
same logic as above.<br>
<br>
That is, if we had a method for renumbering continuously, then it<br>
would improve the efficiency of BGP as well, to almost the same<br>
extent, without incurring the initial internet-wide renumbering<br>
effort.<br>
<br>
Finally, I would note that while routing tables are large, the<br>
internet still functions - this may not be the best use of your time<br>
therefore.<br>
<br>
Dave.<br>
<br>
<o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>

--_000_AM4PR0401MB2241174F682EE6776E9E27E6BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 08:29:16 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F3D129C48; Fri, 28 Apr 2017 08:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 G9Bio4uKTxxl; Fri, 28 Apr 2017 08:29:11 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-oln040092070036.outbound.protection.outlook.com [40.92.70.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486D8129510; Fri, 28 Apr 2017 08:25:26 -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; bh=fXhrDknjOnExRxTv5/xDpabjQMVY4on4D34i3zAO520=; b=PAu3ir3d3Cby8oQ1putxATrnKAWeUyO0Dt2uRB8eFPkA6UJ715UC1/YHAg3wQUSXVcSkwDttuZwpaXBgzh9L2jOttJ9QxQgBlsM1tj2GpxNEOOl2c8SgCzYNp/mKjEkU88tcM0H2QtC07ShuKh+jUvZHKkhsl3KtQa6xW+cMXl8+oKXuFbnccTlE1DdsWyrS6obbgTHM1ZqNumXlie5xDd4rzWvmYRb6IFv7Z/yGLmsOggB+ruqvbahSJxZA8oZPetkYpJP7Hydgt9iI+IgDp8COyaK2yzT4PVj2j1WjxJ+ZcNBnJIrCQcsCP8qMktlPxkjeYMQY6pv3HfM6bYNRbg==
Received: from AM5EUR03FT008.eop-EUR03.prod.protection.outlook.com (10.152.16.52) by AM5EUR03HT186.eop-EUR03.prod.protection.outlook.com (10.152.17.191) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 15:25:24 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.58) by AM5EUR03FT008.mail.protection.outlook.com (10.152.16.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 15:25:24 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 15:25:24 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf-draft-submission@ietf.org" <ietf-draft-submission@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Regional Routing Protocol (RRP).
Thread-Topic: Regional Routing Protocol (RRP).
Thread-Index: AdLAMxPOyQ3b5pg0T4+pdF/szMFgYg==
Date: Fri, 28 Apr 2017 15:25:24 +0000
Message-ID: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:43DB1918883FF33C20D8F899C76DE550A7730F18C9565E15F6BC44DAD7B23B01; UpperCasedChecksum:A4B1EA8DB78B4ED8F4968FEA952BA4F1C7340DB4DAF2E65DF021DBB7F2BFDA9B; SizeAsReceived:7963; Count:40
x-tmn: [jW7mp/wAeH05uDfTu8kSUMBvdZKVIyBK]
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT186; 5:I3VBqax7MyZkslyUWo1vlJeBC5V+iYCvd5NeTPFqpLRTKUPmTEf3UfcAtPTgLlK3snKf5rNkUZ11Lm9x6bcbm7FzK0ep3T85nd+FKBLRbcsgGGmPupBLypeVwAtDWqh2R69W99m/RTRmMsRBTVdxqg==; 24:bBiXadyU59tPVBAOTUhFuJhWULzZRt63dKyXQnai0KyKu08R44rGb0uVi+zZHQ/FYPm7x3w3CIsCWtjxBbyiHfGKf6wOR4moqfmJd/4PkxA=; 7:uSli2+pYrpvmNqa5Xm36itpSqNZ8B7RAo2SFTjhVSQ3GCS58KVS4pWaSizaUhVAeHhPRacig1vXwGOyrXusjKO4S6u/0jSPryKM5RcLxyWYG+fR862BJjhjvmII926eIv88xPyAO9OVTZ5B7bFIsp+QzqtgHwbgTWtyJcjevTkGfgFYh/JwLyuGjBA9jziqNBulzadIUZTX7Ib5nxppdhIMa2PUTkndmCJi1brixyLGmHf41FqldaYKHWmQCNNQYswpLoSy804RsCHVi4CH5EVQzfXgBhjTDnaFkhWZH42+juWuuD1MjPz1mvUL/ablu
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT186; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: a855ee71-d07a-4e7d-b8d2-08d48e4aca88
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(201702181274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR03HT186; 
x-ms-exchange-slblob-mailprops: Ad+mZByrAbSnRUvNi/M6uSCUMh3CeHZwkWI0mOTHFIvcsEEzrwL1ApCgF4Vk3BZCFLhSYaD5UZ5JefjVfptv5UySrmFUjsh1Dt3QeFxGTLKDa/Zktc6zRyaSO/d9t4RB5Kzj0UxaxFMbj9jmQpl5q7XgTEAe4N9lEIMdCvWltFyiM8hEXR5e05u0acos4MoUE2qCwMoaVKFs32/Jlj7gxxD/IjL0SNuLQo2jk07hjne2zv1nw1qN7vh5k7RO82aMAhlRgwsabqNpz5Du3Y1FxiAPMjFrpnuZgec96II4x3Do5OoGigVyhkOnrRjNblAhHJn6VhXNHeNxrwCWyc4UUsQjrtZVSDwwbSsvqMUWUuY1I6PLuYiursITRZvXFPfwW00pUUwyyWeeXA3HsGy815VXK5qVNctCduK2auBc4nVrnL25XjdpxQp+G7zVJDzWZMAG1KpWAN/r7TlkxFI3xq7ZwLxwKQqywtVW4yccOIaNPXgqawvhtTkkAEBBVApMHMfgrEDioNdP2BCIcfzxxcbh5G65/ERDQ1bAcY4nJbZE/yka/7cMM2T3f4Gm8QQDkM9p+9jBx84Ec5+NtMxMTlOqXJlcTPl1Zjibrbw0NauHSraSdc30W0cKNROKATvMTsVnO3YhSdSXyix5Gu/jdnJiKLNcf5Kn
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT186; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT186; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_004_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 15:25:24.1973 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT186
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TolgkfLoaEgg6b9yi0kGB-d6aD4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:29:15 -0000

--_004_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_
Content-Type: multipart/alternative;
	boundary="_000_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_"

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

Hi Jasmine,

Please don't upload the 2nd version of the KRP ID and please upload the 1st=
 new version with another draft title Regional Routing Protocol (RRP) discu=
ssing the same topic as KRP.

Best Regards,

Khaled Omar

--_000_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_
Content-Type: text/html; charset="us-ascii"
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" 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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Jasmine,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please don&#8217;t upload the 2<sup>nd</sup> version=
 of the KRP ID and please upload the 1<sup>st</sup> new version with anothe=
r draft title Regional Routing Protocol (RRP) discussing the same topic as =
KRP.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled Omar <o:p></o:p></p>
</div>
</body>
</html>

--_000_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_--

--_004_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_
Content-Type: text/plain; name="draft-omar-rrp-00.txt"
Content-Description: draft-omar-rrp-00.txt
Content-Disposition: attachment; filename="draft-omar-rrp-00.txt"; size=27424;
	creation-date="Wed, 26 Apr 2017 13:42:14 GMT";
	modification-date="Fri, 28 Apr 2017 15:18:35 GMT"
Content-Transfer-Encoding: base64

//5kAHIAYQBmAHQALQBvAG0AYQByAC0AcgByAHAALQAwADAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgAEsAaABhAGwAZQBkACAATwBtAGEAcgANAAoASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABoAGUAIABSAG8AYQBkACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAA0ACgBJAG4AdABlAG4AZABlAGQAIABzAHQAYQB0AHUAcwA6ACAAUwB0
AGEAbgBkAGEAcgBkACAAVAByAGEAYwBrACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAANAAoARQB4AHAAaQByAGUAcwA6ACAATwBjAHQAbwB2
AGUAcgAgADIAOAAsACAAMgAwADEANwAJAAkAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IABBAHAAcgBpAGwAIAAyADgALAAgADIAMAAxADcADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAADQAKAA0A
CgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAUgBlAGcAaQBv
AG4AYQBsACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgAUgBSAFAAKQANAAoA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
AFMAcABlAGMAaQBmAGkAYwBhAHQAaQBvAG4ADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAGQAcgBhAGYAdAAtAG8AbQBhAHIALQByAHIAcAAt
ADAAMAANAAoADQAKAFMAdABhAHQAdQBzACAAbwBmACAAdABoAGkAcwAgAE0AZQBtAG8ADQAKAA0A
CgAgACAAIABUAGgAaQBzACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAaQBzACAAcwB1
AGIAbQBpAHQAdABlAGQAIABpAG4AIABmAHUAbABsACAAYwBvAG4AZgBvAHIAbQBhAG4AYwBlACAA
dwBpAHQAaAAgAHQAaABlACAAcAByAG8AdgBpAHMAaQBvAG4AcwANAAoAIAAgACAAbwBmACAAQgBD
AFAAIAA3ADgAIABhAG4AZAAgAEIAQwBQACAANwA5AC4ADQAKAA0ACgAgACAAIABJAG4AdABlAHIA
bgBlAHQALQBEAHIAYQBmAHQAcwAgAGEAcgBlACAAdwBvAHIAawBpAG4AZwAgAGQAbwBjAHUAbQBl
AG4AdABzACAAbwBmACAAdABoAGUAIABJAG4AdABlAHIAbgBlAHQAIABFAG4AZwBpAG4AZQBlAHIA
aQBuAGcAIABUAGEAcwBrAA0ACgAgACAAIABGAG8AcgBjAGUAIAAoAEkARQBUAEYAKQAuACAATgBv
AHQAZQAgAHQAaABhAHQAIABvAHQAaABlAHIAIABnAHIAbwB1AHAAcwAgAG0AYQB5ACAAYQBsAHMA
bwAgAGQAaQBzAHQAcgBpAGIAdQB0AGUAIAB3AG8AcgBrAGkAbgBnACAAZABvAGMAdQBtAGUAbgB0
AHMADQAKACAAIAAgAGEAcwAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzAC4AIABUAGgA
ZQAgAGwAaQBzAHQAIABvAGYAIABjAHUAcgByAGUAbgB0ACAASQBuAHQAZQByAG4AZQB0AC0ARABy
AGEAZgB0AHMAIABpAHMAIABhAHQADQAKACAAIAAgAGgAdAB0AHAAOgAvAC8AZABhAHQAYQB0AHIA
YQBjAGsAZQByAC4AaQBlAHQAZgAuAG8AcgBnAC8AZAByAGEAZgB0AHMALwBjAHUAcgByAGUAbgB0
AC8ALgANAAoADQAKACAAIAAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzACAAYQByAGUA
IABkAHIAYQBmAHQAIABkAG8AYwB1AG0AZQBuAHQAcwAgAHYAYQBsAGkAZAAgAGYAbwByACAAYQAg
AG0AYQB4AGkAbQB1AG0AIABvAGYAIABzAGkAeAAgAG0AbwBuAHQAaABzACAAYQBuAGQADQAKACAA
IAAgAG0AYQB5ACAAYgBlACAAdQBwAGQAYQB0AGUAZAAsACAAcgBlAHAAbABhAGMAZQBkACwAIABv
AHIAIABvAGIAcwBvAGwAZQB0AGUAZAAgAGIAeQAgAG8AdABoAGUAcgAgAGQAbwBjAHUAbQBlAG4A
dABzACAAYQB0ACAAYQBuAHkAIAB0AGkAbQBlAC4ADQAKACAAIAAgAEkAdAAgAGkAcwAgAGkAbgBh
AHAAcAByAG8AcAByAGkAYQB0AGUAIAB0AG8AIAB1AHMAZQAgAEkAbgB0AGUAcgBuAGUAdAAtAEQA
cgBhAGYAdABzACAAYQBzACAAcgBlAGYAZQByAGUAbgBjAGUAIABtAGEAdABlAHIAaQBhAGwAIABv
AHIAIAB0AG8AIABjAGkAdABlAA0ACgAgACAAIAB0AGgAZQBtACAAbwB0AGgAZQByACAAdABoAGEA
bgAgAGEAcwAgACIAdwBvAHIAawAgAGkAbgAgAHAAcgBvAGcAcgBlAHMAcwAuACIADQAKAA0ACgAg
ACAAIABUAGgAaQBzACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAdwBpAGwAbAAgAGUA
eABwAGkAcgBlACAAbwBuACAATwBjAHQAbwBiAGUAcgAgADIAOAAsACAAMgAwADEANwAuAA0ACgAN
AAoADQAKAA0ACgBDAG8AcAB5AHIAaQBnAGgAdAAgAE4AbwB0AGkAYwBlAA0ACgANAAoAIAAgACAA
QwBvAHAAeQByAGkAZwBoAHQAIAAoAGMAKQAgADIAMAAxADYAIABJAEUAVABGACAAVAByAHUAcwB0
ACAAYQBuAGQAIAB0AGgAZQAgAHAAZQByAHMAbwBuAHMAIABpAGQAZQBuAHQAaQBmAGkAZQBkACAA
YQBzACAAdABoAGUAIABkAG8AYwB1AG0AZQBuAHQADQAKACAAIAAgAGEAdQB0AGgAbwByAHMALgAg
AEEAbABsACAAcgBpAGcAaAB0AHMAIAByAGUAcwBlAHIAdgBlAGQALgAgAA0ACgANAAoAIAAgACAA
VABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAGkAcwAgAHMAdQBiAGoAZQBjAHQAIAB0AG8AIABC
AEMAUAAgADcAOAAgAGEAbgBkACAAdABoAGUAIABJAEUAVABGACAAVAByAHUAcwB0ACcAcwAgAEwA
ZQBnAGEAbAAgAFAAcgBvAHYAaQBzAGkAbwBuAHMADQAKACAAIAAgAFIAZQBsAGEAdABpAG4AZwAg
AHQAbwAgAEkARQBUAEYAIABEAG8AYwB1AG0AZQBuAHQAcwAgACgAaAB0AHQAcAA6AC8ALwB0AHIA
dQBzAHQAZQBlAC4AaQBlAHQAZgAuAG8AcgBnAC8AbABpAGMAZQBuAHMAZQAtAGkAbgBmAG8AKQAg
AGkAbgAgAGUAZgBmAGUAYwB0AA0ACgAgACAAIABvAG4AIAB0AGgAZQAgAGQAYQB0AGUAIABvAGYA
IABwAHUAYgBsAGkAYwBhAHQAaQBvAG4AIABvAGYAIAB0AGgAaQBzACAAZABvAGMAdQBtAGUAbgB0
AC4AIABQAGwAZQBhAHMAZQAgAHIAZQB2AGkAZQB3ACAAdABoAGUAcwBlACAAZABvAGMAdQBtAGUA
bgB0AHMADQAKACAAIAAgAGMAYQByAGUAZgB1AGwAbAB5ACwAIABhAHMAIAB0AGgAZQB5ACAAZABl
AHMAYwByAGkAYgBlACAAeQBvAHUAcgAgAHIAaQBnAGgAdABzACAAYQBuAGQAIAByAGUAcwB0AHIA
aQBjAHQAaQBvAG4AcwAgAHcAaQB0AGgAIAByAGUAcwBwAGUAYwB0ACAAdABvACAAdABoAGkAcwAN
AAoAIAAgACAAZABvAGMAdQBtAGUAbgB0AC4AIABDAG8AZABlACAAQwBvAG0AcABvAG4AZQBuAHQA
cwAgAGUAeAB0AHIAYQBjAHQAZQBkACAAZgByAG8AbQAgAHQAaABpAHMAIABkAG8AYwB1AG0AZQBu
AHQAIABtAHUAcwB0ACAAaQBuAGMAbAB1AGQAZQANAAoAIAAgACAAUwBpAG0AcABsAGkAZgBpAGUA
ZAAgAEIAUwBEACAATABpAGMAZQBuAHMAZQAgAHQAZQB4AHQAIABhAHMAIABkAGUAcwBjAHIAaQBi
AGUAZAAgAGkAbgAgAFMAZQBjAHQAaQBvAG4AIAA0AC4AZQAgAG8AZgAgAHQAaABlACAAVAByAHUA
cwB0ACAATABlAGcAYQBsAA0ACgAgACAAIABQAHIAbwB2AGkAcwBpAG8AbgBzACAAYQBuAGQAIABh
AHIAZQAgAHAAcgBvAHYAaQBkAGUAZAAgAHcAaQB0AGgAbwB1AHQAIAB3AGEAcgByAGEAbgB0AHkA
IABhAHMAIABkAGUAcwBjAHIAaQBiAGUAZAAgAGkAbgAgAHQAaABlACAAUwBpAG0AcABsAGkAZgBp
AGUAZAANAAoAIAAgACAAQgBTAEQAIABMAGkAYwBlAG4AcwBlAC4ADQAKAA0ACgANAAoAQQBiAHMA
dAByAGEAYwB0AA0ACgANAAoAIAAgACAAVABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAHMAcABl
AGMAaQBmAGkAZQBzACAAUgBlAGcAaQBvAG4AYQBsACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQA
bwBjAG8AbAAsACAAcwBvAG0AZQB0AGkAbQBlAHMAIAByAGUAZgBlAHIAcgBlAGQAIAB0AG8AIABh
AHMADQAKACAAIAAgAEsASABBAEwARQBEACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8A
bAAgACgASwBSAFAAKQAuAA0ACgANAAoADQAKAA0ACgANAAoAVABhAGIAbABlACAAbwBmACAAQwBv
AG4AdABlAG4AdABzAA0ACgANAAoAIAAgACAAMQAuACAASQBuAHQAcgBvAGQAdQBjAHQAaQBvAG4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADEADQAKACAAIAAgADIA
LgAgAFIAZQBnAGkAbwBuAGEAbAAgAFIAbwB1AHQAaQBuAGcAIABQAHIAbwB0AG8AYwBvAGwAIAAo
AFIAUgBQACkALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAxAA0ACgAgACAAIAAzAC4AIABSAFIAUAAgAEYAbwByAHcAYQByAGQAaQBu
AGcAIABNAGUAYwBoAGEAbgBpAHMAbQAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4AMgANAAoAIAAgACAAMwAu
ACAAUwBlAGMAdQByAGkAdAB5ACAAQwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBzAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuADQADQAKACAAIAAgADQALgAgAEEAYwBrAG4AbwB3AGwAZQBkAGcAbQBlAG4A
dABzAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgA0AA0ACgAgACAAIAA1AC4A
IABBAHUAdABoAG8AcgBzACcAIABBAGQAZAByAGUAcwBzAGUAcwAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ANAANAAoAIAAgACAANgAuACAASQBBAE4AQQAgAEMAbwBuAHMAaQBkAGUAcgBh
AHQAaQBvAG4AcwAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADQADQAKACAAIAAgADcALgAg
AFIAZQBmAGUAcgBlAG4AYwBlAHMALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgA0AA0ACgAgACAAIAA4AC4AIABGAHUAbABsACAAQwBvAHAAeQByAGkAZwBoAHQA
IABTAHQAYQB0AGUAbQBlAG4AdAAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ANAANAAoADQAKAA0ACgANAAoA
DQAKAA0ACgBLAGgAYQBsAGUAZAAgAE8AbQBhAHIAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABJ
AG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIABbAFAAYQBnAGUAIAAxAF0ADQAKAA0ACgBSAEYAQwAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAUgBlAGcAaQBvAG4AYQBsACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8A
bAAgACgAUgBSAFAAKQAgACAAIAAgACAAIAAgACAAQQBwAHIAaQBsACAAMgA4ACwAIAAyADAAMQA3
AA0ACgANAAoADQAKAA0ACgAxAC4AIAAgAEkAbgB0AHIAbwBkAHUAYwB0AGkAbwBuAA0ACgANAAoA
DQAKACAAIAAgACAALQAgAFIAZQBnAGkAbwBuAGEAbAAgAFIAbwB1AHQAaQBuAGcAIABQAHIAbwB0
AG8AYwBvAGwAIAAoAFIAUgBQACkAIABpAHMAIABhAG4AIABFAHgAdABlAHIAaQBvAHIAIABHAGEA
dABlAHcAYQB5ACAAUAByAG8AdABvAGMAbwBsACAAKABFAEcAUAApACAAdABoAGEAdAANAAoAIAAg
ACAAIAAgACAAaQBuAHQAcgBvAGQAdQBjAGUAcwAgAGEAIABuAGUAdwAgAHcAYQB5ACAAbwBmACAA
cgBvAHUAdABpAG4AZwAgAEkAUAAgAHAAYQBjAGsAZQB0AHMAIABmAHIAbwBtACAAdABoAGUAIABz
AG8AdQByAGMAZQAgAHQAbwAgAHQAaABlACAAZABlAHMAdABpAG4AYQB0AGkAbwBuAA0ACgAgACAA
IAAgACAAIAB0AGgAcgBvAHUAZwBoACAAZABpAGYAZgBlAHIAZQBuAHQAIABBAHUAdABvAG4AbwBt
AG8AdQBzACAAUwB5AHMAdABlAG0AcwAgACgAQQBTAHMAKQAuAA0ACgAgACAAIAAgAC0AIABUAGgA
ZQAgAEkAbgB0AGUAcgBuAGUAdAAgAHcAaQBsAGwAIABiAGUAIABzAHUAYgBkAGkAdgBpAGQAZQBk
ACAAaQBuAHQAbwAgAGwAbwBnAGkAYwBhAGwAIAByAGUAZwBpAG8AbgBzACAAbwByACAAYgB5ACAA
dABoAGUAIABwAGgAeQBzAGkAYwBhAGwADQAKACAAIAAgACAAIAAgAGwAbwBjAGEAdABpAG8AbgAg
AG8AZgAgAGMAbwBuAHQAaQBuAGUAbgB0AHMALgANAAoAIAAgACAAIAAtACAAVABoAGUAIAByAG8A
dQB0AGkAbgBnACAAcAByAG8AYwBlAHMAcwAgAHQAaABhAHQAIABSAGUAZwBpAG8AbgBhAGwAIABS
AG8AdQB0AGkAbgBnACAAUAByAG8AdABvAGMAbwBsACAAKABSAFIAUAApACAAdQBzAGUAcwAgAGkA
cwAgAGIAYQBzAGUAZAAgAG8AbgAgAHQAaABlAA0ACgAgACAAIAAgACAAIABSAFIAUAAgAFIAZQBn
AGkAbwBuACAATgB1AG0AYgBlAHIAIAAoAFIATgApACwAIAB0AGgAZQAgAFIAUgBQACAAQQB1AHQA
bwBuAG8AbQBvAHUAcwAgAFMAeQBzAHQAZQBtACAATgB1AG0AYgBlAHIAIAAoAEEAUwBOACkALAAg
AEIAZQBzAHQAIABQAGEAdABoACAAQQBsAGcAbwByAGkAdABoAG0ADQAKACAAIAAgACAAIAAgACgA
QQBTACAAUABhAHQAaAApACAAYQBuAGQAIAB0AGgAZQAgAGUAZgBmAG8AcgB0AHMAIABtAGEAZABl
ACAAYgB5ACAAdABoAGUAIABJAEcAUAAgAHcAaQB0AGgAaQBuACAAZQBhAGMAaAAgAEEAUwAuAA0A
CgAgACAAIAAgAC0AIABUAGgAZQAgAG0AYQBqAG8AcgAgAGQAaQBmAGYAZQByAGUAbgBjAGUAIABi
AGUAdAB3AGUAZQBuACAAUgBSAFAAIABhAG4AZAAgAEIARwBQACAAaQBzACAAdABoAGEAdAAgAFIA
UgBQACAAZABvAGUAcwAgAG4AbwB0ACAAdQBzAGUAcwAgAGEAIABsAGEAcgBnAGUAIAB0AGEAYgBs
AGUADQAKACAAIAAgACAAIAAgAHcAaQB0AGgAIABoAHUAbgBkAHIAZQBkAHMAIABvAGYAIAB0AGgA
bwB1AHMAYQBuAGQAcwAgAG8AZgAgAGUAbgB0AHIAaQBlAHMAIAAoAEIARwBQACAAVABhAGIAbABl
ACkAIABzAHQAbwByAGUAZAAgAHcAaQB0AGgAaQBuACAAZQBhAGMAaAAgAEkAbgB0AGUAcgBuAGUA
dAAgAHIAbwB1AHQAZQByACwADQAKACAAIAAgACAAIAAgAGkAbgBzAHQAZQBhAGQAIABvAGYAIAB0
AGgAYQB0ACwAIABpAHQAIAB1AHMAZQBzACAAYQAgAHMAbQBhAHIAdABlAHIAIAB3AGEAeQAgAG8A
ZgAgAHIAbwB1AHQAaQBuAGcAIABiAGEAcwBlAGQAIABvAG4AIAB0AGgAZQAgAFIAUgBQACAAUgBO
ACwAIABSAFIAUAAgAEEAUwBOAA0ACgAgACAAIAAgACAAIABzAHQAbwByAGUAZAAgAHcAaQB0AGgA
aQBuACAAZQBhAGMAaAAgAEkAUAAgAGEAZABkAHIAZQBzAHMALAAgAEIAZQBzAHQAIABQAGEAdABo
ACAAQQBsAGcAbwByAGkAdABoAG0AIAAoAEEAUwAgAFAAYQB0AGgAKQAgAGEAbgBkACAAdABoAGUA
IABlAGYAZgBvAHIAdABzACAAYQBsAHIAZQBhAGQAeQANAAoAIAAgACAAIAAgACAAYgBlAGkAbgBn
ACAAZABvAG4AZQAgAGIAeQAgAGUAYQBjAGgAIABJAEcAUAAgAHcAaQB0AGgAaQBuACAAYQBuACAA
QQBTAC4ADQAKAA0ACgANAAoADQAKAA0ACgAyAC4AIABSAGUAZwBpAG8AbgBhAGwAIABSAG8AdQB0
AGkAbgBnACAAUAByAG8AdABvAGMAbwBsACAAKABSAFIAUAApAA0ACgANAAoADQAKACAAIAAgACAA
LQAgAFIAUgBQACAAdQBzAGUAcwAgAG4AZQB3ACAAdABlAHIAbQBzACAAdABoAGEAdAAgAGMAYQBu
ACAAYgBlACAAZABlAGYAaQBuAGUAZAAgAGEAcwAgAGYAbwBsAGwAbwB3AHMAOgANAAoADQAKAA0A
CgAgACAAIAAgACoAIABSAGUAZwBpAG8AbgAgAE4AdQBtAGIAZQByACAAKABSAE4AKQA6AA0ACgAN
AAoADQAKACAAIAAgAC0AIABUAGgAZQAgADEAcwB0ACAAaABlAHgAIABkAGkAZwBpAHQAIABvAGYA
IAB0AGgAZQAgADIAbgBkACAAZwByAG8AdQBwACAAbwBmACAAYQBuACAASQBQAHYANgAgAGEAZABk
AHIAZQBzAHMAIABkAGUAdABlAHIAbQBpAG4AZQBzACAAbwBuACAAdwBoAGkAYwBoACAAUgBOACAA
dABoAGkAcwAgAEkAUAB2ADYADQAKACAAIAAgACAAIABhAGQAZAByAGUAcwBzACAAaQBzACAAbABv
AGMAYQB0AGUAZAAuAA0ACgAgACAAIAAtACAAVABoAGUAIAAxAHMAdAAgAG8AYwB0AGUAdAAgAG8A
ZgAgAGEAbgAgAEkAUAB2ADQAIABhAGQAZAByAGUAcwBzACAAZABlAHQAZQByAG0AaQBuAGUAcwAg
AG8AbgAgAHcAaABpAGMAaAAgAFIATgAgAHQAaABpAHMAIABJAFAAdgA0ACAAYQBkAGQAcgBlAHMA
cwAgAGkAcwAgAGwAbwBjAGEAdABlAGQALgANAAoAIAAgACAALQAgAFQAaABlACAAdABhAGIAbABl
ACAAdABoAGEAdAAgAHcAaQBsAGwAIABiAGUAIAB1AHMAZQBkACAAbABpAHMAdABpAG4AZwAgAHQA
aABlACAAUgBlAGcAaQBvAG4AIABOAHUAbQBiAGUAcgAgACgAUgBOACkALAAgAHQAaABlACAAYwBv
AHIAcgBlAHMAcABvAG4AZABpAG4AZwAgAEkAUAB2ADYADQAKACAAIAAgACAAIAAyAG4AZAAgAGcA
cgBvAHUAcAAgADEAcwB0ACAAaABlAHgAIABkAGkAZwBpAHQAcwAgAGEAbgBkACAAdABoAGUAIABJ
AFAAdgA0ACAAMQBzAHQAIABvAGMAdABlAHQAIABwAG8AbwBsACAAbwBmACAAbgB1AG0AYgBlAHIA
cwAgAGkAcwAgAGMAYQBsAGwAZQBkACAAdABoAGUADQAKACAAIAAgACAAIABSAGUAZwBpAG8AbgAg
AE4AdQBtAGIAZQByACAAVABhAGIAbABlACAAKABSAE4AVAApACAAYQBuAGQAIABpAHMAIABzAHQA
bwByAGUAZAAgAG8AbgAgAGUAdgBlAHIAeQAgAFIAUgBQACAAcgBvAHUAdABlAHIAIABhAG4AZAAg
AGkAcwAgAGEAcwAgAGYAbwBsAGwAbwB3AHMAOgANAAoADQAKAA0ACgAgACAAIAAgACAAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgANAAoAIAAgACAAIAAgACoAIAAgAFIAZQBnAGkAbwBuACAATgB1AG0AYgBlAHIA
IAAgACoAIAAgADEAcwB0ACAASABlAHgAIABEAGkAZwBpAHQAIABvAGYAIAB0AGgAZQAgADIAbgBk
ACAASQBQAHYANgAgAEcAcgBvAHUAcAAgACAAIAAqACAAIAAxAHMAdAAgAEkAUAB2ADQAIABPAGMA
dABlAHQAIABEAGUAYwBpAG0AYQBsACAARABpAGcAaQB0AHMAIAAgACoAIAANAAoAIAAgACAAIAAg
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAIAAgAA0ACgAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAMQAg
ACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgADAAIAAtACAANQAgAC0A
IABBACAALQAgAEYAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAQQBSAEkATgAgAFAAbwBvAGwAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAA
IAAgACAAIAAgACAADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACAAIAANAAoAIAAgACAA
IAAgACoAIAAgACAAIAAgACAAIAAgADIAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAxACAALQAgADYAIAAtACAAQgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAUgBJAFAARQAgAE4AQwBDACAAUABvAG8AbAAg
ACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgAA0ACgAgACAAIAAgACAAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAgACAADQAKACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAzACAAIAAgACAA
IAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAMgAgAC0AIAA3ACAALQAgAEMAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAA
QQBGAFIASQBOAEkAQwAgAFAAbwBvAGwAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAg
ACAAIAANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAIAAgAA0ACgAgACAAIAAgACAAKgAg
ACAAIAAgACAAIAAgACAANAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgADMAIAAtACAAOAAgAC0AIABEACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAQQBQAE4ASQBDACAAUABvAG8AbAAgACAAIAAgACAA
IAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACAAIAANAAoAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgADUAIAAgACAAIAAgACAAIAAg
ACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAA0ACAALQAgADkAIAAtACAARQAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIABMAEEAQwBO
AEkAQwAgAFAAbwBvAGwAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgAA0A
CgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgANAAoADQAKAA0ACgANAAoAIAAgACAAIAAqACAA
UgBlAGcAaQBvAG4AYQBsACAAQgBvAGEAcgBkAGUAcgAgAFIAbwB1AHQAZQByACAAKABSAEIAUgAp
ACAAPQA9AD4AIABBACAAcgBvAHUAdABlAHIAIABpAG4AIABhACAAcgBlAGcAaQBvAG4AIAB0AGgA
YQB0ACAAaABhAHMADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAYQB0ACAAbABlAGEAcwB0ACAA
bwBuAGUAIABpAG4AdABlAHIAZgBhAGMAZQAgAGMAbwBuAG4AZQBjAHQAZQBkAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAHQAbwAgAGEAIAByAG8AdQB0AGUAcgAnAHMAIABpAG4AdABlAHIAZgBh
AGMAZQAgAGkAbgAgAGEAbgBvAHQAaABlAHIADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAcgBl
AGcAaQBvAG4ALgANAAoADQAKAA0ACgAgACAAIAAgACoAIABSAGUAZwBpAG8AbgBhAGwAIABSAG8A
dQB0AGUAcgAgACgAUgBSACkAIAA9AD0APgAgAC0AIABBACAAcgBvAHUAdABlAHIAIABpAG4AIABh
ACAAcgBlAGcAaQBvAG4AIABhAG4AZAAgAGgAYQBzACAAYQBsAGwAIABpAG4AdABlAHIAZgBhAGMA
ZQBzAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIABjAG8AbgBuAGUAYwB0AGUAZAAgAHQAbwAgAG8AdABoAGUAcgAgAHIA
bwB1AHQAZQByAHMAIABpAG4AIAB0AGgAZQAgAHMAYQBtAGUADQAKACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAHIAZQBnAGkA
bwBuAC4ADQAKAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgAC0AIABBACAAcgBvAHUAdABlAHIAIABpAG4AIABhACAAbABvAGMA
YQBsACAAQQBTACAAdABoAGEAdAAgAGgAYQBzACAAYQB0ACAAbABlAGEAcwB0AA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IABvAG4AZQAgAGkAbgB0AGUAcgBmAGEAYwBlACAAYwBvAG4AbgBlAGMAdABlAGQAIAB0AG8AIABh
ACAAZABpAGYAZgBlAHIAZQBuAHQAIABBAFMALgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAA0ACgANAAoAIAAgACAAIAAq
ACAATABvAGMAYQBsACAAUgBSAFAAIABBAFMAIABSAG8AdQB0AGUAcgAgACgATABSAEEAUgApACAA
PQA9AD4AIABBACAAcgBvAHUAdABlAHIAIABpAG4AIABhAG4AIABBAFMAIAB0AGgAYQB0ACAAaABh
AHMAIABhAGwAbAAgAGkAbgB0AGUAcgBmAGEAYwBlAHMADQAKACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAYwBv
AG4AbgBlAGMAdABlAGQAIAB0AG8AIABvAHQAaABlAHIAIAByAG8AdQB0AGUAcgBzACAAaQBuACAA
dABoAGUAIABzAGEAbQBlACAAQQBTAC4ADQAKAA0ACgANAAoADQAKACAAIAAgAC0AIABFAGEAYwBo
ACAAUgBCAFIAIABhAG4AZAAgAFIAUgAgAGkAcwAgAGMAbwBuAGYAaQBnAHUAcgBlAGQAIAB3AGkA
dABoACAAYQAgAFIAZQBnAGkAbwBuACAATgB1AG0AYgBlAHIAIAAoAFIATgApACAAdABoAGEAdAAg
AGkAZABlAG4AdABpAGYAaQBlAHMADQAKACAAIAAgACAAIABpAG4AIAB3AGgAaQBjAGgAIAByAGUA
ZwBpAG8AbgAgAHQAaABhAHQAIAByAG8AdQB0AGUAcgAgAGkAcwAgAGwAbwBjAGEAdABlAGQALgAg
AA0ACgAgACAAIAAtACAAQQBsAGwAIABSAEIAUgBzACAAYQBuAGQAIABSAFIAcwAgAGkAbgB0AGUA
cgBmAGEAYwBlAHMAIAB3AGkAbABsACAAYgBlACAAYQBzAHMAaQBnAG4AZQBkACAAYgB5ACAAZABl
AGYAYQB1AGwAdAAgAHQAbwAgAHQAaABlACAAYwBvAG4AZgBpAGcAdQByAGUAZAANAAoAIAAgACAA
IAAgAFIAZQBnAGkAbwBuACAATgB1AG0AYgBlAHIAIAAoAFIATgApAC4ADQAKACAAIAAgAA0ACgAg
ACAAIAAtACAAVABoAGUAIAB0AHcAbwAgAGMAbwBuAG4AZQBjAHQAZQBkACAAUgBSAFAAIAByAG8A
dQB0AGUAcgBzACAAZQB4AGMAaABhAG4AZwBlACAAdABoAGUAaQByACAAUgBOAHMAOgAgAA0ACgAN
AAoAIAAgACAAIAAgACAAIAAxACkAIABJAGYAIAB0AGgAZQB5ACAAYQByAGUAIAB0AGgAZQAgAHMA
YQBtAGUALAAgAHQAaABlACAAdAB3AG8AIABSAFIAUAAgAHIAbwB1AHQAZQByAHMAIABhAHIAZQAg
AFIAUgBzAC4ADQAKACAAIAAgACAAIAAgACAAMgApACAASQBmACAAdABoAGUAeQAgAGEAcgBlACAA
ZABpAGYAZgBlAHIAZQBuAHQALAAgAHQAaABlACAAdAB3AG8AIABSAFIAUAAgAHIAbwB1AHQAZQBy
AHMAIABhAHIAZQAgAFIAQgBSAHMALgANAAoADQAKACAAIAANAAoAIAAgACAALQAgAFQAaABlACAA
dAB3AG8AIABjAG8AbgBuAGUAYwB0AGUAZAAgAFIAUgBQACAAcgBvAHUAdABlAHIAcwAgAGUAeABj
AGgAYQBuAGcAZQAgAHQAaABlAGkAcgAgAFIAUgBQACAAQQBTAE4AcwA6AA0ACgANAAoAIAAgACAA
IAAgACAAIAAxACkAIABJAGYAIAB0AGgAZQB5ACAAYQByAGUAIAB0AGgAZQAgAHMAYQBtAGUALAAg
AHQAaABlACAAdAB3AG8AIABSAFIAUAAgAHIAbwB1AHQAZQByAHMAIABhAHIAZQAgAEwAUgBBAFIA
cwAuAA0ACgAgACAAIAAgACAAIAAgADIAKQAgAEkAZgAgAHQAaABlAHkAIABhAHIAZQAgAGQAaQBm
AGYAZQByAGUAbgB0ACwAIAB0AGgAZQAgAHQAdwBvACAAUgBSAFAAIAByAG8AdQB0AGUAcgBzACAA
YQByAGUAIABSAFIAcwAuACAAIAANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoASwBoAGEAbABl
AGQAIABPAG0AYQByACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAASQBuAHQAZQByAG4AZQB0AC0A
RAByAGEAZgB0ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEAZwBl
ACAAMgBdAA0ACgANAAoAUgBGAEMAIAAgACAAIAAgACAAIAAgACAAIAAgACAAUgBlAGcAaQBvAG4A
YQBsACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgAUgBSAFAAKQAgACAAIAAg
ACAAIAAgACAAQQBwAHIAaQBsACAAMgA4ACwAIAAyADAAMQA3AA0ACgANAAoADQAKAA0ACgANAAoA
MwAuACAAUgBSAFAAIABGAG8AcgB3AGEAcgBkAGkAbgBnACAATQBlAGMAaABhAG4AaQBzAG0ADQAK
AA0ACgANAAoADQAKACAAIAAgAC0AIABUAGgAZQAgAFIAUgBQACAAQQBTAE4AIABpAHMAIAByAGUA
cAByAGUAcwBlAG4AdABlAGQAIABhAHMAIABmAG8AbABsAG8AdwBzADoADQAKAA0ACgAgACAAIAAg
ACAAYQApACAAVABoAGUAIAAyAG4AZAAgAHQAdwBvACAAZwByAG8AdQBwAHMAIABvAGYAIABhAG4A
IABJAFAAdgA2ACAAYQBkAGQAcgBlAHMAcwAgAGkAcwAgAHIAZQBwAHIAZQBzAGUAbgB0AGUAZAAg
AGEAcwAgAGYAbwBsAGwAbwB3AHMAOgANAAoADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAeAB4AHgAeAB8AHkAeQB5AHkAfAB5AHkAeQB5AHwAeQB5AHkAeQA6AHkAeQB5
AHkAfAB5AHkAeQB5AHwAeQB5AHkAeQB8AHkAeQB5AHkAIAAgACAAIAAgAEIAaQBuAGEAcgB5ACAA
RgBvAHIAbQBhAHQADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABYAFkAWQBZADoAWQBZ
AFkAWQAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAASABlAHgAYQBkAGUAYwBpAG0A
YQBsACAARgBvAHIAbQBhAHQADQAKAA0ACgAgACAAIAAgACAAIAAgAHcAaABlAHIAZQAgAFgAIABo
AGUAeAAgAGQAaQBnAGkAdAAgAGkAcwAgAGEAcwBzAG8AYwBpAGEAdABlAGQAIAB3AGkAdABoACAA
YQAgAHMAcABlAGMAaQBmAGkAYwAgAFIAZQBnAGkAbwBuACAATgB1AG0AYgBlAHIAIAAoAFIATgAp
AC4ADQAKACAAIAAgACAAIAAgACAAYQBuAGQAIABZAFkAWQA6AFkAWQBZAFkAIABoAGUAeAAgAGQA
aQBnAGkAdABzACAAcgBlAHAAcgBlAHMAZQBuAHQAcwAgAHQAaABlACAASwBSAFAAIABBAHUAdABv
AG4AbwBtAG8AdQBzACAAUwB5AHMAdABlAG0AIABOAHUAbQBiAGUAcgAgACgAQQBTAE4AKQAuAA0A
CgANAAoADQAKAA0ACgAgACAAIAAgACAAYgApACAAVABoAGUAIAAxAHMAdAAgAHQAdwBvACAAbwBj
AHQAZQB0AHMAIABvAGYAIABhAG4AIABJAFAAdgA0ACAAYQBkAGQAcgBlAHMAcwAgAGkAcwAgAHIA
ZQBwAHIAZQBzAGUAbgB0AGUAZAAgAGEAcwAgAGYAbwBsAGwAbwB3AHMAOgANAAoADQAKACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB5AHkA
eQB5AHkAeQB5AHkALgB5AHkAeQB5AHkAeQB5AHkAIAAgACAAIAAgACAAQgBpAG4AYQByAHkAIABG
AG8AcgBtAGEAdAANAAoADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABZAFkALgBZAFkAIAAgACAAIAAgACAAIAAg
ACAAIABIAGUAeABhAGQAZQBjAGkAbQBhAGwAIABGAG8AcgBtAGEAdAANAAoADQAKACAAIAAgACAA
IAAgAHcAaABlAHIAZQAgAFkAWQAuAFkAWQAgAGgAZQB4ACAAZABpAGcAaQB0AHMAIAByAGUAcABy
AGUAcwBlAG4AdABzACAAdABoAGUAIABSAFIAUAAgAEEAdQB0AG8AbgBvAG0AbwB1AHMAIABTAHkA
cwB0AGUAbQAgAE4AdQBtAGIAZQByACAAKABBAFMATgApAC4ADQAKAA0ACgAgACAAIAAgACAATgBv
AHQAZQA6AC0AIAAtACAAVABoAGUAIABSAGUAZwBpAG8AbgAgAE4AdQBtAGIAZQByACAAKABSAE4A
KQAgAGkAcwAgAHUAbgBpAHEAdQBlACAAZgBvAHIAIABlAHYAZQByAHkAIAByAGUAZwBpAG8AbgAu
AA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAtACAAVABoAGUAIABSAFIAUAAgAEEAUwBOACAA
bQB1AHMAdAAgAGIAZQAgAHUAbgBpAHEAdQBlACAAZgBvAHIAIABlAHYAZQByAHkAIABBAFMALgAN
AAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAALQAgAEYAbwByACAASQBQAHYANAAsACAAdABoAGUA
IAAxAHMAdAAgAHQAdwBvACAAbwBjAHQAZQB0AHMAIABhAHIAZQAgAHIAZQBwAHIAZQBzAGUAbgB0
AGUAZAAgAGkAbgAgAGQAZQBjAGkAbQBhAGwAIABpAG4AIAB0AGgAZQAgAEkAUAB2ADQAIABhAGQA
ZAByAGUAcwBzAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAaQB0AHMAZQBsAGYALAAg
AGIAdQB0ACAAdABoAGUAIABSAFIAUAAgAEEAUwBOACAAaQBzACAAcgBlAHAAcgBlAHMAZQBuAHQA
ZQBkACAAaQBuACAANAAgAGgAZQB4AGEAZABlAGMAaQBtAGEAbAAgAGQAaQBnAGkAdABzAC4ADQAK
AA0ACgANAAoADQAKACAAIAAgACAALQAgAFQAaABlAHIAZQAgAGEAcgBlACAAMwAgAHQAeQBwAGUA
cwAgAG8AZgAgAHQAYQBiAGwAZQBzACwAIAAyACAAUgBCAFIAIABtAGUAcwBzAGEAZwBlAHMAIABh
AG4AZAAgADEAIABSAFIAIABtAGUAcwBzAGEAZwBlACAAdABoAGEAdAAgAFIAUgBQACAAdQBzAGUA
cwAgAGYAbwByAA0ACgAgACAAIAAgACAAIABmAG8AcgB3AGEAcgBkAGkAbgBnACAAYQAgAHAAYQBj
AGsAZQB0ADoADQAKAA0ACgANAAoAIAAgACAAIAAgAGEAKQAgAFIAUgBQACAAcgBvAHUAdABlAHIA
IABSAGUAZwBpAG8AbgBhAGwAIABUAGEAYgBsAGUAIAAoAFIAVAApADoADQAKAA0ACgANAAoAIAAg
ACAAIAAtACAARQBhAGMAaAAgAFIAQgBSACAAYQBuAGQAIABSAFIAIABjAHIAZQBhAHQAZQBzACAA
aQB0AHMAIABvAHcAbgAgAFIAZQBnAGkAbwBuAGEAbAAgAFQAYQBiAGwAZQAgACgAUgBUACkALgAN
AAoAIAAgACAAIAAtACAAVABoAGUAIABSAGUAZwBpAG8AbgBhAGwAIABUAGEAYgBsAGUAIAAoAFIA
VAApACAAaQBzACAAYQBzACAAZgBvAGwAbABvAHcAcwA6AA0ACgANAAoADQAKACAAIAAgACAAIAAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqAA0ACgAgACAAIAAgACAAKgAgAEwAbwBjAGEAbAAgAFIA
TgAgACoAIABSAGUAbQBvAHQAZQAgAFIATgAgACoAIABUAHIAYQBmAGYAaQBjACAAQwBsAGEAcwBz
ACAAKgAgAEwAbwBjAGEAbAAgAFIAUgBQACAAQQBTAE4AIAAqACAAUgBCAFIAIABSAFIAUAAgAEEA
UwBOACAAKgAgAA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAgACAADQAK
ACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAA
KgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqAA0ACgAgACAAIAAgACAAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgANAAoADQAKAA0ACgANAAoADQAKAA0ACgBLAGgAYQBsAGUAZAAg
AE8AbQBhAHIAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABJAG4AdABlAHIAbgBlAHQALQBEAHIA
YQBmAHQAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABbAFAAYQBnAGUAIAAz
AF0ADQAKAA0ACgBSAEYAQwAgACAAIAAgACAAIAAgACAAIAAgACAAIABSAGUAZwBpAG8AbgBhAGwA
IABSAG8AdQB0AGkAbgBnACAAUAByAG8AdABvAGMAbwBsACAAKABSAFIAUAApACAAIAAgACAAIAAg
ACAAIABBAHAAcgBpAGwAIAAyADgALAAgADIAMAAxADcADQAKAA0ACgANAAoADQAKAA0ACgAgACAA
IAAgAGIAKQAgAFIAUgBQACAAcgBvAHUAdABlAHIAIABGAG8AcgB3AGEAcgBkAGkAbgBnACAAVABh
AGIAbABlACAAKABGAFQAKQA6AA0ACgANAAoADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgANAAoAIAAgACAAIAAgACoAIAAgACAATABvAGMAYQBsACAAIAAq
ACAAIAAgAFIAZQBtAG8AdABlACAAIAAqACAAIAAgACAAUgBCAFIAIAAgACAAIAAqACAAIAAgACAA
QgBlAHMAdAAgACAAIAAqACAAIAAgAE8AdQB0AHAAdQB0ACAAIAAgACoAIAAgACAATgBlAHgAdAAt
AGgAbwBwACAAIAAqAA0ACgAgACAAIAAgACAAKgAgACAAUgBSAFAAIABBAFMATgAgACoAIAAgAFIA
UgBQACAAQQBTAE4AIAAgACoAIAAgAFIAUgBQACAAQQBTAE4AIAAgACoAIAAgAEEAUwAgAFAAYQB0
AGgAIAAgACoAIAAgAEkAbgB0AGUAcgBmAGEAYwBlACAAKgAgACAASQBQACAAQQBkAGQAcgBlAHMA
cwAgACoADQAKACAAIAAgACAAIAAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAg
ACAADQAKACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAA
IAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACAAKgAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgANAAoA
IAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqAA0ACgANAAoADQAK
AA0ACgAgACAAIAAgAGMAKQAgAFIAUgBQACAAcgBvAHUAdABlAHIAIABJAEcAUAAgAFIAbwB1AHQA
aQBuAGcAIABUAGEAYgBsAGUAIAAoAEkAUgBUACkAOgANAAoADQAKAA0ACgAgACAAIAAgACAAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoADQAKACAAIAAgACAAIAAqACAAUAByAGUAZgBpAHgAIAAoAFMA
dQBiAG4AZQB0ACkAIAAqACAATQBlAHQAcgBpAGMAIAAqACAATwB1AHQAcAB1AHQAIABJAG4AdABl
AHIAZgBhAGMAZQAgACoAIABOAGUAeAB0AC0AaABvAHAAIABJAFAAIABBAGQAZAByAGUAcwBzACAA
KgAgAA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAIAANAAoAIAAgACAAIAAg
ACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACoA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACoAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgAA0ACgAgACAAIAAgACAAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoADQAKACAAIAAgAA0ACgANAAoADQAKACAAIAAgAC0AIABSAEIAUgAg
AEEAZAB2AGUAcgB0AGkAcwBlAGQAIABNAGUAcwBzAGEAZwBlACAASQBuAGYAbwByAG0AYQB0AGkA
bwBuACAAZgBvAHIAIAB0AGgAZQAgAGwAbwBjAGEAbAAgAHIAZQBnAGkAbwBuACcAcwAgAFIAUgBQ
ACAAQQBTAE4AIABpAHMAIABhAHMAIABmAG8AbABsAG8AdwBzADoADQAKAA0ACgANAAoAIAAgACAA
IAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqAA0ACgAgACAAIAAgACAAKgAgAFIAZQBtAG8AdABlACAAUgBOACAAKgAgAFQAcgBh
AGYAZgBpAGMAIABDAGwAYQBzAHMAIAAqACAATgBvAC4AIABvAGYAIABIAG8AcABzACAAKgAgAFIA
QgBSACAASQBQACAAQQBkAGQAcgBlAHMAcwAgACoAIAANAAoAIAAgACAAIAAgACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACAADQAK
ACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAKgAgAA0ACgAgACAAIAAgACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoADQAKAA0ACgANAAoADQAKACAA
IAAgAC0AIABSAEIAUgAgAEEAZAB2AGUAcgB0AGkAcwBlAGQAIABNAGUAcwBzAGEAZwBlACAASQBu
AGYAbwByAG0AYQB0AGkAbwBuACAAZgBvAHIAIAB0AGgAZQAgAHIAZQBtAG8AdABlACAAcgBlAGcA
aQBvAG4AJwBzACAAUgBCAFIAIABpAHMAIABhAHMAIABmAG8AbABsAG8AdwBzADoADQAKAA0ACgAN
AAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgANAAoAIAAgACAAIAAgACoAIABMAG8AYwBhAGwAIAAqACAAUgBlAG0A
bwB0AGUAIAAqACAAVAByAGEAZgBmAGkAYwAgACoAIABOAHUAbQBiAGUAcgAgACAAKgAgAFQAaQBt
AGUALQBvAHUAdAAgACoAIAAgACAAUgBCAFIAIAAgACAAKgANAAoAIAAgACAAIAAgACoAIAAgAFIA
TgAgACAAIAAqACAAIAAgAFIATgAgACAAIAAqACAAIABDAGwAYQBzAHMAIAAgACoAIABvAGYAIABI
AG8AcABzACAAKgAgACAAVgBhAGwAdQBlACAAIAAgACoAIABSAFIAUAAgAEEAUwBOACAAKgANAAoA
IAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAgAA0ACgAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAgACoAIAAg
ACAAIAAgACAAIAAgACAAIAAgACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
KgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgAA0ACgAgACAAIAAg
ACAAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqAA0ACgANAAoADQAKAA0ACgAtACAAUgBSACAAQQBkAHYAZQByAHQAaQBzAGUAZAAgAE0A
ZQBzAHMAYQBnAGUAIABJAG4AZgBvAHIAbQBhAHQAaQBvAG4AIABpAHMAIABhAHMAIABmAG8AbABs
AG8AdwBzADoADQAKAA0ACgANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqAA0ACgAgACAAIAAgACAAKgAgAEwAbwBjAGEAbAAgACoAIABSAGUA
bQBvAHQAZQAgACoAIAAgAEwAbwBjAGEAbAAgACAAKgAgACAAIABSAEIAUgAgACAAIAAqACAAIAAg
ACAAIABSAFIAIAAgACAAIAAgACoADQAKACAAIAAgACAAIAAqACAAIABSAE4AIAAgACAAKgAgACAA
IABSAE4AIAAgACAAKgAgAFIAUgBQACAAQQBTAE4AIAAqACAAUgBSAFAAIABBAFMATgAgACoAIABJ
AFAAIABBAGQAZAByAGUAcwBzACAAKgANAAoAIAAgACAAIAAgACoAKgAqACoAKgAqACoAKgAqACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACAADQAKACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAA
KgAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAAgACAAIAAqACAAIAAgACAAIAAgACAAIAAg
ACoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKgAgACAAIAAgACAAIAANAAoAIAAgACAAIAAgACoA
KgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAq
ACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqACoAKgAqAA0ACgANAAoADQAKAA0A
CgANAAoASwBoAGEAbABlAGQAIABPAG0AYQByACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAASQBu
AHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAWwBQAGEAZwBlACAANABdAA0ACgANAAoAUgBGAEMAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAUgBlAGcAaQBvAG4AYQBsACAAUgBvAHUAdABpAG4AZwAgAFAAcgBvAHQAbwBjAG8AbAAgACgA
UgBSAFAAKQAgACAAIAAgACAAIAAgACAAQQBwAHIAaQBsACAAMgA4ACwAIAAyADAAMQA3AA0ACgBF
AHgAcABpAHIAZQBzADoAIAAyADcALQAxADAALQAyADAAMQA3AA0ACgANAAoADQAKAA0ACgBTAGUA
YwB1AHIAaQB0AHkAIABDAG8AbgBzAGkAZABlAHIAYQB0AGkAbwBuAHMADQAKAA0ACgANAAoADQAK
AEEAYwBrAG4AbwB3AGwAZQBkAGcAbQBlAG4AdABzAA0ACgANAAoAIAAgACAAVABoAGUAIABhAHUA
dABoAG8AcgBzACAAdwBvAHUAbABkACAAbABpAGsAZQAgAHQAbwAgAHQAaABhAG4AawAgAEIALgAg
AFIAYQB2AGUAZQBuAGQAcgBhAG4AIABmAG8AcgAgAHQAaABlACAAdQBzAGUAZgB1AGwAIABpAG4A
cAB1AHQAcwAgAGEAbgBkAA0ACgAgACAAIABkAGkAcwBjAHUAcwBzAGkAbwBuAHMAIABhAGIAbwB1
AHQAIABSAFIAUAAuAA0ACgANAAoADQAKAEEAdQB0AGgAbwByACAAQQBkAGQAcgBlAHMAcwANAAoA
DQAKACAAIAAgAEsAaABhAGwAZQBkACAATwBtAGEAcgAgAEkAYgByAGEAaABpAG0AIABPAG0AYQBy
AA0ACgAgACAAIABUAGgAZQAgAFIAbwBhAGQADQAKACAAIAAgADYAdABoACAAbwBmACAATwBjAHQA
bwBiAGUAcgAgAEMAaQB0AHkALAAgAEcAaQB6AGEADQAKACAAIAAgAEUAZwB5AHAAdAANAAoADQAK
ACAAIAAgAFAAaABvAG4AZQA6ACAAKwAyACAAMAAxADAAMAAzADYAMgAwADIAOAA0AA0ACgAgACAA
IABFAC0AbQBhAGkAbAA6ACAAZQBuAGcALgBrAGgAYQBsAGUAZAAuAG8AbQBhAHIAQABoAG8AdABt
AGEAaQBsAC4AYwBvAG0ADQAKACAAIAAgAE4AYQB0AGkAbwBuAGEAbAAgAEkARAAgAE4AbwAuADoA
IAAyADgANgAxADEAMgA2ADIAMQAwADIAOQA5ADIADQAKAA0ACgANAAoADQAKAEkAQQBOAEEAIABD
AG8AbgBzAGkAZABlAHIAYQB0AGkAbwBuAHMADQAKAA0ACgANAAoADQAKAA0ACgBSAGUAZgBlAHIA
ZQBuAGMAZQBzAA0ACgANAAoADQAKAA0ACgANAAoARgB1AGwAbAAgAEMAbwBwAHkAcgBpAGcAaAB0
ACAAUwB0AGEAdABlAG0AZQBuAHQADQAKAA0ACgAgACAAIABDAG8AcAB5AHIAaQBnAGgAdAAgACgA
QwApACAASQBFAFQARgAgACgAMgAwADEANgApAC4AIAAgAEEAbABsACAAUgBpAGcAaAB0AHMAIABS
AGUAcwBlAHIAdgBlAGQALgANAAoADQAKACAAIAAgAFQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQA
IABhAG4AZAAgAHQAcgBhAG4AcwBsAGEAdABpAG8AbgBzACAAbwBmACAAaQB0ACAAbQBhAHkAIABi
AGUAIABjAG8AcABpAGUAZAAgAGEAbgBkACAAZgB1AHIAbgBpAHMAaABlAGQAIAB0AG8ADQAKACAA
IAAgAG8AdABoAGUAcgBzACwAIABhAG4AZAAgAGQAZQByAGkAdgBhAHQAaQB2AGUAIAB3AG8AcgBr
AHMAIAB0AGgAYQB0ACAAYwBvAG0AbQBlAG4AdAAgAG8AbgAgAG8AcgAgAG8AdABoAGUAcgB3AGkA
cwBlACAAZQB4AHAAbABhAGkAbgAgAGkAdAANAAoAIAAgACAAbwByACAAYQBzAHMAaQBzAHQAIABp
AG4AIABpAHQAcwAgAGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAgAG0AYQB5ACAAYgBlACAA
cAByAGUAcABhAHIAZQBkACwAIABjAG8AcABpAGUAZAAsACAAcAB1AGIAbABpAHMAaABlAGQADQAK
ACAAIAAgAGEAbgBkACAAZABpAHMAdAByAGkAYgB1AHQAZQBkACwAIABpAG4AIAB3AGgAbwBsAGUA
IABvAHIAIABpAG4AIABwAGEAcgB0ACwAIAB3AGkAdABoAG8AdQB0ACAAcgBlAHMAdAByAGkAYwB0
AGkAbwBuACAAbwBmACAAYQBuAHkADQAKACAAIAAgAGsAaQBuAGQALAAgAHAAcgBvAHYAaQBkAGUA
ZAAgAHQAaABhAHQAIAB0AGgAZQAgAGEAYgBvAHYAZQAgAGMAbwBwAHkAcgBpAGcAaAB0ACAAbgBv
AHQAaQBjAGUAIABhAG4AZAAgAHQAaABpAHMAIABwAGEAcgBhAGcAcgBhAHAAaAAgAGEAcgBlAA0A
CgAgACAAIABpAG4AYwBsAHUAZABlAGQAIABvAG4AIABhAGwAbAAgAHMAdQBjAGgAIABjAG8AcABp
AGUAcwAgAGEAbgBkACAAZABlAHIAaQB2AGEAdABpAHYAZQAgAHcAbwByAGsAcwAuACAAIABIAG8A
dwBlAHYAZQByACwAIAB0AGgAaQBzAA0ACgAgACAAIABkAG8AYwB1AG0AZQBuAHQAIABpAHQAcwBl
AGwAZgAgAG0AYQB5ACAAbgBvAHQAIABiAGUAIABtAG8AZABpAGYAaQBlAGQAIABpAG4AIABhAG4A
eQAgAHcAYQB5ACwAIABzAHUAYwBoACAAYQBzACAAYgB5ACAAcgBlAG0AbwB2AGkAbgBnAA0ACgAg
ACAAIAB0AGgAZQAgAGMAbwBwAHkAcgBpAGcAaAB0ACAAbgBvAHQAaQBjAGUAIABvAHIAIAByAGUA
ZgBlAHIAZQBuAGMAZQBzACwAIABlAHgAYwBlAHAAdAAgAGEAcwAgAG4AZQBlAGQAZQBkACAAZgBv
AHIAIAB0AGgAZQAgAHAAdQByAHAAbwBzAGUAIABvAGYADQAKACAAIAAgAGQAZQB2AGUAbABvAHAA
aQBuAGcAIABJAG4AdABlAHIAbgBlAHQAIABzAHQAYQBuAGQAYQByAGQAcwAgAGkAbgAgAHcAaABp
AGMAaAAgAGMAYQBzAGUAIAB0AGgAZQAgAHAAcgBvAGMAZQBkAHUAcgBlAHMAIABmAG8AcgANAAoA
IAAgACAAYwBvAHAAeQByAGkAZwBoAHQAcwAgAGQAZQBmAGkAbgBlAGQAIABpAG4AIAB0AGgAZQAg
AEkAbgB0AGUAcgBuAGUAdAAgAFMAdABhAG4AZABhAHIAZABzACAAcAByAG8AYwBlAHMAcwAgAG0A
dQBzAHQAIABiAGUADQAKACAAIAAgAGYAbwBsAGwAbwB3AGUAZAAsACAAbwByACAAYQBzACAAcgBl
AHEAdQBpAHIAZQBkACAAdABvACAAdAByAGEAbgBzAGwAYQB0AGUAIABpAHQAIABpAG4AdABvACAA
bABhAG4AZwB1AGEAZwBlAHMAIABvAHQAaABlAHIAIAB0AGgAYQBuAA0ACgAgACAAIABFAG4AZwBs
AGkAcwBoAC4ADQAKAA0ACgAgACAAIABUAGgAZQAgAGwAaQBtAGkAdABlAGQAIABwAGUAcgBtAGkA
cwBzAGkAbwBuAHMAIABnAHIAYQBuAHQAZQBkACAAYQBiAG8AdgBlACAAYQByAGUAIABwAGUAcgBw
AGUAdAB1AGEAbAAgAGEAbgBkACAAdwBpAGwAbAAgAG4AbwB0ACAAYgBlAA0ACgAgACAAIAByAGUA
dgBvAGsAZQBkAC4ADQAKAA0ACgAgACAAIABUAGgAaQBzACAAZABvAGMAdQBtAGUAbgB0ACAAYQBu
AGQAIAB0AGgAZQAgAGkAbgBmAG8AcgBtAGEAdABpAG8AbgAgAGMAbwBuAHQAYQBpAG4AZQBkACAA
aABlAHIAZQBpAG4AIABpAHMAIABwAHIAbwB2AGkAZABlAGQAIABvAG4ADQAKACAAIAAgAFQASABF
ACAASQBOAFQARQBSAE4ARQBUACAARQBOAEcASQBOAEUARQBSAEkATgBHACAAVABBAFMASwAgAEYA
TwBSAEMARQAgAEQASQBTAEMATABBAEkATQBTACAAQQBMAEwAIABXAEEAUgBSAEEATgBUAEkARQBT
ACwADQAKACAAIAAgAEUAWABQAFIARQBTAFMAIABPAFIAIABJAE0AUABMAEkARQBEACwAIABJAE4A
QwBMAFUARABJAE4ARwAgAEIAVQBUACAATgBPAFQAIABMAEkATQBJAFQARQBEACAAVABPACAAQQBO
AFkAIABXAEEAUgBSAEEATgBUAFkAIABUAEgAQQBUAA0ACgAgACAAIABUAEgARQAgAFUAUwBFACAA
TwBGACAAVABIAEUAIABJAE4ARgBPAFIATQBBAFQASQBPAE4AIABIAEUAUgBFAEkATgAgAFcASQBM
AEwAIABOAE8AVAAgAEkATgBGAFIASQBOAEcARQAgAEEATgBZACAAUgBJAEcASABUAFMAIABPAFIA
DQAKACAAIAAgAEEATgBZACAASQBNAFAATABJAEUARAAgAFcAQQBSAFIAQQBOAFQASQBFAFMAIABP
AEYAIABNAEUAUgBDAEgAQQBOAFQAQQBCAEkATABJAFQAWQAgAE8AUgAgAEYASQBUAE4ARQBTAFMA
IABGAE8AUgAgAEEAIABQAEEAUgBUAEkAQwBVAEwAQQBSAA0ACgAgACAAIABQAFUAUgBQAE8AUwBF
AC4ADQAKAA==

--_004_AM4PR0401MB22410362BF8678D2CBD3F9E4BD130AM4PR0401MB2241_--


From nobody Fri Apr 28 08:37:36 2017
Return-Path: <ietf2dave@davearonson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6608F1292FD for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 08:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level: 
X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] 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 bGKB-bNoBqna for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 08:37:33 -0700 (PDT)
Received: from p3plsmtpa09-04.prod.phx3.secureserver.net (p3plsmtpa09-04.prod.phx3.secureserver.net [173.201.193.233]) (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 68DB1129C66 for <ietf@ietf.org>; Fri, 28 Apr 2017 08:34:24 -0700 (PDT)
Received: from mail-lf0-f50.google.com ([209.85.215.50]) by :SMTPAUTH: with SMTP id 47u4dh9LLHPB647u4dUfyD; Fri, 28 Apr 2017 08:33:53 -0700
X-Sender: sender@davearonson.com
Received: by mail-lf0-f50.google.com with SMTP id t144so36019874lff.1 for <ietf@ietf.org>; Fri, 28 Apr 2017 08:33:52 -0700 (PDT)
X-Gm-Message-State: AN3rC/5+ecxqlJEKWbvVr7uc7M+0YuAkv6zPnuFX2yBsgkKgqCaZMNfO 0A3FOl1i9aB+UTvXTFbal8ZPAVQ7+w==
X-Received: by 10.25.202.86 with SMTP id h22mr4116702lfj.139.1493393631789; Fri, 28 Apr 2017 08:33:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.235.138 with HTTP; Fri, 28 Apr 2017 08:33:11 -0700 (PDT)
In-Reply-To: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Dave Aronson <ietf2dave@davearonson.com>
Date: Fri, 28 Apr 2017 11:33:11 -0400
X-Gmail-Original-Message-ID: <CAHxKQijBcBPM3h14XxNUtdTAyiRkiwkRxsHcLTTFVS+WQTWYeA@mail.gmail.com>
Message-ID: <CAHxKQijBcBPM3h14XxNUtdTAyiRkiwkRxsHcLTTFVS+WQTWYeA@mail.gmail.com>
Subject: Re: Regional Routing Protocol (RRP).
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-CMAE-Envelope: MS4wfA2gTpY6YYB9njau5WpPFRrzKIleb3XYCEpMFYObIcW+ODLgx7BVaV0MYmtvBKRjzraArXDAvGAWTOFGn7G/L7vxltYq/usPsZpW7y/0j1agrZGH0Tau swzkpUP0FHTVOKsWMlmldAf4ZIQc8FR9KjYw3rtH5MOHYOy0lSk0BBa76cLjhrEUQpkoww+URlRO+A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3epXLhUOH3iFL4lhiX09qsdghQY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:37:34 -0000

On Fri, Apr 28, 2017 at 11:25 AM, Khaled Omar
<eng.khaled.omar@hotmail.com> wrote:

> please upload the 1st new version with another draft title
> Regional Routing Protocol (RRP)

Awww, I was hoping we could find some reason to just stick a W on the
front.  See https://en.wikipedia.org/wiki/WKRP_in_Cincinnati .  ;-)

-- 
Dave Aronson, consulting software developer of Codosaur.us,
PullRequestRoulette.com, Blog.Codosaur.us, and Dare2XL.com.


From nobody Fri Apr 28 08:48:00 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20761242F7 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 08:47:58 -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, RP_MATCHES_RCVD=-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 2yyhBg4F-Avx for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 08:47:55 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 1A2341275C5 for <ietf@ietf.org>; Fri, 28 Apr 2017 08:44:35 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D3C6E2806B2 for <ietf@ietf.org>; Fri, 28 Apr 2017 17:44:33 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id CEFF62806C0; Fri, 28 Apr 2017 17:44:33 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id C87B62806B2 for <ietf@ietf.org>; Fri, 28 Apr 2017 17:44:33 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C5E10606D941 for <ietf@ietf.org>; Fri, 28 Apr 2017 17:44:33 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id BEBE33FC08; Fri, 28 Apr 2017 17:44:32 +0200 (CEST)
Date: Fri, 28 Apr 2017 17:44:32 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Regional Routing Protocol (RRP).
Message-ID: <20170428154432.o6q753ilzsgbmd4s@nic.fr>
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.9.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.4.28.153316
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nNOQe27Labbc3BdKNLxKgxDlI3s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:47:59 -0000

On Fri, Apr 28, 2017 at 03:25:24PM +0000,
 Khaled Omar <eng.khaled.omar@hotmail.com> wrote 
 a message of 581 lines which said:

> Please don't upload the 2nd version of the KRP ID and please upload
> the 1st new version with another draft title Regional Routing
> Protocol (RRP) discussing the same topic as KRP.

Interesting social experiment, this bot which tries to exercice the
limits of the patience of IETF people. Quite tenacious.


From nobody Fri Apr 28 09:17:25 2017
Return-Path: <barryleiba@computer.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 151FC126BF6; Fri, 28 Apr 2017 09:17:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba <barryleiba@computer.org>
To: <secdir@ietf.org>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: Secdir telechat review of draft-ietf-anima-grasp-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149339623098.2939.15599391351369905104@ietfa.amsl.com>
Date: Fri, 28 Apr 2017 09:17:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dhKu0Lk_Ozy21uah55BNA0DHeNQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 16:17:11 -0000

Reviewer: Barry Leiba
Review result: Ready

My concerns during the last call review of version -09 have been
addressed.  Thanks, Brian, especially for plodding through the "UTF-8"
issues with us!

Barry



From nobody Fri Apr 28 11:44:50 2017
Return-Path: <thomas.watteyne@inria.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76DD128A32 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 11:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.4
X-Spam-Level: 
X-Spam-Status: No, score=-6.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-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 0ZJorrl8qlqd for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 11:44:46 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (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 438D91293E9 for <ietf@ietf.org>; Fri, 28 Apr 2017 11:44:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.37,389,1488841200";  d="scan'208,217";a="221894800"
Received: from mail-vk0-f53.google.com ([209.85.213.53]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 28 Apr 2017 20:44:30 +0200
Received: by mail-vk0-f53.google.com with SMTP id j127so38268082vkh.0 for <ietf@ietf.org>; Fri, 28 Apr 2017 11:44:30 -0700 (PDT)
X-Gm-Message-State: AN3rC/4pF481O2NNoELlgchigeLrYSZqU2b9ie1uG2kuq6Ai7W/zF/C7 ULzyIau0/bj4rrQFh+lQfTKw7dQtBg==
X-Received: by 10.31.142.146 with SMTP id q140mr5519963vkd.131.1493405069210;  Fri, 28 Apr 2017 11:44:29 -0700 (PDT)
MIME-Version: 1.0
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com> <20170428154432.o6q753ilzsgbmd4s@nic.fr>
In-Reply-To: <20170428154432.o6q753ilzsgbmd4s@nic.fr>
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Fri, 28 Apr 2017 18:44:18 +0000
X-Gmail-Original-Message-ID: <CADJ9OA_t0Nzs0MfhcRWLW1zYe+_CerFo0nA_CLpTgvY-=1s3MA@mail.gmail.com>
Message-ID: <CADJ9OA_t0Nzs0MfhcRWLW1zYe+_CerFo0nA_CLpTgvY-=1s3MA@mail.gmail.com>
Subject: Re: Regional Routing Protocol (RRP).
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1142f7f6a800f5054e3e76ff
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/94Nl10gay4DiTJxX1SavWVR1mrY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 18:44:49 -0000

--001a1142f7f6a800f5054e3e76ff
Content-Type: text/plain; charset=UTF-8

+1

On Fri, 28 Apr 2017 at 17:48 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> On Fri, Apr 28, 2017 at 03:25:24PM +0000,
>  Khaled Omar <eng.khaled.omar@hotmail.com> wrote
>  a message of 581 lines which said:
>
> > Please don't upload the 2nd version of the KRP ID and please upload
> > the 1st new version with another draft title Regional Routing
> > Protocol (RRP) discussing the same topic as KRP.
>
> Interesting social experiment, this bot which tries to exercice the
> limits of the patience of IETF people. Quite tenacious.
>
> --
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com
_______________________________________

--001a1142f7f6a800f5054e3e76ff
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>+1</div><div><br><div class=3D"gmail_quote"><div>On Fri, 28 Apr 2017 a=
t 17:48 Stephane Bortzmeyer &lt;<a href=3D"mailto:bortzmeyer@nic.fr">bortzm=
eyer@nic.fr</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 Fri, =
Apr 28, 2017 at 03:25:24PM +0000,<br>
=C2=A0Khaled Omar &lt;<a href=3D"mailto:eng.khaled.omar@hotmail.com" target=
=3D"_blank">eng.khaled.omar@hotmail.com</a>&gt; wrote<br>
=C2=A0a message of 581 lines which said:<br>
<br>
&gt; Please don&#39;t upload the 2nd version of the KRP ID and please uploa=
d<br>
&gt; the 1st new version with another draft title Regional Routing<br>
&gt; Protocol (RRP) discussing the same topic as KRP.<br>
<br>
Interesting social experiment, this bot which tries to exercice the<br>
limits of the patience of IETF people. Quite tenacious.<br>
<br>
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-smartmail=
=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div style=3D"f=
ont-size:small"><font face=3D"monospace, monospace">_______________________=
________________</font></div><div style=3D"font-size:small"><font face=3D"m=
onospace, monospace"><br></font></div><div style=3D"font-size:small"><font =
face=3D"monospace, monospace">Thomas Watteyne, PhD</font></div><div style=
=3D"font-size:small"><font face=3D"monospace, monospace">Research Scientist=
 &amp; Innovator, Inria</font></div><div style=3D"font-size:small"><font fa=
ce=3D"monospace, monospace">Sr Networking Design Eng, Linear Tech</font></d=
iv><div style=3D"font-size:small"><font face=3D"monospace, monospace">Found=
er &amp; co-lead, UC Berkeley OpenWSN</font></div><div style=3D"font-size:s=
mall"><font face=3D"monospace, monospace">Co-chair, IETF 6TiSCH</font></div=
><div style=3D"font-size:small"><font face=3D"monospace, monospace"><br></f=
ont></div><div style=3D"font-size:small"><font face=3D"monospace, monospace=
"><a href=3D"http://www.thomaswatteyne.com" target=3D"_blank">www.thomaswat=
teyne.com</a></font></div><div style=3D"font-size:small"><font face=3D"mono=
space, monospace">_______________________________________</font></div></div=
></div></div></div>

--001a1142f7f6a800f5054e3e76ff--


From nobody Fri Apr 28 14:04:19 2017
Return-Path: <remy.leone@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85183129548 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 14:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 MEsCBW32VeOq for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 14:04:15 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 51D0C129521 for <ietf@ietf.org>; Fri, 28 Apr 2017 14:01:53 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id u70so36739619ywe.2 for <ietf@ietf.org>; Fri, 28 Apr 2017 14:01:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oW34ZFWNlhbJXXRm/uIiLhveMRqujeDFFDWRJS/dn3A=; b=Mv9F5DGTFV4Cq6QEgI8xQOC0Dc/rMoIjn684ao8P+QU7miaUR6cpZGk64D2/lYpygB Pg/nuAnoVemykYk514U2wTxjrLtrfpX70R/Yac6mZ/AzTUmvJWEmftna3bq1zkZi1Rl/ SD2egMtUw4CpOi7tDgrUIxziS1RzEB58bcvM+AuzQYHB8glXwT9QkRyRbyzcIwd3krS8 outj8ys0dD+sIdnUxVTwiL+XbrrOF0oWfHWO79Ys0o8x/W5S6ZlhxVm3x2W6O9BRU5PM vExxHDJ/ZC0r12dmSRt0QfqVyOaftnU1oS9gfvWeIX68/K8iFGbwno4dvZ4vr0jRypUw SUmA==
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=oW34ZFWNlhbJXXRm/uIiLhveMRqujeDFFDWRJS/dn3A=; b=MKvdk9bD/2Ozx0tWww7gCl7Dl1YytaM5zoC75kZ4yKgndvo+REUNfBNI/4kTZMU6cB OQpsPBZoeXvMHLSt8iNX7bLneYoeBpdVxtlcUAGKkhrRXT84aBYV1ZpmyV4rOLoLcqkd ZYs/wNvLy8GwlhPDNfZZxptJcwpMoXwB2/gh00JcE3upOvuHkV8dvG4mZofL3JXpmqtg lTQ+fV2HZG4Y2XTRxOZv/TCw1Eeln4UjOahJXqPpOFywt6CbPUAXcvgYIVa1hZRtumE/ UpABa64vGvEcGB6tNJG1ehYYa3YRtNZmhZ9gurIjmYztJDmtE/LxAnniObeIHXAJshIG LZCw==
X-Gm-Message-State: AN3rC/457Uk1EjF1Bbe2i4cPT1aN6lPGN8y4L5+iO0XDAMk55ckjrNr0 x++DgcCnL7/4PCX23a04VORbOzoi0Bzj
X-Received: by 10.129.116.133 with SMTP id p127mr6332130ywc.0.1493413312409; Fri, 28 Apr 2017 14:01:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.50.199 with HTTP; Fri, 28 Apr 2017 14:01:51 -0700 (PDT)
Received: by 10.129.50.199 with HTTP; Fri, 28 Apr 2017 14:01:51 -0700 (PDT)
In-Reply-To: <CADJ9OA_t0Nzs0MfhcRWLW1zYe+_CerFo0nA_CLpTgvY-=1s3MA@mail.gmail.com>
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com> <20170428154432.o6q753ilzsgbmd4s@nic.fr> <CADJ9OA_t0Nzs0MfhcRWLW1zYe+_CerFo0nA_CLpTgvY-=1s3MA@mail.gmail.com>
From: "Remy 'Sieben' Leone" <remy.leone@gmail.com>
Date: Fri, 28 Apr 2017 23:01:51 +0200
Message-ID: <CAHCejjXDkDhF3=B_hsBj_4wy03N=MDYT6PFquKRy=sF-FOHu-A@mail.gmail.com>
Subject: Re: Regional Routing Protocol (RRP).
To: Thomas Watteyne <thomas.watteyne@inria.fr>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1147e57efd5642054e4061d1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MXX_mmAGRBECmi1jz0_7hQ6GgX8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 21:04:17 -0000

--001a1147e57efd5642054e4061d1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yes we should invite this bot to a dinner. Wednesday evening. We would
present it to a couple of friends that are very interested in this kind of
ideas.

Remy < world class maybe world champion >

Le 28 avr. 2017 20:45, "Thomas Watteyne" <thomas.watteyne@inria.fr> a
=C3=A9crit :

> +1
>
> On Fri, 28 Apr 2017 at 17:48 Stephane Bortzmeyer <bortzmeyer@nic.fr>
> wrote:
>
>> On Fri, Apr 28, 2017 at 03:25:24PM +0000,
>>  Khaled Omar <eng.khaled.omar@hotmail.com> wrote
>>  a message of 581 lines which said:
>>
>> > Please don't upload the 2nd version of the KRP ID and please upload
>> > the 1st new version with another draft title Regional Routing
>> > Protocol (RRP) discussing the same topic as KRP.
>>
>> Interesting social experiment, this bot which tries to exercice the
>> limits of the patience of IETF people. Quite tenacious.
>>
>> --
> _______________________________________
>
> Thomas Watteyne, PhD
> Research Scientist & Innovator, Inria
> Sr Networking Design Eng, Linear Tech
> Founder & co-lead, UC Berkeley OpenWSN
> Co-chair, IETF 6TiSCH
>
> www.thomaswatteyne.com
> _______________________________________
>

--001a1147e57efd5642054e4061d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Yes we should invite this bot to a dinner. Wednesday even=
ing. We would present it to a couple of friends that are very interested in=
 this kind of ideas.<div dir=3D"auto"><br></div><div dir=3D"auto">Remy &lt;=
 world class maybe world champion &gt;</div></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">Le=C2=A028 avr. 2017 20:45, &quot;Thomas W=
atteyne&quot; &lt;<a href=3D"mailto:thomas.watteyne@inria.fr">thomas.wattey=
ne@inria.fr</a>&gt; a =C3=A9crit=C2=A0:<br type=3D"attribution"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div>+1</div><div><br><div class=3D"gmail_quote"><div>O=
n Fri, 28 Apr 2017 at 17:48 Stephane Bortzmeyer &lt;<a href=3D"mailto:bortz=
meyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</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 Fri, Apr 28, 2017 at 03:25:24PM +0000,<br>
=C2=A0Khaled Omar &lt;<a href=3D"mailto:eng.khaled.omar@hotmail.com" target=
=3D"_blank">eng.khaled.omar@hotmail.com</a>&gt; wrote<br>
=C2=A0a message of 581 lines which said:<br>
<br>
&gt; Please don&#39;t upload the 2nd version of the KRP ID and please uploa=
d<br>
&gt; the 1st new version with another draft title Regional Routing<br>
&gt; Protocol (RRP) discussing the same topic as KRP.<br>
<br>
Interesting social experiment, this bot which tries to exercice the<br>
limits of the patience of IETF people. Quite tenacious.<br>
<br>
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-smartmail=
=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div style=3D"f=
ont-size:small"><font face=3D"monospace, monospace">_______________________=
_______<wbr>_________</font></div><div style=3D"font-size:small"><font face=
=3D"monospace, monospace"><br></font></div><div style=3D"font-size:small"><=
font face=3D"monospace, monospace">Thomas Watteyne, PhD</font></div><div st=
yle=3D"font-size:small"><font face=3D"monospace, monospace">Research Scient=
ist &amp; Innovator, Inria</font></div><div style=3D"font-size:small"><font=
 face=3D"monospace, monospace">Sr Networking Design Eng, Linear Tech</font>=
</div><div style=3D"font-size:small"><font face=3D"monospace, monospace">Fo=
under &amp; co-lead, UC Berkeley OpenWSN</font></div><div style=3D"font-siz=
e:small"><font face=3D"monospace, monospace">Co-chair, IETF 6TiSCH</font></=
div><div style=3D"font-size:small"><font face=3D"monospace, monospace"><br>=
</font></div><div style=3D"font-size:small"><font face=3D"monospace, monosp=
ace"><a href=3D"http://www.thomaswatteyne.com" target=3D"_blank">www.thomas=
watteyne.com</a></font></div><div style=3D"font-size:small"><font face=3D"m=
onospace, monospace">______________________________<wbr>_________</font></d=
iv></div></div></div></div>
</blockquote></div></div>

--001a1147e57efd5642054e4061d1--


From nobody Fri Apr 28 15:02:04 2017
Return-Path: <prvs=1291aa3ee1=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1FBB129B01 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 15:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPq2jqGb-SCy for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 15:02:01 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3AE7129AF4 for <ietf@ietf.org>; Fri, 28 Apr 2017 14:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1493416760; x=1494021560; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=H1IcQ9EQQ5A45F7Z2fhUfr3Ul L5514KotL1UaEVK6S4=; b=g0NfQxORM+O18hbrEAibTpiqycaySfieSVJ/0jNN9 vTyrfB5C9i5kla+j+DMWd6NOBbKDYAkknN3demmJE8Y1PnaFFzdzLay1x07kXGwY bp57r2z14PrUygq/m8a5nG3E2VvA/mlirkQQgyt7jjRYXZrsNPO9aEy50ktdKr02 6U=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=GY/K+5Q8JLYGAfYixUMcuIklLs+sFOzpuOvXFjiRN5wRT9kA0DfvuKClP18M N+2yoJLs5oFY1YVnKvalzG9BBGLigJlFoprL7MKIxANA1gQX9pKJITGU+ Uz8Kskt5wHwrfnOmWBPyKPhxKawpZHRQCYcDc28iAWKuOr72wEhzYI=;
X-MDAV-Processed: mail.consulintel.es, Fri, 28 Apr 2017 23:59:20 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 28 Apr 2017 23:59:19 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005417022.msg for <ietf@ietf.org>; Fri, 28 Apr 2017 23:59:18 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170428:md50005417022::04OX8U9XLgZOPoqE:0000551g
X-Return-Path: prvs=1291aa3ee1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Fri, 28 Apr 2017 23:59:16 +0200
Subject: Re: Regional Routing Protocol (RRP).
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <eng.khaled.omar@hotmail.com>, IETF Secretariat <ietf-secretariat@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <300BF5D5-0850-4324-8BC1-B5B721A9EE63@consulintel.es>
Thread-Topic: Regional Routing Protocol (RRP).
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wy39T74zquhZBKUUQx9SzhvNcic>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 22:02:03 -0000

Dear Khaled,

Speaking as sergeant-at-arms.

You=E2=80=99ve been warned way too many times about making sure to follow R=
FC3005, and you keep ignoring very basic rules, not reading all the documen=
ts to understand better the process, and keep posting about documents in th=
e general discussion mailing list instead of the specific WG/area, or even =
copying the list about your decisions to upload or not your IDs, which are =
meant only for the submission process.

According to that and in my position of sergeant-at-arms under the RFC3005,=
 I=E2=80=99ve no other way that request the secretariat to immediately rest=
rict your posting rights for an initial period of 30 days.

Hopefully in that period you are able to invest some time to read about the=
 process and not insist in this behavior, as otherwise a new posting rights=
 restrictions will be for a much longer term.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Khaled Omar <eng.khaled.omar@=
hotmail.com>
Responder a: <eng.khaled.omar@hotmail.com>
Fecha: viernes, 28 de abril de 2017, 17:25
Para: "ietf-draft-submission@ietf.org" <ietf-draft-submission@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: Regional Routing Protocol (RRP).

    Hi Jasmine,
    =20
    Please don=E2=80=99t upload the 2nd version of the KRP ID and please up=
load the 1st new version with another draft title Regional Routing Protocol=
 (RRP) discussing the same topic as KRP.
    =20
    Best Regards,
    =20
    Khaled Omar=20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Fri Apr 28 15:43:18 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C8F12945F for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 15:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=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 xG4w7njRc9bZ for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 15:43:16 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-oln040092064088.outbound.protection.outlook.com [40.92.64.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD2C61293E1 for <ietf@ietf.org>; Fri, 28 Apr 2017 15:40:31 -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; bh=jufWEulmnhnJQnHjdhD3bV3as9rmRQHHtTnt4aq5Kz0=; b=MqSTSC2bUTIRXcww9UfbHWjflOMoESr1UmMrkkm8ZXB+eyU4dk6Yg2xmbVEfehZtFFXVnL47cJTtblrk1e6lA6GKni2pFbm5jv0AkwBDfF2NhroPwmMNuXcmAiklwxmbJ8xZdkE1mtQozhudxa7cFMYiZQ6884sf6vFfExRAXfxpZUzMKZxUrpEupGz+VDwj9Y0aLT7Fbixc/r4pE2nqS3517QghlB6XUpXl5dN9bMEcgH3k5wp6v1IHW2m/YdgbVyXvPvCRZtgoQw/DZGhjtZN/7YIAFrnGHeaPQf3USjISh279S7GERjvhXFr1ebLSvLhxufEDzHvXJK13ezZybA==
Received: from VE1EUR01FT019.eop-EUR01.prod.protection.outlook.com (10.152.2.59) by VE1EUR01HT060.eop-EUR01.prod.protection.outlook.com (10.152.3.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 22:40:29 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.2.51) by VE1EUR01FT019.mail.protection.outlook.com (10.152.2.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 22:40:29 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 22:40:29 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: IETF official decisions.
Thread-Topic: IETF official decisions.
Thread-Index: AQHSwHBvzN/P7I/CwEWZK4cZLsGesA==
Date: Fri, 28 Apr 2017 22:40:29 +0000
Message-ID: <AM4PR0401MB2241A3520DA19576FA0787D4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:A60FD9F61E97CA892343D17EA35AC7A908DD61FDCBDEA536CCA81082E461BD7E; UpperCasedChecksum:BD8BBBF5907CF437C9E5348EA191A0E8DAE8F9AEED24E34700C92AD18E8A0058; SizeAsReceived:7732; Count:37
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT060; 5:18gzxlapR7HrIVtppYNWKATSdRt2hTJOeaa/zDuHk3J1xMMibOKLVmkh7z4FPEsR5kNFMX66PLktfprfQxYbEh2jKFJ/0Pd/H3ZoB91nLuNJ3x+loYsrKQidEzTdHktxMaWprl0PhmvBTZCbKIaU+Q==; 24:GjGn3GTWcG0rt1pG9EikUMqHLN258BUD5kMx93MUBTeOpU/OB2t3LkW50pxjn7CGnMg0GhNYcevfVG1YHpE0tNsTrcRZ0X28HFrDqBXf54E=; 7:fpuNWOgaSZSgF80vVZwZVI2G6m11Ccie0hFyq2lH27K+/jrYwTSyFHw3LrrPCL5mQ0ymZc7MydsO1YUSEpDHocd/YsyVwsl4l79cfltYdrgM//woDKNpNKJ54ch6M5JVqv3z2XqBF714O49uhL/E+jENnN5FvL+RFPZWYb8iL2vWizcOFHAmBlmUdLN+oJ06KQ8u71f5Z2nGWTp1IgJN0Nj5TkP4g5cTgAdVcvd9Jk3NdXbLKpOwBTiZM+6Vqrk9fKWwdrAqB0zdCofiIIRNuqydjF764H4zI3Dsaa4fXxCyKSVzMFONDppTl/3VZ+7g
x-incomingheadercount: 37
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT060; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 00bb13ad-13f1-4482-a653-08d48e8791c3
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:VE1EUR01HT060; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT060; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT060; 
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <28A22C7D9FF6DF489A816E5B6F775A55@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 22:40:29.1947 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT060
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L1_WnhKz4SK_ip1pCWSqckGozxQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 22:43:17 -0000

RGVhciBhbGwsIAoKVGhlIGRyYWZ0cyBhcmUgc3VibWl0dGVkIGluZGl2aWR1YWxseSwgSSBzaG91
bGQgZmluZCByZXNwb25zZXMgZnJvbSBBcmVhIERpcmVjdG9ycyBvciBDaGFpcnMgd2hvIHRoaW5r
IHRoYXQgbXkgZHJhZnRzIGZpdHMgd2l0aCB0aGVpciBmb2N1c2VkIHdvcmssIHRha2luZyB0aGVt
IHNlcmlvdXNseSwgd2UgYXJlIG5vdCBzb2xkaWVycyB0byB3YWl0IGZvciBvcmRlcnMsIG1hbnkg
c29sdXRpb25zIGV4aXN0cyB0byB0YWtlIGRyYWZ0cyBmb3J3YXJkLCB0aGUgbWlzc2luZyB0aGlu
ZyBpcyBvZmZpY2lhbCBkZWNpc2lvbnMgb3IgaXQgd2lsbCBiZSBiZXR0ZXIgZm9yIG1lIHRvIHN0
b3Agc3VibWl0dGluZyBuZXcgZHJhZnRzIGlmIHRoZXkgd2lsbCBiZSB1c2VsZXNzLCBJIHNob3Vs
ZG4ndCBrZWVwIHNheWluZyB0aGF0IGJ1dCB3b3JraW5nIGFsb25lIGlzIG5vdCBhIGdvb2QgcHJh
Y3RpY2UuCgpSZWdhcmRzLAoKCktoYWxlZCBPbWFy


From nobody Sat Apr 29 00:50:05 2017
Return-Path: <marius.georgescu@rcs-rds.ro>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D604129B5A; Sat, 29 Apr 2017 00:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RP_MATCHES_RCVD=-0.001, 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=rcs-rds.ro
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 9XS4QChOOzzf; Sat, 29 Apr 2017 00:49:41 -0700 (PDT)
Received: from mailproxy5.rcs-rds.ro (mailproxy5.rcs-rds.ro [212.54.124.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44AC5129568; Sat, 29 Apr 2017 00:47:22 -0700 (PDT)
Received: from [10.252.6.123] (unknown [10.252.6.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailproxy5.rcs-rds.ro (Postfix) with ESMTPSA id F0E262836A1; Sat, 29 Apr 2017 10:47:18 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rcs-rds.ro; s=MailProxy; t=1493452039; bh=Zb8otDAsXI/AYQAqTa++lYnEj6tDRePlfRNT1gEps+E=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=aY0Um0bFsdNK2zVbOn4Q7zu+/6QtbUWypmp/mUcvcIrgdWiMK4WNzel9YF6zE2j4u KYXd8B7K+DLjRemnhVImorOVYi6SD1UZlXe38DJfZxjikFPvvcMd2K1hHBUNfH0wAv rcUklW2plV3m7Hi6CkwwEY+KSvxPc/wTUsJtAc4w=
Subject: Re: Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
References: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Cc: draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
From: Marius Georgescu <marius.georgescu@rcs-rds.ro>
Message-ID: <303391a2-84f1-31dc-1b67-e3cc8b0aea3c@rcs-rds.ro>
Date: Sat, 29 Apr 2017 10:52:23 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ifg53vLxtpGibvepk0HLYzgIPa0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 07:49:44 -0000

Hello Robert,

Thank you very much for your detailed review.

We have revised the draft according to your comments.

The result was uploaded as:

https://tools.ietf.org/html/draft-ietf-bmwg-ipv6-tran-tech-benchmarking-07

Please find inline a punctual overview of the changes.

On 4/26/2017 7:05 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> Review result: Ready with Issues
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
> Reviewer: Robert Sparks
> Review Date: 2017-04-26
> IETF LC End Date: 2017-05-02
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Essentially Ready for publication as an Informational RFC,
> but with some minor issues to address before publication
>
> This document is (with exceptions noted below) straightforward and
> easy to follow
>
> Minor Issues:
>
> Section 8 is very confusing - I suspect it has been made so by
> removing things that were in it earlier. Right now it claims to
> provide additional tests, but the only content is about testing things
> with firewalls, along with a statement that this document is only
> targeting network devices that do not have a firewall function. I
> think you can keep most of the text here (except the statement that
> you aren't talking about things with firewalls) and remove the
> confusion by changing the section heading to something like "Tests in
> the presence of a firewall function".
- we have removed the second paragraph , which was indeed confusing.
The point, which may be clearer in Section 1.1 is that we need
additional benchmarks for stateful IPv6 transition technologies,
which may be (or not) labeled as having a firewall function.  
> It's unclear how to apply the formula in Section 10.2.1 to the results
> that come out of, say, Section 7.3.2, where you are reporting a
> (minimum, median, maximum) tuple. Some discussion about the
> applicability of the tests where you recommend against reporting a
> single number to the methods in this section would help.
+ we added a note in the reporting format part stating: "

*In the case of benchmarks for which more than one value is reported
(e.g. IPDV Section 7.3.2), a column for each of the values SHOULD be
included.*

"
>  It would also
> help to point out that the Xpd result can be go negative (it will go
> negative for things that become smaller as the number of flows
> increase, and positive for things that get bigger). If I read this
> correctly, if throughput (for example) goes to 0 as n increases, Xpd
> will go to -100%. Similary if latency doubles as n increases, Xpd will
> go to +100% (and will go to +200% if latency triples).
+ This was one of the important points which needed clarification. Thank
you for pointing it out.
In order to keep the  performance degradation results in the Lower is
better  direction, we proposed a secondary calculation formula for
higher is better benchmarks (e.g. Throughput). This makes, in our
opinion, the results easier to interpret.

> Nits:
>
> There are several places where you point to Section 6 where I think
> you meant to point to Section 7. See the Procedure: line in 10.2.1 for
> an example. Also make sure 9 is correct where you say "Sections 6
> through 9" in section 12.
+Corrected
>
> Please double-check that you meant "larger MTU" in the last paragraph
> of 5.1. It might be correct, but I find the paragraph confusing.
We find this part to be correct. However, keeping only the 1280 +
overhead recommendation might make it less confusing.
Do you think that would be a viable solution?
> In 8.1 you meant to point to 5.2, not 5.3
>
> Please try to simplify this sentence: 
>   "The duration of each trial SHOULD be at least 60 seconds to reduce
> the potential gain of a DNS64 server, which is able to exhibit higher
> performance by storing the requests and thus utilizing also the
> timeout time for answering them."
+corrected
>
> (Style comment - please feel free to ignore): Consider deleting "as
> well" everywhere it occurs in the document - most of the places it is
> used, the sentence works just as well, and sometimes better, without
> it.
+corrected
> Typos:
> end of section 5.1.1: Appendix A1 should be Appendix A
+corrected

Best regards,
Marius


From nobody Sat Apr 29 14:04:14 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7EA21294B5 for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 14:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[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 kksNNhBY5GNz for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 14:04:11 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::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 5B0E7129494 for <ietf@ietf.org>; Sat, 29 Apr 2017 14:01:51 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id y4so24657646pge.0 for <ietf@ietf.org>; Sat, 29 Apr 2017 14:01:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=HFQVMVRDsY3f8vsZLnxtwVSYNqauPKUeFEDZKduAt0E=; b=eVoCLlpTftIltIfn6pEY55NeYzPqhet1yP0HVOiR7hoTRdiRGmToXIqntqxkhB0Mdu 2MuLiSO9oXWn6bj1h4mzxLH36bTXTWNPrtOcDu99tiXbuAdCzlpXRhWosjBWLjdAy0Dr GmviaTJMCFvdNNwqYDZ+GR3OIDW7XLXczzxOYeHasT8LnfXg3ZdX+8k9lJg6qf6WfK4E SRBQVtqOqyYRPHfvzjZalOlLKH3zHnQOYEcpSLTTYKXIFgql0EXVZrk9UhzDK4bow8J6 fDxB4U3UnhVHybJkt0Gtiqko8eDQEojhJ/i+9Dczs3R/qBB2wjlW83HJW7kb3PoJcq1y muUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=HFQVMVRDsY3f8vsZLnxtwVSYNqauPKUeFEDZKduAt0E=; b=brBiPKvpgd1pvOnh8Nph4HGhyo5OovaQVvkaNkHUxoI+0KoflRluv7Tsc5FriOWFN1 A/I9fi1iK7HbohLUS0i61Xt2ZlDqf8zW6wlmx2XmzGU8KURFOusVoqPK1Ey2ZmZEPBU9 iPdj0+ztpHOKO7pp+dDULx04PRUYtdtvjB9OLHjrH5FStW0oF14r7VdJjXaecZzfOxZ6 QM71ocygdxME6s4nk3O9f28p1xdDlnZ71bvb7pMgLzf1DUG9EOi+lMEfBRSQAVsNQMsN b0KJV1wJ8D/0xgw/utWEHc00gDRsVYSgIRV+kPZ114ZZdhJtDt7yX7aotV6/GvYS7L4+ yD0Q==
X-Gm-Message-State: AN3rC/5gAbZT2t/PIVX+UYHqfxNGExIrQUzkG0BcRCUnH/QejoKEmibF vbB8NrUn6e5BXY3O
X-Received: by 10.99.172.84 with SMTP id z20mr347683pgn.12.1493499710700; Sat, 29 Apr 2017 14:01:50 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.125.144]) by smtp.gmail.com with ESMTPSA id g89sm17827962pfk.25.2017.04.29.14.01.49 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Apr 2017 14:01:50 -0700 (PDT)
To: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Real DMARC damage
Organization: University of Auckland
Message-ID: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
Date: Sun, 30 Apr 2017 09:01:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e5gGDL_Edsb00roNvZP5G40PIMo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 21:04:13 -0000

Am I the only IETF list admin who's had to deal with genuine DMARC damage today?

gen-art@ietf.org had four subscriptions suspended for excessive bounces, all caused
by mail from one participant whose sending domain has published a p=reject policy

Bizarrely, one of the subscriptions disabled was @gmane.org. It's a very strange
choice for them to respect p=reject.

Regards
   Brian Carpenter



From nobody Sat Apr 29 17:06:03 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C87129467 for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 17:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 yAM7k-cCz-KY for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 17:06:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 768C012948D for <ietf@ietf.org>; Sat, 29 Apr 2017 17:04:14 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d4cLU-000475-8N; Sun, 30 Apr 2017 00:04:12 +0000
Date: Sun, 30 Apr 2017 09:04:10 +0900
Message-ID: <m2r30a4v7p.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
Subject: Re: Real DMARC damage
In-Reply-To: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fy9R_IlReIT7L1kFFwXhLGU9_u0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 00:06:02 -0000

> Am I the only IETF list admin who's had to deal with genuine DMARC
> damage today?

when it first came out, a japanese friend took us to the new godzilla
movie.  i had never been to one before.

in a sense, it is not actually about a monster, but rather cultural and
governmental paralysis in dealing with a complex unexpected disaster; a
parable about the bureaucracy's inability to make useful decisions and
actions on how to deal with the aftermath of the tohoku quake.


From nobody Sat Apr 29 18:15:15 2017
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4112612946B for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 18:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 6-zEQ43QKsvh for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 18:15:12 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 5BE9F1296B0 for <ietf@ietf.org>; Sat, 29 Apr 2017 18:13:13 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id g60so73393312qtd.3 for <ietf@ietf.org>; Sat, 29 Apr 2017 18:13:13 -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 :content-transfer-encoding:message-id:references:to; bh=8AvpUsMZhoFvB63UEZUPkL/u9ANvKfEVYAEfa6TnvSQ=; b=m7yHtib1NGNIe26N+ZsEjc6WYMAf/0NbJbJTNb3PMdlwEwmPOAGKbU1hFEWvA65DJz SzrSOsU+y8YQvf0UVq9mQ1jD6XQ3ZGP7h6ywdPjkBN5518dcDKUDbxG7dNii+0KRedbG pasYHqK37nWxEEsqTPK6IfUDAPza3oYhziFFUZatkv6PJBsnogjCeYDqgA1/aFbaq6dJ Sm+6LHBRg+fA5r9zkVqt13u84qHDMM3+ELCTFZKd2aUIzkpFa870SbqJt+KoUR7cAsrU THym26DlV6v65j68SkqJIDW8GjImMYKLS6PWxoYLYciCTBfa1Gnw5+MDefRAfVdpCnZY UYaQ==
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 :content-transfer-encoding:message-id:references:to; bh=8AvpUsMZhoFvB63UEZUPkL/u9ANvKfEVYAEfa6TnvSQ=; b=arKpVjVXXsTJjxhBAfDypVbodCmCmjCsNsR2TS8p89OQoVp6kTqFC/4LkXIDjYxi6P mCFgmrZtEhAMnqfPXaRIFMOXIDXeelToYNjlxlj0vivDgd5kfLnjbcv3iMmBAfto0j4u SutdGHuUexDzR9WNRCV83scH7nNbk7AVPn94isbuflUzZY7TjbOEeMVUetwmFHj0a6Cm okn7ewtC+t0VkUYDjGq7pFVaur8Xb3TtV5p2SvCKHyAlSxXgwEqYpMfhJm6/6QMDmYN3 nXQtxxtZXu6Mxfd+0HMbQNSlci3Kl9y1vUiy7QNlZ/JYOFcdrffjO3EIiznscInz4XIN 3bLw==
X-Gm-Message-State: AN3rC/7SpzJxGXoUJCEd/8ephLxosPB/z+bN9h0LkARFNjpPhWdqCsN5 pj5s3XuPmnQj5Q==
X-Received: by 10.237.62.46 with SMTP id l43mr15540561qtf.88.1493514792392; Sat, 29 Apr 2017 18:13:12 -0700 (PDT)
Received: from [192.168.1.13] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id m188sm6915333qke.48.2017.04.29.18.13.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Apr 2017 18:13:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Real DMARC damage
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
Date: Sat, 29 Apr 2017 21:13:10 -0400
Cc: IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8BB5A45-1326-48EB-A281-5B1E66198C9D@gmail.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WAc-InBxPfuvKrz-dr-IRFt16qM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 01:15:14 -0000

Sent from my iPhone

> On Apr 29, 2017, at 5:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m> wrote:
>=20
> Am I the only IETF list admin who's had to deal with genuine DMARC damage t=
oday?

No, we had one on the SecDir list as well.

Kathleen=20
>=20
> gen-art@ietf.org had four subscriptions suspended for excessive bounces, a=
ll caused
> by mail from one participant whose sending domain has published a p=3Dreje=
ct policy
>=20
> Bizarrely, one of the subscriptions disabled was @gmane.org. It's a very s=
trange
> choice for them to respect p=3Dreject.
>=20
> Regards
>   Brian Carpenter
>=20
>=20


From nobody Sat Apr 29 19:13:00 2017
Return-Path: <blong@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0701127333 for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 19:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.802
X-Spam-Level: 
X-Spam-Status: No, score=-0.802 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=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 0EKuhJN17qN4 for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 19:12:57 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 DED87129406 for <ietf@ietf.org>; Sat, 29 Apr 2017 19:10:53 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id w10so4333574oif.0 for <ietf@ietf.org>; Sat, 29 Apr 2017 19:10:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KJsLk8ZXN3cqsDFpn20tFUtoSVVYZtUousx/xangVn4=; b=FY/kUD4l7FZRenLtOD/OiTpjfvsbr6rHlZqhe742WGY8ii/Frk7OzhvjzDmq/rAqv/ /GGw8/Sl+zMpdJpjP/aLKADCrsN2k5ZdP4aYOoIYSv0FuRz+hnXPw4Eq4V7hihH9q40h xhN8I6Ii7JYCe+iX65yzdQr27MOaX0u7sK5WTmBwyNohzb4kOJY8G/V92USxLOpQVg3E B87tlDqmCxuMYaeLsuwCIleGTtwap7NypSX2hEcXGIuzJwtWpF6rDw7h2oovWm8jUNo8 ZFj9seMQdzulZzDAS4Zpzh+f8RqAFrDMp/EP81gm91T8dSs5w2vw3HNzR40hMF48h5eQ decg==
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=KJsLk8ZXN3cqsDFpn20tFUtoSVVYZtUousx/xangVn4=; b=LHwBWDtM91uJs79Snd3uwAvQYRiZeVxMP0252n04LmysK07HIybm0bq5UzE7PDjiME zbXNf7KBcHSiGcayZwn1ltZY6WvM4U6PFrPNxmy2lJS/cE5BZEUGsEG1f4DW+x/PnpPr Z+2is+iFNhNzk2zp8S6oj/2wxaYoJVUS/XInAbbYF0G92NJIkQe4zEx63aXTEcjBh3VO DVfQ6gEj1pFuOaCS+p05Kx0TDmyu2C58xG48D3MWk9a8JScqSvd/YaI08Ql+jcyGjxSz vubUHjiA4CW6JAhfB59BMVyIZqZC1anfXiNo/Q1yb7PTrFYBd+gx/NqOMstMiHzEdfEt 7BqA==
X-Gm-Message-State: AN3rC/7sBOev3rGT9nPv64ypwvS67E35tIFgnoG3Hpi+nmP1iK+3cRpb W4VwlQnXZ+LRaIq5xXsHzSpgQ42MD2n+
X-Received: by 10.202.204.197 with SMTP id c188mr369634oig.194.1493518252793;  Sat, 29 Apr 2017 19:10:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.8.101 with HTTP; Sat, 29 Apr 2017 19:10:52 -0700 (PDT)
Received: by 10.182.8.101 with HTTP; Sat, 29 Apr 2017 19:10:52 -0700 (PDT)
In-Reply-To: <E8BB5A45-1326-48EB-A281-5B1E66198C9D@gmail.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com> <E8BB5A45-1326-48EB-A281-5B1E66198C9D@gmail.com>
From: Brandon Long <blong@google.com>
Date: Sat, 29 Apr 2017 19:10:52 -0700
Message-ID: <CABa8R6u=FRm=+Y8Pht8yrU60xAQhPAzpzAep=iT3iB9nTJWENA@mail.gmail.com>
Subject: Re: Real DMARC damage
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c17710ecd614054e58d011
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dzG5AcxI2ONj0UhcTaEqiRxh14E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 02:12:59 -0000

--001a11c17710ecd614054e58d011
Content-Type: text/plain; charset=UTF-8

It sounds like there would be benefit to fixing the mailman to not consider
policy bounces as unsub worthy, at least.

On Apr 29, 2017 6:15 PM, "Kathleen Moriarty" <
kathleen.moriarty.ietf@gmail.com> wrote:

>
>
> Sent from my iPhone
>
> > On Apr 29, 2017, at 5:01 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> >
> > Am I the only IETF list admin who's had to deal with genuine DMARC
> damage today?
>
> No, we had one on the SecDir list as well.
>
> Kathleen
> >
> > gen-art@ietf.org had four subscriptions suspended for excessive
> bounces, all caused
> > by mail from one participant whose sending domain has published a
> p=reject policy
> >
> > Bizarrely, one of the subscriptions disabled was @gmane.org. It's a
> very strange
> > choice for them to respect p=reject.
> >
> > Regards
> >   Brian Carpenter
> >
> >
>
>

--001a11c17710ecd614054e58d011
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">It sounds like there would be benefit to fixing the mailm=
an to not consider policy bounces as unsub worthy, at least.</div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Apr 29, 2017 6:15 PM, &=
quot;Kathleen Moriarty&quot; &lt;<a href=3D"mailto:kathleen.moriarty.ietf@g=
mail.com">kathleen.moriarty.ietf@gmail.com</a>&gt; wrote:<br type=3D"attrib=
ution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><br>
<br>
Sent from my iPhone<br>
<br>
&gt; On Apr 29, 2017, at 5:01 PM, Brian E Carpenter &lt;<a href=3D"mailto:b=
rian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Am I the only IETF list admin who&#39;s had to deal with genuine DMARC=
 damage today?<br>
<br>
No, we had one on the SecDir list as well.<br>
<br>
Kathleen<br>
&gt;<br>
&gt; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a> had four subs=
criptions suspended for excessive bounces, all caused<br>
&gt; by mail from one participant whose sending domain has published a p=3D=
reject policy<br>
&gt;<br>
&gt; Bizarrely, one of the subscriptions disabled was @<a href=3D"http://gm=
ane.org" rel=3D"noreferrer" target=3D"_blank">gmane.org</a>. It&#39;s a ver=
y strange<br>
&gt; choice for them to respect p=3Dreject.<br>
&gt;<br>
&gt; Regards<br>
&gt;=C2=A0 =C2=A0Brian Carpenter<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div></div>

--001a11c17710ecd614054e58d011--


From nobody Sat Apr 29 20:24:09 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59A91293F9 for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 20:24:07 -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 dxteHIh0DHQS for <ietf@ietfa.amsl.com>; Sat, 29 Apr 2017 20:24:06 -0700 (PDT)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::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 17179129454 for <ietf@ietf.org>; Sat, 29 Apr 2017 20:22:12 -0700 (PDT)
Received: by mail-pf0-x244.google.com with SMTP id b23so7435002pfc.0 for <ietf@ietf.org>; Sat, 29 Apr 2017 20:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=pxo67aFN9pSkycpM6TDrZ+bvQVnZ6ZBuPWUVQevO1+k=; b=g5w7o8np9zVhFGoLbNAqF0l+xW2g7B66jAXIUakFdCoUi7nHpdai6SpHeWq2LpUEJy nGMEYWTMfaMEqMzOfZYfH5g+JE40JYp/7z4KffeaE4EfF9izpywjDwRllBsQHNpVUMKo jfWBFOfSDB14ICZv1XgIDatrckKbLwU4dbqGUpppF90WyOiBnISS0WFq0qr2XIV759MP ftYcH4Qt9rPc02Q62cse256+Pgz5ZUkN9aIDLbw/rsCA3F2iCgOsdCmHu6kl7F8Z06zn tl4AWYg3/uqQKQLMxg+NSBGeCWUIJLU3015hFshF4WbDKJk+sTORxxbxcbTBEhNGtaHE 4FTw==
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:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=pxo67aFN9pSkycpM6TDrZ+bvQVnZ6ZBuPWUVQevO1+k=; b=Vesldk0AMKIbegoBuSa6oZPDZhXsAJfA4m6WCHHI/qurn1OmLmqi8PL/O6KVpDLdEf 0w1zCwmGVFZ2t3nbD4CdSts1kG4KkT0own158X6JeqiKLL3ScP1ehCfVELfIa1xEFQu/ 804Bye/vW491mOR1UMdrUzdZAf/tg3IbwlgRHbrHxpFyuNeXQapSiluWGmA2dpRWRs+i 2v7Q4GtX7JMmJeTLz7veQx3ZupF/6BNM2v2/yJeFOt6XhIxA/F1sSS1BrwM0UQyKh/Oj EkW+nG9Yrha1ITb6ZAJGZ92cUtpHMgICA4oLOB12Oa+3KukMXNG6skmipbJ92XmpSj2q yWmA==
X-Gm-Message-State: AN3rC/5XAdXB5+JLTedXicxy+1u5bEvQHaZ5kj4TUIG5cXzzXEMbzUpA f9WiU271dmAAxw==
X-Received: by 10.98.68.8 with SMTP id r8mr20518973pfa.168.1493522531735; Sat, 29 Apr 2017 20:22:11 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.125.144]) by smtp.gmail.com with ESMTPSA id b8sm21908479pgn.51.2017.04.29.20.22.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Apr 2017 20:22:11 -0700 (PDT)
Subject: Re: Real DMARC damage
To: Brandon Long <blong@google.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com> <E8BB5A45-1326-48EB-A281-5B1E66198C9D@gmail.com> <CABa8R6u=FRm=+Y8Pht8yrU60xAQhPAzpzAep=iT3iB9nTJWENA@mail.gmail.com>
Cc: IETF <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5db55c92-0e17-2da7-118f-daceae2732f9@gmail.com>
Date: Sun, 30 Apr 2017 15:22:06 +1200
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: <CABa8R6u=FRm=+Y8Pht8yrU60xAQhPAzpzAep=iT3iB9nTJWENA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ga9fK2lV-C2rCwqvPuqRXkFX-DY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 03:24:08 -0000

On 30/04/2017 14:10, Brandon Long wrote:
> It sounds like there would be benefit to fixing the mailman to not consider
> policy bounces as unsub worthy, at least.

Possibly. For now I've increased the bounce threshold on the list, but
that is hardly a solution. (It isn't an unsub, just delivery suspension,
but that's still a problem for all concerned - sender, subscriber, and
list admin.)

    Brian

> 
> On Apr 29, 2017 6:15 PM, "Kathleen Moriarty" <
> kathleen.moriarty.ietf@gmail.com> wrote:
> 
>>
>>
>> Sent from my iPhone
>>
>>> On Apr 29, 2017, at 5:01 PM, Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>>
>>> Am I the only IETF list admin who's had to deal with genuine DMARC
>> damage today?
>>
>> No, we had one on the SecDir list as well.
>>
>> Kathleen
>>>
>>> gen-art@ietf.org had four subscriptions suspended for excessive
>> bounces, all caused
>>> by mail from one participant whose sending domain has published a
>> p=reject policy
>>>
>>> Bizarrely, one of the subscriptions disabled was @gmane.org. It's a
>> very strange
>>> choice for them to respect p=reject.
>>>
>>> Regards
>>>   Brian Carpenter
>>>
>>>
>>
>>
> 


From nobody Sat Apr 29 21:27:05 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D408012420B; Sat, 29 Apr 2017 21:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-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 Smy9Vbl3vhCc; Sat, 29 Apr 2017 21:26:52 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73CC61292D3; Sat, 29 Apr 2017 21:24:41 -0700 (PDT)
Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A9DF229CA6F; Sun, 30 Apr 2017 13:24:39 +0900 (JST)
Received: by mail-oi0-f48.google.com with SMTP id x184so62464533oia.1; Sat, 29 Apr 2017 21:24:39 -0700 (PDT)
X-Gm-Message-State: AN3rC/4S76KihGisreuTUda46+/nmDsyZ+fOmaHMXgHkrb1wmykvWYxA HEyCq0PMAfUS5IBnuPIG5G+NO2p0SA==
X-Received: by 10.157.2.101 with SMTP id 92mr7246001otb.211.1493526278364; Sat, 29 Apr 2017 21:24:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Sat, 29 Apr 2017 21:24:37 -0700 (PDT)
In-Reply-To: <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Sat, 29 Apr 2017 21:24:37 -0700
X-Gmail-Original-Message-ID: <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
Message-ID: <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Brian Raymor <Brian.Raymor@microsoft.com>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c03918c48e9d8054e5aaf1a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mRGlKf3BBlhmobMfropaquMg74w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 04:26:56 -0000

--94eb2c03918c48e9d8054e5aaf1a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,
As far as I've read -08 draft, I think this point has not been addressed
yet. I hope some folks could elaborate a bit more if they think this is not
an important point for the draft.
--
Yoshi

On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <Brian.Raymor@microsoft.com>
wrote:

> I think that I understand your perceptions better. Prior to adoption of
> coap-tcp-tls and before I was active in the WG, I recall discussions
> related to the confusion over application vs transport reliability in CoA=
P
> especially as related to CON and NON. What was intended?
>
>
>
> Tim Carey outlined some concerns in:
>
> https://tools.ietf.org/html/draft-carey-core-std-msg-vs-tran
> s-adapt-00#section-2
>
>
>
> This topic was presented in detail at IETF 93 -
> https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf -
> starting on slide 23.
>
>
>
> And in a related thread on the mailing list back in 2015 -
> https://www.ietf.org/mail-archive/web/core/current/msg06280.html -
> Carsten responded:
>
>
>
> > In any case, CON and NON are about message layer semantics, not about
> application semantics
>
> > -- you gave them a meaning they don't have.
>
>
>
> By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the Con=
fusion
> around              CON/NON was resolved=E2=80=9D.
>
>
>
> Where relevant, I=E2=80=99ve added clarifications - such as the Appendix =
related
> to differences in Observe for reliable transports.
>
>
>
> Both Carsten and Hannes could probably offer more context if needed.
>
>
>
> *From:* Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
> *Sent:* Friday, April 21, 2017 2:08 PM
> *To:* Brian Raymor <Brian.Raymor@microsoft.com>
> *Cc:* Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org;
> draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
> *Subject:* Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
>
>
>
> Hi Brian,
>
>
>
> Just in case,
>
> Reliable transports only provide reliability at transport level. It
> doesn't provide reliability in application protocol level.
>
>
>
> RFC7252 has reliability mechanisms in it since it uses UDP. This means it
> has abilities to check both transport and app level reliability.
>
> This draft only provides transport level reliability and apps will need t=
o
> detect app protocol failure by themselves.
>
> This means 7252 and this draft are not totally equivalent from the
> viewpoint of applications.
>
>
>
> I am not saying this is wrong or bad, but I believe app developer should
> aware this point.
>
> --
>
> Yoshi
>
>
>
> On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <Brian.Raymor@microsoft.co=
m>
> wrote:
>
> Hi Yoshi,
>
>
>
> > OK. I also think we should state that the protocol should notify the
> failure events to applications.
>
> > Since errors can happen not only in TCP, but also TLS and websocket
> level, mentioning only TCP close or reset might not
>
> > be enough.
>
>
>
> After reviewing with the authors, an additional clarification was appende=
d
> to 3.4 Connection Health - https://github.com/core-wg/coa
> p-tcp-tls/pull/140/files
>
>
>
> The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -
> https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is that
> RFC6455 covers the WebSocket case and does not need to be repeated here.
>
>
>
> > When we use 7252, I think applications basically don't need to implemen=
t
> timeouts or retry mechanisms as the protocol
>
> > provides such things.
>
>
>
> RFC7252 provides timeouts and retries because it's implementing a TCP-lik=
e
> reliability mechanism over UDP - https://tools.ietf.org/html/rf
> c7252#section-2.1
>
>
>
> > However, when we use this one, it seems applications will need to have
> such mechanisms. Isn't it a bit confusing? I am thinking that
>
> > there need to be some guidance here.
>
> > BTW, PONG is one example.
>
>
>
> For coap-tcp-tls, there are multiple early implementations. This has neve=
r
> been reported as a source of confusion.
>
>
>
> >> My sense is that we should treat this as an update to RFC7959 based on
> the original language:
>
> > I don't have a strong opinion here. Updating 7959 is fine for me if it'=
s
> clearer to CoAP people.
>
>
>
> I've merged the change - https://github.com/core-wg/coa
> p-tcp-tls/pull/138/files
>
>
>
> Thanks again for helping us to improve the quality of the draft,
>
>
>
> =E2=80=A6Brian
>
>
>

--94eb2c03918c48e9d8054e5aaf1a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div>As far as I&#39;ve read -08 draft, I think this=
 point has not been addressed yet. I hope some folks could elaborate a bit =
more if they think this is not an important point for the draft.</div><div>=
--</div><div>Yoshi</div><div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian.=
Raymor@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-185370657942848524m_7105224061284585916m_-1893619406420712=
677WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">I think that I understand your perceptions better. =
Prior to adoption of coap-tcp-tls and before I was active in the WG, I reca=
ll discussions related to the confusion over application
 vs transport reliability in CoAP especially as related to CON and NON. Wha=
t was intended?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Tim Carey outlined some concerns in:<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><a href=3D"https://tools.ietf.org/html/draft-carey-=
core-std-msg-vs-trans-adapt-00#section-2" target=3D"_blank">https://tools.i=
etf.org/html/dr<wbr>aft-carey-core-std-msg-vs-tran<wbr>s-adapt-00#section-2=
</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This topic was presented in detail at IETF 93 -
<a href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf"=
 target=3D"_blank">https://www.ietf.org/proceedin<wbr>gs/93/slides/slides-9=
3-core-0.<wbr>pdf</a> - starting on slide 23.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">And in a related thread on the mailing list back in=
 2015 -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html=
" target=3D"_blank">https://www.ietf.org/mail-arch<wbr>ive/web/core/current=
/msg06280.<wbr>html</a> - Carsten responded:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; In any case, CON and NON are about message lay=
er semantics, not about application semantics<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; -- you gave them a meaning they don&#39;t have=
.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">By IETF 94, the authors were reporting =E2=80=93 =
=E2=80=9CMost of the Confusion around=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 CON/NON was resolved=E2=80=9D.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Where relevant, I=E2=80=99ve added clarifications -=
 such as the Appendix related to differences in Observe for reliable transp=
orts.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Both Carsten and Hannes could probably offer more c=
ontext if needed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-185370657942848524_m_71052240612845859=
16_m_-1893619406420712677__MailEndCompose"><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></a>=
</p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Yoshifumi Nishida [mailto:<a h=
ref=3D"mailto:nishida@sfc.wide.ad.jp" target=3D"_blank">nishida@sfc.wide.ad=
.jp</a><wbr>]
<br>
<b>Sent:</b> Friday, April 21, 2017 2:08 PM<br>
<b>To:</b> Brian Raymor &lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" t=
arget=3D"_blank">Brian.Raymor@microsoft.com</a>&gt;<br>
<b>Cc:</b> Yoshifumi Nishida &lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" =
target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt;; <a href=3D"mailto:tsv-art=
@ietf.org" target=3D"_blank">tsv-art@ietf.org</a>; <a href=3D"mailto:draft-=
ietf-core-coap-tcp-tls@ietf.org" target=3D"_blank">draft-ietf-core-coap-tcp=
-tls@i<wbr>etf.org</a>; <a href=3D"mailto:core@ietf.org" target=3D"_blank">=
core@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@=
ietf.org</a><br>
<b>Subject:</b> Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-0<wbr>7<=
u></u><u></u></span></p><div><div class=3D"m_-185370657942848524m_710522406=
1284585916h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Hi Brian,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Just in case,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Reliable transports only provide reliability at tran=
sport level. It doesn&#39;t provide reliability in application protocol lev=
el.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">RFC7252 has reliability mechanisms in it since it us=
es UDP. This means it has abilities to check both transport and app level r=
eliability.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This draft only provides transport level reliability=
 and apps will need to detect app protocol failure by themselves.=C2=A0<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This means 7252 and this draft are not totally equiv=
alent from the viewpoint of applications.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I am not saying this is wrong or bad, but I believe =
app developer should aware this point.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Yoshi<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor &lt;<=
a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian.Raymor=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">Hi Yoshi,<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; OK. I also think we should s=
tate that the protocol should notify the failure events to applications.=C2=
=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; Since errors can happen not =
only in TCP, but also TLS and websocket level, mentioning only TCP close or=
 reset might not
<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; be enough.<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">After reviewing with the authors,=
 an additional clarification was appended to 3.4 Connection Health -
<a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files" target=
=3D"_blank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/140/files</a><u></u><u></=
u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">The opinion of the authors (and G=
engyu WEI=E2=80=99s recent response -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html=
" target=3D"_blank">
https://www.ietf.org/mail-arch<wbr>ive/web/core/current/msg08622.<wbr>html<=
/a>) is that RFC6455 covers the WebSocket case and does not need to be repe=
ated here.<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; When we use 7252, I think ap=
plications basically don&#39;t need to implement timeouts or retry mechanis=
ms as the protocol<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; provides such things. <u></u=
><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">RFC7252 provides timeouts and ret=
ries because it&#39;s implementing a TCP-like reliability mechanism over UD=
P -
<a href=3D"https://tools.ietf.org/html/rfc7252#section-2.1" target=3D"_blan=
k">https://tools.ietf.org/html/rf<wbr>c7252#section-2.1</a><u></u><u></u></=
p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; However, when we use this on=
e, it seems applications will need to have such mechanisms. Isn&#39;t it a =
bit confusing? I am thinking that<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; there need to be some guidan=
ce here.<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; BTW, PONG is one example.<u>=
</u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">For coap-tcp-tls, there are multi=
ple early implementations. This has never been reported as a source of conf=
usion.
<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt;&gt; My sense is that we shou=
ld treat this as an update to RFC7959 based on the original language:<u></u=
><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">&gt; I don&#39;t have a strong op=
inion here. Updating 7959 is fine for me if it&#39;s clearer to CoAP people=
.<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">I&#39;ve merged the change - <a h=
ref=3D"https://github.com/core-wg/coap-tcp-tls/pull/138/files" target=3D"_b=
lank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/138/files</a><u></u><u></=
u></p>
<p class=3D"m_-185370657942848524m_7105224061284585916m_-189361940642071267=
7gmail-m-3058448815637676647msoplaintext">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Thanks again for helping us to improve the quality =
of the draft,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=C2=A0</span><span style=3D"color:#88=
8888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=E2=80=A6Brian</span><span style=3D"c=
olor:#888888"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

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

--94eb2c03918c48e9d8054e5aaf1a--


From nobody Sun Apr 30 00:59:38 2017
Return-Path: <buhrmi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2904112951E for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 00:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6S5REUwyVNu9 for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 00:59:32 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::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 A9E86128656 for <ietf@ietf.org>; Sun, 30 Apr 2017 00:57:56 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id u65so70392904wmu.1 for <ietf@ietf.org>; Sun, 30 Apr 2017 00:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=UiW3hTFgTQmpptJYcVaC7tqnTSEvqU54fKRazBgjRMA=; b=bzuB6+y2jnAgHHwDPZ/k8bHiz6MouLP22iqbBPzBlSnvqL9axV37FJZeRk20PtYydb /znCA+ZpRCZEx/Pwf1x6lhQFfE4N0PugtRGmrEhnU5RiepOH1Vpx8CLJ7Z7Fcv5dk5Fa LLgKtlaraSn2P9ty19mUyyWhNsKFfPyawv6Vl/riOtDBDPI0cHCZx9ovTPAOEeLPZTBz vCVXQ7/QT2e4F/0u6L9UFrQ67KoQSnOW2LDEFjqIP9fdgzgs9M/i4Rj5//0CCL+mwq74 Noxxi7K9uxXz9mUnYuAEPX6zFzGqRd5eI2R1l1RBWi4j+tyuarN2HbQwZgi7Z0EyL1nP U5JA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UiW3hTFgTQmpptJYcVaC7tqnTSEvqU54fKRazBgjRMA=; b=n61ure1Ep1kLsZYBpWCW8HMaGcygLglvExDiOdMkwhFG51f/cxNcKqFe9n5URrnLSj J8/2J8uZ+Jei/JF+x/WZYrtc/EN7qCIvMNIaNmGYyDmPL/mtdK/q/OxZfkQlznrwwTiG 2YE6XQK6rxVjLbCB+w07rD81+N926Fz8CiMmX8SnNE7G3GqgNsCiFuBXSpcks69dJCYt 5FcnYabXVcNl4LrzHiro1xbIiMANQR2G48ryjaB02X5fAR/S58njFw+tFfFYW6ZDw6Jn 1vHM2MArDk1AD0+7hcO+hOIfPwUhbwna+3eyw5RxiDtP4PYLtMV9RJMaCjZPlETtHRKI v/oA==
X-Gm-Message-State: AN3rC/4XxGxOKdljffczg6XK/9tvbXnwH7okZcoLV4jSJ1bSQkdKN35+ PqsSaqwU9jWKxKxSahmN/YS6ElT5SE5p
X-Received: by 10.28.133.70 with SMTP id h67mr3024461wmd.136.1493539074981; Sun, 30 Apr 2017 00:57:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.216.75 with HTTP; Sun, 30 Apr 2017 00:57:24 -0700 (PDT)
From: Stefan Buhrmester <buhrmi@gmail.com>
Date: Sun, 30 Apr 2017 16:57:24 +0900
Message-ID: <CANhkrbSg=RMed86CBzBZfK2n8side50diz8POqZLvjbb=yPoLg@mail.gmail.com>
Subject: IPv6 subnet assignments
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114431f805c513054e5daaa5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZQ_Cpg06olaxVDiesadhTkVzgQE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 07:59:35 -0000

--001a114431f805c513054e5daaa5
Content-Type: text/plain; charset=UTF-8

Hello IETF,

I'm new here :)

Just a quick question. I'd like to have a small public IPv6 subnet
statically assigned to me and my company in a specific geographic location
located in Germany without the risk of it being re-assigned to another
location/company/person/etc. in the future by a third-party without
explicit agreement.

Latitude: 52.353628
Longitude: 8.717088

What's the correct point-of-contact for this sort of request? Do I have to
ask the IANA? I would like to act as my own ISP as much as possible.

Cheers,
Stefan

--001a114431f805c513054e5daaa5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello IETF,<div><br></div><div>I&#39;m new here :)</div><d=
iv><br></div><div>Just a quick question. I&#39;d like to have a small publi=
c IPv6 subnet statically assigned to me and my company in a specific geogra=
phic location located in Germany without the risk of it being re-assigned t=
o another location/company/person/etc. in the future by a third-party witho=
ut explicit agreement.</div><div><br></div><div>Latitude:=C2=A052.353628</d=
iv><div>Longitude:=C2=A08.717088</div><div><br></div><div>What&#39;s the co=
rrect point-of-contact for this sort of request? Do I have to ask the IANA?=
 I would like to act as my own ISP as much as possible.</div><div><br></div=
><div>Cheers,</div><div>Stefan</div></div>

--001a114431f805c513054e5daaa5--


From nobody Sun Apr 30 01:11:05 2017
Return-Path: <prvs=12937288d6=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4251293EE for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 01:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcXFU_222IU7 for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 01:11:01 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 541C31294D8 for <ietf@ietf.org>; Sun, 30 Apr 2017 01:09:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1493539764; x=1494144564; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=UDGQfTydrcqN0gN5859nmPp9G 4AJ1/eQydsq/UmYypI=; b=M7GDq93f//JNQjGYnUkOfnPvlyTcvSlovp8dhi6LN ilhX1fHmeRnOCYDSKw346oYKYfw/e+0YjngD6TsX8oGEkstapxjkxyEY5zf0xDzS 1mfNchNIKyDdtSuQZgehqoUhx2czAPkkhLnq6i1pTSJ7q+8sOhgUG89+3L5+60xA Ic=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=QvAidunfjIzI6S+DcRcqqchup6ipFqhQBmpDlLpXEaGciilqoektORC7mOce Xot5M26niUJXiv3iPtd8ztZncV1ffEnFZOwSq82fYCfa3NfKZ14lLiFkV UBwlvr6gPf3nxTaDR81y4QeX1VXMEgkGzsc6gd4QAK696C69hbiYes=;
X-MDAV-Processed: mail.consulintel.es, Sun, 30 Apr 2017 10:09:24 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 30 Apr 2017 10:09:24 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005417926.msg for <ietf@ietf.org>; Sun, 30 Apr 2017 10:09:23 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170430:md50005417926::acXGr163Zdd0KN5K:00005BAu
X-Return-Path: prvs=12937288d6=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Sun, 30 Apr 2017 10:09:20 +0200
Subject: Re: IPv6 subnet assignments
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <buhrmi@gmail.com>, <ietf@ietf.org>
Message-ID: <A32A869D-E9AE-4DE4-A1BB-82C907E9F29C@consulintel.es>
Thread-Topic: IPv6 subnet assignments
References: <CANhkrbSg=RMed86CBzBZfK2n8side50diz8POqZLvjbb=yPoLg@mail.gmail.com>
In-Reply-To: <CANhkrbSg=RMed86CBzBZfK2n8side50diz8POqZLvjbb=yPoLg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W0R9bpuxdBtR2xDEJ-UteBbdiGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 08:11:04 -0000

Hi Stefan,

For Germany, definitively is RIPE the organization you should contact.

Regards,
Jordi
 

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Stefan Buhrmester <buhrmi@gmail.com>
Responder a: <buhrmi@gmail.com>
Fecha: domingo, 30 de abril de 2017, 9:57
Para: <ietf@ietf.org>
Asunto: IPv6 subnet assignments

    Hello IETF,
    I'm new here :)
    
    Just a quick question. I'd like to have a small public IPv6 subnet statically assigned to me and my company in a specific geographic location located in Germany without the risk of it being re-assigned to another location/company/person/etc. in the future by a third-party without explicit agreement.
    
    Latitude: 52.353628
    Longitude: 8.717088
    
    What's the correct point-of-contact for this sort of request? Do I have to ask the IANA? I would like to act as my own ISP as much as possible.
    
    Cheers,
    Stefan
    
    



**********************************************
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 use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From nobody Sun Apr 30 02:25:51 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313AF129486 for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 02:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 opqVEaVvMN_k for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 02:25:48 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 8C8B9129544 for <ietf@ietf.org>; Sun, 30 Apr 2017 02:24:01 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d4l5D-000813-2A; Sun, 30 Apr 2017 09:23:59 +0000
Date: Sun, 30 Apr 2017 18:23:57 +0900
Message-ID: <m2lgqi45aq.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stefan Buhrmester <buhrmi@gmail.com>
Cc: ietf@ietf.org
Subject: Re: IPv6 subnet assignments
In-Reply-To: <CANhkrbSg=RMed86CBzBZfK2n8side50diz8POqZLvjbb=yPoLg@mail.gmail.com>
References: <CANhkrbSg=RMed86CBzBZfK2n8side50diz8POqZLvjbb=yPoLg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RqWqG8WflKUZSBhhHZ21Hwf2kXs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 09:25:50 -0000

> Just a quick question. I'd like to have a small public IPv6 subnet
> statically assigned to me and my company in a specific geographic location
> located in Germany without the risk of it being re-assigned to another
> location/company/person/etc. in the future by a third-party without
> explicit agreement.

https://www.ripe.net/manage-ips-and-asns/resource-management/number-resources


From nobody Sun Apr 30 15:21:11 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9EA129535 for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 15:21:10 -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_50=0.8, RCVD_IN_DNSWL_MED=-2.3, 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 usheh0LQzJho for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 15:21:08 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A796E12954D for <ietf@ietf.org>; Sun, 30 Apr 2017 15:19:02 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v3UMIqTX021328 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Apr 2017 23:18:52 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <590662CB.3050706@foobar.org>
Date: Sun, 30 Apr 2017 23:18:51 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.12 (Macintosh/20170323)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: Real DMARC damage
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
In-Reply-To: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WK3yVoGvjXgJpVcAL9b9IpedvXo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 22:21:10 -0000

Brian E Carpenter wrote:
> Bizarrely, one of the subscriptions disabled was @gmane.org. It's a very strange
> choice for them to respect p=reject.

gmane has been having existential problems over the past while - limited
details on http://home.gmane.org.

Nick


From nobody Sun Apr 30 18:18:39 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8D7129ADD; Sun, 30 Apr 2017 18:18:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: Genart telechat review of draft-ietf-anima-grasp-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149360151701.9927.14136920563894865857@ietfa.amsl.com>
Date: Sun, 30 Apr 2017 18:18:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jnsrRmSwvPTz9FSYS7mKLb-M8J4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 01:18:37 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-anima-grasp-??
Reviewer: Joel Halpern
Review Date: 2017-04-30
IETF LC End Date: 2017-03-02
IESG Telechat date: 2017-05-11

Summary: This document is ready to be Proposed Standard
    The changes in revisions 10 and 11 address all of the concerns in
my review of revision 09

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Sun Apr 30 19:44:46 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0D3127241; Sun, 30 Apr 2017 19:44:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
Subject: Genart telechat review of draft-ietf-dnsop-nsec-aggressiveuse-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149360667193.9876.7534874775326889081@ietfa.amsl.com>
Date: Sun, 30 Apr 2017 19:44:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B4sn6HoA_g1WUqyZdJ_bld7pE_s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 02:44:32 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dnsop-nsec-aggressiveuse-09
Reviewer: Joel Halpern
Review Date: 2017-04-30
IETF LC End Date: 2017-03-27
IESG Telechat date: 2017-05-25

Summary: This document is almost ready for publication as a Proposed
Standard RFC

Major issues:
    Procedural - ID Nits notes that there are normative references to
RFCs 7129 and 7719.  Those are informational RFCs.  The shepherd
writeup does not note these downrefs.  (I see this was also noted by
Jouni Korhonen, but I do not see a resolution.)

Minor issues:

Nits/editorial comments: 



From nobody Sun Apr 30 19:45:47 2017
Return-Path: <shtsuchi@arista.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDFB1293E8 for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 19:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=arista.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 8bY82g0aPUMK for <ietf@ietfa.amsl.com>; Sun, 30 Apr 2017 19:45:43 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 975BC129AD3 for <ietf@ietf.org>; Sun, 30 Apr 2017 19:42:57 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id q66so26043042pfi.3 for <ietf@ietf.org>; Sun, 30 Apr 2017 19:42:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=google;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Lq2Mt3idyszs0LlFmVkIDFfkvP5t2sTKGwMw7IN4FCw=; b=Q/T35NFXRO0ZUvmjtvhwsM0TWj6oOVkgz3Y6WJ1vgBb6DiLvv2/hI8+sA+XnSoVduA 0ue8Hxxzr6l6K3ZS55yEuJN+Llf+IOJYpcBPbsnFXBCgqgPwf4HVHR+5ZwKt31TSR6gu 8uHusziOdHbRE4QnRNpe4Btg3V484xvWB4dcA=
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Lq2Mt3idyszs0LlFmVkIDFfkvP5t2sTKGwMw7IN4FCw=; b=oPfjSRfVKalDZsM9L+Wgd2+P57iUD+4Nsw4dfbJLENEnBkBcZa7XGAWCgeZY/VnFDn +744l511MOSv4j2pQiTqORwFpqSaFRv/GfcePLBAV8921NMohtQ/bKUvlDJWt5SbcDnw hTmSpjYTa+uMFBGQyfN20xYiMpe32mKg5LbulEkYxK10OOwxvmhcPpXz7b9oh3oGzY5F AH5JRioqETk9Ht/hL8X2qDclTO10njl3FXwGjF6vrYQDvnHvJX0YFjwsqOOCYcxYOzja +rdVTEacAaxGCPeSmYsDPyqIyKtf6DU5Evh8VBEaJbJEmDjvGVhCG2AjP5v4qx28HGRg LnOg==
X-Gm-Message-State: AN3rC/4BdANJra1Sv4Lv/ThE9ufMtGxvlQH+tTSkTmntXifhQt/Cd6bW 1yH1tY46rE0u9gXe
X-Received: by 10.99.121.67 with SMTP id u64mr24701761pgc.230.1493606577062; Sun, 30 Apr 2017 19:42:57 -0700 (PDT)
Received: from [192.168.71.251] ([203.215.128.252]) by smtp.gmail.com with ESMTPSA id l22sm22122369pfi.2.2017.04.30.19.42.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Apr 2017 19:42:56 -0700 (PDT)
Subject: Re: Real DMARC damage
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
From: Shishio Tsuchiya <shtsuchi@arista.com>
Message-ID: <cc4712b9-5922-2d1f-6c30-8add4ab60382@arista.com>
Date: Mon, 1 May 2017 11:42:54 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eTiDlwYSqob76oNzRBlcdh94VH4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 02:45:45 -0000

As far as I know,
google.com
microsoft.com
yahoo.com
aol.com
are already p=reject

arista.com is p=quarantine.

I think google.com is one of great contributor of ietf mailing list but 
sometimes old mailing list suspect the mail as spam .
I recovered some mail from my spam folder.
I hope the mailman update to new one.
https://wiki.list.org/DEV/DMARC

Does this mail also suspect spam?

Regards,
-Shishio


On 2017/04/30 6:01, Brian E Carpenter wrote:
> Am I the only IETF list admin who's had to deal with genuine DMARC damage today?
>
> gen-art@ietf.org had four subscriptions suspended for excessive bounces, all caused
> by mail from one participant whose sending domain has published a p=reject policy
>
> Bizarrely, one of the subscriptions disabled was @gmane.org. It's a very strange
> choice for them to respect p=reject.
>
> Regards
>    Brian Carpenter
>
>
>


From nobody Sun Apr 30 20:47:41 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2CE12945D; Sun, 30 Apr 2017 20:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 4xf9LVLu82TR; Sun, 30 Apr 2017 20:47:28 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 92260129AF2; Sun, 30 Apr 2017 20:45:23 -0700 (PDT)
Received: from [192.168.3.100] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id BBD5822E253; Sun, 30 Apr 2017 23:45:16 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Comments on draft-mm-wg-effect-encrypt-11
Message-Id: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
Date: Mon, 1 May 2017 13:45:13 +1000
Cc: IETF Discussion Mailing List <ietf@ietf.org>
To: IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R590PNM2Sn9pinf9wEO6A0IGFlw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 03:47:32 -0000

Sorry for the late review; on the plus side, I'm coming to it with fresh =
eyes.

Overall, this document reads as if it was originally written to =
highlight the downsides of increased use of encryption, and then =
rewritten to be more neutral in tone. Unfortunately, some of the =
original intent posited there still seeps through.

In doing so, it often fails to convey that there are any options other =
than "this has to be done by the network." I know that this has been =
cast as a survey of potential impacts, and therefore doesn't necessary =
need to enumerate alternatives, but the way that it's written could =
easily lead a reader to think that there aren't alternatives. It also is =
odd that alternatives are not enumerated when they're often well-known, =
and the really interesting issues are in the tradeoffs between doing =
something in the network (i.e., as a third party) vs. by one of the =
endpoints (a first party to communication) or their delegates.

For example, Section 2.2 talks about the importance of passive =
monitoring for traffic surveys, but fails to discuss alternative means =
of gathering data (e.g., anonymised data from content providers; =
telemetry from client implementations) that are superior in some ways, =
limited in others. It would be a useful contribution to characterise the =
tradeoffs here, so this is an opportunity lost.

Section 2.3.2.1 points out that "Web proxies are widely used", but fails =
to note that the vast bulk of caching is done by endpoints -- browsers, =
CDNs and reverse proxies, thereby sidestepping the issues of encryption =
(although they have their own unique challenges). Discussing why this =
form of caching has become prevalent might help inform network operators =
as to why getting the economics and trust relationships of =
intermediation right is important.

Section 2.3.2.2 motivates DPI as "Input for Differential Treatment", but =
fails to note the developing efforts to coordinate client and server =
behaviour to adapt to network conditions, without the need for stripping =
encryption.

Section 2.4 talks about need for compression proxies, but fails to note =
the deployment of them in overlay networks (e.g., by Google Chrome, =
UCBrowser, Opera Mini, etc.). There is a minefield of issues surrounding =
them, of course, but it's useful context.

Section 2.5.2 does note that endpoint-based alternatives might be =
possible, but fizzles out after that. Exploring why they haven't =
developed would be a substantial contribution.

A few additional points:

* The Introduction says "it is important to catalog existing standard =
functions around network management, security and troubleshooting that =
have depending upon the availability of open information to function." =
Using the word "standard" here is misleading; some of the described =
functions are not envisioned or enshrined by Internet Standards.

* The Introduction says "The IETF reiterates its view that pervasive =
monitoring is an attack..."  It's odd to have an Informational document =
"reiterate" a BCP.

* Much of the Introduction motivates this document as being about =
"network management, security and troubleshooting." Then, later, it =
inserts things like "monitoring services", policy enforcement, and =
parental controls. These are qualitatively very different things. Being =
able to monitor and run the network to provide a service is not the same =
as being able to impose your will upon the users of that service. =
Elevating the latter to the status of the former is not something we =
should even unintentionally imply, even if it is common practice.

* Section 1.1 asserts that "Increased use of encryption (either =
opportunistic or authenticated) will impact operations for security and =
network management, causing a shift in how these functions are =
performed." This is an assertion about the future that's quite strong. I =
could see it saying that they *have* impacted, and then giving examples, =
or that they *might* impact them in the future, but asserting that it =
*will* impact them seems like an assertion that doesn't have IETF =
consensus.

* Section 2.6.5 talks about injecting HTTP headers into a connection and =
fails to note the significant privacy issues brought about by this =
practice. Using encryption to defeat this is, to many in the IETF =
community, a feature, not a bug.


Hope this helps,

--
Mark Nottingham   https://www.mnot.net/

